hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.9 Data transfer | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.9.1 Acknowledged mode | The SNDCP entity shall initiate acknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated and if acknowledged LLC operation has been established. The N-PDU number in acknowledged mode is a number assigned to each N-PDU received by SNDCP through an SN-DATA.request. N-PDU numbers for different NSAPIs shall be assigned independently. The N-PDU number shall be included in the SNDCP header of the first segment of an N-PDU. Two variables, the Send N-PDU number and the Receive N-PDU number, shall be maintained for each NSAPI using acknowledged peer-to-peer LLC operation. When an NSAPI using acknowledged peer-to-peer LLC operation is activated, the Send N-PDU number and the Receive N-PDU number shall be set to 0. The Send N-PDU number and Receive N-PDU number shall also be set as described in subclause 5.1.2.22. Modulo 256 operation shall be applied to the Send N-PDU number and the Receive N-PDU number. Upon reception of an SN-DATA.request, the SNDCP entity shall assign to the N-PDU received the current value of the Send N-PDU number as the N-PDU number, increment the Send N-PDU number by 1, perform the compression and segmentation functions, then forward the SN-PDU(s) in LL-DATA.request to the LLC layer. If an N-PDU number is already present in the SN-DATA.request, then no new N-PDU number shall be assigned to the N-PDU, and the Send N-PDU number shall not be incremented. The N-PDU shall be stored into a buffer in the SNDCP entity. The buffered N-PDU shall be deleted when the SN-DATA PDU carrying the last segment of the N-PDU is confirmed by an LL-DATA.confirm primitive, or when the entire N-PDU is confirmed by an SNSM-SEQUENCE.indication primitive. During normal operation (i.e., not in the recovery state), when the peer SNDCP entity receives the SN-PDU(s) in an LL-DATA.indication primitive, the SNDCP entity shall reassemble and decompress the SN-PDU(s) to obtain the N-PDU, increment the Receive N-PDU number by 1, and forward the N-PDU to the SNDCP user with the SN-DATA.indication. The correct SNDCP user is identified by the NSAPI field in the SN-PDU(s). In the recovery state, after reassembling and decompressing the SN-PDU(s): - if the N-PDU number of the received N-PDU is equal to the Receive N-PDU number, then the Receive N-PDU number shall be incremented by 1, the recovery state shall be exited and normal operation shall resume for the received N-PDU and all subsequently-received N-PDUs; and - otherwise, the N-PDU shall be discarded. After the SNDCP entity in the SGSN receives an SNSM-STOP-ASSIGN.indication primitive for an NSAPI using acknowledged peer-to-peer LLC operation, it shall stop assigning N-PDU number to N-PDUs received through the SN-DATA.request primitive. If an SN-DATA PDU (T bit set to 0) is received by an NSAPI that does not use acknowledged mode, the PDU shall be ignored without error notification. Originator SNDCP LLC Acknowledgement LL-DATA.req LL-DATA.ind LL-DATA.cnf SNDCP user Receiver SNDCP LLC SNDCP user SN-DATA.req SN-DATA.ind Figure 13: SNDCP acknowledged data transfer ETSI ETSI TS 101 297 V7.3.0 (2000-03) 39 (GSM 04.65 version 7.3.0 Release 1998) |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.9.2 Unacknowledged mode | The SNDCP entity shall initiate unacknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated. The SNDCP entity may initiate unacknowledged data transmission even if the acknowledged peer-to-peer operation is not established for that NSAPI. The N-PDU number in unacknowledged mode is a number assigned to each N-PDU received by SNDCP through an SN-UNITDATA.request. N-PDU numbers for different NSAPIs shall be assigned independently. The N-PDU number shall be included in the SNDCP header of every SN-UNITDATA PDU. A variable, the Send N-PDU number (unacknowledged), shall be maintained for each NSAPI using unacknowledged peer-to-peer LLC operation. When an NSAPI using unacknowledged peer-to-peer LLC operation is activated, the Send N-PDU number (unacknowledged) shall be set to 0. The Send N-PDU number (unacknowledged) shall also be set as described in subclauses 5.1.2.1 and 5.1.2.22. Modulo 4096 operation shall be applied to the Send N-PDU number (unacknowledged). Upon reception of an SN-UNITDATA.request, the SNDCP entity shall assign the current value of the Send N-PDU number (unacknowledged) as the N-PDU number of the N-PDU received, increment Send N-PDU number (unacknowledged) by 1, compress and segment the information, then forward the SN-PDU(s) in LL-UNITDATA.request to the LLC layer. The N-PDU shall be deleted immediately after the data has been delivered to the LLC layer. When the peer SNDCP entity receives the SN-PDU(s) in the LL-UNITDATA.indication primitive, the SNDCP entity shall reassemble and decompress the SN-PDU(s) to obtain the N-PDU, then forwards it to the SNDCP user with the SN-UNITDATA.indication. The correct SNDCP user is identified by the NSAPI field in the SN-PDU(s). If an SN-UNITDATA PDU (T bit set to 1) is received by an NSAPI that does not use unacknowledged mode, the PDU shall be ignored without error notification. The SNDCP entity shall detect lost SN-PDUs. The SNDCP entity shall discard duplicate SN-PDUs and re-order out-of- sequence SN-PDUs, if possible. Originator SNDCP LLC LL-UNITDATA.req LL-UNITDATA.ind SNDCP user Receiver SNDCP LLC SNDCP user SN-UNITDATA.req SN-UNITDATA.ind Figure 14: SNDCP unacknowledged data transfer 6.10 Possible combinations of SNDCP protocol functions and their connection to service access points The following combinations of SNDCP protocol functions are allowed: - One or several NSAPIs may use one SAPI. - Only one SAPI shall be used by one NSAPI. - One or several NSAPIs may use the same protocol control information compression entity. - One NSAPI may use zero, one, or several protocol control information compression entities. - One or several NSAPIs may use the same data compression entity. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 40 (GSM 04.65 version 7.3.0 Release 1998) - One NSAPI may use zero, one, or several data compression entities. - Separate data compression entities shall be used for SN-DATA and SN-UNITDATA PDUs. - Separate protocol control information compression entities shall be used for SN-DATA and SN-UNITDATA PDUs. - One data compression entity shall be connected to one SAPI. - One protocol control information compression entity shall be connected to one SAPI. - One or several protocol control information compression entities may be connected to the same data compression entity. - One protocol control information compression entity shall be connected to zero, one, or several data compression entities. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7 Definition of SN-PDU | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1 Format convention | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1.1 Numbering convention | The convention used in the present document is illustrated in Figure 15. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to N. Bit 8 7 6 5 4 3 2 1 Oct 1 2 … N-1 N Figure 15: Format convention |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1.2 Order of transmission | SN-PDUs are transferred between the SNDCP layer and LLC layer in units of octets, in ascending numerical octet order (i.e., octet 1, 2, …, N-1, N). The order of bit transmission is specific to the underlying protocols used across the Um interface and the Gb interface. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1.3 Field mapping convention | When a field is contained within a single octet, the lowest bit number of the field represents the lowest order value. When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of the field contained in a given octet the lowest bit number represents the lowest order value. For example, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bit number within the octet. Figure 16 illustrates a field that spans from bit (1, 3) to bit (2, 7). The high order bit of the field is mapped on bit (1, 3) and the low order bit is mapped on bit (2, 7). ETSI ETSI TS 101 297 V7.3.0 (2000-03) 41 (GSM 04.65 version 7.3.0 Release 1998) Bit 8 7 6 5 4 3 2 1 1st octet of field 24 23 22 2nd octet of field 21 20 Figure 16: Field mapping convention Figure 17 illustrates an NSAPI field that spans from bit (1,8) to bit (2,1). NSAPI 15 is mapped to bit (1,8) and the other NSAPIs are mapped in decreasingly order until NSAPI 0 that is mapped to bit (2,1). A bit set to 0 means that the compression entity is not applicable to the corresponding NSAPI. A bit set to 1 means that the compression entity is applicable to the corresponding NSAPI. Bit 8 7 6 5 4 3 2 1 1st octet of field 15 14 13 12 11 10 9 8 2nd octet of field 7 6 5 4 3 2 1 0 Figure 17: NSAPI mapping convention |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.2 SN-PDU Formats | Each SN-PDU shall contain an integral number of octets, and shall comprise a header part and a data part. An SN-PDU shall contain data from a single N-PDU only. Two different SN-PDU formats are defined. The SN-DATA PDU shall be used for acknowledged data transfer and SN-UNITDATA PDU for unacknowledged data transfer. Bit 8 7 6 5 4 3 2 1 Oct 1 X F T M NSAPI 2 DCOMP PCOMP 3 N-PDU number - acknowledged mode … Data segment N Figure 18: SN-DATA PDU format Bit 8 7 6 5 4 3 2 1 Oct 1 X F T M NSAPI 2 DCOMP PCOMP 3 Segment number N-PDU number - unacknowledged mode 4 N-PDU number - unacknowledged mode (continued) … Data segment N Figure 19: SN-UNITDATA PDU format More bit (M): 0 Last segment of N-PDU. 1 Not the last segment of N-PDU, more segments to follow. SN-PDU Type (T): 0 SN-DATA PDU. 1 SN-UNITDATA PDU. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 42 (GSM 04.65 version 7.3.0 Release 1998) First segment indicator bit (F): 0 This SN-PDU is not the first segment of an N-PDU. The octet including DCOMP and PCOMP is not included in the SN-DATA PDU or SN-UNITDATA PDU format. Also the octet for N-PDU number for acknowledged mode is not included in the SN-DATA PDU format. 1 This SN-PDU is the first segment of an N-PDU. The octet for DCOMP and PCOMP is included in the SN-DATA PDU or SN-UNITDATA PDU format. Also the octet for N-PDU number for acknowledged mode is included in the SN-DATA PDU format. Spare bit (X): 0 Shall be set to 0 by the transmitting SNDCP entity and ignored by the receiving SNDCP entity. NSAPI: 0 Escape mechanism for future extensions. 1 Point-to-Multipoint Multicast (PTM-M) information. 2-4 Reserved for future use. 5-15 Dynamically allocated NSAPI value (see subclause 6.1). SN-PDU with an unallocated NSAPI value shall be ignored by the receiving SNDCP entity without error notification. Data compression coding (DCOMP): 0 No compression. 1-14 Points to the data compression identifier negotiated dynamically (see subclause 6.6). 15 Reserved for future extensions. SN-PDU with an unallocated DCOMP value shall be ignored by the receiving SNDCP entity without error notification. Protocol control information compression coding (PCOMP): 0 No compression. 1-14 Points to the protocol control information compression identifier negotiated dynamically (see subclause 6.5). 15 Reserved for future extensions. SN-PDU with an unallocated PCOMP value shall be ignored by the receiving SNDCP entity without error notification. Segment number: 0-15 Sequence number for segments carrying an N-PDU. N-PDU number - acknowledged mode: 0-255 N-PDU number of the N-PDU. N-PDU number - unacknowledged mode: 0-4095 N-PDU number of the N-PDU. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 43 (GSM 04.65 version 7.3.0 Release 1998) |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 8 SNDCP XID parameters | The SNDCP XID parameters are shown in Table 8: Table 8: SNDCP XID parameters Parameter name Parameter Type Length Format Range Default value Units Sense of negotiation Version number 0 1 0000bbbb 0-15 0 - down Data Compression 1 variable See subclause 6.6.1 Protocol Control Information Compression 2 variable See subclause 6.5.1 NOTE: The current version of SNDCP is 0. This is also the default value for the version number. It is assumed that the future versions are backward compatible with former ones. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 44 (GSM 04.65 version 7.3.0 Release 1998) Annex A (informative): Change Request History SMG# CR# REV. NEW REV. SUBJECT s23 new 2.0.0 5.0.0 GSM 04.65 GPRS; Subnetwork Dependent Convergence Protocol s24 A001 5.0.0 5.1.0 Introduction of new primitive s24 A003 5.0.0 5.1.0 Introduction of header compression for SN-UNITDATA s24 A004 5.0.0 5.1.0 Introduction of data compression for SN-UNITDATA s24 A005 5.0.0 5.1.0 SNDCP XID negotiation s24 A007 5.0.0 5.1.0 Update of service primitives s24 A008 5.0.0 5.1.0 Separation of N201-I and N201-U s24 A010 5.0.0 5.1.0 1st editorial changes s24 A011 5.0.0 5.1.0 2nd editorial changes s24 A012 5.0.0 5.1.0 Various corrections s25 A013 5.1.0 6.0.0 N-PDU buffering s25 A014 5.1.0 6.0.0 Possible combinations of SNDCP functions s25 A015 5.1.0 6.0.0 Minor modifications s25 A016 5.1.0 6.0.0 Improvements to XID-negotiation procedures s26 A017 6.0.0 6.1.0 Various improvements and editorial corrections s26 A018 6.0.0 6.1.0 Modifications/improvements s27 A020 6.1.0 6.2.0 Acknowledged LLC operation establishment and release procedure s27 A019 6.1.0 6.2.0 Corrections and clarifications s27 A022 6.1.0 6.2.0 TCP/IP header compression and Data compression s27 A024 6.1.0 6.2.0 Data transfer s27 A025 6.1.0 6.2.0 Replacement of "Segment offset" with "Segment number" s27 A021 6.1.0 6.2.0 XID negotiation editorial 6.2.0 6.2.1 Editorial changes, missed references, spell errors s28 A026 6.2.0 6.3.0 Miscellaneous clarifications and corrections s28 A027 6.2.0 6.3.0 Removal of requirement handling lower layer failure s28 A028 6.2.0 6.3.0 Suspension of PDU transfer during establishment and SNDCP XID negotiation s28 A029 6.2.0 6.3.0 Adding a length field to parameter 0 (SNDCP version) s28 A030 6.2.0 6.3.0 TCP/IP header compression negotiation and PCOMP assignment s28 A032 6.2.0 6.3.0 N-PDU number for SN-DATA PDUs s28 A033 6.2.0 6.3.0 Negotiation of parameters of compression entities used with acknowledged LLC operation s28 A034 6.2.0 6.3.0 Initialization of establishment and XID negotiation s28 A035 6.2.0 6.3.0 Introduce the reset procedure for inter-SGSN RA update s28 A036 6.2.1 6.3.0 Corrections to XID parameters s28 A037 6.2.0 6.3.0 Corrections, clarifications and alignment of service primitives s29 A038r1 6.3.0 6.4.0 Improving the user data loss-less inter-SGSN RA update s29 A039r1 6.3.0 6.4.0 XID collision corrections CN#5 A043r1 7.0.0 7.1.0 XID collision corrections CN#5 A044 7.0.0 7.1.0 XID negotiation during PDP context deactivation and modification CN#5 A045 7.0.0 7.1.0 Reset cancels outstanding requests CN#5 A052r1 7.0.0 7.1.0 Failure of Layer-3 XID negotiation CN#5 A056 7.0.0 7.1.0 V.42bis compression CN#6 A059 7.1.1 7.2.0 Using LL-Establish to negotiate protocol control information compression entities CN#6 A061 7.1.1 7.2.0 Including explicit parameters in SNDCP XID responses S31 A067 7.2.0 7.3.0 SNDCPC behaviour after N200LLC retransmissions S31 A069r2 7.2.0 7.3.0 Re-establishment after LL-Reset.ind ETSI ETSI TS 101 297 V7.3.0 (2000-03) 45 (GSM 04.65 version 7.3.0 Release 1998) History Document history V7.0.0 September 1999 Publication V7.1.1 November 1999 Publication V7.3.0 March 2000 Publication |
5674c1ed15972156beea0b9e811e204d | 101 293 | 1 Scope | This document specifies for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by ETSI SMG, those ME functions which are required for conformance testing purposes only. However, except for the Electrical Man Machine Interface (EMMI) and the Multi-slot TCH Loops, they are required for every mobile station. For conformance tests, functions are activated via the radio interface, test SIM or dedicated pins. These functions must be capable of being activated when a test SIM is present but must not function with any other (e.g. network) SIM present except where otherwise stated within this specification. In this state, the MS must be able to perform all functions specified in this TS; in addition however, the special conformance testing functions must be operational. The special conformance testing functions of the ME are enabled by use of a dedicated Subscriber Identity Module (test SIM, see GSM 11.10-1 Annex 4). SIM, in general, is described in GSM 11.11. The ME recognizes the test SIM by the Administrative Data Field. This TS applies to the public land mobile radio service in the GSM900 and DCS1800 systems, using constant envelope modulation and operating on radio frequencies in the 900 and 1800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle. This TS is part of the GSM-series of technical specifications. This TS neither replaces any of the other GSM technical specifications or GSM related TS, nor is it created to provide full understanding of (or parts of) the GSM900 and DCS1800 systems. This TS applies to the unit which includes the hardware to establish a connection across the radio interface. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 2 Normative references | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. - A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] ETR 100 (GSM 01.04): "Digital cellular telecommunication system (Phase 2); Abbreviations and acronyms". [2] GSM 04.07 (ETS 300 556): "Digital cellular telecommunication system (Phase 2); Mobile radio interface signalling layer 3 General aspects". [3] GSM 04.08 (ETS 300 557): "Digital cellular telecommunication system (Phase 2); Mobile radio interface layer 3 specification". [4] GSM 11.10 (ETS 300 607): “Digital cellular telecommunication system (Phase 2); Mobile Station (MS) conformance specification; Part 1: Conformance specification” [5] GSM 11.11 (ETS 300 608): "Digital cellular telecommunication system (Phase 2); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". [6] GSM 11.12 (ETS 300 641): “Digital cellular telecommunications system (Phase 2); Specification of the 3 Volt Subscriber Identity Module - Mobile Equipment (SIM - ME) interface”. ETSI TS 101 293 V5.1.0 (1998-10) 7 GSM 04.14 version 5.1.0 Release 1996 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 3 Definitions, conventions, and applicability | For abbreviations and acronyms, see GSM 01.04. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 3.1 Mobile station definition and configurations | In this TS, a MS can be: - a vehicle mounted station; - a portable station; - a handheld station; - a vehicle mounted/portable station; - a vehicle mounted/handheld station. For a more detailed description of MS-configurations, see GSM 02.06. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 3.2 Applicability | This TS is applicable to all MSs. 4 Activation and deactivation of special test functions in the MS The functions described in this TS can be activated and deactivated from a SS by sending appropriate layer 3 commands to the MS. The protocol discriminator to be used is defined in GSM 04.08, subclause 10.2. The layer 3 commands are sent on the DCCH. On layer 2, SAPI 0 is used in acknowledged mode. Apart from sending the appropriate deactivation command to the MS the functions can be deactivated by switching off the MS or removing the test SIM. The following test functions can be activated (and deactivated): - TCH Loop; - TCH Burst-by-Burst Loop; - Multi-slot Loop; - Electrical MMI; - Test via DAI. The TCH loops and the test via DAI are test functions which are mutually exclusive. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5 Internal test loops | A number of internal test loops are required providing access to isolated functions of the MS without introducing new physical interfaces just for the reason of type approval testing. Fig 5-1 shows a functional block diagram of a reference MS containing the different test loops. NOTE: It should be emphasized that these test loops only describe the functional behaviour of the MS with respect to its external interfaces; physical implementation of the loops is completely left open to the manufacturer. A particular loop is activated in an MS by transmitting the appropriate command message to the MS. ETSI TS 101 293 V5.1.0 (1998-10) 8 GSM 04.14 version 5.1.0 Release 1996 Channel decoder (speech) Channel encoder (speech) Channel decoder (signal.) Channel encoder (signal.) Channel decoder (data) Channel encoder (data) Demo- dulator Modu- lator Control part Terminal adapter or ADC DAC System Simulator Speech decoder Speech encoder (Digital Audio Interface) S R Loop A/B/D/E/F/H Loop A/B/D/E/F Decryp- tion Encryp- tion Loop C/G NOTE: In the case of loops A and B, when a TCH/EFS is used, the MS loops back 244 bits instead of 260 bits, see subclause 5.1.2.1 and 5.1.3.1. Figure 1: Test loops in the MS |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1 Single-slot TCH loops | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.1 Purpose of Single-slot TCH loops | To establish a transparent loop for TCH blocks a TCH must be active between the SS and MS. The TCH may be full or half rate, speech or data of any rate specified in the GSM system. Six types of Single-slot TCH loop back are defined. The first (A) includes the signalling of erased frames and is used to determine Frame Erasure Ratio (FER) and Residual Bit Error Ratio (RBER) for speech TCH and Bit Error Ratio (BER) for any data TCH. The second type (B) is required to determine Class II bit error ratio for the speech TCH. With the third loop (C) the 114 information bits of each TCH burst (excluding stealing flags) prior to applying benefit of the channel decoder, but after decryption, shall be transmitted in an uplink burst. (Equivalent error rate to TCH/FS Class II). All that is received shall be re-transmitted regardless of the state of the received midamble. The midamble in the uplink bursts shall be the normal midamble used by the MS. SACCH and idle bursts are not looped back. ETSI TS 101 293 V5.1.0 (1998-10) 9 GSM 04.14 version 5.1.0 Release 1996 The fourth loop (D) includes the signalling of erased frames and unreliable frames and is used to determine Unreliable Frame Ratio (UFR) and Residual Bit Error Ratio (RBER) for TCH/HS. The fifth loop (E) includes the signalling of erased SID frames and is used to determine Erased SID Frame Rate (ESIDR) and Residual Bit Error Ratio (RBER) for TCH/HS. The sixth loop (F) includes the signalling of erased valid SID frames and is used to determine Erased Valid SID Frame Rate (EVSIDR) and Residual Bit Error Ratio (RBER) for TCH/HS. NOTE: Measurement of TCH/FS chip BER is approximately five times faster using loop C rather than loop B. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.2 TCH loop including signalling of erased frames (A) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.2.1 Procedure | The SS orders the MS to close its TCH loop by transmitting a CLOSE_TCH_LOOP_CMD message, specifying the TCH to be looped and that erased frames are to be signalled by the MS. The SS then starts timer TT01. If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE_TCH_LOOP_CMD message. If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE_TCH_LOOP_ACK message. Upon reception of that message the SS stops timer TT01. After the MS has closed its TCH loop, every good speech frame or any user data frame received by the MS on the specified TCH (downlink) shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH (uplink). In the case where TCH is TCH/FS or TCH/HS, the MS shall loop back the 260 bits after normal channel decoding. In the case where TCH is TCH/EFS, the MS shall loop back the 244 bits after normal and preliminary channel decoding. If the channel decoder detects a bad speech frame , then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH (uplink). If the MS decodes stealing flags as indicating an FACCH frame, then there is no defined response for the MS to the channel encoder for transmission on the TCH (uplink). The FACCH channel shall operate as normal. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.3 Speech TCH loop without signalling of erased frames (B) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.3.1 Procedure | The SS orders the MS to close its TCH loop by transmitting a CLOSE_TCH_LOOP_CMD message, specifying the TCH to be looped. The SS then starts timer TT01. If no TCH is active or any test loop is already closed, the MS shall ignore any CLOSE_TCH_LOOP_CMD message. If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE_TCH_LOOP_ACK. Upon reception of that message the SS stops timer TT01. After the MS has closed its TCH loop, any speech frame received by the MS on the specified TCH (downlink) shall be taken from the output of the channel decoder, input to the channel encoder, and transmitted on the same TCH (uplink). In the case where TCH is TCH/FS or TCH/HS, the MS shall loop back the 260 bits after normal channel decoding. In the case where TCH is TCH/EFS, the MS shall loop back the 244 bits after normal and preliminary channel decoding. The SS should avoid using the FACCH downlink in this situation until the test is complete. ETSI TS 101 293 V5.1.0 (1998-10) 10 GSM 04.14 version 5.1.0 Release 1996 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.4 TCH burst-by-burst loop (C) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.4.1 Applicability | The test loop shall be implemented by all ME, supporting any TCH. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.4.2 Procedure | Establishment and clearing of the loop is performed at ideal radio conditions. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.4.3 Establishment | - The establishment shall be commanded by transmitting a CLOSE_TCH_LOOP_CMD message. The SS then starts timer TT01. This command shall be acknowledged by the MS with a CLOSE_TCH_LOOP_ACK message. Upon receipt of that message the SS stops timer TT01. The MS shall establish the loop within one reporting period [SACCH-block = 104 frames] from the sending of the CLOSE_TCH_LOOP_ACK. - If no TCH is active or any test loop is already closed, the MS shall ignore any CLOSE_TCH_LOOP_CMD message. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.4.4 Operation | - The round trip delay (RTD), which is the number of TCH frames between the reception of one burst at the MS, and the transmission of the same burst (on the uplink) shall be less than 26 TDMA frames. The actual value shall be declared for the implementation to be tested. NOTE 1: The RTD can be as long as required to receive the number of interleaved burst for the relevant TCH. NOTE 2: Example of RTD = 5 TDMA Frame No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Downlink T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 Sd ... Uplink ... T1 T2 T3 T4 T5 T6 T7 Su T8 T9 T10 T11 T12 Sd = Downlink SACCH frame, Su = Uplink SACCH frame, Tn = TCH frame Note from the above that TCH frames looped back prior to the uplink SACCH (or Idle) frame are delayed on the air interface by 5 TDMA frames, but the TCN frames following the SACCH frame are delayed by 6 TDMA frames. The RTD is therefore not to be confused with the TDMA frame delay for a TCH burst, which varies depending on whether the TCH burst is before or after the uplink SACCH frame. The reason for the variable TDMA time delay is to preserve the uplink SACCH frame position in the multi-frame. Note also that the uplink SACCH data is not a looped back version of the downlink SACCH data. 5.1.5 TCH loop including signalling of erased frames and unreliable frames (D) |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.5.1 Procedure | The SS orders the MS to close its TCH loop by transmitting a CLOSE_TCH_LOOP_CMD message, specifying the TCH to be looped and that erased frames and unreliable frames are to be signalled by the MS. The SS then starts timer TT01. If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE_TCH_LOOP_CMD message. If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE_TCH_LOOP_ACK. Upon reception of that message the SS stops timer TT01. ETSI TS 101 293 V5.1.0 (1998-10) 11 GSM 04.14 version 5.1.0 Release 1996 After the MS has closed its TCH loop, every reliable speech frame (UFI = 0) received by the MS on the specified TCH/HS (downlink) shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH (uplink). If the channel decoder detects a bad speech frame or an unreliable frame (BFI = 1 or UFI = 1) or if the MS decodes the stealing flags as indicating an FACCH frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink).The FACCH channel shall operate normally. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.6 TCH loop including signalling of erased SID frames (E) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.6.1 Procedure | The SS orders the MS to close its TCH loop by transmitting a CLOSE_TCH_LOOP_CMD message, specifying the TCH to be looped and that erased SID frames are to be signalled by the MS. The SS then starts timer TT01. If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE_TCH_LOOP_CMD message. If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE_TCH_LOOP_ACK. Upon reception of that message the SS stops timer TT01. After the MS has closed its TCH loop, every valid SID frame (SID = 2) or invalid SID frame (SID = 1) received by the MS on the specified TCH/HS (downlink), shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH/HS (uplink). If the channel decoder detects an erased SID frame (SID = 0), then this shall be signalled to the SS, by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). If the MS decodes the stealing flags as indicating an FACCH frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink).The FACCH channel shall operate normally. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.7 TCH loop including signalling of erased valid SID frames (F) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.1.7.1 Procedure | The SS orders the MS to close its TCH loop by transmitting a CLOSE_TCH_LOOP_CMD message, specifying the TCH to be looped and that erased valid SID frames are to be signalled by the MS. The SS then starts timer TT01. If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE_TCH_LOOP_CMD message. If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE_TCH_LOOP_ACK. Upon reception of that message the SS stops timer TT01. After the MS has closed its TCH loop, every valid SID frame (SID = 2 and BFI = 0) received by the MS on the specified TCH/HS (downlink), shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH/HS (uplink). If the channel decoder detects an erased valid SID frame (SID = 1) or (SID = 0) or ((BFI or UFI) = 1)), then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). If the MS decodes the stealing flags as indicating an FACCH frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink).The FACCH channel shall operate normally. 5.1.8 Additional non-mandatory operating characteristics for single-slot loops In order to optimise the speed and flexibility of mobile manufacturing and repair, the following non-mandatory characteristics of the test loops are suggested: ETSI TS 101 293 V5.1.0 (1998-10) 12 GSM 04.14 version 5.1.0 Release 1996 - The normal FACCH downlink and uplink functions should ideally be maintained when the test loop is closed. In particular, channel assignments or handovers, and call termination from either the mobile or the base station simulator. - Following an assignment or handover, the loop should not open if it was closed prior to the handover. - Following call dropping or deliberate call termination, the loop should be re-opened. - The loopback functions should ideally operate with or without (i.e. no SIM) the test SIM present, but should not operate with a network SIM present. - Audio muting should be enabled when the loop is closed. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.2 Multi-slot TCH loops | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.2.1 Purpose of Multi-slot TCH loops | To establish a transparent loop for TCH blocks, from multiple slots, a TCH must be active between the SS and MS. Two types of Multi-slot TCH loop back are defined. With the first loop (G) the 114 information bits of each multi-slot TCH burst (excluding stealing flags) prior to applying benefit of the channel decoder, but after decryption (see Figure 1), shall be transmitted in an uplink burst. (Equivalent error rate to TCH/FS Class II). All that is received shall be re-transmitted regardless of the state of the received midamble. The midamble in the uplink bursts shall be the normal midamble used by the MS. SACCH and idle bursts are not looped back. The second loop (H) includes the signalling of erased frames and is used to determine Frame Erasure Ratio (FER), Residual Bit Error Ratio (RBER) and Bit Error Ratio (BER) for any multi-slot configuration TCH. Each of the two loops shall support the following mechanisms: The first (Multi-slot mechanism 1) is used to loop the TCH data of slot X of the downlink onto the TCH of the main uplink slot (for HSCSD) or the PACCH uplink slot (for GPRS). This mechanism is needed to cover the case where there are more downlink slots than uplink slots. The second (Multi-slot mechanism 2) is used to loop as many downlink slots as possible to the corresponding uplink slots, based on the following rules for HSCSD and GPRS: HSCSD – Loop back all bi-directional timeslots, and leave the unidirectional slots not looped back. This maintains the logical association with bi-directional timeslots. GPRS - Start with the first downlink slot and loop it back to the first uplink slot. Loop back the second downlink slot to the second uplink slot, and so on, until there are no more downlink slots left to loop back, or there are no more uplink slots available. It should be further noted: The order of the data on the downlink shall be preserved on the uplink. The OPEN_Multi-slot_LOOP_CMD message shall open all Multi-slot loops. Assignment to a new multi-slot configuration shall be preceded by an OPEN_Multi-slot_LOOP_CMD message to open all loops. It is the responsibility of the System Simulator (SS) to ensure that the correct configuration is enabled for the test. Test loops will be opened by the receipt of a OPEN_Multi-slot_LOOP_CMD or by disconnecting the call. Other behaviour, such as receiving a new TxLev or a channel assignment or handover to a new ARFCN will not affect the test loops. The SS should ensure that a new multislot configuration affecting an existing test loop is not included within channel assignment, handover or configuration change commands. ETSI TS 101 293 V5.1.0 (1998-10) 13 GSM 04.14 version 5.1.0 Release 1996 If the Multi-slot mechanism 1 is used and a downlink slot that is not part of the current multi-slot configuration is specified, the MS shall ignore the command and send a negative acknowledgment. The loopback state should not change. Once a loop is closed, a further loopback command shall over-ride a previous command - multiple CLOSE_Multi-slot_LOOP_CMD messages are not additive. Call disconnect for whatever reason shall open all loops. No OPEN_Multi-slot_LOOP_ACK message shall be sent. The multi-slot loopback is restricted to the TCH logical channel only. The downlink and uplink FACCH and SACCH should work as if loopback did not exist. The Multi-slot TCH loops are in addition to any Single-slot TCH loops already specified for the type of MS. Support of the Multi-slot loops is mandatory for any MS supporting a multi-slot service - currently HSCSD and GPRS. Any MS supporting the Multi-Slot loops shall activate the functions defined in this section of the specification regardless of the presence or not of a test SIM. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.2.2 Multi-slot TCH burst-by-burst loop (G) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.2.2.1 Procedure | The establishment shall be commanded by transmitting a CLOSE_Multi-slot_LOOP_CMD message. The SS then starts timer TT01. This command shall be acknowledged by the MS with a CLOSE_Multi-slot_LOOP_ACK message. Upon receipt of that message the SS stops timer TT01. The MS shall establish the loop within one reporting period [SACCH- block = 104 frames] from the sending of the CLOSE_Multi-slot_LOOP_ACK. If no TCH is active or any test loop is already closed, the MS shall ignore any CLOSE_Multi-slot_LOOP_CMD message RTD is as the same as subclause 5.1.4.4. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.2.3 Multi-slot TCH loop including signalling of erased frames (H) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.2.3.1 Procedure | The SS orders the MS to close its Multi-slot TCH loop by transmitting a CLOSE_Multi-slot_LOOP_CMD message, specifying the TCH to be looped and that erased frames are to be signalled by the MS. The SS then starts timer TT01. If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE_Multi-slot_LOOP_CMD message. If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE_Multi- slot_LOOP_ACK message. Upon reception of that message the SS stops timer TT01. After the MS has closed its TCH loop, every good speech frame or any user data frame received by the MS on the specified TCH (downlink) shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH (uplink). If the channel decoder detects a bad speech frame , then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH (uplink). If the MS decodes stealing flags as indicating an FACCH frame, then there is no defined response for the MS to the channel encoder for transmission on the TCH (uplink). The FACCH channel shall operate as normal. ETSI TS 101 293 V5.1.0 (1998-10) 14 GSM 04.14 version 5.1.0 Release 1996 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.3 Deactivating loops | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.3.1 Deactivating Single-slot TCH loops | The SS orders the MS to open any Single-slot TCH loop by transmitting an OPEN_LOOP_CMD message. If no loop is closed the MS shall ignore any OPEN_LOOP_CMD message. If a Single-slot TCH is looped, the MS shall open the loop. If the loop opened was type C, the MS shall send an OPEN_LOOP_CMD message to the SS with bit 0 of the optional acknowledgement element set to 1. All channels shall be open for normal use again. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 5.3.2 Deactivating Multi-slot TCH loops | The SS orders the MS to open any Multi-slot TCH loop by transmitting an OPEN_Multi-slot_LOOP_CMD message. If no loop is closed the MS shall ignore any OPEN_Multi-slot_LOOP_CMD message. If a Multi-slot TCH is looped, the MS shall open the loop and send a OPEN_Multi-slot_LOOP_ACK message to the SS. All channels shall be open for normal use again. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 6 Activating and deactivating EMMI | Activating EMMI requires the presence of a test SIM. EMMI shall be activated by any of the following: - switching on the MS; - inserting a test SIM; - layer 3 message on the radio interface (ACT_EMMI_CMD). When the MS is ready to receive frames, it shall send one XON message. EMMI shall be deactivated by any of the following: - switching off the MS; - removing the test SIM; - layer 3 message on the radio interface (DEACT_EMMI). NOTE: No XOF shall be sent after deactivation. The L3 message used on the radio interface to activate the EMMI is the activation command ACT_EMMI_CMD (see subclause 8.4). This message has to be acknowledged by the message ACT_EMMI_ACK on the radio interface sent by the MS (see subclause 8.5). For deactivation of the EMMI in the MS through the radio interface, the message DEACT_EMMI is defined in subclause 8.6. An acknowledgement of this message is not required. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 7 Activating and deactivating DAI tests | Purpose: to determine the routing of speech data (DAI or internal, i.e. normal mode) and which device is being tested (speech transcoder / DTX functions or A/D & D/A). Prerequisites: a dedicated channel must be established if the manufacturer has stated that the DAI is activated by means of the layer 3 message. ETSI TS 101 293 V5.1.0 (1998-10) 15 GSM 04.14 version 5.1.0 Release 1996 Procedure: the SS sends a TEST_INTERFACE message if the manufacturer has stated that the DAI is activated by means of the layer 3 message or applies the appropriate control signal on the DAI if the manufacturer has declared that the DAI is activated this way. When the test mode is established i.e. speech data comes from test interface, each new test function overrides the previous one. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8 Message definitions and contents | NOTE 1: A message received with skip indicator different from 0 will be ignored. NOTE 2: For definition of "Presence" and "Format", see GSM 04.07 subclauses 11.4 and 11.1.1. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.1 CLOSE_TCH_LOOP_CMD | This message is only sent in the direction SS to MS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 Sub-channel M V 1 where message type is: 8 7 6 5 4 3 2 1 bit no. 0 0 0 0 0 0 0 0 octet 1 and Sub-channel is: 8 7 6 5 4 3 2 1 bit no. 0 spare 0 spare 0 spare B A Z Y X octet 1 X = 0 If there is only one TCH active (so there is no choice) or if sub-channel 0 of two half rate channels is to be looped. X = 1 If sub-channel 1 of two half rate channels is to be used. Y = 0 If the looped TCH is a speech channel then the frame erasure is to be signalled, type A. Y = 1 If the looped TCH is a speech channel then frame erasure is not signalled, type B. Z = 0 The type of the loop is determined by the value Y. Z = 1 The Burst-by-Burst loop is activated, type C. The value of Y is disregarded. A = 0 and B = 0 The loop is determined by the values Z, Y and X. A = 1 and B = 0 If the looped TCH is a half rate speech channel then frame erasure and unreliable frames have to be signalled, type D. The values of Y and Z are disregarded. A = 0 and B = 1 If the looped TCH is a half rate channel sending SID frames then SID frame erasure is to be signalled, type E. The values of Y and Z are disregarded. A = 1 and B = 1 If the looped TCH is a half rate channel sending SID frames then valid SID frame erasure is to be signalled, type F. The values of Y and Z are disregarded. ETSI TS 101 293 V5.1.0 (1998-10) 16 GSM 04.14 version 5.1.0 Release 1996 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.2 CLOSE_TCH_LOOP_ACK | This message is only sent in the direction MS to SS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 where message type is: 8 7 6 5 4 3 2 1 bit no. 0 0 0 0 0 0 0 1 Octet 1 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.3 OPEN_LOOP_CMD | This message is only sent in the direction SS to MS Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 Acknowledge O TV 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 0 0 0 1 1 0 Octet 1 where Acknowledge Information Element Identifier is: 8 7 6 5 4 3 2 1 Bit no. 1 0 0 0 Octet 1 and the Acknowledge Information Element contents are: 4 3 2 1 Bit no. 0 spare 0 spare 0 spare 1 Octet 1 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.4 CLOSE_Multi-slot_LOOP_CMD | This message is only sent in the direction SS to MS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 Loop type M V 1 ETSI TS 101 293 V5.1.0 (1998-10) 17 GSM 04.14 version 5.1.0 Release 1996 where message type is: 8 7 6 5 4 3 2 1 bit no. 0 0 1 0 0 0 0 0 octet 1 and Loop type is: 8 7 6 5 4 3 2 1 bit no. TN Loop mechanism CHC octet 1 CHC, Channel coding 00 = channel coding not needed. The Burst-by-Burst loop is activated, type G 01 = channel coding needed. Frame eraure is to be signalled, type H All other values reserved Loop mechanism 000 = Multi-slot mechanism 1 001 = Multi-slot mechanism 2 All other values reserved TN, Timeslot number Timeslot number used only if Loop mechanism indicates Multi-slot mechanism 1 The TN field is coded as the binary representation of the timeslot number as defined in GSM 05.10. Range: 0 to 7 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.5 CLOSE_Multi-slot_LOOP_ACK | This message is only sent in the direction MS to SS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 Result M V 1 where message type is: 8 7 6 5 4 3 2 1 bit no. 0 0 1 0 0 0 0 1 Octet 1 and Result is: 8 7 6 5 4 3 2 1 bit no. 0 spare 0 spare CHC Loop mechanism Error Ind octet 1 CHC, Channel coding 00 = channel coding not needed. The Burst-by-Burst loop is activated, type G 01 = channel coding needed. Frame eraure is to be signalled, type H All other values reserved Loop mechanism 000 = Multi-slot mechanism 1 001 = Multi-slot mechanism 2 All other values reserved ETSI TS 101 293 V5.1.0 (1998-10) 18 GSM 04.14 version 5.1.0 Release 1996 Error Ind, Error indication 0 = Multi-slot TCH loop was closed successfully 1 = Multi-slot TCH loop was not closed due to error |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.6 OPEN_Multi-slot_LOOP_CMD | This message is only sent in the direction SS to MS Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 1 0 0 0 1 0 Octet 1 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.7 OPEN_Multi-slot_LOOP_ACK | This message is only sent in the direction MS to SS Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 1 0 0 0 1 1 Octet 1 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.8 Command for the activation of the EMMI, ACT_EMMI_CMD | This message is only sent in the direction SS to MS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V ½ Skip indicator GSM 04.07 sect. 11.2.2 M V ½ Message type M V 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 0 0 1 1 0 0 Octet 1 ETSI TS 101 293 V5.1.0 (1998-10) 19 GSM 04.14 version 5.1.0 Release 1996 8.9 Acknowledge of the activation of the EMMI, ACT_EMMI_ACK This message is only sent in the direction MS to SS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V 1/2 Skip indicator GSM 04.07 sect. 11.2.2 M V 1/2 Message type M V 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 0 0 1 1 0 1 Octet 1 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.10 Deactivation of the EMMI, DEACT_EMMI | This message is only sent in the direction SS to MS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V 1/2 Skip indicator GSM 04.07 sect. 11.2.2 M V 1/2 Message type M V 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 0 1 0 0 0 0 Octet 1 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.11 Test_Interface | This message is only sent in the direction SS to MS. Information Element Reference Presence Format Length Protocol discriminator GSM 04.07 sect. 11.2.1 M V 1/2 Skip indicator GSM 04.07 sect. 11.2.2 M V 1/2 Message type M V 1 Tested device M V 1 where message type is: 8 7 6 5 4 3 2 1 Bit no. 0 0 0 1 0 1 0 0 Octet 1 and Tested device is: 8 7 6 5 4 3 2 1 Bit no. 0 spare 0 spare 0 spare 0 spare 0 spare Tested devices Octet 1 ETSI TS 101 293 V5.1.0 (1998-10) 20 GSM 04.14 version 5.1.0 Release 1996 Tested devices: 000 = normal operation (no tested device via DAI) 001 = test of speech decoder / DTX functions (downlink) 010 = test of speech encoder / DTX functions (uplink) 100 = test of acoustic devices and A/D & D/A. All other values are reserved. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 8.12 Timer values | TT01: To be started when a CLOSE_TCH_LOOP_CMD or CLOSE_Multi-slot_LOOP_CMD is sent. To be stopped when the corresponding CLOSE_TCH_LOOP_ACK or CLOSE_Multi-slot_LOOP_ACK is received. Recommended value: [2.5 seconds]. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9 Electrical Man Machine Interface (EMMI) | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.1 Use of the EMMI | Conformity tests of mobile stations are made using the system simulator specified in [Annex 4]. Test signals are sent on the Um interface, and actions of the MS are registered. The Electrical Man Machine Interface (EMMI) is a half duplex communication link between the SS and the MS by which it is possible to automatically register the status, indications and performance of the MS. It is also possible to simulate actions normally made by the user on the keyboard of the MS. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.2 Formal aspects | i) The EMMI is optional for the ME. ii) The EMMI is mandatory for the SS. iii) If the EMMI is to be used in conformance testing of an MS, it shall be possible to connect the SS to a connector on the MS, or to an adapter connected to the same MS. If an adapter is to be used, it shall be provided by the manufacturer. iv) If the MS fulfils the requirements performed with the use of an EMMI, the MS is regarded as having passed that test. v) If the MS is rejected in a test performed with EMMI, the test shall be repeated on the same mobile with the device carrying the EMMI to the MS removed. The MS shall be regarded as fulfilling the requirements, if it then passes the test. vi) When using the EMMI, the MS does not necessarily conform to the RF requirements. Therefore, tests concerning Rx and Tx parameters on MS with integral antenna and cabinet radiation tests for all types of MS will never be performed with the use of the EMMI. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.3 Layered structure of the interface | The definition of the EMMI is divided into three different layers. On layer 1 the use of a 25-pole socket with standard electrical characteristics for serial communication is defined. On layer 2, an extremely simple frame oriented protocol is defined. On layer 3, messages for control and verification of functions and indications are defined. Each layer is defined independently of surrounding layers, and is therefore easy to replace. The EMMI protocol structure takes into account that the SS only sends and receives layer 3 frames when the corresponding step within a test case is to be performed. ETSI TS 101 293 V5.1.0 (1998-10) 21 GSM 04.14 version 5.1.0 Release 1996 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.4 Terminology | EMMI Electrical Man Machine Interface MI Message Identifier ME Mobile Equipment MS Mobile Station SS System Simulator Frame Used on layer 2 to transfer messages to and from layer 3 Message Information on layer 3 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5 Description of the EMMI | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.1 EMMI, Layer 1 | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.1.1 Mechanical and electrical characteristics | If implemented, the EMMI interface shall use the same connector as the Digital Audio Interface (DAI), described in subclause 10.3. The pin assignments for the EMMI shall be as follows: Pin Function Source 2 Transmitted data SS 3 Received data MS 7 EMMI signal ground The electrical characteristics of the interface shall be as given in subclause 10.3.2. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.1.2 Transmission and reception characteristics | The EMMI uses asynchronous serial data transmission with 1 start bit (S), 8 data bits (D1 to D8), no parity and 1 stop bit (E). Table 3: Use of start and stop bits S D1 D2 D3 D4 D5 D6 D7 D8 E The conditions on start and stop characters are defined in REC CCITT V.1. The transmission rates are: 600, 1200, 2400, 4800, 9600 bits per second. The ME shall support at least one of these speeds. The SS will adapt its rate (manually or by MMI) to this ME rate. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2 EMMI, layer 2 | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.1 General structure | On layer 2, frames are used to carry data from higher layers. Frames consist of one or several octets. One frame with variable length is used to carry data from higher layers, and four other frames with the length of one character is used to control the flow of frames. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.2 Control frames | Special frames have been assigned to control the flow of frames on layer 2. They are only one octet long. ETSI TS 101 293 V5.1.0 (1998-10) 22 GSM 04.14 version 5.1.0 Release 1996 Table 4: Characters for flow control Abbr. Meaning Dec.value Bit pattern ACK Acknowledge 06 0000 0110 NAK Not Acknowledge 21 0001 0101 XON Resume sending data 17 0001 0001 XOF Stop sending data 19 0001 0011 |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.3 Frame structure | Two octets, called characters, indicate start and stop of I-frames. Table 5: Start and stop characters Abbr. Meaning Dec.value Bit pattern STX Start of data 02 0000 0010 ETX End of data 03 0000 0011 Information from higher layers are transferred in I-frames with the following structure. Table 6: Information structure in I-frames Field name No of octet Value Start at octet no Note Start 1 Character STX 1 - Length 1 Length of data 2 a1) Data 0-255 Content of data 3 a2) Check 1 Error detection Length+2 a3) End 1 Character ETX Length+3 NOTES: a1) Length: The total number of data octets in the data field of the frame is calculated. The value shall be in the range of (0..255 decimal). The corresponding binary value is put into the length field. a2) Data: Data to and from higher layers are in the form of octets (groups of 8 digital bits). a3) Check: Longitudinal checksum is created by exclusive OR on all characters starting with the Start field and ending with the last octet before the Check field. The value, one octet, is mapped into the Check field. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.4 Flow of I-frames on layer 2 | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.4.1 Transmission of frames | A multiple frame starts with the first octet being the character STX and stops with the last octet with content ETX. The time between the start bits of two consecutive octets shall not be longer than T22. octet n octet n + 1 <------------------------ T22------------------ > The time between two frames is measured from the start bit of the last octet of the nth frame to the start bit of the first octet of the n+1st frame. The time between two consecutive frames shall not be less than T23. STX Frame n ETX STX frame n+1 ETX < --------- T23--------- > |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.4.2 Reception of frames | Start of a frame is defined as (more than T22*2 since previous reception of octet) AND (reception of STX). ETSI TS 101 293 V5.1.0 (1998-10) 23 GSM 04.14 version 5.1.0 Release 1996 End of a frame is defined as (reception of ETX in octet number (length+2)) OR (more than T22*2 since last reception of octet). |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.4.3 Use of ACK and NAK on receiving side | ACK is used by the MS to acknowledge a frame on receiving side if all the following conditions are fulfilled. Otherwise NAK is used. 1) The content of Start field is STX. 2) The content of Check field corresponds to the exclusive OR sum of previous octets in the frame. 3) The content of the last octet is ETX. NAK is used by the SS to request retransmission of a frame. Otherwise ACK is used. NOTE: NAK shall not be used for layer 3 errors, if the layer 2 frame is correct. If the meaning of a layer 3 message is undefined or not performable, then the problem is solved with layer 3 messages. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.4.4 Use of XON and XOF | XON and XOF are used for flow control of layer 2. XOF is sent if the unit (MS or SS) due to internal processing is not capable of receiving a following frame when a frame is being received. XON is sent if XOF has been sent previously, but the reason for that XOF-transmission no longer exists. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.2.4.5 Parameters on layer 2 | Table 7: Timer values on layer 2 Bit rate Value of T22 Value of T23 600 25.0 ms 58.3 ms 1200 12.5 ms 29.2 ms 2400 6.3 ms 14.6 ms 4800 3.1 ms 7.3 ms 9600 1.6 ms 3.6 ms |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.3 EMMI, layer 3 | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.3.1 Message structure | Messages are used on layer 3. They are defined by Message Identifiers (MI) in the range of (0..255). The message identifier is always the first, and often the only, octet of the message. Table 8: Use of message identifiers MI Use 0-49 Not used. 50-179 General messages. All undefined values reserved for further evolution of the EMMI. 180-209 ME-type dependent blocks, may be used by the SS as a sender or receiver, if so requested by the manufacturer. Undefined values available for the manufacturer. 210-239 ME-type dependent blocks, never to be used by the SS in conformance testing. Undefined values available for the manufacturer. 240-255 Reserved for L3 error handling. All undefined values reserved for further evolution of the EMMI. ETSI TS 101 293 V5.1.0 (1998-10) 24 GSM 04.14 version 5.1.0 Release 1996 NOTE 1: Layer 2 is transparent, but to avoid unnecessary interference from layer 3, MI with the same value as control frames on layer 2 are not used. Most of the messages, especially in the direction SS - MS contain only one octet, the message indicator. Some of the messages, especially in the direction MS - SS are quite long. NOTE 2: If the interface is limited only to the minimum required for automatic conformity testing with the electrical man machine interface, then the included L3 messages should be RQTI, KEYS, BEL1, BEL0, HOK1, HOK0, BCAP and RSTI. Table 9: Block types MI Source Value Abbr. Meaning MS SS 051 VOL1 Increase volume (***) X 052 VOL0 Decrease volume (***) X 053 RQTS Request for table, status X 054 RQTI Request for table, indication X 055 RQPL Request for power level X 056 RQBE Request for bell status X 057 RQSM Request for short message X 058 KEYS Perform keystroke sequence X 060 BEL1 Indication user alert on X 061 BEL0 Indication user alert off X 064 HOK1 Hook on X 065 HOK0 Hook off X 070 BCAP Selection of bearer capability X 080 STPO Set power level X 091 RSTS Response table, status X 092 RSTI Response table, indication X 093 RSPO Response, power level X 101 RXSM Received short message X 102 RXSN No short message received X 240 ER00 Internal malfunction detected X 241 ER01 L3 message not recognized X X 242 ER02 L3 message not performable X 255 RESE Perform hardware and software reset X NOTE 3: Functioning of this should be verified, as the volume control in the ME might be of another type (non- incremental). |
5674c1ed15972156beea0b9e811e204d | 101 293 | 9.5.3.2 Definition of messages | Messages are defined in the order of the value of the message identifier. 051 VOL1 Increase volume 052 VOL0 Decrease volume Increase/decrease volume in the loudspeaker by one step. 8 7 6 5 4 3 2 1 Octet 1 Message identifier ETSI TS 101 293 V5.1.0 (1998-10) 25 GSM 04.14 version 5.1.0 Release 1996 053 RQTS Request for table, status 054 RQTI Request for table, indication 055 RQPL Request for power level On receiving a request message RQxy, the corresponding table RSxy shall be sent. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 056 RQBE Request for bell status On receiving a request message RQBE, the internal user alert status (BEL1 or BEL0) shall be sent. BEL1 and BEL0 will indicate whether the ringing or alert procedure has been activated or not. (See also the definition of BEL1 and BEL0). 8 7 6 5 4 3 2 1 Octet 1 Message identifier 057 RQSM Request for short message In response to the RQSM request the MS shall send either the short message type using the message RXSM or, in case of no short message received, the message RXSN. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 058 KEYS Perform keystroke sequence Perform the MS function related to the received keystroke sequence. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 2 First key N Key Number N-1 The possible keystroke sequences are based on the basic public man machine interface as defined in GSM 02.30. There exists a minimum set of key characters. The codes associated with these characters are defined as follows: ETSI TS 101 293 V5.1.0 (1998-10) 26 GSM 04.14 version 5.1.0 Release 1996 Key Code (decimal) # 35 * 42 + 43 0 48 1 49 2 50 3 51 4 52 5 53 6 54 7 55 8 56 9 57 END (function) 18 SEND (function) 20 060 BEL1 Indication user alert on 061 BEL0 Indication user alert off Indication user alert shall indicate, on request of the SS, the internal status of the alert or ringing procedure. For this purpose, the SS shall send the RQBE (request for bell status) message to the MS. BEL1 shall indicate that the alert procedure is active. BEL0 shall indicate that the alert procedure is not active. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 064 HOK1 Hook on 065 HOK0 Hook off Control of the hook. The hook on/off command shall action the normal procedure associated with physically lifting the handset and replacing it whatever that maybe. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 070 BCAP Selection of bearer capability The EMMI BCAP message shall change the default bearer capability on all future calls made via the EMMI "perform keystroke sequence" message. The new default bearer capability shall be in effect until the ME is switched off or until the ME receives another EMMI BCAP message. ETSI TS 101 293 V5.1.0 (1998-10) 27 GSM 04.14 version 5.1.0 Release 1996 8 7 6 5 4 3 2 1 Octet 1 Message identifier 2 Bearer capability (see Note below) NOTE 1: The field "bearer capability" in the BCAP message is mandatory and is coded bit for bit exactly as the "bearer capability" information element as described in GSM 04.08 subclause 10.5.4.4, beginning with octet 2 (length of the bearer capability contents). Because the "bearer capability" is mandatory, the first byte of the field shall be the length of the bearer capability content and not the bearer capability information element identifier. 080 STPO Set power level Used to control the Tx power level of the ME. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 2 Power level (see Note 2 below) NOTE 2: The power level is defined as the 2nd octet of the power command information element in GSM 04.08. 091 RSTS Response table, status Response table status is sent as an answer to the corresponding request. 8 7 6 5 4 3 2 1 Octet 1 Message identifier F1 F2 2 Status field (see Note 3 below) F3 ETSI TS 101 293 V5.1.0 (1998-10) 28 GSM 04.14 version 5.1.0 Release 1996 NOTE 3: F1 0 0 0 0 Spare F2 (1=yes, 0=no) Bit 4 L2 link on SACCH established Bit 3 Speech connection on TCH establ Bit 2 Listening to BCCH Bit 1 SDCCH established F3 Bit 8 Frequency hopping (yes/no) Bit 7-1ARFCN of BCCH of serving cell 092 RSTI Response table, indication Response table indication send as an answer to the corresponding request. 8 7 6 5 4 3 2 1 Octet 1 Message identifier F1 F2 2 Indication field (see Note 4 below) NOTE 4: F1 0000000 Spare F2 (yes=1, no=0) Bit 1 Service indication On (yes/no) 093 RSPO Response, power level Response power level is sent as an answer to the corresponding request. 8 7 6 5 4 3 2 1 Octet 1 Message identifier F1 F2 2 Power Level (see Note 5 below) NOTE 5: The power level is defined as the 2nd octet of the power command information element in GSM 04.08. 101 RXSM Received short message ETSI TS 101 293 V5.1.0 (1998-10) 29 GSM 04.14 version 5.1.0 Release 1996 The message RXSM has to be sent by the MS in response to the RQSM request if a short message has been received. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 2 SM field octet 1 (see note below) N SM field octet N-1 NOTE 6: The SM field is defined as the content of the data field short message storage defined in GSM 11.11 paragraph 3.5.1, excluding byte 1, as follows: 1 byte NULL value 12 bytesTP Originating Address 12 bytesTS Service Centre Address 1 byte TP Protocol Identifier 1 byte TP Data Coding Scheme 7 bytes TP Service Centre Time Stamp 1 byte TP User Data Length up to 140 bytes TP User Data. If the length of the address for TP and for TS service centre is less than 12 bytes, the remaining bytes are filled with null values. 102 RXSN No short message received The message RXSN has to be sent by the MS in response to the RQSM request if no short message has been received. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 240 ER00 Internal malfunction detected Used to indicate to the SS that the MS has discovered an internal error. This error message is to be handled in the same manner as the layer 3 error messages (only to be sent to the SS in response to a Layer 3 message received at the MS). 8 7 6 5 4 3 2 1 Octet 1 Message identifier 2 Error indication (see Note 7 below) NOTE 7: The error indicator is defined by the manufacturer of the ME. 241 ER01 L3 message not recognized Used by the receiver to indicate to the sender that the message was correctly received, but ignored due to the fact that it was not understandable (e.g. a KEYS message with one or many values which are not part of the standard set of keys for the MSE). The message to the MS implies a request for re-sending the latest message sent. ETSI TS 101 293 V5.1.0 (1998-10) 30 GSM 04.14 version 5.1.0 Release 1996 8 7 6 5 4 3 2 1 Octet 1 Message identifier 242 ER02 L3 message not performable Used by the receiver to indicate to the sender that the message was understood, but not performable due to intentional lack of functionality in the MS (e.g. as answer to a CALL message containing a type of service which the MS is not able to use) or to a message requesting a change to a state already existent. 8 7 6 5 4 3 2 1 Octet 1 Message identifier 255 RESE Perform HW and SW reset The MS shall perform a total reset. The MS shall behave as if it has been switched "off" and "on". 8 7 6 5 4 3 2 1 Octet 1 Message identifier |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10 Digital audio interface | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.1 General | A special interface is required in order to perform the bit exact test of the speech coder/decoder and to test the SLR/RLR performance of the analogue and acoustic devices. It shall be possible to insert and extract speech data in both the transmit and receive directions. The interruption of the normal speech data paths can be commanded either by a layer 3 message over the air interface or by special control lines in the test interface. The MS need react to only one of these command methods. The manufacturer shall state which method is to be used. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.2 Formal aspects | It shall be possible to connect the SS to the ME or to an adapter connected to the ME. If an adapter is to be used, it shall be provided by the manufacturer of the ME. When using the DAI, the MS does not necessarily conform to all RF requirements. When the DAI is connected the MS shall be able to correctly send and receive on a TCH and associated channels under ideal radio conditions. NOTE: Prior to tests of the speech coder, other functional entities involved in the tests, such as the channel codec or RF units must have been verified successfully. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.3 Hardware aspect of the interface | The data exchanged on the interface are 13 bit linear PCM at 8000 samples per second, which, in order to keep the pin count low, are transferred on a duplex set of serial lines at 104 kbit/s. One additional line resets the speech transcoder and the speech A/D and D/A functions. Two lines control the data flow direction and working mode of the interface, one mode being normal operation of the MS. These lines are controlled by the SS. Another line, controlled by the MS, clocks the data as required or available. ETSI TS 101 293 V5.1.0 (1998-10) 31 GSM 04.14 version 5.1.0 Release 1996 This is described in detail below. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.3.1 Mechanical characteristics of the interface | The interface shall use a 25-pin DSUB socket, detailed in the ISO 2110 document. The ME shall use a female part. The manufacturer may provide this interface on an external test "adapter". The pin assignment of the connector shall be as follows: Pin Use Function Source 1 Chassis ground ME 2-3 EMMI Signals 4-6 Not used 7 EMMI Signal ground 8-10 Not used 11 DAI Test control 1 SS 12 DAI Signal ground 13 DAI Test control 2 SS 14-21 Not used 22 DAI Reset SS 23 DAI Data ME 24 DAI Data clock (104 kHz) ME 25 DAI Data SS NOTE: The EMMI interface is optional and is described in clause 9. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.3.2 Electrical characteristics of the interface | The state of a signal pin is defined by the voltage (V) between the pin and its associated ground as follows: Logical state Voltage v 0 or "LOW" or "ON" 0 V < v < + 0,8 V 1 or "HIGH" or "OFF" + 3,5 V < v < + 5 V undefined + 0,8 V < v < + 3,5 V forbidden v < 0 V, v > + 5 V |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.3.3 Timing characteristics of the interface | The following timing applies: Parameter Value Clock frequency 104 kHz +/- 20 ppm Duty cycle 40 to 60 % Clock rising edge time < 1 microsecond Clock falling edge time < 1 microsecond Reset pulse duration >= 4 millisecond ETSI TS 101 293 V5.1.0 (1998-10) 32 GSM 04.14 version 5.1.0 Release 1996 |<-------------------- 9,6 µs ------------------->| | | logical state | |<--- 4,8 µs +/-1 µs --->| 1 or high | | | ---------\ |<--- 4,8 µs +/-1 µs --->| /------------------\ | ..............\.|........................|./....................\.|......90% |\| |/| \| ..............|.\......................../.|......................\......50% | \ / | \ ..............|...\..................../...|........................\....10% | |\ /| | \ | | \----------------/ | | \------ | | | | logical state ^ |<->| |<->| 0 or low ---_ falling rising edge < 1µs edge < 1µs Data shall be stable during the period between 3 microseconds before and 1 microsecond after the rising edge of the clock (50% level). |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.4 Logical interface | The reset signal is active low. The data consists of 13 bit words in two's complement format, with the most significant bit transmitted first. Data are read in by the MS or SS at the rising edge and are output by the SS or MS at the falling edge of the clock, as defined in Figure 2. The clock signal is high when inactive. The two test control lines determine the routing of the speech data (DAI or internal, i.e. normal mode) and which device is being tested (speech transcoder/DTX functions or A/D & D/A) as follows: Test control line Function 1 2 Low Low Normal operation Low High Test of speech decoder / DTX functions (downlink) High Low Test of speech encoder / DTX functions (uplink) High High Test of acoustic devices and A/D & D/A The same test setup may be achieved by the layer 3 TEST_INTERFACE message (see 7 and 8.7). |
5674c1ed15972156beea0b9e811e204d | 101 293 | 10.5 Functionality of the DAI | To initiate a test, the SS shall apply the appropriate test control signals or send the appropriate layer 3 messages and then, more than 1 second later, apply a reset pulse. Upon release of the reset pulse, the MS subsequently starts the test by issuing clock pulses when data are required or are ready. When testing uplink speech transcoding or DTX functions, the first falling clock edge shall request from the SS the first bit of the speech samples to be encoded, the transmission of which shall start at the next earliest possible interleaved block TDMA frame (as defined in GSM 05.02) after the release of the reset pulse. When testing downlink speech transcoding or DTX functions, the first falling clock edge shall output to the SS the first bit of the speech samples decoded from the first interleaved block TDMA frames, the reception of which is completed subsequently to the release of the reset pulse. The MS speech transcoders shall be reset by the end of the reset pulse, whenever it occurs, whilst the DAI is in one of the active states (Test of speech decoder / DTX functions (downlink), Test of speech encoder / DTX functions (uplink), Test of acoustic devices and A/D and D/A). ETSI TS 101 293 V5.1.0 (1998-10) 33 GSM 04.14 version 5.1.0 Release 1996 Reset Clock Data SS to MS Data MS to SS Undefined MSB MSB Undefined Figure 2: DAI Timing |
5674c1ed15972156beea0b9e811e204d | 101 293 | 11 SIM/ME test interface | |
5674c1ed15972156beea0b9e811e204d | 101 293 | 11.1 General | A special interface is required in order to perform the tests of the SIM/ME interface. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 11.2 Formal aspects | It shall be possible to connect the SIM simulator to the ME. If an adapter is to be used, it shall be provided by the manufacturer of the ME. When using the SIM simulator, the ME does not necessarily conform to all RF requirements. When the SIM simulator is connected the ME shall be able to correctly send and receive on a TCH and associated channels under ideal radio conditions (according to GC3 of Annex 1). |
5674c1ed15972156beea0b9e811e204d | 101 293 | 11.3 Hardware and logical aspects of the interface | The signals on this interface are specified in GSM 11.11. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 11.4 Mechanical characteristics of the interface | The interface of the SIM-simulator offers two connection types : i) a paddle which is inserted into the ME under test in place of an IC card SIM, and connects with wires to the measuring equipment. The dimensions of the paddle are shown in Figure 3. ii) a connector with leads of length 12cm, terminated directly at the contacting elements inside the ME under test. For ME which use the plug in SIM, or when the paddle cannot be inserted due to constraints imposed by the ME design, then the ME manufacturer shall, for the purpose of testing the SIM/ME interface only, provide the ME with the connector of type ii) and the leads attached directly to the contacting elements. This connector with the flying leads shall be delivered by the test house. ETSI TS 101 293 V5.1.0 (1998-10) 34 GSM 04.14 version 5.1.0 Release 1996 52.98 m m Figure 3: Dimensions of full size paddle ETSI TS 101 293 V5.1.0 (1998-10) 35 GSM 04.14 version 5.1.0 Release 1996 Annex A (informative): Change History Status of Technical Specification GSM 04.14 Date Version Remarks October 1998 5.1.0 change requests agreed by SMG#27: CR 04.14-A002 Changes to 04.14 Text: WinWord 7.0 Stylesheet: etsiw_70.dot Rapporteur: Andrew Howell (Motorola) ETSI TS 101 293 V5.1.0 (1998-10) 36 GSM 04.14 version 5.1.0 Release 1996 History Document history V5.0.0 July 1998 Publication V5.1.0 October 1998 Publication ISBN 2-7437-2651-2 Dépôt légal : Octobre 1998 |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 1 Scope | The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "SIM Application Toolkit". SIM Application Toolkit is a set of commands and procedures for use during the network operation phase of GSM, in addition to those defined in GSM 11.11 [14]. Specifying the interface is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in GSM 02.17 [3]. The present document defines: - the commands; - the application protocol; - the mandatory requirements on the SIM and ME for each procedure. Unless otherwise stated, references to GSM also apply to DCS 1800. The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the SIM or the ME are only specified where these reflect over the interface. The present document does not specify any of the security algorithms which may be used. The present document defines an enhancement for GSM Phase 2+ of the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification. |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1997 document, references to GSM documents are for Release 1997 versions (version 6.x.y). [1] GSM 01.02: "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". [2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [3] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber Identity Modules (SIM) Functional characteristics". [4] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man-Machine Interface (MMI) of the Mobile Station (MS)". [5] GSM 03.38: "Digital cellular telecommunications system (Phase 2+); Alphabets and language-specific information". ETSI TS 101 267 V6.3.0 (1999-05) 8 (GSM 11.14 version 6.3.0 Release 1997) [7] GSM 03.41: "Digital cellular telecommunications system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SMSCB)". [8] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [9] GSM 04.11: "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [10] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [11] GSM 04.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data (USSD) - Stage 3". [12] GSM 07.05: "Digital cellular telecommunications system (Phase 2+); Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". [13] GSM 09.91: "Digital cellular telecommunications system; Interworking aspects of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface between Phase 1 and Phase 2". [14] GSM 11.11 (ETS 100 608): "Digital cellular telecommunications system (Phase 2); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface" [15] CCITT Recommendation E.164: "Numbering plan for the ISDN era". [16] ISO/IEC 7816-3 (1989): "Identification cards - Integrated circuit(s) cards with contacts, Part 3: Electronic signals and transmission protocols". [17] ISO/IEC 7816-6 (1995): "Identification cards - Integrated circuit(s) cards with contacts, Part 6 Inter-industry data elements". [18] GSM 02.40: "Digital cellular telecommunications system (Phase 2); Procedures for call progress indications". [19] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Stations (MS) features". [20] GSM 11.11: "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". [21] GSM 11.12: "Digital cellular telecommunications system (Phase 2); Specification of the 3 Volt Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". [22] GSM 03.22 (ETS 300 930): "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode". [23] GSM 04.07 (ETS 300 939): "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 03.48: "Digital cellular telecommunications system (Phase 2+); Security Mechanisms for the SIM application toolkit ". ETSI TS 101 267 V6.3.0 (1999-05) 9 (GSM 11.14 version 6.3.0 Release 1997) |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 3 Definitions, abbreviations and symbols | |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. For further information and definitions refer to GSM 01.02 [1]. application: An application consists of a set of security mechanisms, files, data and protocols (excluding transmission protocols). application protocol: The set of procedures required by the application. card session: A link between the card and the external world starting with the ATR and ending with a subsequent reset or a deactivation of the card. data object: Information seen at the interface for which are defined a tag (identifier), a length and a value. Data objects can be either BER-TLV (objects that conform to the Basic Encoding Rules of ASN.1) or SIMPLE-TLV. In the present document, all BER-TLV data objects are "primitive": the value part consists only of SIMPLE-TLV data objects. padding: One or more bits appended to a message in order to cause the message to contain the required number of bits or bytes. proactive SIM: A SIM which is capable of issuing commands to the ME within the T=0 protocol. proactive SIM session: Sequence of related SIM application toolkit commands and responses. A proactive SIM session starts with the status response '91 xx' (proactive command pending) and ends with a status response of '90 00' (normal ending of command) after Terminal Response. SIM application session: The execution of a sequence of commands internal to the SIM that can result in the performance of one or several proactive SIM sessions. The SIM application session can be started by any event in the card session, and can execute for the duration of the card session. Processing of the SIM application session will not interfere with normal GSM operation. SIM Application Toolkit: A set of applications and related procedures which may be used during a GSM session. |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply, in addition to those listed in GSM 01.04 [2]: A3 Algorithm 3, authentication algorithm; used for authenticating the subscriber A5 Algorithm 5, cipher algorithm; used for enciphering/deciphering data A8 Algorithm 8, cipher key generator; used to generate Kc A38 A single algorithm performing the functions of A3 and A8 ADN Abbreviated Dialling Number APDU Application Protocol Data Unit BCD Binary Coded Decimal BDN Barred Dialling Number BER Basic Encoding Rules of ASN.1 CB Cell Broadcast CBMI Cell Broadcast Message Identifier CCP Capability/Configuration Parameter DCS Digital Cellular System DTMF Dual Tone Multiple Frequency EF Elementary File ETSI European Telecommunications Standards Institute etu elementary time unit FDN Fixed Dialling Number GSM Global System for Mobile communications ID IDentifier ETSI TS 101 267 V6.3.0 (1999-05) 10 (GSM 11.14 version 6.3.0 Release 1997) IEC International Electrotechnical Commission IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity ISO International Organization for Standardization Kc Cryptographic key; used by the cipher A5 Ki Subscriber authentication key; the cryptographic key used by the authentication algorithm, A3, and cipher key generator, A8 lgth The (specific) length of a data unit LND Last Number Dialled ME Mobile Equipment MMI Man Machine Interface MS Mobile Station NMR Network Measurement Results (see also GSM 04.08 [8]) NPI Numbering Plan Identifier RAND A RANDom challenge issued by the network RFU Reserved for Future Use SIM Subscriber Identity Module SMS Short Message Service SRES Signed RESponse calculated by a SIM SS Supplementary Service SSC Supplementary Service Control string SW1/SW2 Status Word 1 / Status Word 2 TLV Tag, length, value. TON Type Of Number TP Transfer layer Protocol TS Technical Specification UCS2 Universal two byte coded Character Set USSD Unstructured Supplementary Service Data |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 3.3 Symbols | '0' to '9' and 'A' to 'F' The sixteen hexadecimal digits. |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 4 Overview of SIM Application Toolkit | The SIM Application Toolkit provides mechanisms which allow applications, existing in the SIM, to interact and operate with any ME which supports the specific mechanism(s) required by the application. The following mechanisms have been defined. These mechanisms are dependent upon the commands and protocols relevant to SIM Application Toolkit in GSM 11.11 [20]. |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 4.1 Profile Download | Profile downloading provides a mechanism for the ME to tell the SIM what it is capable of. The ME knows what the SIM is capable of through the SIM Service Table and EFPHASE. |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 4.2 Proactive SIM | Proactive SIM gives a mechanism whereby the SIM can initiate actions to be taken by the ME. These actions include: - display text from the SIM to the ME; - send a short message; - set up a voice call to a number held by the SIM; - set up a data call to a number and bearer capabilities held by the SIM; - send a SS control or USSD string; - play tone in earpiece; - initiate a dialogue with the user; - SIM initialization request and notification of changes to EF(s); ETSI TS 101 267 V6.3.0 (1999-05) 11 (GSM 11.14 version 6.3.0 Release 1997) - provide local information from the ME to the SIM. For each command involved in the dialog with the user, a help information may be available, either for each item of a list of items proposed to the user, or with each command requesting a response from the user. If a proactive command involved in the dialog with the user indicates the availability of the help feature, the support of this feature is optional for the ME. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.