hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
4.3 Data download to SIM
|
Data downloading to the SIM uses the transport mechanisms of SMS point-to-point and Cell Broadcast. Transferral of information over the SIM-ME interface uses the ENVELOPE command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
4.4 Menu selection
|
A set of possible menu entries is supplied by the SIM in a proactive SIM command. The menu selection mechanism is used to transfer the SIM application menu item which has been selected by the user to the SIM. The menu selection mechanism may also be used for requesting help information on the items of the SIM application menu.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
4.5 Call control by SIM
|
When this service is activated by the SIM, all dialled digit strings, supplementary service control strings and USSD strings are first passed to the SIM before the ME sets up the call, the supplementary service operation or the USSD operation. The ME shall also pass to the SIM at the same time its current serving cell. The SIM has the ability to allow, bar or modify the call, the supplementary service operation or the USSD operation. The SIM also has the ability to replace a call request, a supplementary service operation or a USSD operation by another call request or supplementary service operation or USSD operation. For example, a call request can be replaced by a supplementary service operation or a USSD operation, and vice-versa.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
4.6 Security
|
Applications designed using the features in the present document may require methods to ensure data confidentiality, data integrity, and data sender validation, or any subset of these. Requirements for these mechanisms are defined in clause 15.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
5 Profile download
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
5.1 Procedure
|
The profile download instruction is sent by the ME to the SIM as part of the SIM initialization procedure. This procedure is specified in GSM 11.11 [14]. In this procedure, the ME reads EFPHASE. If EFPHASE indicates that the SIM requires the ME to perform the profile download procedure, then the ME shall, after having performed the CHV1 verification procedure and before selecting EFIMSI or EFLOCI, send the TERMINAL PROFILE command, as specified below, to the SIM. The profile sent by the ME shall state the facilities relevant to SIM Application Toolkit that are supported by the ME. This procedure is important, as it is by this that the SIM knows what the ME is capable of, and the SIM can then limit its instruction range accordingly. If no command is sent by the ME, the SIM shall assume that the ME does not support SIM Application Toolkit.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
5.2 Structure and coding of TERMINAL PROFILE
|
Direction: ME to SIM The command header is specified in GSM 11.11 [14]. ETSI TS 101 267 V6.3.0 (1999-05) 12 (GSM 11.14 version 6.3.0 Release 1997) Command parameters/data: Description Section M/O Length Profile - M lgth - Profile: Contents: The list of SIM Application Toolkit facilities that are supported by the ME. Coding: 1 bit is used to code each facility: bit = 1: facility supported by ME bit = 0: facility not supported by ME First byte (Download): b8 b7 b6 b5 b4 b3 b2 b1 Profile download SMS-PP data download Cell Broadcast data download Menu selection '9E XX' response code for SIM data download error RFU, bit = 0 Second byte (Other): b8 b7 b6 b5 b4 b3 b2 b1 Command result Call Control by SIM Cell identity included in Call Control by SIM RFU Handling of the alpha identifier according to subclause 9.1.3 UCS2 Entry supported UCS2 Display supported RFU, bit = 0 Third byte (Proactive SIM): b8 b7 b6 b5 b4 b3 b2 b1 Proactive SIM: DISPLAY TEXT Proactive SIM: GET INKEY Proactive SIM: GET INPUT Proactive SIM: MORE TIME Proactive SIM: PLAY TONE Proactive SIM: POLL INTERVAL Proactive SIM: POLLING OFF Proactive SIM: REFRESH Fourth byte (Proactive SIM): b8 b7 b6 b5 b4 b3 b2 b1 Proactive SIM: SELECT ITEM Proactive SIM: SEND SHORT MESSAGE Proactive SIM: SEND SS RFU Proactive SIM: SET UP CALL Proactive SIM: SET UP MENU Proactive SIM: PROVIDE LOCAL INFORMATION (MCC, MNC, LAC, Cell ID & IMEI) Proactive SIM: PROVIDE LOCAL INFORMATION (NMR) Subsequent bytes: b8 b7 b6 b5 b4 b3 b2 b1 RFU, bit = 0 RFU bits, and all bits of subsequent bytes, are reserved to indicate future facilities. A SIM supporting only the features of SIM Application Toolkit defined here shall not check the value of RFU bits. ETSI TS 101 267 V6.3.0 (1999-05) 13 (GSM 11.14 version 6.3.0 Release 1997) Response parameters/data: None.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6 Proactive SIM
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.1 Introduction
|
GSM 11.11 [14] defines that the ME communicates to the SIM using the T=0 protocol, which is specified in ISO/IEC 7816-3 [16]. The ME is always the "master" and initiates commands to the SIM, and therefore there is no mechanism for the SIM to initiate a communication with the ME. This limits the possibility of introducing new SIM features requiring the support of the ME, as the ME needs to know in advance what actions it should take. The proactive SIM service provides a mechanism which stays within the protocol of T=0, but adds a new status response word SW1. This status response has the same meaning as the normal ending ('90 00'), and can be used with most of the commands that allow the normal ending, but it also allows the SIM to say to the ME "I have some information to send to you". The ME then uses the FETCH function to find out what this information is. To avoid cross-phase compatibility problems, these functions shall only be used between a proactive SIM and an ME that supports the proactive SIM feature. The SIM can issue a variety of commands through this mechanism, given in alphabetical order: - DISPLAY TEXT, which displays text on screen (no more than 160 characters). A high priority is available, to replace anything else on screen. - GET INKEY, which sends text to the display and requests a single character response in return. It is intended to allow a dialogue between the SIM and the user, particularly for selecting an option from a menu. - GET INPUT, which sends text to the display and requests a response in return. It is intended to allow a dialogue between the SIM and the user. - MORE TIME, which does not request any action from the ME. The ME is required to respond with TERMINAL RESPONSE (OK) as normal - see below. The purpose of the MORE TIME command is to provide a mechanism for the SIM Application Toolkit task in the SIM to request more processing time. - PLAY TONE, which requests the ME to play a tone in its earpiece, ringer, or other appropriate loudspeaker. - POLL INTERVAL, which negotiates how often the ME sends STATUS commands to the SIM during idle mode. Polling is disabled with POLLING OFF. Use of STATUS for the proactive SIM is described in GSM 11.11 [14]. - PROVIDE LOCAL INFORMATION which requests the ME to pass local information to the SIM, for example the mobile country and network codes (MCC + MNC) of the network on which the user is registered. - REFRESH, which requests the ME to carry out a SIM initialization according to GSM 11.11 subclause 12.2.1, and/or advises the ME that the contents or structure of EFs on the SIM have been changed. The command also makes it possible to restart a card session by resetting the SIM. - SELECT ITEM, where the SIM supplies a list of items, and the user is expected to choose one. The ME presents the list in an implementation-dependent way. - SEND SHORT MESSAGE, which sends a short message or SMS-COMMAND to the network. - SEND SS, which sends a SS request to the network. - SET UP CALL, of which there are three types: - set up a call, but only if not currently busy on another call; - set up a call, putting all other calls (if any) on hold; - set up a call, disconnecting all other calls (if any); - SET UP MENU, where the SIM supplies a list of items to be incorporated into the ME's menu structure. ETSI TS 101 267 V6.3.0 (1999-05) 14 (GSM 11.14 version 6.3.0 Release 1997) The ME tells the SIM if the command was successful or not using the command result procedure defined in subclause 6.7. Responsibility for what happens after that (whether to repeat the command, try another one immediately, try again sometime later, or not to try again at all) lies with the SIM application. However, the SIM application needs to know why the command failed, so the ME provides the SIM with the result of the command. Results are grouped into three main types: - OK. - Temporary problem. These results are further broken down into types of temporary problems, and specific causes. Generally, they indicate to the SIM that it may be worth trying again. - Permanent problem. These results are again further broken down into types of permanent problems, and specific causes. Generally, they indicate to the SIM that it is not worth trying again during this GSM session. If the SIM issues an instruction to the ME to initiate a Mobile Originated transaction (e.g. SEND SMS), then unless explicitly stated elsewhere in the present document or in GSM 11.11 [14], the content supplied by the SIM for onward transmission by the ME shall not be altered by the ME.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.2 Identification of proactive SIMs and of ME support
|
A proactive SIM shall be identified by having the proactive SIM service activated in the SIM Service Table (see GSM 11.11 [14]). An ME that supports proactive SIMs shall be identified as such when it sends a TERMINAL PROFILE command during SIM initialization. The ME shall then send STATUS commands to the SIM at intervals determined by the poll interval procedure (see subclause 6.4.6). A proactive SIM shall not send any command requests (status bytes SW1 SW2 = '91 XX') to a mobile that does not support the proactive SIM feature. An ME that supports the proactive SIM feature shall not send proactive SIM related commands to a SIM that does not have the proactive SIM service activated.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.3 General procedure
|
For all of the procedures that can end in '90 00' (indicating normal ending to the command), and which cannot end in '9F XX' (response data available from SIM), a proactive SIM operating with an ME that supports proactive SIMs may instead use the status response '91 XX'. The response code '91 XX' shall indicate to the ME that the previous command has been successfully executed by the SIM in the same way as '90 00' (i.e. "OK"), but additionally it shall indicate response data which contains a command from the SIM for a particular ME procedure (defined in subclause 6.4). The value 'XX' indicates the length of the response data. The ME shall use the FETCH command to obtain this data. It is the responsibility of the SIM to remind the ME of a pending proactive command by applying the '91 XX' returncode until it is fetched by the ME. Note: The last value of 'XX' received in a '91 XX' returncode from the SIM should be used by the ME in a following FETCH command. It is recommended that the ME interprets a '90 00' following a '91 XX' without a corresponding FETCH as if no proactive command is available in the SIM and regard the proactive SIM session as being terminated. However, the SIM should be able to handle a FETCH command being sent in this case, e.g. by applying the appropriate error handling (cf. "Handling of unknown, unforeseen and erroneous messages"). GSM 11.11 [20] shows how the SIM can initiate a proactive command in each of the five cases of transmission protocol identified in GSM 11.11 [14]. Some commands require the SIM to indicate that it has response data for the ME (through SW1/SW2 = '9F XX'), and the ME gets this data using the GET RESPONSE command. When the ME has received a command from the SIM, it shall attempt to process the command immediately. ETSI TS 101 267 V6.3.0 (1999-05) 15 (GSM 11.14 version 6.3.0 Release 1997) - If the command has been successfully executed, the ME shall inform the SIM as soon as possible, using TERMINAL RESPONSE. - If the command was not successfully executed, the ME shall inform the SIM as soon as possible using TERMINAL RESPONSE with an error condition. Responsibility for re-trying lies with the SIM application. The SIM application can make a judgement whether to send the same command again, to send a different one, or not to try again, from the information given by the ME in TERMINAL RESPONSE. If the SIM application wishes the ME to try again, it shall issue a new (identical) command. Only one proactive command can be ongoing at any one time.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4 Proactive SIM commands and procedures
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.1 DISPLAY TEXT
|
This command instructs the ME to display a text message. It allows the SIM to define the priority of that message, and the text string format. Two types of priority are defined: - Display normal priority text on screen. - Display high priority text on screen. The text string can be in one of three formats: - packed format in SMS default alphabet - (see 12.15.2); - unpacked format in SMS default alphabet - (see 12.15.2); - UCS2 alphabet format - (see 12.15.3). A flag (see command qualifier, subclause 12.6) shall be set to inform the ME whether the availability of the screen for subsequent information display after its use for ‘Display Text’ should be either after a short delay (the duration of the delay being at the discretion of the ME manufacturer), or following a user MMI action. - If the user has indicated the need to end the proactive SIM application session, the ME shall send a TERMINAL RESPONSE with "Proactive SIM application session terminated by the user" result value. - If the user has indicated the need to go backwards in the proactive SIM application session, the ME shall send a TERMINAL RESPONSE with "Backward move in the proactive SIM session requested by the user" result value. - If a flag of the command qualifier (see subclause 12.6) indicates that the ME shall wait for the user to clear message and if the ME decides that no user response has been received, the ME shall send a TERMINAL RESPONSE with "No response from user" result value. - Otherwise, the ME shall send TERMINAL RESPONSE (Command performed successfully) at the expiration of the short delay, or following a user MMI action not described above. In each case the availability of the screen for the subsequent information display is defined in subclause 6.9. NOTE: For the case where the text is cleared after a short delay, the ME may also allow the user to clear the display via the MMI prior to this. The ME shall reject normal priority text commands if the screen is currently being used for more than its normal stand- by display. If the command is rejected, the ME informs the SIM using TERMINAL RESPONSE (ME currently unable to process command - screen busy). High priority text shall be displayed on the screen immediately, except if there is a conflict of priority level of alerting such as incoming calls or a low battery warning. In that situation, the resolution is left to the ME. If the command is rejected in spite of the high priority, the ME shall inform the SIM using TERMINAL RESPONSE (ME currently unable to process command - screen is busy). ETSI TS 101 267 V6.3.0 (1999-05) 16 (GSM 11.14 version 6.3.0 Release 1997) If help information is requested by the user, this command may be used to display help information on the screen. The help information should be sent as high priority text and with the option that it should be cleared after a short delay.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.2 GET INKEY
|
This command instructs the ME to display text, and to expect the user to enter a single character. Any response entered by the user shall be passed transparently by the ME to the SIM. The text can be in one of three formats: - packed format in SMS default alphabet - (see 12.15.2); - unpacked format in SMS default alphabet - (see 12.15.2); - UCS2 alphabet format - (see 12.15.3). The response can be from one of three character sets. This is specified by the SIM: - digits only (0-9, *, #, and +); - characters from the SMS default alphabet; - characters from the UCS2 alphabet. Upon receiving the command, the ME shall display the text. The ME shall allow the user to enter a single character in response. - If the user has indicated the need to go backwards in the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Backward move in the proactive SIM session requested by the user" result value. - If the user has indicated the need to end the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Proactive SIM session terminated by the user" result value. - If the ME decides that no user response has been received, the ME shall send a TERMINAL RESPONSE with "No response from user" result value. - If the SIM requests a digit only, the ME shall only allow the user to enter a character from the digits 0-9, *, # and +. When the user has entered a digit, the ME shall pass the entered digit transparently to the SIM, using TERMINAL RESPONSE. - If help information is available for the command and if the user has indicated the need to get help information, the ME shall send a TERMINAL RESPONSE with "help information required by the user" result value. - If the SIM requests a character from the SMS default alphabet, the ME shall allow the user to enter a character using characters from this alphabet. When the user has entered a character, the ME shall pass the entered character transparently to the SIM, using TERMINAL RESPONSE. NOTE: If the MMI of the ME requires more than one keypress in order to select a character, it is an implementation decision for the ME manufacturer how to indicate completion (e.g. timeout, pressing SEND, OK). It may be useful to echo the input character on the display. For digits only (0-9,*,# and +) and SMS default alphabet characters sets, the response shall be coded using the SMS default alphabet in unpacked format.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.3 GET INPUT
|
This command instructs the ME to display text, and that any response string entered by the user shall be passed transparently by the ME to the SIM. If if the SIM provides a default text, the ME shall display this default text, which the user may accept, reject or edit as the response string. The text can be in one of three formats: - packed format in SMS default alphabet - (see 12.15.2); - unpacked format in SMS default alphabet - (see 12.15.2); - UCS2 alphabet format - (see 12.15.3). ETSI TS 101 267 V6.3.0 (1999-05) 17 (GSM 11.14 version 6.3.0 Release 1997) The SIM indicates how many characters are expected for the response string, by giving a minimum and a maximum acceptable length. The SIM specifies three variables for the response string it is expecting from the user: - the response contains either digits only (0-9, *, # and +) or characters from the SMS default alphabet; - the response for digits only (0-9,*,# and +) or characters from SMS default alphabet is either in an unpacked format or in a packed format; - the ME may display the text string being entered by the user (the response), or the ME shall hide (i.e. not display) the actual text string. The combination of characters from the SMS default alphabet and hidden entry mode is not allowed. In hidden entry mode, only digits from the set “0-9”,“*” and “#” are allowed for the user input. “+” is not allowed for user input in this mode. If the SIM requests that the user input (text string) is to be hidden, it is permissible for the ME to indicate the entry of characters, so long as the characters themselves are not revealed. Upon receiving the command, the ME shall display the text. The ME shall allow the user to enter characters in response. - The ME MMI is responsible for managing the entry of the correct number of characters. - If the user has indicated the need to go backwards in the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Backward move in the proactive SIM session requested by the user" result value. - If the user has indicated the need to end the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Proactive SIM session terminated by the user" result value. - If the ME decides that no user response has been received, the ME shall send a TERMINAL RESPONSE with "No response from user" result value. - If the SIM requests digits only, the ME shall only allow the user to enter the digits 0-9, *, # and +. When the user presses SEND (or otherwise indicates completion), the ME shall pass the entered digit string transparently to the SIM, using TERMINAL RESPONSE. - If the SIM requests characters from the UCS2 alphabet or SMS default alphabet, the ME shall allow the user to enter a character string using characters from one of these alphabets. When the user presses SEND (or otherwise indicates completion), the ME shall pass the entered text string transparently to the SIM, using TERMINAL RESPONSE. - If help information is available for the command and if the user has indicated the need to get help information, the ME shall send a TERMINAL RESPONSE with ‘help information required by the user’ result value. If the SIM requests the user input to be in packed format, then the ME shall pack the text according to GSM 03.38 [5] before submitting it to the SIM.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.4 MORE TIME
|
This procedure is provided to allow the SIM Application Toolkit task in the SIM more time for processing, where the processing is so long that it is in danger of affecting normal GSM operation, and clock stop prevents processing to take place in the background. The ME shall take no extraordinary action when it receives this command, and all other operations shall be unaffected. The ME shall conclude the command by sending TERMINAL RESPONSE (OK) to the SIM, as soon as possible after receiving the MORE TIME command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.5 PLAY TONE
|
This command instructs the ME to play an audio tone. Upon receiving this command, the ME shall check if it is currently in, or in the process of setting up (SET-UP message sent to the network, see GSM 04.08 [8]), a speech call. ETSI TS 101 267 V6.3.0 (1999-05) 18 (GSM 11.14 version 6.3.0 Release 1997) - If the ME is in, or is setting up a speech call, it shall superimpose the tone on top of the downlink audio (if any), for the duration given in the command. The progress or current state of the call shall not be affected in any way. The ME shall send the TERMINAL RESPONSE (Command performed successfully) as soon as possible after the tone has been completed and, if an alpha identifier was included and displayed, the screen is available for subsequent information display. - If the ME is not in or setting up a speech call, it shall route the audio to the external ringer, or other appropriate audio device, and play the tone for the duration given in the command. The ME shall send the TERMINAL RESPONSE (Command performed successfully) as soon as possible after the tone has been completed and, if an alpha identifier was included and displayed, the screen is available for subsequent information display. - If the user has indicated the need to end the proactive SIM application session while the ME plays the tone, the ME shall stop playing the tone and shall send a TERMINAL RESPONSE with "Proactive SIM application session terminated by the user" result value. - If ME support for the specific tone requested is optional, and the ME does not support this particular tone, the ME shall inform the SIM using TERMINAL RESPONSE (Command beyond ME's capabilities). This proactive command contains no information on how a call is progressing; therefore the ME shall not generate any verbal indication or display any text or graphical indication about the normal meaning of this tone (e.g. display "called subscriber busy"). If the SIM wishes to convey a meaning in text to the user, it shall do this through the alpha identifier data object. If the ME is required to generate a supervisory tone due to the progress of the current call (e.g. the network sends the ME call control cause information) as defined in GSM 02.40 [18], then the call supervisory tone shall take precedence over the tone requested by the SIM.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.6 POLL INTERVAL
|
This procedure negotiates how often the ME shall send STATUS commands related to Proactive Polling (defined in GSM 11.11 [20]). The SIM indicates the poll interval it requests from then onwards, and the ME responds through TERMINAL RESPONSE with the maximum interval that it will use. If the ME does not support the poll interval requested by the SIM, then the ME shall respond with the closest interval to the one requested by the SIM, or, if the intervals the ME can offer are equidistant (higher and lower) from the SIM's request, the ME shall respond with the lower interval of the two. NOTE: Applications on the SIM should not request short time intervals for an extended period, as this will have an adverse effect on battery life.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.7 REFRESH
|
The purpose of this command is to enable the ME to be notified of the changes to the SIM configuration that have occurred as the result of a SIM application activity. It is up to the SIM application to ensure that this is done correctly. The command supports five different modes: - SIM Initialization. This mode tells the ME to carry out SIM initialization as it is defined in GSM 11.11 subclause 12.2.1 only, starting after the CHV1 verification procedure. The ME shall not reset the SIM electrically. - File Change Notification. This mode advises the ME of the identity of the EFs that have been changed (in structure and/or contents) in the SIM. This information can be used by the ME if there is an image of SIM EFs (e.g. the ADN file) in the ME's memory, to determine whether it needs to update this image. - SIM Initialization and File Change Notification. This is a combination of the first two modes above. - SIM Initialization and Full File Change Notification. This mode causes the ME to perform the SIM initialization procedure of the first mode above and advises the ME that several EFs have been changed (in structure or contents) in the SIM. If there is an image of SIM EFs in the ME's memory, the ME shall completely update this image. ETSI TS 101 267 V6.3.0 (1999-05) 19 (GSM 11.14 version 6.3.0 Release 1997) - SIM Reset. This mode causes the ME to run the GSM session termination procedure and to deactivate the SIM in accordance with GSM 11.11 [20]. Subsequently, the ME activates the SIM again and starts a new card session. In case of a 3 Volt technology ME, the ME shall restart the SIM with the same supply voltage as in the previous session, if the ME can ensure that the SIM has not been changed in between. Otherwise, the ME shall perform the supply voltage switching in accordance with GSM 11.12 [21]. The ME shall not send the TERMINAL RESPONSE; this is an exception from the normal procedure, where TERMINAL RESPONSE is sent after completion of the command. The SIM Application shall interpret a new activation of the contacts of the SIM as an implicit TERMINAL RESPONSE. The SIM Reset mode is used when a SIM application requires ATR or complete SIM initialization procedures to be performed. SIM Applications should take into account that early implementations of SIM Application Toolkit in some MEs may send a TERMINAL RESPONSE after performing the REFRESH command involving resetting the SIM electrically. If the ME performs the REFRESH command successfully for only those EFs indicated in the mode, the ME shall inform the SIM using TERMINAL RESPONSE (OK), after it has completed its refreshing. For REFRESH commands with mode other than “SIM Reset”, it is permissible for the ME, as part of its execution of the REFRESH command, to read EFs in addition to those notified by the SIM, or to perform a SIM initialisation, provided that the procedure executed wholly encompasses the mode requested by the SIM. The ME shall not electrically reset the SIM. If the ME does the refreshing successfully, it shall inform the SIM using TERMINAL RESPONSE (Refresh performed with additional EFs read), after the ME has completed its refreshing. It should be noted that reading additional EFs will lengthen the refresh procedure. If the ME receives a REFRESH command while in a state where execution of the command would be unacceptable, upsetting the current user operation (e.g. notification during a call that the IMSI has changed), the ME shall inform the SIM using TERMINAL RESPONSE (ME currently unable to process command - currently busy on call) or TERMINAL RESPONSE (ME currently unable to process command - screen is busy) as appropriate. NOTE 1: Many MEs copy an image of the SIM's memory to the ME at initialization to speed up access to these fields during a GSM session. One of the purposes of this coding of the REFRESH command is to enable MEs to change such an image efficiently. If, on receipt of the REFRESH command, the ME replies that it is busy (e.g. in call or navigating menus), the toolkit application may shorten the polling interval utilising the POLL INTERVAL command in order to resend the REFRESH command more frequently. It is recommended for the ME to minimise the use of sending temporary problem TERMINAL RESPONSE, as during the period between the SIM issuing a REFRESH command and the ME performing the refresh procedure, there may be inconsistencies between data held in the ME and in the SIM. However, responsibility for retrying of all pro-active commands lies with the SIM Application.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.8 SET UP MENU
|
The SIM shall supply a set of menu items, which shall be integrated with the menu system (or other MMI facility) in order to give the user the opportunity to choose one of these menu items at his own discretion. Each item comprises a short identifier (used to indicate the selection) and a text string. The SIM shall include an alpha identifier which acts as a title for the list of menu items. The SIM may include an items next action indicator data object located at the end of the list of items. The inclusion of the items next action indicator is to allow the ME to indicate to the user the consequences of performing the selection of an item. NOTE: The maximum amount of data sent in one proactive SIM command is 256 bytes. It is therefore unavoidable that there is trade-off between the number of items and the length of the descriptive text (the alpha identifier of the SET-UP MENU command and the text strings of the items), e.g. for an average length of 10 bytes per text string the maximum amount of items is 18. The list of menu items shall then be part of the menu system of the ME and the user is allowed to select an item from this list. The presentation style is left as an implementation decision to the ME manufacturer. The menu provided by the SIM in the last SET UP MENU command shall no longer be part of the menu system of the ME if the ME is powered off or the SIM is removed or electrically reset, Any subsequent SET-UP MENU command replaces the current list of menu items supplied in the previous SET-UP MENU command. The SET-UP MENU command can also be used to remove a menu from the menu system in the ME; see subclause 6.6.7. ETSI TS 101 267 V6.3.0 (1999-05) 20 (GSM 11.14 version 6.3.0 Release 1997) When the ME has successfully integrated or removed the list of menu items, it shall send TERMINAL RESPONSE (OK) to the SIM. When the ME is not able to successfully integrate or remove the list of menu items, it shall sent TERMINAL RESPONSE (Command beyond ME's capabilities). When the user has selected one of the menu items of this menu item list, then the ME shall use the Menu Selection mechanism to transfer the identifier of the selected menu item to the SIM. If help is available for the command and if the user has indicated the need to get help information on one of the menu items, the ME shall use the Menu Selection mechanism to inform the SIM about this help request.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.9 SELECT ITEM
|
The SIM shall supply a set of items from which the user may choose one. Each item comprises a short identifier (used to indicate the selection) and a text string. Optionally the SIM may include an alpha identifier. The alpha identifier is intended to act as a title for the list of items. The SIM may include an items next action indicator data object located at the end of the list of items. The inclusion of the items next action indicator is to allow the ME to indicate to the user the consequences of performing the selection of an item. The alpha identifier included by the SIM shall be used by the ME as the title for the list of items. NOTE: The maximum amount of data sent in one proactive SIM command is 256 bytes. It is therefore unavoidable that there is trade-off between the number of items and the length of the descriptive text (the alpha identifier of the SELECT ITEM command and the text strings of the items), e.g. for an average length of 10 bytes per text string the maximum amount of items is 18. The ME shall present the list of text strings to the user, and allow the user to select an item from this list. The presentation style is left as an implementation decision to the ME manufacturer. The menu provided by the SIM in the last SET UP MENU command shall no longer be part of the menu system of the ME if the ME is powered off or the SIM is removed or electrically reset. The SIM may supply with the list, if applicable, indication of the default item, e.g. the previously selected item. When the user has selected an item, the ME shall send TERMINAL RESPONSE (OK) to the SIM with the identifier of the item chosen. - If the user has indicated the need to end the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Proactive SIM session terminated by the user" result value. - If the user has indicated the need to go backwards in the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Backward move in the proactive SIM session requested by the user" result value. - If the ME decides that no user response has been received, the ME shall send a TERMINAL RESPONSE with "No response from user" result value. - If help information is available for the command and if the user has indicated the need to get help information, the ME shall send a TERMINAL RESPONSE with "help information required by the user" result value to the SIM with the identifier of the item for which the user is requiring help information.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.10 SEND SHORT MESSAGE
|
Two types are defined: - A short message to be sent to the network in an SMS-SUBMIT message, or an SMS-COMMAND message, where the user data can be passed transparently; - A short message to be sent to the network in an SMS-SUBMIT message where the text needs to be packed by the ME. ETSI TS 101 267 V6.3.0 (1999-05) 21 (GSM 11.14 version 6.3.0 Release 1997) Where the text has been packed, the text string provided by the SIM shall not be longer than 160 characters. It shall use the SMS default 7-bit coded alphabet, packed into 8-bit octets, in accordance with GSM 03.38 [5]. The data coding indication contained in the Data Coding Scheme byte shall be "default alphabet". The text length (which is part of the SMS TPDU) given by the SIM shall state the number of 7-bit characters in the text string. The command details shall indicate "packing not required". 8-bit data Short Messages may be sent by the SIM. The command shall indicate packing not required. The data coding indication contained in the Data Coding Scheme byte shall be "8 bit". The string shall not be longer than 140 bytes, and the length (in SMS TPDU) shall state the number of bytes in the string. If UCS2 is supported by the ME, 16-bit data Short Messages may be sent by the SIM. The text string provided by the SIM shall not be longer than 70 characters. It shall use the 16-bit UCS2 alphabet format, in accordance with GSM 03.38 [5]. The text length (which is part of the SMS TPDU) given by the SIM shall state the number of 16-bit characters in the text string. The command details shall indicate "packing not required". SMS commands may be sent by the SIM. These shall count as packed text message. The SMS TPDU from the SIM shall indicate SMS-COMMAND. The command details shall indicate "packing not required". Where packing by the ME is required, the text string provided by the SIM shall not be longer than 160 characters. It shall use the SMS default 7-bit coded alphabet as defined in GSM 03.38 [5] with bit 8 set to 0. The text length given by the SIM shall state the number of characters in the text string. The ME shall pack the text string and modify the Data Coding Scheme byte to "default alphabet" in accordance with GSM 03.38 [5] before submitting the message to the network. Optionally, the SIM may include in this command an alpha identifier. The use of this alpha identifier by the ME is described below : - If the alpha identifier is provided by the SIM and is not a null data object, the ME shall use it to inform the user. This is also an indication that the ME should not give any other information to the user on the fact that the ME is sending a short message. - If the alpha identifier is provided by the SIM and is a null data object (i.e. length = '00' and no value part), this is an indication that the ME should not give any information to the user on the fact that the ME is sending a short message. - If the alpha identifier is not provided by the SIM, the ME may give information to the user concerning what is happening. If the ME is capable of SMS-MO, then it shall send the data as a Short Message TPDU to the destination address. The ME shall give the result to the SIM using TERMINAL RESPONSE (indicating successful or unsuccessful transmission of the Short Message) after receiving an SMS RP-ACK or RP-Error from the network. If an alpha identifier was provided by the SIM, the ME should not give any information to the user at the reception of SMS RP-ACK or RP-Error. If the Short Message TPDU is unsuccessfully received by the network (e.g. the reception of a CP-ERROR), the ME shall inform the SIM using TERMINAL RESPONSE (network currently unable to process command). If a null alpha identifier was provided by the SIM, the ME should not give any information to the user at the unsuccessful network reception.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.11 SEND SS
|
Even if the Fixed Dialling Number service is enabled, the supplementary service control string included in the SEND SS proactive command shall not be checked against those of the FDN list. Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive: - If the command is rejected because the ME is busy on an SS transaction, the ME informs the SIM using TERMINAL RESPONSE (ME unable to process command - currently busy on SS transaction); - If the command is rejected because the ME does not support that Supplementary Service, the ME informs the SIM using TERMINAL RESPONSE (Command beyond ME's capabilities). If the ME is able to send the SS request, the ME shall: - Send the SS request immediately, without need to alert the user first. ETSI TS 101 267 V6.3.0 (1999-05) 22 (GSM 11.14 version 6.3.0 Release 1997) - Optionally, the SIM may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below: - If the alpha identifier is provided by the SIM and is not a null data object, the ME shall use it to inform the user. This is also an indication that the ME should not give any other information to the user on the fact that the ME is sending a SS request. - If the alpha identifier is provided by the SIM and is a null data object (i.e. length = '00' and no value part), this is an indication that the ME should not give any information to the user on the fact that the ME is sending an SS request. - If the alpha identifier is not provided by the SIM, the ME may give information to the user concerning what is happening. - Once an SS Return Result message not containing an error has been received from the network, the ME shall inform the SIM that the command has been successfully executed, using TERMINAL RESPONSE. This command shall include the contents of SS Return Result as additional data. If a null alpha identifier was provided by the SIM, the ME should not give any information to the user at the reception of an SS Return Result message; - If the command is rejected because the network cannot support or is not allowing the Supplementary Service request, the ME informs the SIM using TERMINAL RESPONSE (SS Return Result error code). If a null alpha identifier was provided by the SIM, the ME should not give any information to the user at the reception of a SS Return Result message; - If the SS request is unsuccessfully received by the network, the ME shall inform the SIM using TERMINAL RESPONSE (network currently unable to process command), and not retry to send the request. If a null alpha identifier was provided by the SIM, the ME should not give any information to the user at the reception of a SS Return Result message. If the ME supports the Last Number Dialled service, the ME shall not store in EFLND the supplementary service control string sent by the SIM in this command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.12 Not used
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.13 SET UP CALL
|
Three types are defined: - set up a call, but only if not currently busy on another call; - set up a call, putting all other calls (if any) on hold; - set up a call, disconnecting all other calls (if any) first. For each of these types, the SIM may request the use of an automatic redial mechanism according to the GSM 02.07 [19]. The SIM may also request an optional maximum duration for the redial mechanism. The ME shall attempt at least one call set-up. In addition to the called party number, the command may contain capability configuration parameters (giving the bearer capability to request for the call) and the called party subaddress. The ME shall use these in its call set-up request to the network. The command may also include DTMF digits, which the ME shall send to the network after the call has connected. It is possible for the SIM to request the ME to set up an emergency call by supplying the number "112" as called party number. If the SIM supplies a number stored in EFECC, this shall not result in an emergency call. If the Fixed Dialling Number service is enabled, the number included in the SET UP CALL proactive command shall not be checked against those of the FDN list. Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive: - If the command is rejected because the ME is busy on another call, the ME informs the SIM using TERMINAL RESPONSE (ME unable to process command - currently busy on call); - If the command is rejected because the ME is busy on a SS transaction, the ME informs the SIM using TERMINAL RESPONSE (ME unable to process command - currently busy on SS transaction); ETSI TS 101 267 V6.3.0 (1999-05) 23 (GSM 11.14 version 6.3.0 Release 1997) - If the command is rejected because the ME cannot support Call Hold, or because the ME does not support the capability configuration parameters requested by the SIM, the ME informs the SIM using TERMINAL RESPONSE (Command beyond ME's capabilities); - If the command is rejected because the network cannot support or is not allowing Call Hold of a multi party call, the ME informs the SIM using TERMINAL RESPONSE (SS Return Result error code); - If the command is rejected because the network cannot support or is not allowing Call Hold of a single call, the ME informs the SIM using TERMINAL RESPONSE (Network currently unable to process command). If the ME is able to set up the call on the serving network, the ME shall: - Alert the user (as for an incoming call). - Optionally, the SIM may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below: - If the alpha identifier is provided by the SIM, the ME shall use it to inform the user, at the latest when the user is alerted. The ME may also use it to inform the user during the call set-up. - If the user accepts the call, the ME shall then set up a call to the destination address given in the response data, with the relevant capability configuration parameters and called party subaddress (if provided by the SIM); - If the user does not accept the call, or rejects the call, then the ME informs the SIM using TERMINAL RESPONSE (user did not accept call set-up request). The operation is aborted; - If the user has indicated the need to end the proactive SIM session, the ME shall send a TERMINAL RESPONSE with "Proactive SIM session terminated by the user" result value; - Optionally, during call set-up, the ME can give some audible or display indication concerning what is happening; - Once a CONNECT message has been received from the network (defined in GSM 04.08), the ME shall inform the SIM that the command has been successfully executed, using TERMINAL RESPONSE. Operation of the call then proceeds as normal. If the first call set-up attempt is unsuccessful: - If the SIM did not request redial then the ME shall inform the SIM using TERMINAL RESPONSE (network currently unable to process command), and not redial to set-up the call; - If the SIM requested redial, then the ME may automatically redial the call (depending on its capability/configuration). In this case, the ME shall not send a command result to the SIM concerning the first or any subsequent failed set-up attempts. If the call set-up has not been successful, and the ME is not going to perform any more redials, or the time elapsed since the first call set-up attempt has exceeded the duration requested by the SIM, then the ME shall inform the SIM using TERMINAL RESPONSE (network currently unable to process command), and the redial mechanism shall be terminated; - If the user stops the call set-up attempt or the redial mechanism before a result is received from the network, the ME informs the SIM using TERMINAL RESPONSE (user cleared down call before connection or network release). If the ME supports the Last Number Dialled service, the ME shall not store in EFLND the call set-up details (called party number and associated parameters) sent by the SIM in this command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.14 POLLING OFF
|
This command disables the Proactive Polling (defined in GSM 11.11 [20]). SIM Presence Detection (defined in GSM 11.11 [20]) is not affected by this command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.4.15 PROVIDE LOCAL INFORMATION
|
This command requests the ME to send current local information to the SIM. At present, this information is restricted to: ETSI TS 101 267 V6.3.0 (1999-05) 24 (GSM 11.14 version 6.3.0 Release 1997) - location information: the mobile country code (MCC), mobile network code (MNC), location area code (LAC) and cell ID of the current serving cell; - the IMEI of the ME; - and the Network Measurement Results and the BCCH channel list. The ME shall return the requested local information within a TERMINAL RESPONSE. Where location information has been requested and no service is currently available, then the ME shall return TERMINAL RESPONSE (ME currently unable to process command - no service). If the NMR are requested and a call is in progress, the value of all the returned parameters provided by the ME in the response to the command will be valid. The NMR returned when a call is in progress from MEs supporting multiband operation, shall be according to the value of the multiband reporting parameter as defined in GSM 04.08 [8]. If a call is not in progress (i.e. ME is in idle mode) some of the returned parameters (e.g. RXQUAL) may be invalid. In idle mode, MEs supporting multiband operation shall ignore the value of the multiband reporting parameter and the NMR returned shall be as defined in GSM 04.08 [8] when the multiband reporting parameter equals zero. NOTE 1: When in idle mode, the only information element on which it is possible to rely on is the RXLEV-FULL- SERVING-CELL, which contains the value of the received signal strength on the BCCH of the current serving cell. NOTE 2: Network Measurement Results are defined in GSM 04.08 [8] as Measurement Results.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.