hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.5 Common elements in proactive SIM commands
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.5.1 Command number
|
The command number is to cater for the future possibility of multiple ongoing commands (i.e. when the SIM issues further commands before receiving the response to the ongoing command). The implications of such multiple ongoing commands have not been elaborated at this stage of the toolkit specification. Each command issued by a proactive SIM during a GSM session shall have its own command number. Command numbers may take any hexadecimal value between '01' and 'FE'. The command number is held in the command details data object. The SIM is responsible for assigning the command number. The ME shall keep a record of the status of each command and its command number, until the ME gives the result of the command to the SIM, using TERMINAL RESPONSE. After this, the ME may erase all internal records concerning this command. The command number is then free for allocation by the SIM to a new command. When the MS is powered off and on, the details of any ongoing command shall be reset. The ME shall not be expected to know the status of commands issued in a previous GSM session.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.5.2 Device identities
|
This data object gives the devices which are the source and destination for the instruction. Only certain combinations of source and destination devices are allowed for each proactive command. These are given in clause 14 of the present document.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.5.3 Alpha identifier
|
Many of the commands include an alpha identifier data object. This is intended to be a short one or two word identifier which shall be displayed on screen by the ME at the same time as the SIM command is performed. If longer text statements are required, which must be displayed on the screen, the SIM shall send a separate display command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6 Structure of proactive SIM commands
|
The general structure of proactive SIM commands using TLV objects is described in annex D. ETSI TS 101 267 V6.3.0 (1999-05) 25 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.1 DISPLAY TEXT
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Text string 12.15 M Y C
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.2 GET INKEY
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Text string 12.15 M Y C - Text string Contents: text for the ME to display in conjunction with asking the user to respond.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.3 GET INPUT
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D+E) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Text string 12.15 M Y C Response length 12.11 M Y D Default Text 12.23 O N E - Text string Contents: text for the ME to display in conjunction with asking the user to respond. - Response length Contents: the minimum and maximum acceptable lengths for the response from the user. - Default Text Contents: text for the ME to display, corresponds to a default text string offered by the SIM. ETSI TS 101 267 V6.3.0 (1999-05) 26 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.4 MORE TIME
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.5 PLAY TONE
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D+E) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Alpha identifier 12.2 O N C Tone 12.16 O N D Duration 12.8 O N E - Tone Contents: the standard supervisory tone or proprietary ME tone that the ME shall generate, either on its own or on top of the downlink audio path. If no tone is specified, then the ME shall default to "general beep". NOTE: Some supervisory tones are optional for mobile equipment (see GSM 02.40 [18]). - Duration Contents: the length of time for which the ME shall generate the tone, if the tone is continuous or repeatable. For single tones, the value of this data object shall be ignored by the ME. If no duration is specified, the ME shall default to a duration determined by the ME manufacturer.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.6 POLL INTERVAL
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Duration 12.8 M Y C - Duration Contents: the maximum interval between two STATUS commands related to Proactive Polling.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.7 SET-UP MENU
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D1+D2+...Dn+E) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Alpha identifier 12.2 M Y C Item data object for item 1 12.9 M Y D1 Item data object for item 2 12.9 O N D2 ...... 12.9 O N Dx Item data object for last item in list 12.9 O N Dn Items Next Action Indicator 12.24 O N E ETSI TS 101 267 V6.3.0 (1999-05) 27 (GSM 11.14 version 6.3.0 Release 1997) The SET-UP MENU command BER-TLV data object shall contain Item SIMPLE-TLV data objects. Each Item data object contains an item in the list, for the user to choose. The length of each Item data object may be different. Within a list, each Item shall have a unique item identifier. If the "Item data object for item 1" is a null data object (i.e. length = '00' and no value part), this is an indication to the ME to remove the existing menu from the menu system in the ME. The SIM shall provide an Items Next Action Indicator data object with the comprehension required flag set to ‘0’.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.8 SELECT ITEM
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D1+D2+...Dn+E+F) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Alpha identifier 12.2 O N C Item data object for item 1 12.9 M Y D1 Item data object for item 2 12.9 O N D2 ...... 12.9 O N Dx Item data object for last item in list 12.9 O N Dn Items Next Action Indicator 12.24 O N E Item Identifier 12.10 O N F The SELECT ITEM command BER-TLV data object shall contain Item SIMPLE-TLV data objects. Each Item data object contains an item in the list, for the user to choose. The length of each Item data object may be different. Within a list, each Item shall have a unique item identifier. The SELECT ITEM command BER-TLV data object may contain a single Item Identifier data object as an indication of the default item. The Comprehension Required flag in the Item Identifier data object shall be set to 0, indicating that it is not mandatory for the ME to support indication of the default item. The SIM shall provide an Items Next Action Indicator data object with a comprehension required flag set to '0'.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.9 SEND SHORT MESSAGE
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D+E) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Alpha identifier 12.2 O N C Address 12.1 O N D SMS TPDU (SMS-SUBMIT or SMS- COMMAND) 12.13 M Y E The address data object holds the RP_Destination_Address of the Service Centre. If no RP_Destination_Address is transferred, then the ME shall insert the default Service Centre address. ETSI TS 101 267 V6.3.0 (1999-05) 28 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.10 SEND SS
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Alpha identifier 12.2 O N C SS string 12.14 M Y D
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.11 Not used
|
6.6.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
11 Not used
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.12 SET UP CALL
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C+D+E+F+G) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B Alpha identifier 12.2 O N C Address 12.1 M Y D Capability configuration parameters 12.4 O N E Called party subaddress 12.3 O N F Duration 12.8 O N G If the capability configuration parameters are not present, the ME shall assume the call is a speech call. If the called party subaddress is not present, the ME shall not provide a called party subaddress to the network. If the duration is not present, the SIM imposes no restrictions on the ME of the maximum duration of redials.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.13 REFRESH
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B+C) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B File List 12.18 M/O N C For the refresh modes “File Change Notification“ and “SIM Initialization and File Change Notification”, the SIM shall supply a File List data object, indicating which EFs need to be refreshed. For other modes, inclusion of a File List is optional, and the ME shall ignore it.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.14 POLLING OFF
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B) - M Y 1 or 2 Command details 12.6 M Y A Device identities 12.7 M Y B ETSI TS 101 267 V6.3.0 (1999-05) 29 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.6.15 PROVIDE LOCAL INFORMATION
|
Description Section M/O Min Length Proactive SIM command Tag 13.2 M Y 1 Length (A+B) - M Y 1 or 2 Command details 12.6 M Y A Device Identities 12.7 M Y B
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.7 Command results
|
Once the ME has made its attempt to execute a proactive command from the SIM, the ME shall inform the SIM of the success or otherwise of that command, by using TERMINAL RESPONSE. This message gives the command details, including the number of the command (see subclause 6.5.1), a general result, and sometimes more specific information. Three overall categories of results are defined: - Command performed successfully. This is returned by the ME for every successful command; - Temporary problem with executing command. This is further defined below, but generally these indicate to the SIM that it is worth trying again later; - Permanent problem with executing command. These are further defined below, but generally indicate that the same command will end in the same result if repeated during the same GSM session. Successful commands are further defined as: - Command performed successfully. There were no problems; - Command performed with partial comprehension. Here the ME receives a command with one or more SIMPLE- TLV data objects that are unrecognized or unexpected, all of which do not have their "comprehension required" flag set (subclause 13.3), but the parent BER-TLV data object still has the minimum set of SIMPLE-TLV data objects required to perform the command; - Command performed, with missing information. The ME received at least the minimum set of component parts, but did not receive all of the parts that it believed mandatory for the SIM to send. - Command performed, but modified by call control. This is sent by the ME to indicate that call control modified the type of request indicated in the proactive command, and that the action requested by call control was performed successfully. Temporary problems are further defined as: - ME is currently unable to process the command. Specific causes for this are: - the screen is busy; - ME currently busy on a call; - ME currently busy on SS transaction; - no service is currently available; - access control class barred on serving network; - no radio resource currently available; - not in speech call. If none of these can be made to apply, a "no cause can be given" value can be used. - Network is currently unable to process the command. Specific cause values are the cause values given by the network, as defined in GSM 04.08 [8]. - The user did not accept the call set-up request. This is where the ME alerts the user before setting up a call, and the user either rejected or did not accept the "call". - The user cleared down the call, before the call connected (CONNECT received from network, as defined in GSM 04.08 [8]) or before the network released the call. ETSI TS 101 267 V6.3.0 (1999-05) 30 (GSM 11.14 version 6.3.0 Release 1997) - Interaction with call control by SIM, temporary problem. This is sent by the ME to indicate that call control modified the type of request indicated in the proactive command, and that the action requested by call control encounters a temporary problem. Permanent problems are further defined as: - Command is beyond ME's capabilities. This is sent by the ME when it understands what the SIM is asking it to do, but does not have the capability to do it, e.g. ME which only supports SMS asked to set up a call. - Command type not understood by ME. This is sent by the ME when the SIM sends a command with the Type of Command byte set to a value the ME does not know. This is to allow future expansion of commands. - Command data not understood by ME. This is sent by the ME when the command type is understood by the ME, but the related data object(s) are not, e.g. reserved values have been included in a data object, or one or more unknown SIMPLE-TLV data objects have a "comprehension required" tag. - SS Return Error. This is given to the SIM when the network returns a SS error in response to a previous SS command. Specific cause values are the same as given by the network in the Return Error message. - SMS RP-ERROR. This is given to the SIM when the network returns an error in response to the ME trying to send a short message. Specific cause values are the same as the cause value of RP-Cause in an RP-ERROR message. - Error, required values are missing. This is given when the command type is understood by the ME, but it does not receive the minimum set of SIMPLE-TLV data objects that it requires to perform the command. These components are shown by the "Min" column in the command structure definitions. - Interaction with call control by SIM or MO short message control by SIM, permanent problem. This is sent by the ME to indicate that: - call control by SIM does not allow the action corresponding to the proactive command or - call control by SIM has modified the type of request indicated in the proactive command and that the action requested by call control encounters a permanent problem. Specific cause values for this are: - action not allowed; - the type of request has changed; If none of these can be made to apply, a "no cause can be given" value can be used.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.8 Structure of TERMINAL RESPONSE
|
Direction: ME to SIM The command header is specified in GSM 11.11 [14]. Length (A+B+C+D+E+F+G+H+I) is indicated by P3 of the header. Command parameters/data: ETSI TS 101 267 V6.3.0 (1999-05) 31 (GSM 11.14 version 6.3.0 Release 1997) Description Section M/O Min Length Command details 12.6 M Y A Device identities 12.7 M N B Result 12.12 M Y C Duration (only required in response to a POLL INTERVAL proactive command) 12.8 M/O Y/N D Text string (only required in response to a GET INKEY or GET INPUT proactive command) 12.15 M/O Y/N E Item identifier (only required in response to SELECT ITEM proactive command) 12.10 M/O Y/N F Local information (only required in response to PROVIDE LOCAL INFORMATION proactive command) 12.19 /12.20 /12.22 and 12.29 M/O Y/N G Call control requested action (only required if call control by SIM has modified a proactive command SET UP CALL or SEND SS in another type of request) 12.30 M/O Y/N H Result data object 2 (only required if call control by SIM has modified a proactive command SET UP CALL or SEND SS in another type of request) 12.12 M/O Y/N I - Command details: this data object shall be identical to the command details data object (including the comprehension required flag) given by the SIM in the proactive command to which the ME is giving the result. If the ME has not received a valid Command number, all Command Details object values shall be set to '00' and the Result shall indicate an error. If the failure is caused by a problem on the transmission layer, the ME shall respond with "temporary problem" ("ME currently not able to process command"). If not, the ME shall respond with "permanent problem" (either "command not understood by ME" or "Error required values are missing"). The SIM shall interpret a Terminal Response with a command number '00' as belonging to the last proactive command having been sent to the ME. - Device identities: the ME shall set the device identities to: Source: ME Destination: SIM - Result: This data object holds the result of the proactive SIM command. - Duration: When the ME issues a successful TERMINAL RESPONSE for a POLL INTERVAL command, it shall state the polling interval it will be using in the Duration data object. All other types of TERMINAL RESPONSE do not need to include Duration. If one is included by the ME, the SIM shall ignore it. - Text string: When the ME issues a successful TERMINAL RESPONSE ('0X' result value - refer to subclause 12.12) for a GET INKEY or GET INPUT command, it shall supply the single character or the character string entered by the user in the Text string data object, no matter what type of string was entered. All other types of TERMINAL RESPONSE do not need to include Text string. If one is included by the ME, the SIM shall ignore it. - Item identifier: When the ME issues a successful TERMINAL RESPONSE ('0X' result value - refer to subclause 12.12) for a SELECT ITEM command, it shall supply the identifier of the item selected by the user in the Item identifier data object. If the ME issues a TERMINAL RESPONSE with result "Help information required by the user" for a SELECT ITEM command, it shall supply the identifier of the item for which the user is requiring help information. All other types of TERMINAL RESPONSE do not need to include Item identifier. If one is included by the ME, the SIM shall ignore it. - Local information. When the ME issues a successful TERMINAL RESPONSE for a PROVIDE LOCAL INFORMATION command, it shall supply the requested local information. ETSI TS 101 267 V6.3.0 (1999-05) 32 (GSM 11.14 version 6.3.0 Release 1997) - Where the SIM has requested location information, TERMINAL RESPONSE shall contain the location information data object. All other types of TERMINAL RESPONSE do not need to include location information. If one is included by the ME, the SIM shall ignore it. - Where the SIM has requested the IMEI, TERMINAL RESPONSE shall contain the IMEI data object. All other types of TERMINAL RESPONSE do not need to include IMEI information. If one is included by the ME, the SIM shall ignore it. - Where the SIM has requested the Network Measurement Results the TERMINAL RESPONSE shall contain the NMR data object and the BCCH channel list data object. All other types of TERMINAL RESPONSE do not need to include the NMR information or the BCCH channel list. If one is included by the ME, the SIM shall ignore it. - Call control requested action. When the ME issues a TERMINAL RESPONSE for a proactive command SET UP CALL orSEND SS which has been modified by call control by SIM in another type of request, it shall supply the response data given in response to the ENVELOPE (CALL CONTROL). - Result data object 2. When the ME issues a TERMINAL RESPONSE for a proactive command SET UP CALL or SEND SS which has been modified by call control by SIM in another type of request, it shall supply the Result data object it would have supplied for the proactive command equivalent to the action requested by call control, and given in the Call control request data element. Under no circumstances shall the SIM wait indefinitely for a TERMINAL RESPONSE. Any future additional SIMPLE-TLV objects shall be included as Min = N and comprehension not required. This will ensure that any proactive command will end in a predictable way. Response parameters/data: None.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.9 Proactive SIM session and ME display interaction
|
During a proactive session the ME display shall be refreshed by any display data contained in the first and each subsequent proactive command. The refresh shall occur once the ME has retrieved the proactive command using the Fetch instruction, following the proactive command pending status response. If no proactive command is pending (status response of ‘90 00’ following the Terminal Response), then the session releases the display back into ME control. If this session was terminated in a backwards move, and the session was initiated from an Envelope command containing a Menu Selection, it is recommended that the display returns to the Setup Menu.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10 Handling of unknown, unforeseen and erroneous messages
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.1 General
|
The procedures described in this subclause apply to the BER-TLV and SIMPLE-TLV data objects described in the present document. The purpose of this subclause is to allow greater flexibility in future versions of the present document, and a greater predictability across different versions of this standard. The procedures described here specify how the ME and SIM shall behave when they receive a proactive command or response that is not fully compliant with the standards by which it was designed. A response will be made to the SIM by means of the "general result" field of the "result" If the ME sends a FETCH or TERMINAL RESPONSE to the SIM that contains values that the SIM does not understand, then the SIM shall issue the appropriate SW1 / SW2 error response. The current proactive transaction shall be considered complete and neither the ME or the SIM shall take no further action with regard to it. In this case, unless the "General result" is "command performed..." then the SIM shall assume that the command was not carried out and that a permanent error exists with regard to that particular proactive command. If the command was performed, but the "additional information on result" field was not understood, then the SIM may attempt the command again at a later stage in the current GSM session. ETSI TS 101 267 V6.3.0 (1999-05) 33 (GSM 11.14 version 6.3.0 Release 1997) If the SIM has enough information to proceed (i.e. it has received all the data objects of the Minimum set) then it shall do so.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.2 Message too short
|
Any information received that is not a complete tag and length shall be ignored.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.3 Missing minimum information
|
If a message is received that does not have all the mandatory elements in it, then if all of the minimum set elements are present then the receiver shall complete the command and report "command performed, with missing information". If the minimum set of elements is not complete, then the ME shall respond with "Error, required values are missing".
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.4 Unknown Tag value
|
If a BER-TLV object is received that has a tag that is understood, but contains SIMPLE-TLV components that have unknown tags, then provided the minimum set condition is fulfilled, the "comprehension required" bit of the tag shall determine how the receiving entity behaves. If the comprehension required flag in an unknown tag is set to '1', and the ME either does not recognize or is not expecting one or more of the SIMPLE-TLV objects in the message, then it shall respond with "Command data not understood by ME". If the comprehension required flag is set to '0', then the ME shall read the length field that follows and ignore that object. In this case the ME will be able to carry out the command without the SIMPLE-TLV components that it cannot understand. It shall respond with "command performed with partial comprehension ".
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.5 Unexpected Tag value
|
If a BER-TLV object is received that contains elements that have recognisable tags, but which where not expected in the context of this message (for example, the ME sees SMS TDPU tag as part of TEXT FOR DISPLAY), then is shall discard that element. It shall then proceed as described for Unknown Tag values. If a received object has a tag that has already been received, then the first instance shall be used and any subsequent instances shall be discarded.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.6 Length errors
|
If the total lengths of the SIMPLE-TLV data objects are not consistent with the length given in the BER-TLV data object, then the whole BER-TLV data object shall be rejected. The result field in the TERMINAL RESPONSE shall have the error condition "Command data not understood by ME". If the length of the BER-TLV data object is shorter than the length of the response data, the ME shall ignore response data following the complete BER-TLV data object. If the length of the BER-TLV data object is longer than the length of the response data, then sections 6.10.2. and 6.10.3 apply.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.7 Contents not understood
|
If the contents of a SIMPLE-TLV data object contains a field with a value that is defined as reserved, then the whole SIMPLE-TLV data object shall be considered as invalid. It will then depend on the "comprehension required" bit of the relevant tag as to whether the whole BER-TLV data object shall be rejected, or whether that particular SIMPLE-TLV data object shall be ignored. If the contents of a BER-TLV object contains RFU bits or bytes, then these shall be ignored. ETSI TS 101 267 V6.3.0 (1999-05) 34 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.10.8 Extended length data objects
|
If a SIMPLE-TLV data object has a length longer than expected (i.e. more information has been added), then the receiver shall ignore this extra information to the end of the object. The end of the object shall be found by looking at the "length" field of that object. NOTE: If comprehension of the extra bytes is required, this can be achieved by the use of a reserved coding in an earlier field. ETSI TS 101 267 V6.3.0 (1999-05) 35 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
6.11 Proactive commands versus possible Terminal response
|
The following table shows for each proactive command the possible terminal response returned (marked by a "•" character). Proactive Command GET INKEY GET INPUT SELECT ITEM PLAY TONE DIS- PLAY TEXT SET UP MENU POLL- ING OFF POLL INTER- VAL RE- FRESH SET UP CALL SEND SMS SEND SS PRO- VIDE LOCAL INFO MORE TIME Terminal response 00 Command performed successfully • • • • • • • • • • • • • • 01 Command performed with partial comprehension • • • • • • • • • • • • • • 02 Command performed, with missing information • • • • • • • • • • • • • • 03 REFRESH performed with additional EFs read • 05 Command performed, but modified by call control by SIM • • 10 Proactive SIM session terminated by the user • • • • • • 11 Backward move in the proactive SIM session requested by the user • • • • 12 No response from user • • • • 13 Help information required by the user, • • • 20 ME currently unable to process command • • • • • • • • • • • • • • 21 Network currently unable to process command • • • 22 User did not accept call setup request • 23 User cleared down call before connection or network release • 25 interaction with call control by SIM, temporary problem • • 30 Command beyond MEs capabilities • • • • • • • • • • • • • • 31 Command type not understood by ME • • • • • • • • • • • • • • 32 Command data not understood by ME • • • • • • • • • • • • • • 33 Command number not known by ME • • • • • • • • • • • • • • 34 SS Return Error • • 35 SMS RPERROR • 36 Error, required values are missing • • • • • • • • • • • • • • 39 interaction with call control by SIM or MO short message control by SIM, permanent problem • • • ETSI TS 101 267 V6.3.0 (1999-05) 36 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7 Data download to SIM
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7.1 SMS-PP data download
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7.1.1 Procedure
|
If the service "data download via SMS Point-to-point" is allocated and activated in the SIM Service Table (see GSM 11.11 [14]), then the ME shall follow the procedure below: - When the ME receives a Short Message with: protocol identifier = SIM data download, and data coding scheme = class 2 message, then the ME shall pass the message transparently to the SIM using the ENVELOPE (SMS-PP DOWNLOAD) command as defined below. - The ME shall not display the message, or alert the user of a short message waiting. - The ME shall wait for an acknowledgement from the SIM. - If the SIM responds with '90 00', the ME shall acknowledge the receipt of the short message to the network using an RP- ACK message. - If the SIM responds with '93 00', the ME shall either retry the command or send back an RP-ERROR message to the network with the TP-FCS value indicating "SIM Application Toolkit Busy" (see GSM 03.40 [6]). - If the SIM responds with '9F XX', the ME shall use the GET RESPONSE command to get the response data. The response data from the SIM will be supplied by the ME in the TP-User-Data element of the RP-ACK message it will send back to the network (see GSM 03.40 [6] and GSM 04.11 [9]). The values of protocol identifier and data coding scheme in RP-ACK shall be as in the original message. - If the ME has indicated in TERMINAL PROFILE that it supports the status word '9E XX' and if the SIM responds with '9E XX', the ME shall use the GET RESPONSE command to get the response data. The response data from the SIM will be supplied by the ME in the TP-User-Data element of the RP-ERROR message it will send back to the network (see GSM 03.40 [6] and GSM 04.11 [9]). The values of protocol identifier and data coding scheme in RP-ERROR shall be as in the original message. The value of the TP-FCS element of the RP-ERROR shall be "SIM data download error". If the service "data download via SMS-PP" is not allocated and activated in the SIM Service Table, and the ME receives a Short Message with the protocol identifier = SIM data download and data coding scheme = class 2 message, then the ME shall store the message in EFSMS in accordance with GSM 11.11 [14]. NOTE: MEs not supporting SIM Application Toolkit are likely to store data download messages in EFSMS, as if they were normal short messages.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7.1.2 Structure of ENVELOPE (SMS-PP DOWNLOAD)
|
Direction: ME to SIM The command header is specified in GSM 11.11 [14]. Command parameters/data: Description Section M/O Min Length SMS-PP download tag 13.1 M Y 1 Length (A+B+C) - M Y 1 or 2 Device identities 12.7 M Y A Address 12.1 O N B SMS TPDU (SMS-DELIVER) 12.13 M Y C - Device identities: the ME shall set the device identities to: ETSI TS 101 267 V6.3.0 (1999-05) 37 (GSM 11.14 version 6.3.0 Release 1997) Source: Network Destination: SIM - Address: The address data object holds the RP_Originating_Address of the Service Centre (TS-Service-Centre- Address), as defined in GSM 04.11 [9]. Response parameters/data: It is permissible for the SIM not to provide response data. If the SIM responds with '90 00' then no response parameter shall be available, otherwise the SIM shall respond with '9F XX' or '9E XX' and the following data is returned: Byte(s) Description Length 1-X (X•128) SIM Acknowledgement X
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7.2 Cell Broadcast data download
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7.2.1 Procedure
|
If the service "data download via SMS-CB" is allocated and activated in the SIM Service Table (see GSM 11.11 [14]), then the ME shall follow the procedure below: - When the ME receives a new Cell Broadcast message, the ME shall compare the message identifier of the Cell Broadcast message with the message identifiers contained in EFCBMID. - If the message identifier is found in EFCBMID, the cell broadcast page is passed to the SIM using the ENVELOPE (CELL BROADCAST DOWNLOAD) command, defined below. The ME shall not display the message. - If the message identifier of the incoming cell broadcast message is not found in EFCBMID, then the ME shall determine if the message should be displayed, by following the procedures in GSM 03.41 [7] and GSM 11.11 [14]. The ME shall identify new cell broadcast pages by their message identifier, serial number and page values.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
7.2.2 Structure of ENVELOPE (CELL BROADCAST DOWNLOAD)
|
Direction: ME to SIM The command header is specified in GSM 11.11 [14]. Command parameters/data: Description Section M/O Min Length Cell Broadcast Download tag 13.1 M Y 1 Length (A+B) - M Y 1 or 2 Device identities 12.7 M Y A Cell Broadcast page 12.5 M Y B - Device identities: the ME shall set the device identities to: Source: Network Destination: SIM Response parameters/data: None for this type of ENVELOPE command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
8 Menu Selection
|
A set of possible menu options can be supplied by the SIM using the proactive command SET UP MENU. If the SIM has sent this command, and the user subsequently chooses an option or the user requests help on it, the ME informs the SIM using this procedure. ETSI TS 101 267 V6.3.0 (1999-05) 38 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
8.1 Procedure
|
If the service "menu selection" is allocated and activated in the SIM Service Table (see GSM 11.11 [14]), then the ME shall follow the procedure below. - When the ME receives a menu selection from one of the menu items defined by a "SET-UP MENU" command issued previously by the SIM, or the user has indicated the need to get help information on one of these menu items, then it shall pass the identifier of the selected menu item to the SIM using the ENVELOPE (MENU SELECTION) command, as defined below.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
8.2 Structure of ENVELOPE (MENU SELECTION)
|
Direction: ME to SIM The command header is specified in GSM 11.11 [14]. Command parameters/data: Description Section M/O Min Length Menu Selection tag 13.1 M Y 1 Length (A+B+C) - M Y 1 or 2 Device identities 12.7 M Y A Item identifier 12.10 M Y B Help request 12.21 O N C - Device identities: the ME shall set the device identities to: Source: Keypad Destination: SIM - Help request: inclusion of this data object depends upon whether the user actually selected the named menu item or just requested help information on it. If the user actually selected the menu item, this data object shall not be included. If the user indicated the need to get help information on the menu item, this data object shall be included. Response parameters/data: None for this type of ENVELOPE command.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9 Call Control by SIM
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9.1 Procedure for mobile originated calls
|
If the service "call control" is allocated and activated in the SIM Service Table (see GSM 11.11 [14]), then the ME shall follow the procedure below: - For all call set-up attempts (even those resulting from a SET UP CALL proactive SIM command, or those occurring when another call is already in progress), the ME shall first pass the call set-up details (dialled digits and associated parameters) to the SIM, using the ENVELOPE (CALL CONTROL) command defined below. The ME shall also pass to the SIM in the ENVELOPE (CALL CONTROL) command the current serving cell. One exception is for the ME managing automatic redial attempts, for which the ME is required to pass the call set-up details to the SIM for the first attempt only. The only other exception is for the user dialling "112" or an emergency call code stored in EFECC, for which the ME sets up an emergency call instead of passing the call set-up details to the SIM. - If the SIM responds with '90 00', the ME shall set up the call with the dialled digits and other parameters as sent to the SIM. - If the SIM responds with '93 00', the ME shall not set up the call and may retry the command. - If the SIM responds with '9F XX', the ME shall use the GET RESPONSE command to get the response data. The response data from the SIM shall indicate to the ME whether to set up the call as proposed, not set up the call, set up a call using the data supplied by the SIM, or instead send a supplementary service or USSD operation using the data supplied by the SIM. It is mandatory for the ME to perform the call set-up request and the supplementary service or ETSI TS 101 267 V6.3.0 (1999-05) 39 (GSM 11.14 version 6.3.0 Release 1997) USSD operation in accordance with the data from the SIM. It is possible for the SIM to request the ME to set up an emergency call by supplying the number "112" as the response data. If the SIM supplies a number stored in EFECC, this shall not result in an emergency call. In the case where the initial call set-up request results from a proactive command SET UP CALL: - if the call control result is "not allowed", the ME shall inform the SIM using TERMINAL RESPONSE ("interaction with call control by SIM or MO short message control by SIM, action not allowed"). - if the call set-up request is changed by call control in a supplementary service or USSD operation, then the ME shall send this request to the network. The ME shall then send back a TERMINAL RESPONSE to the SET UP CALL command at the same time it would have done for the proactive command equivalent to the action requested by call control (i.e. SEND SS). However, in that case, the TERMINAL RESPONSE shall contain the response data given in the response to ENVELOPE (CALL CONTROL) and a second Result TLV identical to the one given in response to the proactive command equivalent to the action requested by call control (i.e. SEND SS). The mapping between the general result in the first Result TLV and the general result in the second Result TLV is given below : - the general result "command performed, but modified by call control by SIM" shall be given in the first Result TLV if the general result of the second Result TLV is '0X' or '1X'. - the general result "interaction with call control by SIM, temporary problem" shall be given in the first Result TLV if the general result of the second Result TLV is '2X'. - the general result "interaction with call control by SIM or MO short message control by SIM, permanent problem" shall be given in the first Result TLV if the general result of the second Result TLV is '3X'. If the ME supports the Last Number Dialled service, the ME shall update EFLND with the call set-up details (digits string and associated parameters) corresponding to the initial user request. The ME shall then follow the call set-up procedure defined in GSM 04.08 [8] or the supplementary service or USSD operation procedure defined in GSM 04.80 [10].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9.2 Procedure for Supplementary Services and USSD
|
If the service "call control" is allocated and activated in the SIM Service Table (see GSM 11.11 [14]), then for all supplementary service and USSD operations (including those resulting from a SEND SS proactive SIM command), the ME shall first pass the supplementary service or USSD control string (corresponding to the supplementary service or USSD operation and coded as defined in GSM 02.30 [4], even if this SS or USSD operation has been performed via a specific menu of the ME) to the SIM, using the ENVELOPE (CALL CONTROL) command defined below. The ME shall also pass to the SIM in the ENVELOPE (CALL CONTROL) command the current serving cell. The SIM shall respond in the same way as for mobile originated calls. The ME shall interpret the response as follows: - If the SIM responds with '90 00', the ME shall send the supplementary service or USSD operation with the information as sent to the SIM. - If the SIM responds with '93 00', the ME shall not send the supplementary service or USSD operation and may retry the command. - If the SIM responds with '9F XX', the ME shall use the GET RESPONSE command to get the response data. The response data from the SIM shall indicate to the ME whether to send the supplementary service or USSD operation as proposed, not send the SS or USSD operation, send the SS or USSD operation using the data supplied by the SIM, or instead set up a call using the data supplied by the SIM. It is mandatory for the ME to perform the supplementary service or USSD operation or the call set-up request in accordance with the data from the SIM. In the case where the initial SS or USSD request results from a proactive command SEND SS: - if the call control result is "not allowed", the ME shall inform the SIM using TERMINAL RESPONSE ("interaction with call control by SIM or MO short message control by SIM, action not allowed"). - if the SS or USSD request is changed by call control in a call set-up request, then the ME shall set up the call using the data given by the SIM. The ME shall then send back a TERMINAL RESPONSE to the initial proactive command at the same time it would have done for the proactive command equivalent to the action requested by call control (i.e. SET UP CALL). However, in that case, the TERMINAL RESPONSE shall contain the response data given in the response to ENVELOPE (CALL CONTROL) and a second Result TLV identical to the one given in response to the proactive ETSI TS 101 267 V6.3.0 (1999-05) 40 (GSM 11.14 version 6.3.0 Release 1997) command equivalent to the action requested by call control (i.e. SET UP CALL). The mapping between the general result in the first Result TLV and the general result in the second Result TLV is the same as the one described in subclause 9.1. If the ME supports the Last Number Dialled service, the ME shall update EFLND with the supplementary service or USSD control string corresponding to the initial user request. The ME shall then follow the supplementary service or USSD operation procedure defined in GSM 04.80 [10] or the call set- up procedure defined in GSM 04.08 [8].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9.3 Indication to be given to the user
|
If the SIM indicates support ofThe SIM may optionally include an alpha-identifier in the response data to the ENVELOPE (CALL CONTROL) message, in order to inform the user at the time the response is received by the ME. The use of this alpha identifier by the ME is described below : - if the SIM responds with "allowed, no modification", then : - 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 during the call set-up; - 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 modify the display corresponding to the initial user request; - if the alpha identifier is not provided by the SIM, the ME may give information to the user concerning what is happening; - if the SIM responds with "not allowed", then: - 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 reason of the barring; - if the alpha identifier is provided by the SIM and is a null data object (i.e. length = '00' and no value part), the ME may give information to the user concerning what is happening; - if the alpha identifier is not provided by the SIM, the ME may give information to the user concerning what is happening. - if the SIM responds with "allowed, with modifications", then : - 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. The ME shall then not display the destination address or SS string given by the SIM. This is also an indication that the ME should not give any other information to the user on the changes made by the SIM to the initial user 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 changes made by the SIM to the initial user request. The ME shall not display the destination address or SS string given by the SIM. The ME should not modify the display corresponding to the initial user request; - if the alpha identifier is not provided by the SIM, the ME may indicate to the user that the initial user request has been changed.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9.4 Interaction with Fixed Dialling Number
|
It is permissible for the Fixed Dialling Number service to be enabled (see GSM 11.11 [14]) at the same time as Call Control is allocated and activated in the SIM Service Table. If FDN is enabled and Call Control is activated, the ME shall follow this procedure: - The ME shall check that the number (or the supplementary service control string) entered through the MMI is on the FDN list, in accordance with GSM 02.07 [19]. - If the MMI input does not pass the FDN check, the call (or the supplementary service operation) shall not be set up. ETSI TS 101 267 V6.3.0 (1999-05) 41 (GSM 11.14 version 6.3.0 Release 1997) - If the MMI input does pass the FDN check, the ME shall pass the dialled digits (or the supplementary service control string) and other parameters to the SIM, using the ENVELOPE (CALL CONTROL) command. - If the SIM responds with "allowed, no modification", the ME shall set up the call (or the supplementary service operation) as proposed. - If the SIM responds with "not allowed", the ME shall not set up the call (or the supplementary service operation). - If the SIM responds with "allowed with modifications", the ME shall set up the call (or supplementary service operation) in accordance with the response from the SIM. If the modifications involve changing the dialled digits (or the supplementary service control string), the ME shall not re-check this modified number (or string) against the FDN list. If the user wishes to enable or disable Fixed Dialling Number, the ME shall follow the procedure in GSM 11.11 [14]. The state of the Call Control service shall have no effect on this procedure.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9.5 Support of Barred Dialling Number (BDN) service
|
The BDN service shall be allocated and activated in the SIM Service Table only if Call Control is also allocated and activated in the SIM Service Table. If Barred Dialling Number service is enabled (see GSM 11.11 [14]), when receiving the dialled number (or supplementary service control string) and other parameters from the ME, the SIM may check this information against those stored in EFBDN (examples of comparison methods are given in GSM 02.07 [19]). - If the SIM responds with "not allowed" (e.g., a match is made against a BDN), the ME shall not set up the call (or the supplementary service operation). - If the SIM responds with "allowed, no modification", the ME shall set up the call (or the supplementary service operation) as proposed. - If the SIM responds with "allowed with modifications", the ME shall set up the call (or the supplementary service operation) in accordance with the response from the SIM. If the modifications involve changing the dialled number (or the supplementary service control string), the ME shall not re-check this modified number (or string) against the FDN list when FDN is enabled. If the user wishes to enable or disable Barred Dialling Number, the ME shall follow the procedure in GSM 11.11 [14].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
9.6 Structure of ENVELOPE (CALL CONTROL)
|
Direction: ME to SIM The command header is specified in GSM 11.11 [14]. Command parameters/data: Description Section M/O Min Length Call control tag 13.1 M Y 1 Length (A+B+C+D+E) - M Y 1 or 2 Device identities 12.7 M Y A Address or SS string 12.1 or 12.14 M Y B Capability configuration parameters 12.4 O N C Called party subaddress 12.3 O N D Location information 12.19 M N E - Device identities: the ME shall set the device identities to: Source: ME Destination: SIM - Address or SS string : only one data object shall be sent to the SIM. ETSI TS 101 267 V6.3.0 (1999-05) 42 (GSM 11.14 version 6.3.0 Release 1997) For a call set-up, the address data object is used and holds the Called Party Number, as defined in GSM 04.08 [8], to which the ME is proposing setting up the call. For a supplementary service operation, the SS string data object is used and holds the corresponding supplementary service control string. - Capability configuration parameters: Only used for a call set-up, this contains the Bearer capabilities that the ME is proposing to send to the network. If this data object is not present, this shall indicate a speech call. - Called party subaddress: Only used for a call set-up, this contains the called party subaddress that the ME is proposing to send to the network. If one is not present, this shall indicate that the ME is proposing not to send this information element to the network. - Location information: This data object contains the identification (MCC, MNC, LAC, Cell Identity) of the current serving cell of the MS. The comprehension required flag of this data object in this command shall be set to '0'. Response parameters/data: It is permissible for the SIM to provide no response data, by responding with SW1 / SW2 = '90 00'. If the SIM does not provide any response data, then this shall have the same meaning as "allowed, no modification". Description Section M/O Min Length Call control result - M Y 1 Length (A+B+C+D) - M Y 1 or 2 Address or SS string 12.1 or 12.14 O N A Capability configuration parameters 12.4 O N B Called party subaddress 12.3 O N C Alpha identifier 12.2 O N D - Call control result: Contents: the command that the SIM gives to the ME concerning whether to allow, bar or modify the proposed call (or supplementary service operation). Coding: '00' = Allowed, no modification '01' = Not allowed '02' = Allowed with modifications - Address or SS string : Only one data object may be included if the SIM requests the call (or supplementary service operation) details to be modified. For a call set-up, if the address data object is not present, then the ME shall assume the Dialling number is not to be modified. For a supplementary service operation, if the SS string data object is not present, then the ME shall assume that SS operation is not to be modified. - Capability configuration parameters: Only used for a call set-up, this data object is only required if the SIM requests the call details to be modified. If the capability configuration parameters are not present, then the ME shall assume the parameters are not to be modified. - Called party subaddress: Only used for a call set-up, this data object is only required if the SIM requests the call details to be modified. If the called party subaddress is not present, then the ME shall assume the subaddress is not to be modified. If the subaddress supplied by the SIM is a null data object, then the ME shall not provide a called party subaddress to the network. A null data object shall have length = '00' and no value part. - Alpha identifier: this data object is only required if the SIM requests a particular indication to be given to the user. The handling of this data object by the ME is described in section 9.3. The comprehension required flag of this data object shall be set to '0'. It is mandatory for the SIM to provide at least one of the optional data objects if it has set the Call control result to "allowed with modifications". ETSI TS 101 267 V6.3.0 (1999-05) 43 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
10 Not used
|
11 Not used
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12 SIMPLE-TLV data objects
|
This clause specifies the coding of the SIMPLE-TLV data objects, which are contained in a BER-TLV data object. SIMPLE- TLV data objects may be transferred across the interface in either direction. A SIMPLE-TLV data object consists of a tag of length one byte, a length indicator, which gives the number of bytes in the value field, and a value part of variable length, whose contents, meaning and coding are given below. Tag codings are given in subclause 13.3 for all SIMPLE-TLV data objects. '00' and 'FF' are never used as tag values for SIMPLE-TLVs. This is in alignment with ISO/IEC 7816-6 [17]. Padding characters are not allowed. For some of the SIMPLE-TLV data objects described, the length field shall be coded on 1 or 2 bytes (Y value) according to annex D, depending on the value of byte 1. All bits and bytes indicated as RFU within all SIMPLE-TLV data objects shall be respectively set to 0 and ‘00’ by the sending entity. The handling of reserved values and RFU bits or bytes within all SIMPLE-TLV data objects at the receiving entity is described in subclause 6.10.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.1 Address
|
Byte(s) Description Length 1 Address tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 TON and NPI 1 (Y-1)+4 to (Y-1)+X+2 Dialling number string X-1 TON/NPI is coded as for EFADN. Dialling number string is coded as for EFADN, and may include DTMF separators and DTMF digits, which the ME shall send in the same way as for EFADN. See GSM 11.11 [14] for the coding of all EFs.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.2 Alpha identifier
|
Byte(s) Description Length 1 Alpha identifier tag 1 2 to (Y-1)+2 Length (X) Y1 (Y-1)+3 to (Y-1)+X+2 Alpha identifier X The alpha identifier is coded as for EFADN. See GSM 11.11 [14] for the coding of all EFs. ETSI TS 101 267 V6.3.0 (1999-05) 44 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.3 Called party subaddress
|
Byte(s) Description Length 1 Called party subaddress tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 to (Y-1)+X+2 Called party subaddress X Called party subaddress contains information as defined for this purpose in GSM 04.08 [8]. All information defined in GSM 04.08 shall be given in the value part of the data object, except the information element identifier and the length of called party subaddress contents (which is given by the length part of the data object).
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.4 Capability configuration parameters
|
Byte(s) Description Length 1 Capability configuration parameters tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 to (Y-1)+X+2 Capability configuration parameters X Capability configuration parameters are coded as for EFCCP. If it is being provided by the SIM, the SIM shall supply all information required to complete the Bearer Capability Information Element in the Call Set-up message (see GSM 04.08 [8]). Any unused bytes at the end of the value part shall be coded 'FF'. See GSM 11.11 [14] for the coding of all EFs. Note: The second byte of this TLV contains the length of the TLV and the third byte contains the length of the bearer capability contents, followed by the actual contents.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.5 Cell Broadcast Page
|
Byte(s) Description Length 1 Cell Broadcast page tag 1 2 Length = '58' (88 decimal) 1 3 - 90 Cell Broadcast page 88 The Cell Broadcast page is formatted in the same way as described in GSM 03.41 [7].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.6 Command details
|
Byte(s) Description Length 1 Command details tag 1 2 Length = '03' 1 3 Command number 1 4 Type of command 1 5 Command Qualifier 1 - Command number For contents and coding, see subclause 6.5.1. - Type of command: Contents: The Type of Command specifies the required interpretation of the data objects which follow, and the required ME procedure. Coding: See section 13.4 The ME shall respond to reserved values (i.e. values not listed) with the result "Command type not understood". ETSI TS 101 267 V6.3.0 (1999-05) 45 (GSM 11.14 version 6.3.0 Release 1997) - Command Qualifier: Contents: Qualifiers specific to the command. Coding: - REFRESH; '00' =SIM Initialization and Full File Change Notification; '01' = File Change Notification; '02' = SIM Initialization and File Change Notification; '03' = SIM Initialization; '04' = SIM Reset; '05' to 'FF' = reserved values. - MORE TIME; This byte is RFU. - POLL INTERVAL; This byte is RFU. - POLLING OFF; This byte is RFU. - SET UP CALL; '00' = set up call, but only if not currently busy on another call; '01' = set up call, but only if not currently busy on another call, with redial; '02' = set up call, putting all other calls (if any) on hold; '03' = set up call, putting all other calls (if any) on hold, with redial; '04' = set up call, disconnecting all other calls (if any); '05' = set up call, disconnecting all other calls (if any), with redial; '06' to 'FF' = reserved values. - SEND SS; This byte is RFU. - SEND SHORT MESSAGE; bit 1: 0 = packing not required 1 = SMS packing by the ME required bits 2-8: = 0 RFU. - PLAY TONE; This byte is RFU. - DISPLAY TEXT, bit 1: 0 = normal priority 1 = high priority bits 2-7: = RFU bit 8: 0 = clear message after a delay 1 = wait for user to clear message - GET INKEY, bit 1 0 = digits (0-9, *, # and +) only 1 = alphabet set; bit 2 0 = SMS default alphabet 1 = UCS2 alphabet bits 3-7: = RFU bit 8: 0 = no help information available 1 = help information available - GET INPUT, bit 1 0 = digits (0-9, *, #, and +) only 1 = alphabet set bit 2 0 = SMS default alphabet 1 = UCS2 alphabet bit 3: 0 = ME may echo user input on the display 1 = user input shall not be revealed in any way (see note) bit 4: 0 = user input to be in unpacked format ETSI TS 101 267 V6.3.0 (1999-05) 46 (GSM 11.14 version 6.3.0 Release 1997) 1 = user input to be in SMS packed format bits 5 to 7: = RFU bit 8: 0 = no help information available 1 = help information available NOTE: Where user input is not to be revealed, the ME may provide an indication of key entries, such as by displaying "*"s. See subclause 6.4.3 for more information on the character set available in this mode. - SELECT ITEM. bits 1 to 7: = RFU bit 8: 0 = no help information available 1 = help information available - SET UP MENU. bits 1 to 7 = RFU bit 8 0 = no help information available 1 = help information available PROVIDE LOCAL INFORMATION '00' = Location Information (MCC, MNC, LAC and Cell Identity) '01' = IMEI of the ME '02' = Network Measurement Results '03' to 'FF' = Reserved The ME shall respond to reserved values with the result "Command type not understood".
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.7 Device identities
|
Byte(s) Description Length 1 Device identities tag 1 2 Length = '02' 1 3 Source device identity 1 4 Destination device identity 1 - Source device identity Contents: the source device for information held in the data objects which follow. - Destination device identity Contents: the destination device for information held in the data objects which follow. NOTE: Only some combinations of Type of Command, Data Download type and Device identities are allowed. These are defined in clause 14. Coding: both Source and Destination device identities are coded as follows: - '01' = Keypad - '02' = Display - '03' = Earpiece - '81' = SIM - '82' = ME - '83' = Network All other values are reserved.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.8 Duration
|
Byte(s) Description Length 1 Duration tag 1 2 Length = '02' 1 3 Time unit 1 4 Time interval 1 ETSI TS 101 267 V6.3.0 (1999-05) 47 (GSM 11.14 version 6.3.0 Release 1997) - Time unit Contents: time unit used; minutes, seconds or tenths of seconds. Coding: '00'Minutes '01'Seconds '02'Tenths of seconds All other values are reserved. - Time interval Contents: the length of time required, expressed in units. Coding: The time interval is coded in integer multiples of the time unit used. The range is from 1 unit to 255 units. The encoding is: - '00': reserved - '01': 1 unit - '02': 2 units - : : - 'FF': 255 units
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.9 Item
|
Byte(s) Description Length 1 Item tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 Identifier of item 1 (Y-1)+4 to (Y-1)+X+2 Text string of item X - 1 The identifier is a single byte between '01' and 'FF'. Each item shall have a unique identifier within an Item list. The text string is coded in the same way as the alpha identifier for EFADN. Any unused bytes at the end of the value part shall be coded 'FF'.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.10 Item identifier
|
Byte(s) Description Length 1 Item identifier tag 1 2 Length = '01' 1 3 Identifier of item chosen 1 The identifier is a single byte between '01' and 'FF', exactly the same as for the Item data object. A null item identifier is coded '00'.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.11 Response length
|
Byte(s) Description Length 1 Response length tag 1 2 Length = '02' 1 3 Minimum length of response 1 4 Maximum length of response 1 The range of length is between '00' and 'FF'. A minimum length coding of '00' indicates that there is no minimum length requirement; a maximum length coding of 'FF' indicates that there is no maximum length requirement. If a fixed length is required the minimum and maximum values are identical. ETSI TS 101 267 V6.3.0 (1999-05) 48 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.12 Result
|
Byte(s) Description Length 1 Result tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 General result 1 (Y-1)+4 to (Y-1)+X+2 Additional information on result X-1 - General result Contents: General result specifies the result and indicates appropriate SIM action: Coding: - '00' = Command performed successfully; - '01' = Command performed with partial comprehension; - '02' = Command performed, with missing information; - '03' = REFRESH performed with additional EFs read; - '04' = RFU; - '05' = Command performed, but modified by call control by SIM; - '10' = Proactive SIM session terminated by the user; - '11' = Backward move in the proactive SIM session requested by the user; - '12' = No response from user; - ‘13’ = Help information required by the user. Results '0X' and '1X' indicate that the command has been performed. - '20' = ME currently unable to process command; - '21' = Network currently unable to process command; - '22' = User did not accept call set-up request; - '23' = User cleared down call before connection or network release; - '24' = RFU; - '25' = Interaction with call control by SIM, temporary problem. Results '2X' indicate to the SIM that it may be worth re-trying the command at a later opportunity. - '30' = Command beyond ME's capabilities; - '31' = Command type not understood by ME; - '32' = Command data not understood by ME; - '33' = Command number not known by ME; - '34' = SS Return Error; - '35' = SMS RP-ERROR; - '36' = Error, required values are missing; - '37' = RFU; - '38' = RFU; - '39' = Interaction with call control by SIM or MO short message control by SIM, permanent problem. Results '3X' indicate that it is not worth the SIM re-trying with an identical command, as it will only get the same response. However, the decision to retry lies with the SIM application. The SIM application should avoid a rapid sequence of repeated retried commands as this may be detrimental to ME performance. All other values are reserved. - Additional information Contents: For the general result "Command performed successfully", some proactive commands require additional information in the command result. This is defined in the subclauses below. For the general results '20', '21', '34', '35', '37' and '39', it is mandatory for the ME to provide a specific cause value as additional information, as defined in the subclauses below. For the other general results, the ME may optionally supply additional information. If additional information is not supplied, then the length of the value part of the data object need only contain the general result. ETSI TS 101 267 V6.3.0 (1999-05) 49 (GSM 11.14 version 6.3.0 Release 1997) 12.12.1 Additional information for SEND SS When the ME issues a successful COMMAND RESULT for a SEND SS proactive command, it shall also include the Operation Code and Parameters included in the Return Result component from the network, as additional information. The first byte of the additional information shall be the SS Return Result Operation code, as defined in GSM 04.80 [10]. The rest of the additional information shall be the SS Return Result Parameters, as defined in GSM 04.80 [10]. 12.12.2 Additional information for ME problem For the general result "ME currently unable to process command", it is mandatory for the ME to provide additional information, the first byte of which to be as defined below: - '00' = No specific cause can be given; - '01' = Screen is busy; - '02' = ME currently busy on call; - '03' = ME currently busy on SS transaction; - '04' = No service; - '05' = Access control class bar; - '06' = Radio resource not granted; - '07' = Not in speech call. - ‘08’ = ME currently busy on USSD transaction All other values shall be interpreted by the SIM as '00'.The coding '00' shall only be used by the ME if no others apply. 12.12.3 Additional information for network problem For the general result "network currently unable to process command", it is mandatory for the ME to provide additional information. The first byte shall be the cause value of the Cause information element returned by the network (as defined in GSM 04.08 [8]). Bit 8 shall be set to '1'. One further value is defined: - '00' = No specific cause can be given. All other values shall be interpreted by the SIM as '00'. The coding '00' shall only be used by the ME if no others apply. 12.12.4 Additional information for SS problem For the general result "SS Return Error", it is mandatory for the ME to provide additional information. The first byte shall be the error value given in the Facility (Return result) information element returned by the network (as defined in GSM 04.80 [10]). One further value is defined: - '00' = No specific cause can be given. All other values shall be interpreted by the SIM as '00'. The coding '00' shall only be used by the ME if no others apply. 12.12.5 Additional information for SMS problem For the general result "SMS RP-ERROR", it is mandatory for the ME to provide additional information. The first byte shall be the cause value given in the RP-Cause element of the RP-ERROR message returned by the network (as defined in GSM 04.11 [9]), with bit 8 = 0. One further value is defined: - '00' = No specific cause can be given. All other values shall be interpreted by the SIM as '00'. Specific cause '00' shall only be used by the ME if no others apply. 12.12.6 Not used 12.12.7 Not used ETSI TS 101 267 V6.3.0 (1999-05) 50 (GSM 11.14 version 6.3.0 Release 1997) 12.12.8 Additional information for interaction with call control For the general result "interaction with call control by SIM or MO short message control by SIM, permanent problem", it is mandatory for the ME to provide additional information, the first byte of which to be as defined below: - '00' = No specific cause can be given; - '01' = Action not allowed; - '02' = The type of request has changed All other values shall be interpreted by the SIM as '00'.The coding '00' shall only be used by the ME if no others apply.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.13 SMS TPDU
|
Byte(s) Description Length 1 SMS TPDU tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 to (Y-1)+X+2 SMS TPDU X The TPDU is formatted as described in GSM 03.40 [6]. Where the TPDU is being sent from the SIM to the ME (to be forwarded to the network), and where it includes a TP-Message- Reference which is to be incremented by the ME for every outgoing message, the TP-Message-Reference as provided by the SIM need not be the valid value. TP-Message-Reference shall be checked and corrected by the ME to the value described in GSM 03.40 [6].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.14 SS string
|
Byte(s) Description Length 1 SS string tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 TON and NPI 1 (Y-1)+4 to (Y-1)+X+2 SS or USSD string X - 1 TON/NPI and SS or USSD control string are coded as for EFADN, where the ADN record relates to a Supplementary Service Control string. See GSM 11.11 [14] for the coding of EFADN.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.15 Text string
|
Byte(s) Description Length 1 Text string tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 Data coding scheme 1 (Y-1)+4 to (Y-1)+X+2 Text string X-1 A null text string shall be coded with Length = '00', and no Value part. Data coding scheme is coded as for SMS Data coding scheme defined in GSM 03.38 [5]. 12.15.1 Coding of text in unpacked format This is indicated by the data coding scheme having a value of 8 bit data. Other parts of the data coding scheme shall be ignored. This string shall be no longer than 160 characters, and use the SMS default 7-bit coded alphabet as defined in GSM 03.38 [5] with bit 8 set to 0. It may or may not include formatting characters, but all such formatting characters shall be taken from the set given in the SMS alphabet. ETSI TS 101 267 V6.3.0 (1999-05) 51 (GSM 11.14 version 6.3.0 Release 1997) NOTE: This is exactly the same format as is used for EFADN alpha-identifiers. It is also the same as SMS messages that have been "unpacked". 12.15.2 Coding of text in packed format This is indicated by the data coding scheme having a value of 7 bit GSM default alphabet. Other parts of the data coding scheme shall be ignored. This string shall be no longer than 160 characters, and use the SMS default 7-bit coded alphabet, packed into 8-bit octets, as defined in GSM 03.38 [5]. It may or may not include formatting characters, but all such formatting characters shall be taken from the set given in the SMS alphabet. If the total number of characters in the text string equals (8n-1) where n=1,2,3 etc. then there are 7 spare bits at the end of the message. To avoid the situation where the receiving entity confuses 7 binary zero pad bits as the @ character, the carriage return (i.e. <CR>) character shall be used for padding in this situation, as defined in GSM 03.38 [5]. NOTE: This is the same format as is used in SMS messages to and from the network. 12.15.3 Coding of text in 16 bits UCS2 alphabet format This is indicated by the data coding scheme having a value of 16 bit UCS2 alphabet. Other parts of the data coding scheme shall be ignored. This string shall be no longer than 140 bytes, i.e. up to 70 UCS2 characters and use the UCS2 alphabet if the UCS2 is supported, as defined in GSM 03.38 [5]. It may or may not include formatting characters, but all such formatting characters shall be taken from the set given in the UCS2 alphabet. NOTE: This is the same format as is used in SMS messages to and from the network.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.16 Tone
|
Byte(s) Description Length 1 Tone tag 1 2 Length = '01' 1 3 Tone 1 - Tone Contents: Tones can be either the standard supervisory tone, as defined in GSM 02.40 [18], or proprietary tones defined by the ME manufacturer. The code values for proprietary tones shall be supported by the ME. If proprietary tones are not supported the ME shall map these codings to tones that it can generate. The tones to be used are left as an implementation decision by the manufacturer. Coding: Standard supervisory tones: '01' Dial tone '02' Called subscriber busy '03' Congestion '04' Radio path acknowledge '05' Radio path not available / Call dropped '06' Error / Special information '07' Call waiting tone '08' Ringing tone ME proprietary tones: '10' General beep '11' Positive acknowledgement tone '12' Negative acknowledgement or error tone All other values are reserved. ETSI TS 101 267 V6.3.0 (1999-05) 52 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.17 Not used
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.18 File List
|
Byte(s) Description Length 1 File List tag 1 2 to (Y-1)+2 Length (X) of bytes following Y (Y-1)+3 Number of files (n) 1 (Y-1)+4 to (Y-1)+X+2 Files X-1 Number of files: This is the number of files that will be described in the following list. Files: Full paths are given to files. Each of these shall be at least 4 octets in length (e.g. '3F002FE2' or '3F007F206FAD'). Each entry in the file description is composed of two bytes, where the first byte identifies the type of file (see GSM 11.11). An entry in the file description shall therefore always begin with '3FXX'. There can be any number of Dedicated File entries between the Master File and Elementary File. There shall be no delimiters between files, as this is implied by the fact that the full path to any EF starts with '3FXX' and ends with an Elementary type file.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.19 LOCATION INFORMATION
|
Byte(s) Description Length 1 Location Information tag 1 2 Length = ‘07’ 1 3 - 5 Mobile Country & Network Codes (MCC & MNC) 3 6 - 7 Location Area Code (LAC) 2 8 - 9 Cell Identity Value (Cell ID) 2 The mobile country code (MCC), the mobile network code (MNC), the location area code (LAC) and the cell ID are coded as in GSM 04.08 [8].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.20 IMEI
|
Byte(s) Description Length 1 IMEI tag 1 2 Length = ‘08’ 1 3 - 10 IMEI of the ME 8 The IMEI is coded as in GSM 04.08 [8].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.21 Help Request
|
Byte(s) Description Length 1 Help Request tag 1 2 Length = ‘00’ 1
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.22 Network Measurement Results
|
ETSI TS 101 267 V6.3.0 (1999-05) 53 (GSM 11.14 version 6.3.0 Release 1997) Byte(s) Description Length 1 Network Measurement Results tag 1 2 Length = '10' 1 3 - 18 Network Measurement Results 16 The Network Measurement Results are coded as for the Measurement Results information element in GSM 04.08 [8], starting at octet 2 (the IEI is removed, as this information is duplicated by the data object tag).
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.23 Default Text
|
The coding of this data object is the same as for the Text String data object (see subclause 12.15) with the exception that the Default Text tag has a specific value (see subclause 13.3).
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.24 Items Next Action Indicator
|
Byte(s) Description Length 1 Items Next Action Indicator tag 1 2 Length (X) 1 3 to 3+X-1 Items Next Action Indicator list X Contents : Each item of a list of items has a next action indicator coded on one byte. The length of the Items Next Action Indicator list shall be the number of items of the list of items (X shall be the number of items in the list). The order of each item next action indicator, shall reflect the order o the items in the list of items. The Item Next action indicator gives the possible actions that will be initiated by the SIM in case of selection by the user. Coding : If the value is equal to ‘00' or if the value is reserved (that is, value not listed), the ME shall ignore the next action indicator type. See subclause 13.4 for further information. Example : For the following list of items : - item #1; - item #2; - item #3; - .... - item #n, the Items Next Action Indicator (NAI) shall be as follows : Tag Length NAI#1 NAI#2 NAI#3 ... NAI#n
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.25 Not Used
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.26 Not used
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.27 Not used
| |
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.28 Not used
|
ETSI TS 101 267 V6.3.0 (1999-05) 54 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.29 BCCH channel list
|
Byte(s) Description Length 1 BCCH channel list tag 1 2 Length (X) of bytes following 1 3 to X+2 BCCH channel list X - BCCH channel list Contents: the list of absolute RF channels for BCCH carriers, as known by the ME from the SYSTEM INFORMATION messages. The BCCH channel list is composed of one to three BCCH channel sub lists, each sub list is derived from the set of frequencies defined by reference neighbour cells description information element or elements. In the latter case the set is the union of the different subsets defined by the neighbour cells description information elements. The length X is therefore 16 bytes (one sub list), 32 bytes (two sub lists) or 48 bytes (three sub lists). See the description of the measurement result information element in GSM 04.08 [8] for more details. Coding: as for the neighbour cell description information element in GSM 04.08 [8].
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
12.30 Call control requested action
|
Byte(s) Description Length 1 Call control requested action tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 to (Y-1)+X+2 Call control requested action X - Call control requested action Contents: The action given in response to the ENVELOPE (CALL CONTROL). It may contain in the same order as given by the SIM, the address or SS string, the capability configuration parameters, the called party sub-address and the alpha identifier. Coding: as described in subclause 9.1, starting with the first optional element given in the response data to the ENVELOPE (CALL CONTROL).
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
13 Tag values
|
This clause specifies the tag values used to identify the BER-TLV and SIMPLE-TLV data objects used in the present document. ETSI TS 101 267 V6.3.0 (1999-05) 55 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
13.1 BER-TLV tags in ME to SIM direction
|
Description Length of tag Value SMS-PP download tag 1 'D1' Cell Broadcast download tag 1 'D2' Menu Selection tag 1 'D3' Call control tag 1 'D4'
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
13.2 BER-TLV tags in SIM TO ME direction
|
Description Length of tag Value Proactive SIM command tag 1 'D0'
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
13.3 SIMPLE-TLV tags in both directions
|
8 7 6 5 4 3 2 1 CR Tag value CR: Comprehension required for this object. Unless otherwise stated, for SIMPLE-TLV data objects it is the responsibility of the SIM application and the ME to decide the value of the CR flag for each data object in a given command. Handling of the CR flag at the receiving entity is described in subclause 6.10. CR Value Comprehension required 1 Comprehension not required 0 Description Length of tag Tag value, bits 1-7 (Range: '01' - '7E') Tag (CR and Tag value) Command details tag 1 '01' '01' or ‘81’ Device identity tag 1 '02' '02' or ‘82’ Result tag 1 '03' '03' or ‘83’ Duration tag 1 '04' '04’ or ‘84’ Alpha identifier tag 1 '05' '05’ or ‘85’ Address tag 1 '06' '06’ or ‘86’ Capability configuration parameters tag 1 '07' '07’ or ‘87’ Called party subaddress tag 1 '08' '08’ or ‘88’ SS string tag 1 '09' '09’ or ‘89’ RFU 1 '0A' '0A’ or ‘8A’ SMS TPDU tag 1 '0B' '0B’ or ‘8B’ Cell Broadcast page tag 1 '0C' '0C’ or ‘8C’ Text string tag 1 '0D' '0D’ or ‘8D’ Tone tag 1 '0E' '0E’ or ‘8E’ Item tag 1 '0F' '0F’ or ‘8F’ Item identifier tag 1 '10' '10’ or ‘90’ Response length tag 1 '11' '11’ or ‘91’ File List tag 1 '12' '12’ or ‘92’ Location Information tag 1 '13' '13’ or ‘93’ IMEI tag 1 '14' '14’ or ‘94’ Help request tag 1 '15' '15' or '95' Network Measurement Results tag 1 '16' '16' or '96' Default Text 1 ‘17’ ‘17’ or ‘97’ Items Next Action Indicator tag 1 ‘18’ ‘18’ only RFU 1 ‘19’ '19' or '99' RFU 1 ‘1A’ '1A' or '9A' RFU 1 ‘1B’ '1B' or '9B' RFU 1 ‘1C’ '1C' or '9C' BCCH channel list tag 1 '1D' '1D' or '9D' Call control requested action 1 '27' '27' or 'A7' ETSI TS 101 267 V6.3.0 (1999-05) 56 (GSM 11.14 version 6.3.0 Release 1997)
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
13.4 Type of Command and Next Action Indicator
|
The table below shows the values which shall be used for Type of Command coding (see subclause 12.6) and Next Action Indicator coding (see subclause 12.24). Value Name used for Type of Command coding used for Next Action Indicator coding ‘00’ - - ‘01’ REFRESH X ‘02’ MORE TIME X ‘03’ POLL INTERVAL X ‘04’ POLLING OFF X ‘10’ SET UP CALL X X ‘11’ SEND SS X X ‘13’ SEND SHORT MESSAGE X X ‘20’ PLAY TONE X X ‘21’ DISPLAY TEXT X X ‘22’ GET INKEY X X ‘23’ GET INPUT X X ‘24’ SELECT ITEM X X ‘25’ SET UP MENU X X ‘26’ PROVIDE LOCAL INFORMATION X ‘81’ End of the proactive session not applicable X 14 Allowed Type of command and Device identity combinations Only certain types of commands can be issued with certain device identities. These are defined below: Command description Source Destination CALL CONTROL ME SIM CELL BROADCAST DOWNLOAD Network SIM COMMAND RESULT ME SIM DISPLAY TEXT SIM Display GET INKEY SIM ME GET INPUT SIM ME MENU SELECTION Keypad SIM MORE TIME SIM ME PLAY TONE SIM Earpiece (see note) POLLING OFF SIM ME POLL INTERVAL SIM ME PROFILE DOWNLOAD ME SIM REFRESH SIM ME SELECT ITEM SIM ME SEND SHORT MESSAGE SIM Network SEND SS SIM Network SET UP CALL SIM Network SET UP MENU SIM ME SMS-PP DOWNLOAD Network SIM PROVIDE LOCAL INFORMATION SIM ME NOTE: The ME may route the tone to other loudspeakers (external ringer, car kit) if more appropriate.
|
099e4bd0b61d814e89668f7c98053995
|
101 267
|
15 Security requirements
|
GSM 03.48 [24] specifies standardised methods of securing the content of application messages to and from the SIM Application Toolkit. If it is necessary to secure application messaging to Toolkit applications, then GSM 03.48 may be used. ETSI TS 101 267 V6.3.0 (1999-05) 57 (GSM 11.14 version 6.3.0 Release 1997) Annex A (normative): Support of SIM Application Toolkit by Mobile Equipment Support of SIM Application Toolkit is optional for Mobile Equipment. However, any ME claiming to support SIM Application Toolkit need not support all toolkit functions from all numerical classes, but, support of all functions within a class is mandatory. The table below indicates the classes. Classes Command description 1bis 2 CALL CONTROL X CELL BROADCAST DOWNLOAD X DISPLAY TEXT X X GET INKEY X GET INPUT X X MENU SELECTION X X MORE TIME X PLAY TONE X X POLLING OFF X POLL INTERVAL X PROVIDE LOCAL INFORMATION X X REFRESH X X SELECT ITEM X X SEND SHORT MESSAGE X X SEND SS X X SET UP CALL (idle only) X X SET UP CALL (full implementation) X SET UP MENU X X SMS-PP DOWNLOAD X X ETSI TS 101 267 V6.3.0 (1999-05) 58 (GSM 11.14 version 6.3.0 Release 1997) Annex B (informative): Example command sequences for proactive SIM This subclause shows example APDU sequences for proactive SIM commands, and is for information only. Case 1: Proactive SIM request following a normal command from the ME ME SIM Normal command Normal Data, if any '91' lgth [Possible "normal GSM operation" command/response pairs] FETCH Proactive SIM command '90' '00' [Possible "normal GSM operation" command/response pairs] [ME performs command] TERMINAL RESPONSE (OK) '90' '00' Case 2: Proactive SIM request following a (polling) STATUS command from the ME ME SIM STATUS command Normal Data on DF '91' lgth [Possible "normal GSM operation" command/response pairs] FETCH Proactive SIM command '90' '00' [Possible "normal GSM operation" command/response pairs] [ME performs command] TERMINAL RESPONSE (OK) '90' '00' Case 3: STATUS command from ME, not followed by any proactive SIM request ME SIM STATUS command Normal Data on DF '90' '00' Case 4: Unsuccessful proactive SIM request, followed by SIM asking the ME to retry ME SIM Normal command Normal Data, if any '91' lgth ETSI TS 101 267 V6.3.0 (1999-05) 59 (GSM 11.14 version 6.3.0 Release 1997) [Possible "normal GSM operation" command/response pairs] FETCH Proactive SIM command '90' '00' [Possible "normal GSM operation" command/response pairs] [ME performs command] TERMINAL RESPONSE (temporary problem) '91' lgth [Possible "normal GSM operation" command/response pairs] FETCH Repeat of proactive SIM command '90' '00' [Possible "normal GSM operation" command/response pairs] [ME performs command] TERMINAL RESPONSE (OK) '90' '00' Case 5: Unsuccessful proactive SIM request, and the SIM does not ask for the ME to retry ME SIM Normal command Normal Data, if any '91' lgth [Possible "normal GSM operation" command/response pairs] FETCH Proactive SIM command '90' '00' [Possible "normal GSM operation" command/response pairs] [ME performs command] TERMINAL RESPONSE (temporary problem) '90' '00' ETSI TS 101 267 V6.3.0 (1999-05) 60 (GSM 11.14 version 6.3.0 Release 1997) Annex C (informative): Example of DISPLAY TEXT Proactive SIM Command Example of DISPLAY TEXT Proactive SIM Command (BER-TLV Data Object) Byte# Value (Hex) Description 1 D0 Proactive SIM command tag 2 0F length 3 81 command details tag 4 03 length 5 01 command number 6 - 7 21 00 Display text (normal priority, clear message after a delay) 8 82 Device identities tag 9 02 length 10 81 source: SIM 11 02 destination: Display 12 8D Text string tag 13 04 length 14 04 Data coding scheme ('04'=8-bit default SMS) 15 - 17 53,41,54 text string ("SAT") ETSI TS 101 267 V6.3.0 (1999-05) 61 (GSM 11.14 version 6.3.0 Release 1997) Annex D (normative): Structure of SIM Application Toolkit communications BER-TLV data object T L V 1..n SIMPLE-TLV objects SIMPLE-TLV data object T L V 1..m elements T L V Elements within the data object SIM Application Toolkit commands and responses are sent across the interface as BER-TLV data objects. Each APDU shall only contain one BER-TLV object. The tag is a constant value, length one byte, indicating it is a SIM Application Toolkit command. The length is coded onto 1,or 2 bytes according to ISO/IEC 7816-6 [17]. The following table details this coding: Length Byte 1 Byte 2 0-127 length ('00' to '7F') not present 128-255 '81' length ('80' to 'FF') Any length within the APDU limits (up to 255 bytes) can thus be encoded on two bytes. This coding is chosen to remain compatible with ISO/IEC 7816-6 [17]. Any values for byte 1 or byte 2 that are not shown above shall be treated as an error and the whole message shall be rejected. The value part of the BER-TLV data object consists of SIMPLE-TLV data objects, as shown in the description of the SIMPLE- TLV data objects on individual commands. It is mandatory for SIMPLE-TLV data objects to be provided in the order given in the description of each command. New SIMPLE-TLV data objects can be added to the end of a command. The M/O columns specify whether it is mandatory or optional for the sender to send that particular SIMPLE-TLV data object for compliance with the current version of the present document. The Min (Minimum Set) column describes whether it is necessary for the receiver to have received that particular SIMPLE-TLV data object to be able to attempt at least the most basic form of this command. The procedure for dealing with incomplete messages is described in subclause 6.10. '00' and 'FF' are never used as tag values for BER-TLVs. This is in accordance with ISO/IEC 7816-6 [17]. Padding characters are not allowed. See ISO/IEC 7816-6 [17] for more information on data objects. ETSI TS 101 267 V6.3.0 (1999-05) 62 (GSM 11.14 version 6.3.0 Release 1997) Annex E (informative): ME display in proactive SIM session Example of the ME display whilst the ME is in a proactive SIM session. ME [Setup menu being navigated] Envelope (Menu Selection) SW = 91 XX Fetch Select Item Terminal Response SW = 91 XX Fetch Get Inkey Terminal Response SW = 90 00 SIM Setup Menu list Select Item list Get Inkey ME Display ME display ETSI TS 101 267 V6.3.0 (1999-05) 63 (GSM 11.14 version 6.3.0 Release 1997) Annex F (informative): Help information feature processing The following example shows the use of the commands Menu Selection / Select Item and Get Input in conjunction with the help information feature. ME SIM TERMINAL PROFILE ------------------> <----------------- 91xx FETCH ------------------> <----------------- SET UP MENU (Help available) TERMINAL RESPONSE (OK) ------------------> <----------------- 90 00 ... ENVELOPE (MENU SELECTION, help on menu item m) ------------------> <----------------- 91 xx FETCH ------------------> <----------------- DISPLAY TEXT (Help info to item m) TERMINAL RESPONSE (OK) ------------------> <----------------- 90 00 (ME offers menu again and user selects item m) ENVELOPE (MENU SELECTION, select item m) ------------------> <----------------- 91 xx FETCH ------------------> <----------------- SELECT ITEM (Item list under item m, help available) TERMINAL RESPONSE (Help on item mn in item list under item m ) ------------------> <----------------- 91 xx FETCH ------------------> <----------------- DISPLAY TEXT (Help info to item mn) TERMINAL RESPONSE (OK) ------------------> <----------------- 91 xx FETCH ------------------> <----------------- Repetition of SELECT ITEM (Item list under item m, help available) ... <----------------- 91xx FETCH ------------------> <----------------- GET INPUT TERMINAL RESPONSE (Help info required) ------------------> <----------------- 91 xx FETCH ------------------> <----------------- DISPLAY TEXT (Help info) TERMINAL RESPONSE (OK) ------------------> <----------------- 91 xx FETCH ------------------> <----------------- Repetition of GET INPUT TERMINAL RESPONSE (OK) ------------------> ... ... ETSI TS 101 267 V6.3.0 (1999-05) 64 (GSM 11.14 version 6.3.0 Release 1997) Annex G (informative): Change history This annex lists all change requests approved for the present document since the first phase2+ version was approved by ETSI SMG. SMG# SMG tdoc SMG9 tdoc VERS CR RV PH CAT SUBJECT Resulting Version s18 263/96 2.0.0 R96 Final draft version of GSM 11.14 approved 5.0.0 s19 515/96 134/96 5.0.0 A001 2 R96 B Enhancement of call control (refresh command) 5.1.0 s20 580/96 206/96 5.1.0 A002 R96 B Barred Dialling Numbers 5.2.0 703/96 208/96 A003 R96 B Enhancement of REFRESH command 703/96 208/96 A004 R96 C Enhancement to the command DISPLAY TEXT 703/96 208/96 A006 R96 B Enhancement to the SIM Application Toolkit s21 102/97 087/97 5.2.0 A007 1 R96 B Ending of proactive session. 5.3.0 102/97 063/97 A008 R96 D Example of Proactive SIM Command 102/97 049/97 A009 R96 D Editorial clarifications to Text s22 357/97 151/97 5.3.0 A010 R96 F General Result values : interpretation 5.4.0 357/97 171/97 A011 1 R96 D Clarifications to the DISPLAY TEXT command 357/97 176/97 A012 1 R96 D Length indicator clarification of some simple TLV data obj. 357/97 172/97 A014 1 R96 D Clarification of ME & SIM toolkit actions during REFRESH 357/97 178/97 A015 1 R96 F Set Up Menu command without Item Data Object 357/97 169/97 A016 R96 F Call control, corrections and editorial clarifications 357/97 170/97 A017 R96 C Call Control : call set-up,SS and USSD operation 357/97 190/97 A018 R96 F Call control,USSD operations s23 789/97 284/97 5.4.0 A020 1 R97 B Help information facility 5.5.0 789/97 257/97 A021 R96 F Corrections to Annex D 789/97 263/97 A022 R96 F Response data following an ENVELOPE command 789/97 280/97 A023 1 R96 F Length of resp. data after SMS-PP ENVELOPE command 789/97 265/97 A024 R96 F Clarification of the TP-Message Ref incrementation 789/97 266/97 A025 R96 F Correction of the use of the Comprehension Required flag 789/97 267/97 A026 R96 F DCS byte coding for send short message command 789/97 292/97 A027 R96 F Concerning Annex C 789/97 274/97 A028 R96 F Clarification of POLLING OFF command 789/97 275/97 A029 R96 F Interaction between SIM toolkit and emergency calls 789/97 269/97 A030 R96 F removal of setup menu 789/97 278/97 A031 R96 F Clarification of result retry 789/97 251/97 A032 R96 F Coding of simple TLV data objects 789/97 237/97 A033 R96 F Interaction between proactive commands and FDN 789/97 254/97 A034 R96 F Toolkit and ME display interaction 789/97 279/97 A035 R96 F Poll interval 789/97 240/97 A036 R96 F Clarifications to to REFRESH command. 789/97 282/97 A037 1 R96 F Clarification of length and removal of padding 789/97 289/97 A038 1 R96 F Correction to display text 789/97 290/97 A040 1 R96 F Terminal response without command details 789/97 288/97 A041 R96 F Number of possible ongoing proactive commands 789/97 291/97 A042 R96 F Provide Local Information 789/97 276/97 A043 R96 F Interaction with Last Number Dialled s24 97-1124 97/362 5.5.0 A044 R96 F high priority of DISPLAY TEXT 5.6.0 97-0886 97/363 a045 R97 B new type of DISPLAY TEXT and SET UP CALL 97-0886 97/373 a047 1 R97 D Extension of the Annex on help information feature. 97-0886 97/367 a048 R97 C Enhancement to PROVIDE LOCAL INFORMATION 97-0886 97/370 a049 R96 F GET INPUT - Hidden text 97-0886 97/375 a050 R97 B Default choice possibility for Get Input 97-0886 97/382 a051 2 R97 B Improvement of the dialogue with the user 97-0886 97/352 a052 R97 C cell identity available in call control by SIM 97-0886 97/377 a053 R96 F Profile download 97-0886 97/380 a054 R97 B send USSD 97-0886 97/381 a055 R97 B MO SMS control by SIM (continued) ETSI TS 101 267 V6.3.0 (1999-05) 65 (GSM 11.14 version 6.3.0 Release 1997) Change history (concluded) SMG# SMG tdoc SMG9 tdoc VERS CR RV PH CAT SUBJECT Resulting Version NOTE: At SMG #25, it was decided to create a version 6.0.0 of every specification that contained at least one release '97 workitem. Thus release 97 CRs approved at or after SMG #25 will only be found in the version 6.x.y of the present document. s25 98-0158 98p092 5.6.0 A046 1 R96 F Proactive Commands versus possible Terminal Response 6.0.0 98-0158 98p068 A056 R97 C Indications to be given to the user 98-0158 98p071 A057 R96 F Length of text string TLVs 98-0158 98p058 A058 R96 F Corrections to Command results 98-0158 98p076 A059 R97 F MO SM control by SIM 98-0158 98p081 A060 1 R97 B Previously selected item indication 98-0158 98p096 A061 1 R97 B Event driven information 98-0158 98p106 A062 1 R97 B Addition of UCS2 alphabet in the proactive commands 98-0158 98p098 A063 1 R96 F PLAY TONE - addition of user abort while tone is playing 98-0158 98p097 A064 R97 C Addition of warning of incompleteness of class 3 s26 98-0399 98p211 6.0.0 A067 R97 F Network not supporting / allowing call hold during the SET UP CALL 6.1.0 98-0399 98p213 A069 R97 F Correction to unknown tag value 98-0399 98p214 A070 R97 F Item Identifier in TERMINAL RESPONSE to SELECT ITEM 98-0399 98p216 A072 R97 F Correction to PLAY TONE 98-0399 98p217 A073 R97 F Network measurment results 98-0399 98p219 A075 R97 F Missing response code 98-0399 98p242 A076 1 R97 F SIM Toolkit Class Handling 98-0399 98p222 A077 R97 F Addition of reference to GSM 03.48 98-0399 98p249 A082 R97 F RP-ACK RP-ERROR for SIM data download error 98-0399 98p256 A089 1 R97 F clarification to FETCH command s27 98-0669 98p253 6.1.0 A087 R97 B Introduction of a 1bis SIM toolkit class 6.2.0 98-0670 98p344 A093 R97 F Additional information field mandatory in case of USSD Return Error result. 98-0670 98p346 A095 R97 F Possible result values for SET UP EVENT LIST command 98-0670 98p356 A097 R97 A Clarification regarding the ME changing the contents of SIM commands e.g. SEND SMS 98-0670 98p362 A099 R97 F Clarification about USSD return result 98-0670 98p375 A101 R97 F Clarification of the ’93 00’ status response handling 98-0670 98p370 A109 R97 F Interaction between call control by SIM / MO short message control and proactive commands s28 P-99-185 98p431 6.2.0 A113 R97 F Clarification about USSD Return Result parameters in Terminal Response 6.3.0 P-99-185 9-P-99077 A118 R97 F Clarification to PROVIDE LOCAL INFO (NMR for multiband) P-99-185 9-P-99059 A119 R97 F Configuration parameters P-99-185 9-P-99084 A125 R97 D Clarification to PROVIDE LOCAL INFO (NMR in idle mode) P-99-185 9-P-98438 A130 R97 F Correction of reply to SEND USSD (Note: this CR conflicts with A133, which removes the SEND USSD command and was therefore not implemented) P-99-188 A131 R97 D Deletion of $(......)$ release markers P-99-188 A133 R97 D Deletion of references to class 1 and deletion of class 3 related material. ETSI TS 101 267 V6.3.0 (1999-05) 66 (GSM 11.14 version 6.3.0 Release 1997) History Document history V6.0.0 April 1998 Publication V6.1.0 July 1998 Publication V6.2.0 November 1998 Publication V6.3.0 May 1999 Publication ISBN 2-7437-3099-4 Dépôt légal : Mai 1999
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
1 Scope
|
The present document defines an intermediate universal Geographical Area Description which subscriber applications or GSM services can use and the network can convert into an equivalent radio coverage map. For GSM services which involve the use of an "area", it can be assumed that in the majority of cases the Service Requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the Service Requester will not have direct access to network entities (e.g. BSC/BTS). The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly within the given area and all other technical and quality of service aspects are out of the scope of the present document.
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
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.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3 General aspects". [3] Military Standard WGS84 Metric MIL-STD-2401 (11 January 1994): "Military Standard Department of Defence World Geodetic System (WGS)".
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
3 Definitions and abbreviations
| |
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
3.1 Definitions
|
For the purposes of the present document, the following definitions apply: Service Requester: Entity, which uses the Geographical Area Description in any protocol to inform the network about a defined area
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
3.2 Abbreviations
|
In addition to those mentioned below, abbreviations used in the present document are listed in GSM 01.04. For the purposes of the present document, the following abbreviations apply: GAD Geographical Area Description GPS Global Positioning System WGS World Geodetic System ETSI TS 101 109 V6.0.0 (1999-04) 6 (GSM 03.32 version 6.0.0 Release 1997)
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
4 Reference system
|
The reference system chosen for the coding of locations is the World Geodetic System 1984, (WGS 84), which is also used by the Global Positioning System, (GPS). The origin of the WGS 84 co-ordinate system is the geometric centre of the WGS 84 ellipsoid. The ellipsoid is constructed by the rotation of an ellipse around the minor axis which is oriented in the North-South direction. The rotation axis is the polar axis of the ellipsoid, and the plane orthogonal to it and including the centre of symmetry is the equatorial plane. The relevant dimensions are as follows: Major Axis (a) = 6378137 m Minor Axis (b) = 6356752,314 m First eccentricity of the ellipsoid = − = 2 a 2 b 2 b 0,0066943800668 Co-ordinates are then expressed in terms of longitude and latitude relevant to this ellipsoid. The range of longitude is -180° to +180°, and the range of latitude is -90° to +90°. 0° longitude corresponds to the Greenwich Meridian, and positive angles are to the East, while negative angles are to the West. 0° latitude corresponds to the equator, and positive angles are to the North, while negative angles are to the South. Altitudes are defined as the distance between the ellipsoid and the point, along a line orthogonal to the ellipsoid.
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
5 Shapes
|
The intention is to incorporate a number of different shapes, that can be chosen according to need. In this version only a minimum number of shapes are described. - Ellipsoid Point; - Ellipsoid point with uncertainty circle; - Polygon. Each shape is discussed individually.
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
5.1 Ellipsoid Point
|
The description of an ellipsoid point is that of a point on the surface of the ellipsoid, and consists of a latitude and a longitude. In practice, such a description can be used to refer to a point on Earth’s surface, or close to Earth’s surface, with the same longitude and latitude. No provision is made in this version of the standard to give the height of a point. Figure 1 illustrates a point on the surface of the ellipsoid and its co-ordinates. The latitude is the angle between the equatorial plane and the perpendicular to the plane tangent to the ellipsoid surface at the point. Positive latitudes correspond to the North hemisphere. The longitude is the angle between the half-plane determined by the Greenwich meridian and the half-plane defined by the point and the polar axis, measured Eastward. ETSI TS 101 109 V6.0.0 (1999-04) 7 (GSM 03.32 version 6.0.0 Release 1997) Figure 1: Description of a Point as two co-ordinates
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
5.2 Ellipsoid point with uncertainty circle
|
The "ellipsoid point with uncertainty circle" is characterised by the co-ordinates of an ellipsoid point (the origin) and a distance r. It describes formally the set of points on the ellipsoid which are at a distance from the origin less than or equal to r, the distance being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points, as shown in figure 2. As for the ellipsoid point, this can be used to indicate points on the Earth surface, or near the Earth surface, of same latitude and longitude. The typical use of this shape is to indicate a point when its position is known only with a limited accuracy. Figure 2: Description of an uncertainty Circle ETSI TS 101 109 V6.0.0 (1999-04) 8 (GSM 03.32 version 6.0.0 Release 1997)
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
5.3 Polygon
|
A polygon is an arbitrary shape described by an ordered series of points (in the example pictured in the drawing, A to E). The minimum number of points allowed is 3, and the maximum number of points allowed is 15. The points shall be connected in the order that they are given. A connecting line is defined as the line over the ellipsoid joining the two points and of minimum distance (geodesic). The last point is connected to the first. The list of points must respect a number of conditions: - a connecting line shall not cross another connecting line; - two successive points must not be diametrically opposed on the ellipsoid. The described area is situated to the right of the lines with the downward direction being toward the Earth’s centre and the forward direction being from a point to the next. NOTE: This definition does not permit connecting lines greater than roughly 20 000 km. If such a need arises, the polygon can be described by adding an intermediate point. Computation of geodesic lines is not simple. Approximations leading to a maximum distance between the computed line and the geodesic line of less than 3 metres are acceptable. A B C D E Figure 3: Description of a Polygon
|
1c4b4f087015eb6e69461ecdbc9d8f65
|
101 109
|
6 Coding
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.