9.9.3 EPS Mobility Management (EMM) information elements

24.3013GPPNon-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)Release 18Stage 3TS

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

9.9.3.0A Additional update result

The purpose of the Additional update result information element is to provide additional information about the result of a combined attach procedure or a combined tracking area updating procedure.

The Additional update result information element is coded as shown in figure 9.9.3.0A.1 and table 9.9.3.0A.1.

The Additional update result is a type 1 information element.

Additional update result IEI

Spare

Additional update result value

Octet 1

Figure 9.9.3.0A.1: Additional update result information element

Table 9.9.3.0A.1: Additional update result information element

Additional update result value (octet 1)

Bits
2	1
0	0	no additional information
0	1	CS Fallback not preferred
1	0	SMS only
1	1	reserved

Bits 4 and 3 of octet 1 are spare and shall all be coded as zero.

NOTE: Bits 4 and 3 of octet 1 were used in earlier versions of this release of this specification.

9.9.3.0B Additional update type

The purpose of the Additional update type information element is to provide additional information about the type of request for an attach or a tracking area updating procedure.

The Additional update type information element is coded as shown in figure 9.9.3.0B.1 and table 9.9.3.0B.1.

The Additional update type is a type 1 information element.

Additional update type

IEI

PNB-CIoT

SAF

AUTV

octet 1

Figure 9.9.3.0B.1: Additional update type information element

Table 9.9.3.0B.1: Additional update type information element

Additional update type value (AUTV) (octet 1)

Bit
1
0	no additional information. If received it shall be interpreted as request for combined attach or combined tracking area updating.
1	SMS only

"Signalling active" flag (SAF) (octet 1)

Bit
2
0	keeping the NAS signalling connection is not required after the completion of the tracking area updating procedure
1	keeping the NAS signalling connection is required after the completion of the tracking area updating procedure

Preferred CIoT network behaviour (PNB-CIoT) (octet 1)

Bit
4	3
0	0	no additional information
0	1	control plane CIoT EPS optimization
1	0	user plane CIoT EPS optimization
1	1	reserved

9.9.3.1 Authentication failure parameter

See clause 10.5.3.2.2 in 3GPP TS 24.008 [13].

9.9.3.2 Authentication parameter AUTN

See clause 10.5.3.1.1 in 3GPP TS 24.008 [13].

9.9.3.3 Authentication parameter RAND

See clause 10.5.3.1 in 3GPP TS 24.008 [13].

9.9.3.4 Authentication response parameter

The purpose of the Authentication response parameter information element is to provide the network with the authentication response calculated in the USIM.

The Authentication response parameter information element is coded as shown in figure 9.9.3.4.1 and table 9.9.3.4.1.

The Authentication response parameter is a type 4 information element with a minimum length of 6 octets and a maximum length of 18 octets.

In an EPS authentication challenge, the response calculated in the USIM (RES) is minimum 4 octets and may be up to 16 octets in length.

In a 5G AKA authentication challenge, the response calculated in the ME (RES*) is 16 octets in length.

8	7	6	5	4	3	2	1
Authentication response parameter IEI								octet 1
Length of Authentication response parameter contents								octet 2
RES or RES*								octet 3
								octet 18

Figure 9.9.3.4.1: Authentication response parameter information element

Table 9.9.3.4.1: Authentication response parameter information element

RES value (octet 3 to 18)

This contains the RES or RES*.

9.9.3.4A Ciphering key sequence number

See clause 10.5.1.2 in 3GPP TS 24.008 [13].

9.9.3.4B SMS services status

The purpose of the SMS services status information element is to indicate the status of availability for SMS services requested by the UE during the normal attach procedure or tracking area updating procedure.

The SMS services status information element is coded as shown in figure 9.9.3.4B.1 and table 9.9.3.4B.1.

The SMS services status is a type 1 information element.

SMS services status IEI

Spare

SMS services status value

octet 1

Figure 9.9.3.4B.1: SMS services status information element

Table 9.9.3.4B.1: SMS services status information element

SMS services status value (octet 1, bit 1 to 3)

Bits

3	2	1
0	0	0	SMS services not available
0	0	1	SMS services not available in this PLMN
0	1	0	Network failure
0	1	1	Congestion

All other values are unused and shall be treated as abnormal case, if received by the UE.

Bit 4 of octet 1 is spare and shall be coded as zero.

9.9.3.5 CSFB response

The purpose of the CSFB response information element is to indicate whether the UE accepts or rejects a paging for CS fallback.

The CSFB response information element is coded as shown in figure 9.9.3.5.1 and table 9.9.3.5.1.

The CSFB response is a type 1 information element.

CSFB response

IEI

spare

CSFB response value

octet 1

Figure 9.9.3.5.1: CSFB response information element

Table 9.9.3.5.1: CSFB response information element

CSFB response value (octet 1)

Bits
3	2	1
0	0	0	CS fallback rejected by the UE
0	0	1	CS fallback accepted by the UE

All other values are reserved.

9.9.3.6 Daylight saving time

See clause 10.5.3.12 in 3GPP TS 24.008 [13].

9.9.3.7 Detach type

The purpose of the Detach type information element is to indicate the type of detach.

The Detach type information element is coded as shown in figure 9.9.3.7.1 and table 9.9.3.7.1.

The Detach type is a type 1 information element.

Detach type

IEI

Switch

off

Type of detach

octet 1

Figure 9.9.3.7.1: Detach type information element

Table 9.9.3.7.1: Detach type information element

Type of detach (octet 1)

In the UE to network direction:
Bits
3	2	1
0	0	1	EPS detach
0	1	0	IMSI detach
0	1	1	combined EPS/IMSI detach
1	1	0	reserved
1	1	1	reserved

All other values are interpreted as "combined EPS/IMSI detach" in this version of the protocol.

In the network to UE direction:
Bits
3	2	1
0	0	1	re-attach required
0	1	0	re-attach not required
0	1	1	IMSI detach
1	1	0	reserved
1	1	1	reserved

All other values are interpreted as "re-attach not required" in this version of the protocol.

Switch off (octet 1)

In the UE to network direction:
Bit
4
0			normal detach
1			switch off

In the network to UE direction bit 4 is spare. The network shall set this bit to zero.

9.9.3.8 DRX parameter

See clause 10.5.5.6 in 3GPP TS 24.008 [13].

9.9.3.9 EMM cause

The purpose of the EMM cause information element is to indicate the reason why an EMM request from the UE is rejected by the network.

The EMM cause information element is coded as shown in figure 9.9.3.9.1 and table 9.9.3.9.1.

The EMM cause is a type 3 information element with 2 octets length.

8	7	6	5	4	3	2	1
EMM cause IEI								octet 1
Cause value								octet 2

Figure 9.9.3.9.1: EMM cause information element

Table 9.9.3.9.1: EMM cause information element

Cause value (octet 2)

Bits
8	7	6	5	4	3	2	1
0	0	0	0	0	0	1	0	IMSI unknown in HSS
0	0	0	0	0	0	1	1	Illegal UE
0	0	0	0	0	1	0	1	IMEI not accepted
0	0	0	0	0	1	1	0	Illegal ME
0	0	0	0	0	1	1	1	EPS services not allowed
0	0	0	0	1	0	0	0	EPS services and non-EPS services not allowed
0	0	0	0	1	0	0	1	UE identity cannot be derived by the network
0	0	0	0	1	0	1	0	Implicitly detached
0	0	0	0	1	0	1	1	PLMN not allowed
0	0	0	0	1	1	0	0	Tracking Area not allowed
0	0	0	0	1	1	0	1	Roaming not allowed in this tracking area
0	0	0	0	1	1	1	0	EPS services not allowed in this PLMN
0	0	0	0	1	1	1	1	No Suitable Cells In tracking area
0	0	0	1	0	0	0	0	MSC temporarily not reachable
0	0	0	1	0	0	0	1	Network failure
0	0	0	1	0	0	1	0	CS domain not available
0	0	0	1	0	0	1	1	ESM failure
0	0	0	1	0	1	0	0	MAC failure
0	0	0	1	0	1	0	1	Synch failure
0	0	0	1	0	1	1	0	Congestion
0	0	0	1	0	1	1	1	UE security capabilities mismatch
0	0	0	1	1	0	0	0	Security mode rejected, unspecified
0	0	0	1	1	0	0	1	Not authorized for this CSG
0	0	0	1	1	0	1	0	Non-EPS authentication unacceptable
0	0	0	1	1	1	1	1	Redirection to 5GCN required
0	0	1	0	0	0	1	1	Requested service option not authorized in this PLMN
0	0	1	0	0	1	1	1	CS service temporarily not available
0	0	1	0	1	0	0	0	No EPS bearer context activated
0	0	1	0	1	0	1	0	Severe network failure
0	1	0	0	1	1	1	0	PLMN not allowed to operate at the present UE location
0	1	0	1	1	1	1	1	Semantically incorrect message
0	1	1	0	0	0	0	0	Invalid mandatory information
0	1	1	0	0	0	0	1	Message type non-existent or not implemented
0	1	1	0	0	0	1	0	Message type not compatible with the protocol state
0	1	1	0	0	0	1	1	Information element non-existent or not implemented
0	1	1	0	0	1	0	0	Conditional IE error
0	1	1	0	0	1	0	1	Message not compatible with the protocol state
0	1	1	0	1	1	1	1	Protocol error, unspecified

Any other value received by the mobile station shall be treated as 0110 1111, "protocol error, unspecified". Any other value received by the network shall be treated as 0110 1111, "protocol error, unspecified".

9.9.3.10 EPS attach result

The purpose of the EPS attach result information element is to specify the result of an attach procedure.

The EPS attach result information element is coded as shown in figure 9.9.3.10.1 and table 9.9.3.10.1.

The EPS attach result is a type 1 information element.

EPS attach result IEI

Spare

EPS attach result value

octet 1

Figure 9.9.3.10.1: EPS attach result information element

Table 9.9.3.10.1: EPS attach result information element

EPS attach result value (octet 1)
Bits
3	2	1
0	0	1	EPS only
0	1	0	combined EPS/IMSI attach

All other values are reserved.

Bit 4 of octet 1 is spare and shall be coded as zero.

9.9.3.11 EPS attach type

The purpose of the EPS attach type information element is to indicate the type of the requested attach.

The EPS attach type information element is coded as shown in figure 9.9.3.11.1 and table 9.9.3.11.1.

The EPS attach type is a type 1 information element.

EPS attach type IEI

Spare

EPS attach type value

octet 1

Figure 9.9.3.11.1: EPS attach type information element

Table 9.9.3.11.1: EPS attach type information element

EPS attach type value (octet 1)
Bits
3	2	1
0	0	1	EPS attach
0	1	0	combined EPS/IMSI attach
0	1	1	EPS RLOS attach (NOTE)
1	1	0	EPS emergency attach
1	1	1	reserved

All other values are unused and shall be interpreted as "EPS attach", if received by the network.

Bit 4 of octet 1 is spare and shall be coded as zero.

NOTE: "EPS RLOS attach" shall be interpreted as "EPS attach" by a network not supporting attach for access to RLOS.

9.9.3.12 EPS mobile identity

The purpose of the EPS mobile identity information element is to provide either the IMSI, the GUTI or the IMEI.

The EPS mobile identity information element is coded as shown in figures 9.9.3.12.1 and 9.9.3.12.2 and table 9.9.3.12.1.

The EPS mobile identity is a type 4 information element with a minimum length of 3 octets and a maximum length of 13 octets.

8	7	6	5	4	3	2	1
EPS mobile identity IEI								octet 1
Length of EPS mobile identity contents								octet 2
1	1	1	1	odd/ even indic	Type of identity			octet 3
MCC digit 2				MCC digit 1				octet 4
MNC digit 3				MCC digit 3				octet 5
MNC digit 2				MNC digit 1				octet 6
MME Group ID								octet 7
MME Group ID (continued)								octet 8
MME Code								octet 9
M-TMSI								octet 10
M-TMSI (continued)								octet 11
M-TMSI (continued)								octet 12
M-TMSI (continued)								octet 13

Figure 9.9.3.12.1: EPS mobile identity information element for type of identity "GUTI"

8	7	6	5	4	3	2	1
EPS mobile identity IEI								octet 1
Length of EPS mobile identity contents								octet 2
Identity digit 1				odd/ even indic	Type of identity			octet 3
Identity digit p+1				Identity digit p				octet 4*

Figure 9.9.3.12.2: EPS mobile identity information element for type of identity "IMSI" or "IMEI"

Table 9.9.3.12.1: EPS mobile identity information element

Type of identity (octet 3) Bits
3	2	1
0	0	1	IMSI
1	1	0	GUTI
0	1	1	IMEI
All other values are reserved.

Odd/even indication (octet 3) Bit
4
0			even number of identity digits and also when the GUTI is used
1			odd number of identity digits

Identity digits (octet 4 etc) For the IMSI, this field is coded using BCD coding. If the number of identity digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111".

For the GUTI, then bits 5 to 8 of octet 3 are coded as "1111", octet 4 through 6 contain the MCC and MNC values as specified below, and bit 8 of octet 7 is the most significant bit and bit 1 of the last octet the least significant bit for the subsequent fields. The required fields for the GUTI are as defined in 3GPP TS 23.003 [2].
MCC, Mobile country code (octet 4, octet 5 bits 1 to 4) The MCC field is coded as in ITU-T Recommendation E.212 [30], annex A.

MNC, Mobile network code (octet 5 bits 5 to 8, octet 6) The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, bits 5 to 8 of octet 5 shall be coded as "1111". The MCC and MNC digits are coded as octets 6 to 8 of the Temporary Mobile Group Identity IE in figure 10.5.154 of 3GPP TS 24.008 [13].

For the IMEI, this field is coded using BCD coding. The format of the IMEI is described in 3GPP TS 23.003 [2].

9.9.3.12A EPS network feature support

The purpose of the EPS network feature support information element is to indicate whether certain features are supported by the network.

The EPS network feature support information element is coded as shown in figure 9.9.3.12A.1 and table 9.9.3.12A.1.

The EPS network feature support is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets.

If the network does not include octet 4 or octet 5 as defined below in the present version of the protocol, then the UE shall interpret this as a receipt of an information element with all bits of octet 4 and 5 coded as zero.

EPS network feature support IEI

octet 1

Length of EPS network feature support contents

octet 2

CP CIoT

ERw/oPDN

ESR
PS

CS-LCS

EPC-LCS

EMC BS

IMS VoPS

octet 3

15 bearers

IWKN26

RestrictDCNR

RestrictEC

ePCO

HC-CP CIoT

S1-U data

UP CIoT

octet 4*

Spare

PTCC

RPR

PIV

NCR

octet 5*

Figure 9.9.3.12A.1: EPS network feature support information element

Table 9.9.3.12A.1: EPS network feature support information element

IMS voice over PS session indicator (IMS VoPS) (octet 3, bit 1)

Bit
1
0		IMS voice over PS session in S1 mode not supported
1		IMS voice over PS session in S1 mode supported

Emergency bearer services indicator (EMC BS) (octet 3, bit 2)

Bit
2
0		emergency bearer services in S1 mode not supported
1		emergency bearer services in S1 mode supported

Location services indicator in EPC (EPC-LCS) (octet 3, bit 3)

Bit
3
0		location services via EPC not supported
1		location services via EPC supported

Location services indicator in CS (CS-LCS) (octet 3, bit 4 to 5)

Bit
5	4
0	0	no information about support of location services via CS domain is available
0	1	location services via CS domain supported
1	0	location services via CS domain not supported
1	1	reserved

Support of EXTENDED SERVICE REQUEST for packet services (ESRPS) (octet 3, bit 6)

Bit
6
0		network does not support use of EXTENDED SERVICE REQUEST to request for packet services
1		network supports use of EXTENDED SERVICE REQUEST to request for packet services

EMM REGISTERED without PDN connectivity (ERw/oPDN) (octet 3, bit 7)
This bit indicates the capability for EMM-REGISTERED without PDN connection
Bit
7
0		EMM-REGISTERED without PDN connection not supported
1		EMM-REGISTERED without PDN connection supported

Control plane CIoT EPS optimization (CP CIoT) (octet 3, bit 8)
This bit indicates the capability for control plane CIoT EPS optimization
Bit
8
0		Control plane CIoT EPS optimization not supported
1		Control plane CIoT EPS optimization supported

User plane CIoT EPS optimization (UP CIoT) (octet 4, bit 1)
This bit indicates the capability for user plane CIoT EPS optimization
Bit
1
0		User plane CIoT EPS optimization not supported
1		User plane CIoT EPS optimization supported

S1-u data transfer (S1-U data) (octet 4, bit 2)
This bit indicates the capability for S1-u data transfer. This bit shall be considered only if the Control plane CIoT EPS optimization (CP CIoT) bit (octet 3, bit 8) is set to 1. If the Control plane CIoT EPS optimization (CP CIoT) bit (octet 3, bit 8) is set to 0, the UE shall assume S1-u data transfer is supported.
Bit
2
0		S1-u data transfer not supported
1		S1-u data transfer supported

Header compression for control plane CIoT EPS optimization (HC-CP CIoT) (octet 4, bit 3)
This bit indicates the capability for header compression for control plane CIoT EPS optimization
Bit
3
0		Header compression for control plane CIoT EPS optimization not supported
1		Header compression for control plane CIoT EPS optimization supported

Extended protocol configuration options (ePCO) (octet 4, bit 4) This bit indicates the support of the extended protocol configuration options IE.
Bit
4
0		Extended protocol configuration options IE not supported
1		Extended protocol configuration options IE supported

Restriction on enhanced coverage (RestrictEC) (octet 4, bit 5) This bit indicates if the use of enhanced coverage is restricted or not.
Bit
5
0		Use of enhanced coverage is not restricted
1		Use of enhanced coverage is restricted
Restriction on the use of dual connectivity with NR (RestrictDCNR) (octet 4, bit 6) This bit indicates if the use of dual connectivity with NR is restricted or not.
Bit
6
0		Use of dual connectivity with NR is not restricted
1		Use of dual connectivity with NR is restricted
Interworking without N26 interface indicator (IWK N26) (octet 4, bit 7) This bit indicates whether interworking without N26 interface is supported.
Bit
7
0		Interworking without N26 interface not supported
1		Interworking without N26 interface supported
Signalling for a maximum number of 15 EPS bearer contexts (15 bearers) (octet 4, bit 8) This bit indicates the support of signalling for a maximum number of 15 EPS bearer contexts.
Bit
8
0		Signalling for a maximum number of 15 EPS bearer contexts not supported
1		Signalling for a maximum number of 15 EPS bearer contexts supported

NAS signalling connection release (NCR) (octet 5, bit 1)
This bit indicates the support of NAS signalling connection release.
Bit
1
0		NAS signalling connection release not supported
1		NAS signalling connection release supported

Paging indication for voice services (PIV) (octet 5, bit 2)
This bit indicates the support of paging indication for voice services.
Bit
2
0		paging indication for voice services not supported
1		paging indication for voice services supported

Reject paging request (RPR) (octet 5, bit 3)
This bit indicates the support of reject paging request.
Bit
3
0		reject paging request not supported
1		reject paging request supported

Paging restriction (PR) (octet 5, bit 4)
This bit indicates the support of paging restriction.
Bit
4
0		paging restriction not supported
1		paging restriction supported

Paging timing collision control (PTCC) (octet 5, bit 5)
This bit indicates the support of paging timing collision control.
Bit
5
0		paging timing collision control not supported
1		paging timing collision control supported

Bits 6 to 8 in octet 5 are spare and shall be coded as zero if included.

9.9.3.13 EPS update result

The purpose of the EPS update result information element is to specify the result of the associated updating procedure.

The EPS update result information element is coded as shown in figure 9.9.3.13.1 and table 9.9.3.13.1.

The EPS update result is a type 1 information element.

EPS update result

IEI

Spare

EPS update result

value

octet 1

Figure 9.9.3.13.1: EPS update result information element

Table 9.9.3.13.1: EPS update result information element

EPS update result value (octet 1, bit 1 to 3)
Bits
3	2	1
0	0	0	TA updated
0	0	1	combined TA/LA updated
1	0	0	TA updated and ISR activated (NOTE)
1	0	1	combined TA/LA updated and ISR activated (NOTE)

All other values are reserved.

Bit 4 of octet 1 is spare and shall be coded as zero.

NOTE: Values "TA updated and ISR activated" and "combined TA/LA updated and ISR activated" are used only for a UE supporting also A/Gb or Iu mode.

9.9.3.14 EPS update type

The purpose of the EPS update type information element is to specify the area the updating procedure is associated with.

The EPS update type information element is coded as shown in figure 9.9.3.14.1 and table 9.9.3.14.1.

The EPS update type is a type 1 information element.

EPS update type

IEI

"Active" flag

EPS update type

Value

octet 1

Figure 9.9.3.14.1: EPS update type information element

Table 9.9.3.14.1: EPS update type information element

EPS update type value (octet 1, bit 1 to 3)

Bits

3	2	1
0	0	0	TA updating
0	0	1	combined TA/LA updating
0	1	0	combined TA/LA updating with IMSI attach
0	1	1	periodic updating
1	0	0	unused; shall be interpreted as "TA updating", if received by the network.
1	0	1	unused; shall be interpreted as "TA updating", if received by the network.

All other values are reserved.

"Active" flag (octet 1, bit 4)
Bit

4
0			No bearer establishment requested
1			Bearer establishment requested

9.9.3.15 ESM message container

The purpose of the ESM message container information element is to enable piggybacked transfer of a single ESM message within an EMM message. The ESM message included in this IE shall be coded as specified in clause 8.3, i.e. without NAS security header.

The ESM message container information element is coded as shown in figure 9.9.3.15.1 and table 9.9.3.15.1.

The ESM message container is a type 6 information element.

8	7	6	5	4	3	2	1
ESM message container IEI								octet 1
Length of ESM message container contents								octet 2
								octet 3
								octet 4
ESM message container contents
								octet n

Figure 9.9.3.15.1: ESM message container information element

Table 9.9.3.15.1: ESM message container information element

ESM message container contents (octet 4 to octet n); Max value of 65535 octets

This IE can contain any ESM PDU as defined in clause 8.3.

9.9.3.16 GPRS timer

See clause 10.5.7.3 in 3GPP TS 24.008 [13].

9.9.3.16A GPRS timer 2

See clause 10.5.7.4 in 3GPP TS 24.008 [13].

9.9.3.16B GPRS timer 3

See clause 10.5.7.4a in 3GPP TS 24.008 [13].

9.9.3.17 Identity type 2

See clause 10.5.5.9 in 3GPP TS 24.008 [13].

9.9.3.18 IMEISV request

See clause 10.5.5.10 in 3GPP TS 24.008 [13].

9.9.3.19 KSI and sequence number

The purpose of the KSI and sequence number information element is to provide the network with the key set identifier (KSI) value of the current EPS security context and the 5 least significant bits of the NAS COUNT value applicable for the message including this information element.

The KSI and sequence number information element is coded as shown in figure 9.9.3.19.1 and table 9.9.3.19.1.

The KSI and sequence number is a type 3 information element with a length of 2 octets.

8	7	6		5	4	3	2	1
KSI and sequence number IEI									octet 1
KSI			Sequence number (short)						octet 2

Figure 9.9.3.19.1: KSI and sequence number information element

Table 9.9.3.19.1: KSI and sequence number information element

Sequence number (short) (octet 2, bit 1 to 5)

This field contains the 5 least significant bits of the NAS COUNT value applicable when this message is sent.

KSI (octet 2, bit 6 to 8)

This field contains the key set identifier value, as specified in bit 1 to 3 of octet 1 of the NAS key set identifier information element. (see clause 9.9.3.21.)

9.9.3.20 MS network capability

See clause 10.5.5.12 in 3GPP TS 24.008 [13].

9.9.3.20A MS network feature support

See clause 10.5.1.15 in 3GPP TS 24.008 [13].

9.9.3.21 NAS key set identifier

The NAS key set identifier is allocated by the network.

The NAS key set identifier information element is coded as shown in figure 9.9.3.21.1 and table 9.9.3.21.1.

The NAS key set identifier is a type 1 information element.

8	7	6	5	4	3	2	1
NAS key set identifier IEI				TSC	NAS key set identifier			octet 1

Figure 9.9.3.21.1: NAS key set identifier information element

Table 9.9.3.21.1: NAS key set identifier information element

Type of security context flag (TSC) (octet 1)

Bit
4
0			native security context (for KSI_ASME or KSI_AMF)
1			mapped security context (for KSI_SGSN or KSI_AMF)

TSC does not apply for NAS key set identifier value "111".

NAS key set identifier (octet 1)

Bits
3	2	1

0	0	0
through			possible values for the NAS key set identifier
1	1	0

1	1	1	no key is available (UE to network);
			reserved (network to UE)

9.9.3.22 NAS message container

This information element is used to encapsulate the SMS messages transferred between the UE and the network. The NAS message container information element is coded as shown in figure 9.9.3.22.1 and table 9.9.3.22.1.

The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length of 253 octets.

8	7	6	5	4	3	2	1
NAS message container IEI								octet 1
Length of NAS message container contents								octet 2
								octet 3
NAS message container contents
								octet n

Figure 9.9.3.22.1: NAS message container information element

Table 9.9.3.22.1: NAS message container information element

NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in clause 7.2 in 3GPP TS 24.011 [13A].

9.9.3.23 NAS security algorithms

The purpose of the NAS security algorithms information element is to indicate the algorithms to be used for ciphering and integrity protection.

The NAS security algorithms information element is coded as shown in figure 9.9.3.23.1 and table 9.9.3.23.1.

The NAS security algorithms is a type 3 information element with a length of 2 octets.

NAS security algorithms IEI

octet 1

spare

Type of ciphering algorithm

spare

Type of integrity protection algorithm

octet 2

Figure 9.9.3.23.1: NAS security algorithms information element

Table 9.9.3.23.1: NAS security algorithms information element

Type of integrity protection algorithm (octet 2, bit 1 to 3)
Bits
3	2	1
0	0	0	EPS integrity algorithm EIA0 (null integrity protection algorithm)
0	0	1	EPS integrity algorithm 128-EIA1
0	1	0	EPS integrity algorithm 128-EIA2
0	1	1	EPS integrity algorithm 128-EIA3
1	0	0	EPS integrity algorithm EIA4
1	0	1	EPS integrity algorithm EIA5
1	1	0	EPS integrity algorithm EIA6
1	1	1	EPS integrity algorithm EIA7

Type of ciphering algorithm (octet 2, bit 5 to 7)
Bits
7	6	5
0	0	0	EPS encryption algorithm EEA0 (null ciphering algorithm)
0	0	1	EPS encryption algorithm 128-EEA1
0	1	0	EPS encryption algorithm 128-EEA2
0	1	1	EPS encryption algorithm 128-EEA3
1	0	0	EPS encryption algorithm EEA4
1	0	1	EPS encryption algorithm EEA5
1	1	0	EPS encryption algorithm EEA6
1	1	1	EPS encryption algorithm EEA7

Bit 4 and 8 of octet 2 are spare and shall be coded as zero.

9.9.3.24 Network name

See clause 10.5.3.5a in 3GPP TS 24.008 [13].

9.9.3.24A Network resource identifier container

See clause 10.5.5.31 in 3GPP TS 24.008 [13].

9.9.3.25 Nonce

The purpose of the Nonce information element is to transfer a 32-bit nonce value to support deriving a new mapped EPS security context.

The Nonce information element is coded as shown in figure 9.9.3.25.1 and table 9.9.3.25.1.

The Nonce is a type 3 information element with a length of 5 octets.

Nonce IEI

octet 1

Nonce value

octet 2

octet 5

Figure 9.9.3.25.1: Nonce information element

Table 9.9.3.25.1: Nonce information element

Nonce value (octet 2 to 5)

This field contains the binary representation of the nonce. Bit 8 of octet 2 represents the most significant bit of the nonce and bit 1 of octet 5 the least significant bit.

9.9.3.25A Paging identity

The purpose of the Paging identity information element is to indicate the identity used for paging for non-EPS services.

The Paging identity information element is coded as shown in figure 9.9.3.25A.1 and table 9.9.3.25A.1.

The Paging identity is a type 3 information element with 2 octets length.

8	7	6	5	4	3	2	1
Paging identity IEI								octet 1
0	0	0	0	0	0	0	Paging identity value	octet 2
spare							Paging identity value	octet 2

Figure 9.9.3.25A.1: Paging identity information element

Table 9.9.3.25A.1: Paging identity information element

Paging identity value (octet 2)

Bit

0 IMSI

1 TMSI

9.9.3.26 P-TMSI signature

See clause 10.5.5.8 in 3GPP TS 24.008 [13].

9.9.3.26A Extended EMM cause

The purpose of the extended EMM cause information element is to indicate additional information associated with the EMM cause.

The Extended EMM cause information element is coded as shown in figure 9.9.3.26A.1 and table 9.9.3.26A.1.

The Extended EMM cause is a type 1 information element.

Extended EMM cause IEI

Spare

NB-IoT

allowed

EPS optimization info

E-UTRAN allowed

Octet 1

Figure 9.9.3.26A.1: Extended EMM cause information element

Table 9.9.3.26A.1: Extended EMM cause information element

E-UTRAN allowed value (octet 1, bit 1)

Bit
1
0		E-UTRAN allowed
1		E-UTRAN not allowed

EPS optimization info (octet 1, bit 2)

Bit
0		No EPS optimization information
1		requested EPS optimization not supported

NB-IoT allowed value (octet 1, bit 3)

Bit
0		NB-IoT allowed
1		NB-IoT not allowed

Bit 4 of octet 1 is spare and shall be coded as zero.

9.9.3.27 Service type

The purpose of the Service type information element is to specify the purpose of the service request procedure.

The Service type information element is coded as shown in figure 9.9.3.27.1 and table 9.9.3.27.1.

The Service type is a type 1 information element.

Service type

IEI

Service type value

octet 1

Figure 9.9.3.27.1: Service type information element

Table 9.9.3.27.1: Service type information element

Service type value (octet 1)

Service type value
Bits
4	3	2	1
0	0	0	0	mobile originating CS fallback or 1xCS fallback
0	0	0	1	mobile terminating CS fallback or 1xCS fallback
0	0	1	0	mobile originating CS fallback emergency call or 1xCS fallback emergency call
0	0	1	1	unused; shall be interpreted as "mobile originating CS fallback or 1xCS fallback", if received by the network
0	1	0	0	unused; shall be interpreted as "mobile originating CS fallback or 1xCS fallback", if received by the network
1	0	0	0	packet services via S1
1	0	0	1	unused; shall be interpreted as "packet services via S1", if received by the network
1	0	1	0	unused; shall be interpreted as "packet services via S1", if received by the network
1	0	1	1	unused; shall be interpreted as "packet services via S1", if received by the network

All other values are reserved.

9.9.3.28 Short MAC

The purpose of the Short MAC information element is to protect the integrity of a SERVICE REQUEST message.

The integrity protection shall include octet 1 and 2 of the SERVICE REQUEST message. For the used algorithm and other input parameters to the algorithm see clause 9.5. Only the 2 least significant octets of the resulting message authentication code are included in the information element.

The Short MAC information element is coded as shown in figure 9.9.3.28.1 and table 9.9.3.28.1.

The Short MAC is a type 3 information element with a length of 3 octets.

8	7	6	5	4	3	2	1
Short MAC IEI								octet 1
Short MAC value								octet 2
Short MAC value (continued)								octet 3

Figure 9.9.3.28.1: Short MAC information element

Table 9.9.3.28.1: Short MAC information element

Short MAC value (octet 2 and 3)

This field contains the 2 least significant octets of the message authentication code calculated for the SERVICE REQUEST message. Bit 1 of octet 3 contains the least significant bit, and bit 8 of octet 2 the most significant bit of these 2 octets.

9.9.3.29 Time zone

See clause 10.5.3.8 in 3GPP TS 24.008 [13].

9.9.3.30 Time zone and time

See clause 10.5.3.9 in 3GPP TS 24.008 [13].

9.9.3.31 TMSI status

See clause 10.5.5.4 in 3GPP TS 24.008 [13].

9.9.3.32 Tracking area identity

The purpose of the Tracking area identity information element is to provide an unambiguous identification of tracking areas within the area covered by the 3GPP system.

The Tracking area identity information element is coded as shown in figure 9.9.3.32.1 and table 9.9.3.32.1.

The Tracking area identity is a type 3 information element with a length of 6 octets.

8	7	6	5	4	3	2	1
Tracking area identity IEI								octet 1
MCC digit 2				MCC digit 1				octet 2
MNC digit 3				MCC digit 3				octet 3
MNC digit 2				MNC digit 1				octet 4
TAC								octet 5
TAC (continued)								octet 6

Figure 9.9.3.32.1: Tracking area identity information element

Table 9.9.3.32.1: Tracking area identity information element

MCC, Mobile country code (octet 2 and 3)

The MCC field is coded as in ITU-T Rec. E212 [30], annex A.

If the TAI is deleted the MCC and MNC shall take the value from the deleted TAI.

In abnormal cases, the MCC stored in the UE can contain elements not in the set {0, 1 … 9}. In such cases the UE should transmit the stored values using full hexadecimal encoding. When receiving such an MCC, the network shall treat the TAI as deleted.

MNC, Mobile network code (octet 3 bits 5 to 8, octet 4)

The coding of this field is the responsibility of each administration, but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. For PCS 1900 for NA, Federal regulation mandates that a 3-digit MNC shall be used. However a network operator may decide to use only two digits in the MNC in the TAI over the radio interface. In this case, bits 5 to 8 of octet 3 shall be coded as "1111". Mobile equipment shall accept a TAI coded in such a way.

In abnormal cases, the MNC stored in the UE can have:

– digit 1 or 2 not in the set {0, 1 … 9}, or

– digit 3 not in the set {0, 1 … 9, F} hex.

In such cases the UE shall transmit the stored values using full hexadecimal encoding. When receiving such an MNC, the network shall treat the TAI as deleted.

The same handling shall apply for the network, if a 3-digit MNC is sent by the UE to a network using only a 2-digit MNC.

TAC, Tracking area code (octet 5 and 6)

In the TAC field bit 8 of octet 5 is the most significant bit and bit 1 of octet 6 the least significant bit.

The coding of the tracking area code is the responsibility of each administration except that two values are used to mark the TAC, and hence the TAI, as deleted. Coding using full hexadecimal representation may be used. The tracking area code consists of 2 octets.

If a TAI has to be deleted then all bits of the tracking area code shall be set to one with the exception of the least significant bit which shall be set to zero. If a USIM is inserted in a mobile equipment with the tracking area code containing all zeros, then the mobile equipment shall recognise this TAC as part of a deleted TAI.

9.9.3.33 Tracking area identity list

The purpose of the Tracking area identity list information element is to transfer a list of tracking areas from the network to the UE.

The coding of the information element allows combining different types of lists. The lists of type "00" and "01" allow a more compact encoding, when the different TAIs are sharing the PLMN identity.

The Tracking area identity list information element is coded as shown in figure 9.9.3.33.1, figure 9.9.3.33.2, figure 9.9.3.33.3, figure 9.9.3.33.4 and table 9.9.3.33.1.

The Tracking area identity list is a type 4 information element, with a minimum length of 8 octets and a maximum length of 98 octets. The list can contain a maximum of 16 different tracking area identities.

8	7	6	5	4	3	2	1
Tracking area identity list IEI								octet 1
Length of tracking area identity list contents								octet 2
Partial tracking area identity list 1								octet 3 octet i
Partial tracking area identity list 2								octet i+1* octet l*
…								octet l+1* octet m*
Partial tracking area identity list p								octet m+1* octet n*

Figure 9.9.3.33.1: Tracking area identity list information element

8	7	6	5	4	3	2	1
0 Spare	Type of list		Number of elements					octet 1
MCC digit 2				MCC digit 1				octet 2
MNC digit 3				MCC digit 3				octet 3
MNC digit 2				MNC digit 1				octet 4
TAC 1								octet 5
TAC 1 (continued)								octet 6
…								…
…								…
TAC k								octet 2k+3*
TAC k (continued)								octet 2k+4*

Figure 9.9.3.33.2: Partial tracking area identity list – type of list = "00"

8	7	6	5	4	3	2	1
0 Spare	Type of list		Number of elements					octet 1
MCC digit 2				MCC digit 1				octet 2
MNC digit 3				MCC digit 3				octet 3
MNC digit 2				MNC digit 1				octet 4
TAC 1								octet 5
TAC 1 (continued)								octet 6

Figure 9.9.3.33.3: Partial tracking area identity list – type of list = "01"

8	7	6	5	4	3	2	1
0 Spare	Type of list		Number of elements					octet 1
MCC digit 2				MCC digit 1				octet 2
MNC digit 3				MCC digit 3				octet 3
MNC digit 2				MNC digit 1				octet 4
TAC 1								octet 5
TAC 1 (continued)								octet 6
MCC digit 2				MCC digit 1				octet 7*
MNC digit 3				MCC digit 3				octet 8*
MNC digit 2				MNC digit 1				octet 9*
TAC 2								octet 10*
TAC 2 (continued)								octet 11*
…
…
MCC digit 2				MCC digit 1				octet 5k-3*
MNC digit 3				MCC digit 3				octet 5k-2*
MNC digit 2				MNC digit 1				octet 5k-1*
TAC k								octet 5k*
TAC k (continued)								octet 5k+1*

Figure 9.9.3.33.4: Partial tracking area identity list – type of list = "10"

Table 9.9.3.33.1: Tracking area identity list information element

Value part of the Tracking area identity list information element (octet 3 to n)

The value part of the Tracking area identity list information element consists of one or several partial tracking area identity lists. The length of each partial tracking area identity list can be determined from the ‘type of list’ field and the ‘number of elements’ field in the first octet of the partial tracking area identity list.
The UE shall store the complete list received. If more than 16 TAIs are included in this information element, the UE shall store the first 16 TAIs and ignore the remaining octets of the information element.


Partial tracking area identity list:

Type of list (octet 1)
Bits
7	6
0	0	list of TACs belonging to one PLMN, with non-consecutive TAC values
0	1	list of TACs belonging to one PLMN, with consecutive TAC values
1	0	list of TAIs belonging to different PLMNs (see NOTE)

All other values are reserved.

Number of elements (octet 1)
Bits
5	4	3	2	1
0	0	0	0	0	1 element
0	0	0	0	1	2 elements
0	0	0	1	0	3 elements
…
0	1	1	0	1	14 elements
0	1	1	1	0	15 elements
0	1	1	1	1	16 elements

All other values are unused and shall be interpreted as 16, if received by the UE.

Bit 8 of octet 1 is spare and shall be coded as zero.


For type of list = "00" and number of elements = k:

octet 2 to 4 contain the MCC+MNC, and
for j = 1, k:
octet 2j+3 and 2j+4 contain the TAC of the j-th TAI belonging to the partial list,

For type of list = "01" and number of elements = k:

octet 2 to 4 contain the MCC+MNC, and
octet 5 and 6 contain the TAC of the first TAI belonging to the partial list.
The TAC values of the other k-1 TAIs are TAC+1, TAC+2, …, TAC+k-1.

For type of list = "10" and number of elements = k:

for j = 1, k.
octet 5j-3 to 5j-1 contain the MCC+MNC, and
octet 5j and 5j+1 contain the TAC of the j-th TAI belonging to the partial list.


MCC, Mobile country code

The MCC field is coded as in ITU-T Recommendation E.212 [30], annex A.

MNC, Mobile network code

The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, MNC digit 3 shall be coded as "1111".

TAC, Tracking area code

In the TAC field bit 8 of the first octet is the most significant bit and bit 1 of second octet the least significant bit.
The coding of the tracking area code is the responsibility of each administration. Coding using full hexadecimal representation may be used. The tracking area code consists of 2 octets.

NOTE: If the "list of TAIs belonging to different PLMNs" is used, the PLMNs included in the list need to be present in the list of "equivalent PLMNs".

9.9.3.34 UE network capability

The purpose of the UE network capability information element is to provide the network with information concerning aspects of the UE related to EPS or interworking with GPRS and 5GS. The contents might affect the manner in which the network handles the operation of the UE. The UE network capability information indicates general UE characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on.

The UE network capability information element is coded as shown in figure 9.9.3.34.1 and table 9.9.3.34.1.

The UE network capability is a type 4 information element with a minimum length of 4 octets and a maximum length of 15 octets.

NOTE: The requirements for the support of UMTS security algorithms in the UE are specified in 3GPP TS 33.102 [18], and the requirements for the support of EPS security algorithms in 3GPP TS 33.401 [19].

UE network capability IEI

octet 1

Length of UE network capability contents

octet 2

EEA0

128-

EEA1

128-

EEA2

128-

EEA3

EEA4

EEA5

EEA6

EEA7

octet 3

EIA0

128-

EIA1

128-

EIA2

128-

EIA3

EIA4

EIA5

EIA6

EPS-UPIP

octet 4

UEA0

UEA1

UEA2

UEA3

UEA4

UEA5

UEA6

UEA7

octet 5*

UCS2

UIA1

UIA2

UIA3

UIA4

UIA5

UIA6

UIA7

octet 6*

ProSe-dd

ProSe

H.245-ASH

ACC-CSFB

LPP

LCS

1xSR

VCC

octet 7*

ePCO

HC-CP CIoT

ERw/oPDN

S1-U data

UP CIoT

CP CIoT

Prose-relay

ProSe-dc

octet 8*

15 bearers

SGC

N1mode

DCNR

CP backoff

RestrictEC

V2X PC5

multipleDRB

octet 9*

RPR

PIV

NCR

V2X NR-PC5

UP-MT-EDT

CP-MT-EDT

WUSA

RACS

octet 10*

Spare

PTCC

octet 11*

octet 12* -15*

Spare

Figure 9.9.3.34.1: UE network capability information element

Table 9.9.3.34.1: UE network capability information element

EPS encryption algorithms supported (octet 3)

EPS encryption algorithm EEA0 supported (octet 3, bit 8)

EPS encryption algorithm EEA0 not supported

EPS encryption algorithm EEA0 supported

EPS encryption algorithm 128-EEA1 supported (octet 3, bit 7)

EPS encryption algorithm 128-EEA1 not supported

EPS encryption algorithm 128-EEA1 supported

EPS encryption algorithm 128-EEA2 supported (octet 3, bit 6)

EPS encryption algorithm 128-EEA2 not supported

EPS encryption algorithm 128-EEA2 supported

EPS encryption algorithm 128-EEA3 supported (octet 3, bit 5)

EPS encryption algorithm 128-EEA3 not supported

EPS encryption algorithm 128-EEA3 supported

EPS encryption algorithm EEA4 supported (octet 3, bit 4)

EPS encryption algorithm EEA4 not supported

EPS encryption algorithm EEA4 supported

EPS encryption algorithm EEA5 supported (octet 3, bit 3)

EPS encryption algorithm EEA5 not supported

EPS encryption algorithm EEA5 supported

EPS encryption algorithm EEA6 supported (octet 3, bit 2)

EPS encryption algorithm EEA6 not supported

EPS encryption algorithm EEA6 supported

EPS encryption algorithm EEA7 supported (octet 3, bit 1)

EPS encryption algorithm EEA7 not supported

EPS encryption algorithm EEA7 supported

EPS integrity algorithms supported (octet 4)

EPS integrity algorithm EIA0 supported (octet 4, bit 8)

EPS integrity algorithm EIA0 not supported

EPS integrity algorithm EIA0 supported

EPS integrity algorithm 128-EIA1 supported (octet 4, bit 7)

EPS integrity algorithm 128-EIA1 not supported

EPS integrity algorithm 128-EIA1 supported

EPS integrity algorithm 128-EIA2 supported (octet 4, bit 6)

EPS integrity algorithm 128-EIA2 not supported

EPS integrity algorithm 128-EIA2 supported

EPS integrity algorithm 128-EIA3 supported (octet 4, bit 5)

EPS integrity algorithm 128-EIA3 not supported

EPS integrity algorithm 128-EIA3 supported

EPS integrity algorithm EIA4 supported (octet 4, bit 4)

EPS integrity algorithm EIA4 not supported

EPS integrity algorithm EIA4 supported

EPS integrity algorithm EIA5 supported (octet 4, bit 3)

EPS integrity algorithm EIA5 not supported

EPS integrity algorithm EIA5 supported

EPS integrity algorithm EIA6 supported (octet 4, bit 2)

EPS integrity algorithm EIA6 not supported

EPS integrity algorithm EIA6 supported

EPS-UPIP supported (octet 4, bit 1)

EPS-UPIP not supported

EPS-UPIP supported

UMTS encryption algorithms supported (octet 5)

UMTS encryption algorithm UEA0 supported (octet 5, bit 8)

UMTS encryption algorithm UEA0 not supported

UMTS encryption algorithm UEA0 supported

UMTS encryption algorithm UEA1 supported (octet 5, bit 7)

UMTS encryption algorithm UEA1 not supported

UMTS encryption algorithm UEA1 supported

UMTS encryption algorithm UEA2 supported (octet 5, bit 6)

UMTS encryption algorithm UEA2 not supported

UMTS encryption algorithm UEA2 supported

UMTS encryption algorithm UEA3 supported (octet 5, bit 5)

UMTS encryption algorithm UEA3 not supported

UMTS encryption algorithm UEA3 supported

UMTS encryption algorithm UEA4 supported (octet 5, bit 4)

UMTS encryption algorithm UEA4 not supported

UMTS encryption algorithm UEA4 supported

UMTS encryption algorithm UEA5 supported (octet 5, bit 3)

UMTS encryption algorithm UEA5 not supported

UMTS encryption algorithm UEA5 supported

UMTS encryption algorithm UEA6 supported (octet 5, bit 2)

UMTS encryption algorithm UEA6 not supported

UMTS encryption algorithm UEA6 supported

UMTS encryption algorithm UEA7 supported (octet 5, bit 1)

UMTS encryption algorithm UEA7 not supported

UMTS encryption algorithm UEA7 supported

UCS2 support (UCS2) (octet 6, bit 8)

This information field indicates the likely treatment of UCS2 encoded character strings by the UE.

The UE has a preference for the default alphabet (defined in

3GPP TS 23.038 [3]) over UCS2 (see ISO/IEC 10646 [29]).

The UE has no preference between the use of the default alphabet and

the use of UCS2.

UMTS integrity algorithms supported (octet 6)

UMTS integrity algorithm UIA1 supported (octet 6, bit 7)

UMTS integrity algorithm UIA1 not supported

UMTS integrity algorithm UIA1 supported

UMTS integrity algorithm UIA2 supported (octet 6, bit 6)

UMTS integrity algorithm UIA2 not supported

UMTS integrity algorithm UIA2 supported

UMTS integrity algorithm UIA3 supported (octet 6, bit 5)

UMTS integrity algorithm UIA3 not supported

UMTS integrity algorithm UIA3 supported

UMTS integrity algorithm UIA4 supported (octet 6, bit 4)

UMTS integrity algorithm UIA4 not supported

UMTS integrity algorithm UIA4 supported

UMTS integrity algorithm UIA5 supported (octet 6, bit 3)

UMTS integrity algorithm UIA5 not supported

UMTS integrity algorithm UIA5 supported

UMTS integrity algorithm UIA6 supported (octet 6, bit 2)

UMTS integrity algorithm UIA6 not supported

UMTS integrity algorithm UIA6 supported

UMTS integrity algorithm UIA7 supported (octet 6, bit 1)

UMTS integrity algorithm UIA7 not supported

UMTS integrity algorithm UIA7 supported

NF capability (octet 7, bit 1)

notification procedure not supported

notification procedure supported

1xSRVCC capability (octet 7, bit 2)

SRVCC from E-UTRAN to cdma2000^® 1x CS not supported

SRVCC from E-UTRAN to cdma2000^® 1x CS supported

(see 3GPP TS 23.216 [8])

Location services (LCS) notification mechanisms capability (octet 7, bit 3)

LCS notification mechanisms not supported

LCS notification mechanisms supported (see 3GPP TS 24.171 [13C])

LTE Positioning Protocol (LPP) capability (octet 7, bit 4)

LPP not supported

LPP supported (see 3GPP TS 36.355 [22A])

Access class control for CSFB (ACC-CSFB) capability (octet 7, bit 5)

eNodeB-based access class control for CSFB not supported

eNodeB-based access class control for CSFB supported

(see 3GPP TS 22.011 [1A])

H.245 After SRVCC Handover capability (H.245-ASH) (octet 7, bit 6)

This bit indicates the capability for H.245 with support and use of pre-defined codecs, and if needed, H.245 codec negotiation after SRVCC handover.

H.245 after SRVCC handover capability not supported

H.245 after SRVCC handover capability supported

(see 3GPP TS 23.216 [8])

ProSe (octet 7, bit 7)

This bit indicates the capability for ProSe.

ProSe not supported

ProSe supported

ProSe direct discovery (ProSe-dd) (octet 7, bit 8)

This bit indicates the capability for ProSe direct discovery.

ProSe direct discovery not supported

ProSe direct discovery supported

ProSe direct communication (ProSe-dc) (octet 8, bit 1)

This bit indicates the capability for ProSe direct communication.

ProSe direct communication not supported

ProSe direct communication supported

ProSe UE-to-network-relay (ProSe-relay) (octet 8, bit 2)

This bit indicates the capability to act as a ProSe UE-to-network relay

Acting as a ProSe UE-to-network relay not supported

Acting as a ProSe UE-to-network relay supported

Control plane CIoT EPS optimization (CP CIoT) (octet 8, bit 3)

This bit indicates the capability for control plane CIoT EPS optimization.

Control plane CIoT EPS optimization not supported

Control plane CIoT EPS optimization supported

User plane CIoT EPS optimization (UP CIoT) (octet 8, bit 4)

This bit indicates the capability for user plane CIoT EPS optimization.

User plane CIoT EPS optimization not supported

User plane CIoT EPS optimization supported

S1-u data transfer (S1-U data) (octet 8, bit 5)

This bit indicates the capability for S1-u data transfer. This bit shall be considered only if the Control plane CIoT EPS optimization (CP CIoT) bit (octet 8, bit 3) is set to 1. If the Control plane CIoT EPS optimization (CP CIoT) bit (octet 8, bit 3) is set to 0, the MME shall assume S1-u data transfer is supported by the UE.

S1-U data transfer not supported

S1-U data transfer supported

EMM-REGISTERED without PDN connection (ERw/oPDN) (octet 8, bit 6)

This bit indicates the capability for EMM REGISTERED without PDN connectivity.

EMM-REGISTERED without PDN connection not supported

EMM-REGISTERED without PDN connection supported

Header compression for control plane CIoT EPS optimization (HC-CP CIoT) (octet 8, bit 7)

This bit indicates the capability for header compression for control plane CIoT EPS optimization.

Header compression for control plane CIoT EPS optimization not supported

Header compression for control plane CIoT EPS optimization supported

Extended protocol configuration options (ePCO) (octet 8, bit 8)

This bit indicates the support of the extended protocol configuration options IE.

Extended protocol configuration options IE not supported

Extended protocol configuration options IE supported

Multiple DRB support (multipleDRB) (octet 9, bit 1)

This bit indicates the capability to support multiple user plane radio bearers (see 3GPP TS 36.306 [44], 3GPP TS 36.331 [22]) in NB-S1 mode.

Multiple DRB not supported

Multiple DRB supported

V2X communication over PC5 (V2X PC5) (octet 9, bit 2)

This bit indicates the capability for V2X communication over E-UTRA-PC5.

V2X communication over E-UTRA-PC5 not supported

V2X communication over E-UTRA-PC5 supported

Restriction on use of enhanced coverage support (RestrictEC) (octet 9, bit 3)

This bit indicates the capability to support restriction on use of enhanced coverage.

Restriction on use of enhanced coverage not supported

Restriction on use of enhanced coverage supported

Control plane data backoff support (CP backoff) (octet 9, bit 4)

This bit indicates the support of back-off timer for transport of user data via the control plane..

back-off timer for transport of user data via the control plane not supported

back-off timer for transport of user data via the control plane supported

Dual connectivity with NR (DCNR) (octet 9, bit 5)

This bit indicates the capability for dual connectivity with NR.

dual connectivity with NR not supported

dual connectivity with NR supported

N1 mode supported (N1mode) (octet 9, bit 6)

This bit indicates the capability for N1 mode for 3GPP access.

N1 mode for 3GPP access not supported

N1 mode for 3GPP access supported

Service gap control (SGC) (octet 9, bit 7)

This bit indicates the capability for service gap control

service gap control not supported

service gap control supported

Signalling for a maximum number of 15 EPS bearer contexts (15 bearers) (octet 9, bit 8)

This bit indicates the support of signalling for a maximum number of 15 EPS bearer contexts

Signalling for a maximum number of 15 EPS bearer contexts not supported

Signalling for a maximum number of 15 EPS bearer contexts supported

Radio capability signalling optimisation (RACS) capability (octet 10, bit 1)

This bit indicates the capability for RACS.

RACS not supported

RACS supported

Wake-up signal (WUS) assistance (octet 10, bit 2)

This bit indicates the support of wake-up signal assistance

WUS assistance not supported

WUS assistance supported

Control plane Mobile Terminated-Early Data Transmission (CP-MT-EDT) (octet 10, bit 3)

This bit indicates the support of control plane Mobile Terminated-Early Data Transmission

Control plane Mobile Terminated-Early Data Transmission not supported

Control plane Mobile Terminated-Early Data Transmission supported

User plane Mobile Terminated-Early Data Transmission (UP-MT-EDT) (octet 10, bit 4)

This bit indicates the support of user plane Mobile Terminated-Early Data Transmission

User plane Mobile Terminated-Early Data Transmission not supported

User plane Mobile Terminated-Early Data Transmission supported

V2X communication over NR-PC5 (V2X NR-PC5) (octet 10, bit 5)

This bit indicates the capability for V2X communication over NR-PC5.

V2X communication over NR-PC5 not supported

V2X communication over NR-PC5 supported

NAS signalling connection release (NCR) (octet 10, bit 6)

This bit indicates the support of NAS signalling connection release.

NAS signalling connection release not supported

NAS signalling connection release supported

Paging indication for voice services (PIV) (octet 10, bit 7)

This bit indicates the support of paging indication for voice services.

paging indication for voice services not supported

paging indication for voice services supported

Reject paging request (RPR) (octet 10, bit 8)

This bit indicates the support of reject paging request.

reject paging request not supported

reject paging request supported

Paging restriction (PR) (octet 11, bit 1)

This bit indicates the support of paging restriction.

paging restriction not supported

paging restriction supported

Paging timing collision control (PTCC) (octet 11, bit 2)

This bit indicates the support of paging timing collision control.

paging timing collision control not supported

paging timing collision control supported

All other bits in octet 11 to 15 are spare and shall be coded as zero, if the respective octet is included in the information element.

NOTE 1: For a UE supporting dual connectivity with NR, if the UE supports one of the encryption algorithms for E-UTRAN (bits 8 to 5 of octet 3), it shall support the same algorithm for NR-PDCP as specified in 3GPP TS 33.401 [19]. The NR-PDCP is specified in 3GPP TS 38.323 [53].

NOTE 2: For a UE supporting dual connectivity with NR, if the UE supports one of the integrity algorithms for E-UTRAN (bits 8 to 5 of octet 4), it shall support the same algorithm for NR-PDCP as specified in 3GPP TS 33.401 [19].

NOTE 3: In this release of the specification, the EPS-UPIP supported bit is only applicable for a UE supporting dual connectivity with NR.

9.9.3.35 UE radio capability information update needed

The purpose of the UE radio capability information update needed information element is to indicate whether the MME shall delete the stored UE radio capability information, if any.

The UE radio capability information update needed information element is coded as shown in figure 9.9.3.35.1and table 9.9.3.35.1.

The UE radio capability information update needed is a type 1 information element.

UE radio capability information update needed IEI

URC

upd

octet 1

spare

Figure 9.9.3.35.1: UE radio capability information update needed information element

Table 9.9.3.35.1: UE radio capability information update needed information element

UE radio capability information update needed flag (URC upd) (octet 1)
Bit
1
0				UE radio capability information update not needed
1				UE radio capability information update needed

9.9.3.36 UE security capability

The UE security capability information element is used by the network to indicate which security algorithms are supported by the UE in S1 mode, Iu mode and Gb mode. Security algorithms supported in S1 mode are supported both for NAS and for AS security. If the UE supports S101 mode, then these security algorithms are also supported for NAS security in S101 mode.

The UE security capability information element is coded as shown in figure 9.9.3.36.1 and table 9.9.3.36.1.

The UE security capability is a type 4 information element with a minimum length of 4 octets and a maximum length of 7 octets.

Octets 5, 6, and 7 are optional. If octet 5 is included, then also octet 6 shall be included and octet 7 may be included.

If a UE did not indicate support of any security algorithm for Gb mode, octet 7 shall not be included. If the UE did not indicate support of any security algorithm for Iu mode and Gb mode, octets 5, 6, and 7 shall not be included.

If the UE did not indicate support of any security algorithm for Iu mode but indicated support of a security algorithm for Gb mode, octets 5, 6, and 7 shall be included. In this case octets 5 and 6 are filled with the value of zeroes.

UE security capability IEI

octet 1

Length of UE security capability contents

octet 2

EEA0

128-

EEA1

128-

EEA2

128-

EEA3

EEA4

EEA5

EEA6

EEA7

octet 3

EIA0

128-

EIA1

128-

EIA2

128-

EIA3

EIA4

EIA5

EIA6

EPS-UPIP

octet 4

UEA0

UEA1

UEA2

UEA3

UEA4

UEA5

UEA6

UEA7

octet 5*

spare

UIA1

UIA2

UIA3

UIA4

UIA5

UIA6

UIA7

octet 6*

spare

GEA1

GEA2

GEA3

GEA4

GEA5

GEA6

GEA7

octet 7*

Figure 9.9.3.36.1: UE security capability information element

Table 9.9.3.36.1: UE security capability information element

EPS encryption algorithms supported (octet 3)

EPS encryption algorithm EEA0 supported (octet 3, bit 8)
0					EPS encryption algorithm EEA0 not supported
1					EPS encryption algorithm EEA0 supported

EPS encryption algorithm 128-EEA1 supported (octet 3, bit 7)
0					EPS encryption algorithm 128-EEA1 not supported
1					EPS encryption algorithm 128-EEA1 supported

EPS encryption algorithm 128-EEA2 supported (octet 3, bit 6)
0					EPS encryption algorithm 128-EEA2 not supported
1					EPS encryption algorithm 128-EEA2 supported

EPS encryption algorithm 128-EEA3 supported (octet 3, bit 5)
0					EPS encryption algorithm 128-EEA3 not supported
1					EPS encryption algorithm 128-EEA3 supported

EPS encryption algorithm EEA4 supported (octet 3, bit 4)
0					EPS encryption algorithm EEA4 not supported
1					EPS encryption algorithm EEA4 supported

EPS encryption algorithm EEA5 supported (octet 3, bit 3)
0					EPS encryption algorithm EEA5 not supported
1					EPS encryption algorithm EEA5 supported

EPS encryption algorithm EEA6 supported (octet 3, bit 2)
0					EPS encryption algorithm EEA6 not supported
1					EPS encryption algorithm EEA6 supported

EPS encryption algorithm EEA7 supported (octet 3, bit 1)
0					EPS encryption algorithm EEA7 not supported
1					EPS encryption algorithm EEA7 supported

EPS integrity algorithms supported (octet 4)

EPS integrity algorithm EIA0 supported (octet 4, bit 8)
0					EPS integrity algorithm EIA0 not supported
1					EPS integrity algorithm EIA0 supported

EPS integrity algorithm 128-EIA1 supported (octet 4, bit 7)
0					EPS integrity algorithm 128-EIA1 not supported
1					EPS integrity algorithm 128-EIA1 supported

EPS integrity algorithm 128-EIA2 supported (octet 4, bit 6)
0					EPS integrity algorithm 128-EIA2 not supported
1					EPS integrity algorithm 128-EIA2 supported

EPS integrity algorithm 128-EIA3 supported (octet 4, bit 5)
0					EPS integrity algorithm 128-EIA3 not supported
1					EPS integrity algorithm 128-EIA3 supported

EPS integrity algorithm EIA4 supported (octet 4, bit 4)
0					EPS integrity algorithm EIA4 not supported
1					EPS integrity algorithm EIA4 supported

EPS integrity algorithm EIA5 supported (octet 4, bit 3)
0					EPS integrity algorithm EIA5 not supported
1					EPS integrity algorithm EIA5 supported

EPS integrity algorithm EIA6 supported (octet 4, bit 2)
0					EPS integrity algorithm EIA6 not supported
1					EPS integrity algorithm EIA6 supported

EPS-UPIP integrity algorithm EIA7 supported (octet 4, bit 1)
0					EPS-UPIP not supported
1					EPS-UPIP supported

UMTS encryption algorithms supported (octet 5)

UMTS encryption algorithm UEA0 supported (octet 5, bit 8)
0					UMTS encryption algorithm UEA0 not supported
1					UMTS encryption algorithm UEA0 supported

UMTS encryption algorithm UEA1 supported (octet 5, bit 7)
0					UMTS encryption algorithm UEA1 not supported
1					UMTS encryption algorithm UEA1 supported

UMTS encryption algorithm UEA2 supported (octet 5, bit 6)
0					UMTS encryption algorithm UEA2 not supported
1					UMTS encryption algorithm UEA2 supported

UMTS encryption algorithm UEA3 supported (octet 5, bit 5)
0					UMTS encryption algorithm UEA3 not supported
1					UMTS encryption algorithm UEA3 supported

UMTS encryption algorithm UEA4 supported (octet 5, bit 4)
0					UMTS encryption algorithm UEA4 not supported
1					UMTS encryption algorithm UEA4 supported

UMTS encryption algorithm UEA5 supported (octet 5, bit 3)
0					UMTS encryption algorithm UEA5 not supported
1					UMTS encryption algorithm UEA5 supported

UMTS encryption algorithm UEA6 supported (octet 5, bit 2)
0					UMTS encryption algorithm UEA6 not supported
1					UMTS encryption algorithm UEA6 supported

UMTS encryption algorithm UEA7 supported (octet 5, bit 1)
0					UMTS encryption algorithm UEA7 not supported
1					UMTS encryption algorithm UEA7 supported

UMTS integrity algorithms supported (octet 6)

Bit 8 of octet 6 is spare and shall be coded as zero.

UMTS integrity algorithm UIA1 supported (octet 6, bit 7)
0					UMTS integrity algorithm UIA1 not supported
1					UMTS integrity algorithm UIA1 supported

UMTS integrity algorithm UIA2 supported (octet 6, bit 6)
0					UMTS integrity algorithm UIA2 not supported
1					UMTS integrity algorithm UIA2 supported

UMTS integrity algorithm UIA3 supported (octet 6, bit 5)
0					UMTS integrity algorithm UIA3 not supported
1					UMTS integrity algorithm UIA3 supported

UMTS integrity algorithm UIA4 supported (octet 6, bit 4)
0					UMTS integrity algorithm UIA4 not supported
1					UMTS integrity algorithm UIA4 supported

UMTS integrity algorithm UIA5 supported (octet 6, bit 3)
0					UMTS integrity algorithm UIA5 not supported
1					UMTS integrity algorithm UIA5 supported

UMTS integrity algorithm UIA6 supported (octet 6, bit 2)
0					UMTS integrity algorithm UIA6 not supported
1					UMTS integrity algorithm UIA6 supported

UMTS integrity algorithm UIA7 supported (octet 6, bit 1)
0					UMTS integrity algorithm UIA7 not supported
1					UMTS integrity algorithm UIA7 supported

GPRS encryption algorithms supported (octet 7)

Bit 8 of octet 7 is spare and shall be coded as zero.

GPRS encryption algorithm GEA1 supported (octet 7, bit 7)
0					GPRS encryption algorithm GEA1 not supported
1					GPRS encryption algorithm GEA1 supported

GPRS encryption algorithm GEA2 supported (octet 7, bit 6)
0					GPRS encryption algorithm GEA2 not supported
1					GPRS encryption algorithm GEA2 supported

GPRS encryption algorithm GEA3 supported (octet 7, bit 5)
0					GPRS encryption algorithm GEA3 not supported
1					GPRS encryption algorithm GEA3 supported

GPRS encryption algorithm GEA4 supported (octet 7, bit 4)
0					GPRS encryption algorithm GEA4 not supported
1					GPRS encryption algorithm GEA4 supported

GPRS encryption algorithm GEA5 supported (octet 7, bit 3)
0					GPRS encryption algorithm GEA5 not supported
1					GPRS encryption algorithm GEA5 supported

GPRS encryption algorithm GEA6 supported (octet 7, bit 2)
0					GPRS encryption algorithm GEA6 not supported
1					GPRS encryption algorithm GEA6 supported

GPRS encryption algorithm GEA7 supported (octet 7, bit 1)
0					GPRS encryption algorithm GEA7 not supported
1					GPRS encryption algorithm GEA7 supported

NOTE 1: For a UE supporting dual connectivity with NR, if the UE supports one of the encryption algorithms for E-UTRAN (bits 8 to 5 of octet 3), it shall support the same algorithm for NR-PDCP as specified in 3GPP TS 33.401 [19]. NOTE 2: For a UE supporting dual connectivity with NR, if the UE supports one of the integrity algorithms for E-UTRAN different from EIA0 (bits 7 to 5 of octet 4), it shall support the same algorithm for NR-PDCP as specified in 3GPP TS 33.401 [19].

9.9.3.37 Emergency Number List

See clause 10.5.3.13 in 3GPP TS 24.008 [13].

9.9.3.37A Extended emergency number list

The purpose of this information element is to encode one or more local emergency number(s) together with a sub-services field containing zero or more sub-services of the associated emergency service URN and a validity indication. An emergency service URN is a service URN with top level service type of "sos" as specified in IETF RFC 5031 [55].

EXAMPLE 1: If the associated emergency service URN is "urn:service:sos.gas", there is only one sub-service provided in the sub-services field which is "gas".

EXAMPLE 2: If the associated emergency service URN is "urn:service:sos", there is no sub-services provided in the sub-services field and the length of the sub-services field is "0".

NOTE: The associated emergency service URN can be a country-specific emergency service URN as defined in 3GPP TS 24.229 [13D].

The Extended emergency number list information element is coded as shown in figure 9.9.3.37A.1 and table 9.9.3.37A.1.

The Extended emergency number list IE is a type 6 information element with a minimum length of 7 octets and a maximum length of 65538 octets.

Extended emergency number list IEI

octet 1

Length of Extended emergency number list IE contents

octet 2

octet 3

EENLV

octet 4

spare

Length of 1^st Emergency Number information (Note 1)

octet 5

Number digit 2

Number digit 1

octet 6

(Note 2)

Number digit 4

Number digit 3

octet 7*

(Note 3)

octet j-1*

Length of 1st sub-services field (Note 4)

octet j

sub-services field

octet j+1*

(Note 5)

octet k-1*

Length of 2^nd Emergency Number information (Note 1)

octet k*

Number digit 2

Number digit 1

octet k+1*

(Note 2)

Number digit 4

Number digit 3

octet k+2*

(Note 3)

octet l-1*

Length of 2^nd sub-services field (Note 4)

octet l*

sub-services field

octet l+1*

(Note 5)

octet m-1*

Length of 3^rd Emergency Number information (Note 1)

octet m*

Number digit 2

Number digit 1

octet m+1*

(Note 2)

Number digit 4

Number digit 3

octet m+2*

(Note 3)

octet n-1*

Length of 3^rd sub-services field (Note 4)

octet n*

sub-services field

octet n+1*

(Note 5)

octet o*

NOTE 1: The length shall contain the number of octets used to encode the number digits.

NOTE 2: The number digit(s) in octet 6 precedes the digit(s) in octet 7 etc. The number digit, which would be entered first, is located in octet 6, bits 1 to 4. The contents of the number digits are coded as shown in table 10.5.118/3GPP TS 24.008 [13].

NOTE 3: If the emergency number contains an odd number of digits, bits 5 to 8 of the last octet of the respective emergency number shall be filled with an end mark coded as "1111".

NOTE 4: The length shall contain the number of octets used to encode the sub-services field.

NOTE 5: The characters of the sub-services of the associated emergency service URN shall be coded in accordance to GSM 7 bit default alphabet and the appropriate padding characters and bit-fill are added to octet boundary as specified in clause 6.1.2.3.1 of 3GPP TS 23.038 [3]and the first character starts in octet j+1, l+1 or n+1.

Figure 9.9.3.37A.1 Extended Emergency Number List IE

EXAMPLE 3: If the associated emergency service URN is "urn:service:sos.police.municipal", the sub-services field contains "police.municipal" and the first character is "p".

Table 9.9.3.37A.1: Extended Emergency Number List Validity information IE

Extended Emergency Number List Validity (EENLV) (octet 4)
Bit
1
0				Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received
1				Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received

9.9.3.38 CLI

The purpose of the CLI information element is to convey information about the calling line for a terminated call to a CS fallback capable UE.

The CLI information element is coded as shown in figure 9.9.3.38.1 and table 9.9.3.38.1.

The CLI is a type 4 information element with a minimum length of 3 octets and a maximum length of 14 octets.

8	7	6	5	4	3	2	1
CLI IEI								octet 1
Length of CLI								octet 2
CLI (value part)								octet 3 to
								octet 14

Figure 9.9.3.38.1: CLI information element

Table 9.9.3.38.1: CLI information element

CLI (value part)

The coding of the CLI value part is the same as for octets 3 to 14 of the Calling party BCD number information element defined in clause 10.5.4.9 of 3GPP TS 24.008 [13].

9.9.3.39 SS Code

The purpose of the SS code information element is to convey information related to a network initiated supplementary service request to a CS fallback capable UE.

The SS Code information element is coded as shown in figure 9.9.3.39.1 and table 9.9.3.39.1.

The SS Code is a type 3 information element with 2 octets length.

8	7	6	5	4	3	2	1
SS Code IEI								octet 1
SS Code value								octet 2

Figure 9.9.3.39.1: SS Code information element

Table 9.9.3.39.1: SS Code information element

SS Code value

The coding of the SS Code value is given in clause 17.7.5 of 3GPP TS 29.002 [15C].

9.9.3.40 LCS indicator

The purpose of the LCS indicator information element is to indicate that the origin of the message is due to a LCS request and the type of this request to a CS fallback capable UE.

The LCS indicator information element is coded as shown in figure 9.9.3.40.1 and table 9.9.3.40.1.

The LCS indicator is a type 3 information element with 2 octets length.

8	7	6	5	4	3	2	1
LCS indicator IEI								octet 1
LCS indicator value								octet 2

Figure 9.9.3.40.1: LCS indicator information element

Table 9.9.3.40.1: LCS indicator information element

LCS indicator value

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 Normal, unspecified in this version of the protocol.

0 0 0 0 0 0 0 1 MT-LR

0 0 0 0 0 0 1 0

to Normal, unspecified in this version of the protocol

1 1 1 1 1 1 1 1

9.9.3.41 LCS client identity

The purpose of the LCS client identity information element is to convey information related to the client of a LCS request for a CS fallback capable UE.

The LCS client identity information element is coded as shown in figure 9.9.3.41.1 and table 9.9.3.41.1.

The LCI client identity is a type 4 information element with a minimum length of 3 octets and a maximum length of 257 octets.

8	7	6	5	4	3	2	1
LCS client identity IEI								octet 1
Length of LCS client identity								octet 2
LCS client identity (value part)								octet 3 to
								octet 257

Figure 9.9.3.41.1: LCS client identity information element

Table 9.9.3.41.1: LCS client identity information element

LCS client identity (value part)

The coding of the value part of the LCS client identity is given in clause 17.7.13 of 3GPP TS 29.002 [15C].

9.9.3.42 Generic message container type

The purpose of the generic message container type information element is to specify the type of message contained in the generic message container IE.

The generic message container type information element is coded as shown in table 9.9.3.42.1.

Table 9.9.3.42.1: Generic message container type information element

Bits
8	7	6	5	4	3	2	1

0	0	0	0	0	0	0	0	Reserved
0	0	0	0	0	0	0	1	LTE Positioning Protocol (LPP) message container (see 3GPP TS 36.355 [22A])
0	0	0	0	0	0	1	0	Location services message container (see 3GPP TS 24.171 [13C])
0	0	0	0	0	0	1	1
to								Unused
0	1	1	1	1	1	1	1
1	0	0	0	0	0	0	0
to								Reserved
1	1	1	1	1	1	1	1

9.9.3.43 Generic message container

This information element is used to encapsulate the application message transferred between the UE and the network. The generic message container information element is coded as shown in figure 9.9.3.43.1 and table 9.9.3.43.1.

The generic message container is a type 6 information element.

8	7	6	5	4	3	2	1
Generic message container IEI								octet 1
Length of generic message container contents								octet 2
								octet 3
								octet 4
Generic message container contents
								octet n

Figure 9.9.3.43.1: Generic message container information element

Table 9.9.3.43.1: Generic message container information element

Generic message container contents (octet 4 to octet n); Max value of 65535 octets

The coding of the contents of the generic message container is dependent on the particular application.

9.9.3.44 Voice domain preference and UE’s usage setting

See clause 10.5.5.28 in 3GPP TS 24.008 [13].

9.9.3.45 GUTI type

The purpose of the GUTI type information element is to indicate whether the GUTI included in the same message in an information element of type EPS mobile identity represents a native GUTI or a mapped GUTI.

The GUTI type information element information element is coded as shown in figure 9.9.3.45.1 and table 9.9.3.45.1.

The GUTI type is a type 1 information element.

8	7	6	5	4	3	2	1
GUTI type IEI				0	0	0	GUTI type	octet 1
GUTI type IEI				spare			GUTI type	octet 1

Figure 9.9.3.45.1: GUTI type information element

Table 9.9.3.45.1: GUTI type information element

GUTI type (octet 1)
Bit
1
0				Native GUTI
1				Mapped GUTI

Bits 2 to 4 of octet 1 are spare and shall be coded as zero.

9.9.3.46 Extended DRX parameters

See clause 10.5.5.32 in 3GPP TS 24.008 [13].

9.9.3.47 Control plane service type

The purpose of the Control plane service type information element is to specify the purpose of the CONTROL PLANE SERVICE REQUEST message.

The Control plane service type information element is coded as shown in figure 9.9.3.47.1 and table 9.9.3.47.1.

The Control plane service type is a type 1 information element.

Control plane service type

IEI

"Active" flag

Control plane service type

value

octet 1

Figure 9.9.3.47.1: Control plane service type information element

Table 9.9.3.47.1: Control plane service type information element

Control plane service type value (octet 1, bit 1 to 3)

Bits

3	2	1
0	0	0	mobile originating request
0	0	1	mobile terminating request
0	1	0
	to		unused; shall be interpreted as " mobile originating request", if received
1	1	1	by the network.

"Active" flag (octet 1, bit 4)
Bit

4
0			No radio bearer establishment requested
1			Radio bearer establishment requested

9.9.3.48 DCN-ID

See clause 10.5.5.35 in 3GPP TS 24.008 [13].

9.9.3.49 Non-3GPP NW provided policies

See clause 10.5.5.37 in 3GPP TS 24.008 [13].

9.9.3.50 Hash_MME

The purpose of the Hash_MME information element is to transfer a 64-bit hash value to the UE so the UE can check the MME calculated value against the value locally calculated by the UE to determine whether the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message sent by the UE has been modified.

The Hash_MME information element is coded as shown in figure 9.9.3.50.1 and table 9.9.3.50.1.

The Hash_MME is a type 4 information element with a length of 10 octets.

8	7	6	5	4	3	2	1
Hash_MME IEI								octet 1
Length of Hash_MME								octet 2
Hash_MME value								octet 3 octet 10

Figure 9.9.3.50.1: Hash_MME information element

Table 9.9.3.50.1: Hash_MME information element

Hash_MME value (octet 3 to 10)

This field contains the binary representation of the Hash_MME. Bit 8 of octet 3 represents the most significant bit of the Hash_MME and bit 1 of octet 10 the least significant bit.

9.9.3.51 Replayed NAS message container

The purpose of the Replayed NAS message container IE is to, during an ongoing attach or tracking area updating procedure, re-send the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message with which the UE had initiated the procedure, if the MME has included a HASH_MME in the SECURITY MODE COMMAND message and the HASH_MME is different from the hash value locally calculated at the UE as described in 3GPP TS 33.401 [19]. If an ATTACH REQUEST message is included in this IE, the ATTACH REQUEST message shall be coded as specified in clause 8.2.4, i.e. without NAS security header. If a TRACKING AREA UPDATE REQUEST message is included in this IE, the TRACKING AREA UPDATE REQUEST message shall be coded as specified in clause 8.2.29, i.e. without NAS security header

The Replayed NAS message container information element is coded as shown in figure 9.9.3.51.1 and table 9.9.3.51.1.

The Replayed NAS message container is a type 6 information element.

8	7	6	5	4	3	2	1
Replayed NAS message container IEI								octet 1
Length of Replayed NAS message container contents								octet 2
								octet 3
								octet 4
Replayed NAS message container contents
								octet n

Figure 9.9.3.51.1: Replayed NAS message container information element

Table 9.9.3.51.1: Replayed NAS message container information element

Replayed NAS message container contents (octet 4 to octet n); Max value of 65535 octets

This IE can contain an ATTACH REQUEST message as defined in clause 8.2.4, or a TRACKING AREA UPDATE REQUEST message as defined in clause 8.2.29.

9.9.3.52 Network policy

The purpose of the Network policy information element is to provide network policy information to the UE during attach or tracking area updating procedure via the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message.

The Network policy information element is coded as shown in figure 9.9.3.52.1 and table 9.9.3.52.1.

The Network policy is a type 1 information element.

Network policy IEI

spare

redir- policy

octet 1

Figure 9.9.3.52.1: Network policy information element

Table 9.9.3.52.1: Network policy information element

Network policy value

Redirection to GERAN security policy (redir-policy) (octet 1, bit 1)
0					Unsecured redirection to GERAN allowed
1					Unsecured redirection to GERAN not allowed

Bits 2 to 4 are spare and shall be set to "0".

9.9.3.53 UE additional security capability

The UE additional security capability information element is used by the UE to indicate which additional security algorithms are supported by the UE for S1 mode in dual connectivity with NR or for N1 mode or both.

The UE additional security capability information element is coded as shown in figure 9.9.3.53.1 and table 9.9.3.53.1.

The UE additional security capability is a type 4 information element with a length of 6 octets.

UE additional security capability IEI

octet 1

Length of UE additional security capability contents

octet 2

5G-EA0

128-

5G-EA1

128-

5G-EA2

128-

5G-EA3

5G-EA4

5G-EA5

5G-EA6

5G-EA7

octet 3

5G-EA8

5G-EA9

5G-EA10

5G-EA11

5G-EA12

5G-EA13

5G-EA14

5G-EA15

octet 4

5G-IA0

128-

5G-IA1

128-

5G-IA2

128-

5G-IA3

5G-IA4

5G-IA5

5G-IA6

5G-IA7

octet 5

5G-IA8

5G-IA9

5G-IA10

5G-IA11

5G-IA12

5G-IA13

5G-IA14

5G-IA15

octet 6

Figure 9.9.3.53.1: UE additional security capability information element

Table 9.9.3.53.1: UE additional security capability information element

5GS encryption algorithms supported (octet 3) (NOTE 1)

5GS encryption algorithm 5G-EA0 supported (octet 3, bit 8)
0					5GS encryption algorithm 5G-EA0 not supported
1					5GS encryption algorithm 5G-EA0 supported

5GS encryption algorithm 128-5G-EA1 supported (octet 3, bit 7)
0					5GS encryption algorithm 128-5G-EA1 not supported
1					5GS encryption algorithm 128-5G-EA1 supported

5GS encryption algorithm 128-5G-EA2 supported (octet 3, bit 6)
0					5GS encryption algorithm 128-5G-EA2 not supported
1					5GS encryption algorithm 128-5G-EA2 supported

5GS encryption algorithm 128-5G-EA3 supported (octet 3, bit 5)
0					5GS encryption algorithm 128-5G-EA3 not supported
1					5GS encryption algorithm 128-5G-EA3 supported

5GS encryption algorithm 5G-EA4 supported (octet 3, bit 4)
0					5GS encryption algorithm 5G-EA4 not supported
1					5GS encryption algorithm 5G-EA4 supported

5GS encryption algorithm 5G-EA5 supported (octet 3, bit 3)
0					5GS encryption algorithm 5G-EA5 not supported
1					5GS encryption algorithm 5G-EA5 supported

5GS encryption algorithm 5G-EA6 supported (octet 3, bit 2)
0					5GS encryption algorithm 5G-EA6 not supported
1					5GS encryption algorithm 5G-EA6 supported

5GS encryption algorithm 5G-EA7 supported (octet 3, bit 1)
0					5GS encryption algorithm 5G-EA7 not supported
1					5GS encryption algorithm 5G-EA7 supported

5GS encryption algorithms supported (octet 4)

5GS encryption algorithm 5G-EA8 supported (octet 4, bit 8)
0					5GS encryption algorithm 5G-EA8 not supported
1					5GS encryption algorithm 5G-EA8 supported

5GS encryption algorithm 5G-EA9 supported (octet 4, bit 7)
0					5GS encryption algorithm 5G-EA9 not supported
1					5GS encryption algorithm 5G-EA9 supported

5GS encryption algorithm 5G-EA10 supported (octet 4, bit 6)
0					5GS encryption algorithm 5G-EA10 not supported
1					5GS encryption algorithm 5G-EA10 supported

5GS encryption algorithm 5G-EA11 supported (octet 4, bit 5)
0					5GS encryption algorithm 5G-EA11 not supported
1					5GS encryption algorithm 5G-EA11 supported

5GS encryption algorithm 5G-EA12 supported (octet 4, bit 4)
0					5GS encryption algorithm 5G-EA12 not supported
1					5GS encryption algorithm 5G-EA12 supported

5GS encryption algorithm 5G-EA13 supported (octet 4, bit 3)
0					5GS encryption algorithm 5G-EA13 not supported
1					5GS encryption algorithm 5G-EA13 supported

5GS encryption algorithm 5G-EA14 supported (octet 4, bit 2)
0					5GS encryption algorithm 5G-EA14 not supported
1					5GS encryption algorithm 5G-EA14 supported

5GS encryption algorithm 5G-EA15 supported (octet 4, bit 1)
0					5GS encryption algorithm 5G-EA15 not supported
1					5GS encryption algorithm 5G-EA15 supported

5GS integrity algorithms supported (octet 5) (NOTE 2)

5GS integrity algorithm 5G-IA0 supported (octet 5, bit 8) (NOTE 3)
0					5GS integrity algorithm 5G-IA0 not supported
1					5GS integrity algorithm 5G-IA0 supported

5GS integrity algorithm 128-5G-IA1 supported (octet 5, bit 7)
0					5GS integrity algorithm 128-5G-IA1 not supported
1					5GS integrity algorithm 128-5G-IA1 supported

5GS integrity algorithm 128-5G-IA2 supported (octet 5, bit 6)
0					5GS integrity algorithm 128-5G-IA2 not supported
1					5GS integrity algorithm 128-5G-IA2 supported

5GS integrity algorithm 128-5G-IA3 supported (octet 5, bit 5)
0					5GS integrity algorithm 128-5G-IA3 not supported
1					5GS integrity algorithm 128-5G-IA3 supported

5GS integrity algorithm 5G-IA4 supported (octet 5, bit 4)
0					5GS integrity algorithm 5G-IA4 not supported
1					5GS integrity algorithm 5G-IA4 supported

5GS integrity algorithm 5G-IA5 supported (octet 5, bit 3)
0					5GS integrity algorithm 5G-IA5 not supported
1					5GS integrity algorithm 5G-IA5 supported

5GS integrity algorithm 5G-IA6 supported (octet 5, bit 2)
0					5GS integrity algorithm 5G-IA6 not supported
1					5GS integrity algorithm 5G-IA6 supported

5GS integrity algorithm 5G-IA7 supported (octet 5, bit 1)
0					5GS integrity algorithm 5G-IA7 not supported
1					5GS integrity algorithm 5G-IA7 supported

5GS integrity algorithms supported (octet 6)

5GS integrity algorithm 5G-IA8 supported (octet 6, bit 8)
0					5GS integrity algorithm 5G-IA8 not supported
1					5GS integrity algorithm 5G-IA8 supported

5GS integrity algorithm 5G-IA9 supported (octet 6, bit 7)
0					5GS integrity algorithm 5G-IA9 not supported
1					5GS integrity algorithm 5G-IA9 supported

5GS integrity algorithm 5G-IA10 supported (octet 6, bit 6)
0					5GS integrity algorithm 5G-IA10 not supported
1					5GS integrity algorithm 5G-IA10 supported

5GS integrity algorithm 5G-IA11 supported (octet 6, bit 5)
0					5GS integrity algorithm 5G-IA11 not supported
1					5GS integrity algorithm 5G-IA11 supported

5GS integrity algorithm 5G-IA12 supported (octet 6, bit 4)
0					5GS integrity algorithm 5G-IA12 not supported
1					5GS integrity algorithm 5G-IA12 supported

5GS integrity algorithm 5G-IA13 supported (octet 6, bit 3)
0					5GS integrity algorithm 5G-IA13 not supported
1					5GS integrity algorithm 5G-IA13 supported

5GS integrity algorithm 5G-IA14 supported (octet 6, bit 2)
0					5GS integrity algorithm 5G-IA14 not supported
1					5GS integrity algorithm 5G-IA14 supported

5GS integrity algorithm 5G-IA15 supported (octet 6, bit 1)
0					5GS integrity algorithm 5G-IA15 not supported
1					5GS integrity algorithm 5G-IA15 supported

NOTE 1: For a UE supporting dual connectivity with NR. if the UE supports one of the encryption algorithms for 5GS in bits 8 to 5 of octet 3, it shall support the same algorithms for E-UTRAN as specified in 3GPP TS 33.401 [19].
NOTE 2: For a UE supporting dual connectivity with NR, if the UE supports one of the integrity protection algorithms for 5GS different from 5G-IA0 (bits 7 to 5 of octet 5), it shall support the same algorithms for E-UTRAN as specified in 3GPP TS 33.401 [19]. NOTE 3: This algorithm is not applicable to dual connectivity with NR. A UE not supporting N1 mode shall set this bit to "0".

9.9.3.54 UE status

See clause 9.11.3.56 in 3GPP TS 24.501 [54].

9.9.3.55 Additional information requested

The purpose of the Additional information requested information element is to enable the UE to request ciphering keys for deciphering of ciphered broadcast assistance data.

The Additional information requested information element is coded as shown in figure 9.9.3.55.1 and table 9.9.3.55.1.

The Additional information requested is a type 3 information element with a length of 2 octets.

8	7	6	5	4	3	2	1
Ciphered broadcast assistance data IEI								octet 1
0	0	0	0	0	0	0	CipherKey	octet 2
Spare							CipherKey	octet 2

Figure 9.9.3.55.1: Additional information requested information element

Table 9.9.3.55.1: Additional information requested information element

Ciphering keys for ciphered broadcast assistance data (CipherKey) (octet 2, bit 1)
Bit
1
0				ciphering keys for ciphered broadcast assistance data not requested
1				ciphering keys for ciphered broadcast assistance data requested

Bits 8 to 2 of octet 2 are spare and shall be coded as zero.

9.9.3.56 Ciphering key data

The purpose of the Ciphering key data information element is to transfer a list of ciphering data sets from the network to the UE for deciphering of ciphered assistance data.

The Ciphering key data information element is coded as shown in figure 9.9.3.56.1, figure 9.9.3.56.2 and table 9.9.3.56.1.

The Ciphering key data is a type 6 information element, with a minimum length of 35 octets and a maximum length of 2291 octets. The list can contain a maximum of 16 ciphering data sets.

8	7	6	5	4	3	2	1
Ciphering key data IEI								octet 1
Length of ciphering key data contents								octet 2 octet 3
Ciphering data set 1								octet 4 octet i
Ciphering data set 2								octet i+1* octet l*
…								octet l+1* octet m*
Ciphering data set p								octet m+1* octet n*

Figure 9.9.3.56.1: Ciphering key data information element

8	7	6	5	4	3	2	1
Ciphering set ID								octet 1 octet 2
Ciphering key								octet 3 octet 18
0	0	0	c0 length					octet 19
Spare			c0 length					octet 19
c0								octet 20 octet k
PosSIBType1-1	PosSIBType1-2	PosSIBType1-3	PosSIBType1-4	PosSIBType1-5	PosSIBType1-6	PosSIBType1-7	PosSIBType2-1	octet k+1 octet k+4
PosSIBType2-2	PosSIBType2-3	PosSIBType2-4	PosSIBType2-5	PosSIBType2-6	PosSIBType2-7	PosSIBType2-8	PosSIBType2-9
PosSIBType2-10	PosSIBType2-11	PosSIBType2-12	PosSIBType2-13	PosSIBType2-14	PosSIBType2-15	PosSIBType2-16	PosSIBType2-17
PosSIBType2-18	PosSIBType2-19	PosSIBType3-1	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare
Validity start time								octet k+5 octet k+9
Validity duration								octet k+10 octet k+11
TAIs list								octet k+12 octet n

Figure 9.9.3.56.2: Ciphering data set

Table 9.9.3.56.1: Ciphering key data information element

Value part of the Ciphering key data information element (octets 4 to n)

The value part of the Ciphering key data information element consists of one or several ciphering data sets.
The UE shall store the complete list received. If more than 16 ciphering data sets are included in this information element, the UE shall store the first 16 ciphering data sets and ignore the remaining octets of the information element.


Ciphering data set:

Ciphering set ID (octets 1 to 2)

This field contains the binary encoding of the ID identifying the ciphering set.

Ciphering key (octets 3 to octet 18)

This field contains the 128 bit ciphering key.

c0 length (octet 19, bits 5 to 1) This field contains the binary encoding of the length, in octets, of the c0 counter. The maximum value for the length of the c0 counter is 16 octets.

Bits 8 to 6 of octet 19 are spare and shall be coded as zero.


c0 (octets 20 to k)

This field contains the binary encoding of the c0 counter.


Positioning SIB types for which the ciphering data set is applicable (octets k+1 to k+4)

Ciphering data set applicable for positioning SIB type 1-1 (octet k+1, bit 8)
0						Ciphering data set not applicable to positioning SIB type 1-1
1						Ciphering data set applicable to positioning SIB type 1-1

Ciphering data set applicable for positioning SIB type 1-2 (octet k+1, bit 7)
0						Ciphering data set not applicable to positioning SIB type 1-2
1						Ciphering data set applicable to positioning SIB type 1-2

Ciphering data set applicable for positioning SIB type 1-3 (octet k+1, bit 6)
0						Ciphering data set not applicable to positioning SIB type 1-3
1						Ciphering data set applicable to positioning SIB type 1-3

Ciphering data set applicable for positioning SIB type 1-4 (octet k+1, bit 5)
0						Ciphering data set not applicable to positioning SIB type 1-4
1						Ciphering data set applicable to positioning SIB type 1-4

Ciphering data set applicable for positioning SIB type 1-5 (octet k+1, bit 4)
0						Ciphering data set not applicable to positioning SIB type 1-5
1						Ciphering data set applicable to positioning SIB type 1-5

Ciphering data set applicable for positioning SIB type 1-6 (octet k+1, bit 3)
0						Ciphering data set not applicable to positioning SIB type 1-6
1						Ciphering data set applicable to positioning SIB type 1-6

Ciphering data set applicable for positioning SIB type 1-7 (octet k+1, bit 2)
0						Ciphering data set not applicable to positioning SIB type 1-7
1						Ciphering data set applicable to positioning SIB type 1-7

Ciphering data set applicable for positioning SIB type 2-1 (octet k+1, bit 1)
0						Ciphering data set not applicable to positioning SIB type 2-1
1						Ciphering data set applicable to positioning SIB type 2-1


Ciphering data set applicable for positioning SIB type 2-2 (octet k+2, bit 8)
0						Ciphering data set not applicable to positioning SIB type 2-2
1						Ciphering data set applicable to positioning SIB type 2-2

Ciphering data set applicable for positioning SIB type 2-3 (octet k+2, bit 7)
0						Ciphering data set not applicable to positioning SIB type 2-3
1						Ciphering data set applicable to positioning SIB type 2-3

Ciphering data set applicable for positioning SIB type 2-4 (octet k+2, bit 6)
0						Ciphering data set not applicable to positioning SIB type 2-4
1						Ciphering data set applicable to positioning SIB type 2-4

Ciphering data set applicable for positioning SIB type 2-5 (octet k+2, bit 5)
0						Ciphering data set not applicable to positioning SIB type 2-5
1						Ciphering data set applicable to positioning SIB type 2-5

Ciphering data set applicable for positioning SIB type 2-6 (octet k+2, bit 4)
0						Ciphering data set not applicable to positioning SIB type 2-6
1						Ciphering data set applicable to positioning SIB type 2-6

Ciphering data set applicable for positioning SIB type 2-7 (octet k+2, bit 3)
0						Ciphering data set not applicable to positioning SIB type 2-7
1						Ciphering data set applicable to positioning SIB type 2-7

Ciphering data set applicable for positioning SIB type 2-8 (octet k+2, bit 2)
0						Ciphering data set not applicable to positioning SIB type 2-8
1						Ciphering data set applicable to positioning SIB type 2-8

Ciphering data set applicable for positioning SIB type 2-9 (octet k+2, bit 1)
0						Ciphering data set not applicable to positioning SIB type 2-9
1						Ciphering data set applicable to positioning SIB type 2-9

Ciphering data set applicable for positioning SIB type 2-10 (octet k+3, bit 8)
0						Ciphering data set not applicable to positioning SIB type 2-10
1						Ciphering data set applicable to positioning SIB type 2-10

Ciphering data set applicable for positioning SIB type 2-11 (octet k+3, bit 7)
0						Ciphering data set not applicable to positioning SIB type 2-11
1						Ciphering data set applicable to positioning SIB type 2-11

Ciphering data set applicable for positioning SIB type 2-12 (octet k+3, bit 6)
0						Ciphering data set not applicable to positioning SIB type 2-12
1						Ciphering data set applicable to positioning SIB type 2-12

Ciphering data set applicable for positioning SIB type 2-13 (octet k+3, bit 5)
0						Ciphering data set not applicable to positioning SIB type 2-13
1						Ciphering data set applicable to positioning SIB type 2-13

Ciphering data set applicable for positioning SIB type 2-14 (octet k+3, bit 4)
0						Ciphering data set not applicable to positioning SIB type 2-14
1						Ciphering data set applicable to positioning SIB type 2-14

Ciphering data set applicable for positioning SIB type 2-15 (octet k+3, bit 3)
0						Ciphering data set not applicable to positioning SIB type 2-15
1						Ciphering data set applicable to positioning SIB type 2-15

Ciphering data set applicable for positioning SIB type 2-16 (octet k+3, bit 2)
0						Ciphering data set not applicable to positioning SIB type 2-16
1						Ciphering data set applicable to positioning SIB type 2-16

Ciphering data set applicable for positioning SIB type 2-17 (octet k+3, bit 1)
0						Ciphering data set not applicable to positioning SIB type 2-17
1						Ciphering data set applicable to positioning SIB type 2-17

Ciphering data set applicable for positioning SIB type 2-18 (octet k+4, bit 8)
0						Ciphering data set not applicable to positioning SIB type 2-18
1						Ciphering data set applicable to positioning SIB type 2-18

Ciphering data set applicable for positioning SIB type 2-19 (octet k+4, bit 7)
0						Ciphering data set not applicable to positioning SIB type 2-19
1						Ciphering data set applicable to positioning SIB type 2-19

Ciphering data set applicable for positioning SIB type 3-1 (octet k+4, bit 6)
0						Ciphering data set not applicable to positioning SIB type 3-1
1						Ciphering data set applicable to positioning SIB type 3-1

Bits 5 to 1 of octet k+4 are spare and shall be coded as zero.


Validity start time (octets k+5 to k+9)

This field contains the UTC time when the ciphering data set becomes valid, encoded as octets 2 to 6 of the Time zone and time IE specified in 3GPP TS 24.008 [13].


Validity duration (octets k+10 to k+11)

This field contains the duration for which the ciphering data set is valid after the validity start time, in units of minutes.


TAIs list (octets k+12 to n)

This field contains the list of tracking areas for which the ciphering data set is applicable, encoded as octets 2 to n of the Tracking area identity list IE as specified in clause 9.9.3.33. If the TAIs list is empty (as indicated by a zero length), the ciphering data set is applicable to the entire serving PLMN.

9.9.3.57 N1 UE network capability

The purpose of the N1 UE network capability IE is to allow the UE that supports N1 mode, to provide the network with information related to the UE’s capabilities for 5GS.

The N1 UE network capability information element is coded as shown in figure 9.9.3.57.1 and table 9.9.3.57.1.

The N1 UE network capability is a type 4 information element.

8	7	6	5	4	3	2	1
N1 UE network capability IEI								octet 1
Length of N1 UE network capability contents								octet 2
0 Spare	5G-EHC-CP CIoT	5GS-PNB-CIoT		5G-UP CIoT	5G-HC-CP CIoT	N3 data	5G-CP CIoT	octet 3

Figure 9.9.3.57.1: N1 UE network capability information element

Table 9.9.3.57.1: N1 UE network capability information element

Control plane CIoT 5GS optimization (5G-CP CIoT) (octet 3, bit 1)
This bit indicates the capability for control plane CIoT 5GS optimization
Bit
1
0		Control plane CIoT 5GS optimization not supported
1		Control plane CIoT 5GS optimization supported

N3 data transfer (N3 data) (octet 3, bits 2) This bit indicates the capability for N3 data transfer.
Bit
2
0		N3 data transfer supported
1		N3 data transfer not supported

IP header compression for control plane CIoT 5GS optimization (5G-HC-CP CIoT) (octet 3, bit 3) This bit indicates the capability for IP header compression for control plane CIoT 5GS optimization.
Bit
3
0		IP header compression for control plane CIoT 5GS optimization not supported
1		IP header compression for control plane CIoT 5GS optimization supported

User plane CIoT 5GS optimization (5G-UP CIoT) (octet 3, bit 4)
This bit indicates the capability for user plane CIoT 5GS optimization
Bit
4
0		User plane CIoT 5GS optimization not supported
1		User plane CIoT 5GS optimization supported

5GS Preferred CIoT network behaviour (5GS-PNB-CIoT) (octet 3, bits 5 and 6)
These bits indicate the 5GS CIoT network behaviour the UE prefers to use
Bits
6	5
0	0	no additional information
0	1	control plane CIoT 5GS optimization
1	0	user plane CIoT 5GS optimization
1	1	reserved
Ethernet header compression for control plane CIoT 5GS optimization (5G-EHC-CP CIoT) (octet 3, bit 7) This bit indicates the capability for Ethernet header compression for control plane CIoT 5GS optimization. Bit 7 0 Ethernet header compression for control plane CIoT 5GS optimization not supported 1 Ethernet header compression for control plane CIoT 5GS optimization supported
All other bits in octet 3 are spare and shall be coded as zero, if the respective octet is included in the information element.

9.9.3.58 UE radio capability ID availability

The purpose of the UE radio capability ID availability information element is to indicate that the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN.

The UE radio capability ID availability is a type 4 information element with a length of 3 octets.

The UE radio capability ID availability information element is coded as shown in figure 9.9.3.58.1 and table 9.9.3.58.1.

8	7		6			5		4		3	2	1
UE radio capability ID availability IEI													octet 1
Length of UE radio capability ID availability contents													octet 2
0	0	0			0			0		UE radio capability ID availability value
Spare													octet 3
8	7			6			5		4	3		2	1

Figure 9.9.3.58.1: UE radio capability ID availability information element

Table 9.9.3.58.1: UE radio capability ID availability information element

UE radio capability ID availability value (bits 3 to 1 of octet 3)
Bits
3	2	1
0	0	0	UE radio capability ID not available
0	0	1	UE radio capability ID available

All other values are interpreted as UE radio capability ID not available by this version of the protocol.
Bits 4 to 8 of octet 3 are spare and shall be coded as zero.

9.9.3.59 UE radio capability ID request

The purpose of the UE radio capability ID request information element is to indicate that the UE radio capability ID shall be included by the UE in the SECURITY MODE COMPLETE message.

The UE radio capability ID request is a type 4 information element with a length of 3 octets.

The UE radio capability ID request information element is coded as shown in figure 9.9.3.59.1 and table 9.9.3.59.1.

UE radio capability ID request IEI

octet 1

Length of UE radio capability ID request contents

octet 2

Spare

URCIDR

octet 3

Figure 9.9.3.59.1: UE radio capability ID request information element

Table 9.9.3.59.1: UE radio capability ID request information element

UE radio capability ID request (URCIDR) (octet 3, bit 1)
Bit
1
0				UE radio capability ID not requested
1				UE radio capability ID requested

Bits 2 to 8 of octet 3 are spare and shall be coded as zero.

9.9.3.60 UE radio capability ID

See clause 9.11.3.68 in 3GPP TS 24.501 [54].

9.9.3.61 UE radio capability ID deletion indication

See clause 9.11.3.69 in 3GPP TS 24.501 [54].

9.9.3.62 WUS assistance information

The purpose of the WUS assistance information information element is to transfer the required assistance information to determine the WUS group used when paging the UE.

The coding of the information element allows combining different types of WUS assistance information.

The WUS assistance information information element is coded as shown in figure 9.9.3.62.1, figure 9.9.3.62.2 and table 9.9.3.62.1.

The WUS assistance information is a type 4 information element, with a minimum length of 3 octets.

8	7	6	5	4	3	2	1
WUS assistance information IEI								octet 1
Length of WUS assistance information contents								octet 2
WUS assistance information type 1								octet 3 octet i
WUS assistance information type 2								octet i+1* octet l*
…								octet l+1* octet m*
WUS assistance information type p								octet m+1* octet n*

Figure 9.9.3.62.1: WUS assistance information information element

8	7	6		5	4	3	2	1
Type of information				UE paging probability information value						octet 1

Figure 9.9.3.62.2: WUS assistance information type –type of information= "000"

Table 9.9.3.62.1: WUS assistance information information element

Value part of the WUS assistance information information element (octets 3 to n)

The value part of the WUS assistance information information element consists of one or several types of WUS assistance information.

WUS assistance information type:

Type of information (octet 1)
Bits
8		7		6
0		0		0		UE paging probability information

All other values are reserved.

UE paging probability information value:

This field contains the value of UE paging probability information requested by the UE or negotiated by the network. It represents the probability of the UE receiving the paging. bit
5	4		3		2		1	UE paging probability information value
0	0		0		0		0	p00 (UE calculated paging probability is 0%)
0	0		0		0		1	p05 (UE calculated paging probability > 0% and <= 5%)
0	0		0		1		0	p10 (UE calculated paging probability > 5% and <= 10%)
0	0		0		1		1	p15 (UE calculated paging probability > 10% and <= 15%)
0	0		1		0		0	p20 (UE calculated paging probability > 15% and <= 20%)
0	0		1		0		1	p25 (UE calculated paging probability > 20% and <= 25%)
0	0		1		1		0	p30 (UE calculated paging probability > 25% and <= 30%)
0	0		1		1		1	p35 (UE calculated paging probability > 30% and <= 35%)
0	1		0		0		0	p40 (UE calculated paging probability > 35% and <= 40%)
0	1		0		0		1	p45 (UE calculated paging probability > 40% and <= 45%)
0	1		0		1		0	p50 (UE calculated paging probability > 45% and <= 50%)
0	1		0		1		1	p55 (UE calculated paging probability > 50% and <= 55%)
0	1		1		0		0	p60 (UE calculated paging probability > 55% and <= 60%)
0	1		1		0		1	p65 (UE calculated paging probability > 60% and <= 65%)
0	1		1		1		0	p70 (UE calculated paging probability > 65% and <= 70%)
0	1		1		1		1	p75 (UE calculated paging probability > 70% and <= 75%)
1	0		0		0		0	p80 (UE calculated paging probability > 75% and <= 80%)
1	0		0		0		1	p85 (UE calculated paging probability > 80% and <= 85%)
1	0		0		1		0	p90 (UE calculated paging probability > 85% and <= 90%)
1	0		0		1		1	p95 (UE calculated paging probability > 90% and <= 95%)
1	0		1		0		0	p100 (UE calculated paging probability > 95% and <= 100%)

All other values shall be interpreted as 10100 by this version of the protocol.

9.9.3.63 NB-S1 DRX parameter

The purpose of the NB-S1 DRX parameter information element is to indicate that the UE intends to use the UE specific DRX parameter in NB-S1 mode and for the network to indicate the negotiated UE specific DRX parameter to be used at paging in NB-S1 mode.

The NB-S1 DRX parameters information element is coded as shown in figure 9.9.3.63.1 and table 9.9.3.63.1.

The NB-S1 DRX parameters is a type 4 information element with a length of 3 octets.

8	7	6	5	4	3	2	1
NB-S1 mode DRX parameters IEI								octet 1
Length of NB-S1 mode DRX parameters contents								octet 2
0	0	0	0	NB-S1 mode DRX value
Spare				NB-S1 mode DRX value				octet 3

Figure 9.9.3.63.1: NB-S1 DRX parameter information element

Table 9.9.3.63.1: NB-S1 DRX parameter information element

NB-S1 mode DRX value (bits 4 to 1 of octet 3) This field represents the DRX cycle parameter ‘T’ as defined in 3GPP TS 36.304 [21].
Bits
4	3	2	1
0	0	0	0	DRX value not specified and use cell specific DRX value
0	0	0	1	DRX cycle parameter T = 32
0	0	1	0	DRX cycle parameter T = 64
0	0	1	1	DRX cycle parameter T = 128
0	1	0	0	DRX cycle parameter T = 256
0	1	0	1	DRX cycle parameter T = 512
0	1	1	0	DRX cycle parameter T = 1024

All other values shall be interpreted as "DRX value not specified and use cell specific DRX value" by this version of the protocol.
Bits 5 to 8 of octet 3 are spare and shall be coded as zero.

9.9.3.64 IMSI offset

The purpose of the IMSI offset information element is to indicate an IMSI offset value that is used for calculating an alternative IMSI value as specified in 3GPP TS 23.401 [10] that is used for deriving the paging occasion as specified in 3GPP TS 36.304 [21].

The IMSI offset information element is coded as shown in figure 9.9.3.64.1 and table 9.9.3.64.1.

The IMSI offset is a type 4 information element with a length of 4 octets.

8	7	6	5	4	3	2	1
IMSI offset IEI								octet 1
Length of IMSI offset value								octet 2
IMSI offset value								octet 3 octet 4

Figure 9.9.3.64.1: IMSI offset information element

Table 9.9.3.64.1: IMSI offset information element

IMSI offset value (octet 3 to 4)

This field contains the binary representation of the IMSI offset. Bit 8 of octet 3 represents the most significant bit of the IMSI offset and bit 1 of octet 4 the least significant bit.

9.9.3.65 UE request type

The purpose of the UE request type information element is to enable a MUSIM UE to request the network to perform specific requests due to activity on another USIM.

The UE request type information element is coded as shown in figure 9.9.3.65.1 and table 9.9.3.65.1.

The UE request type is a type 4 information element with a length of 3 octets.

8	7	6	5	4	3	2	1
UE request type IEI								octet 1
Length of UE request type contents								octet 2
0 Spare	0 Spare	0 Spare	0 Spare	Request type				octet 3

Figure 9.9.3.65.1: UE request type information element

Table 9.9.3.65.1: UE request type information element

Request type (bits 4 to 1 of octet 3)
Bits
4	3	2	1
0	0	0	0	reserved
0	0	0	1	NAS signalling connection release
0	0	1	0	Rejection of paging

All other values are reserved.
Bits 5 to 8 of octet 3 are spare and shall be coded as zero.

9.9.3.66 Paging restriction

The purpose of the Paging restriction information element is to request the network to restrict paging.

The Paging restriction information element is coded as shown in figure 9.9.3.66.1, figure 9.9.3.66.2 and table 9.9.3.66.1.

The Paging restriction is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets.

8	7	6	5	4	3	2	1
Paging restriction IEI								octet 1
Length of Paging restriction contents								octet 2
0 Spare	0 Spare	0 Spare	0 Spare	Paging restriction type				octet 3

Figure 9.9.3.66.1: Paging restriction information element for Paging restriction type = "All paging is restricted" and for Paging restriction type = "All paging is restricted except voice"

Paging restriction IEI

octet 1

Length of Paging restriction contents

octet 2

Spare

Paging restriction type

octet 3

EBI

(7)

EBI

(6)

EBI

(5)

EBI

(4)

EBI

(3)

EBI

(2)

EBI

(1)

EBI

(0)

octet 4*

EBI

(15)

EBI

(14)

EBI

(13)

EBI

(12)

EBI

(11)

EBI

(10)

EBI

(9)

EBI

(8)

octet 5*

Figure 9.9.3.66.2: Paging restriction information element for Paging restriction type = "All paging is restricted except for specified PDN connection(s)" and for Paging restriction type = "All paging is restricted except for voice service and specified PDN connection(s)"

Table 9.9.3.66.1: Paging restriction information element

Paging restriction type (bits 4 to 1 of octet 3)
Bits
4	3	2	1
0	0	0	0	reserved
0	0	0	1	All paging is restricted
0	0	1	0	All paging is restricted except for voice service
0	0	1	1	All paging is restricted except for specified PDN connection(s)
0	1	0	0	All paging is restricted except for voice service and specified PDN connection(s)

All other values are reserved.
Bits 5 to 8 of octet 3 are spare and shall be coded as zero. EBI(x) (bits 8 to 1 of octet 4 and octet 5): This field indicates the PDN connections associated with the EPS bearer identities for which paging is restricted. EBI(0): (bit 1 of octet 4) Spare and shall be coded as zero. EBI(1) – EBI(15): 0 if the corresponding EPS bearer context is a default EPS bearer context, indicates that paging is restricted for the PDN connection associated with the EPS bearer identity. (see NOTE) 1 if the corresponding EPS bearer context is a default EPS bearer context, indicates that paging is not restricted for the PDN connection associated with the EPS bearer identity. (see NOTE)
NOTE: If the corresponding EPS bearer context is not a default EPS bearer context, the value is always set to 1. If the corresponding EPS bearer context is not activated, the value is always set to 1.

9.9.3.67 EPS additional request result

The purpose of the EPS additional request result information element is to inform the UE about the result of additional request.

The EPS additional request result information element is coded as shown in figure 9.9.3.67.1 and table 9.9.3.67.1.

The EPS additional request result is a type 4 information element with a length of 3 octets.

8	7	6	5	4	3	2	1
EPS additional request result IEI								octet 1
Length of EPS additional request result contents								octet 2
0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	PRD		octet 3

Figure 9.9.3.67.1: EPS additional request result information element

Table 9.9.3.67.1: EPS additional request result information element

Paging restriction decision (PRD) (bits 2 to 1 of octet 3)
Bits
2	1
0	0	no additional information
0	1	paging restriction is accepted
1	0	paging restriction is rejected

All other values are reserved.
Bits 3 to 8 of octet 3 are spare and shall be coded as zero.

9.9.3.0A Additional update result

9.9.3.0B Additional update type

9.9.3.1 Authentication failure parameter

9.9.3.2 Authentication parameter AUTN

9.9.3.3 Authentication parameter RAND

9.9.3.4 Authentication response parameter

9.9.3.4A Ciphering key sequence number

9.9.3.4B SMS services status

9.9.3.5 CSFB response

9.9.3.6 Daylight saving time

9.9.3.7 Detach type

9.9.3.8 DRX parameter

9.9.3.9 EMM cause

9.9.3.10 EPS attach result

9.9.3.11 EPS attach type

9.9.3.12 EPS mobile identity

9.9.3.12A EPS network feature support

9.9.3.13 EPS update result

9.9.3.14 EPS update type

9.9.3.15 ESM message container

9.9.3.16 GPRS timer

9.9.3.16A GPRS timer 2

9.9.3.16B GPRS timer 3

9.9.3.17 Identity type 2

9.9.3.18 IMEISV request

9.9.3.19 KSI and sequence number

9.9.3.20 MS network capability

9.9.3.20A MS network feature support

9.9.3.21 NAS key set identifier

9.9.3.22 NAS message container

9.9.3.23 NAS security algorithms

9.9.3.24 Network name

9.9.3.24A Network resource identifier container

9.9.3.25 Nonce

9.9.3.25A Paging identity

9.9.3.26 P-TMSI signature

9.9.3.26A Extended EMM cause

9.9.3.27 Service type

9.9.3.28 Short MAC

9.9.3.29 Time zone

9.9.3.30 Time zone and time

9.9.3.31 TMSI status

9.9.3.32 Tracking area identity

9.9.3.33 Tracking area identity list

9.9.3.34 UE network capability

9.9.3.35 UE radio capability information update needed

9.9.3.36 UE security capability

9.9.3.37 Emergency Number List

9.9.3.37A Extended emergency number list

9.9.3.38 CLI

9.9.3.39 SS Code

9.9.3.40 LCS indicator

9.9.3.41 LCS client identity

9.9.3.42 Generic message container type

9.9.3.43 Generic message container

9.9.3.44 Voice domain preference and UE’s usage setting

9.9.3.45 GUTI type

9.9.3.46 Extended DRX parameters

9.9.3.47 Control plane service type

9.9.3.48 DCN-ID

9.9.3.49 Non-3GPP NW provided policies

9.9.3.50 HashMME

9.9.3.51 Replayed NAS message container

9.9.3.52 Network policy

9.9.3.53 UE additional security capability

9.9.3.54 UE status

9.9.3.55 Additional information requested

9.9.3.56 Ciphering key data

9.9.3.57 N1 UE network capability

9.9.3.58 UE radio capability ID availability

9.9.3.59 UE radio capability ID request

9.9.3.60 UE radio capability ID

9.9.3.61 UE radio capability ID deletion indication

9.9.3.62 WUS assistance information

9.9.3.63 NB-S1 DRX parameter

9.9.3.64 IMSI offset

9.9.3.65 UE request type

9.9.3.66 Paging restriction

9.9.3.67 EPS additional request result

9.9.3.50 Hash_MME