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