hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.2 STATUS
|
COMMAND CLASS INS P1 P2 P3 STATUS 'A0' 'F2' '00' '00' lgth The response parameters/data are identical to the response parameters/data of the SELECT command in case of an MF or DF.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.3 READ BINARY
|
COMMAND CLASS INS P1 P2 P3 READ BINARY 'A0' 'B0' offset high offset low lgth ETSI ETSI TS 100 977 V6.3.0 (2000-05) 42 (GSM 11.11 version 6.3.0 Release 1997) Response parameters/data: Byte(s) Description Length 1 - lgth Data to be read lgth
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.4 UPDATE BINARY
|
COMMAND CLASS INS P1 P2 P3 UPDATE BINARY 'A0' 'D6' offset high offset low lgth Command parameters/data: Byte(s) Description Length 1 - lgth Data lgth
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.5 READ RECORD
|
COMMAND CLASS INS P1 P2 P3 READ RECORD 'A0' 'B2' Rec.No. Mode lgth Parameter P2 specifies the mode: - '02' = next record; - '03' = previous record; - '04' = absolute mode/current mode, the record number is given in P1 with P1='00' denoting the current record. For the modes "next" and "previous" P1 has no significance and shall be set to '00' by the ME. To ensure phase compatibility between Phase 2 SIMs and Phase 1 MEs, the SIM shall not interpret the value given by the ME. Response parameters/data: Byte(s) Description Length 1 - lgth The data of the record lgth
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.6 UPDATE RECORD
|
COMMAND CLASS INS P1 P2 P3 UPDATE RECORD 'A0' 'DC' Rec.No. Mode lgth Parameter P2 specifies the mode: - '02' = next record; - '03' = previous record; - '04' = absolute mode/current mode; the record number is given in P1 with P1='00' denoting the current record. For the modes "next" and "previous" P1 has no significance and shall be set to '00' by the ME. To ensure phase compatibility between Phase 2 SIMs and Phase 1 MEs, the SIM shall not interpret the value given by the ME. Command parameters/data: Byte(s) Description Length 1 - lgth Data lgth ETSI ETSI TS 100 977 V6.3.0 (2000-05) 43 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.7 SEEK
|
COMMAND CLASS INS P1 P2 P3 SEEK 'A0' 'A2' '00' Type/Mode lgth Parameter P2 specifies type and mode: - 'x0' = from the beginning forward; - 'x1' = from the end backward; - 'x2' = from the next location forward; - 'x3' = from the previous location backward; - with x='0' specifies type 1 and x='1' specifies type 2 of the SEEK command. Command parameters/data: Byte(s) Description Length 1 - lgth Pattern lgth There are no response parameters/data for a type 1 SEEK. A type 2 SEEK returns the following response parameters/data: Byte(s) Description Length 1 Record number 1
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.8 INCREASE
|
COMMAND CLASS INS P1 P2 P3 INCREASE 'A0' '32' '00' '00' '03' Command parameters/data: Byte(s) Description Length 1 - 3 Value to be added 3 Response parameters/data: Byte(s) Description Length 1 - X Value of the increased record X X+1 - X+3 Value which has been added 3 NOTE: X denotes the length of the record.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.9 VERIFY CHV
|
COMMAND CLASS INS P1 P2 P3 VERIFY CHV 'A0' '20' '00' CHV No. '08' Parameter P2 specifies the CHV: - '01' = CHV1; - '02' = CHV2. Command parameters/data: Byte(s) Description Length 1 - 8 CHV value 8 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 44 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.10 CHANGE CHV
|
COMMAND CLASS INS P1 P2 P3 CHANGE CHV 'A0' '24' '00' CHV No. '10' Parameter P2 specifies the CHV: - '01' = CHV1; - '02' = CHV2. Command parameters/data: Byte(s) Description Length 1 - 8 Old CHV value 8 9 - 16 New CHV value 8
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.11 DISABLE CHV
|
COMMAND CLASS INS P1 P2 P3 DISABLE CHV 'A0' '26' '00' '01' '08' Command parameters/data: Byte(s) Description Length 1 - 8 CHV1 value 8
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.12 ENABLE CHV
|
COMMAND CLASS INS P1 P2 P3 ENABLE CHV 'A0' '28' '00' '01' '08' Command parameters/data: Byte(s) Description Length 1 - 8 CHV1 value 8
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.13 UNBLOCK CHV
|
COMMAND CLASS INS P1 P2 P3 UNBLOCK CHV 'A0' '2C' '00' CHV No. '10' Parameter P2 specifies the CHV: - 00 = CHV1; - 02 = CHV2. NOTE: The coding '00' for CHV1 differs from the coding of CHV1 used for other commands. Command parameters/data: Byte(s) Description Length 1 - 8 UNBLOCK CHV value 8 9 - 16 New CHV value 8 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 45 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.14 INVALIDATE
|
COMMAND CLASS INS P1 P2 P3 INVALIDATE 'A0' '04' '00' '00' '00'
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.15 REHABILITATE
|
COMMAND CLASS INS P1 P2 P3 REHABILITATE 'A0' '44' '00' '00' '00'
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.16 RUN GSM ALGORITHM
|
COMMAND CLASS INS P1 P2 P3 RUN GSM ALGORITHM 'A0' '88' '00' '00' '10' Command parameters/data: Byte(s) Description Length 1 - 16 RAND 16 Response parameters/data: Byte(s) Description Length 1 - 4 SRES 4 5 - 12 Cipher Key Kc 8 The most significant bit of SRES is coded on bit 8 of byte 1. The most significant bit of Kc is coded on bit 8 of byte 5.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.17 SLEEP
|
COMMAND CLASS INS P1 P2 P3 SLEEP 'A0' 'FA' '00' '00' '00' NOTE: This command is used by Phase 1 MEs only.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.18 GET RESPONSE
|
COMMAND CLASS INS P1 P2 P3 GET RESPONSE 'A0' 'C0' '00' '00' lgth The response data depends on the preceding command. Response data is available after the commands RUN GSM ALGORITHM, SEEK (type 2), SELECT, INCREASE and ENVELOPE. If the command GET RESPONSE is executed, it is required that it is executed immediately after the command it is related to (no other command shall come between the command/response pair and the command GET RESPONSE). If the sequence is not respected, the SIM shall send the status information "technical problem with no diagnostic given" as a reaction to the GET RESPONSE. Since the MF is implicitly selected after activation of the SIM, GET RESPONSE is also allowed as the first command after activation. The response data itself is defined in the subclause for the corresponding command.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.19 TERMINAL PROFILE
|
COMMAND CLASS INS P1 P2 P3 TERMINAL PROFILE 'A0' '10' '00' '00' lgth ETSI ETSI TS 100 977 V6.3.0 (2000-05) 46 (GSM 11.11 version 6.3.0 Release 1997) Command parameters/data: length lgth. The structure of the command parameters is defined in GSM 11.14 [27]. Response parameters/data: none available
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.20 ENVELOPE
|
COMMAND CLASS INS P1 P2 P3 ENVELOPE 'A0' 'C2' '00' '00' lgth Command parameters/data: length lgth. The structure of the command parameters is defined in GSM 11.14 [27]. Response parameters/data: The structure of the data is defined in GSM 11.14 [27].
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.21 FETCH
|
COMMAND CLASS INS P1 P2 P3 FETCH 'A0' '12' '00' '00' lgth Command parameters/data: none. Response parameters/data: length lgth. The structure of the data is defined in GSM 11.14 [27].
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.2.22 TERMINAL RESPONSE
|
COMMAND CLASS INS P1 P2 P3 TERMINAL RESPONSE 'A0' '14' '00' '00' lgth Command parameters/data: length lgth. The structure of the command parameters is defined in GSM 11.14 [27]. Response parameters/data: none available.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.3 Definitions and coding
|
The following definitions and coding are used in the response parameters/data of the commands. Coding Each byte is represented by bits b8 to b1, where b8 is the most significant bit (MSB) and b1 is the least significant bit (LSB). In each representation the leftmost bit is the MSB. RFU In a GSM specific card all bytes which are RFU shall be set to '00' and RFU bits to 0. Where the GSM application exists on a multiapplication card or is built on a generic telecommunications card (e.g. TE9) then other values may apply. The ETSI ETSI TS 100 977 V6.3.0 (2000-05) 47 (GSM 11.11 version 6.3.0 Release 1997) values will be defined in the appropriate specifications for such cards. These bytes and bits shall not be interpreted by an ME in a GSM session. File status b8 b7 b6 b5 b4 b3 b2 b1 b1=0: invalidated; b1=1: not invalidated RFU b3=0: not readable or updatable when invalidated b3=1: readable and updatable when invalidated RFU Bit b3 may be set to 1 in special circumstances when it is required that the EF can be read and updated even if the EF is invalidated, e.g. reading and updating the EFADN when the FDN feature is enabled, or reading and updating the EFBDN when the BDN feature is disabled. Structure of file - '00'transparent; - '01'linear fixed; - '03'cyclic. Type of File - '00'RFU; - '01'MF; - '02'DF; - '04'EF. Coding of CHVs and UNBLOCK CHVs A CHV is coded on 8 bytes. Only (decimal) digits (0-9) shall be used, coded in CCITT T.50 [20] with bit 8 set to zero. The minimum number of digits is 4. If the number of digits presented by the user is less than 8 then the ME shall pad the presented CHV with 'FF' before sending it to the SIM. The coding of the UNBLOCK CHVs is identical to the coding of the CHVs. However, the number of (decimal) digits is always 8. Coding of Access Conditions The access conditions for the commands are coded on bytes 9, 10 and 11 of the response data of the SELECT command. Each condition is coded on 4 bits as shown in table 10. Table 10: Access conditions ALW '0' * CHV1 '1' * CHV2 '2' * RFU '3' ADM '4' ..... .. ADM 'E' NEW 'F' * Entries marked "*" in the table above, are also available for use as administrative codes in addition to the ADM access levels '4' to 'E' (refer to subclause 7.3) if required by the appropriate administrative authority. If any of these access conditions are used, the code returned in the Access Condition bytes in the response data shall be the code applicable to that particular level. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 48 (GSM 11.11 version 6.3.0 Release 1997) Byte 9: b8 b7 b6 b5 b4 b3 b2 b1 UPDATE READ; SEEK Byte 10: b8 b7 b6 b5 b4 b3 b2 b1 RFU INCREASE Byte 11: b8 b7 b6 b5 b4 b3 b2 b1 INVALIDATE REHABILITATE
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4 Status conditions returned by the card
|
This subclause specifies the coding of the status words SW1 and SW2.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.1 Responses to commands which are correctly executed
|
SW1 SW2 Description '90' '00' - normal ending of the command '91' 'XX' - normal ending of the command, with extra information from the proactive SIM containing a command for the ME. Length 'XX' of the response data '9E' 'XX' - length 'XX' of the response data given in case of a SIM data download error '9F' 'XX' - length 'XX' of the response data
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.2 Responses to commands which are postponed
|
SW1 SW2 Error description '93' '00' - SIM Application Toolkit is busy. Command cannot be executed at present, further normal commands are allowed.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.3 Memory management
|
SW1 SW2 Error description '92' '0X' - command successful but after using an internal update retry routine 'X' times '92' '40' - memory problem
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.4 Referencing management
|
SW1 SW2 Error description '94' '00' - no EF selected '94' '02' - out of range (invalid address) '94' '04' - file ID not found - pattern not found '94' '08' - file is inconsistent with the command ETSI ETSI TS 100 977 V6.3.0 (2000-05) 49 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.5 Security management
|
SW1 SW2 Error description '98' '02' - no CHV initialized '98' '04' - access condition not fulfilled - unsuccessful CHV verification, at least one attempt left - unsuccessful UNBLOCK CHV verification, at least one attempt left - authentication failed (see note) '98' '08' - in contradiction with CHV status '98' '10' - in contradiction with invalidation status '98' '40' - unsuccessful CHV verification, no attempt left - unsuccessful UNBLOCK CHV verification, no attempt left - CHV blocked - UNBLOCK CHV blocked '98' '50' - increase cannot be performed, Max value reached NOTE: A Phase 1 SIM may send this error code after the third consecutive unsuccessful CHV verification attempt or the tenth consecutive unsuccessful unblocking attempt.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.6 Application independent errors
|
SW1 SW2 Error description '67' 'XX' - incorrect parameter P3 (see note) '6B' 'XX'# - incorrect parameter P1 or P2 (see ##) '6D' 'XX'# - unknown instruction code given in the command '6E' 'XX'# - wrong instruction class given in the command '6F' 'XX'# - technical problem with no diagnostic given NOTE 1: # These values of 'XX' are specified by ISO/IEC; at present the default value 'XX'='00' is the only one defined. NOTE 2: ## When the error in P1 or P2 is caused by the addressed record being out of range, then the return code '94 02' shall be used. NOTE 3: 'XX' gives the correct length or states that no additional information is given ('XX' = '00').
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
9.4.7 Commands versus possible status responses
|
The following table shows for each command the possible status conditions returned (marked by an asterisk *). ETSI ETSI TS 100 977 V6.3.0 (2000-05) 50 (GSM 11.11 version 6.3.0 Release 1997) Table 11: Commands and status words OK B u s y Mem Sta Refer. Status Security Status Application Independent Errors Commands 9 0 0 0 9 1 X X 9 E X X 9 F X X 9 3 0 0 9 2 0 X 9 2 4 0 9 4 0 0 9 4 0 2 9 4 0 4 9 4 0 8 9 8 0 2 9 8 0 4 9 8 0 8 9 8 1 0 9 8 4 0 9 8 5 0 6 7 X X 6 B X X 6 D X X 6 E X X 6 F X X Select * * * * * * * Status * * * * * * * Update Binary * * * * * * * * * * * * Update Record * * * * * * * * * * * * * Read Binary * * * * * * * * * * * Read Record * * * * * * * * * * * * Seek * * * * * * * * * * * * Increase * * * * * * * * * * * * Verify CHV * * * * * * * * * * * * Change CHV * * * * * * * * * * * * Disable CHV * * * * * * * * * * * * Enable CHV * * * * * * * * * * * * Unblock CHV * * * * * * * * * * * * Invalidate * * * * * * * * * * * Rehabilitate * * * * * * * * * * * Run GSM Algorithm * * * * * * * * Sleep * * * * * Get Response * * * * * * * Terminal Profile * * * * * * * * Envelope * * * * * * * * * * * Fetch * * * * * * Terminal Response * * * * * * * * The responses '91 XX', '93 00' and '9E XX' can only be given by a SIM supporting SIM Application Toolkit, to an ME also supporting SIM Application Toolkit. For the SEEK command the response '91 XX' can be given directly after a Type 1 SEEK command. Following the Type 2 SEEK command the SIM can give the response '91 XX' only after the GET RESPONSE command.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10 Contents of the Elementary Files (EF)
|
This clause specifies the EFs for the GSM session defining access conditions, data items and coding. A data item is a part of an EF which represents a complete logical entity, e.g. the alpha tag in a EFADN record. EFs or data items having an unassigned value, or, which during the GSM session, are cleared by the ME, shall have their bytes set to 'FF'. After the administrative phase all data items shall have a defined value or have their bytes set to 'FF'. If a data item is 'deleted' during a GSM session by the allocation of a value specified in another GSM TS, then this value shall be used, and the data item is not unassigned; e.g. for a deleted LAI in EFLOCI the last byte takes the value 'FE' (GSM 04.08 [15] refers). EFs are mandatory (M) or optional (O). The file size of an optional EF may be zero. All implemented EFs with a file size greater than zero shall contain all mandatory data items. Optional data items may either be filled with 'F', or, if located at the end of an EF, need not exist. When the coding is according to CCITT Recommendation T.50 [20], bit 8 of every byte shall be set to 0. For an overview containing all files see figure 8. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 51 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.1 Contents of the EFs at the MF level
|
There are only two EFs at the MF level.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.1.1 EFICCID (ICC Identification)
|
This EF provides a unique identification number for the SIM. Identifier: '2FE2' Structure: transparent Mandatory File size: 10 bytes Update activity: low Access Conditions: READ ALWAYS UPDATE NEVER INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 10 Identification number M 10 bytes - Identification number Contents: - according to CCITT Recommendation E.118 [18]. However, network operators who are already issuing Phase 1 SIM cards with an identification number length of 20 digits may retain this length. Purpose: - card identification number. Coding: - BCD, left justified and padded with 'F'; after padding the digits within a byte are swapped (see below). However, network operators who are already issuing Phase 1 SIM cards where the digits within a byte are not swapped may retain this configuration. Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 1 : : MSB of Digit 1 LSB of Digit 2 : : MSB of Digit 2 Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 3 : : MSB of Digit 3 LSB of Digit 4 : : MSB of Digit 4 etc. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 52 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.1.2 EFELP (Extended language preference)
|
This EF contains the codes for up to n languages. This information, determined by the user/operator, defines the preferred languages of the user in order of priority. This information may be used by the ME for MMI purposes and for short message handling (e.g. screening of preferred languages in SMS-CB). When the CB Message Identifier capability is both allocated and activated the ME selects only those CB messages the language of which corresponds to one of the languages given in this EF or in EFLP, whichever of these EFs is used (see subclause 11.2.1). The CB message language is recognized according to GSM 03.38 by its data coding scheme. Identifier: '2F 05' Structure: transparent Optional File size: 2n bytes Update activity: low Access Conditions: READ ALW UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 2 1st language code (highest prior.) O 2 bytes 3 - 4 2nd language code O 2 bytes 2n-1 - 2n nth language code (lowest prior.) O 2 bytes Coding: - each language code is a pair of alpha-numeric characters, defined in ISO 639 [30]. Each alpha-numeric character shall be coded on one byte using the SMS default 7-bit coded alphabet as defined in GSM 03.38 [12] with bit 8 set to 0. Unused language entries shall be set to 'FF FF'.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.2 DFs at the GSM application level
|
For compatibility with other systems based on the GSM switching platform, DFs may be present as child directories of DFGSM. The following have been defined. DFIRIDIUM '5F30' DFGLOBALSTAR '5F31' DFICO '5F32' DFACeS '5F33' DFPCS1900 '5F40'
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3 Contents of files at the GSM application level
|
The EFs in the Dedicated File DFGSM contain network related information.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.1 EFLP (Language preference)
|
This EF contains the codes for one or more languages. This information, determined by the user/operator, defines the preferred languages of the user in order of priority. This information may be used by the ME for MMI purposes and for short message handling (e.g. screening of preferred languages in SMS-CB). When the CB Message Identifier capability is both allocated and activated the ME selects only those CB messages the language of which corresponds to one of the languages given in this EF or in EFELP, whichever of these EFs is used (see subclause 11.2.1). The CB message language is recognized according to GSM 03.41 by its data coding scheme. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 53 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F05' Structure: transparent Mandatory File size: 1-n bytes Update activity: low Access Conditions: READ ALW UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 1st language code (highest prior.) M 1 byte 2 2nd language code O 1 byte n nth language code (lowest prior.) O 1 byte Coding: according to GSM 03.41 [14]. Using the command GET RESPONSE, the ME can determine the size of the EF.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.2 EFIMSI (IMSI)
|
This EF contains the International Mobile Subscriber Identity (IMSI). Identifier: '6F07' Structure: transparent Mandatory File size: 9 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE CHV1 Bytes Description M/O Length 1 length of IMSI M 1 byte 2 - 9 IMSI M 8 bytes - length of IMSI Contents: - the length indicator refers to the number of significant bytes, not including this length byte, required for the IMSI. Coding: according to GSM 04.08 [15]. - IMSI Contents: - international Mobile Subscriber Identity. Coding: - this information element is of variable length. If a network operator chooses an IMSI of less than 15 digits, unused nibbles shall be set to 'F'. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 54 (GSM 11.11 version 6.3.0 Release 1997) Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 1 0 0 Parity LSB of Digit 1 : : MSB of Digit 1 For the parity bit, see GSM 04.08 [15]. Byte 3: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 2 : : MSB of Digit 2 LSB of Digit 3 : : MSB of Digit 3 etc.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.3 EFKc (Ciphering key Kc)
|
This EF contains the ciphering key Kc and the ciphering key sequence number n. Identifier: '6F20' Structure: transparent Mandatory File size: 9 bytes Update activity: high Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 8 Ciphering key Kc M 8 bytes 9 Ciphering key sequence number n M 1 byte - Ciphering key Kc Coding: - the least significant bit of Kc is the least significant bit of the eighth byte. The most significant bit of Kc is the most significant bit of the first byte. - Ciphering key sequence number n Coding: b8 b7 b6 b5 b4 b3 b2 b1 n bits b4 to b8 are coded 0 NOTE: GSM 04.08 [15] defines the value of n=111 as "key not available". Therefore the value '07' and not 'FF' should be present following the administrative phase. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 55 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.4 EFPLMNsel (PLMN selector)
|
This EF contains the coding for n PLMNs, where n is at least eight. This information determined by the user/operator defines the preferred PLMNs of the user in priority order. Identifier: '6F30' Structure: transparent Optional File size: 3n (n ≥8) bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 3 1st PLMN (highest priority) M 3 bytes 22 - 24 8th PLMN M 3 bytes 25 - 27 9th PLMN O 3 bytes (3n-2)-3n nth PLMN (lowest priority) O 3 bytes - PLMN Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: - according to GSM 04.08 [15]; - if storage for fewer than the maximum possible number n is required, the excess bytes shall be set to 'FF'; - for instance, using 246 for the MCC and 81 for the MNC and if this is the first and only PLMN, the contents reads as follows: - Bytes 1-3: '42' 'F6' '18'; - Bytes 4-6: 'FF' 'FF' 'FF'; - etc.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.5 EFHPLMN (HPLMN search period)
|
This EF contains the interval of time between searches for the HPLMN (see GSM 02.11 [5]). Identifier: '6F31' Structure: transparent Mandatory File size: 1 byte Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Time interval M 1 byte - Time interval Contents: - the time interval between two searches. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 56 (GSM 11.11 version 6.3.0 Release 1997) Coding: - the time interval is coded in integer multiples of n minutes. The range is from n minutes to a maximum value. The value '00' indicates that no attempts shall be made to search for the HPLMN. The encoding is: - '00': No HPLMN search attempts; - '01': n minutes; - '02': 2n minutes; - : : - 'YZ': (16Y+Z)n minutes (maximum value). - all other values shall be interpreted by the ME as a default period. For specification of the integer timer interval n, the maximum value and the default period refer to GSM 02.11 [5].
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.6 EFACMmax (ACM maximum value)
|
This EF contains the maximum value of the accumulated call meter. This EF shall always be allocated if EFACM is allocated. Identifier: '6F37' Structure: transparent Optional File size: 3 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1/CHV2 (fixed during administrative management) INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 3 Maximum value M 3 bytes - Maximum value Contents: - maximum value of the Accumulated Call Meter (ACM). Coding: First byte: b8 b7 b6 b5 b4 b3 b2 b1 223 222 221 220 219 218 217 216 Second byte: b8 b7 b6 b5 b4 b3 b2 b1 215 214 213 212 211 210 29 28 Third byte: b8 b7 b6 b5 b4 b3 b2 b1 27 26 25 24 23 22 21 20 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 57 (GSM 11.11 version 6.3.0 Release 1997) For instance, '00' '00' '30' represents 25+24. All ACM data is stored in the SIM and transmitted over the SIM/ME interface as binary. ACMmax is not valid, as defined in GSM 02.24 [7], if it is coded '000000'.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.7 EFSST (SIM service table)
|
This EF indicates which services are allocated, and whether, if allocated, the service is activated. If a service is not allocated or not activated in the SIM, the ME shall not select this service. Identifier: '6F38' Structure: transparent Mandatory File size: X bytes, X ≥2 Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Services n°1 to n°4 M 1 byte 2 Services n°5 to n°8 M 1 byte 3 Services n°9 to n°12 O 1 byte 4 Services n°13 to n°16 O 1 byte 5 Services n°17 to n°20 O 1 byte 6 Services n°21 to n°24 O 1 byte 7 Services n°25 to n°28 O 1 byte 8 Services n°29 to n°32 O 1 byte etc. X Services (4X-3) to (4X) O 1 byte ETSI ETSI TS 100 977 V6.3.0 (2000-05) 58 (GSM 11.11 version 6.3.0 Release 1997) -Services Contents: Service n°1 : CHV1 disable function Service n°2 : Abbreviated Dialling Numbers (ADN) Service n°3 : Fixed Dialling Numbers (FDN) Service n°4 : Short Message Storage (SMS) Service n°5 : Advice of Charge (AoC) Service n°6 : Capability Configuration Parameters (CCP) Service n°7 : PLMN selector Service n°8 : RFU Service n°9 : MSISDN Service n°10: Extension1 Service n°11: Extension2 Service n°12: SMS Parameters Service n°13: Last Number Dialled (LND) Service n°14: Cell Broadcast Message Identifier Service n°15: Group Identifier Level 1 Service n°16: Group Identifier Level 2 Service n°17: Service Provider Name Service n°18: Service Dialling Numbers (SDN) Service n°19: Extension3 Service n°20: RFU Service n°21: VGCS Group Identifier List (EFVGCS and EFVGCSS) Service n°22: VBS Group Identifier List (EFVBS and EFVBSS) Service n°23: enhanced Multi-Level Precedence and Pre-emption Service Service n°24: Automatic Answer for eMLPP Service n°25: Data download via SMS-CB Service n°26: Data download via SMS-PP Service n°27: Menu selection Service n°28: Call control Service n°29: Proactive SIM Service n°30: Cell Broadcast Message Identifier Ranges Service n°31: Barred Dialling Numbers (BDN) Service n°32: Extension4 Service n°33: De-personalization Control Keys Service n°34: Co-operative Network List Service n°35: Short Message Status Reports Service n°36 Network's indication of alerting in the MS Service n°37 Mobile Originated Short Message control by SIM Service n°38 GPRS For a phase 2 SIM, the EF shall contain at least two bytes which correspond to the Phase 1 services. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF. The coding falls under the responsibility of ETSI. NOTE 1: Service N°8 was used in Phase 1 for Called Party Subaddress. To prevent any risk of incompatibility Service N°8 should not be reallocated. NOTE 2: As the BDN service relies on the Call Control feature, service n°31 (BDN) should only be allocated and activated if service n°28 (Call control) is allocated and activated. Coding: 2 bits are used to code each service: first bit = 1: service allocated first bit = 0: service not allocated where the first bit is b1, b3, b5 or b7; second bit = 1: service activated second bit = 0: service not activated where the second bit is b2, b4, b6 or b8. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 59 (GSM 11.11 version 6.3.0 Release 1997) Service allocated means that the SIM has the capability to support the service. Service activated means that the service is available for the card holder (only valid if the service is allocated). The following codings are possible: - first bit = 0: service not allocated, second bit has no meaning; - first bit = 1 and second bit = 0: service allocated but not activated; - first bit = 1 and second bit = 1: service allocated and activated. The bits for services not yet defined shall be set to RFU. For coding of RFU see subclause 9.3. First byte: b8 b7 b6 b5 b4 b3 b2 b1 Service n°1 Service n°2 Service n°3 Service n°4 Second byte: b8 b7 b6 b5 b4 b3 b2 b1 Service n°5 Service n°6 Service n°7 Service n°8 etc. The following example of coding for the first byte means that service n°1 "CHV1-Disabling" is allocated but not activated: b8 b7 b6 b5 b4 b3 b2 b1 X X X X X X 0 1 If the SIM supports the FDN feature (FDN allocated and activated) a special mechanism shall exist in the SIM which invalidates both EFIMSI and EFLOCI once during each GSM session. This mechanism shall be invoked by the SIM automatically if FDN is enabled. This invalidation shall occur at least before the next command following selection of either EF. FDN is enabled when the ADN is invalidated or not activated. If the SIM supports the BDN feature (BDN allocated and activated) a special mechanism shall exist in the SIM which invalidates both EFIMSI and EFLOCI once during each GSM session and which forbids the REHABILITATE command to rehabilitate both EFIMSI and EFLOCI until the PROFILE DOWNLOAD procedure is performed indicating that the ME supports the "Call control by SIM" facility. This mechanism shall be invoked by the SIM automatically if BDN is enabled. The invalidation of EFIMSI and EFLOCI shall occur at least before the next command following selection of either EF. BDN is enabled when the EFBDN is not invalidated.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.8 EFACM (Accumulated call meter)
|
This EF contains the total number of units for both the current call and the preceding calls. NOTE: The information may be used to provide an indication to the user for advice or as a basis for the calculation of the monetary cost of calls (see GSM 02.86 [9]). ETSI ETSI TS 100 977 V6.3.0 (2000-05) 60 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F39' Structure: cyclic Optional Record length: 3 bytes Update activity: high Access Conditions: READ CHV1 UPDATE CHV1/CHV2 (fixed during administrative management) INCREASE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 3 Accumulated count of units M 3 bytes - Accumulated count of units Contents: value of the ACM Coding: see the coding of EFACMmax
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.3.9 EFGID1 (Group Identifier Level 1)
|
This EF contains identifiers for particular SIM-ME associations. It can be used to identify a group of SIMs for a particular application. Identifier: '6F3E' Structure: transparent Optional File size: 1-n bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - n SIM group identifier(s) O n bytes 10.3.10 EFGID2 (Group Identifier Level 2) This EF contains identifiers for particular SIM-ME associations. It can be used to identify a group of SIMs for a particular application. Identifier: '6F3F' Structure: transparent Optional File size: 1-n bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - n SIM group identifier(s) O n bytes NOTE: The structure of EFGID1 and EFGID2 are identical. They are provided to allow the network operator to enforce different levels of security dependant on application. 10.3.11 EFSPN (Service Provider Name) This EF contains the service provider name and appropriate requirements for the display by the ME. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 61 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F46' Structure: transparent Optional File Size: 17 bytes Update activity: low Access Conditions: READ ALWAYS UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Display Condition M 1 byte 2 - 17 Service Provider Name M 16 bytes - Display Condition Contents: display condition for the service provider name in respect to the registered PLMN (see GSM 02.07 [3]). Coding: see below Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 b1=0: display of registered PLMN not required b1=1: display of registered PLMN required RFU (see subclause 9.3) - Service Provider Name Contents: service provider string to be displayed Coding: the string shall use either: - the SMS default 7-bit coded alphabet as defined in GSM 03.38 [12] with bit 8 set to 0. The string shall be left justified. Unused bytes shall be set to 'FF'; - one of the UCS2 code options defined in annex B. 10.3.12 EFPUCT (Price per unit and currency table) This EF contains the Price per Unit and Currency Table (PUCT). The PUCT is Advice of Charge related information which may be used by the ME in conjunction with EFACM to compute the cost of calls in the currency chosen by the subscriber, as specified in GSM 02.24 [7]. This EF shall always be allocated if EFACM is allocated. Identifier: '6F41' Structure: transparent Optional File size: 5 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1/CHV2 (fixed during administrative management) INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 3 Currency code M 3 bytes 4 - 5 Price per unit M 2 bytes - Currency code Contents: the alpha-identifier of the currency code. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 62 (GSM 11.11 version 6.3.0 Release 1997) Coding: bytes 1, 2 and 3 are the respective first, second and third character of the alpha identifier. This alpha-tagging shall use the SMS default 7-bit coded alphabet as defined in GSM 03.38 [12] with bit 8 set to 0. - Price per unit Contents: price per unit expressed in the currency coded by bytes 1-3. Coding: Byte 4 and bits b1 to b4 of byte 5 represent the Elementary Price per Unit (EPPU) in the currency coded by bytes 1-3. Bits b5 to b8 of byte 5 are the decimal logarithm of the multiplicative factor represented by the absolute value of its decimal logarithm (EX) and the sign of EX, which is coded 0 for a positive sign and 1 for a negative sign. Byte 4: b8 b7 b6 b5 b4 b3 b2 b1 211 210 29 28 27 26 25 24 of EPPU Byte 5: b8 b7 b6 b5 b4 b3 b2 b1 23 22 21 20 of EPPU Sign of EX 20 of Abs(EX) 21 of Abs(EX) 22 of Abs(EX) The computation of the price per unit value is made by the ME in compliance with GSM 02.24 [7] by the following formula: price per unit = EPPU * 10EX. The price has to be understood as expressed in the coded currency. 10.3.13 EFCBMI (Cell broadcast message identifier selection) This EF contains the Message Identifier Parameters which specify the type of content of the cell broadcast messages that the subscriber wishes the MS to accept. Any number of CB Message Identifier Parameters may be stored in the SIM. No order of priority is applicable. Identifier: '6F45' Structure: transparent Optional File size: 2n bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 2 CB Message Identifier 1 O 2 bytes 3 - 4 CB Message Identifier 2 O 2 bytes 2n-1 - 2n CB Message Identifier n O 2 bytes ETSI ETSI TS 100 977 V6.3.0 (2000-05) 63 (GSM 11.11 version 6.3.0 Release 1997) - Cell Broadcast Message Identifier Coding: as in GSM 03.41, "Message Format on BTS-MS Interface - Message Identifier". Values listed show the types of message which shall be accepted by the MS. Unused entries shall be set to 'FF FF'. 10.3.14 EFBCCH (Broadcast control channels) This EF contains information concerning the BCCH according to GSM 04.08 [15]. BCCH storage may reduce the extent of a Mobile Station's search of BCCH carriers when selecting a cell. The BCCH carrier lists in an MS shall be in accordance with the procedures specified in GSM 04.08 [15]. The MS shall only store BCCH information from the System Information 2 message and not the 2bis extension message. Identifier: '6F74' Structure: transparent Mandatory File size: 16 bytes Update activity: high Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 16 BCCH information M 16 bytes - BCCH information Coding: The information is coded as octets 2-17 of the "neighbour cells description information element" in GSM 04.08 [15]. 10.3.15 EFACC (Access control class) This EF contains the assigned access control class(es). GSM 02.11 [5] refers. The access control class is a parameter to control the RACH utilization. 15 classes are split into 10 classes randomly allocated to normal subscribers and 5 classes allocated to specific high priority users. For more information see GSM 02.11 [5]. Identifier: '6F78' Structure: transparent Mandatory File size: 2 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 2 Access control classes M 2 bytes - Access control classes Coding: Each ACC is coded on one bit. An ACC is "allocated" if the corresponding bit is set to 1 and "not allocated" if this bit is set to 0. Bit b3 of byte 1 is set to 0. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 64 (GSM 11.11 version 6.3.0 Release 1997) Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 15 14 13 12 11 10 09 08 Number of the ACC (except for bit b3) Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 07 06 05 04 03 02 01 00 Number of the ACC 10.3.16 EFFPLMN (Forbidden PLMNs) This EF contains the coding for four Forbidden PLMNs (FPLMN). It is read by the ME as part of the SIM initialization procedure and indicates PLMNs which the MS shall not automatically attempt to access. A PLMN is written to the EF if a network rejects a Location Update with the cause "PLMN not allowed". The ME shall manage the list as follows. When four FPLMNs are held in the EF, and rejection of a further PLMN is received by the ME from the network, the ME shall modify the EF using the UPDATE command. This new PLMN shall be stored in the fourth position, and the existing list "shifted" causing the previous contents of the first position to be lost. When less than four FPLMNs exist in the EF, storage of an additional FPLMN shall not cause any existing FPLMN to be lost. Dependent upon procedures used to manage storage and deletion of FPLMNs in the EF, it is possible, when less than four FPLMNs exist in the EF, for 'FFFFFF' to occur in any position. The ME shall analyse all the EF for FPLMNs in any position, and not regard 'FFFFFF' as a termination of valid data. Identifier: '6F7B' Structure: transparent Mandatory File size: 12 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 3 PLMN 1 M 3 bytes 4 - 6 PLMN 2 M 3 bytes 7 - 9 PLMN 3 M 3 bytes 10 - 12 PLMN 4 M 3 bytes - PLMN Contents: Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: according to GSM 04.08 [15]. For instance, using 246 for the MCC and 81 for the MNC and if this is stored in PLMN 3 the contents is as follows: Bytes 7-9:'42' 'F6' '18' If storage for fewer than 4 PLMNs is required, the unused bytes shall be set to 'FF'. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 65 (GSM 11.11 version 6.3.0 Release 1997) 10.3.17 EFLOCI (Location information) This EF contains the following Location Information: - Temporary Mobile Subscriber Identity (TMSI); - Location Area Information (LAI); - TMSI TIME; - Location update status. Identifier: '6F7E' Structure: transparent Mandatory File size: 11 bytes Update activity: high Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE CHV1 Bytes Description M/O Length 1 - 4 TMSI M 4 bytes 5 - 9 LAI M 5 bytes 10 TMSI TIME M 1 byte 11 Location update status M 1 byte - TMSI Contents: Temporary Mobile Subscriber Identity Coding: according to GSM 04.08 [15]. Byte 1: first byte of TMSI b8 b7 b6 b5 b4 b3 b2 b1 MSB - LAI Contents: Location Area Information Coding: according to GSM 04.08 [15]. Byte 5: first byte of LAI (MCC) b8 b7 b6 b5 b4 b3 b2 b1 LSB of MCC Digit 1 : : MSB of MCC Digit 1 LSB of MCC Digit 2 : : MSB of MCC Digit 2 Byte 6: second byte of LAI (MCC continued) b8 b7 b6 b5 b4 b3 b2 b1 LSB of MCC Digit 3 : : MSB of MCC Digit 3 bits b5 to b8 are 1 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 66 (GSM 11.11 version 6.3.0 Release 1997) Byte 7: third byte of LAI (MNC) b8 b7 b6 b5 b4 b3 b2 b1 LSB of MNC Digit 1 : : MSB of MNC Digit 1 LSB of MNC Digit 2 : : MSB of MNC Digit 2 Byte 8: fourth byte of LAI (LAC) Byte 9: fifth byte of LAI (LAC continued) - TMSI TIME Contents: Current value of Periodic Location Updating Timer (T3212). This byte is used by Phase 1 MEs, but it shall not be used by Phase 2 MEs. - Location update status Contents: status of location update according to GSM 04.08 [15]. Coding: Byte 11: Bits: b3 b2 b1 0 0 0 : updated 0 0 1 : not updated 0 1 0 : PLMN not allowed 0 1 1 : Location Area not allowed 1 1 1 : reserved Bits b4 to b8 are RFU (see subclause 9.3). 10.3.18 EFAD (Administrative data) This EF contains information concerning the mode of operation according to the type of SIM, such as normal (to be used by PLMN subscribers for GSM operations), type approval (to allow specific use of the ME during type approval procedures of e.g. the radio equipment), cell testing (to allow testing of a cell before commercial use of this cell), manufacturer specific (to allow the ME manufacturer to perform specific proprietary auto-test in its ME during e.g. maintenance phases). It also provides an indication of whether some ME features should be activated during normal operation. Identifier: '6FAD' Structure: transparent Mandatory File size: 3+X bytes Update activity: low Access Conditions: READ ALW UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 MS operation mode M 1 byte 2 - 3 Additional information M 2 bytes 4 - 3+X RFU O X bytes - MS operation mode Contents: mode of operation for the MS ETSI ETSI TS 100 977 V6.3.0 (2000-05) 67 (GSM 11.11 version 6.3.0 Release 1997) Coding: Initial value - normal operation '00' - type approval operations '80' - normal operation + specific facilities '01' - type approval operations + specific facilities '81' - maintenance (off line) '02' - cell test operation '04' - Additional information Coding: - specific facilities (if b1=1 in byte 1); Byte 2 (first byte of additional information): b8 b7 b6 b5 b4 b3 b2 b1 RFU Byte 3: b8 b7 b6 b5 b4 b3 b2 b1 b1=0: OFM to be disabled by the ME b1=1: OFM to be activated by the ME RFU - ME manufacturer specific information (if b2=1 in byte 1). 10.3.19 EFPhase (Phase identification) This EF contains information concerning the phase of the SIM. Identifier: '6FAE' Structure: transparent Mandatory File size: 1 byte Update activity: low Access Conditions: READ ALW UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 SIM Phase M 1 byte - SIM Phase Coding: '00' : phase 1 '02' : phase 2 '03' : phase 2 and PROFILE DOWNLOAD required (see GSM 11.14 [27]). All other codings are reserved for specification by ETSI TC SMG. Codings '04' to '0F' indicate that the SIM supports, as a minimum, the mandatory requirements defined in this specification. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 68 (GSM 11.11 version 6.3.0 Release 1997) This phase identification does not preclude a SIM to support some features of a phase later than the one indicated in EFPhase. For example : if EFPhase is coded '00', it may be assumed by the ME that some Phase 2 or Phase 2+ features are supported by this SIM; if EFPhase is coded '02' or '03', it may be assumed by the ME that some Phase 2+ features are supported by this SIM. However, the services n°3 (FDN) and/or n°5 (AoC) shall only be allocated and activated in SIMs of phase 2 or later with EFPhase being coded '02' or greater. Similarly, service n°31 (BDN) shall only be allocated and activated in SIMs with EFPhase being coded '03' or greater. If EFPhase is coded '03' or greater, an ME supporting SIM Application Toolkit shall perform the PROFILE DOWNLOAD procedure, as defined in GSM 11.14 [27]. 10.3.20 EFVGCS (Voice Group Call Service) This EF contains a list of those VGCS group identifiers the user has subscribed to. The elementary file is used by the ME for group call establishment and group call reception. Identifier: '6FB1' Structure: transparent Optional File size: 4n bytes (n <= 50) Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 4 Group ID 1 M 4 bytes 5 - 8 Group ID 2 O 4 bytes : : : : (4n-3)-4n Group ID n O 4 bytes - Group ID Contents: VGCS Group ID, according to GSM 03.03 [10] Coding: The VGCS Group ID is of a variable length with a maximum length of 8 digits. Each VGCS Group ID is coded on four bytes, with each digit within the code being coded on four bits corresponding to BCD code. If a VGCS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to 'F'. VGCS Group ID Digit 1 is the most significant digit of the Group ID. Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 1 of Group ID 1 : : MSB of Digit 1 of Group ID 1 LSB of Digit 2 of Group ID 1 : : MSB of Digit 2 of Group ID 1 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 69 (GSM 11.11 version 6.3.0 Release 1997) Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 3 of Group ID 1 : : MSB of Digit 3 of Group ID 1 LSB of Digit 4 of Group ID 1 : : MSB of Digit 4 of Group ID 1 Byte 3: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 5 of Group ID 1 : : MSB of Digit 5 of Group ID 1 LSB of Digit 6 of Group ID 1 : : MSB of Digit 6 of Group ID 1 Byte 4: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 7 of Group ID 1 : : MSB of Digit 7 of Group ID 1 LSB of Digit 8 of Group ID 1 : : MSB of Digit 8 of Group ID 1 : : etc........ Byte (4n-3)-4n: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 7 of Group ID n : : MSB of Digit 7 of Group ID n LSB of Digit 8 of Group ID n : : MSB of Digit 8 of Group ID n If storage for fewer than the maximum possible number n of VGCS Group IDs, is required, the excess bytes shall be set to 'FF'. 10.3.21 EFVGCSS (Voice Group Call Service Status) This EF contains the status of activation for the VGCS group identifiers. The elementary file is directly related to the EFVGCS. This EF shall always be allocated if EFVGCS is allocated. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 70 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6FB2' Structure: transparent Optional File size: 7 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 7 Activation/Deactivation Flags M 7 bytes - Activation/Deactivation Flags Contents: Activation/Deactivation Flags of the appropriate Group IDs Coding: bit = 0 means - Group ID deactivated bit = 1 means - Group ID activated Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 Group ID 1 : : : : : : Group ID 8 etc : : : : : : : : Byte 7: b8 b7 b6 b5 b4 b3 b2 b1 Group ID 49 Group ID 50 1 1 1 1 1 1 10.3.22 EFVBS (Voice Broadcast Service) This EF contains a list of those VBS group identifiers the user has subscribed to. The elementary file is used by the ME for broadcast call establishment and broadcast call reception. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 71 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6FB3' Structure: transparent Optional File size: 4n bytes (n <= 50) Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 4 Group ID 1 M 4 bytes 5 - 2 Group ID 2 O 4 bytes : : : : (4n-3)-4n Group ID n O 4 bytes - Group ID Contents: VBS Group ID, according to GSM 03.03 [10] Coding: The VBS Group ID is of a variable length with a maximum length of 8 digits. Each VBS Group ID is coded on four bytes, with each digit within the code being coded on four bits corresponding to BCD code. If a VBS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to 'F'. VBS Group ID Digit 1 is the most significant digit of the Group ID. Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 1 of Group ID 1 : : MSB of Digit 1 of Group ID 1 LSB of Digit 2 of Group ID 1 : : MSB of Digit 2 of Group ID 1 Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 3 of Group ID 1 : : MSB of Digit 3 of Group ID 1 LSB of Digit 4 of Group ID 1 : : MSB of Digit 4 of Group ID 1 Byte 3: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 5 of Group ID 1 : : MSB of Digit 5 of Group ID 1 LSB of Digit 6 of Group ID 1 : : MSB of Digit 6 of Group ID 1 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 72 (GSM 11.11 version 6.3.0 Release 1997) Byte 4: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 7 of Group ID 1 : : MSB of Digit 7 of Group ID 1 LSB of Digit 8 of Group ID 1 : : MSB of Digit 8 of Group ID 1 : : etc........ Byte (4n-3)-4n: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 7 of Group ID n : : MSB of Digit 7 of Group ID n LSB of Digit 8 of Group ID n : : MSB of Digit 8 of Group ID n If storage for fewer than the maximum possible number n of VBS Group IDs is required, the excess bytes shall be set to 'FF'. 10.3.23 EFVBSS (Voice Broadcast Service Status) This EF contains the status of activation for the VBS group identifiers. The elementary file is directly related to the EFVBS. This EF shall always be allocated if EFVBS is allocated. Identifier: '6FB4' Structure: transparent Optional File size: 7 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 7 Activation/Deactivation Flags M 7 bytes - Activation/Deactivation Flags Contents: Activation/Deactivation Flags of the appropriate Group IDs Coding: see coding of EFVGCS 10.3.24 EFeMLPP (enhanced Multi Level Pre-emption and Priority) This EF contains information about priority levels and fast call set-up conditions for the enhanced Multi Level Pre- emption and Priority service that which can be used by the subscriber. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 73 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6FB5' Structure: transparent Optional File size: 2 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Priority levels M 1 byte 2 Fast call set-up conditions M 1 byte - Priority levels Contents: The eMLPP priority levels subscribed to. Coding: Each eMLPP priority level is coded on one bit. Priority levels subscribed to have their corresponding bits set to 1. Priority levels not subscribed to have their corresponding bits set to 0. Bit b8 is reserved and set to 0. Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 priority level A priority level B priority level 0 priority level 1 priority level 2 priority level 3 priority level 4 0 NOTE: Priority levels A and B can not be subscribed to (see 02.67 [33] for details). EXAMPLE 1: If priority levels 0, 1 and 2 are subscribed to, EFeMLPP shall be coded '1C'. - Fast call set-up conditions Contents: For each eMLPP priority level, the capability to use a fast call set-up procedure. Coding: Each eMLPP priority level is coded on one bit. Priority levels for which fast call set-up is allowed have their corresponding bits set to 1. Priority levels for which fast call set-up is not allowed have their corresponding bits set to 0. Bit b8 is reserved and set to 0. Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 fast call set-up condition for priority level A ` fast call set-up condition for priority level B fast call set-up condition for priority level 0 fast call set-up condition for priority level 1 fast call set-up condition for priority level 2 fast call set-up condition for priority level 3 fast call set-up condition for priority level 4 0 EXAMPLE 2: If fast call set-up is allowed for priority levels 0 and 1, then byte 2 of EFeMLPP is coded '0C'. 10.3.25 EFAAeM (Automatic Answer for eMLPP Service) This EF contains those priority levels (of the Multi Level Pre-emption and Priority service) for which the mobile station shall answer automatically to incoming calls. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 74 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6FB6' Structure: transparent Optional File size: 1 byte Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Automatic answer priority levels M 1 byte - Automatic answer priority levels Contents: For each eMLPP priority level, the capability for the mobile station to answer automatically to incoming calls (with the corresponding eMLPP priority level). Coding: Each eMLPP priority level is coded on one bit. Priority levels allowing an automatic answer from the mobile station have their corresponding bits set to 1. Priority levels not allowing an automatic answer from the mobile station have their corresponding bits set to 0. Bit b8 is reserved and set to 0. Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 Automatic answer priority for priority level A Automatic answer priority for priority level B Automatic answer priority for priority level 0 Automatic answer priority for priority level 1 Automatic answer priority for priority level 2 Automatic answer priority for priority level 3 Automatic answer priority for priority level 4 0 EXAMPLE: If automatic answer is allowed for incoming calls with priority levels A, 0 and 1, then EFAAeMLPP is coded '0D'. 10.3.26 EFCBMID (Cell Broadcast Message Identifier for Data Download) This EF contains the message identifier parameters which specify the type of content of the cell broadcast messages which are to be passed to the SIM. Any number of CB message identifier parameters may be stored in the SIM. No order of priority is applicable. Identifier: '6F48' Structure: transparent Optional File size: 2n bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1-2 CB Message Identifier 1 O 2 bytes 3-4 CB Message Identifier 2 O 2 bytes 2n-1-2n CB Message Identifier n O 2 bytes - Cell Broadcast Message Identifier ETSI ETSI TS 100 977 V6.3.0 (2000-05) 75 (GSM 11.11 version 6.3.0 Release 1997) Coding: as in GSM 03.41 [14]. Values listed show the identifiers of messages which shall be accepted by the MS to be passed to the SIM. Unused entries shall be set to 'FF FF'. 10.3.27 EFECC (Emergency Call Codes) This EF contains up to 5 emergency call codes. Identifier: '6FB7' Structure: transparent Optional File size: 3n (n ≤5) bytes Update activity: low Access Conditions: READ ALW UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 3 Emergency Call Code 1 O 3 bytes 4 - 6 Emergency Call Code 2 O 3 bytes (3n-2) - 3n Emergency Call Code n O 3 bytes - Emergency Call Code Contents: Emergency Call Code Coding: The emergency call code is of a variable length with a maximum length of 6 digits. Each emergency call code is coded on three bytes, with each digit within the code being coded on four bits as shown below. If a code of less that 6 digits is chosen, then the unused nibbles shall be set to 'F'. Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 1 : : MSB of Digit 1 LSB of Digit 2 : : MSB of Digit 2 Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 3 : : MSB of Digit 3 LSB of Digit 4 : : MSB of Digit 4 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 76 (GSM 11.11 version 6.3.0 Release 1997) Byte 3: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 5 : : MSB of Digit 5 LSB of Digit 6 : : MSB of Digit 6 10.3.28 EFCBMIR (Cell broadcast message identifier range selection) This EF contains ranges of cell broadcast message identifiers that the subscriber wishes the MS to accept. Any number of CB Message Identifier Parameter ranges may be stored in the SIM. No order of priority is applicable. Identifier: '6F50' Structure: transparent Optional File size: 4n bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 4 CB Message Identifier Range 1 O 4 bytes 5 - 8 CB Message Identifier Range 2 O 4 bytes (4n-3) - 4n CB Message Identifier Range n O 4 bytes - Cell Broadcast Message Identifier Ranges Contents: CB Message Identifier ranges: Coding: bytes one and two of each range identifier equal the lower value of a cell broadcast range, bytes three and four equal the upper value of a cell broadcast range, both values are coded as in GSM 03.41 [14] "Message Format on BTS-MS Interface - Message Identifier". Values listed show the ranges of messages which shall be accepted by the MS. Unused entries shall be set to 'FF FF FF FF'. 10.3.29 EFDCK De-personalization Control Keys This EF provides storage for the de-personalization control keys associated with the OTA de-personalization cycle of GSM 02.22. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 77 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F2C' Structure: transparent Optional File size: 16 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to 4 8 digits of network de-personalization control key M 4 bytes 5 to 8 8 digits of network subset de-personalization control key M 4 bytes 9 to 12 8 digits of service provider de-personalization control key M 4 bytes 13 to 16 8 digits of corporate de-personalization control key M 4 bytes Empty control key records shall be coded 'FFFFFFFF'. 10.3.30 EFCNL(Co-operative Network List) This EF contains the Co-operative Network List for the multiple network personalization services defined in GSM 02.22. Identifier: '6F32' Structure: transparent Optional File size: 6n bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to 6 Element 1 of co-operative net list O 6 bytes 6n-5 to 6n Element n of co-operative net list O 6 bytes - Co-operative Network List Contents: MCC, MNC, network subset, service provider ID and corporate ID of co-operative networks. Coding: For each 6 byte list element Byte 1: b8 b7 b6 b5 b4 b3 b2 b1 LS bit of MCC digit 1 : : MS bit of MCC digit 1 LS bit of MCC digit 2 : : MS bit of MCC digit 2 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 78 (GSM 11.11 version 6.3.0 Release 1997) Byte 2: b8 b7 b6 b5 b4 b3 b2 b1 LS bit of MCC digit 3 : : MS bit of MCC digit 3 LS bit of MNC digit 3 : : MS bit of MNC digit 3 Byte 3: b8 b7 b6 b5 b4 b3 b2 b1 LS bit of MNC digit 1 : : MS bit of MNC digit 1 LS bit of MNC digit 2 : : MS bit of MNC digit 2 Byte 4: b8 b7 b6 b5 b4 b3 b2 b1 LS bit of network subset digit 1 : : MS bit of network subset digit 1 LS bit of network subset digit 2 : : MS bit of network subset digit 2 NOTE: Digit 3 of the MNC is placed directly after the MCC fields for compatibility between GSM and PCS 1900 PLMN structures. Byte 5: b8 b7 b6 b5 b4 b3 b2 b1 LS bit of service provider digit 1 : : MS bit of service provider digit 1 LS bit of service provider digit 2 : : MS bit of service provider digit 2 Byte 6: b8 b7 b6 b5 b4 b3 b2 b1 LS bit of corporate digit 1 : : MS bit of corporate digit 1 LS bit of corporate digit 2 : : MS bit of corporate digit 2 For 2 digit MNCs digit 3 of this field shall be 'F'. For 1 digit network subsets digit 2 of this field shall be 0. Empty fields shall be coded with 'FF'. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 79 (GSM 11.11 version 6.3.0 Release 1997) The end of the list is delimited by the first MCC field coded 'FFF'. 10.3.31 EFNIA(Network's Indication of Alerting) This EF contains categories and associated text related to the Network's indication of alerting in the MS service defined in GSM 02.07 [3]. Identifier: '6F51' Structure: linear fixed Optional Record length : X+1 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Alerting category M 1 byte 2 to X+1 Informative text M X bytes - Alerting category Contents: category of alerting for terminating traffic. Coding: according to GSM 04.08 [15]. Value 'FF' means that no information on alerting category is available. - Informative text Contents: text describing the type of terminating traffic associated with the category. Coding: see the coding of the Alpha Identifier item of the EFADN (subclause 10.4.1). The maximum number of characters for this informative text is indicated in GSM 02.07 [3]. 10.3.32 EFKcGPRS (GPRS Ciphering key KcGPRS) This EF contains the ciphering key KcGPRS and the ciphering key sequence number n for GPRS (see GSM 03.60 [32]). Identifier: '6F52' Structure: transparent Mandatory File size: 9 bytes Update activity: high Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 8 Ciphering key KcGPRS M 8 bytes 9 Ciphering key sequence number n for GPRS M 1 byte - Ciphering key KcGPRS Coding: The least significant bit of KcGPRS is the least significant bit of the eighth byte. The most significant bit of KcGPRS is the most significant bit of the first byte. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 80 (GSM 11.11 version 6.3.0 Release 1997) - Ciphering key sequence number n for GPRS Coding: b8 b7 b6 b5 b4 b3 b2 b1 n bits b4 to b8 are coded 0 NOTE: GSM 04.08 [15] defines the value of n=111 as "key not available". Therefore the value '07' and not 'FF' should be present following the administrative phase. 10.3.33 EFLOCIGPRS (GPRS location information) This EF contains the following Location Information: - Packet Temporary Mobile Subscriber Identity (P-TMSI); - Packet Temporary Mobile Subscriber Identity signature value (P-TMSI signature value); - Routing Area Information (RAI); - Routing Area update status. Identifier: '6F53' Structure: transparent Mandatory File size: 14 bytes Update activity: high Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 - 4 P-TMSI M 4 bytes 5 – 7 P-TMSI signature value M 3 bytes 8 - 13 RAI M 6 bytes 14 Routing Area update status M 1 byte - P-TMSI Contents: Packet Temporary Mobile Subscriber Identity Coding: according to GSM 04.08 [15]. Byte 1: first byte of P-TMSI b8 b7 b6 b5 b4 b3 b2 b1 MSB - P-TMSI signature value Contents: Packet Temporary Mobile Subscriber Identity signature value Coding: according to GSM 04.08 [15]. Byte 5: first byte of P-TMSI signature value b8 b7 b6 b5 b4 b3 b2 b1 MSB - RAI ETSI ETSI TS 100 977 V6.3.0 (2000-05) 81 (GSM 11.11 version 6.3.0 Release 1997) Contents: Routing Area Information Coding: according to GSM 04.08 [15]. Byte 8: first byte of RAI b8 b7 b6 b5 b4 b3 b2 b1 LSB of MCC Digit 1 : : MSB of MCC Digit 1 LSB of MCC Digit 2 : : MSB of MCC Digit 2 Byte 9: second byte of RAI (MCC continued) b8 b7 b6 b5 b4 b3 b2 b1 LSB of MCC Digit 3 : : MSB of MCC Digit 3 bits b5 to b8 are 1 Byte 10: third byte of RAI (MNC) b8 b7 b6 b5 b4 b3 b2 b1 LSB of MNC Digit 1 : : MSB of MNC Digit 1 LSB of MNC Digit 2 : : MSB of MNC Digit 2 Byte 11: fourth byte of RAI (LAC) Byte 12: fifth byte of RAI (LAC continued) Byte 13: sixth byte of RAI (RAC) Routing Area update status Contents: status of routing area update according to GSM 04.08 [15]. Byte 14: Bits: b3 b2 b1 0 0 0 : updated 0 0 1 : not updated 0 1 0 : PLMN not allowed 0 1 1 : Routing Area not allowed 1 1 1 : reserved Bits b4 to b8 are RFU (see subclause 9.3).
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4 Contents of files at the telecom level
|
The EFs in the Dedicated File DFTELECOM contain service related information.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.1 EFADN (Abbreviated dialling numbers)
|
This EF contains Abbreviated Dialling Numbers (ADN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 82 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F3A' Structure: linear fixed Optional Record length: X+14 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE CHV2 REHABILITATE CHV2 Bytes Description M/O Length 1 to X Alpha Identifier O X bytes X+1 Length of BCD number/SSC contents M 1 byte X+2 TON and NPI M 1 byte X+3 to X+12 Dialling Number/SSC String M 10 bytes X+13 Capability/Configuration Identifier M 1 byte X+14 Extension1 Record Identifier M 1 byte - Alpha Identifier Contents: Alpha-tagging of the associated dialling number. Coding: this alpha-tagging shall use either: - the SMS default 7-bit coded alphabet as defined in GSM 03.38 [12] with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'; - one of the UCS2 coded options as defined in Annex B. NOTE 1: The value of X may be from zero to 241. Using the command GET RESPONSE the ME can determine the value of X. - Length of BCD number/SSC contents Contents: this byte gives the number of bytes of the following two data items containing actual BCD number/SSC information. This means that the maximum value is 11, even when the actual ADN/SSC information length is greater than 11. When an ADN/SSC has extension, it is indicated by the extension1 identifier being unequal to 'FF'. The remainder is stored in the EFEXT1 with the remaining length of the additional data being coded in the appropriate additional record itself (see subclause 10.4.10). Coding: according to GSM 04.08 [15]. - TON and NPI Contents: Type of number (TON) and numbering plan identification (NPI). Coding: according to GSM 04.08 [15]. If the Dialling Number/SSC String does not contain a dialling number, e.g. a control string deactivating a service, the TON/NPI byte shall be set to 'FF' by the ME (see note 2). NOTE 2: If a dialling number is absent, no TON/NPI byte is transmitted over the radio interface (see GSM 04.08 [15]). Accordingly, the ME should not interpret the value 'FF' and not send it over the radio interface. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 83 (GSM 11.11 version 6.3.0 Release 1997) b8 b7 b6 b5 b4 b3 b2 b1 NPI TON 1 - Dialling Number/SSC String Contents: up to 20 digits of the telephone number and/or SSC information. Coding: according to GSM 04.08 [15] , GSM 02.30 [8] and the extended BCD-coding (see table 12). If the telephone number or SSC is longer than 20 digits, the first 20 digits are stored in this data item and the remainder is stored in an associated record in the EFEXT1. The record is identified by the Extension1 Record Identifier. If ADN/SSC require less than 20 digits, excess nibbles at the end of the data item shall be set to 'F'. Where individual dialled numbers, in one or more records, of less than 20 digits share a common appended digit string the first digits are stored in this data item and the common digits stored in an associated record in the EFEXT1. The record is identified by the Extension 1 Record Identifier. Excess nibbles at the end of the data item shall be set to 'F'. Byte X+3 b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 1 : : MSB of Digit 1 LSB of Digit 2 : : MSB of Digit 2 Byte X+4: b8 b7 b6 b5 b4 b3 b2 b1 LSB of Digit 3 : : MSB of Digit 3 LSB of Digit 4 : : MSB of Digit 4 etc. - Capability/Configuration Identifier Contents: capability/configuration identification byte. This byte identifies the number of a record in the EFCCP containing associated capability/configuration parameters required for the call. The use of this byte is optional. If it is not used it shall be set to 'FF'. Coding: binary. - Extension1 Record Identifier Contents: extension1 record identification byte. This byte identifies the number of a record in the EFEXT1 containing an associated called party subaddress or additional data. The use of this byte is optional. If it is not used it shall be set to 'FF'. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 84 (GSM 11.11 version 6.3.0 Release 1997) If the ADN/SSC requires both additional data and called party subaddress, this byte identifies the additional record. A chaining mechanism inside EFEXT1 identifies the record of the appropriate called party subaddress (see subclause 10.4.10). Coding: binary. NOTE 3: As EFADN is part of the DFTELECOM it may be used by GSM and also other applications in a multi-application card. If the non-GSM application does not recognize the use of Type of Number (TON) and Number Plan Identification (NPI), then the information relating to the national dialling plan must be held within the data item dialling number/SSC and the TON and NPI fields set to UNKNOWN. This format would be acceptable for GSM operation and also for the non-GSM application where the TON and NPI fields shall be ignored. EXAMPLE: SIM storage of an International Number using E.164 [19] numbering plan. TON NPI Digit field GSM application 001 0001 abc... Other application compatible with GSM 000 0000 xxx...abc... where "abc..." denotes the subscriber number digits (including its country code), and "xxx..." denotes escape digits or a national prefix replacing TON and NPI. NOTE 4: When the ME acts upon the EFADN with a SEEK command in order to identify a character string in the alpha-identifier, it is the responsibility of the ME to ensure that the number of characters used as SEEK parameters are less than or equal to the value of X if the MMI allows the user to offer a greater number. Table 12: Extended BCD coding BCD Value Character/Meaning '0' "0" '9' "9" 'A' "*" 'B' "#" 'C' DTMF Control digit separator (GSM 02.07 [3]) 'D' "Wild" value This will cause the MMI to prompt the user for a single digit (see GSM 02.07 [3]). 'E' Expansion digit ("Shift Key"). It has the effect of adding '10' to the following digit. The following BCD digit will hence be interpreted in the range of '10'-'1E'. The purpose of digits in this range is for further study. 'F' Endmark e.g. in case of an odd number of digits BCD values 'C', 'D' and 'E' are never sent across the radio interface. NOTE 5: The interpretation of values 'D', 'E' and 'F' as DTMF digits is for further study. NOTE 6: A second or subsequent 'C' BCD value will be interpreted as a 3 second PAUSE (see GSM 02.07 [3]). ETSI ETSI TS 100 977 V6.3.0 (2000-05) 85 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.2 EFFDN (Fixed dialling numbers)
|
This EF contains Fixed Dialling Numbers (FDN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging. Identifier: '6F3B' Structure: linear fixed Optional Record length: X+14 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV2 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to X Alpha Identifier O X bytes X+1 Length of BCD number/SSC contents M 1 byte X+2 TON and NPI M 1 byte X+3 to X+12 Dialling Number/SSC String M 10 bytes X+13 Capability/Configuration Identifier M 1 byte X+14 Extension2 Record Identifier M 1 byte For contents and coding of all data items see the respective data items of the EFADN (subclause 10.4.1), with the exception that extension records are stored in the EFEXT2. NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.3 EFSMS (Short messages)
|
This EF contains information in accordance with GSM 03.40 [13] comprising short messages (and associated parameters) which have either been received by the MS from the network, or are to be used as an MS originated message. Identifier: '6F3C' Structure: linear fixed Optional Record length: 176 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Status M 1 byte 2 to 176 Remainder M 175 bytes - Status Contents: Status byte of the record which can be used as a pattern in the SEEK command. For MS originating messages sent to the network, the status shall be updated when the MS receives a status report, or sends a successful SMS Command relating to the status report. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 86 (GSM 11.11 version 6.3.0 Release 1997) Coding: b8 b7 b6 b5 b4 b3 b2 b1 X X 0 free space X X 1 used space 0 0 1 message received by MS from network; message read 0 1 1 message received by MS from network; message to be read 1 1 1 MS originating message; message to be sent RFU (see subclause 9.3) b8 b7 b6 b5 b4 b3 b2 b1 X X 1 0 1 MS originating message; message sent to the network: 0 0 1 0 1 status report not requested 0 1 1 0 1 status report requested but not (yet) received; 1 0 1 0 1 status report requested, received but not stored in EF-SMSR; 1 1 1 0 1 status report requested, received and stored in EF-SMSR; RFU (see subclause 9.3) - Remainder Contents: This data item commences with the TS-Service-Centre-Address as specified in GSM 04.11 [16]. The bytes immediately following the TS-Service-Centre-Address contain an appropriate short message TPDU as specified in GSM 03.40 [13], with identical coding and ordering of parameters. Coding: according to GSM 03.40 [13] and GSM 04.11 [16]. Any TP-message reference contained in an MS originated message stored in the SIM, shall have a value as follows: Value of the TP-message-reference: message to be sent: 'FF' message sent to the network: the value of TP-Message-Reference used in the message sent to the network. Any bytes in the record following the TPDU shall be filled with 'FF'. It is possible for a TS-Service-Centre-Address of maximum permitted length, e.g. containing more than 18 address digits, to be associated with a maximum length TPDU such that their combined length is 176 bytes. In this case the ME shall store in the SIM the TS-Service-Centre-Address and the TPDU in bytes 2-176 without modification, except for the last byte of the TPDU, which shall not be stored.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.4 EFCCP (Capability configuration parameters)
|
This EF contains parameters of required network and bearer capabilities and ME configurations associated with a call established using an abbreviated dialling number, a fixed dialling number, an MSISDN, a last number dialled, a service dialling number or a barred dialling number. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 87 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F3D' Structure: linear fixed Optional Record length: 14 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to 10 Bearer capability information element M 10 bytes 11 to 14 Bytes reserved - see below M 4 bytes - Bearer capability information element Contents and Coding: see GSM 04.08 [15]. The Information Element Identity (IEI) shall be excluded. i.e. the first byte of the EFCCP record shall be Length of the bearer capability contents. - Bytes 11-14 shall be set to 'FF' and shall not be interpreted by the ME.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.5 EFMSISDN (MSISDN)
|
This EF contains MSISDN(s) related to the subscriber. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging. Identifier: '6F40' Structure: linear fixed Optional Record length: X+14 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to X Alpha Identifier O X bytes X+1 Length of BCD number/SSC contents M 1 byte X+2 TON and NPI M 1 byte X+3 to X+12 Dialling Number/SSC String M 10 bytes X+13 Capability/Configuration Identifier M 1 byte X+14 Extension1 Record Identifier M 1 byte For contents and coding of all data items see the respective data items of EFADN. NOTE 1: If the SIM stores more than one MSISDN number and the ME displays the MSISDN number(s) within the initialization procedure then the one stored in the first record shall be displayed with priority. NOTE 2: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.6 EFSMSP (Short message service parameters)
|
This EF contains values for Short Message Service header Parameters (SMSP), which can be used by the ME for user assistance in preparation of mobile originated short messages. For example, a service centre address will often be common to many short messages sent by the subscriber. The EF consists of one or more records, with each record able to hold a set of SMS parameters. The first (or only) record in the EF shall be used as a default set of parameters, if no other record is selected. To distinguish between records, an alpha-identifier may be included within each record, coded on Y bytes. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 88 (GSM 11.11 version 6.3.0 Release 1997) The SMS parameters stored within a record may be present or absent independently. When a short message is to be sent from the MS, the parameter in the SIM record, if present, shall be used when a value is not supplied by the user. Identifier: '6F42' Structure: linear fixed Optional Record length: 28+Y bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to Y Alpha-Identifier O Y bytes Y+1 Parameter Indicators M 1 byte Y+2 to Y+13 TP-Destination Address M 12 bytes Y+14 to Y+25 TS-Service Centre Address M 12 bytes Y+26 TP-Protocol Identifier M 1 byte Y+27 TP-Data Coding Scheme M 1 byte Y+28 TP-Validity Period M 1 byte Storage is allocated for all of the possible SMS parameters, regardless of whether they are present or absent. Any bytes unused, due to parameters not requiring all of the bytes, or due to absent parameters, shall be set to 'FF'. - Alpha-Identifier Contents: Alpha Tag of the associated SMS-parameter. Coding: see subclause 10.4.1 (EFADN). NOTE: The value of Y may be zero, i.e. the alpha-identifier facility is not used. By using the command GET RESPONSE the ME can determine the value of Y. - Parameter Indicators Contents: Each of the default SMS parameters which can be stored in the remainder of the record are marked absent or present by individual bits within this byte. Coding: Allocation of bits: Bit number Parameter indicated 1 TP-Destination Address 2 TS-Service Centre Address 3 TP-Protocol Identifier 4 TP-Data Coding Scheme 5 TP-Validity Period 6 reserved, set to 1 7 reserved, set to 1 8 reserved, set to 1 ETSI ETSI TS 100 977 V6.3.0 (2000-05) 89 (GSM 11.11 version 6.3.0 Release 1997) Bit value Meaning 0 Parameter present 1 Parameter absent - TP-Destination Address Contents and Coding: As defined for SM-TL address fields in GSM 03.40 [13]. - TP-Service Centre Address Contents and Coding: As defined for RP-Destination address Centre Address in GSM 04.11 [16]. - TP-Protocol Identifier Contents and Coding: As defined in GSM 03.40 [13]. - TP-Data Coding Scheme Contents and Coding: As defined in GSM 03.38 [12]. - TP-Validity Period Contents and Coding: As defined in GSM 03.40 [13] for the relative time format.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.7 EFSMSS (SMS status)
|
This EF contains status information relating to the short message service. The provision of this EF is associated with EFSMS. Both files shall be present together, or both absent from the SIM. Identifier: '6F43' Structure: transparent Optional File size: 2+X bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Last Used TP-MR M 1 byte 2 SMS "Memory Cap. Exceeded" Not. Flag M 1 byte 3 to 2+X RFU O X bytes - Last Used TP-MR. Contents: the value of the TP-Message-Reference parameter in the last mobile originated short message, as defined in GSM 03.40 [13]. Coding: as defined in GSM 03.40 [13]. - SMS "Memory Capacity Exceeded" Notification Flag. Contents: This flag is required to allow a process of flow control, so that as memory capacity in the MS becomes available, the Network can be informed. The process for this is described in GSM 03.40 [13]. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 90 (GSM 11.11 version 6.3.0 Release 1997) Coding: b1=1 means flag unset; memory capacity available b1=0 means flag set b2 to b8 are reserved and set to 1.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.8 EFLND (Last number dialled)
|
This EF contains the last numbers dialled (LND) and/or the respective supplementary service control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain associated alpha-tagging. Identifier: '6F44' Structure: cyclic Optional Record length: X+14 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INCREASE NEVER INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 to X Alpha Identifier O X bytes X+1 Length of BCD number/SSC contents M 1 byte X+2 TON and NPI M 1 byte X+3 to X+12 Dialling Number/SSC String M 10 bytes X+13 Capability/Configuration Identifier M 1 byte X+14 Extension1 Record Identifier M 1 byte Contents and coding: see subclause 10.4.1 (EFADN). The value of X in EFLND may be different to both the value of X in EFADN and of X in EFFDN. If the value of X in EFLND is longer than the length of the α-tag of the number to be stored, then the ME shall pad the α-tag with 'FF'. If the value of X in EFLND is shorter than the length of the α-tag of the number to be stored, then the ME shall cut off excessive bytes.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.4.9 EFSDN (Service Dialling Numbers)
|
This EF contains special service numbers (SDN) and/or the respective supplementary service control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain associated alpha-tagging. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 91 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F49' Structure: linear fixed Optional Record length: X+14 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1-X Alpha identifier O X bytes X+1 Length of BCD number/SSC contents M 1 bytes X+2 TON and NPI M 1 byte X+3-X+12 Dialling Number/SSC String M 10 bytes X+13 Capability/Configuration Identifier M 1 byte X+14 Extension3 Record Identifier M 1 byte For contents and coding of all data items see the respective data items of the EFADN (subclause 10.4.1), with the exception that extension records are stored in the EFEXT3. NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN. 10.4.10 EFEXT1 (Extension1) This EF contains extension data of an ADN/SSC, an MSISDN, or an LND. Extension data is caused by: - an ADN/SSC (MSISDN, LND) which is greater than the 20 digit capacity of the ADN/SSC (MSISDN, LND) Elementary File or where common digits are required to follow an ADN/SSC string of less than 20 digits. The remainder is stored in this EF as a record, which is identified by a specified identification byte inside the ADN/SSC (MSISDN, LND) Elementary File. The EXT1 record in this case is specified as additional data; - an associated called party subaddress. The EXT1 record in this case is specified as subaddress data. Identifier: '6F4A' Structure: linear fixed Optional Record length: 13 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Record type M 1 byte 2 to 12 Extension data M 11 bytes 13 Identifier M 1 byte - Record type Contents: type of the record Coding: b8 b7 b6 b5 b4 b3 b2 b1 Called Party Subaddress Additional data RFU b3-b8 are reserved and set to 0; a bit set to 1 identifies the type of record; only one type can be set; '00' indicates the type "unknown". ETSI ETSI TS 100 977 V6.3.0 (2000-05) 92 (GSM 11.11 version 6.3.0 Release 1997) The following example of coding means that the type of extension data is "additional data": b8 b7 b6 b5 b4 b3 b2 b1 0 0 0 0 0 0 1 0 - Extension data Contents: Additional data or Called Party Subaddress depending on record type. Coding: Case 1, Extension1 record is additional data: The first byte of the extension data gives the number of bytes of the remainder of ADN/SSC (respectively MSISDN, LND). The coding of remaining bytes is BCD, according to the coding of ADN/SSC (MSISDN, LND). Unused nibbles at the end have to be set to 'F'. It is possible if the number of additional digits exceeds the capacity of the additional record to chain another record inside the EXT1 Elementary File by the identifier in byte 13. Case 2, Extension1 record is Called Party Subaddress: The subaddress data contains information as defined for this purpose in GSM 04.08 [15]. All information defined in GSM 04.08, except the information element identifier, shall be stored in the SIM. The length of this subaddress data can be up to 22 bytes. In those cases where two extension records are needed, these records are chained by the identifier field. The extension record containing the first part of the called party subaddress points to the record which contains the second part of the subaddress. - Identifier Contents: identifier of the next extension record to enable storage of information longer than 11 bytes. Coding: record number of next record. 'FF' identifies the end of the chain. EXAMPLE: Of a chain of extension records being associated to an ADN/SSC. The extension1 record identifier (Byte 14+X) of ADN/SSC is set to 3. No of Record : : Record 3 Record 4 Record 5 Record 6 : : Type : : ‘02’ ‘xx’ ‘01’ ‘01’ : : Extension Data : : xx ........xx xx ........xx xx ........xx xx ........xx : : Next : : ‘06’ ‘xx’ ‘FF’ ‘05’ : : Record In this example ADN/SSC is associated to additional data (record 3) and a called party subaddress whose length is more than 11 bytes (records 6 and 5). 10.4.11 EFEXT2 (Extension2) This EF contains extension data of an FDN/SSC (see EXT2 in 10.4.2). ETSI ETSI TS 100 977 V6.3.0 (2000-05) 93 (GSM 11.11 version 6.3.0 Release 1997) Identifier: '6F4B' Structure: linear fixed Optional Record length: 13 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV2 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Record type M 1 byte 2 to 12 Extension data M 11 bytes 13 Identifier M 1 byte For contents and coding see subclause 10.4.10 (EFEXT1). 10.4.12 EFEXT3 (Extension3) This EF contains extension data of an SDN (see EXT3 in subclause 10.4.9). Identifier: '6F4C' Structure: linear fixed Optional Record length: 13 bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Record type M 1 byte 2 to 12 Extension data M 11 bytes 13 Identifier M 1 byte For contents and coding see subclause 10.4.10 EFEXT1 . 10.4.13 EFBDN (Barred Dialling Numbers) This EF contains Barred Dialling Numbers (BDN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging. Identifier: '6F4D' Structure: linear fixed Optional Record length: X+15 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV2 INVALIDATE CHV2 REHABILITATE CHV2 Bytes Description M/O Length 1 to X Alpha Identifier O X bytes X+1 Length of BCD number/SSC contents M 1 byte X+2 TON and NPI M 1 byte X+3 to X+12 Dialling Number/SSC String M 10 bytes X+13 Capability/Configuration Identifier M 1 byte X+14 Extension4 Record Identifier M 1 byte X+15 Comparison Method Information M 1 byte For contents and coding of all data items, except for the Comparison Method Information, see the respective data items of the EFADN (subclause 10.4.1), with the exception that extension records are stored in the EFEXT4. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 94 (GSM 11.11 version 6.3.0 Release 1997) NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN. - Comparison Method Information Contents: this byte describes the comparison method which is associated with that BDN. Its interpretation is not specified but it shall be defined by the operators implementing the BDN feature on their SIMs. Coding: binary; values from 0 to 255 are allowed. 10.4.14 EFEXT4 (Extension4) This EF contains extension data of an BDN/SSC (see EXT4 in subclause 10.4.13). Identifier: '6F4E' Structure: linear fixed Optional Record length: 13 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV2 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 Record type M 1 byte 2 to 12 Extension data M 11 bytes 13 Identifier M 1 byte For contents and coding see subclause 10.4.10 EFEXT1 10.4.15 EFSMSR (Short message status reports) This EF contains information in accordance with GSM 03.40 [13] comprising short message status reports which have been received by the MS from the network. Each record is used to store the status report of a short message in a record of EFSMS. The first byte of each record is the link between the status report and the corresponding short message in EFSMS. Identifier: '6F47' Structure: linear fixed Optional Record length: 30 bytes Update activity: low Access Conditions: READ CHV1 UPDATE CHV1 INVALIDATE ADM REHABILITATE ADM Bytes Description M/O Length 1 SMS record identifier M 1 2 - 30 SMS status report M 29 bytes - SMS record identifier Contents: This data item identifies the corresponding SMS record in EFSMS, e.g. if this byte is coded '05' then this status report corresponds to the short message in record #5 of EFSMS. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 95 (GSM 11.11 version 6.3.0 Release 1997) Coding: '00' - empty record '01' - 'FF' - record number of the corresponding SMS in EFSMS. - SMS status report Contents: This data item contains the SMS-STATUS-REPORT TPDU as specified in GSM 03.40 [13], with identical coding and ordering of parameters. Coding: according to GSM 03.40 [13]. Any bytes in the record following the TPDU shall be filled with 'FF'.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
10.5 Files of GSM (figure 8)
|
This subclause contains a figure depicting the file structure of the SIM. DFGSM shall be selected using the identifier '7F20'. If selection by this means fails, then DCS 1800 MEs shall, and optionally GSM MEs may then select DFGSM with '7F21'. NOTE 1: The selection of the GSM application using the identifier '7F21', if selection by means of the identifier '7F20' fails, is to ensure backwards compatibility with those Phase 1 SIMs which only support the DCS 1800 application using the Phase 1 directory DFDCS1800 coded '7F21'. NOTE 2: To ensure backwards compatibility with those Phase 1 DCS 1800 MEs which have no means to select DFGSM two options have been specified. These options are given in GSM 09.91 [17]. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 96 (GSM 11.11 version 6.3.0 Release 1997) MF '3F00' DFGSM DFTELECOM DFIS-41 EFICCID EFELP '7F20' '7F10' '7F22' '2FE2' '2F05' s EFADN EFFDN EFSMS EFCCP EFMSISDN '6F3A' '6F3B' '6F3C' '6F3D' '6F40' EFSMSP EFSMSS EFLND EFSMSR EFSDN '6F42' '6F43' '6F44' '6F47' '6F49' EFEXT1 EFEXT2 EFEXT3 EFBDN EFEXT4 '6F4A' '6F4B' '6F4C' '6F4D' '6F4E' DFIRIDIUM DFGLOBST DFICO DFACeS '5F30' '5F31' '5F32' '5F33' DFPCS1900 '5F40' EFLP EFIMSI EFKc EFPLMNsel EFHPLMN EFACMmax '6F05' '6F07' '6F20' '6F30' '6F31' '6F37' EFSST EFACM EFGID1 EFGID2 EFPUCT EFCBMI '6F38' '6F39' '6F3E' '6F3F' '6F41' '6F45' EFSPN EFCBMID EFBCCH EFACC EFFPLMN EFLOCI '6F46' '6F48' '6F74' '6F78' '6F7B' '6F7E' EFAD EFPHASE EFVGCS EFVGCSS EFVBS EFVBSS '6FAD' '6FAE' '6FB1' '6FB2' '6FB3' '6FB4' EFeMLPP EFAAeM EFECC EFCBMIR EFNIA EFKcGPRS '6FB5' '6FB6' '6FB7' '6F50' '6F51' '6F52' EFLOCIGPRS '6F53' Figure 8: File identifiers and directory structures of GSM ETSI ETSI TS 100 977 V6.3.0 (2000-05) 97 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11 Application protocol
|
When involved in GSM administrative management operations, the SIM interfaces with appropriate terminal equipment. These operations are outside the scope of the present document. When involved in GSM network operations the SIM interfaces with an ME with which messages are exchanged. A message can be a command or a response. - A GSM command/response pair is a sequence consisting of a command and the associated response. - A GSM procedure consists of one or more GSM command/response pairs which are used to perform all or part of an application-oriented task. A procedure shall be considered as a whole, that is to say that the corresponding task is achieved if and only if the procedure is completed. The ME shall ensure that, when operated according to the manufacturer's manual, any unspecified interruption of the sequence of command/response pairs which realize the procedure, leads to the abortion of the procedure itself. - A GSM session of the SIM in the GSM application is the interval of time starting at the completion of the SIM initialization procedure and ending either with the start of the GSM session termination procedure, or at the first instant the link between the SIM and the ME is interrupted. During the GSM network operation phase, the ME plays the role of the master and the SIM plays the role of the slave. Some procedures at the SIM/ME interface require MMI interactions. The descriptions hereafter do not intend to infer any specific implementation of the corresponding MMI. When MMI interaction is required, it is marked "MMI" in the list given below. Some procedures are not clearly user dependent. They are directly caused by the interaction of the MS and the network. Such procedures are marked "NET" in the list given below. Some procedures are automatically initiated by the ME. They are marked "ME" in the list given below. The list of procedures at the SIM/ME interface in GSM network operation is as follows: General Procedures: - Reading an EF ME - Updating an EF ME - Increasing an EF ME SIM management procedures: - SIM initialization ME - GSM session termination ME - Emergency call codes request ME - Extended language preference request ME - Language preference request ME - Administrative information request ME - SIM service table request ME - SIM phase request ME CHV related procedures: - CHV verification MMI - CHV value substitution MMI - CHV disabling MMI - CHV enabling MMI - CHV unblocking MMI ETSI ETSI TS 100 977 V6.3.0 (2000-05) 98 (GSM 11.11 version 6.3.0 Release 1997) GSM security related procedures: - GSM algorithms computation NET - IMSI request NET - Access control information request NET - HPLMN search period request NET - Location Information NET - Cipher key NET - BCCH information NET - Forbidden PLMN information NET Subscription related procedures: - Dialling Numbers (ADN, FDN, MSISDN, LND, SDN, BDN) MMI/ME - Short messages (SMS) MMI - Advice of Charge (AoC) MMI - Capability Configuration Parameters (CCP) MMI - PLMN Selector MMI - Cell Broadcast Message Identifier (CBMI) MMI - Group Identifier Level 1 (GID1) MMI/ME - Group Identifier Level 2 (GID2) MMI/ME - Service Provider Name (SPN) ME - Voice Group Call Service (VGCS) MMI/ME - Voice Broadcast Service (VBS) MMI/ME - Enhanced Multi Level Pre-emption and Priority (eMLPP) MMI/ME - Depersonalisation Control Keys ME - Short message status reports (SMSR) MMI - Network's indication of alerting ME SIM Application Toolkit related procedures: - Data Download via SMS-CB (CBMID) NET - Data Download via SMS-PP NET - Menu selection MMI - Call Control MMI/ME/NET - Proactive SIM MMI/ME/NET - Mobile Originated Short Message control by SIM MMI/ME/NET The procedures listed in subclause 11.2 are basically required for execution of the procedures in subclauses 11.3, 11.4 and 11.5. The procedures listed in subclauses 11.3 and 11.4 are mandatory (see GSM 02.17 [6]). The procedures listed in subclause 11.5 are only executable if the associated services, which are optional, are provided in the SIM. However, if the procedures are implemented, it shall be in accordance with subclause 11.5. If a procedure is related to a specific service indicated in the SIM Service Table, it shall only be executed if the corresponding bits denote this service as "allocated and activated" (see subclause 10.3.7). In all other cases this procedure shall not start.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.1 General procedures
| |
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.1.1 Reading an EF
|
The ME selects the EF and sends a READ command. This contains the location of the data to be read. If the access condition for READ is fulfilled, the SIM sends the requested data contained in the EF to the ME. If the access condition is not fulfilled, no data will be sent and an error code will be returned. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 99 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.1.2 Updating an EF
|
The ME selects the EF and sends an UPDATE command. This contains the location of the data to be updated and the new data to be stored. If the access condition for UPDATE is fulfilled, the SIM updates the selected EF by replacing the existing data in the EF with that contained in the command. If the access condition is not fulfilled, the data existing in the EF will be unchanged, the new data will not be stored, and an error code will be returned.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.1.3 Increasing an EF
|
The ME selects the EF and sends an INCREASE command. This contains the value which has to be added to the contents of the last updated/increased record. If the access condition for INCREASE is fulfilled, the SIM increases the existing value of the EF by the data contained in the command, and stores the result. If the access condition is not fulfilled, the data existing in the EF will be unchanged and an error code will be returned. NOTE: The identification of the data within an EF to be acted upon by the above procedures is specified within the command. For the procedures in subclauses 11.1.1 and 11.1.2 this data may have been previously identified using a SEEK command, e.g. searching for an alphanumeric pattern.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2 SIM management procedures
|
Phase 2 MEs shall support all SIMs which comply with the mandatory requirements of Phase 1, even if these SIMs do not comply with all the mandatory requirements of Phase 2. Furthermore, Phase 2 MEs shall take care of potential incompatibilities with Phase 1 SIMs which could arise through use of inappropriate commands or misinterpretation of response data. Particular note should be taken of making a false interpretation of RFU bytes in a Phase 1 SIM having contradictory meaning in Phase 2; e.g. indication of EF invalidation state.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.1 SIM initialization
|
After SIM activation (see subclause 4.3.2), the ME selects the Dedicated File DFGSM and optionally attempts to select EFECC. If EFECC is available, the ME requests the emergency call codes. The ME requests the Extended Language Preference. The ME only requests the Language Preference (EFLP) if at least one of the following conditions holds: - EFELP is not available; - EFELP does not contain an entry corresponding to a language specified in ISO 639[30]; - the ME does not support any of the languages in EFELP. If both EFs are not available or none of the languages in the EFs is supported then the ME selects a default language. It then runs the CHV1 verification procedure. If the CHV1 verification procedure is performed successfully, the ME then runs the SIM Phase request procedure. For a SIM requiring PROFILE DOWNLOAD, then the ME shall perform the PROFILE DOWNLOAD procedure in accordance with GSM 11.14 [27]. When BDN is enabled on a SIM, the PROFILE DOWNLOAD procedure is used to indicate to the SIM whether the ME supports the "Call Control by SIM" facility. If so, then the SIM is able to allow the REHABILITATE command to rehabilitate EFIMSI and EFLOCI. If the ME detects a SIM of Phase 1, it shall omit the following procedures relating to FDN and continue with the Administrative Information request. The ME may omit procedures not defined in Phase 1 such as HPLMN Search Period request. For a SIM of Phase 2 or greater, GSM operation shall only start if one of the two following conditions is fulfilled: - if EFIMSI and EFLOCI are not invalidated, the GSM operation shall start immediately; - if EFIMSI and EFLOCI are invalidated, the ME rehabilitates these two EFs; ETSI ETSI TS 100 977 V6.3.0 (2000-05) 100 (GSM 11.11 version 6.3.0 Release 1997) - MEs without FDN capability but with Call control by SIM facility shall not rehabilitate EFIMSI and/or EFLOCI if FDN is enabled in the SIM and therefore have no access to these EFs. GSM operation will therefore be prohibited; - MEs without FDN capability and without Call control by SIM facility shall not rehabilitate EFIMSI and/or EFLOCI and therefore have no access to these EFs. GSM operation will therefore be prohibited; - It is these mechanisms which are used for control of services n°3 and n°31 by the use of SIMs for these services which always invalidate these two EFs at least before the next command following selection of either EF. NOTE: When FDN and BDN are both enabled, and if the ME supports FDN but does not support the Call control by SIM facility, the rehabilitation of EFIMSI and EFLOCI will not be successful because of a restriction mechanism of the REHABILITATE command linked to the BDN feature. When EFIMSI and EFLOCI are successfully rehabilitated, if the FDN capability procedure indicates that: i) FDN is allocated and activated in the SIM; and FDN is set "enabled", i.e. ADN "invalidated" or not activated; and the ME supports FDN; or ii) FDN is allocated and activated in the SIM; and FDN is set "disabled", i.e. ADN "not invalidated"; or iii) FDN is not allocated or not activated; then GSM operation shall start. In all other cases GSM operation shall not start. Afterwards, the ME runs the following procedures: - Administrative Information request; - SIM Service Table request; - IMSI request; - Access Control request; - HPLMN Search Period request; - PLMN selector request; - Location Information request; - Cipher Key request; - BCCH information request; - Forbidden PLMN request; - CBMID request; - Depersonalisation Control Keys request; - Network's indication of alerting request. If the SIM service table indicates that the proactive SIM service is active, then from this point onwards, the ME, if it supports the proactive SIM service, shall send STATUS commands at least every 30s during idle mode as well as during calls, in order to enable the proactive SIM to respond with a command. The SIM may send proactive commands (see GSM 11.14 [27]), including a command to change the interval between STATUS commands from the ME, when in idle mode. In-call requirements for STATUS for SIM Presence Detection are unchanged by this command. After the SIM initialization has been completed successfully, the MS is ready for a GSM session.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.2 GSM session termination
|
NOTE 1: This procedure is not to be confused with the deactivation procedure in subclause 4.3.2. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 101 (GSM 11.11 version 6.3.0 Release 1997) The GSM session is terminated by the ME as follows: The ME runs all the procedures which are necessary to transfer the following subscriber related information to the SIM: - Location Information update; - Cipher Key update; - BCCH information update; - Advice of Charge increase; - Forbidden PLMN update. As soon as the SIM indicates that these procedures are completed, the ME/SIM link may be deactivated. Finally, the ME deletes all these subscriber related information elements from its memory. NOTE 2: If the ME has already updated any of the subscriber related information during the GSM Session, and the value has not changed until GSM session termination, the ME may omit the respective update procedure.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.3 Emergency Call Codes
|
Request: The ME performs the reading procedure with EFECC. Update: The ME performs the updating procedure with EFECC. NOTE: The update procedure is only applicable when access conditions of ADM for update is set to ALW, CHV1 or CHV2.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.4 Language preference
|
Request: The ME performs the reading procedure with EFLP. Update: The ME performs the updating procedure with EFLP.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.5 Administrative information request;
|
The ME performs the reading procedure with EFAD.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.6 SIM service table request
|
The ME performs the reading procedure with EFSST.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.7 SIM phase request
|
The ME performs the reading procedure with EFPhase.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.8 SIM Presence Detection and Proactive Polling
|
As an additional mechanism, to ensure that the SIM has not been removed during a card session, the ME sends, at frequent intervals, a STATUS command during each call. A STATUS command shall be issued within all 30 second periods of inactivity on the SIM-ME interface during a call. Inactivity in this case is defined as starting at the end of the last communication or the last issued STATUS command. If no response data is received to this STATUS command, then the call shall be terminated as soon as possible but at least within 5 seconds after the STATUS command has been sent. If the DF indicated in response to a STATUS command is not the same as that which was indicated in the previous response, or accessed by the previous command, then the call shall be terminated as soon as possible but at least within 5 seconds after the response data has been received. This procedure shall be used in addition to a mechanical or other device used to detect the removal of a SIM. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 102 (GSM 11.11 version 6.3.0 Release 1997) If the ME supports the proactive SIM service, and the SIM has this service activated in its Service Table, then during idle mode the ME shall send STATUS commands to the SIM at intervals no longer than the interval negotiated with the SIM (see GSM 11.14 [27]).
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.2.9 Extended Language preference
|
Request: The ME performs the reading procedure with EFELP. Update: The ME performs the updating procedure with EFELP.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.3 CHV related procedures
|
A successful completion of one of the following procedures grants the access right of the corresponding CHV for the GSM session. This right is valid for all files within the GSM application protected by this CHV. After a third consecutive presentation of a wrong CHV to the SIM, not necessarily in the same GSM session, the CHV status becomes "blocked" and if the CHV is "enabled", the access right previously granted by this CHV is lost immediately. An access right is not granted if any of the following procedures are unsuccessfully completed or aborted.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.3.1 CHV verification
|
The ME checks the CHV status. In the case of CHV1 the following procedure applies: - if the CHV1 status is "blocked" and CHV1 is "enabled", the procedure ends and is finished unsuccessfully; - if the CHV1 status is "blocked" but CHV1 is "disabled", the procedure ends and is finished successfully. The ME shall, however, accept SIMs which do not grant access rights when CHV1 is "blocked" and "disabled". In that case ME shall consider those SIMs as "blocked"; - if the CHV1 status is not "blocked" and CHV1 is "disabled", the procedure is finished successfully; - if the CHV1 status is not "blocked" and CHV1 is "enabled", the ME uses the VERIFY CHV function. If the CHV1 presented by the ME is equal to the corresponding CHV1 stored in the SIM, the procedure is finished successfully. If the CHV1 presented by the ME is not equal to the corresponding CHV1 stored in the SIM, the procedure ends and is finished unsuccessfully. In the case of CHV2 the following procedure applies: - if the CHV2 status is "blocked", the procedure ends and is finished unsuccessfully; - if the CHV2 status is not "blocked", the ME uses the VERIFY CHV function. If the CHV2 presented by the ME is equal to the corresponding CHV2 stored in the SIM, the procedure is finished successfully. If the CHV2 presented by the ME is not equal to the corresponding CHV2 stored in the SIM, the procedure ends and is finished unsuccessfully.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.3.2 CHV value substitution
|
The ME checks the CHV status. If the CHV status is "blocked" or "disabled", the procedure ends and is finished unsuccessfully. If the CHV status is not "blocked" and the enabled/disabled indicator is set "enabled", the ME uses the CHANGE CHV function. If the old CHV presented by the ME is equal to the corresponding CHV stored in the SIM, the new CHV presented by the ME is stored in the SIM and the procedure is finished successfully. If the old CHV and the CHV in memory are not identical, the procedure ends and is finished unsuccessfully. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 103 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.3.3 CHV disabling
|
Requirement: Service n°1 "allocated and activated". The ME checks the CHV1 status. If the CHV1 status is "blocked", the procedure ends and is finished unsuccessfully. If the CHV1 status is not "blocked", the ME reads the CHV1 enabled/disabled indicator. If this is set "disabled", the procedure ends and is finished unsuccessfully. If the CHV1 status is not "blocked" and the enabled/disabled indicator is set "enabled", the ME uses the DISABLE CHV function. If the CHV1 presented by the ME is equal to the CHV1 stored in the SIM, the status of CHV1 is set "disabled" and the procedure is finished successfully. If the CHV1 presented by the ME is not equal to the CHV1 stored in the SIM, the procedure ends and is finished unsuccessfully.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.3.4 CHV enabling
|
The ME checks the CHV1 status. If the CHV1 status is "blocked", the procedure ends and is finished unsuccessfully. If the CHV1 status is not "blocked", the ME reads the CHV1 enabled/disabled indicator. If this is set "enabled", the procedure ends and is finished unsuccessfully. If the CHV1 status is not "blocked" and the enabled/disabled indicator is set "disabled", the ME uses the ENABLE CHV function. If the CHV1 presented by the ME is equal to the CHV1 stored in the SIM, the status of CHV1 is set "enabled" and the procedure is finished successfully. If the CHV presented by the ME is not equal to the CHV1 stored in the SIM, the procedure ends and is finished unsuccessfully.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.3.5 CHV unblocking
|
The execution of the CHV unblocking procedure is independent of the corresponding CHV status, i.e. being blocked or not. The ME checks the UNBLOCK CHV status. If the UNBLOCK CHV status is "blocked", the procedure ends and is finished unsuccessfully. If the UNBLOCK CHV status is not "blocked", the ME uses the UNBLOCK CHV function. If the UNBLOCK CHV presented by the ME is equal to the corresponding UNBLOCK CHV stored in the SIM, the relevant CHV status becomes "unblocked" and the procedure is finished successfully. If the UNBLOCK CHV presented by the ME is not equal to the corresponding UNBLOCK CHV stored in the SIM, the procedure ends and is finished unsuccessfully.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4 GSM security related procedures
| |
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.1 GSM algorithms computation
|
The ME selects DFGSM and uses the RUN GSM ALGORITHM function (see subclause 8.16). The response SRES-Kc is sent to the ME when requested by a subsequent GET RESPONSE command.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.2 IMSI request
|
The ME performs the reading procedure with EFIMSI.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.3 Access control request
|
The ME performs the reading procedure with EFACC.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.4 HPLMN search period request
|
The ME performs the reading procedure with EFHPLMN. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 104 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.5 Location information
|
Request: The ME performs the reading procedure with EFLOCI. Update: The ME performs the updating procedure with EFLOCI.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.6 Cipher key
|
Request: The ME performs the reading procedure with EFKc. Update: The ME performs the updating procedure with EFKc.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.7 BCCH information
|
Request: The ME performs the reading procedure with EFBCCH. Update: The ME performs the updating procedure with EFBCCH.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.4.8 Forbidden PLMN
|
Request: The ME performs the reading procedure with EFPLMN. Update: The ME performs the updating procedure with EFPLMN.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5 Subscription related procedures
| |
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.1 Dialling numbers
|
The following procedures may not only be applied to EFADN and its associated extension files EFCCP and EFEXT1 as described in the procedures below, but also to EFFDN, EFMSISDN, EFLND, EFBDN and EFSDN and their associated extension files. If these files are not allocated and activated, as denoted in the SIM service table, the current procedure shall be aborted and the appropriate EFs shall remain unchanged. As an example, the following procedures are described as applied to ADN. Requirement: Service n°2 "allocated and activated" (Service n°3 for FDN, Service n°9 for MSISDN, Service n°13 for LND, Service n°18 for SDN), Service n°31 for BDN) Update: The ME analyses and assembles the information to be stored as follows (the byte identifiers used below correspond to those in the description of the EFs in subclauses 10.4.1, 10.4.4 and 10.4.10): i) The ME identifies the Alpha-tagging, Capability/Configuration Identifier and Extension1 Record Identifier. ii) The dialling number/SSC string shall be analysed and allocated to the bytes of the EF as follows: - if a "+" is found, the TON identifier is set to "International"; - if 20 or less "digits" remain, they shall form the dialling number/SSC string; ETSI ETSI TS 100 977 V6.3.0 (2000-05) 105 (GSM 11.11 version 6.3.0 Release 1997) - if more than 20 "digits" remain, the procedure shall be as follows: Requirement: Service n°10 "allocated and activated" (Service n°10 applies also for MSISDN and LND; Service n°11 for FDN; Service n°19 for SDN; Service n°32 for BDN.) The ME seeks for a free record in EFEXT1. If an Extension1 record is not marked as "free", the ME runs the Purge procedure. If an Extension1 record is still unavailable, the procedure is aborted. The first 20 "digits" are stored in the dialling number/SSC string. The value of the length of BCD number/SSC contents is set to the maximum value, which is 11. The Extension1 record identifier is coded with the associated record number in the EFEXT1. The remaining digits are stored in the selected Extension1 record where the type of the record is set to "additional data". The first byte of the Extension1 record is set with the number of bytes of the remaining additional data. The number of bytes containing digit information is the sum of the length of BCD number/SSC contents of EFADN and byte 2 of all associated chained Extension1 records containing additional data (see subclauses 10.4.1 and 10.4.10). iii) If a called party subaddress is associated to the ADN/SSC the procedure shall proceed as follows: Requirement: Service n°10 "allocated and activated" (Service n°10 applies also for MSISDN and LND; Service n°11 for FDN; Service n°19 for SDN; Service n°32 for BDN.) If the length of the called party subaddress is less than or equal to 11 bytes (see GSM 04.08 [15] for coding): The ME seeks for a free record in EFEXT1. If an Extension1 record is not marked as "free", the ME runs the Purge procedure. If an Extension1 record is still unavailable, the procedure is aborted. The ME stores the called party subaddress in the Extension1 record, and sets the Extension1 record type to "called party subaddress". If the length of the called party subaddress is greater than 11 bytes (see GSM 04.08 [15] for coding): The ME seeks for two free records in EFEXT1. If no such two records are found, the ME runs the Purge procedure. If two Extension1 records are still unavailable, the procedure is aborted. The ME stores the called party subaddress in the two Extension1 records. The identifier field in the Extension1 record containing the first part of the subaddress data is coded with the associated EFEXT1 record number containing the second part of the subaddress data. Both Extension1 record types are set to "called party subaddress". Once i), ii), and iii) have been considered the ME performs the updating procedure with EFADN. If the SIM has no available empty space to store the received ADN/SSC, or if the procedure has been aborted, the ME advises the user. NOTE 1: For reasons of memory efficiency the ME is allowed to analyse all Extension1 records to recognize if the additional or subaddress data to be stored is already existing in EFEXT1. In this case the ME may use the existing chain or the last part of the existing chain from more than one ADN (LND, MSISDN). The ME is only allowed to store extension data in unused records. If existing records are used for multiple access, the ME shall not change any data in those records to prevent corruption of existing chains. Erasure: The ME sends the identification of the information to be erased. The content of the identified record in EFADN is marked as "free". Request: The ME sends the identification of the information to be read. The ME shall analyse the data of EFADN (subclause 10.4.1) to ascertain, whether additional data is associated in EFEXT1 or EFCCP. If necessary, then the ME performs the reading procedure on these EFs to assemble the complete ADN/SSC. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 106 (GSM 11.11 version 6.3.0 Release 1997) Purge: The ME shall access each EF which references EFEXT1 (EFEXT2) for storage and shall identify records in these files using extension data (additional data or called party subaddress). Note that existing chains have to be followed to the end. All referred Extension1 (Extension2) records are noted by the ME. All Extension1 (Extension2) records not noted are then marked by the ME as "free" by setting the whole record to 'FF'. NOTE 2: Dependent upon the implementation of the ME, and in particular the possibility of erasure of ADN/SSC records by Phase 1 MEs, which have no knowledge of the EFEXT1, it is possible for Extension1 records to be marked as "used space" (not equal to 'FF'), although in fact they are no longer associated with an ADN/SSC record. The following three procedures are only applicable to service n°3 (FDN). FDN capability request. The ME has to check the state of service n°3, i.e. if FDN is "enabled" or "disabled". In case of enabled FDN, the ME has to switch to a restrictive terminal mode (see GSM 02.07). To ascertain the state of FDN, the ME checks in EFSST whether or not ADN is activated. If ADN is not activated, service n°3 is enabled. If ADN is activated, the ME checks the response data of EFADN. If EFADN is invalidated, service n°3 is enabled. In all other cases service n°3 is disabled. FDN disabling. The FDN disabling procedure requires that CHV2 verification procedure has been performed successfully and that ADN is activated. If not, FDN disabling procedure will not be executed successfully. To disable FDN capability, the ME rehabilitates EFADN. The invalidate/rehabilitate flag of EFADN, which is implicitly set by the REHABILITATE command, is at the same time the indicator for the state of the service n°3. If ADN is not activated, disabling of FDN is not possible and thus service n°3 is always enabled (see FDN capability request). NOTE 3: If FDN is disabled (by rehabilitating EFADN) using an administrative terminal then the FDN disabling procedure of this administrative terminal need also to rehabilitate EFIMSI and EFLOCI to ensure normal operation of the SIM in a phase 1 ME or a phase 2 ME which does not support FDN. FDN enabling. The FDN enabling procedure requires that CHV2 verification procedure has been performed successfully. If not, FDN enabling procedure will not be executed successfully. To enable FDN capability, the ME invalidates EFADN. The invalidate/rehabilitate flag of EFADN, which is implicitly cleared by the INVALIDATE command, is at the same time the indicator for the state of the service n°3 (see FDN capability request). If ADN is not activated, service n°3 is always enabled. Invalidated ADNs may optionally still be readable and updatable depending on the file status (see clause 9.3) The following three procedures are only applicable to service n°31 (BDN). BDN capability request. The ME has to check the state of service n°31, i.e. if BDN is "enabled" or "disabled". BDN service is "enabled" only if service n°31 is allocated and activated, and EFBDN is not invalidated. In all other cases, the BDN service is "disabled". BDN disabling. The BDN disabling procedure requires that CHV2 verification procedure has been performed successfully. If not, BDN disabling procedure will not be executed successfully. To disable BDN capability, the ME invalidates EFBDN. The invalidate/rehabilitate flag of EFBDN, which is implicitly cleared by the INVALIDATE command, is at the same time the indicator for the state of the service n°31 (see BDN capability request). BDN enabling. The BDN enabling procedure requires that CHV2 verification procedure has been performed successfully. If not, BDN enabling procedure will not be executed successfully. To enable BDN capability, the ME rehabilitates EFBDN. The invalidate/rehabilitate flag of EFBDN, which is implicitly set by the REHABILITATE command, is at the same time the indicator for the state of the service n°31 (see BDN capability request). Invalidated BDNs (when BDN capability is disabled) may optionally still be readable and updatable depending on the file status (see clause 9.3).
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.2 Short messages
|
Requirement: Service n°4 "allocated and activated". Request: The SIM seeks for the identified short message. If this message is found, the ME performs the reading procedure with EFSMS. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 107 (GSM 11.11 version 6.3.0 Release 1997) If service n°35 is "allocated and activated" and the status of the SMS is '1D' (status report requested, received and stored in EFSMSR), the ME performs the reading procedure with the corresponding record in EFSMSR. If the ME does not find a corresponding record in EFSMSR, then the ME shall update the status of the SMS with '19' (status report requested, received but not stored in EFSMSR). If the short message is not found within the SIM memory, the SIM indicates that to the ME. Update: The ME looks for the next available area to store the short message. If such an area is available, it performs the updating procedure with EFSMS. If there is no available empty space in the SIM to store the received short message, a specific MMI will have to take place in order not to loose the message. Erasure: The ME will select in the SIM the message area to be erased. Depending on the MMI, the message may be read before the area is marked as "free". After performing the updating procedure with EFSMS, the memory allocated to this short message in the SIM is made available for a new incoming message. The memory of the SIM may still contain the old message until a new message is stored in this area. If service n°35 is "allocated and activated" and the status of the SMS is '1D' (status report requested, received and stored in EFSMSR), the ME performs the erasure procedure for EFSMSR with the corresponding record in EFSMSR.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.3 Advice of Charge (AoC)
|
Requirement: Service n°5 "allocated and activated". Accumulated Call Meter. Request: The ME performs the reading procedure with EFACM. The SIM returns the last updated value of the ACM. Initialization: The ME performs the updating procedure with EFACM using the new initial value. Increasing: The ME performs the increasing procedure with EFACM sending the value which has to be added. Accumulated Call Meter Maximum Value. Request: The ME performs the reading procedure with EFACMmax. Initialization: The ME performs the updating procedure with EFACMmax using the new initial maximum value. Price per Unit and Currency Table (PUCT). Request: The ME performs the reading procedure with EFPUCT. Update: The ME performs the updating procedure with EFPUCT.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.4 Capability configuration parameters
|
Requirement: Service n°6 "allocated and activated". Request: The ME performs the reading procedure with EFCCP. Update: The ME performs the updating procedure with EFCCP. Erasure: The ME sends the identification of the requested information to be erased. The content of the identified record in EFCCP is marked as "free".
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.5 PLMN selector
|
Requirement: Service n°7 "allocated and activated". ETSI ETSI TS 100 977 V6.3.0 (2000-05) 108 (GSM 11.11 version 6.3.0 Release 1997) Request: The ME performs the reading procedure with EFPLMNsel. Update: The ME performs the updating procedure with EFPLMNsel.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.6 Cell broadcast message identifier
|
Requirement: Service n°14 "allocated and activated". Request: The ME performs the reading procedure with EFCBMI. Update: The ME performs the updating procedure with EFCBMI.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.7 Group identifier level 1
|
Requirement: Service n°15 "allocated and activated". Request: The ME performs the reading procedure with EFGID1.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.8 Group identifier level 2
|
Requirement: Service n°16 "allocated and activated". Request: The ME performs the reading procedure with EFGID2.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.5.9 Service Provider Name
|
Requirement: Service n°17 "allocated and activated". Request: The ME performs the reading procedure with EFSPN. 11.5.10 Voice Group Call Services Requirement: Service n°18 "allocated and activated". Voice Group Call Service Request: The ME performs the reading procedure with EFVGCS. Voice Group Call Service Status Request: The ME performs the reading procedure with EFVGCSS. Update: The ME performs the updating procedure with EFVGCSS. 11.5.11 Voice Broadcast Services Requirement: Service n°19 "allocated and activated". Voice Broadcast Service Request: The ME performs the reading procedure with EFVBS. Voice Broadcast Service Status Request: The ME performs the reading procedure with EFVBSS. Update: The ME performs the updating procedure with EFVBSS. 11.5.12 Enhanced Multi Level Pre-emption and Priority Service Requirement: Service n°18 "allocated and activated". ETSI ETSI TS 100 977 V6.3.0 (2000-05) 109 (GSM 11.11 version 6.3.0 Release 1997) Enhanced Multi Level Pre-emption and Priority Request: The ME performs the reading procedure with EFeMLPP. Automatic Answer on eMLPP service Request: The ME performs the reading procedure with EFAAeM. Update: The ME performs the updating procedure with EFAAeM. 11.5.13 Cell Broadcast Message range identifier Requirement: Service n°30 "allocated and activated". Request: The ME performs the reading procedure with EFCBMIR. Update: The ME performs the updating procedure with EFCBMIR. 11.5.14 Depersonalisation Control Keys Requirement: Service n°33 "allocated and activated". Request: The ME performs the reading procedure with EFDCK. 11.5.15 Short message status report Requirement: Service n°35 "allocated and activated". Request: If the status of a stored short message indicates that there is a corresponding status report, the ME performs the seek function with EFSMSR to identify the record containing the appropriate status report. The ME performs the reading procedure with EFSMSR. Update: If a status report is received, the ME first seeks within the SMS record identifiers of EFSMSR for the same record number it used for the short message in EFSMS. If such a record identifier is found in EFSMSR, it is used for storage. If such a record identifier is not found, then the ME seeks for a free entry in EFSMSR for storage. If no free entry is found the ME runs the Purge procedure with EFSMSR. If there is still no free entry, the status report is not stored. If the ME found an appropriate record in EFSMSR for storage, it updates the record with the status report setting the record identifier in EFSMSR to the appropriate record number of the short message in EFSMS. The status in EFSMS is updated accordingly (see 10.4.3) by performing the update procedure with EFSMS. Erasure: The ME runs the update procedure with EFSMSR by at least storing '00' in the first byte of the record. The ME may optionally update the following bytes with 'FF'. Purge: The ME shall read the SMS record identifier (byte 1) of each record of EFSMSR. With each record the ME checks the corresponding short messages in EFSMS. If the status (byte 1) of the corresponding SMS is not equal '1D' (status report requested, received and stored in EFSMSR), the ME shall perform the erasure procedure with the appropriate record in EFSMSR. 11.5.16 Network's indication of alerting Requirement: Service n°36 "allocated and activated". Request: The ME performs the reading procedure with EFNIA. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 110 (GSM 11.11 version 6.3.0 Release 1997)
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.6 SIM Application Toolkit related procedures
|
SIM Application Toolkit is an optional feature. The higher level procedures, and contents and coding of the commands, are given in GSM 11.14 [27]. Procedures relating to the transmission of commands and responses across the SIM/ME interface are given in this section. A SIM or ME supporting SIM Application Toolkit shall conform to the requirements given in this section.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.6.1 Initialization procedure
|
A SIM supporting SIM Application Toolkit shall indicate this through relevant data in EFPhase and EFSST, as defined in the relevant sections above. An ME supporting SIM Application Toolkit shall perform initialization as defined in the SIM Initialization section above.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.6.2 Proactive polling
|
An ME supporting proactive SIM (part of SIM Application Toolkit) shall support the polling procedure as defined above.
|
7cb4fd1069780e5630834ee9b5bf2c49
|
100 977
|
11.6.3 Support of commands
|
A SIM or ME supporting SIM Application Toolkit shall support the commands TERMINAL PROFILE, ENVELOPE, FETCH and TERMINAL RESPONSE. These commands shall never be used if either the SIM or ME does not support SIM Application Toolkit. Therefore standard SIMs and MEs do not need to support these commands.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.