Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 31.102  Word version:  18.5.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.6.5…   4.6.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M… 
4.2.17 EFLOCI (Location Information)  4.2.18 EFAD (Administrative Data)  4.2.20 EFCBMID (Cell Broadcast Message Identifier for Data Download)  4.2.21 EFECC (Emergency Call Codes)  4.2.22 EFCBMIR (Cell Broadcast Message Identifier Range selection)  4.2.23 EFPSLOCI (Packet Switched location information)  4.2.24 EFFDN (Fixed Dialling Numbers)  4.2.25 EFSMS (Short messages) 
...

 

4.2.17  EFLOCI (Location Information)  p. 41

This EF contains the following Location Information:
  • Temporary Mobile Subscriber Identity (TMSI);
  • Location Area Information (LAI);
  • Location update status.
See clause 5.2.5 for special requirements when updating EFLOCI.
Identifier: '6F7E'Structure: transparentMandatory
SFI: '0B'
File size: 11 bytesUpdate activity: high
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4TMSIM4 bytes
5 to 9LAIM5 bytes
10RFUM1 byte
11Location update statusM1 byte
TMSI
Contents:
Temporary Mobile Subscriber Identity.
Coding:
according to TS 24.008.
b8 b7 b6 b5 b4 b3 b2 b1
MSB
 
LAI
Contents:
Location Area Information.
Coding:
according to TS 24.008.
Byte 5: first byte of LAI
b8 b7 b6 b5 b4 b3 b2 b1
MSB
 
Location update status
Contents:
status of location update according to TS 24.008.
Coding:
Byte 11:
Bits:b3b2b1
000:  updated.
001:  not updated.
010:  PLMN not allowed.
011:  Location Area not allowed.
111:  reserved.
Bits b4 to b8 are RFU (see TS 31.101).
Up

4.2.18  EFAD (Administrative Data)  p. 42

This EF contains information concerning the mode of operation according to the type of USIM, such as normal (to be used by PLMN subscribers for 3GPP network 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 about how some ME features shall work during normal operation as well as information about the length of the MNC, which is part of the International Mobile Subscriber Identity (IMSI) if service No. 130 is "not available".
Identifier: '6FAD'Structure: transparentMandatory
SFI: '03'
File size: 4+X bytesUpdate activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1UE operation modeM1 byte
2 to 3Additional informationM2 bytes
4length of MNC in the IMSIM1 byte
5 to 4+XRFUOX bytes
UE operation mode:
Contents:
mode of operation for the UE
Coding:
Initial value
'00'
normal operation.
'80'
type approval operations.
'01'
normal operation + specific facilities.
'81'
type approval operations + specific facilities.
'02'
maintenance (off line).
'04'
cell test operation.
All other values are RFU
Additional information:
Contents:
additional information depending on the UE operation mode
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 (see TS 31.101)
     
    Byte 3 (second byte of additional information):
    b8 b7 b6 b5 b4 b3 b2 b1
    RFU (see TS 31.101) b5:
    5G ProSe, see below
    		b4:
    extended DRX cycle
    		b3:
    ProSe services for Public Safety, see below
    		b2:
    CSG Display Control bit, see below
    		b1=0:
    ciphering indicator feature disabled
    b1=1:
    ciphering indicator feature enabled
    b1 is used to control the ciphering indicator feature as specified in TS 22.101.
    b2 is used to indicate which CSGs the UE shall display during manual CSG selection. This bit corresponds to the value of OperatorCSGEntries_Only leaf described in TS 24.285. This bit shall be ignored when service No. 92 is not "available".
    • b2=0: for every PLMN not included in EFOCSGL, or for which a CSG display indicator tag is not present, all available CSGs can be displayed without any restriction.
    • b2=1: for every PLMN not included in EFOCSGL or any PLMN for which a CSG display indicator tag is not present, only the available CSGs found in the Operator CSG list shall be displayed.
    b3 is used to indicate whether the USIM enables the Public Safety UE to use the ME provisioning parameters for Public Safety usage, in the cases described in TS 24.334.
    • b3=0: the ME is not authorized for ProSe services for Public Safety usage (i.e. Direct Discovery and Direct Communication as per TS 24.334) without contacting the ProSe Function.
    • b3=1: the ME is authorized to use the parameters stored in the USIM or in the ME for ProSe services for Public Safety usage, as described in TS 24.334 without contacting the ProSe Function.
    b4 is used to indicate whether the UICC polling interval to retrieve proactive commands can be modified (as described in TS 31.101) or weather the UICC interface can be deactivated (as described in clause 5.1.11) during extended DRX cycle.
    • b4=0: the ME is not authorized to modify the polling interval and/or disable the UICC interface during extended DRX cycle.
    • b4=1: the ME is authorized to modify the polling interval and/or disable the UICC interface during extended DRX cycle.
    b5 is used to indicate whether the USIM enables the UE to use "operator-managed" radio resources, in the cases described in TS 23.304.
    • b5=0: the UE is not authorized to use "operator-managed" radio resources.
    • b5=1: the UE is authorized to use "operator-managed" radio resources.
     
  • ME manufacturer specific information (if b2=1 in byte 1):
     
    Byte 2 (first byte of additional information):
    b8 b7 b6 b5 b4 b3 b2 b1
    Any value
     
    Byte 3 (second byte of additional information):
    b8 b7 b6 b5 b4 b3 b2 b1
    Any value
Length of MNC in the IMSI:
Contents:
The length indicator refers to the number of digits, used for extracting the MNC from the IMSI if service No. 130 is "not available" and the value shall be set to 0 if service No. 130 is "available".
Coding:
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) This value codes the number of digits of the MNC in the IMSI. Only the values '0000', '0010' and '0011' are currently specified, '0000' value is used if service No. 130 is "available", all other values are reserved for future use.
Up

4.2.19  Void

4.2.20  EFCBMID (Cell Broadcast Message Identifier for Data Download)  p. 44

If service No. 29 is "available", this file shall be present.
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 USIM.
Any number of CB message identifier parameters may be stored in the USIM. No order of priority is applicable.
Identifier: '6F48'Structure: transparentOptional
SFI: '0E'
File size: 2n bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 2CB Message Identifier 1O2 bytes
3 to 4CB Message Identifier 2O2 bytes
…
2n-1 to 2nCB Message Identifier nO2 bytes
Cell Broadcast Message Identifier
Coding:
as in TS 23.041. Values listed show the identifiers of messages which shall be accepted by the UE to be passed to the USIM.
Unused entries shall be set to 'FF FF'.
Up

4.2.21  EFECC (Emergency Call Codes)  p. 45

This EF contains emergency call codes.
Identifier: '6FB7'Structure: linear fixedMandatory
SFI: '01'
Record size: X+4 bytesUpdate activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 3Emergency Call CodeM3 bytes
4 to X+3Emergency Call Code Alpha IdentifierOX bytes
X+4Emergency Service CategoryM1 byte
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 than 6 digits is chosen, then the unused nibbles shall be set to 'F'.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 2 : : LSB of Digit 2 MSB of Digit 1 : : LSB of Digit 1
 
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 4 : : LSB of Digit 4 MSB of Digit 3 : : LSB of Digit 3
 
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1
MSB of Digit 6 : : LSB of Digit 6 MSB of Digit 5 : : LSB of Digit 5
 
Emergency Call Code Alpha Identifier
Contents:
Information about the dialled emergency number to be displayed to the user.
Coding:
this alpha-tagging shall use
either:
  • the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'.
or
Emergency Service Category
Contents:
Information to be sent to the network indicating the category of the emergency call.
Coding:
Coding according to TS 24.008.
Up

4.2.22  EFCBMIR (Cell Broadcast Message Identifier Range selection)  p. 46

If service No. 16 is "available", this file shall be present.
This EF contains ranges of cell broadcast message identifiers that the subscriber wishes the UE to accept.
Any number of CB Message Identifier Parameter ranges may be stored in the USIM. No order of priority is applicable.
Identifier: '6F50'Structure: transparentOptional
File size: 4n bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4CB Message Identifier Range 1O4 bytes
5 to 8CB Message Identifier Range 2O4 bytes
…
(4n-3) to 4nCB Message Identifier Range nO4 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 TS 23.041 "Message Format on BTS-MS Interface - Message Identifier". Values listed show the ranges of messages which shall be accepted by the UE.
Unused entries shall be set to 'FF FF FF FF'.
Up

4.2.23  EFPSLOCI (Packet Switched location information)  p. 46

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: '6F73'Structure: transparentMandatory
SFI: '0C'
File size: 14 bytesUpdate activity: high
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 4P-TMSIM4 bytes
5 to 7P-TMSI signature valueM3 bytes
8 to 13RAIM6 bytes
14Routing Area update statusM1 byte
P-TMSI
Contents:
Packet Temporary Mobile Subscriber Identity.
Coding:
according to TS 24.008.
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 TS 24.008.
Byte 5: first byte of P-TMSI signature value.
b8 b7 b6 b5 b4 b3 b2 b1
MSB
 
RAI
Contents:
Routing Area Information.
Coding:
according to TS 24.008.
Byte 8: first byte of RAI
b8 b7 b6 b5 b4 b3 b2 b1
MSB
 
Routing Area update status
Contents:
status of routing area update according to TS 24.008.
Coding:
byte 14:
Bits:b3b2b1
000:  updated.
001:  not updated.
010:  PLMN not allowed.
011:  Location Area not allowed.
111:  reserved.
Bits b4 to b8 are RFU (see TS 31.101).
Up

4.2.24  EFFDN (Fixed Dialling Numbers)  p. 48

If service No. 2 and/or service No. 89 is "available", this file shall be present.
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 at the USIM ADF level. It may also contain an associated alpha-tagging. If this file is present in the USIM, the Enabled Services Table (EFEST) shall also be present.
Identifier: '6F3B'Structure: linear fixedOptional
Record length: X+14 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XAlpha IdentifierOX bytes
X+1Length of BCD number/SSC contentsM1 byte
X+2TON and NPIM1 byte
X+3 to X+12Dialling Number/SSC StringM10 bytes
X+13Capability/Configuration2 Record IdentifierM1 byte
X+14Extension2 Record IdentifierM1 byte
For contents and coding of all data items see the respective data items of the EFADN (clause 4.4.2.3), with the exception that extension records are stored in the EFEXT2.
By default, destination addresses which are not in EFFDN shall not be allowed on any CS bearer service/teleservice, or IMS communication or SMS when FDN is enabled.
For the FDN procedures related to SMS see TS 22.101 and TS 31.111.
Up

4.2.25  EFSMS (Short messages)  p. 48

If service No. 10 is "available", this file shall be present.
This EF contains information in accordance with TS 23.040 comprising short messages (and associated parameters) which have either been received by the UE from the network, or are to be used as an UE originated message.
Identifier: '6F3C'Structure: linear fixedOptional
Record length: 176 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1StatusM1 byte
2 to 176RemainderM175 bytes
Status
Contents:
Status byte of the record which can be used as a pattern in the SEARCH RECORD command. For UE originating messages sent to the network, the status shall be updated when the UE receives a status report, or sends a successful SMS Command relating to the status report.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101)
X X 0free space
X X 1used space
0 0 1message received by UE from network; message read
0 1 1message received by UE from network; message to be read
1 1 1UE originating message; message to be sent
 
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101)
X X 1 0 1UE originating message; message sent to the network:
0 0 1 0 1Status report not requested
0 1 1 0 1Status report requested but not (yet) received;
1 0 1 0 1 Status report requested, received but not stored in EFSMSR;
1 1 1 0 1 Status report requested, received and stored in EFSMSR;
 
Remainder
Contents:
This data item commences with the TS-Service-Centre-Address as specified in TS 24.011. The bytes immediately following the TS-Service-Centre-Address contain an appropriate short message TPDU as specified in TS 23.040, with identical coding and ordering of parameters.
Coding:
According to TS 23.040 and TS 24.011. Any TP-message reference contained in an UE originated message stored in the USIM, 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 USIM the TS-Service-Centre-Address and the TPDU in bytes 2 to 176 without modification, except for the last byte of the TPDU, which shall not be stored.
Up

Up   Top   ToC