10.5 Contents of files at the telecom level

11.113GPPRelease 1999Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) InterfaceTS

The EFs in the Dedicated File DFTELECOM contain service related information.

10.5.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.

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 TS 23.038 [12] with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to ‘FF’; or

– 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.5.10).

Coding:

according to TS 04.08 [15].

‑ TON and NPI

Contents:

Type of number (TON) and numbering plan identification (NPI).

Coding:

according to TS 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 TS 04.08 [15]). Accordingly, the ME should not interpret the value ‘FF’ and not send it over the radio interface.

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 TS 04.08 [15] , TS 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’.

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.5.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 (TS 02.07 [3])

‘D’

"Wild" value

This will cause the MMI to prompt the user for a single digit (see TS 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 TS 02.07 [3]).

10.5.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.5.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.

10.5.3 EFSMS (Short messages)

This EF contains information in accordance with TS 23.040 [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.

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 TS 24.011 [16]. The bytes immediately following the TS‑Service‑Centre‑Address contain an appropriate short message TPDU as specified in TS 23.040 [13], with identical coding and ordering of parameters.

Coding:

according to TS 23.040 [13] and TS 24.011 [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.

10.5.4 Capability configuration parameters

10.5.4.1 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.

For compatibility reasons, this file may be present for release 98 or earlier MEs in order to support Capability Configuration Parameters service.

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 TS 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.

10.5.4.2 EFECCP (Extended 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.

The number of records of the EFECCP shall be equal to the number of records of the EFCCP. Each record of the EFCCP shall have a corresponding record in the EFECCP with the same record number.

If an ME has to update a record, then the ME shall update each record of both files, EFCCP with 10 bytes and EFECCP with X bytes (X15).

If an ME has to read a record, then the ME shall check the consistency between the record of the EFECCP and the corresponding record of the EFCCP and update the record of the EFECCP with the value of the corresponding record of the EFCPP.

Identifier: ‘6F4F’

Structure: linear fixed

Optional

Record length: X (X15)

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to X

Bearer capability information element

M

X bytes

‑ Bearer capability information element

Contents and Coding:

see TS 24.008 [47]. The Information Element Identity (IEI) shall be excluded, i.e. the first byte of the EFECCP record shall be Length of the bearer capability contents.

Unused bytes are filled with ‘FF’.

10.5.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.

10.5.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.

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.5.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

Bit value Meaning

0 Parameter present

1 Parameter absent

‑ TP‑Destination Address

Contents and Coding: As defined for SM‑TL address fields in TS 23.040 [13].

‑ TP‑Service Centre Address

Contents and Coding: As defined for RP‑Destination address Centre Address in TS 24.011 [16].

‑ TP‑Protocol Identifier

Contents and Coding: As defined in TS 23.040 [13].

‑ TP‑Data Coding Scheme

Contents and Coding: As defined in TS 23.038 [12].

‑ TP‑Validity Period

Contents and Coding: As defined in TS 23.040 [13] for the relative time format.

10.5.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 TS 23.040 [13].

Coding:

as defined in TS 23.040 [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 TS 23.040 [13].

Coding:

b1=1 means flag unset; memory capacity available

b1=0 means flag set

b2 to b8 are reserved and set to 1.

10.5.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

For contents and coding, see subclause 10.5.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.

10.5.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.

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 to 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 to 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.5.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.5.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".

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 TS 04.08 [15]. All information defined in TS 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.

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.5.11 EFEXT2 (Extension2)

This EF contains extension data of an FDN/SSC (see EXT2 in subclause 10.5.2).

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.5.10 EFEXT1.

10.5.12 EFEXT3 (Extension3)

This EF contains extension data of an SDN (see EXT3 in subclause 10.5.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.5.10 EFEXT1.

10.5.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 / ADM (set at personalisation)

REHABILITATE CHV2 / ADM (set at personalisation)

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 Pointer

M

1 byte

For contents and coding of all data items, except for the Comparison Method Pointer, see the respective data items of the EFADN (subclause 10.5.1), with the exception that extension records are stored in the EFEXT4. The Comparison Method Pointer refers to a record number in EFCMI.

NOTE: The value of X (the number of bytes in the alpha‑identifier) may be different to the length denoted X in EFADN.

10.5.14 EFEXT4 (Extension4)

This EF contains extension data of an BDN/SSC (see EXT4 in subclause 10.5.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.5.10 EFEXT1.

10.5.15 EFSMSR (Short message status reports)

This EF contains information in accordance with TS 23.040 [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 to 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.

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 TS 23.040 [13], with identical coding and ordering of parameters.

Coding:

according to TS 23.040 [13]. Any bytes in the record following the TPDU shall be filled with ‘FF’.

10.5.16 EFCMI (Comparison Method Information)

This EF contains a list of Comparison Method Identifiers and alpha-tagging associated with BDN entries (see EFBDN). This EF shall always be present if EFBDN is present.

Identifier: ‘6F58’

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 to X

Alpha Identifier

M

X bytes

X+1

Comparison Method Identifier

M

1 byte

– Alpha Identifier

Contents:

Alpha-tagging of the associated Comparison Method Identifier

Coding:

Same as the alpha identifier in EFADN.

‑ Comparison Method Identifier

Contents:

this byte describes the comparison method which is associated with a BDN record. Its interpretation is not specified but it shall be defined by the operators implementing the BDN feature.

Coding:

’00’ – ‘FE’ = Comparison Method Identifier.

‘FF’ = Default method.