hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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... |
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... |
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... |
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 t... |
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 inc... |
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 ne... |
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 (... |
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 no... |
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 0... |
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 t... |
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 is... |
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 separ... |
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 u... |
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 generat... |
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 la... |
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 ... |
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... |
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 ... |
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 dat... |
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 speci... |
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 ... |
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 com... |
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... |
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, ... |
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 unkno... |
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 receive... |
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 o... |
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 wheth... |
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 require... |
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 re... |
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 ... |
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 devi... |
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 co... |
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:... |
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 Rele... |
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 t... |
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... |
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 ... |
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 ... |
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, ... |
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... |
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 fro... |
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 part... |
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 v... |
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. S... |
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 ... |
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... |
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 th... |
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 hel... |
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... |
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 identif... |
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 ... |
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 pe... |
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... |
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 i... |
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 suppo... |
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... |
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 G... |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.20 IMEI | Byte(s) Description Length 1 IMEI tag 1 2 Length = ‘08’ 1 3 - 10 IMEI of the ME 8 The IMEI is coded as in GSM 04.08 [8]. |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.21 Help Request | Byte(s) Description Length 1 Help Request tag 1 2 Length = ‘00’ 1 |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.22 Network Measurement Results | ETSI TS 101 267 V6.3.0 (1999-05) 53 (GSM 11.14 version 6.3.0 Release 1997) Byte(s) Description Length 1 Network Measurement Results tag 1 2 Length = '10' 1 3 - 18 Network Measurement Results 16 The Network Measurement Results are coded as for the Measurement Results information element in GSM 04.08 [8], starting at oct... |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.23 Default Text | The coding of this data object is the same as for the Text String data object (see subclause 12.15) with the exception that the Default Text tag has a specific value (see subclause 13.3). |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.24 Items Next Action Indicator | Byte(s) Description Length 1 Items Next Action Indicator tag 1 2 Length (X) 1 3 to 3+X-1 Items Next Action Indicator list X Contents : Each item of a list of items has a next action indicator coded on one byte. The length of the Items Next Action Indicator list shall be the number of items of the list of items (X shall... |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.25 Not Used | |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.26 Not used | |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.27 Not used | |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.28 Not used | ETSI TS 101 267 V6.3.0 (1999-05) 54 (GSM 11.14 version 6.3.0 Release 1997) |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.29 BCCH channel list | Byte(s) Description Length 1 BCCH channel list tag 1 2 Length (X) of bytes following 1 3 to X+2 BCCH channel list X - BCCH channel list Contents: the list of absolute RF channels for BCCH carriers, as known by the ME from the SYSTEM INFORMATION messages. The BCCH channel list is composed of one to three BCCH channel su... |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 12.30 Call control requested action | Byte(s) Description Length 1 Call control requested action tag 1 2 to (Y-1)+2 Length (X) Y (Y-1)+3 to (Y-1)+X+2 Call control requested action X - Call control requested action Contents: The action given in response to the ENVELOPE (CALL CONTROL). It may contain in the same order as given by the SIM, the address or SS s... |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 13 Tag values | This clause specifies the tag values used to identify the BER-TLV and SIMPLE-TLV data objects used in the present document. ETSI TS 101 267 V6.3.0 (1999-05) 55 (GSM 11.14 version 6.3.0 Release 1997) |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 13.1 BER-TLV tags in ME to SIM direction | Description Length of tag Value SMS-PP download tag 1 'D1' Cell Broadcast download tag 1 'D2' Menu Selection tag 1 'D3' Call control tag 1 'D4' |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 13.2 BER-TLV tags in SIM TO ME direction | Description Length of tag Value Proactive SIM command tag 1 'D0' |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 13.3 SIMPLE-TLV tags in both directions | 8 7 6 5 4 3 2 1 CR Tag value CR: Comprehension required for this object. Unless otherwise stated, for SIMPLE-TLV data objects it is the responsibility of the SIM application and the ME to decide the value of the CR flag for each data object in a given command. Handling of the CR flag at the receiving entity is describe... |
099e4bd0b61d814e89668f7c98053995 | 101 267 | 13.4 Type of Command and Next Action Indicator | The table below shows the values which shall be used for Type of Command coding (see subclause 12.6) and Next Action Indicator coding (see subclause 12.24). Value Name used for Type of Command coding used for Next Action Indicator coding ‘00’ - - ‘01’ REFRESH X ‘02’ MORE TIME X ‘03’ POLL INTERVAL X ‘04’ POLLING OFF X ‘... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.