Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  17.1.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.5…   4.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.26  EFMSISDN (MSISDN)Word‑p. 47

UICC File Structure: EFs under USIM (MSISDN, SMSP, SMSS, SDN, EXT2, EXT3, SMSR, ICI)
Up
If service No. 21 is "available", this file shall be present.
This EF contains MSISDN(s) related to the subscriber. 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.
Identifier: '6F40'Structure: linear fixedOptional
Record length: X+14 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN/ADM (fixed during administrative management)
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+14Extension5 Record IdentifierM1 byte
For contents and coding of all data items see the respective data items of EF ADN.
If the USIM stores more than one MSISDN number and the ME displays the MSISDN number(s) within the initialisation procedure then the one stored in the first record shall be displayed with priority.
Up

4.2.27  EFSMSP (Short message service parameters)

If service No. 12 is "available", this file shall be present.
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.
The SMS parameters stored within a record may be present or absent independently. When a short message is to be sent from the UE, the parameter in the USIM record, if present, shall be used when a value is not supplied by the user.
Identifier: '6F42'Structure: linear fixedOptional
Record length: 28+Y bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to YAlpha-IdentifierOY bytes
Y+1Parameter IndicatorsM1 byte
Y+2 to Y+13TP-Destination AddressM12 bytes
Y+14 to Y+25TS-Service Centre AddressM12 bytes
Y+26TP-Protocol IdentifierM1 byte
Y+27TP-Data Coding SchemeM1 byte
Y+28TP-Validity PeriodM1 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 clause 4.4.2.3 (EF ADN).
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 numberParameter indicated
1TP-Destination Address
2TS-Service Centre Address
3TP-Protocol Identifier
4TP-Data Coding Scheme
5TP-Validity Period
6reserved, set to 1
7reserved, set to 1
8reserved, set to 1
Bit valueMeaning
0Parameter present
1Parameter absent
TP-Destination Address
Contents and Coding:
as defined for SM-TL address fields in TS 23.040.
TP-Service Centre Address
Contents and Coding:
as defined for RP-Destination address Centre Address in TS 24.011.
TP-Protocol Identifier
Contents and Coding:
as defined in TS 23.040.
TP-Data Coding Scheme
Contents and Coding:
as defined in TS 23.038.
TP-Validity Period
Contents and Coding:
as defined in TS 23.040 for the relative time format.
Up

4.2.28  EFSMSS (SMS status)Word‑p. 49

If service No. 10 is "available", this file shall be present.
This EF contains status information relating to the short message service.
Identifier: '6F43'Structure: transparentOptional
File size: 2+X bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Last Used TP-MRM1 byte
2SMS "Memory Cap. Exceeded" Not. FlagM1 byte
3 to 2+XRFUOX bytes
Last Used TP-MR
Contents:
the value of the TP-Message-Reference parameter in the last mobile originated short message, as defined in TS 23.040.
Coding:
as defined in TS 23.040.
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 UE becomes available, the Network can be informed. The process for this is described in TS 23.040.
Coding:
b1=1 means flag unset; memory capacity available;
b1=0 means flag set;
b2 to b8 are reserved and set to 1.
Up

4.2.29  EFSDN (Service Dialling Numbers)

If service No. 4 and or service No. 89 is "available", this file shall be present.
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 at the USIM ADF level. It may also contain associated alpha-tagging. If the service No. 89 is available this file will contain the eCall test and reconfiguration numbers that are used by an UE in eCall and normal service mode.
Identifier: '6F49'Structure: linear fixedOptional
Record length: X+14 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1-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+14Extension3 Record IdentifierM1 byte
For contents and coding of all data items see the respective data items of the EF ADN (clause 4.4.2.3), with the exception that extension records are stored in the EF EXT3 and capability/configuration parameters are stored in EF CCP2.
Up

4.2.30  EFEXT2 (Extension2)Word‑p. 50

If service No. 3 is "available", this file shall be present.
This EF contains extension data of an FDN (see FDN in 4.2.24).
Identifier: '6F4B'Structure: linear fixedOptional
Record length: 13 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Record typeM1 byte
2 to 12Extension dataM11 bytes
13IdentifierM1 byte
For contents and coding see clause 4.4.2.4 (EFEXT1).
Up

4.2.31  EFEXT3 (Extension3)

If service No. 5 is "available", this file shall be present.
This EF contains extension data of an SDN (see SDN in 4.2.29).
Identifier: '6F4C'Structure: linear fixedOptional
Record length: 13 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Record typeM1 byte
2 to 12Extension dataM11 bytes
13IdentifierM1 byte
For contents and coding see clause 4.4.2.4 (EFEXT1).
Up

4.2.32  EFSMSR (Short message status reports)Word‑p. 51

If service No. 11 is "available", this file shall be present.
This EF contains information in accordance with TS 23.040 comprising short message status reports which have been received by the UE from the network.
Each record is used to store the status report of a short message in a record of EF SMS. The first byte of each record is the link between the status report and the corresponding short message in EF SMS.
Identifier: '6F47'Structure: linear fixedOptional
Record length: 30 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1SMS record identifierM1 byte
2 to 30SMS status reportM29 bytes
SMS record identifier
Contents:
this data item identifies the corresponding SMS record in EF SMS, e.g. if this byte is coded '05' then this status report corresponds to the short message in record #5 of EF SMS.
Coding:
'00'empty record
'01' to 'FF'record number of the corresponding SMS in EF SMS
SMS status report
Contents:
this data item contains the SMS-STATUS-REPORT TPDU as specified in TS 23.040, with identical coding and ordering of parameters.
Coding:
according to TS 23.040. Any bytes in the record following the TPDU shall be filled with 'FF'.
Up

4.2.33  EFICI (Incoming Call Information)

If service No. 9 is "available", this file shall be present.
This EF is located within the USIM application. The incoming call information can be linked to the phone book stored under DFTELECOM or to the local phone book within the USIM. The EF ICI contains the information related to incoming calls.
The time of the call and duration of the call are stored in this EF. This EF can also contain associated alpha identifier that may be supplied with the incoming call. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM ADF level. The structure of this EF is cyclic, so the contents shall be updated only after a call is disconnected.
If CLI is supported and the incoming phone number matches a number stored in the phone book the incoming call information is linked to the corresponding information in the phone book. If the incoming call matches an entry but is indicated as hidden in the phone book the link is established but the information is not displayed by the ME if the code for the secret entry has not been verified. The ME shall not ask for the secret code to be entered at this point.
Optionally the ME may store the link to phone book entry in the file, so that it does not need to look again for a match in the phone book when it reuses the entry. But the ME will have to check that the incoming call number still exits in the linked phone book entry, as the link might be broken (entry modified). When not used by the ME or no link to the phone book has been found, this field shall be set to 'FFFFFF'.
The first byte of this link is used to identify clearly the phone book location either global (i.e. under DFTELECOM) or local (i.e. USIM specific). To allow the reuse of the referring mechanism in further implementation of the phonebook under discussion, this byte can be used to indicate those.
For the current version of the phone book, the phone book entry is identified as follows:
  • the record number in the EF PBR which indicates the EF ADN containing the entry;
  • the record number inside the indicated EF ADN.
The structure of EF ICI is shown below. Coding scheme is according to EF ADN
Identifier: '6F80'Structure: CyclicOptional
SFI: '14'
Record length: X+28 bytesUpdate activity: high
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XAlpha IdentifierOX bytes
X+1Length of BCD number contentsM1 byte
X+2TON and NPIM1 byte
X+3 to X+12Incoming Call NumberM10 bytes
X+13Capability/Configuration2 Record IdentifierM1 byte
X+14Extension5 Record IdentifierM1 byte
X+15 to X+21Incoming call date and time (see detail 1)M7 bytes
X+22 to X+24Incoming call duration (see detail 2)M3 bytes
X+25Incoming call status (see detail 3)M1 byte
X+26 to X+28Link to phone book entry (see detail 4)M3 bytes
Detail 1: Coding of date and time
Content:
the date and time are defined by the ME.
Coding:
it is according to the extended BCD coding from Byte1 to Byte 7. The first 3 bytes show year, month and day (yy.mm.dd). The next 3 bytes show hour, minute and second (hh.mm.ss). The last Byte 7 is Time Zone. The Time Zone indicates the difference, expressed in quarters of an hour, between the local time and GMT. Bit 4 in Byte 7 represents the algebraic sign of this difference (0: positive, 1: negative). If the terminal does not support the Time Zone, Byte 7 shall be "FF". Byte X+15: Year.
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit year LSB of second digit year MSB of first digit year LSB of first digit year
 
Byte X+16: Month
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit month LSB of second digit month MSB of first digit month LSB of first digit month
 
Byte X+17: Day
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit day LSB of second digit day MSB of first digit day LSB of first digit day
 
Byte X+18: Hour
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit hour LSB of second digit hour MSB of first digit hour LSB of first digit hour
 
Byte X+19: Minute
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit minute LSB of second digit minute MSB of first digit minute LSB of first digit minute
 
Byte X+20: Second
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit second LSB of second digit second MSB of first digit second LSB of first digit second
 
Byte X+21: Time Zone
b8 b7 b6 b5 b4 b3 b2 b1
MSB of second digit indicates by quarters an hour LSB of second digit indicates by quarters an hour MSB of first digit indicates by quarters an hour the algebraic sign (0: positive, 1: negative) LSB of first digit indicates by quarters an hour
 
Detail 2: Coding of call duration
Call duration is indicated by second.
Byte X+22:
b8 b7 b6 b5 b4 b3 b2 b1
223 222 221 220 219 218 217 216
 
Byte X+23:
b8 b7 b6 b5 b4 b3 b2 b1
215 214 213 212 211 210 29 28
 
Byte X+24:
b8 b7 b6 b5 b4 b3 b2 b1
27 26 25 24 23 22 21 20
 
For instance, '00' '00' '30' represents 25+24.
 
Detail 3: Coding of Call status
Byte X+25:
b8 b7 b6 b5 b4 b3 b2 b1
RFU Answered='0'/ Not Answered='1'
 
Detail 4: Link to phone book entry
For the current implementation of the phone book the following coding applies:
Phone book reference.
Byte X+26:
b8 b7 b6 b5 b4 b3 b2 b1
RFU 0 Global Phone Book (DFTELECOM)
1 Local Phone Book (USIM Specific)
 
EF PBR record number:
  • Byte X+27: Hexadecimal value.
    EF ADN record number:
  • Byte X+28: Hexadecimal value.
Up

Up   Top   ToC