8 COMPREHENSION-TLV data objects

31.1113GPPRelease 18TSUniversal Subscriber Identity Module (USIM) Application Toolkit (USAT)

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

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

8.1 Address

See ETSI TS 102 223 [32] clause 8.1.

8.2 Alpha identifier

See ETSI TS 102 223 [32] clause 8.2.

8.3 Subaddress

See ETSI TS 102 223 [32] clause 8.3.

8.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 EF_CCP. If it is being provided by the UICC, the UICC shall supply all information required to complete the Bearer Capability Information Element in the Call Set-up message (see TS 24.008 [9]). Any unused bytes at the end of the value part shall be coded ‘FF’.

See TS 31.102 [14] 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.

8.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 the GSM Cell Broadcast Message Parameter, as described in TS 23.041 [6].

8.6 Command details

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

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

– SEND SS:

this byte is RFU.

– SEND USSD:

this byte is RFU.

– PROVIDE LOCAL INFORMATION.

The following additional values are defined:

’00’ = Location Information (MCC, MNC, LAC/TAC, Cell Identity and Extended Cell Identity).

’02’ = Network Measurement results.

’05’ = Timing Advance.

‘0C’ = current WSID.

’11’ = CSG ID list and corresponding HNB name.

’12’ = H(e)NB IP address.

’13’ = H(e)NB surrounding macrocells.

’14’ = current WLAN identifier.

’15’ = slices information.

’16’ = CAG information list and the corresponding human-readable network name per CAG ID.

’17’ to ’19’ = reserved for 3GPP (for future usage)

The following values do not apply

’07’ = Reserved by ETSI (ESN)

‘0B’ = Reserved by ETSI (MEID)

– REFRESH. The following additional values are defined:

’07’ = Steering of Roaming as defined in TS 23.122 [7].

’08’ = Steering of Roaming for I-WLAN as defined in TS 24.234 [42].

– Geographical Location Request:

this byte is RFU.

– OPEN CHANNEL related to CS bearer, GPRS/UTRAN packet service/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN, local bearer, Default (network) bearer, I-WLAN bearer, WLAN bearer, Terminal Server Mode, UICC Server Mode:

– As defined in ETSI TS 102 223 [32]

– OPEN CHANNEL for IMS:

this byte is RFU.

8.7 Device identities

See ETSI TS 102 223 [32] clause 8.7.

8.8 Duration

See ETSI TS 102 223 [32] clause 8.8.

8.9 Item

See ETSI TS 102 223 [32] clause 8.9.

8.10 Item identifier

See ETSI TS 102 223 [32] clause 8.10.

8.11 Response length

See ETSI TS 102 223 [32] clause 8.11.

8.12 Result

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

– ’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 USIM or MO short message control by USIM, permanent problem;

In addition, the following values are reserved for 3GPP for future usage:

– ’15’ = reserved for 3GPP (for future usage);

– ’16’ = reserved for 3GPP (for future usage);

– ’28’ = reserved for 3GPP (for future usage);

– ’29’ = reserved for 3GPP (for future usage);

– ‘3E’ = reserved for 3GPP (for future usage);

– ‘3F’ = reserved for 3GPP (for future usage);

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 ETSI TS 102 223 [32] clause 8.12.

8.12.1 Additional information for SEND SS

When the ME issues a successful general 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 [11].

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

8.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 in ETSI TS 102 223 [32] clause 8.12.2, with the addition of the following value:

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

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

8.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 24.008 [9]). 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 UICC as ’00’. The coding ’00’ shall only be used by the ME if no others apply.

8.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 Error) information element returned by the network (as defined in TS 24.080 [11]). One further value is defined:

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

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

8.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 [10]), with bit 8 = 0. One further value is defined:

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

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

8.12.6 Not used

8.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 Error) information element returned by the network (as defined in TS 24.080 [11]). One further value is defined:

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

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

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

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

For the general result "interaction with call control by USIM or MO short message control by USIM, 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 UICC as ’00’. The coding ’00’ shall only be used by the ME if no others apply.

8.12.9 Additional information for MultipleCard commands

See ETSI TS 102 223 [32] clause 8.12.9.

8.12.10 Additional information for launch browser problem

See ETSI TS 102 223 [32] clause 8.12.10.

8.12.11 Additional information for Bearer Independent Protocol

See ETSI TS 102 223 [32] clause 8.12.11.

8.12.12 Additional information for Frames commands

See ETSI TS 102 223 [32] clause 8.12.12.

8.12.13 Additional information for SUBMIT and RETRIEVE MULTIMEDIA MESSAGE

See ETSI TS 102 223 [32] clause 8.12.13.

8.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 [5].

Where the TPDU is being sent from the UICC 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 UICC 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 [5].

8.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 EF_ADN, where the ADN record relates to a Supplementary Service Control string. See TS 31.102 [14] for the coding of EF_ADN.

8.15 Text string

Content and coding is defined ETSI TS 102 223 [32] clause 8.15, with the following requirement:

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

8.16 Tone

See ETSI TS 102 223 [32] clause 8.16.

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

8.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 [4]. The coding of the USSD string is defined in TS 22.030 [2].

NOTE 1: The MMI mode uses a 7 bit character set, the Application mode uses a 8 bit character set.

NOTE2: The DCS is set to 0x96 to indicate that the USSD string is formatted according to TS 31.115 [41].

8.18 File List

See ETSI TS 102 223 [32] clause 8.18.

8.19 Location Information

8.19.1 Location Information for GERAN

Byte(s)	Description	Length
1	Location Information tag	1
2	Length = ’07’ or ’05’ (see Note)	1
3 – 5	Mobile Country & Network Codes (MCC & MNC)	3
6 – 7	Location Area Code (LAC)	2
8 – 9	Cell Identity Value (Cell ID) (see Note)	2
NOTE: When this object is used in the Network Rejection event download, the Cell Identity Value (Cell ID) field shall not be present and the length field shall be set to ’05’.

The Mobile Country Code (MCC), the Mobile Network Code (MNC) and the Location Area Code (LAC) are coded as in TS 24.008 [9].

For GERAN, the Cell Identity Value is coded as in TS 24.008 [9].

8.19.2 Location Information for UTRAN

Byte(s)	Description	Length
1	Location Information tag	1
2	Length = ’09’ or ’05’ (see Note)	1
3 – 5	Mobile Country & Network Codes (MCC & MNC)	3
6 – 7	Location Area Code (LAC)	2
8 – 9	Cell Identity Value (Cell ID) (see Note)	2
10 – 11	Extended Cell identity Value (see Note)	2
NOTE: When this object is used in the Network Rejection event download, the Cell Identity Value (Cell ID) and Extended Cell identity Value fields shall not be present and the length field shall be set to ’05’.

The Mobile Country Code (MCC), the Mobile Network Code (MNC) and the Location Area Code (LAC) are coded as in TS 24.008 [9].

Only the C-id part of the UC-id is returned in the Cell Identity Value (i.e. the 16 least significant bits of the UC-id), as defined in TS 25.401 [35] and TS 25.413 [36].

The Extended Cell identity Value is coded as the RNC-id part of the UC-id, as defined in TS 25.401 [35] and TS 25.413 [36]. It is left padded with zeros (this means that byte 10 contains the 4 most significant bits of the RNC-id value, and byte 11 contains the 8 least significant bits of the RNC-id value).

8.19.3 Location Information for E-UTRAN and Satellite E-UTRAN

Byte(s)	Description	Length (bytes)
1	Location Information tag	1
2	Length (see Note)	1
3 – 5	Mobile Country & Network Codes (MCC & MNC)	3
6 – 7	Tracking Area Code (TAC)	2
8 – 11	E-UTRAN/Satellite E-UTRAN Cell Identifier (ECI) (see Note)	4
12	E-UTRAN Tracking Area Identification (TAI) list Identifier tag	1
13	Length of total bytes in Satellite E-UTRAN TAI List	1
14 to 13+(N*5)	Satellite E-UTRAN TAI List ‘N’ denotes Number of elements in TAI List (up to 12). Where N is ranging: 1<=N<=12	N * 5
NOTE: When this object is used in the Network Rejection event download, the E-UTRAN/Satellite E-UTRAN Cell Identifier (ECI) and Satellite E-UTRAN TAI list related fields shall not be present and the length field shall be set to ’05’.

Coding of each TAI in Satellite E-UTRAN TAI List:

Description	Value	M/O	Length (bytes)
Mobile Country & Network Codes (MCC & MNC)	—	M	3
Tracking Area Code (TAC)	—	M	2

The Mobile Country Code (MCC), the Mobile Network Code (MNC) is coded as in TS 24.008 [9].

The Tracking Area Code (TAC) for E-UTRAN is coded in 2 bytes as specified in TS 24.301 [46].

For Satellite E-UTRAN, when multiple TACs are received from the lower layers of the ME,
the ME shall derive the Current TAI as specified in TS 24.301 [46] and indicate it to UICC in bytes 3 – 7
of Satellite E-UTRAN Location Information. The ME shall additionally include the complete list of TAIs received from the lower layers in the Satellite E-UTRAN TAI List of the Location Information.

The E-UTRAN/Satellite E-UTRAN Cell Identifier (ECI) is coded as defined in TS 36.401 [48]. ECI has a length of 28 bits. The most significant bit of ECI is coded on the most significant bit of byte 8. The least significant bit of ECI is coded on the 4^th bit of byte 11. The 4 least significant bits of byte 11 shall be set to 1.

8.19.4 Location Information for NG-RAN and Satellite NG-RAN

Byte(s)	Description	Length (bytes)
1	Location Information tag	1
2	Length (see Note)	1
3 – 5	Mobile Country & Network Codes (MCC & MNC)	3
6 – 8	Tracking Area Code (TAC) (see Note)	3
9 – 13	NG-RAN/Satellite NG-RAN Cell Identifier (NCI) (see Note)	5
14	NG-RAN Tracking Area Identification (TAI) list Identifier tag	1
15	Length of total bytes in Satellite NG-RAN TAI List	1
16 to 15+(N*6)	Satellite NG-RAN TAI List ‘N’ denotes Number of elements in TAI List (up to 12). Where N is ranging: 1<=N<=12	N * 6
NOTE: When this object is used in the Network Rejection event download, the Tracking Area Code (TAC), NG-RAN/Satellite NG-RAN Cell Identifier (NCI) and the Satellite NG-RAN TAI List related fields shall not be present and the length field shall be set to ’03’.

Coding of each TAI in Satellite NG-RAN TAI List:

Description	Value	M/O	Length (bytes)
Mobile Country & Network Codes (MCC & MNC)	—	M	3
Tracking Area Code (TAC)	—	M	3

The Mobile Country Code (MCC), the Mobile Network Code (MNC) is coded as in TS 24.008 [9].

The Tracking Area Code (TAC) for NG-RAN is coded in 3 bytes as specified in TS 24.501 [70]. The most significant bit of TAC is coded on the most significant bit of byte 6. The least significant bit of TAC is coded on the least significant bit of byte 8.

For Satellite NG-RAN, when multiple TACs are received from the lower layers of the ME,
the ME shall derive the Current TAI as specified in TS 24.501 [70] and indicate it to the UICC in bytes 3 – 8
of Satellite NG-RAN Location Information. The ME shall additionally include the complete list of TAIs received from the lower layers in the Satellite NG-RAN TAI List of the Location Information.

NR Cell Identifier (NCI) Value is coded on 36 bits as referenced in TS 38.413 [69] clause 9.3.1.7. The most significant bit of NCI is coded on the most significant bit of byte 9. The least significant bit of NCI is coded on the 4^th bit of byte 13. The 4 least significant bits of byte 13 shall be set to 1.

8.19.5 Location Information when no surrounding macrocell is detected

When PROVIDE LOCAL INFORMATION with command qualifier ’13’ is used and no surrounding macrocell is detected for an Access Technology, a location information data object with length set to ’00’ shall be present.

Byte(s)	Description	Length
1	Location Information tag	1
2	Length = ’00’	1

8.20 IMEI

See ETSI TS 102 223 [32] clause 8.20.

8.21 Help Request

See ETSI TS 102 223 [32] clause 8.21.

8.22 Network Measurement Results

Byte(s)	Description	Length
1	Network Measurement Results tag	1
2	Length (X) of bytes following	1
3 – to X+2	Network Measurement Results	X

For GERAN: The Network Measurement Results are coded as for the Measurement Results information element in TS 44.018 [27], starting at octet 2 (the IEI is removed, as this information is duplicated by the data object tag). The Length shall be set to ’10’ (16 decimal).

For UTRAN: The Network Measurement Results are coded as for the "MeasurementReport" information element as defined in the ASN.1 description of TS 25.331 [38], according to the following:

– The "Measurement identity" field in the MEASUREMENT REPORT shall be set to the value ‘1’.

– If "intra-frequency measurements" are requested by USIM, the ME shall, in the MEASUREMENT REPORT, include IE "Intra-frequency measured results list" in IE "Measured Results". The ME shall report CPICH Ec/No, CPICH RSCP and pathloss for the up to 6 strongest (highest Ec/No value) intra-frequency cells, if available in the ME according to TS 25.331 [38] and TS 25.133 [39].

– If "inter-frequency measurements" are requested by USIM, the ME shall, in the MEASUREMENT REPORT, include IE "inter-frequency measured results list" in IE "Measured Results". The ME shall report CPICH Ec/No, CPICH RSCP and pathloss for the up to 6 strongest (highest Ec/No value) inter-frequency cells per monitored frequency, if available in the ME according to TS 25.331 [38] and TS 25.133 [39].

– If "inter-RAT (GERAN) measurements" are requested by USIM, the ME shall, in the MEASUREMENT REPORT, include IE "inter-RAT measured results list" in IE "Measured Results". The ME shall report GSM carrier RSSI for up to 8 strongest (highest RSSI value) inter-RAT GERAN cells (identified by the BCCH ARFCN), if available in the ME according to TS 25.331 [38] and TS 25.133 [50].

– If "inter-RAT (E-UTRAN)" are requested by USIM, the ME shall, in the MEASUREMENT REPORT, include IE "E-UTRA measured results". The ME shall report RSRP and RSRQ for the up to 4 strongest (highest RSRQ value) inter-RAT E-UTRAN cells per monitored frequency, if available in the ME according to TS 25.331 [38] and TS 25.133 [39].

– All other optional fields in the MeasurementReport shall be set to be absent.

For E-UTRAN and Satellite E-UTRAN:

Intra-frequency & inter-RAT (GERAN): the Network Measurement Results are coded as for the MeasurementReport information element as defined in the ASN.1 description of TS 36.331 [49], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServCell" with RSRP and RSRQ of the serving cell.

– If "intra-frequency measurements" are requested by USIM, the ME shall, in the MeasurementReport, include IE "measResultListEUTRA" in IE "measResults". The ME shall report RSRP, RSRQ, Physical Cell ID and IE "cgi-Info" for the up to 8 strongest (highest RSRQ value) intra-frequency cells, if available in the ME according to TS 36.331 [49] and TS 36.133 [50].

– If "inter-RAT (GERAN) measurements" are requested by USIM, the ME shall, in the MeasurementReport, include IE "measResultListGERAN" in IE "measResults". The ME shall report GERAN carrier RSSI and Physical Cell ID for the up to 8 strongest (highest RSSI value) inter-RAT GERAN cells (identified by the BCCH ARFCN) and IE "cgi-Info", if available in the ME according to TS 36.331 [49] and TS 36.133 [50].

– All other optional fields in the MeasurementReport shall be set to be absent.

Inter-frequency & inter-RAT (UTRAN): the ME can send more than one Network Measurement Results TLV object, each containing the results of one frequency. Each Network Measurement Results shall include 2 bytes with the frequency value coded as the ARFCN-ValueEUTRA for inter-frequency measurements or as the ARFCN-ValueUTRA for inter-RAT (UTRAN) measurements as defined in TS 36.331 [49], followed by the MeasurementReport information element as defined in the ASN.1 description of TS 36.331 [49], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServCell" with RSRP and RSRQ of the serving cell.

– If "inter-frequency measurements" are requested by the USIM, the ME shall, in the MeasurementReport, include IE " measResultListEUTRA" in IE "measResults". The ME shall report RSRP, RSRQ, Physical Cell ID and IE "cgi-Info" for the up to 8 strongest (highest RSRQ value) inter-frequency cells per monitored frequency, if available in the ME according to TS 36.331 [49] and TS 36.133 [50].

– If "inter-RAT (UTRAN) measurements" are requested by the USIM, the ME shall, in the MeasurementReport, include IE " measResultListUTRA" in IE "measResults". The ME shall report CPICH Ec/No, CPICH RSCP, Physical Cell ID and IE "cgi-Info" for the up to 8 strongest (highest Ec/No value) inter-RAT UTRAN cells per monitored frequency, if available in the ME according to TS 36.331 [49] and TS 36.133 [50].

– All other optional fields in the MeasurementReport shall be set to be absent.

For inter-frequency measurement results with EARFCN that exceeds maxEARFCN, the ME shall use the E-UTRAN/Satellite E-UTRAN Inter-frequency Network Measurement Results TLV objects if the service "extended EARFCN" is available in the USIM Service Table (see TS 31.102 [14]) or not include them otherwise.

Inter-RAT (NR): the ME can send more than one Network Measurement Results TLV object, each containing the results of one frequency. Each Network Measurement Results shall include 4 bytes containing the frequency value coded as the ARFCN-ValueNR for inter-RAT (NR) measurements as defined in TS 36.331 [49], where the least significant byte of the frequency value is stored in the least significant byte of this 4 byte field and the unused bytes of these 4 byte field are set to 0, followed by the MeasurementReport information element as defined in the ASN.1 description of TS 36.331 [49], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServCell" with RSRP and RSRQ of the serving cell.

– If "inter-RAT (NR) measurements" are requested by the USIM, the ME shall, in the MeasurementReport, include IE "measResultNeighCellListNR" in IE "measResults". The ME shall report Physical Cell ID, related RSRP,RSRQ and SINR for the up to 8 strongest inter-RAT NR cells per monitored frequency, if available in the ME according to TS 36.331 [49] and TS 36.133 [50].

– All other optional fields in the MeasurementReport shall be set to be absent.

For NG-RAN and Satellite NG-RAN:

Intra-frequency : the Network Measurement Results are coded as for the MeasurementReport information element as defined in the ASN.1 description of TS 38.331 [71], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServingCell" with RSRP,RSRQ and the available SINR of the serving cell.

– If "intra-frequency measurements" are requested by USIM, the ME shall, in the MeasurementReport, include IE "MeasResultListNR" in IE "measResults". The ME shall report Physical Cell ID,related RSRP,RSRQ,SINR and IE " cgi-Info" for the up to 8 strongest intra-frequency cells, if available in the ME according to TS 38.331 [71] and TS 38.133 [72].

– All other optional fields in the MeasurementReport shall be set to be absent.

Inter-frequency and inter-RAT (E-UTRAN): the ME can send more than one Network Measurement Results TLV object, each containing the results of one frequency. Each Network Measurement Results shall include 3 bytes containing the frequency value coded as the ARFCN-ValueNR for Inter-frequency measurements or as the ARFCN-ValueEUTRA for inter-RAT (E-UTRAN) measurements as defined in TS 38.331[71].the Network Measurement Results are coded as for the MeasurementReport information element as defined in the ASN.1 description of TS 38.331 [71], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServingCell" with RSRP,RSRQ and the available SINR of the serving cell.

– If "inter-frequency measurements" are requested by USIM, the ME shall, in the MeasurementReport, include IE "MeasResultListNR" in IE "measResults". The ME shall report Physical Cell ID,related RSRP,RSRQ,SINR and IE " cgi-Info" for the up to 8 strongest inter-frequency cells per monitored frequency, if available in the ME according to TS 38.331 [71] and TS 38.133 [72].

– If "inter-RAT (E-UTRAN)" are requested by the USIM, the ME shall, in the MeasurementReport, include IE " measResultListEUTRA" in IE "measResults". The ME shall report RSRP, RSRQ, SINR,Physical Cell ID and IE "cgi-Info" for the up to 8 strongest inter-RAT E-UTRAN/Satellite E-UTRAN cells per monitored frequency, if available in the ME according to TS 38.331 [71] and TS 38.133 [72].

– All other optional fields in the MeasurementReport shall be set to be absent.

Inter-frequency & inter-RAT (UTRAN): the ME can send more than one Network Measurement Results TLV object, each containing the results of one frequency. Each Network Measurement Results shall include 3 bytes with the frequency value coded as the ARFCN-ValueNR for Inter-frequency measurements or as the ARFCN-ValueUTRA for inter-RAT (UTRAN) measurements as defined in TS 38.331 [49], followed by the MeasurementReport information element as defined in the ASN.1 description of TS 38.331 [49], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServCell" with RSRP and RSRQ and the available SINR of the serving cell.

– If "inter-frequency measurements" are requested by the USIM, the ME shall, in the MeasurementReport, include IE " measResultListNR" in IE " measResults ". The ME shall report Physical Cell ID,related RSRP,RSRQ,SINR and IE " cgi-Info" for the up to 8 strongest inter-frequency cells per monitored frequency, if available in the ME according to TS 38.331 [71] and TS 38.133 [72].

– If "inter-RAT (UTRAN) measurements" are requested by the USIM, the ME shall, in the MeasurementReport, include IE "measResultListUTRA-FDD-r16" in IE "measResults". The ME shall report CPICH Ec/No, CPICH RSCP, Physical Cell ID for the up to 8 strongest (highest Ec/No value) inter-RAT UTRAN cells per monitored frequency, if available in the ME according to TS 38.331 [49] and TS 38.133 [50].

– All other optional fields in the MeasurementReport shall be set to be absent.

8.23 Default Text

See ETSI TS 102 223 [32] clause 8.23.

8.24 Items Next Action Indicator

See ETSI TS 102 223 [32] clause 8.24.

8.25 Event list

For the event list byte coding, the following value are defined in addition to those in ETSI TS 102 223 [32] clause 8.25:

– ’11’ = (I-)WLAN Access Status.

– ’12’ = Network Rejection

– ’15’ = CSG cell selection

– ’17’ = IMS Registration

– ’18’ = Incoming IMS data

– ‘1D’ = Data Connection Status Change

– ‘1E’ = CAG cell selection

– ‘1F’ = Slices Status Change

In addition, the following events are reserved for 3GPP for future usage:

– ’20’ = reserved for 3GPP (for future usage);

– ’21’ = reserved for 3GPP (for future usage);

– ’22’ = reserved for 3GPP (for future usage);

8.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 24.008 [9], 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).

8.27 Location status

See ETSI TS 102 223 [32] clause 8.27.

Editor’s note: It is FFS to specify the behavior in case of Satellite NG-RAN

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

If the terminal supports IMS:

– TI value is an identifier generated by the terminal to uniquely identify the call, regardless of the bearer of the call.

– TI flag is:

– Call connected event: "1"

– MT Call event: "0"

– Call disconnected event: "0" if caller disconnects the call, "1" otherwise

If the terminal does not support IMS:

– Call connected event: Transaction Identifier in the corresponding call connect message

– MT Call event: Transaction Identifier in the corresponding call setup message from the network

– Call disconnected event: Transaction Identifier in the corresponding disconnect message triggering the ENVELOPE command, or in case of radio link failure, the Transaction Identifier as in an ME initated disconnect message.

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

In case of Data Connection Status Change event, the transaction identifier is encoded as:

– TI value is an identifier generated by the terminal to uniquely identify the PDP or PDN or PDU data connection, regardless of the bearer of the connection.

– TI flag is always 0 in this data connection transaction identifier.

8.29 BCCH channel list

This information is only available when the ME is connected to a GSM access network.

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 44.018 [27]). 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)

8.30 Call control requested action

Byte(s)	Description	Length
1	Call control requested action tag	1
2 to (Y-1)+2	Length (X)	Y
(Y-1)+3 to (Y-1)+X+2	Call control requested action	X

– Call control requested action:

Contents:

– The action given in response to the ENVELOPE (CALL CONTROL). It may contain, in the same order as given by the UICC, the address or SS string, the capability configuration parameters, the called party sub-address and the alpha identifier, or the IMS Request-URI;

Coding:

– As described in clause 7.3.1.6, starting with the first optional element given in the response data to the ENVELOPE (CALL CONTROL).

8.31 Icon Identifier

See ETSI TS 102 223 [32] clause 8.31.

8.32 Item Icon Identifier list

See ETSI TS 102 223 [32] clause 8.32.

8.33 Card reader status

See ETSI TS 102 223 [32] clause 8.33.

8.34 Card ATR

See ETSI TS 102 223 [32] clause 8.34.

8.35 C-APDU

See ETSI TS 102 223 [32] clause 8.35.

8.36 R-APDU

See ETSI TS 102 223 [32] clause 8.36.

8.37 Timer identifier

See ETSI TS 102 223 [32] clause 8.37.

8.38 Timer value

See ETSI TS 102 223 [32] clause 8.38.

8.39 Date-Time and Time zone

See ETSI TS 102 223 [32] clause 8.39.

NOTE: coding is as for the Time Zone and Time information element in TS 24.008 [9], starting at octet 2.

8.40 AT Command

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 [12], which may contain single or concatenated AT commands.

8.41 AT Response

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 [12], 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 UICC then the AT Response string shall be truncated to this length by the ME.

8.42 BC Repeat indicator

Byte(s)	Description	Length
1	BC repeat indicator tag	1
2	Length = ’01’	1
3	BC repeat indicator values	1

Contents & coding:

– The BC repeat indicator is structured exactly as defined in 3GPP TS 24.008 [09].

8.43 Immediate response

See ETSI TS 102 223 [32] clause 8.43.

8.44 DTMF string

See ETSI TS 102 223 [32] clause 8.44.

8.45 Language

See ETSI TS 102 223 [32] clause 8.45.

8.46 Timing Advance

This information is only available when the ME is connected to a GSM access network.

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 44.018 [27], starting at octet 2 (the IEI is removed, as this information is duplicated by the data object tag).

8.47 Browser Identity

See ETSI TS 102 223 [32] clause 8.37.

8.48 URL

See ETSI TS 102 223 [32] clause 8.48.

8.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/UTRAN packet service/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN;

– ’04’ to ‘FF’ = RFU.

8.50 Provisioning File Reference

See ETSI TS 102 223 [32] clause 8.50.

8.51 Browser Termination Cause

See ETSI TS 102 223 [32] clause 8.51.

8.52 Bearer description

8.52.0 Structure of 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 ETSI TS 102 223 [32], the following are defined:

’01’ = CSD;

’02’ = GPRS / UTRAN packet service / E-UTRAN / Satellite E-UTRAN / NG-RAN / Satelitte NG-RAN.

’09’ = UTRAN packet service with extended parameters / HSDPA / E-UTRAN / Satellite E-UTRAN / NG-RAN / Satelitte NG-RAN.

‘0A’ = (I-)WLAN.

‘0B’ = E-UTRAN / Satellite E-UTRAN / NG-RAN / Satelitte NG-RAN / mapped UTRAN packet service.

‘0C’ = NG-RAN / Satellite NG-RAN

‘0D’ and ‘0E’ = reserved for 3GPP (for future usage)

– Bearer parameters coding: see the following clauses.

8.52.1 Bearer parameters for CSD

Contents: parameters specific to the bearer.

In this case X=3.

NOTE: 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 (see TS 22.002 [1]).

Coding:

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

Coding of Byte 4:

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

Coding of byte 5:

– Bearer service: same as the "name" subparameter defined in TS 27.007 [12].

Coding of Byte 6:

– Connection element: same as the "ce" subparameter defined in TS 27.007 [12].

8.52.2 Bearer parameters for GPRS / UTRAN Packet Service / E-UTRAN / Satellite E-UTRAN / NG-RAN / Satellite NG-RAN

Contents: parameters describing the Quality of Service (QoS) and the type of PDP. This is an element of the PDP context. These parameters can be used for 3GPP network packet service.

In this case X=6.

Coding:

– The following values are as defined in the TS 27.007 [12], for the "+CGQREQ" extended command. They are coded in hexadecimal.

Coding of Byte 4:

– Precedence class: same as the "precedence" subparameter, defined in TS 27.007 [12].

Coding of Byte 5:

– Delay class: same as the "delay" subparameter, defined in TS 27.007 [12].

Coding of Byte 6:

– Reliability class: same as the "reliability" subparameter, defined in TS 27.007 [12].

Coding of Byte 7:

– Peak throughput class: same as the "peak" subparameter, defined in TS 27.007 [12].

Coding of Byte 8:

– Mean throughput class: same as the "mean" subparameter, defined in TS 27.007 [12].

Coding of Byte 9:

– Packet data protocol type (PDP type):

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

’07’ = Non-IP (Transfer of Non-IP data to external packet data network);

all other values are reserved.

NOTE 1: The mapping between the UTRAN and E-UTRAN/Satellite E-UTRAN QoS parameters are defined in TS 23.203 [47].

NOTE 2: For NG-RAN and Satellite NG-RAN, QoS parameters are not applicable.

8.52.3 Bearer parameters for UTRAN Packet Service with extended parameters / HSDPA / E-UTRAN / Satellite E-UTRAN / NG-RAN / Satellite NG-RAN

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

In this case X=17.

Coding:

– The following values are as defined in the TS 27.007 [12], for the "+CGEQREQ" extended command. They are coded in hexadecimal.

Coding of Byte 4:

– Traffic class: same as the "Traffic class" subparameter, defined in TS 27.007 [12].

Coding of Byte 5 and 6:

– Maximum bitrate UL: same as the "Maximum bitrate UL" subparameter, defined in TS 27.007 [12]. The ME shall fill all octets with ‘FF’ in case the value exceeds the maximum that can be represented.

Coding of Byte 7 and 8:

– Maximum bitrate DL: same as the "Maximum bitrate DL" subparameter, defined in TS 27.007 [12]. The ME shall fill all octets with ‘FF’ in case the value exceeds the maximum that can be represented.

Coding of Byte 9 and 10:

– Guaranteed bitrate UL: same as the "Guaranteed bitrate UL" subparameter, defined in TS 27.007 [12]. The ME shall fill all octets with ‘FF’ in case the value exceeds the maximum that can be represented.

Coding of Byte 11 and 12:

– Guaranteed bitrate DL: same as the "Guaranteed bitrate DL" subparameter, defined in TS 27.007 [12]. The ME shall fill all octets with ‘FF’ in case the value exceeds the maximum that can be represented.

Coding of Byte 13:

– Delivery order: same as the "Delivery order" subparameter, defined in TS 27.007 [12].

Coding of Byte 14:

– Maximum SDU size: same as the "Maximum SDU size" subparameter, defined in TS 24.008 [9].

Coding of Byte 15:

– SDU error ratio: same as the "SDU error ratio" subparameter, defined in TS 24.008 [9], coded in the first 4 bits. The 4 most significant bits shall be set to 0.

Coding of Byte 16:

– Residual bit error ratio: same as the "Residual bit error ratio" subparameter, defined in TS 24.008 [9], coded in the first 4 bits. The 4 most significant bits shall be set to 0.

Coding of Byte 17:

– Delivery of erroneous SDUs: same as the "Delivery of erroneous SDUs" subparameter, defined in TS 27.007 [12].

Coding of Byte 18:

– Transfer delay: same as the "Transfer delay" subparameter, defined in TS 24.008 [9] , coded in the first 6 bits. The 2 most significant bits shall be set to 0.

Coding of Byte 19:

– Traffic handling priority: same as the "Traffic handling priority" subparameter, defined in TS 27.007 [12].

Coding of Byte 20:

– PDP_type: same as the "PDP type" subparameter, defined in TS 24.008 [9] for ETSI or IETF allocated address.

NOTE 1: HSDPA parameters and UTRAN Packet Service parameters are the same except for the maximum bitrate DL and the guaranteed bitrate DL, which can be higher for HSDPA (see TS 24.008 [9]).

NOTE 2: The mapping between the UTRAN and E-UTRAN QoS parameters are defined in TS 23.203 [47].

NOTE 3: For NG-RAN and Satellite NG-RAN, QoS parameters are not applicable.

8.52.4 Bearer parameters for (I-)WLAN

Content: parameters specific to the bearer. RFU.

In this case X=0

8.52.5 Bearer parameters for E-UTRAN / Satellite E-UTRAN / NG-RAN / Satellite NG-RAN / mapped UTRAN packet service

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

In this case X=2 or X=6 or X=10 or X=14, depending on the size of the "EPS quality of service" information element and the resource type (GBR or non-GBR).

In case of a non-GBR QCI, the QoS octets in the "EPS quality of service" information element are ignored by the UE, as specified in TS 24.301 [46]. In this case, the UE shall use X=2, passing only the QCI value.

Coding of Byte 4 to Byte X+2:

Byte 4 same as "octet 3" of the "EPS quality of service" information element, defined in TS 24.301 [46].

For a GBR QCI each subsequent Byte shall be present only if the corresponding next octet in the "EPS quality of service" information element is present. The coding of the corresponding bytes shall be the same.

Coding of Byte X+3:

– PDP_type: same as the "PDP type" subparameter, defined in TS 24.008 [9] for ETSI or IETF allocated address.

NOTE 1: the UICC should handle the cases with X > 14 gracefully, ignoring additional octets.

NOTE 2: For NG-RAN and Satellite NG-RAN, QoS parameters are not applicable.

8.52.6 Bearer parameters for NG-RAN / Satellite NG-RAN

Contents: parameters describing the type of PDU session. This is an element of the PDU session context.

When the ME has successfully established PDU session it shall include this Bearer parameter in the TERMINAL RESPONSE to inform the USIM.

The Bearer parameters for NR shall contain the PDU session type.

Length:

– 1 to X Bytes

Coding:

– Coding of Byte 4:

PDU session type: same as the "PDU session type", defined in Figure 9.11.4.11.1 of TS 24.501 [70].

– Coding of further Bytes:

RFU

8.53 Channel data

See ETSI TS 102 223 [32] clause 8.53.

8.54 Channel data length

See ETSI TS 102 223 [32] clause 8.54.

8.55 Buffer size

See ETSI TS 102 223 [32] clause 8.55.

8.56 Channel status

ETSI TS 102 223 [32] clause 8.56 applies, with the following addition.

In case of an OPEN CHANNEL for IMS, the coding is as follows:

Coding :

– byte 3 :

– Bit 1 to 3 : Channel identifier 1 to 7;

Channel identifier 0 means "no channel available".

– Bit 4 to 7 : RFU

– Bit 8 : 0 = BIP channel not established;

1 = BIP channel established.

– byte 4:

’00’ = No further info can be given;

’01’ = Not used;

’02’ = Not used;

’03’ = Not used;

’04’ = Not used;

’05’ = Link dropped (network failure or user cancellation);

all other values are reserved.

8.57 Card reader identifier

See ETSI TS 102 223 [32] clause 8.57.

8.58 Other Address

See ETSI TS 102 223 [32] clause 8.58.

8.59 UICC/ME interface transport level

See ETSI TS 102 223 [32] clause 8.59.

8.60 AID

See ETSI TS 102 223 [32] clause 8.60.

8.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 (GGSN) or a Packet Data Network Gateway (PDN-GW) or a User Plane Function (UPF), which provides interworking with an external packet data network. For GPRS, UTRAN packet service and E-UTRAN/Satellite E-UTRAN, the Network Access Name is an APN. For NG-RAN and Satellite NG-RAN, the Network Access Name is a DNN (which is coded same as an APN).

Coding:

– As defined in TS 23.003 [30].

8.62 Access Technology

See ETSI TS 102 223 [32] clause 8.61.

8.63 Display parameters

See ETSI TS 102 223 [32] clause 8.62.

8.64 Service Record

See ETSI TS 102 223 [32] clause 8.63.

8.65 Device Filter

See ETSI TS 102 223 [32] clause 8.64.

8.66 Service Search

See ETSI TS 102 223 [32] clause 8.65.

8.67 Attribute Information

See ETSI TS 102 223 [32] clause 8.66.

8.68 Service Availability

See ETSI TS 102 223 [32] clause 8.67.

8.69 Remote Entity Address

See ETSI TS 102 223 [32] clause 8.68.

8.70 Text Attribute

See ETSI TS 102 223 [32] clause 8.72.

8.71 Item Text Attribute List

See ETSI TS 102 223 [32] clause 8.73.

8.72 PDP context Activation parameters

Byte(s)	Description	Length
1	PDP context Activation parameters tag	1
2 to (Y+1)	Length (X)	Y
(Y+2) to (Y+X+1)	PDP context Activation parameters	X

The PDP context Activation parameters are coded as the ACTIVATE PDP CONTEXT REQUEST message, refer to TS 24.008 [9].

NOTE: If the "Protocol configuration options" in the ACTIVATE PDP CONTEXT REQUEST message is too large (i.e. greater than 229-L, where L is the sum of the length of the Requested QoS Information Element, the Requested PDP address Information Element, and the Access point name Information Element), the ME may decide not to include the "Protocol configuration options" and any subsequent information elements of the ACTIVATE PDP CONTEXT REQUEST message inside the "PDP context Activation parameters".

8.73 UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN Measurement Qualifier

This information is only available when the ME is connected to a UTRAN or an E-UTRAN or a NG-RAN or a Satellite NG-RAN.

Byte(s)	Description	Length
1	UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN Measurement Qualifier tag	1
2	Length (1)	1
3	UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN Measurement Qualifier	1

UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN Measurement Qualifier

Contents: Qualifier specific to the UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN NMR

Coding

’01’ UTRAN Intra-frequency measurements

’02’ UTRAN Inter-frequency measurements

’03’ UTRAN Inter-RAT (GERAN) measurements

’04’ UTRAN Inter-RAT (E-UTRAN) measurements

’05’ E-UTRAN/Satellite E-UTRAN Intra-frequency measurements

’06’ E-UTRAN/Satellite E-UTRAN Inter-frequency measurements

’07’ E-UTRAN/Satellite E-UTRAN Inter-RAT (GERAN) measurements

’08’ E-UTRAN/Satellite E-UTRAN Inter-RAT (UTRAN) measurements

’09’ E-UTRAN/Satellite E-UTRAN Inter-RAT (NR) measurements

‘0A’ NG-RAN/Satellite NG-RAN Intra-frequency measurements

‘0B’ NG-RAN/Satellite NG-RAN Inter-frequency measurements

‘0C’ NG-RAN/Satellite NG-RAN Inter-RAT (E-UTRAN) measurements

‘0D’ NG-RAN/Satellite NG-RAN Inter-RAT (UTRAN) measurements

All other values are reserved

8.74 Multimedia Message Reference

See ETSI TS 102 223 [32] clause 8.82.

8.75 Multimedia Message Identifier

See ETSI TS 102 223 [32] clause 8.83.

8.76 Multimedia Message Transfer status

See ETSI TS 102 223 [32] clause 8.84.

8.77 MM Content Identifier

In addition to ETSI TS 102 223 [32] clause 8.85, the codinf of the MM Content Data Object tag is done according to TS 31.102[14].

8.78 Multimedia Message Notification

See ETSI TS 102 223 [32] clause 8.86.

8.79 Last Envelope

See ETSI TS 102 223 [32] clause 8.87.

8.80 Frames Layout

See ETSI TS 102 223 [32] clause 8.78.

8.81 Frames Information

See ETSI TS 102 223 [32] clause 8.79.

8.82 Frames identifier

See ETSI TS 102 223 [32] clause 8.80.

8.83 I-WLAN Identifier

Byte(s)	Description	Length
1	I-WLAN Identifier tag	1
2	Length (X)	1
3 to (2+X)	WSID value	X

The WSID Value is coded as the WLAN Specific Identifier (WSID) defined in TS 24.234 [42].

8.84 (I-)WLAN Access Status

Byte(s)	Description	Length
1	(I-)WLAN Access Status tag	1
2	Length (1)	1
3	Access status	1

Coding of Access status:

– ’00’ = No current (I-)WLAN coverage;

– ’01’ = (I-)WLAN coverage available, no current connection;

– ’02’ = (I-)WLAN coverage available, connection on-going;

– ’03’ to’FF’= reserved values.

8.85 IMEISV

See ETSI TS 102 223 [32] clause 8.74.

8.86 Network search mode

See ETSI TS 102 223 [32] clause 8.75.

8.87 Battery State

See ETSI TS 102 223 [32] clause 8.76.

8.88 Browsing status

See ETSI TS 102 223 [32] clause 8.77.

8.89 Registry application data

See ETSI TS 102 223 [32] clause 8.88.

8.90 PLMNwAcT List

Byte(s)	Description	Length
1	PLMNwAcT List tag	1
2	Length (5n)	1
3 to 5	1^st PLMN Identifier(highest priority)	3
6 to 7	1^st PLMN Access Technology Identifier	2
:	:
(5n-2) to (5n)	nth PLMN Identifier (lowest priority)	3
(5n+1) to (5n+2)	nth PLMN Access Technology Identifier	2

Coding of PLMN Identifier:

As for PLMN within EF_PLMNwACT in TS 31.102 [14].

Coding of PLMN Access Technology Identifier:

As for Access Technology Identifier within EF_PLMNwACT in TS 31.102 [14].

8.91 Routing Area Identification

Byte(s)	Description	Length
1	Routing Area Information Tag	1
2	Length	1
3 – 5	Mobile Country & Network Codes (MCC & MNC)	3
6 – 7	Location Area Code (LAC)	2
8	Routing Area code (RAC)	1

When present, this object shall contain the Routing Area Identification information of rejecting network. The RAI is coded in the same manner as the value part of the Routing Area Identification information element as specified in TS 24.008 [9].

8.92 Update/Attach/Registration Type

Byte(s)	Description	Length
1	Update/Attach/Registration Type Tag	1
2	Length	1
3	Update/Attach/Registration Type	1

Contents:

– In the case of GERAN/UTRAN, the terminal shall use this information as a mechanism to indicate to the UICC the location updating type that was sent in the LOCATION UPDATING REQUEST message or the attach type that was sent in the GPRS Attach Request message or the update type that was sent in the Routing Area Updating Request message, as specified in TS 24.008 [9].

– In the case of E-UTRAN/Satellite E-UTRAN, the terminal shall use this information as a mechanism to indicate to the UICC the EPS attach type that was sent in the EMM ATTACH REQUEST message or the EPS update type that was sent in the TRACKING AREA UPDATE REQUEST message, as specified in TS 24.301 [46].

– In the case of NG-RAN/Satellite NG-RAN, the terminal shall use this information as a mechanism to indicate to the UICC the 5GS registration type that was sent in the REGISTRATION REQUEST message, as specified in TS 24.501 [70].

Coding:

– ’00’ = "Normal Location Updating" in the case of a Location Updating Request message;

– ’01’ = "Periodic Updating" in the case of a Location Updating Request message;

– ’02’ = "IMSI Attach" in the case of a Location Updating Request message;

– ’03’ = "GPRS Attach" in the case of a GPRS Attach Request message;

– ’04’ = "Combined GPRS/IMSI Attach" in the case of a GPRS Attach Request message;

– ’05’ = "RA Updating" in the case of a Routing Area Update Request message;

– ’06’ = "Combined RA/LA Updating" in the case of a Routing Area Update Request message;

– ’07’ = "Combined RA/LA Updating with IMSI Attach" in the case of a Routing Area Update Request message;

– ’08’ = "Periodic Updating" in the case of a Routing Area Update Request message

– ’09’ = "EPS Attach" in the case of an EMM ATTACH REQUEST message

– ‘0A’ = "Combined EPS/IMSI Attach" in the case of an EMM ATTACH REQUEST message

– ‘0B’ = "TA updating " in the case of an EMM TRACKING AREA UPDATE REQUEST message

– ‘0C’ = "Combined TA/LA updating" in the case of an EMM TRACKING AREA UPDATE REQUEST message

– ‘0D’ = "Combined TA/LA updating with IMSI attach" in the case of an EMM TRACKING AREA UPDATE REQUEST message

– ‘0E’ = "Periodic updating" in the case of an EMM TRACKING AREA UPDATE REQUEST message

– ‘0F’ = "Initial Registration" in the case of a 5GMM REGISTRATION REQUEST message

– ’10’ = "Mobility Registration updating" in the case of a 5GMM REGISTRATION REQUEST message

– ’11’ = "Periodic Registration updating" in the case of a 5GMM REGISTRATION REQUEST message

– All other values are reserved for future use

8.93 Rejection Cause Code

Byte(s)	Description	Length
1	Rejection Cause Code Tag	1
2	Length	1
3	Rejection Cause Code	1

For GERAN/UTRAN, in the case of a Location Updating Reject message, this object shall contain the Reject Cause as received in the Location Updating Reject message. The Reject Cause is coded in the same manner as the value part of the Reject Cause information element as specified in TS 24.008 [9]

For GERAN/UTRAN, in the case of a GPRS Attach Reject message or a Routing Area Update Reject message, this object shall contain the GMM Cause as received in the GPRS Attach Reject message or Routing Area Update Reject message. The GMM Cause is coded in the same manner as the value part of the GMM Cause information element as specified in TS 24.008 [9].

For E-UTRAN/Satellite E-UTRAN, in the case of an EMM ATTACH REJECT message or an EMM TRACKING AREA UPDATE REJECT message, this object shall contain the EMM Cause as received in the EMM ATTACH REJECT message or EMM TRACKING AREA UPDATE REJECT message. The EMM Cause is coded in the same manner as the value part of the EMM Cause information element as specified in TS 24.301 [46].

For NG-RAN/Satellite NG-RAN, in the case of a 5GMM REGISTRATION REJECT message, this object shall contain the 5GMM Cause as received in the 5GMM REGISTRATION REJECT message. The 5GMM Cause is coded in the same manner as the value part of the 5GMM Cause information element as specified in TS 24.501 [70].

8.94 Geographical Location Parameters

Byte(s)	Description	Length
1	Geographical Location Parameters Tag	1
2	Length	1
3	Horizontal accuracy	1
4	Vertical coordinate	1
5	Velocity	1
6	Preferred GAD shapes	1
7	Preferred NMEA sentences	1
8	Preferred Maximum Response Time	1

Horizontal accuracy:

Contents:

– the preferred horizontal accuracy.

Coding:

– ’81’ : horizontal accuracy not specified / best effort;

– ‘xx’ where ’00’ ≤ ‘xx’ ≤ ‘7F’: ‘xx’ represents the uncertainty for longitude and latitude as described in TS 23.032 [44]. A value in this range may be specified in the parameters of the "Geographical Location Request" command. The horizontal location error should be less than the error indicated by the horizontal accuracy with 67% confidence.

– All other values are reserved.

Vertical coordinate:

Contents:

– indicates if the vertical coordinate (altitude) is requested and potentially indicate the preferred vertical coordinate accuracy.

Coding:

– ’80’ : vertical coordinate is not requested (i.e. 2D location fix is acceptable);

– ’81’ : vertical coordinate is requested, (i.e. 3D location fix is preferred) but accuracy is not specified (best effort);

– ‘xx’ where ’00’ ≤ ‘xx’ ≤ ‘7F’: vertical coordinate is requested and ‘xx’ represents the altitude uncertainty as described in TS 23.032 [44]. A value in this range may be specified in the parameters of the "Geographical Location Request" command. The vertical location error should be less than the error indicated by the vertical accuracy with 67% confidence.

– All other values are reserved.

Velocity:

Contents:

– indicates if a velocity and a velocity uncertainty are requested. When a velocity type or an uncertainty are requested, the corresponding bit shall be set to 1. Otherwise the bit is set to 0. If b1 is set to zero, b2, b3 and b4 shall be ignored. If b2 is set to zero, b4 shall be ignored.

Coding:

Horizontal velocity requested

Vertical velocity requested

Uncertainty of horizontal velocity requested

Uncertainty of vertical velocity requested

RFU, bit = 0

Preferred GAD shapes:

Contents:

– the preferred GAD shape(s). When a GAD shape is indicated as "preferred", the corresponding bit shall be set to 1. Otherwise the bit is set to 0. The UICC application should be capable of extracting the needed information from all GAD shapes indicated in the bit map below.

Coding:

Ellipsoid point

Ellipsoid point with uncertainty circle

Ellipsoid point with uncertainty ellipse

Ellipsoid point with altitude

Polygon

Ellipsoid point with altitude and uncertainty ellipsoid

Ellipsoid arc

RFU, bit = 0

Preferred NMEA sentences:

Contents:

– the preferred NMEA sentence(s). When a NMEA sentence is indicated as "preferred", the corresponding bit shall be set to 1. Otherwise the bit is set to 0. The UICC application should be capable of extracting the needed information from all NMEA sentences indicated in the bit map below.

Coding:

$–RMC

$–GGA

$–GLL

$–GNS

RFU, bit = 0

Preferred Maximum Response Time:

Contents:

– indicates the preferred maximum response time. This hint may be used by the ME to make trade-offs between requirements for positioning accuracy and response time.

Coding:

– ‘xx’ where ’02’ ≤ ‘xx’ ≤ ’07’: 2^^‘xx’ represents the preferred maximum response time in seconds.

– All other values are reserved;

8.95 GAD shapes

Byte(s)	Description	Length
1	GAD shapes Tag	1
2	Length	1
3	Length of GAD shape	1
4 to X+3	GAD shape	X
X+4	Length of Velocity	1
X+5 to X+Y+4	Velocity	Y

Length of GAD shape:

Contents:

– the length of the GAD shape.

Coding:

– binary.

GAD shape:

Contents:

– universal geographical area description shape.

Coding:

– shape encoded as described in TS 23.032 [44] with the first byte of the shape (i.e. octet 1 containing the type shape) encoded on byte 4.

Length of Velocity:

Contents:

– the length of the velocity. This byte shall be set to ’00’ when the Velocity is not available.

Coding:

– binary.

Velocity:

Contents:

– velocity.

Coding:

– velocity encoded as described in TS 23.032 [44] with the first byte of the velocity (i.e. octet 1 containing the velocity shape) encoded on byte X+5.

8.96 NMEA sentence

Byte(s)	Description	Length
1	NMEA sentence Tag	1
2	Length	1
3 to X+2	NMEA sentence	X

NMEA sentence:

Contents:

– NMEA sentence as defined in IEC 61162-1 [45]. The ME should use one of the Preferred NMEA sentences indicated in the "Geographical Location Parameters" by the UICC. Otherwise, one of the NMEA sentences listed in clause 8.94 shall be used.

Coding:

ASCII;

8.97 PLMN List

Byte(s)	Description	Length
1	PLMN List tag	1
2	Length (3n)	1
3 to 5	1^st PLMN Identifier(highest priority)	3
:	:
(3n) to (3n+2)	nth PLMN Identifier (lowest priority)	3

Coding of PLMN Identifier:

As for PLMN within EF_OPLMNWLAN in TS 31.102 [14].

8.98 EPS PDN connection activation parameters

Byte(s)	Description	Length
1	EPS PDN connection Activation parameters tag	1
2 to (Y+1)	Length (X)	Y
(Y+2) to (Y+X+1)	EPS PDN connection Activation parameters	X

The EPS PDN connection Activation parameters are coded as the PDN CONNECTIVITY REQUEST message, refer to TS 24.301 [46].

NOTE: If the "Protocol configuration options" in the PDN CONNECTIVITY REQUEST message is too large (i.e. greater than 229-L, where L is the length of the Access point name Information Element), the ME may decide not to include the "Protocol configuration options" and any subsequent information elements of the PDN CONNECTIVITY REQUEST message inside the "EPS PDN connection Activation parameters".

8.99 Tracking Area Identification

Byte(s)	Description	Length
1	Tracking Area Identification Tag	1
2	Length	1
3 – 5	Mobile Country & Network Codes (MCC & MNC)	3
6 – X	Tracking Area Code (TAC) (See NOTE)	X – 5
NOTE: TAC is coded in 2 bytes for E-UTRAN/Satellite E-UTRAN and in 3 bytes for NG-RAN and Satellite NG‑RAN

This object shall contain the Tracking Area Identification information of rejecting network (i.e. MCC, MNC and TAC). The value part of this object is coded in the same manner as the value part of the Tracking Area Identity information element as specified in TS 24.301 [46] for E-UTRAN and Satellite E-UTRAN, or as the value part of the Tracking Area Identity information element as specified in TS 24.501 [70] for NG-RAN and Satellite NG-RAN.

This object shall contain the Tracking Area Identification information of rejecting network (i.e. MCC, MNC and TAC). The value part of this object is coded in the same manner as the value part of the Tracking Area Identity information element as specified in TS 24.301 [46] for E-UTRAN, or as the value part of the Tracking Area Identity information element as specified in TS 24.501 [70] for NG-RAN and Satellite NG-RAN.

8.100 CSG ID list identifier

Byte(s)	Description	Length
1	CSG ID list Identifier tag	1
2 to 1+Y	Length	Y
(Y+2) to (Y+X+1)	CSG ID List	X (X>1)

CSG ID List:

Description	Value	M/O	Length (bytes)
PLMN Tag	’80’	M	1
Length	A	M	1
PLMN	—	M	A
CSG ID and Name Tag	’81’	M	1
Length	B	M	1
CSG ID and Name	–	M	B

The CSG ID List TLV object shall contain one PLMN TLV object, Tag ’80’, followed by at least one CSG ID and Name TLV, Tag ’81’. The CSG ID List TLV object can contain more than one PLMN TLV objects. Each CSG ID and Name TLV belongs to the previous PLMN.

Coding of PLMN object (Tag ’80’):

Content:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

according to TS 24.008 [9].

Coding of CSG ID and name (Tag ’81’):

Content:

CSG ID and HNB Name

Coding:

1 to 4	CSG ID	M	4 bytes
5 to B	HNB Name	M	B-4 bytes

CSG ID: as in EF_ACSGL, in TS 31.102 [14].

HNB Name: as for HNB name in EF_HNBN in TS 31.102 [14].

8.101 CSG cell selection status

Byte(s)	Description	Length
1	CSG cell selection status tag	1
2	Length	1
3	CSG cell selection status	2

Coding of CSG cell selection status:

Byte 1 : general information

– ’00’ = not camped on a CSG or Hybrid cell in the Allowed CSG list or the Operator CSG list

– ’01’ = camped on a CSG or Hybrid cell of the Operator CSG list or Allowed CSG list

– other values are RFU

Byte 2 : additional information

This byte may contain additional information. If additional information is present, bit b1 shall be set to 1. If b1 is set to 0, this byte shall be ignored.

Bits b7 and b8 indicate the CSG selection mechanism used; see TS 25.304 [59] and TS 36.304 [60].

Additional information presence bit

RFU

Result of a manual CSG selection

Result of another CSG selection type

8.102 CSG ID

Byte(s)	Description	Length
1	CSG ID tag	1
2	Length	1
3 to X+2	CSG ID	X

Coding of CSG ID:

As for CSG ID in EF_ACSGL, in TS 31.102 [14]

8.103 HNB name

Byte(s)	Description	Length
1	HNB name tag	1
2	Length	1
3 to 2+X	HNB name	X

Coding of HNB name:

As for HNB name in EF_HNBN in TS 31.102 [14]

8.104 Activate descriptor

Not required by 3GPP.

8.105 Broadcast Network information

Not required by 3GPP.

8.106 Contactless state request

Not required by 3GPP.

8.107 Contactless functionality state

Not required by 3GPP.

8.108 IMS URI

Byte(s)	Description	Length
1	IMS URI Tag	1
2 to (Y+1)	Length	Y
(Y+2) to (Y+X+1)	IMS URI (IMPU)	X

Content :

IMS URI shall take the form of IMPU, which is SIP URI or tel URI, as defined in TS 24.229 [52]

Coding of IMS URI

As defined in TS 24.229 [52]

8.109 Extended registry application data

See ETSI TS 102 223 [32] clause 8.93.

8.110 IARI

Byte(s)	Description	Length
1	IARI Tag	1
2 to (Y+1)	Length	Y
(Y+2) to (Y+X+1)	IARI value	X
NOTE: X>0

Coding:

– IARI value shall be coded as specified in TS 24.229 [52].

8.111 IMPU List

Byte(s)	Description	Length
1	IMPU List Tag	1
2 to (Y+1)	Length	Y
Y+2	URI TLV tag	1
(Y+3) to (Y+Z+2)	URI TLV length	Z
..	:	…
…	…	…

Coding:

– For contents and syntax of URI TLV data object values see IETF RFC 3261 [53]. The URI shall be encoded to an octet string according to UTF-8 encoding rules as specified in IETF RFC 3629 [54]. The tag value of the URI TLV data object shall be ’80’.

8.112 IMS status code

Byte(s)	Description	Length
1	IMS Status-code Tag	1
2	Length	1
3 to X+2	IMS Status-code	X
NOTE: X>0

Content

– IMS status code as specified in 3GPP TS 24.229 [52]

Coding:

– Sequence of digits in ASCII format.

8.113 eCAT client profile

Not required by 3GPP.

8.114 eCAT client identity

Not required by 3GPP.

8.115 Encapsulated envelope type

Not required by 3GPP.

8.116 Void

8.117 Void

8.118 PLMN ID

Byte(s)	Description	Length
1	PLMN Identity Tag	1
2	Length	1
3 to 5	PLMN identity	3

PLMN ID TLV object shall contain PLMN identity Tag followed by Length and PLMN identity, containing Mobile Country Code (MCC) and Mobile Network Code (MNC), coded according to TS 24.008 [9].

8.119 E-UTRAN/ Satellite E-UTRAN Inter-frequency Network Measurement Results

Byte(s)	Description	Length
1	E-UTRAN/Satellite E-UTRAN Inter-frequency Network Measurement Results tag	1
2	Length (X) of bytes following	1
3 – 6	Frequency value	4
7 – to X+6	Measurement Report information	X

The ME can send more than one E-UTRAN/Satellite E-UTRAN Inter-frequency Network Measurement Results TLV object, each containing the results of one frequency. This TLV object shall be used only if the service "extended EARFCN" is available in the USIM Service Table (see TS 31.102 [14]).

The frequency value shall be coded as the ARFCN-ValueEUTRA-v9e0 as defined in TS 36.331 [49].

The Measurement Report information shall be coded as MeasurementReport information element defined in the ASN.1 description of TS 36.331 [49], according to the following:

– The "measId" field in the "measResults" shall be set to the value ‘1’.

– the ME shall include IE "measResultServCell" with RSRP and RSRQ of the serving cell.

– the ME shall, in the MeasurementReport, include IE " measResultListEUTRA" in IE "Measured Results". The ME shall report RSRP, RSRQ, Physical Cell ID and IE "cgi-Info" for the up to 6 strongest (highest RSRQ value) inter-frequency cells per monitored frequency, if available in the ME according to TS 36.331 [49] and TS 36.133 [50].

– All other optional fields in the MeasurementReport shall be set to be absent.

8.120 Call control result

Not required by 3GPP.

8.121 eCAT sequence number

Not required by 3GPP.

8.122 Encrypted TLV list

Not required by 3GPP.

8.123 MAC

Not required by 3GPP.

8.124 SA template

Not required by 3GPP.

8.125 CAT service list

Not required by 3GPP.

8.126 Refresh enforcement policy

See ETSI TS 102 223 [32] clause 8.103.

8.127 DNS Server Address

See ETSI TS 102 223 [32] clause 8.104.

8.128 ProSe Report Data

Byte(s)	Description	Length
1	ProSe Report Data Tag	1
2 to (X+1)	Length	X (1 or 2)
X+2 to X+1+Y	ProSe Report Data	Y

Contents:

– Contains the ProSe Report

Coding:

– Coded according to the XML schema defined in TS 24.334 [61] with <prose-pc3ch-message> element as the root element and one <USAGE_INFORMATION_REPORT_LIST> element inside it.

8.129 SSID

Byte(s)	Description	Length
1	SSID tag	1
2	Length (X)	1
3 to (2+X)	SSID Value	X ≤ 32

The SSID value is coded as specified for the SSID field in IEEE 802.11 [64].

8.130 BSSID

Byte(s)	Description	Length
1	BSSID tag	1
2	Length = ’06’	1
3 to 8	BSSID value	6

The BSSID value is coded as specified for the BSSID field in IEEE 802.11 [64].

8.131 HESSID

Byte(s)	Description	Length
1	HESSID tag	1
2	Length = ’06’	1
3 to 8	HESSID value	6

The HESSID value is coded as specified for the HESSID field in IEEE 802.11 [64].

8.132 Media Type

The Media Type data element indicates the media type of the communication.

Byte(s)	Description	Length
1	Media type tag	1
2	Length = ’01’	1
3	Media type value	1

Coding:

– The Media type value is coded as a bitmap

First byte (conversational communication):

Bit = 1 if the type of media is voice

Bit = 1 if the type of media is video

Bit = 0: RFU

8.133 IMS call disconnection cause

Byte(s)	Description	Length
1	IMS cause tag	1
2	Length = ’03’	1
3	Protocol	1
4 to 5	Cause	2

Protocol is the value of the protocol header field parameter in the Reason header field of the SIP message triggering the call disconnect event. It is coded on 1 byte as follows:

– ’01’ for SIP

– ’02’ for Q.850

– Other values are RFU

Cause is the value of the cause header field parameter in the Reason header field of the SIP message triggering the call disconnect event. It is coded as 2-bytes integer, e.g. a value of "603" translates to ‘025B’.

8.134 E-UTRAN/Satellite E-UTRAN Primary Timing Advance Information

Byte(s)	Description	Length
1	E-UTRAN/Satellite E-UTRAN Timing Advance tag	1
2	Length = ’03’	1
3	ME Status	1
4 – 5	E-UTRAN/Satellite E-UTRAN Primary Timing Advance value	2

Coding of ME status:

– ’00’ = ME is in the idle state;

– ’01’ = ME is not in idle state;

– ’02’ to ‘FF’ = reserved values.

The E-UTRAN/Satellite E-UTRAN Primary Timing Advance value is equal to the total "Timing offset between uplink and downlink radio frames at the UE, expressed in units of Ts" (Basic time unit), as defined in TS 36.211 [66].

If the ME has never been in E-UTRAN/Satellite E-UTRAN RRC connected mode on the current cell, the value of the E-UTRAN Primary Timing Advance shall be set to ‘FF FF’.

8.135 URI truncated

Byte(s)	Description	Length
1	URI truncated tag	1
2	Length = ‘0’	1

8.136 Extended Rejection Cause Code

Byte(s)	Description	Length
1	Extended Rejection Cause Code Tag	1
2	Length	1
3	Extended Rejection Cause Code	1

For E-UTRAN and Satellite E-UTRAN, in the case of an EMM ATTACH REJECT message or an EMM TRACKING AREA UPDATE REJECT message, if the Extended EMM Cause is available, then this object shall contain the Extended EMM Cause as received in the EMM ATTACH REJECT message or EMM TRACKING AREA UPDATE REJECT message. The Extended EMM Cause is coded in the same manner as the value part of the Extended EMM Cause information element as specified in TS 24.301 [46].

8.137 Data connection status

This data object shall contain the result of the PDP request procedure, PDN request procedure or PDU establishment procedure as defined in 3GPP TS 24.008 [9] for GERAN and UTRAN, 3GPP TS 24.301 [46] for E-UTRAN and Satellite E-UTRAN or 3GPP TS 24.501 [70] for NG-RAN and Satellite NG-RAN.

Byte(s)	Description	Length
1	Data connection status tag	1
2	Length = ’01’	1
3	Data connection status value	1

Data connection status value coding:

– ’00’ = Data connection successful; Successful means accepted by the network and completed by the device.

– ’01’ = Data connection rejected;

– ’02’ = Data connection dropped or deactivated.

– Other values RFU

8.138 Data connection type

This data object shall contain the type of procedure, PDP request procedure, PDN request procedure or PDU establishment procedure, as defined in 3GPP TS 24.008 [9] for GERAN and UTRAN, 3GPP TS 24.301 [46] for E-UTRAN and Satellite E-UTRAN or 3GPP TS 24.501 [70] for NG-RAN and Satellite NG-RAN.

Byte(s)	Description	Length
1	Data connection type tag	1
2	Length = ’01’	1
3	Data connection type	1

Data connection type coding:

– ’00’ = PDP connection

– ’01’ = PDN connection

– ’02’ = PDU connection

– Other values RFU

8.139 (E/5G)SM cause

This data object shall contain the value of the SM cause for PDP as defined in 3GPP TS 24.008 [9] for GERAN & UTRAN, the ESM Cause for PDN as defined in 3GPP TS 24.301 [46] for E-UTRAN and Satellite E-UTRAN or the 5GSM Cause for PDU as defined in 3GPP TS 24.501 [70] for NG-RAN and Satellite NG-RAN.

Byte(s)	Description	Length
1	(E/5G)SM cause tag	1
2	Length = ’01’	1
3	(E/5G)SM cause value	1

(E/5G)SM cause value coding:

For PDP procedures:

The coding of the cause is defined in 3GPP TS 24.008 [9]

– If the data connection (i.e. request procedure) is accepted, (E/5G)SM cause value is the SM cause value contained in the message for PS session management (i.e. ACTIVATE PDP CONTEXT ACCEPT message) coded as in TS 24.008 [9] clause 10.5.6.6a;

– If the data connection (i.e. request procedure) fails or is deactivated, (E/5G)SM cause value is the SM cause value contained in the messages for PS session management (i.e. ACTIVATE PDP CONTEXT REJECT message or REQUEST PDP CONTEXT ACTIVATION REJECT message or the DEACTIVATE PDP CONTEXT REQUEST message) and is coded as in TS 24.008 [9] clause 10.5.6.6.

For PDN procedures:

The coding of the cause is defined in 3GPP TS 24.301 [46].

– If the data connection (i.e. request procedure) fails or is deactivated, (E/5G)SM cause value is the ESM cause value contained in the message types for EPS session management (ie. in the PDN CONNECTIVITY REJECT message or ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message or the DEACTIVATE EPS BEARER CONTEXT REQUEST message) and is coded as in TS 24.301 [46] clause 9.9.4.4.

For PDU procedures:

The coding of the cause is defined in 3GPP TS 24.501 [70].

– If the data connection (i.e. request procedure) fails or is deactivated/released, (E/5G)SM cause value is the 5GSM cause value contained in the message types for 5GS session management (ie. in the PDU SESSION ESTABLISHMENT REJECT message or in the PDU SESSION RELEASE REQUEST message) and is coded as in TS 24.501 [70] clause 9.11.4.2.

8.140 IP address list

Byte(s)	Description	Length
1	IP address list Tag	1
2	Length	1
3 to (2+X)	Other address TLV object(s)	X

Content :

– List of IP addresses on the H(e)NB-network interface.

Coding:

– coding of Other address : see clause 8.58.

8.141 Surrounding macrocells

Byte(s)	Description	Length
1	Surrounding macrocell list Tag	1
2	Length	1
3 to 5	Access Technology TLV object(s)	3
6 to 6+X	Location information TLV object(s)	X

Content :

– List of surrounding macrocells, per access technology

Coding:

– coding of Access Technology : see clause 8.62.

– coding of Location Information : see clause 8.19.

8.142 PDP/PDN/PDU type

This data object shall contain the PDP, PDN or PDU Session type, as defined in 3GPP TS 24.008 [9] for GERAN and UTRAN, in 3GPP TS 24.301 [46] for E-UTRAN and Satellite E-UTRAN or in 3GPP TS 24.501 [70] for NG-RAN and Satellite NG-RAN.

Byte(s)	Description	Length
1	PDP/PDN/PDU type tag (see Note)	1
2	Length = ’01’	1
3	PDP/PDN type or PDU Session type	1
NOTE: Interpretation of the type depends on the value for the Access Technology (see clause 8.62)

PDP/PDN type coding:

– ’00’ = IPv4

– ’01’ = IPv6

– ’03’ = IPv4v6

– ’04’ = PPP

– ’05’ = non IP

All other values are RFU.

PDU Session type coding:

– ’00’ = IPv4

– ’01’ = IPv6

– ’03’ = IPv4v6

– ’04’ = Unstructured

– ’05’ = Ethernet

All other values are RFU.

8.143 PDU Session Establishment parameters

Byte(s)	Description	Length
1	PDU Session Establishment parameters tag	1
2 to (Y+1)	Length (Z+X)	Y
(Y+2) to (Y+Z+1)	DNN	Z
(Y+Z+2) to (Y+Z+X+1)	PDU Session Establishment parameters	X

The DNN is coded as specified in TS 24.501 [70] clause 9.11.2.1B.

The PDU Session Establishment parameters are coded as the PDU SESSION ESTABLISHMENT REQUEST message as specified in TS 24.501 [70].

NOTE: If the "SM PDU DN request container" in the PDU SESSION ESTABLISHMENT REQUEST message is too large (i.e. greater than 207-Z, where Z is the length of the DNN Information Element), the ME may decide not to include the "SM PDU DN request container" and any subsequent information elements of the PDU SESSION ESTABLISHMENT REQUEST message inside the "PDU Session Establishment parameters". If the "Extended protocol configuration options" in the PDU SESSION ESTABLISHMENT REQUEST message is too large (i.e. greater than 207-Z-L, where Z is the length of the DNN Information Element, L is the length of the "SM PDU DN request container", and L<=(207-Z)), the ME may decide not to include the "Extended protocol configuration options" inside the "PDU Session Establishment parameters".

8.144 NG-RAN/Satellite NG-RAN Primary Timing Advance Information

Byte(s)	Description	Length
1	NG-RAN/Satellite NG-RAN Timing Advance tag	1
2	Length = ’04’	1
3	ME Status	1
4 – 6	NG-RAN/Satellite NG-RAN Primary Timing Advance value	3

Coding of ME status:

– ’00’ = ME is in the idle state;

– ’01’ = ME is in inactive state;

– ’02’ = ME is in connect state;

– ’03’ to ‘FF’ = reserved values.

The NG-RAN/Satellite NG-RAN Primary Timing Advance value is equal to the total "Timing offset between uplink and downlink radio frames at the UE, expressed in units of Ts" (Basic time unit), as defined in TS 38.211 [73].

If the ME has never been in NG-RAN or Satellite NG-RAN RRC connected mode on the current cell, the value of the NG-RAN/Satellite NG-RAN Primary Timing Advance shall be set to ‘FF FF FF’.

8.145 Slices information

This data object contain a list of slice information.

Each slice information element is a S-NSSAI as specified in 3GPP TS 23.003 [30].

Byte(s)	Description	Length	M/O/C
1	Slices information tag	1	M
2	Length (X = 1 + 4n) of bytes following	1	M
3	Number of Served S-NSSAIs (n)	1	M
4 to 7	Served S-NSSAI 1 – SST + SD	4	C (see Note)
	…	…	C (see Note)
(X – 1) to (X + 2)	Served S-NSSAI n – SST + SD	4	C (see Note)
NOTE : if no Served S-NSSAI is available, this field is not present

Number of Served S-NSSAIs

– Contents:

– Value set to 0 if no Served S-NSSAI is available else this is the number of Served S-NSSAI that will be described in the following list.

Served S-NSSAI

– Coding:

S-NSSAI shall be coded on 32 bits.

– As specified in TS 23.003 [30], SD reserved value "no SD value associated with the SST" defined as hexadecimal FFFFFF shall be used to pad value to 32 bits

8.146 SOR-CMCI

Byte(s)	Description	Length
1	SOR-CMCI tag	1
2	Length (X)	2
4 to (3+X)	SOR-CMCI parameters	X

Coding of SOR-CMCI parameters:The SOR-CMCI parameters are coded as specified in TS 24.501 [70] clause 9.11.3.51 and start from octet (o+3) of SOR-CMCI as defined in Figure 9.11.3.51.7 of TS 24.501 [70].

8.147 CAG cell selection status

Byte(s)	Description	Length
1	CAG cell selection status tag	1
2	Length	1
3	CAG cell selection status	2

Coding of CAG cell selection status:

Byte 1 : general information

– ’00’ = not camped on a CAG cell

– ’01’ = camped on a CAG cell

– other values are RFU

Byte 2 : additional information

This byte may contain additional information. If additional information is present, bit b1 shall be set to 1. If b1 is set to 0, this byte shall be ignored.

Bits b7 and b8 indicate the CAG selection mechanism used; see TS 23.122 [7].

Additional information presence bit

RFU

Result of a manual CAG selection

Result of another CAG selection type

8.148 CAG information list

Byte(s)	Description	Length
1	CAG information list tag	1
2	Length	1
3 to X+2	CAG information list	X

Coding of CAG information list:

As for CAG information list entry in EF_CAG, in TS 31.102 [14]

8.149 CAG ID human-readable network name list

Byte(s)	Description	Length
1	CAG ID human-readable network name list tag	1
2 to 1 + X	Length	X
(X+2) to (Y+X+1)	CAG ID human-readable network name list	Y

CAG ID human-readable network name list:

Description	Value	M/O	Length (bytes)
1^st CAG ID human-readable network name Tag	’80’	M	1
Length	4+A1	M	1
1^st CAG ID	—	M	4
1^st CAG ID human-readable network name	–	M	A1
…
Last CAG ID human-readable network name Tag	’80’	O	1
Length	4+An	O	1
Last CAG ID	—	O	4
Last CAG ID human-readable network name	–	O	An

The CAG ID human-readable network name list shall contain at least one CAG ID human-readable network name Tag, Tag ’80’.

Coding of CAG ID human-readable network name (Tag ’80’):

Content:

CAG ID on 32 bits followed by CAG ID human-readable network name.

Coding of CAG ID:

The coding of the CAG-ID is defined as the CAG-Identifier in 3GPP TS 23.003 [30]

Coding of CAG ID human-readable network name:

The coding is HRNN coding as defined in TS 23.003 [30].

8.150 Slices status

Byte(s)	Description	Length
1	Slices status tag	1
2	Length	1
3	Slices status	1

Coding of Slices status:

– ’01’ = Allowed: if any S-NSSAI is included to or removed from Allowed NSSAI stored in a non-volatile memory in the ME when Allowed NSSAI IE is included in REGISTRATION ACCEPT or CONFIGURATION UPDATE COMMAND as specified in TS 24.501 [70]

– ’02’ = Rejected: if any S-NSSAI is included to or removed from Rejected NSSAI stored in a non-volatile memory in the ME when Rejected NSSAI or Extended Rejected NSSAI IEs are included in REGISTRATION ACCEPT, REGISTRATION REJECT, DEREGISTRATION REQUEST or CONFIGURATION UPDATE COMMAND as specified in TS 24.501 [70]

– other values are RFU

8.151 Rejected slices information

This data object contain a list of rejected slices information (S-NSSAI) and corresponding rejection cause.

Byte(s)	Description	Length	M/O/C
1	Rejected slices information tag	1	M
2	Length (X = 1 + 5n) of bytes following	1	M
3	Number of Rejected S-NSSAIs (n)	1	M
4 to 7	Rejected S-NSSAI 1 – SST + SD	4	C (see Note)
8	Rejection cause for S-NSSAI 1	1	C (see Note)
	…	…
(X – 2) to (X + 1)	Rejected S-NSSAI n – SST + SD	4	C (see Note)
X+2	Rejection cause for S-NSSAI n	1	C (see Note)
NOTE: If nor Rejected NSSAI IE neither Extended Rejected NSSAI IE is present in associated NAS messages this field is not present

Number of Rejected S-NSSAIs

– Contents:

– Value is 0 if nor Rejected NSSAI IE neither Extended Rejected NSSAI IE is present in associated NAS messages else this is the total number of Rejected S-NSSAIs included in Rejected NSSAI and Extended Rejected NSSAI IEs, if supported, as defined in 3GPP TS 24.501 [70] that will be described in the following list.

Rejected S-NSSAI

– Contents:

– this is the Rejected S-NSSAI

– Coding:

S-NSSAI shall be coded on 32 bits

– As specified in 3GPP TS 23.003 [30], SD reserved value "no SD value associated with the SST" defined as hexadecimal FFFFFF shall be used to padd value to 32 bits

Rejected cause for S-NSSAI

– Contents:

– this is the rejection cause for the corresponding S-NSSAI provided by network in associated NAS message

– Coding:

– If the Rejected S-NSSAI comes from Rejected NSSAI IE as specified in 3GPP TS 24.501 [70], this is Cause value from Figure 9.11.3.46.2 coded as defined in Table 9.11.3.46.1 but on one byte.

– If the Rejected S-NSSAI comes from Extended Rejected NSSAI IE if supported, as specified in 3GPP TS 24.501 [70], this is Cause value from Figure 9.11.3.75.4 coded as defined in Table 9.11.3.75.1 but on one byte.