12 SIMPLE-TLV data objects

3GPP51.014Release 4Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interfaceTS

The coding of the TLV objects is as described in TS 102 223 [37], except when stated otherwise in the present document.

12.1 Address

See TS 102 223 [37].

12.2 Alpha identifier

See TS 102 223 [37].

12.3 Subaddress

See TS 102 223 [37].

12.4 Capability configuration parameters

Byte(s)

Description

Length

1

Capability configuration parameters tag

1

2 to (Y‑1)+2

Length (X)

Y

(Y‑1)+3 to (Y‑1)+X+2

Capability configuration parameters

X

Capability configuration parameters are coded as for EFCCP. If it is being provided by the SIM, the SIM shall supply all information required to complete the Bearer Capability Information Element in the Call Set-up message (see TS 24.008 [11]). Any unused bytes at the end of the value part shall be coded ‘FF’.

See TS 51.011 [20] for the coding of all EFs.

NOTE: The second byte of this TLV contains the Length of the TLV and the third byte contains the Length of the bearer capability contents, followed by the actual contents.

12.5 Cell Broadcast Page

Byte(s)

Description

Length

1

Cell Broadcast page tag

1

2

Length = ’58’ (88 decimal)

1

3 – 90

Cell Broadcast page

88

The Cell Broadcast page is formatted in the same way as described in TS 23.041 [7].

12.6 Command details

The content and the coding of the Command Details TLV object is defined in TS 102 223 [37], except for the following.

  • The coding of the Command Qualifier is defined for the following commands:

Coding:

– REFRESH;

’00’ =SIM Initialization and Full File Change Notification;

’01’ = File Change Notification;

’02’ = SIM Initialization and File Change Notification;

’03’ = SIM Initialization;

’04’ = SIM Reset;

’05’ to ‘FF’ = reserved values.

– SEND SS;

This byte is RFU.

– SEND USSD;

This byte is RFU.

– GET INKEY,

bit 1: 0 = digits (0‑9, *, # and +) only

1 = alphabet set;

bit 2: 0 = SMS default alphabet

1 = UCS2 alphabet

bit 3: 0 = character sets defined by bit 1 and bit 2 are enabled

1 = character sets defined by bit 1 and bit 2 are disabled and the "Yes/No" response is requested

bits 4‑7: = RFU

bit 8: 0 = no help information available

1 = help information available

– PROVIDE LOCAL INFORMATION

’00’ = Location Information (MCC, MNC, LAC and Cell Identity)

’01’ = IMEI of the ME

’02’ = Network Measurement results

’03’ = Date, time and time zone

’04’ = Language setting

’05’ = Timing Advance

’06’ to ‘FF’ = Reserved

12.7 Device identities

See TS 102 223 [37].

12.8 Duration

See TS 102 223 [37].

12.9 Item

See TS 102 223 [37].

12.10 Item identifier

See TS 102 223 [37].

12.11 Response length

See TS 102 223 [37].

12.12 Result

For the general result byte coding the following values are defined in addition to or replacement of those in TS 102 223 [32]:

– ’14’ = USSD or SS transaction terminated by the user.

– ’34’ = SS Return Error;

– ’35’ = SMS RP-ERROR;

– ’37’ = USSD Return Error;

– ’39’ = Interaction with call control by SIM or MO short message control by SIM, permanent problem;

– Additional information.

– Contents: For the general result "Command performed successfully", some proactive commands require additional information in the command result. This is defined in the clauses below. For the general result values ’20’, ’21’, ’34’, ’35’, ’37’, and ’39’, it is mandatory for the ME to provide a specific cause value as additional information, as defined in the clauses below. For other values, see TS 102 223 [32].

12.12.1 Additional information for SEND SS

When the ME issues a successful COMMAND RESULT for a SEND SS proactive command, it shall also include the Operation Code and Parameters included in the Return Result component from the network, as additional information.

The first byte of the additional information shall be the SS Return Result Operation code, as defined in TS 24.080 [10].

The rest of the additional information shall be the SS Return Result Parameters, as defined in TS 24.080 [10].

12.12.2 Additional information for ME problem

For the general result "ME currently unable to process command", it is mandatory for the ME to provide additional information, the first byte of which to be as defined below:

– ’00’ = No specific cause can be given;

– ’01’ = Screen is busy;

– ’02’ = ME currently busy on call;

– ’03’ = ME currently busy on SS transaction;

– ’04’ = No service;

– ’05’ = Access control class bar;

– ’06’ = Radio resource not granted;

– ’07’ = Not in speech call;

– ’08’ = ME currently busy on USSD transaction;

– ’09’ = ME currently busy on SEND DTMF command.

All other values shall be interpreted by the SIM as ’00’.The coding ’00’ shall only be used by the ME if no others apply.

12.12.3 Additional information for network problem

For the general result "network currently unable to process command", it is mandatory for the ME to provide additional information. The first byte shall be the cause value of the Cause information element returned by the network (as defined in TS 04.08 [8]). Bit 8 shall be set to ‘1’. One further value is defined:

– ’00’ = No specific cause can be given.

All other values shall be interpreted by the SIM as ’00’. The coding ’00’ shall only be used by the ME if no others apply.

12.12.4 Additional information for SS problem

For the general result "SS Return Error", it is mandatory for the ME to provide additional information. The first byte shall be the error value given in the Facility (Return result) information element returned by the network (as defined in TS 24.080 [10]). One further value is defined:

– ’00’ = No specific cause can be given.

All other values shall be interpreted by the SIM as ’00’. The coding ’00’ shall only be used by the ME if no others apply.

12.12.5 Additional information for SMS problem

For the general result "SMS RP-ERROR", it is mandatory for the ME to provide additional information. The first byte shall be the cause value given in the RP-Cause element of the RP-ERROR message returned by the network (as defined in TS 24.011 [9]), with bit 8 = 0. One further value is defined:

– ’00’ = No specific cause can be given.

All other values shall be interpreted by the SIM as ’00’. Specific cause ’00’ shall only be used by the ME if no others apply.

12.12.6 Not used

12.12.7 Additional information for USSD problem

For the general result "USSD Return Error", the ME shall provide additional information. The first byte shall be the error value given in the Facility (Return result) information element returned by the network (as defined in TS 24.080 [10]). One further value is defined:

– ’00’ = No specific cause can be given.

All other values shall be interpreted by the SIM as ’00’.

The coding ’00’ shall only be used by the ME if no others apply.

12.12.8 Additional information for interaction with call control or MO SM control

For the general result "interaction with call control by SIM or MO short message control by SIM, permanent problem", it is mandatory for the ME to provide additional information, the first byte of which to be as defined below:

– ’00’ = No specific cause can be given;

– ’01’ = Action not allowed;

– ’02’ = The type of request has changed.

All other values shall be interpreted by the SIM as ’00’. The coding ’00’ shall only be used by the ME if no others apply.

12.12.9 Additional information for MultipleCard commands

See TS 102 223 [37].

12.12.10 Additional information for Launch Browser problem

See TS 102 223 [37].

12.12.11 Additional information for Bearer Independent Protocol

See TS 102 223 [37].

12.13 SMS TPDU

Byte(s)

Description

Length

1

SMS TPDU tag

1

2 to (Y‑1)+2

Length (X)

Y

(Y‑1)+3 to (Y‑1)+X+2

SMS TPDU

X

The TPDU is formatted as described in TS 23.040 [6].

Where the TPDU is being sent from the SIM to the ME (to be forwarded to the network), and where it includes a TP-Message-Reference which is to be incremented by the ME for every outgoing message, the TP-Message-Reference as provided by the SIM need not be the valid value. TP-Message-Reference shall be checked and corrected by the ME to the value described in TS 23.040 [6].

12.14 SS string

Byte(s)

Description

Length

1

SS string tag

1

2 to (Y‑1)+2

Length (X)

Y

(Y‑1)+3

TON and NPI

1

(Y‑1)+4 to (Y‑1)+X+2

SS or USSD string

X – 1

TON/NPI and SS or USSD control string are coded as for EFADN, where the ADN record relates to a Supplementary Service Control string. See TS 51.011 [20] for the coding of EFADN.

12.15 Text string

Content and coding is defined TS 102 223 [37], with the following requirement :

Data coding scheme is coded as for SMS Data coding scheme defined in TS 23.038 [5]. Parts of the data coding scheme other than the character set indication shall be ignored.

12.16 Tone

See TS 102 223 [37]. Excepted for the following:

Coding of the ME proprietary tones:

’10’ General beep

’11’ Positive acknowledgement tone

’12’ Negative acknowledgement or error tone

All other values are reserved.

NOTE: Standard supervisory tones for 3G are specified in TS 22.001 [22].

12.17 USSD string

Byte(s)

Description

Length

1

USSD string tag

1

2 to (Y-1)+2

Length (X)

Y

(Y-1)+3

Data coding scheme

1

(Y-1)+4 to (Y-1)+X+2

USSD string

X-1

The Data coding scheme is coded as for Cell Broadcast defined in TS 23.038 [5]. The coding of the USSD string is defined in TS 02.30 [4].

12.18 File List

Byte(s)

Description

Length

1

File List tag

1

2 to (Y‑1)+2

Length (X) of bytes following

Y

(Y‑1)+3

Number of files (n)

1

(Y‑1)+4 to (Y‑1)+X+2

Files

X‑1

Number of files:

This is the number of files that will be described in the following list.

Files:

Full paths are given to files. Each of these shall be at least 4 octets in length (e.g. ‘3F002FE2’ or ‘3F007F206FAD’). Each entry in the file description is composed of two bytes, where the first byte identifies the type of file (see TS 51.011 [20]).

An entry in the file description shall therefore always begin with ‘3FXX’. There can be any number of Dedicated File entries between the Master File and Elementary File. There shall be no delimiters between files, as this is implied by the fact that the full path to any EF starts with ‘3FXX’ and ends with an Elementary type file.

12.19 Location Information

Byte(s)

Description

Length

1

Location Information tag

1

2

Length = ’07’

1

3 – 5

Mobile Country & Network Codes (MCC & MNC)

3

6 – 7

Location Area Code (LAC)

2

8 – 9

Cell Identity Value (Cell ID)

2

The mobile country code (MCC), the mobile network code (MNC), the location area code (LAC) and the cell ID are coded as in TS 04.08 [8].

12.20 IMEI

See TS 102 223 [37].

12.21 Help Request

See TS 102 223 [37].

12.22 Network Measurement Results

Byte(s)

Description

Length

1

Network Measurement Results tag

1

2

Length = ’10’

1

3 – 18

Network Measurement Results

16

The Network Measurement Results are coded as for the Measurement Results information element in TS 04.08 [8], starting at octet 2 (the IEI is removed, as this information is duplicated by the data object tag).

12.23 Default Text

See TS 102 223 [37].

12.24 Items Next Action Indicator

See TS 102 223 [37].

12.25 Event list

See TS 102 223 [37].

12.26 Cause

Byte(s)

Description

Length

1

Cause tag

1

2

Length (X) of bytes following. X=0, or 2  X  30.

1

3 to X+2

Cause

X

The Cause data object is coded as for the Cause call control information element in TS 04.08 [8], starting at octet 3 (the IEI and Length information are removed, as this information is duplicated by the data object tag and length).

Radio Link Timeout is indicated by the Cause data object having a value part of zero length (only the Tag and Length components are sent).

12.27 Location status

See TS 102 223 [37].

12.28 Transaction identifier

Byte(s)

Description

Length

1

Transaction identifier tag

1

2

Length (X) of bytes following

1

3 to X+2

Transaction identifier list

X

– Transaction identifier list

Contents: A list of transaction identifiers, of variable length. Each byte in the list defines a transaction identifier. Each transaction identifier shall not appear more than once within the list.

Coding: Each byte in the transaction identifier list shall be coded as defined below:

bits 1 to 4 = RFU

bits 5 to 7 = TI value

bit 8 = TI flag

TI value and TI flag are coded as defined in TS 24.007 [23].

12.29 BCCH channel list

Byte(s)

Description

Length

1

BCCH channel list tag

1

2

Length (X) of bytes following

1

3 to X+2

BCCH channel list

X

– BCCH channel list

Contents: the list of absolute RF channels for BCCH carriers, as known by the ME from the SYSTEM INFORMATION messages. The BCCH channel list is composed of one to three BCCH channel sub lists, each sub list is derived from the set of frequencies defined by reference neighbour cells description information element or elements. In the latter case the set is the union of the different subsets defined by the neighbour cells description information elements (see TS 04.08 [8]). The length of the BCCH channel list field depends on the length of the received BCCH channel list derived from the different SYSTEM INFORMATION messages to be considered.

Coding: Each ARFCN is represented by 10 bits. Spare bit(s) are to be filled with 0.

Bit 8

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Byte 1

ARFCN#1 (high part)

Byte 2

ARFCN#1 (low part)

ARFCN#2 (high part)

Byte 3

ARFCN#2 (low part)

ARFCN#3 (high part)

Byte X-1

ARFCN#m-1 (low part)

ARFCN#m (high part)

Byte X

ARFCN#m (low part)

Spare bit (0)

Spare bit

(0)

SIM applications should take into account that early implementations of SIM application toolkit may have coded this field differently, because of an inconsistancy between the content and the coding of this element in previous versions of 11.14. The SIM is able to identify MEs that are using the coding described above by evaluating the indication "BCCH Channel List coding" in the TERMINAL PROFILE command.

12.30 Call control requested action

See TS 102 223 [37].

12.31 Icon Identifier

See TS 102 223 [37].

12.32 Item Icon Identifier list

See TS 102 223 [37].

12.33 Card reader status

See TS 102 223 [37].

12.34 Card ATR

This subclause applies only if class "a" is supported.

See TS 102 223 [37].

12.35 C-APDU

This subclause applies only if class "a" is supported.

See TS 102 223 [37].

12.36 R-APDU

This subclause applies only if class "a" is supported.

See TS 102 223 [37].

12.37 Timer identifier

See TS 102 223 [37].

12.38 Timer value

See TS 102 223 [37].

12.39 Date-Time and Time zone

See TS 102 223 [37].

12.40 AT Command

This subclause applies only if class "b" is supported.

Byte(s)

Description

Length

1

AT Command tag

1

2 to (Y-1)+2

Length (X)

Y

(Y-1)+3 to (Y-1)+3+X-1

AT Command string

X

Contents: The AT Command string is structured exactly as the AT Command line as defined in TS 27.007 [27], which may contain single or concatenated AT commands.

12.41 AT Response

This subclause applies only if class "b" is supported.

Byte(s)

Description

Length

1

AT Response tag

1

2 to (Y-1)+2

Length (X)

Y

(Y-1)+3 to (Y-1)+3+X-1

AT Response string

X

Contents: The AT Response string is structured exactly as the response to a command line as defined in TS 27.007 [27], which may contain single or concatenated responses appropriate to the issued AT command.

If the AT Response string is longer than the maximum length capable of being transmitted to the SIM then the AT Response string shall be truncated to this length by the ME.

12.42 BC Repeat indicator

Byte(s)

Description

Length

1

BC repeat indicator tag

1

2

Length

1

3

BC repeat indicator values

1

Contents & coding: The BC repeat indicator is structured exactly as defined in TS 24.008 [10].

12.43 Immediate response

See TS 102 223 [37].

12.44 DTMF string

See TS 102 223 [37].

12.45 Language

See TS 102 223 [37].

12.46 Timing Advance

Byte(s)

Description

Length

1

Timing Advance tag

1

2

Length = ’02’

1

3

ME Status

1

4

Timing Advance

1

Coding of ME status:

’00’ = ME is in the idle state

’01’ = ME is not in idle state

’02’ to’FF’= reserved values

The Timing Advance is coded as for the Timing Advance information element in TS 04.08 [8], starting at octet 2 (the IEI is removed, as this information is duplicated by the data object tag).

12.47 Browser Identity

See TS 102 223 [37].

12.48 URL

See TS 102 223 [37].

12.49 Bearer

Byte(s)

Description

Length

1

Bearer tag

1

2 to (Y + 1)

Length (X)

Y

(Y+2) to (Y + X +1)

List of bearers in order of priority requested

X

The ME shall use this list to choose which bearers are allowed in order of priority.

Coding of the bearers :

’00’ = SMS ;

’01’ = CSD ;

’02’ = USSD ;

’03’ = GPRS ;

’04’ to ‘FF’ = RFU.

12.50 Provisioning File Reference

See TS 102 223 [37].

12.51 Browser Termination Cause

See TS 102 223 [37].

12.52 Bearer description

Byte(s)

Description

Length

1

Bearer description tag

1

2

Length (X+1)

1

3

Bearer type

1

4 to (3+X)

Bearer parameters

X

– Bearer Type coding: in addition to the values defined in TS 102 223 [32], the following are defined:

– ’01’ = CSD;

– ’02’ = GPRS / 3G packet service;

– Bearer parameters coding: see the following clauses for 2G specific technologies.

12.52.1 Bearer parameters for CSD

Contents: parameters specific to the bearer.

The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations and values of these subparameters are supported by GSM (refer TS 22.002 [30]).

X (length of parameters) = 3.

Coding:

The following values are as defined in the TS 27.007 [27] for the select service bearer type "+CBST" extended command. They are coded in hexadecimal.

– byte 4 – Data rate: same as the "speed" subparameter defined in TS 27.007 [27].

– byte 5 – bearer service: same as the "name" subparameter defined in TS 27.007 [27].

– byte 6 – connection element: same as the "ce" subparameter defined in TS 27.007 [27].

12.52.2 Bearer parameters for GPRS / packet service

Contents : parameters describing the Quality of Service (QoS) and the type of PDP. This is an element of the PDP context.

The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations and values of these subparameters are supported by GSM (refer TS 22.002 [30]).

X (length of parameters) = 6.

Coding: The following values are as defined in TS 27.007 [27], for the quality of Service profile requested "+CGQREQ" extended command. They are coded in hexadecimal.

– Coding of Byte 4 – Precedence class: same as the "precedence" subparameter, defined in TS 27.007 [27].

– Coding of Byte 5 – Delay class: same as the "delay" subparameter, defined in TS 27.007 [27].

– Coding of Byte 6 – Reliability class: same as the "reliability" subparameter, defined in TS 27.007 [27].

– Coding of Byte 7 – Peak throughput class: same as the "peak" subparameter, defined in TS 27.007 [27].

– Coding of Byte 8 – Mean throughput class: same as the "mean" subparameter, defined in TS 27.007 [27].

– Coding of Byte 9 – Packet data protocol type:

– ’02’ = IP (Internet Protocol, IETF STD 5);

– all other values are reserved.

12.53 Channel data

This subclause applies only if class "e" is supported.

See TS 102 223 [37].

12.54 Channel data length

This subclause applies only if class "e" is supported.

See TS 102 223 [37].

12.55 Buffer size

This subclause applies only if class "e" is supported.

See TS 102 223 [37].

12.56 Channel status

This subclause applies only if class "e" is supported.

See TS 102 223 [37].

12.57 Card reader identifier

This subclause applies only if class "a" is supported.

See TS 102 223 [37].

12.58 Other Address

See TS 102 223 [37].

12.59 SIM/ME interface transport level

See TS 102 223 [37].

12.60 Void

12.61 Network Access Name

Byte(s)

Description

Length

1

Network Access Name tag

1

2

Length (X)

1

3 to 3+X-1

Network Access Name

X

– Content: The Network Access Name is used to identify the Gateway entity, which provides interworking with
an external packet data network. For GPRS, the Network Access Name is an APN.

– Coding: As defined in TS 23.003 [36].

12.62 Service Record

See TS 102 223 [37].

12.63 Device Filter

See TS 102 223 [37].

12.64 Service Search

See TS 102 223 [37].

12.65 Attribute Information

See TS 102 223 [37].

12.66 Service Availability

See TS 102 223 [37].

12.67 Remote Entity Address

See TS 102 223 [37].

12.68 Access Technology

See TS 102 223 [32].

12.69 Display parameters

See TS 102 223 [32].