9.11.3 5GS mobility management (5GMM) information elements

24.5013GPPNon-Access-Stratum (NAS) protocol for 5G System (5GS)Release 17Stage 3TS

9.11.3.1 5GMM capability

The purpose of the 5GMM capability information element is to provide the network with information concerning aspects of the UE related to the 5GCN or interworking with the EPS. The contents might affect the manner in which the network handles the operation of the UE.

The 5GMM capability information element is coded as shown in figure 9.11.3.1.1 and table 9.11.3.1.1.

The 5GMM capability is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets.

8

7

6

5

4

3

2

1

5GMM capability IEI

octet 1

Length of 5GMM capability contents

octet 2

SGC

5G-IPHC-CP CIoT

N3 data

5G-CP CIoT

RestrictEC

LPP

HO attach

S1 mode

octet 3

RACS

NSSAA

5G-LCS

V2XCNPC5

V2XCEPC5

V2X

5G-UP CIoT

5GSRVCC

octet 4*

ProSe-l2relay

ProSe-dc

ProSe-dd

ER-NSSAI

5G-EHC-CP CIoT

multipleUP

WUSA

CAG

octet 5*

PR

RPR

PIV

NCR

NR-PSSI

ProSe-l3rmt

ProSe-l2rmt

ProSe-l3relay

octet 6*

spare

spare

spare

spare

spare

spare

MINT

NSSRG

octet 7*

0

0

0

0

0

0

0

0

octet 8*-15*

Spare

Figure 9.11.3.1.1: 5GMM capability information element

Table 9.11.3.1.1: 5GMM capability information element

EPC NAS supported (S1 mode) (octet 3, bit 1)

0

S1 mode not supported

1

S1 mode supported

ATTACH REQUEST message containing PDN CONNECTIVITY REQUEST message for handover support (HO attach) (octet 3, bit 2)

0

ATTACH REQUEST message containing PDN CONNECTIVITY REQUEST message with request type set to "handover" or "handover of emergency bearer services" to transfer PDU session from N1 mode to S1 mode not supported

1

ATTACH REQUEST message containing PDN CONNECTIVITY REQUEST message with request type set to "handover" or "handover of emergency bearer services" to transfer PDU session from N1 mode to S1 mode supported

LTE Positioning Protocol (LPP) capability (octet 3, bit 3)

0

LPP in N1 mode not supported

1

LPP in N1 mode supported (see 3GPP TS 36.355 [26])

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

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

0

Restriction on use of enhanced coverage not supported

1

Restriction on use of enhanced coverage supported

Control plane CIoT 5GS optimization (5G-CP CIoT) (octet 3, bit 5)

This bit indicates the capability for control plane CIoT 5GS optimization.

0

Control plane CIoT 5GS optimization not supported

1

Control plane CIoT 5GS optimization supported

N3 data transfer (N3 data) (octet 3, bit 6)

This bit indicates the capability for N3 data transfer.

0

N3 data transfer supported

1

N3 data transfer not supported

IP header compression for control plane CIoT 5GS optimization (5G-IPHC-CP CIoT) (octet 3, bit 7)

This bit indicates the capability for IP header compression for control plane CIoT 5GS optimization.

0

IP header compression for control plane CIoT 5GS optimization not supported

1

IP header compression for control plane CIoT 5GS optimization supported

Service gap control (SGC) (octet 3, bit 8)

0

service gap control not supported

1

service gap control supported

5G-SRVCC from NG-RAN to UTRAN (5GSRVCC) capability (octet 4, bit 1)

0

5G-SRVCC from NG-RAN to UTRAN not supported

1

5G-SRVCC from NG-RAN to UTRAN supported (see 3GPP TS 23.216 [6A])

User plane CIoT 5GS optimization (5G-UP CIoT) (octet 4, bit 2)

This bit indicates the capability for user plane CIoT 5GS optimization.

0

User plane CIoT 5GS optimization not supported

1

User plane CIoT 5GS optimization supported

V2X capability (V2X) (octet 4, bit 3)

This bit indicates the capability for V2X, as specified in 3GPP TS 24.587 [19B].

Bit

3

0

V2X not supported

1

V2X supported

V2X communication over E-UTRA-PC5 capability (V2XCEPC5) (octet 4, bit 4)

This bit indicates the capability for V2X communication over E-UTRA-PC5, as specified in 3GPP TS 24.587 [19B].

Bit

4

0

V2X communication over E-UTRA-PC5 not supported

1

V2X communication over E-UTRA-PC5 supported

V2X communication over NR-PC5 capability (V2XCNPC5) (octet 4, bit 5)

This bit indicates the capability for V2X communication over NR-PC5, as specified in 3GPP TS 24.587 [19B].

Bit

5

0

V2X communication over NR-PC5 not supported

1

V2X communication over NR-PC5 supported

Location Services (5G-LCS) notification mechanisms capability (octet 4, bit 6)

0

LCS notification mechanisms not supported

1

LCS notification mechanisms supported (see 3GPP TS 23.273 [6B])

Network slice-specific authentication and authorization (NSSAA) (octet 4, bit 7)

This bit indicates the capability to support network slice-specific authentication and authorization.

0

Network slice-specific authentication and authorization not supported

1

Network slice-specific authentication and authorization supported

Radio capability signalling optimisation (RACS) capability (octet 4, bit 8)

0

RACS not supported

1

RACS supported

Closed Access Group (CAG) capability (octet 5, bit 1)

0 CAG not supported

1 CAG supported

WUS assistance (WUSA) information reception capability (octet 5, bit 2)

0 WUS assistance information reception not supported

1 WUS assistance information reception supported

Multiple user-plane resources support (multipleUP) (octet 5, bit 3)

This bit indicates the capability to support multiple user-plane resources in NB-N1 mode.

0

Multiple user-plane resources not supported

1

Multiple user-plane resources supported

Ethernet header compression for control plane CIoT 5GS optimization (5G-EHC-CP CIoT) (octet 5, bit 4)

0 Ethernet header compression for control plane CIoT 5GS optimization not supported

1 Ethernet header compression for control plane CIoT 5GS optimization supported

Extended rejected NSSAI support (ER-NSSAI) (octet 5, bit 5)

This bit indicates the capability to support extended rejected NSSAI.

0

Extended rejected NSSAI not supported

1

Extended rejected NSSAI supported

ProSe direct discovery (ProSe-dd) (octet 5, bit 6)

This bit indicates the capability for ProSe direct discovery.

Bit

6

0

ProSe direct discovery not supported

1

ProSe direct discovery supported

ProSe direct communication (ProSe-dc) (octet 5, bit 7)

This bit indicates the capability for ProSe direct communication.

Bit

7

0

ProSe direct communication not supported

1

ProSe direct communication supported

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

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

Bit

8

0

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

1

Acting as a ProSe layer-2 UE-to-network relay UE supported

ProSe layer-3 UE-to-network-relay (ProSe-l3relay) (octet 6, bit 1)

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

Bit

1

0

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

1

Acting as a ProSe layer-3 UE-to-network relay UE supported

ProSe layer-2 UE-to-network-remote (ProSe-l2rmt) (octet 6, bit 2)

This bit indicates the capability to act as a layer-2 ProSe UE-to-network remote UE

Bit

2

0

Acting as a ProSe layer-2 UE-to-network remote UE not supported

1

Acting as a ProSe layer-2 UE-to-network remote UE supported

ProSe layer-3 UE-to-network-remote (ProSe-l3rmt) (octet 6, bit 3)

This bit indicates the capability to act as a layer-3 ProSe UE-to-network remote UE

3

0

Acting as a ProSe layer-3 UE-to-network remote UE not supported

1

Acting as a ProSe layer-3 UE-to-network remote UE supported

NR paging subgroup support indication (NR-PSSI) (octet 6, bit 4)

This bit indicates the capability to support NR paging subgrouping

4

0

NR paging subgrouping not supported

1

NR paging subgrouping supported

N1 NAS signalling connection release (NCR) (octet 6, bit 5)

This bit indicates whether N1 NAS signalling connection release is supported.

Bit

5

0

N1 NAS signalling connection release not supported

1

N1 NAS signalling connection release supported

Paging indication for voice services (PIV) (octet 6, bit 6)

This bit indicates whether paging indication for voice services is supported.

Bit

6

0

paging indication for voice services not supported

1

paging indication for voice services supported

Reject paging request (RPR) (octet 6, bit 7)

This bit indicates whether reject paging request is supported.

Bit

7

0

reject paging request not supported

1

reject paging request supported

Paging restriction (PR) (octet 6, bit 8)

This bit indicates whether paging restriction is supported.

Bit

8

0

paging restrictions not supported

1

paging restrictions supported

NSSRG (octet 7, bit 1)

This bit indicates the capability to support the NSSRG.

0

NSSRG not supported

1

NSSRG supported

Minimization of service interruption (MINT) (octet 7, bit 2)

This bit indicates the capability to support Minimization of service interruption (MINT)

2

0

MINT not supported

1

MINT supported

bits 3-8 in octet 7 and bits in octets 8 to 15 are spare and shall be coded as zero, if the respective octet is included in the information element.

9.11.3.2 5GMM cause

The purpose of the 5GMM cause information element is to indicate the reason why a 5GMM request from the UE is rejected by the network.

The 5GMM cause information element is coded as shown in figure 9.11.3.2.1 and table 9.11.3.2.1.

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

8

7

6

5

4

3

2

1

5GMM cause IEI

octet 1

Cause value

octet 2

Figure 9.11.3.2.1: 5GMM cause information element

Table 9.11.3.2.1: 5GMM cause information element

Cause value (octet 2)

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

1

1

Illegal UE

0

0

0

0

0

1

0

1

PEI not accepted

0

0

0

0

0

1

1

0

Illegal ME

0

0

0

0

0

1

1

1

5GS 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 de-registered

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

1

No suitable cells in tracking area

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

1

0

Non-5G authentication unacceptable

0

0

0

1

1

0

1

1

N1 mode not allowed

0

0

0

1

1

1

0

0

Restricted service area

0

0

0

1

1

1

1

1

Redirection to EPC required

0

0

1

0

1

0

1

1

LADN not available

0

0

1

1

1

1

1

0

No network slices available

0

1

0

0

0

0

0

1

Maximum number of PDU sessions reached

0

1

0

0

0

0

1

1

Insufficient resources for specific slice and DNN

0

1

0

0

0

1

0

1

Insufficient resources for specific slice

0

1

0

0

0

1

1

1

ngKSI already in use

0

1

0

0

1

0

0

0

Non-3GPP access to 5GCN not allowed

0

1

0

0

1

0

0

1

Serving network not authorized

0

1

0

0

1

0

1

0

Temporarily not authorized for this SNPN

0

1

0

0

1

0

1

1

Permanently not authorized for this SNPN

0

1

0

0

1

1

0

0

Not authorized for this CAG or authorized for CAG cells only

0

1

0

0

1

1

0

1

Wireline access area not allowed

0

1

0

0

1

1

1

0

PLMN not allowed to operate at the present UE location

0

1

0

0

1

1

1

1

UAS services not allowed

0

1

0

1

1

0

1

0

Payload was not forwarded

0

1

0

1

1

0

1

1

DNN not supported or not subscribed in the slice

0

1

0

1

1

1

0

0

Insufficient user-plane resources for the PDU session

0

1

0

1

1

1

0

1

Onboarding services terminated

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.11.3.2A 5GS DRX parameters

The purpose of the 5GS DRX parameters information element is to indicate that the UE wants to use DRX and for the network to indicate the DRX cycle value to be used at paging.

The 5GS DRX parameters is a type 4 information element with a length of 3 octets.

The 5GS DRX parameters information element is coded as shown in figure 9.11.3.2A.1 and table 9.11.3.2A.1.

The value part of a DRX parameter information element is coded as shown in table 9.11.3.2A.1.

8

7

6

5

4

3

2

1

5GS DRX parameters IEI

octet 1

Length of 5GS DRX parameters contents

octet 2

0

0

0

0

DRX value

spare

octet 3

Figure 9.11.3.2A.1: 5GS DRX parameters information element

Table 9.11.3.2A.1: 5GS DRX parameters information element

DRX value (bits 4 to 1 of octet 3)

This field represents the DRX cycle parameter ‘T’ as defined in 3GPP TS 38.304 [28] or 3GPP TS 36.304 [25C].

Bits

4

3

2

1

0

0

0

0

DRX value not specified

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

All other values shall be interpreted as "DRX value not specified" by this version of the protocol.

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

9.11.3.3 5GS identity type

The purpose of the 5GS identity type information element is to specify which identity is requested.

The 5GS identity type is a type 1 information element.

The 5GS identity type information element is coded as shown in figure 9.11.3.3.1 and table 9.11.3.3.1.

8

7

6

5

4

3

2

1

5GS identity type

IEI

0

spare

Type of

identity

octet 1

Figure 9.11.3.3.1: 5GS identity type information element

Table 9.11.3.3.1: 5GS identity type information element

Type of identity (octet 1)

Bits

3

2

1

0

0

1

SUCI

0

1

0

5G-GUTI

0

1

1

IMEI

1

0

0

5G-S-TMSI

1

0

1

IMEISV

1

1

0

MAC address

1

1

1

EUI-64

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

9.11.3.4 5GS mobile identity

The purpose of the 5GS mobile identity information element is to provide either the SUCI, the 5G-GUTI, the IMEI, the IMEISV, the 5G-S-TMSI, the MAC address or the EUI-64.

The 5GS mobile identity information element is coded as shown in figures 9.11.3.4.1, 9.11.3.4.2, 9.11.3.4.3, 9.11.3.4.4, 9.11.3.4.5, 9.11.3.4.6, 9.11.3.4.8 and 9.11.3.4.7, and table 9.11.3.4.1.

The 5GS mobile identity is a type 6 information element with a minimum length of 4.

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

1

1

1

1

0

spare

Type of identity

octet 4

MCC digit 2

MCC digit 1

octet 5

MNC digit 3

MCC digit 3

octet 6

MNC digit 2

MNC digit 1

octet 7

AMF Region ID

octet 8

AMF Set ID

octet 9

AMF Set ID (continued)

AMF Pointer

octet 10

5G-TMSI

octet 11

5G-TMSI (continued)

octet 12

5G-TMSI (continued)

octet 13

5G-TMSI (continued)

octet 14

Figure 9.11.3.4.1: 5GS mobile identity information element for type of identity "5G-GUTI"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

Identity digit 1

odd/

even

indic

Type of identity

octet 4

Identity digit p+1

Identity digit p

octet 5*

Figure 9.11.3.4.2: 5GS mobile identity information element for type of identity "IMEI" or "IMEISV"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

0

spare

SUPI format

0

spare

Type of identity

octet 4

MCC digit 2

MCC digit 1

octet 5

MNC digit 3

MCC digit 3

octet 6

MNC digit 2

MNC digit 1

octet 7

Routing indicator digit 2

Routing indicator digit 1

octet 8

Routing indicator digit 4

Routing indicator digit 3

octet 9

0

Spare

0

Spare

0

Spare

0

Spare

Protection scheme Id

octet 10

Home network public key identifier

octet 11

Scheme output

octet 12 – x

Figure 9.11.3.4.3: 5GS mobile identity information element for type of identity "SUCI" and SUPI format "IMSI"

8

7

6

5

4

3

2

1

MSIN digit 2

MSIN digit 1

octet 12

MSIN digit n+1

MSIN digit n

octet x

Figure 9.11.3.4.3a: Scheme output for type of identity "SUCI", SUPI format "IMSI" and Protection scheme Id "Null scheme"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

0

Spare

SUPI format

0

Spare

Type of identity

octet 4

SUCI NAI

octet 5 – y

Figure 9.11.3.4.4: 5GS mobile identity information element for type of identity "SUCI" and SUPI format "Network specific identifier", "GCI" or "GLI"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

1

1

1

1

0

spare

Type of identity

octet 4

AMF Set ID

octet 5

AMF Set ID (continued)

AMF Pointer

octet 6

5G-TMSI

octet 7

5G-TMSI (continued)

octet 8

5G-TMSI (continued)

octet 9

5G-TMSI (continued)

octet 10

Figure 9.11.3.4.5: 5GS mobile identity information element for type of identity "5G-S-TMSI"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

0

0

0

0

0

Type of identity

octet 4

spare

Figure 9.11.3.4.6: 5GS mobile identity information element for type of identity "No identity"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

0

spare

0

spare

0

spare

0

spare

MAURI

Type of identity

octet 4

MAC address

octet 5

octet 10

Figure 9.11.3.4.7: 5GS mobile identity information element for type of identity "MAC address"

8

7

6

5

4

3

2

1

5GS mobile identity IEI

octet 1

Length of 5GS mobile identity contents

octet 2

octet 3

0

spare

0

spare

0

spare

0

spare

0

spare

Type of identity

octet 4

EUI-64

octet 5

octet 12

Figure 9.11.3.4.8: 5GS mobile identity information element for type of identity "EUI-64"

Table 9.11.3.4.1: 5GS mobile identity information element

Type of identity (octet 4)

Bits

3

2

1

0

0

0

No identity (see NOTE 1)

0

0

1

SUCI

0

1

0

5G-GUTI

0

1

1

IMEI

1

0

0

5G-S-TMSI

1

0

1

IMEISV

1

1

0

MAC address

1

1

1

EUI-64

All other values are reserved.

Odd/even indication (octet 4)

Bit

4

0

even number of identity digits

1

odd number of identity digits

For the 5G-GUTI, then bits 5 to 8 of octet 4 are coded as "1111", octet 5 through 7 contain the MCC and MNC values as specified below, octet 8 through 10 contain the AMF Region ID, the AMF Set ID and the AMF Pointer values and octet 11 through 14 contain the 5G-TMSI as defined in 3GPP TS 23.003 [4].

MCC, Mobile country code (octet 5, octet 6 bits 1 to 4)

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

MNC, Mobile network code (octet 6 bits 5 to 8, octet 7)

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 6 shall be coded as "1111".

The contents of 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 [12].

AMF Region ID (octet 8)

This field contains the binary encoding of the AMF Region ID. Bit 8 of octet 7 is the most significant bit and bit 1 of octet 7 is the least significant bit.

AMF Set ID (octet 9, octet 10 bits 7 to 8)

This field contains the binary encoding of the AMF Set ID. Bit 8 of octet 9 is the most significant bit and bit 7 of octet 10 is the least significant bit.

AMF Pointer (octet 10 bits 1 to 6)

This field contains the binary encoding of the AMF Pointer. Bit 6 of octet 9 is the most significant bit and bit 1 of octet 9 is the least significant bit.

5G-TMSI (octet 11 to 14)

Bit 8 of octet 11 is the most significant bit and bit 1 of octet 14 is the least significant bit.

Identity digit (octet 4 bits 5 to 8, octet 5 etc.)

For the IMEI, Identity digit 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". The format of the IMEI is described in 3GPP TS 23.003 [4].

For the IMEISV, Identity digit field is coded using BCD coding. Bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". The format of the IMEISV is described in 3GPP TS 23.003 [4].

For the SUCI, bit 8 of octet 4 is spare and shall be coded as zero. Bits 5-7 of octet 4 contain the SUPI format and are coded as shown below.

SUPI format (octet 4, bits 5-7)

Bits

7

6

5

0

0

0

IMSI

0

0

1

Network specific identifier

0

1

0

GCI

0

1

1

GLI

All other values are interpreted as IMSI by this version of the protocol.

For the SUCI with SUPI format "IMSI", octets 5 through 7 contain the MCC and MNC values as specified below. For subsequent fields, bit 8 of octet 8 is the most significant bit and bit 1 of the last octet the least significant bit. The required fields for the SUCI are as defined in 3GPP TS 23.003 [4].

MCC, Mobile country code (octet 5, octet 6 bits 1 to 4)

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

MNC, Mobile network code (octet 6 bits 5 to 8, octet 7)

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 6 shall be coded as "1111".

The contents of 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 [12].

Routing indicator (octets 8-9)

Routing Indicator shall consist of 1 to 4 digits. The coding of this field is the responsibility of home network operator but BCD coding shall be used. If a network operator decides to assign less than 4 digits to Routing Indicator, the remaining digits shall be coded as "1111" to fill the 4 digits coding of Routing Indicator (see NOTE 2). If no Routing Indicator is configured in the USIM, the UE shall code bits 1 to 4 of octet 8 of the Routing Indicator as "0000" and the remaining digits as "1111".

Protection scheme identifier (octet 10 bits 1 to 4)

Bits

4

3

2

1

0

0

0

0

Null scheme

0

0

0

1

ECIES scheme profile A

0

0

1

0

ECIES scheme profile B

0

0

1

1

to

Reserved

1

0

1

1

1

1

0

0

to

Operator-specific protection scheme

1

1

1

1

Bits 5-8 of octet 10 are spare and shall be coded as zero.

Home network public key identifier (octet 11)

The Home network public key identifier (PKI) field is coded as defined in 3GPP TS 23.003 [4]. Home network public key identifier shall be coded as "00000000" when Protection scheme identifier is set to "0000" (i.e. Null scheme).

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

0

Home network PKI value 0

0

0

0

0

0

0

0

1

to

Home network PKI value (1-254)

1

1

1

1

1

1

1

0

1

1

1

1

1

1

1

1

Reserved

Scheme output (octets 12 to x)

The Scheme output field consists of a string of characters with a variable length or hexadecimal digits as specified in 3GPP TS 23.003 [4]. If Protection scheme identifier is set to "0000" (i.e. Null scheme), then the Scheme output consists of the MSIN and is coded using BCD coding with each digit of the MSIN coded over 4 bits. If the MSIN includes an odd number of digits, bits 5 to 8 of octet x shall be coded as "1111". If Protection scheme identifier is not "0000" (i.e. ECIES scheme profile A, ECIES scheme profile B or Operator-specific protection scheme), then Scheme output is coded as hexadecimal digits.

For the SUCI with SUPI format set to "Network specific identifier", the SUCI NAI field contains an NAI constructed as specified in subclause 28.7.3 of 3GPP TS 23.003 [4] and encoded as UTF-8 string.

For the SUCI with SUPI format set to "GCI", the SUCI NAI field contains an NAI constructed as specified in subclause 28.15.5 of 3GPP TS 23.003 [4] and encoded as UTF-8 string.

For the SUCI with SUPI format set to "GLI", the SUCI NAI field contains an NAI constructed as specified in subclause 28.16.5 of 3GPP TS 23.003 [4] and encoded as UTF-8 string.

For the 5G-S-TMSI, bits 5 to 8 of octet 4 are coded as "1111". The coding of the 5G-S-TMSI is left open for each administration.

AMF Set ID (octet 5, octet 6 bits 7 to 8)

This field contains the binary encoding of the AMF Set ID. Bit 8 of octet 5 is the most significant bit and bit 7 of octet 6 is the least significant bit.

AMF Pointer (octet 6 bits 1 to 6)

This field contains the binary encoding of the AMF Pointer. Bit 6 of octet 6 is the most significant bit and bit 1 of octet 6 is the least significant bit.

5G-TMSI (octet 7 to 10)

Bit 8 of octet 7 is the most significant bit and bit 1 of octet 10 is the least significant bit.

For Type of identity "No identity", the length of mobile identity contents parameter shall be set to 1 and the bits 4-8 of octet 4 are spare and shall be coded as zero.

MAC address usage restriction indication (MAURI) (octet 4 bit 4)

Bit

4

0

No restrictions

1

MAC address is not usable as an equipment identifier

MAC address (octets 5 to 10)

This field contains the MAC address as defined in subclause 8 of IEEE Std 802 [43].

Bit 8 of octet 5 is the most significant bit and bit 1 of octet 10 is the least significant bit.

EUI-64 (octets 5 to 12)

This field contains an EUI-64 as defined in [48].

Bit 8 of octet 5 is the most significant bit and bit 1 of octet 12 is the least significant bit.

NOTE 1: This can be used when the requested identity is not available at the UE during the identification procedure.

NOTE 2: For a 3-digit Routing Indicator, e.g "567", bits 1 to 4 of octet 8 are coded as "0101", bits 5 to 8 of octet 8 are coded as "0110", bits 1 to 4 of octet 9 are coded as "0111", bits 5 to 8 of octet 9 are coded as "1111".

9.11.3.5 5GS network feature support

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

The 5GS network feature support information element is coded as shown in figure 9.11.3.5.1 and table 9.11.3.5.1.

The 5GS 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 as defined in figure 9.11.3.5.1 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 coded as zero.

8

7

6

5

4

3

2

1

5GS network feature support IEI

octet 1

Length of 5GS network feature support contents

octet 2

MPSI

IWK N26

EMF

EMC

IMS- VoPS-N3GPP

IMS- VoPS-3GPP

octet 3

5G-UP CIoT

5G-IPHC-CP CIoT

N3 data

5G-CP CIoT

RestrictEC

MCSI

EMCN3

octet 4*

0 Spare

PR

RPR

PIV

NCR

5G-EHC-CP CIoT

ATS-IND

5G-LCS

octet 5*

Figure 9.11.3.5.1: 5GS network feature support information element

Table 9.11.3.5.1: 5GS network feature support information element

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

This bit indicates the support of IMS voice over PS session over 3GPP access (see NOTE 1).

Bit

1

0

IMS voice over PS session not supported over 3GPP access

1

IMS voice over PS session supported over 3GPP access

IMS voice over PS session over non-3GPP access indicator (IMS-VoPS-N3GPP) (octet 3, bit 2)

This bit indicates the support of IMS voice over PS session over non-3GPP access.

Bit

2

0

IMS voice over PS session not supported over non-3GPP access

1

IMS voice over PS session supported over non-3GPP access

Emergency service support indicator for 3GPP access (EMC) (octet 3, bit 3 and bit 4)

These bits indicate the support of emergency services in 5GS for 3GPP access (see NOTE 1).

Bits

4

3

0

0

Emergency services not supported

0

1

Emergency services supported in NR connected to 5GCN only

1

0

Emergency services supported in E-UTRA connected to 5GCN only

1

1

Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN

Emergency services fallback indicator for 3GPP access (EMF) (octet 3, bit 5 and bit 6)

These bits indicate the support of emergency services fallback for 3GPP access (see NOTE 1).

Bits

6

5

0

0

Emergency services fallback not supported

0

1

Emergency services fallback supported in NR connected to 5GCN only

1

0

Emergency services fallback supported in E-UTRA connected to 5GCN only

1

1

Emergency services fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN

Interworking without N26 interface indicator (IWK N26) (octet 3, 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

MPS indicator (MPSI) (octet 3, bit 8)

This bit indicates the validity of MPS.

Bit

8

0

Access identity 1 not valid

1

Access identity 1 valid

Emergency service support for non-3GPP access indicator (EMCN3) (octet 4, bit 1)

This bit indicates the support of emergency services in 5GS for non-3GPP access.

Bit (see NOTE 2)

1

0

Emergency services not supported over non-3GPP access

1

Emergency services supported over non-3GPP access

MCS indicator (MCSI) (octet 4, bit 2)

This bit indicates the validity of MCS.

Bit

2

0

Access identity 2 not valid

1

Access identity 2 valid

Restriction on enhanced coverage (RestrictEC) (octet 4, bit 3 and bit 4)

These bits indicate enhanced coverage restricted information.

In WB-N1 mode these bits are set as follows:

Bits

3

4

0

0

Both CE mode A and CE mode B are not restricted

0

1

Both CE mode A and CE mode B are restricted

1

0

CE mode B is restricted

1

1

Reserved

In NB-N1 mode these bits are set as follows

Bits

3

4

0

0

Use of enhanced coverage is not restricted

0

1

Use of enhanced coverage is restricted

1

0

Reserved

1

1

Reserved

Control plane CIoT 5GS optimization (5G-CP CIoT) (octet 4, bit 5)

This bit indicates the capability for control plane CIoT 5GS optimization.

Bit

5

0

Control plane CIoT 5GS optimization not supported

1

Control plane CIoT 5GS optimization supported

N3 data transfer (N3 data) (octet 4, bit 6)

This bit indicates the capability for N3 data transfer.

Bit

6

0

N3 data transfer supported

1

N3 data transfer not supported

IP header compression for control plane CIoT 5GS optimization (5G-IPHC-CP CIoT) (octet 4, bit 7)

This bit indicates the capability for IP header compression for control plane CIoT 5GS optimization.

Bit

7

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 4, bit 8)

This bit indicates the capability for user plane CIoT 5GS optimization.

Bit

8

0

User plane CIoT 5GS optimization not supported

1

User plane CIoT 5GS optimization supported

Location Services indicator in 5GC (5G-LCS) (octet 5, bit 1)

Bit

1

0

Location services via 5GC not supported

1

Location services via 5GC supported

ATSSS support indicator (ATS-IND) (octet 5, bit 2)

This bit indicates the network support for ATSSS.

Bit

2

0

ATSSS not supported

1

ATSSS supported

Ethernet header compression for control plane CIoT 5GS optimization (5G-EHC-CP CIoT) (octet 5, bit 3)

This bit indicates the capability for Ethernet header compression for control plane CIoT 5GS optimization

Bit

3

0

Ethernet header compression for control plane CIoT 5GS optimization not supported

1

Ethernet header compression for control plane CIoT 5GS optimization supported

N1 NAS signalling connection release (NCR) (octet 5, bit 4)

This bit indicates whether N1 NAS signalling connection release is supported.

Bit

4

0

N1-NAS signalling connection release not supported

1

N1-NAS signalling connection release supported

Paging indication for voice services (PIV) (octet 5, bit 5)

This bit indicates whether paging indication for voice services is supported.

Bit

5

0

paging indication for voice services not supported

1

paging indication for voice services supported

Reject paging request (RPR) (octet 5, bit 6)

This bit indicates whether reject paging request is supported.

Bit

6

0

reject paging request not supported

1

reject paging request supported

Paging restriction (PR) (octet 5, bit 7)

This bit indicates whether paging restriction is supported.

Bit

7

0

paging restriction not supported

1

paging restriction supported

Bit 8 in octet 5 is spare and shall be coded as zero.

NOTE 1: For a registration procedure over non-3GPP access, bit 1 of octet 3 and bits 3 to 6 of octet 3 are ignored.

NOTE 2: For a registration procedure over 3GPP access, bit 2 of octet 3 and vbit 1 of octet 4 are ignored.

9.11.3.6 5GS registration result

The purpose of the 5GS registration result information element is to specify the result of a registration procedure.

The 5GS registration result information element is coded as shown in figure 9.11.3.6.1 and table 9.11.3.6.1.

The 5GS registration result is a type 4 information element with a length of 3 octets.

8

7

6

5

4

3

2

1

5GS registration result IEI

octet 1

Length of 5GS registration result contents

octet 2

0

Spare

Disaster roaming registration result value

Emergency registered

NSSAA Performed

SMS allowed

5GS registration result value

octet 3

Figure 9.11.3.6.1: 5GS registration result information element

Table 9.11.3.6.1: 5GS registration result information element

5GS registration result value (octet 3, bits 1 to 3) (NOTE)

Bits

3

2

1

0

0

1

3GPP access

0

1

0

Non-3GPP access

0

1

1

3GPP access and non-3GPP access

1

1

1

reserved

All other values are unused and shall be treated as "3GPP access", if received by the UE.

SMS over NAS transport allowed (SMS allowed) (octet 3, bit 4) (NOTE)

Bit

4

0

SMS over NAS not allowed

1

SMS over NAS allowed

Network slice-specific authentication and authorization is to be performed (NSSAA to be performed) (octet 3, bit 5) (NOTE)

Bit

5

0

Network slice-specific authentication and authorization is not to be performed

1

Network slice-specific authentication and authorization is to be performed

Emergency registered (octet 3, bit 6)

Bit

6

0

Not registered for emergency services

1

Registered for emergency services

Disaster roaming registration result value (octet 3, bit 7)

Bit

7

0

No additional information

1

Request for registration for disaster roaming service accepted as registration not for disaster roaming service

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

NOTE: All bits other than bit 6 in octet 3 shall be ignored by the UE when the 5GS registration result IE is received in the CONFIGURATION UPDATE COMMAND message

9.11.3.7 5GS registration type

The purpose of the 5GS registration type information element is to indicate the type of the requested registration.

The 5GS registration type information element is coded as shown in figure 9.11.3.7.1 and table 9.11.3.7.1.

The 5GS registration type is a type 1 information element with a length of 1 octet.

8

7

6

5

4

3

2

1

5GS registration type IEI

FOR

5GS registration type value

octet 1

Figure 9.11.3.7.1: 5GS registration type information element

Table 9.11.3.7.1: 5GS registration type information element

5GS registration type value (octet 1, bits 1 to 3)

Bits

3

2

1

0

0

1

initial registration

0

1

0

mobility registration updating

0

1

1

periodic registration updating

1

0

0

emergency registration

1

0

1

SNPN onboarding registration

1

1

0

disaster roaming mobility registration updating

1

1

1

disaster roaming initial registration

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

Follow-on request bit (FOR) (octet 1, bit 4)

Bit

4

0

No follow-on request pending

1

Follow-on request pending

9.11.3.8 5GS tracking area identity

The purpose of the 5GS tracking area identity information element is to provide an unambiguous identification of tracking areas within the area covered by the 5GS.

The 5GS tracking area identity information element is coded as shown in figure 9.11.3.8.1 and table 9.11.3.8.1.

The 5GS tracking area identity is a type 3 information element with a length of 7 octets.

8

7

6

5

4

3

2

1

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

TAC (continued)

octet 7

Figure 9.11.3.8.1: 5GS tracking area identity information element

Table 9.11.3.8.1: 5GS tracking area identity information element

MCC, Mobile country code (octets 2 and 3)

The MCC field is coded as in ITU-T Rec. E212 [39], 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 (octets 5 to 7)

In the TAC field bit 8 of octet 5 is the most significant bit and bit 1 of octet 7 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 3 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.11.3.9 5GS tracking area identity list

The purpose of the 5GS 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 5GS tracking area identity list information element is coded as shown in figure 9.11.3.8.1, figure 9.11.3.8.2, figure 9.11.3.9.3, figure 9.11.3.9.4 and table 9.11.3.9.1.

The 5GS tracking area identity list is a type 4 information element, with a minimum length of 9 octets and a maximum length of 114 octets. The list can contain a maximum of 16 different tracking area identities.

8

7

6

5

4

3

2

1

5GS tracking area identity list IEI

octet 1

Length of 5GS 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.11.3.9.1: 5GS 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 1 (continued)

octet 7

TAC k

octet 3k+2*

TAC k (continued)

octet 3k+3*

TAC k (continued)

octet 3k+4*

Figure 9.11.3.9.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

TAC 1 (continued)

octet 7

Figure 9.11.3.9.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

TAC 1 (continued)

octet 7

MCC digit 2

MCC digit 1

octet 8*

MNC digit 3

MCC digit 3

octet 9*

MNC digit 2

MNC digit 1

octet 10*

TAC 2

octet 11*

TAC 2 (continued)

octet 12*

TAC 2 (continued)

octet 13*

MCC digit 2

MCC digit 1

octet 6k-4*

MNC digit 3

MCC digit 3

octet 6k-3*

MNC digit 2

MNC digit 1

octet 6k-2*

TAC k

octet 6k-1*

TAC k (continued)

octet 6k*

TAC k (continued)

octet 6k+1*

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

Table 9.11.3.9.1: Tracking area identity list information element

Value part of the Tracking area identity list information element (octets 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 or SNPN, with non-consecutive TAC values

0

1

list of TACs belonging to one PLMN or SNPN, 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:

octets 3j+2 to 3j+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

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

octets 6j-4 to 6j-2 contain the MCC+MNC, and

octets 6j-1 to 6j+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 [42], 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 third 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 3 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". This type of list is not applicable in an SNPN.

9.11.3.9A 5GS update type

The purpose of the 5GS update type IE is to allow the UE to provide additional information to the network when performing a registration procedure.

The 5GS update type information element is coded as shown in figure 9.11.3.9A.1 and table 9.11.3.9A.1.

The 5GS update type is a type 4 information element.

8

7

6

5

4

3

2

1

5GS update type IEI

octet 1

Length of 5GS update type

octet 2

0

Spare

0

Spare

EPS- PNB-CIoT

5GS-PNB-CIoT

NG-RAN-RCU

SMS requested

octet 3

Figure 9.11.3.9A.1: 5GS update type information element

Table 9.11.3.9A.1: 5GS update type information element

SMS over NAS transport requested (SMS requested) (octet 3, bit 1)

Bit

1

0

SMS over NAS not supported

1

SMS over NAS supported

NG-RAN Radio Capability Update (NG-RAN-RCU) (octet 3, bit 2)

Bit

2

0

UE radio capability update not needed

1

UE radio capability update needed

For a list of RATs for which a radio capability update can be triggered by means of this indication see subclause 5.5.1.3.2, case n).

5GS Preferred CIoT network behaviour (5GS PNB-CIoT) (octet 3, bits 3 and 4)

Bits

4

3

0

0

no additional information

0

1

control plane CIoT 5GS optimization

1

0

user plane CIoT 5GS optimization

1

1

reserved

EPS Preferred CIoT network behaviour (EPS-PNB-CIoT) (octet 3, bits 5 and 6)

Bits

6

5

0

0

no additional information

0

1

control plane CIoT EPS optimization

1

0

user plane CIoT EPS optimization

1

1

reserved

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

9.11.3.10 ABBA

The purpose of the ABBA information element is to enable the bidding down protection of security features.

The ABBA information element is coded as shown in figure 9.11.3.10.1 and table 9.11.3.10.1.

The ABBA is a type 4 information element with a minimum length of 4 octets.

8

7

6

5

4

3

2

1

ABBA IEI

octet 1

Length of ABBA contents

octet 2

ABBA contents

octet 3

octet n

Figure 9.11.3.10.1: ABBA information element

Table 9.11.3.10.1: ABBA information element

ABBA contents (octet 3-n):

indicate set of security features defined for 5GS as described in 3GPP TS 33.501 [24].

NOTE 1: If the UE receives the ABBA IE with a length that is set to a value of 2 and with a value of 0000H, the UE shall use the length and the contents of the ABBA IE as received from the network.

NOTE 2: If the UE receives the ABBA IE with a length that is set to a value larger than 2 or with a value that is different from 0000H, the UE shall use the length and the contents of the ABBA IE as received from the network.

9.11.3.11 Void

9.11.3.12 Additional 5G security information

The purpose of the Additional 5G security information information element is to provide the UE with additional security parameters (e.g. horizontal derivation parameter) or to request the UE to retransmit an initial NAS message during a security mode control procedure as defined in 3GPP TS 33.501 [24]. The UE uses these parameters for completion of security mode control procedure.

The Additional 5G security information information element is coded as shown in figure 9.11.3.12.1 and table 9.11.3.12.1.

The Additional 5G security information is a type 4 information element with a length of 3 octets.

8

7

6

5

4

3

2

1

Additional 5G security information IEI

octet 1

Length of Additional 5G security information contents

octet 2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

RINMR

HDP

octet 3

Figure 9.11.3.12.1: Additional 5G security information information element

Table 9.11.3.12.1: Additional 5G security information information element

Horizontal derivation parameter (HDP) (octet 3, bit 1)

0

KAMF derivation is not required

1

KAMF derivation is required

Retransmission of initial NAS message request (octet 3, bit 2)

0

Retransmission of the initial NAS message not requested

1

Retransmission of the initial NAS message requested

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

9.11.3.12A 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.11.3.12A.1 and table 9.11.3.12A.1.

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

8

7

6

5

4

3

2

1

Additional information requested IEI

octet 1

Length of additional information requested contents

octet 2

0

0

0

0

0

0

0

CipherKey

octet 3

Spare

Figure 9.11.3.12A.1: Additional information requested information element

Table 9.11.3.12A.1: Additional information requested information element

Ciphering keys for ciphered broadcast assistance data (CipherKey) (octet 3, 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 3 are spare and shall be coded as zero.

9.11.3.13 Allowed PDU session status

The purpose of the Allowed PDU session status information element is to indicate to the network user-plane resources of PDU sessions associated with non-3GPP access that are allowed to be re-established over 3GPP access or if there is no PDU session(s) for which the UE allows the user-plane resources to be re-established over 3GPP access.

NOTE: Allowed PDU session status IE is not applicable for MA PDU session(s) in this release of specification.

The Allowed PDU session status information element is coded as shown in figure 9.11.3.13.1 and table 9.11.3.13.1.

The Allowed PDU session status is a type 4 information element with minimum length of 4 octets and maximum length of 34 octets.

8

7

6

5

4

3

2

1

Allowed PDU session status IEI

octet 1

Length of Allowed PDU session status contents

octet 2

PSI

(7)

PSI

(6)

PSI

(5)

PSI

(4)

PSI

(3)

PSI

(2)

PSI

(1)

PSI

(0)

octet 3

PSI

(15)

PSI

(14)

PSI

(13)

PSI

(12)

PSI

(11)

PSI

(10)

PSI

(9)

PSI

(8)

octet 4

0

0

0

0

0

0

0

0

Spare

octet 5* -34*

Figure 9.11.3.13.1: Allowed PDU session status information element

Table 9.11.3.13.1: Allowed PDU session status information element

PSI(x) shall be coded as follows:

PSI(0):

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

PSI(1) – PSI(15):

0 indicates that the user-plane resources of corresponding PDU session is not allowed to be re-established over 3GPP access.

1 indicates that the user-plane resources of corresponding PDU session can be re-established over 3GPP access.

If there is no PDU session for which the user-plane resources can be re-established over 3GPP access, all bits in PSI(1) – PSI(15) shall be coded as zero.

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

9.11.3.14 Authentication failure parameter

See subclause 10.5.3.2.2 in 3GPP TS 24.008 [12].

9.11.3.15 Authentication parameter AUTN

See subclause 10.5.3.1.1 in 3GPP TS 24.008 [12].

9.11.3.16 Authentication parameter RAND

See subclause 10.5.3.1 in 3GPP TS 24.008 [12].

9.11.3.17 Authentication response parameter

See subclause 9.9.3.4 in 3GPP TS 24.301 [15].

9.11.3.18 Configuration update indication

The purpose of the Configuration update indication information element is to indicate the additional information associated with the generic UE configuration update procedure.

The Configuration update indication information element is coded as shown in figure 9.11.3.18.1 and table 9.11.3.18.1.

The Configuration update indication is a type 1 information element.

8

7

6

5

4

3

2

1

Configuration update indication IEI

0

Spare

0

Spare

RED

ACK

octet 1

Figure 9.11.3.18.1: Configuration update indication

Table 9.11.3.18.1: Configuration update indication

Acknowledgement (ACK) (octet 1, bit 1)

Bit

1

0

acknowledgement not requested

1

acknowledgement requested

Registration requested (RED) (octet 1, bit 2)

Bit

2

0

registration not requested

1

registration requested

Bits 3 and 4 are spare and shall be coded as zero,

9.11.3.18A CAG information list

The purpose of the CAG information list information element is to provide "CAG information list" or to delete the "CAG information list" at the UE.

The CAG information list information element is coded as shown in figures 9.11.3.18A.1 and 9.11.3.18A.2 and table 9.11.3.18A.1.

The CAG information list is a type 6 information element, with a minimum length of 3 octets.

8

7

6

5

4

3

2

1

CAG information list IEI

octet 1

Length of CAG information list contents

octet 2

octet 3

Entry 1

octet 4*

octet a*

Entry 2

octet a+1*

octet b*

octet b+1*

octet g*

Entry n

octet g+1*

octet h*

Figure 9.11.3.18A.1: CAG information list information element

8

7

6

5

4

3

2

1

Length of entry contents

octet q

MCC digit 2

MCC digit 1

octet q+1

MNC digit 3

MCC digit 3

octet q+2

MNC digit 2

MNC digit 1

octet q+3

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

CAG

only

octet q+4

CAG-ID 1

octet q+5*

octet q+8*

CAG-ID 2

octet q+9*

octet q+12*

octet q+13*

octet q+4m*

CAG-ID n

octet q+4m+1*

octet q+4m+4*

Figure 9.11.3.18A.2: Entry n

Table 9.11.3.18A.1: CAG information list information element

MCC, Mobile country code (octet q+1 and bits 1 to 4 octet q+2)

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

MNC, Mobile network code (bits 5 to 8 of octet q+2 and octet q+3)

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 q+2 shall be coded as "1111".

The contents of 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 [12].

Indication that the UE is only allowed to access 5GS via CAG cells (CAGonly) (bit 1 of octet q+4)

Bit

1

0

"Indication that the UE is only allowed to access 5GS via CAG cells" is not set (i.e., the UE is allowed to access 5GS via non-CAG cells)

1

"Indication that the UE is only allowed to access 5GS via CAG cells" is set (i.e., the UE is not allowed to access 5GS via non-CAG cells)

CAG-ID m (octet q+4m+1 to octet q+4m+4)

This field contains the 32 bit CAG-ID. The coding of the CAG-ID is defined as the CAG-Identifier in 3GPP TS 23.003 [4].

NOTE 1: The Length of CAG information list contents shall be 3 if no subscription data for CAG information list exists.

NOTE 2: The Length of entry contents shall be 4 if there is no allowed CAG-ID for the PLMN.

NOTE 3: Bit 2 in octet q+4 may be set to 1 in the USIM (see 3GPP TS 31.102 [22]).

NOTE 4: For a given PLMN ID, there shall be up to one Entry containing the MCC value and the MNC value of the PLMN ID.

9.11.3.18B CIoT small data container

This information element is used to encapsulate the CIoT user data, SMS, or location services message with a size that is not more than 254 octets between the UE and the AMF when the UE is using control plane CIoT 5GS optimization. The CIoT small data container information element is coded as shown in figure 9.11.3.18B.1, figure 9.11.3.18B.2, figure 9.11.3.18B.3, figure 9.11.3.18B.4 and table 9.11.3.18B.1.

The CIoT small data container is a type 4 information element with a minimum length of 4 octets and a maximum length of 257 octets.

8

7

6

5

4

3

2

1

CIoT small data container IEI

octet 1

Length of CIoT small data container contents

octet 2

octet 3

CIoT small data container contents

octet 257

Figure 9.11.3.18B.1: CIoT small data container information element

8

7

6

5

4

3

2

1

Data type

DDX

PDU session identity

octet 3

Data contents

octet 4

octet 257

Figure 9.11.3.18B.2: CIoT small data container contents for Data type "Control plane user data"

8

7

6

5

4

3

2

1

Data type

DDX

0

Spare

0

Spare

0

Spare

octet 3

Length of additional information

octet 4

Additional information

octet 5*

octet m*

Data contents

octet m+1

octet n

Figure 9.11.3.18B.3: CIoT small data container contents for Data type "Location services message container"

8

7

6

5

4

3

2

1

Data type

Spare

octet 3

Data contents

octet 4

octet n

Figure 9.11.3.18B.4: CIoT small data container contents for Data type "SMS"

Table 9.11.3.18B.1: CIoT small data container information element

CIoT small data container contents (octet 3 to octet 257)

These octets include user data to be delivered between UE and AMF.

Data type (octet 3, bits 6 to 8)

Bits

8

7

6

0

0

0

Control plane user data

0

0

1

SMS

0

1

0

Location services message container

All other values are spare.

When the Data type is "Control plane user data ", the PDU session identity and Downlink data expected (DDX) fields are encoded as follows:

PDU session identity (octet 3, bits 1 to 4)

Bit

3

2

1

0

0

0

No PDU session identity assigned

0

0

1

PDU session identity value 1

0

1

0

PDU session identity value 2

0

1

1

PDU session identity value 3

1

0

0

PDU session identity value 4

1

0

1

PDU session identity value 5

1

1

0

PDU session identity value 6

1

1

1

PDU session identity value 7

Downlink data expected (DDX) (octet 3, bits 5 to 6)

Bits

5

4

0

0

No information available

0

1

No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected

1

0

Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected

1

1

reserved

NOTE: The DDX field is only used in the UE to network direction.

Data contents (octet 4 to octet 257)

This field contains the control plane user data.

When the Data type is "SMS", Bits 1 to 5 of octet 3 are spare and shall be coded as zero.

Data contents (octet 4 to octet 257)

This field contains an SMS message.

When the Data type is "Location services message container":

Downlink data expected (DDX) (octet 3, bits 5 to 4)

This field is encoded as described above for the case when the Data type is "Control plane user data".

Bits 3 to 1 of octet 3 are spare and shall be encoded as zero.

Length of Additional information (octet 4) (see NOTE)

Indicates the length, in octets, of the Additional information field.

Additional information (octets 5 to m)

Contains additional information if provided by the upper layer location services application.

Data contents (octets m+1 to n)

Contains the location services message payload.

NOTE: The Length of Additional information shall be set to zero if the upper layer location service application does not provide routing information.

9.11.3.18C 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.11.3.18C.1, figure 9.11.3.18C.2 and table 9.11.3.18C.1.

The Ciphering key data is a type 6 information element, with a minimum length of 34 octets and a maximum length of 2675 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.11.3.18C.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

octet 20

octet k

0

0

0

0

E-UTRA posSIB length

octet k+1

Spare

PosSIBType1-1

PosSIBType1-2

PosSIBType1-3

PosSIBType1-4

PosSIBType1-5

PosSIBType1-6

PosSIBType1-7

PosSIBType1-8

octet k+2

octet k+3

PosSIBType2-1

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

PosSIBType2-20

PosSIBType2-21

PosSIBType2-22

PosSIBType2-23

PosSIBType2-24

PosSIBType2-25

PosSIBType3-1

PosSIBType4-1

PosSIBType5-1

0

Spare

0

Spare

0

Spare

0

Spare

octet p

0

0

0

0

NR posSIB length

octet p+1

Spare

PosSIBType1-1

PosSIBType1-2

PosSIBType1-3

PosSIBType1-4

PosSIBType1-5

PosSIBType1-6

PosSIBType1-7

PosSIBType1-8

octet p+2

octet p+3

octet q

PosSIBType2-1

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

PosSIBType2-20

PosSIBType2-21

PosSIBType2-22

PosSIBType2-23

PosSIBType3-1

PosSIBType4-1

PosSIBType5-1

PosSIBType6-1

PosSIBType6-2

PosSIBType6-3

0

Spare

0

Spare

0

Spare

Validity start time

octet q+1

octe q+5

Validity duration

octet q+6

octet q+7

TAIs list

octet q+8

octet r

Figure 9.11.3.18C.2: Ciphering data set

Table 9.11.3.18C.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 octect 19 are spare and shall be coded as zero.

c0 (octets 20 to k)

This field contains the binary encoding of the c0 counter.

E-UTRA posSIB length (octet k+1, bits 4 to 1)

This field contains the length in octets of the E -UTRA Positioning SIB types. A length of zero means E -UTRA Positioning SIB types are not included (see NOTE).

E-UTRA Positioning SIB types for which the ciphering data set is applicable (octets k+2 to p). Unassigned bits shall be ignored by a UE. Non-included bits shall be assumed to be zero by a UE.

Ciphering data set applicable for positioning SIB type 1-1 (octet k+2, 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+2, 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+2, 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+2, 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+2, 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+2, 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+2, 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 1-8 (octet k+2, bit 1)

0

Ciphering data set not applicable to positioning SIB type 1-8

1

Ciphering data set applicable to positioning SIB type 1-8

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

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+3, bit 7)

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+3, bit 6)

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+3, bit 5)

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+3, bit 4)

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+3, bit 3)

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+3, bit 2)

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+3, bit 1)

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+4, bit 8)

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+4, bit 7)

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+4, bit 6)

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+4, bit 5)

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+4, bit 4)

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+4, bit 3)

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+4, bit 2)

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+4, bit 1)

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+5, bit 8)

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+5, bit 7)

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+5, bit 6)

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 2-20 (octet k+5, bit 5)

0

Ciphering data set not applicable to positioning SIB type 2-20

1

Ciphering data set applicable to positioning SIB type 2-20

Ciphering data set applicable for positioning SIB type 2-21 (octet k+5, bit 4)

0

Ciphering data set not applicable to positioning SIB type 2-21

1

Ciphering data set applicable to positioning SIB type 2-21

Ciphering data set applicable for positioning SIB type 2-22 (octet k+5, bit 3)

0

Ciphering data set not applicable to positioning SIB type 2-22

1

Ciphering data set applicable to positioning SIB type 2-22

Ciphering data set applicable for positioning SIB type 2-23 (octet k+5, bit 2)

0

Ciphering data set not applicable to positioning SIB type 2-23

1

Ciphering data set applicable to positioning SIB type 2-23

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

0

Ciphering data set not applicable to positioning SIB type 2-24

1

Ciphering data set applicable to positioning SIB type 2-24

Ciphering data set applicable for positioning SIB type 2-25 (octet k+6, bit 8)

0

Ciphering data set not applicable to positioning SIB type 2-25

1

Ciphering data set applicable to positioning SIB type 2-25

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

0

Ciphering data set not applicable to positioning SIB type 3-1

1

Ciphering data set applicable to positioning SIB type 3-1

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

0

Ciphering data set not applicable to positioning SIB type 4-1

1

Ciphering data set applicable to positioning SIB type 4-1

Ciphering data set applicable for positioning SIB type 5-1 (octet k+6, bit 5)

0

Ciphering data set not applicable to positioning SIB type 5-1

1

Ciphering data set applicable to positioning SIB type 5-1

Any unassigned bits shall be coded as zero.

NR posSIB length (octet p+1, bits 4 to 1)

This field contains the length in octets of the NR Positioning SIB types. A length of zero means NR Positioning SIB types are not included (see NOTE).

NR Positioning SIB types for which the ciphering data set is applicable (octets p+2 to q). Unassigned bits shall be ignored. Non-included bits shall be assumed to be zero.

Ciphering data set applicable for positioning SIB type 1-1 (octet p+2, 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 p+2, 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 p+2, 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 p+2, 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 p+2, 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 p+2, 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 p+2, 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 1-8 (octet p+2, bit 1)

0

Ciphering data set not applicable to positioning SIB type 1-8

1

Ciphering data set applicable to positioning SIB type 1-8

Ciphering data set applicable for positioning SIB type 2-1 (octet p+3, bit 8)

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 p+3, bit 7)

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 p+3, bit 6)

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 p+3, bit 5)

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 p+3, bit 4)

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 p+3, bit 3)

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 p+3, bit 2)

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 p+3, bit 1)

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 p+4, bit 8)

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 p+4, bit 7)

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 p+4, bit 6)

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 p+4, bit 5)

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 p+4, bit 4)

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 p+4, bit 3)

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 p+4, bit 2)

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 p+4, bit 1)

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 p+5, bit 8)

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 p+5, bit 7)

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 p+5, bit 6)

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 2-20 (octet p+5, bit 5)

0

Ciphering data set not applicable to positioning SIB type 2-20

1

Ciphering data set applicable to positioning SIB type 2-20

Ciphering data set applicable for positioning SIB type 2-21 (octet p+5, bit 4)

0

Ciphering data set not applicable to positioning SIB type 2-21

1

Ciphering data set applicable to positioning SIB type 2-21

Ciphering data set applicable for positioning SIB type 2-22 (octet p+5, bit 3)

0

Ciphering data set not applicable to positioning SIB type 2-22

1

Ciphering data set applicable to positioning SIB type 2-22

Ciphering data set applicable for positioning SIB type 2-23 (octet p+5, bit 2)

0

Ciphering data set not applicable to positioning SIB type 2-23

1

Ciphering data set applicable to positioning SIB type 2-23

Ciphering data set applicable for positioning SIB type 3-1 (octet p+5, bit 1)

0

Ciphering data set not applicable to positioning SIB type 3-1

1

Ciphering data set applicable to positioning SIB type 3-1

Ciphering data set applicable for positioning SIB type 4-1 (octet p+6, bit 8)

0

Ciphering data set not applicable to positioning SIB type 4-1

1

Ciphering data set applicable to positioning SIB type 4-1

Ciphering data set applicable for positioning SIB type 5-1 (octet p+6, bit 7)

0

Ciphering data set not applicable to positioning SIB type 5-1

1

Ciphering data set applicable to positioning SIB type 5-1

Ciphering data set applicable for positioning SIB type 6-1 (octet p+6, bit 6)

0

Ciphering data set not applicable to positioning SIB type 6-1

1

Ciphering data set applicable to positioning SIB type 6-1

Ciphering data set applicable for positioning SIB type 6-2 (octet p+6, bit 5)

0

Ciphering data set not applicable to positioning SIB type 6-2

1

Ciphering data set applicable to positioning SIB type 6-3

Ciphering data set applicable for positioning SIB type 6-3 (octet p+6, bit 4)

0

Ciphering data set not applicable to positioning SIB type 6-3

1

Ciphering data set applicable to positioning SIB type 6-3

Any unassigned bits shall be coded as zero.

Validity start time (octets q+1 to q+5)

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 [12].

Validity duration (octets q+6 to q+7)

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 q+8 to r)

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 subclause 9.11.3.9. If the TAIs list is empty (as indicated by a zero length), the ciphering data set is applicable to the entire serving PLMN.

NOTE: The ciphering data set is always applicable to at least one of the E -UTRA Positioning SIB types or the NR Positioning SIB types.

9.11.3.18D 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.11.3.18D.1 and table 9.11.3.18D.1.

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

8

7

6

5

4

3

2

1

Control plane service type

IEI

0

Spare

Control plane service type

value

octet 1

Figure 9.9.3.18D.1: Control plane service type information element

Table 9.9.3.18D.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

emergency services

0

1

1

emergency services fallback

1

0

0

to

unused; shall be interpreted as " mobile originating request", if received by the network.

1

1

1

9.11.3.19 Daylight saving time

See subclause 10.5.3.12 in 3GPP TS 24.008 [12].

9.11.3.20 De-registration type

The purpose of the De-registration type information element is to indicate the type of de-registration.

The De-registration type information element is coded as shown in figure 9.11.3.20.1 and table 9.11.3.20.1.

The De-registration type is a type 1 information element.

8

7

6

5

4

3

2

1

De-registration type

IEI

Switch

off

Re-registration required

Access type

octet 1

Figure 9.11.3.20.1: Deregistration type information element

Table 9.11.3.20.1: Deregistration type information element

Switch off (octet 1, bit 4)

In the UE to network direction:

Bit

4

0

Normal de-registration

1

Switch off

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

Re-registration required (octet 1, bit 3)

In the network to UE direction:

Bit

3

0

re-registration not required

1

re-registration required

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

Access type (octet 1,bit 2, bit 1)

Bit

2

1

0

1

3GPP access

1

0

Non-3GPP access

1

1

3GPP access and non-3GPP access

All other values are reserved.

9.11.3.21 Void

9.11.3.22 Void

9.11.3.23 Emergency number list

See subclause 10.5.3.13 in 3GPP TS 24.008 [12].

9.11.3.23A EPS bearer context status

See subclause 9.9.2.1 in 3GPP TS 24.301 [15].

9.11.3.24 EPS NAS message container

The purpose of the EPS NAS message container information element is to transport an EPS NAS message as specified in 3GPP TS 24.301 [15].

The EPS NAS message container information element is coded as shown in figure 9.11.3.24.1 and table 9.11.3.24.1.

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

8

7

6

5

4

3

2

1

EPS NAS message container IEI

octet 1

Length of EPS NAS message container contents

octet 2

octet 3

EPS NAS message container

octet 4

octet n

Figure 9.11.3.24.1: EPS NAS message container information element

Table 9.11.3.24.1: EPS NAS message container information element

EPS NAS message container (octet 4 to n)

An EPS NAS message as specified in 3GPP TS 24.301 [15].

9.11.3.25 EPS NAS security algorithms

See subclause 9.9.3.23 in 3GPP TS 24.301 [15].

9.11.3.26 Extended emergency number list

See subclause 9.9.3.37A in 3GPP TS 24.301 [15].

9.11.3.26A Extended DRX parameters

See subclause 10.5.5.32 in 3GPP TS 24.008 [12].

9.11.3.27 Void

9.11.3.28 IMEISV request

See subclause 10.5.5.10 in 3GPP TS 24.008 [12].

9.11.3.29 LADN indication

The purpose of the LADN indication information element is to request the network for LADN information for specific LADN DNN(s) or to indicate a request for LADN information.

The LADN indication information element is coded as shown in figure 9.11.3.29.1 and table 9.11.3.29.1.

The LADN indication is a type 6 information element with a minimum length of 3 octets and a maximum length of 811 octets.

The LADN indication information element can contain a minimum of 0 and a maximum of 8 different LADN DNN values.

8

7

6

5

4

3

2

1

LADN indication IEI

octet 1

Length of LADN indication contents

octet 2

octet 3

LADN DNN value 1

octet 4*

octet a*

LADN DNN value 2

octet a+1*

octet b*

octet b+1*

octet g*

LADN DNN value n

octet g+1*

octet h*

Figure 9.11.3.29.1: LADN indication information element

Table 9.11.3.29.1: LADN indication information element

Value part of the LADN indication information element (octet 4 to h):

The value part of the LADN indication information element consists of zero or more LADN DNN values. If the LADN indication information element conveys more than 8 LADN DNN values in this information element, the network shall consider the first 8 LADN DNN values and ignore the remaining octets of the information element.

LADN DNN value:

LADN DNN value is coded as the length and value part of DNN information element as specified in subclause 9.11.2.1B starting with the second octet.

9.11.3.30 LADN information

The purpose of the LADN information information element is to provide the UE with the LADN service area for each available LADN in the current registration area or to delete the LADN information at the UE.

The LADN information information element is coded as shown in figure 9.11.3.30.1, figure 9.11.3.30.2 and table 9.11.3.30.1.

The LADN information is a type 6 information element with a minimum length of 3 octets and a maximum length of 1715 octets.

The LADN information information element can contain a minimum of 0 and a maximum of 8 different LADNs each including a DNN and a 5GS tracking area identity list.

8

7

6

5

4

3

2

1

LADN information IEI

octet 1

Length of LADN information contents

octet 2

octet 3

LADN 1

octet 4

octet a

LADN 2

octet a+1*

octet b*

octet b+1*

octet g*

LADN n

octet g+1*

octet h*

Figure 9.11.3.30.1: LADN information information element

8

7

6

5

4

3

2

1

Length of DNN value

octet 4

DNN value

octet 5

octet m

5GS tracking area identity list

octet m+1

octet a

Figure 9.11.3.30.2: LADN

Table 9.11.3.30.1: LADN information information element

Value part of the LADN information information element (octet 4 to octet h)

The value part of the LADN information information element consists of one or several LADNs. Each LADN (e.g. octet 4 to octet a) consists one DNN value and one 5GS tracking area identity list. The length of each LADN is determined by the length of DNN value field and the length of 5GS tracking area identity list field.

The UE shall store the complete list as received. If more than 8 LADNs are included in this information element, the UE shall store the first 8 LADNs and ignore the remaining octets of the information element.

DNN value (octet 5 to octet m):

DNN value field is coded as DNN value part of DNN information element as specified in subclause 9.11.2.1B starting with the third octet.

5GS tracking area identity list (octet m+1 to octet a):

5GS tracking area identity list field is coded as the length and the value part of the 5GS Tracking area identity list information element as specified in subclause 9.11.3.9 starting with the second octet.

9.11.3.31 MICO indication

The purpose of the MICO indication information element is to indicate the use of MICO mode or the re-negotiation of MICO mode.

The MICO indication information element is coded as shown in figure 9.11.3.31.1 and table 9.11.3.31.1.

The MICO indication is a type 1 information element.

8

7

6

5

4

3

2

1

MICO indication IEI

0

Spare

0

Spare

SPRTI

RAAI

octet 1

Figure 9.11.3.31.1: MICO indication

Table 9.11.3.31.1: MICO indication

Registration Area Allocation Indication (RAAI) (octet 1, bit 1)

In the network to UE direction:

Bit

1

0

all PLMN registration area not allocated

1

all PLMN registration area allocated

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

Strictly Periodic Registration Timer Indication (SPRTI) (octet 1, bit 2)

In the network to UE and the UE to network direction:

Bit

2

0

strictly periodic registration timer not supported

1

strictly periodic registration timer supported

Bits 3 and 4 are spare and shall be coded as zero.

NOTE: In the network to UE direction in the CONFIGURATION UPDATE COMMAND message, bits 1 and 2 shall be coded as zero.

9.11.3.31A MA PDU session information

The purpose of the MA PDU session information information element is to convey the MA-related information for the PDU session.

The MA PDU session information information element is coded as shown in figure 9.11.3.31A.1 and table 9.11.3.31A.1.

The MA PDU session information is a type 1 information element.

8

7

6

5

4

3

2

1

MA PDU session information IEI

MA PDU session information value

octet 1

Figure 9.11.3.31A.1: MA PDU session information information element

Table 9.11.3.31A.1: MA PDU session information information element

MA PDU session information value (octet 1, bit 1 to bit 4)

Bits

4

3

2

1

0

0

0

0

No additional information

0

0

0

1

MA PDU session network upgrade is allowed

All other values are spare.

9.11.3.31B Mapped NSSAI

The purpose of the Mapped NSSAI information element is to transfer S-NSSAI(s) applicable in the HPLMN to the visited PLMN.

The Mapped NSSAI information element is coded as shown in figure 9.11.3.31B.1, figure 9.11.3.31B.2 and table 9.11.3.31B.1.

The Mapped NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 42 octets.

NOTE 1: The total number of S-NSSAI values in a requested mapped NSSAI cannot exceed eight.

8

7

6

5

4

3

2

1

Mapped NSSAI IEI

octet 1

Length of Mapped NSSAI contents

octet 2

Mapped S-NSSAI content 1

octet 3

octet m

Mapped S-NSSAI content 2

octet m+1*

octet n*

octet n+1*

octet u*

Mapped S-NSSAI content n

octet u+1*

octet v*

Figure 9.11.3.31B.1: Mapped NSSAI information element

8

7

6

5

4

3

2

1

Length of Mapped S-NSSAI content

octet 3

Mapped HPLMN SST

octet 4

Mapped HPLMN SD

octet 5*

octet 7*

Figure 9.11.3.31B.2: Mapped S-NSSAI content

Table 9.11.3.31B.1: Mapped NSSAI information element

Value part of the Mapped NSSAI information element (octet 3 to v)

The value part of the Mapped NSSAI information element consists of one or more mapped S-NSSAI contents.

Mapped S-NSSAI content:

Length of S-NSSAI contents (octet 3)

Mapped HPLMN Slice/service type (SST) (octet 4)

This field contains the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SST value is mapped. The coding of the SST value part is defined in 3GPP TS 23.003 [4].

NOTE 1: Octet 4 (i.e. mapped HPLMN SST) shall always be included.

Mapped HPLMN Slice differentiator (SD) (octet 5 to octet 7)

This field contains a 24-bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SD value is mapped. The coding of the SD value part is defined in 3GPP TS 23.003 [4].

NOTE 2: If the octet 5 is included, then octet 6 and octet 7 shall be included.

9.11.3.31C Mobile station classmark 2

See subclause 10.5.1.6 in 3GPP TS 24.008 [12].

9.11.3.32 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.11.3.32.1 and table 9.11.3.32.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.11.3.32.1: NAS key set identifier information element

Table 9.11.3.32.1: NAS key set identifier information element

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

Bit

4

0

native security context (for KSIAMF)

1

mapped security context (for KSIASME)

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.11.3.33 NAS message container

The purpose of the NAS message container IE is to encapsulate a plain 5GS NAS REGISTRATION REQUEST or SERVICE REQUEST message, or to encapsulate non-cleartext IEs of a CONTROL PLANE SERVICE REQUEST message.

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

The NAS message container is a type 6 information element.

8

7

6

5

4

3

2

1

NAS message container IEI

octet 1

Length of NAS message container contents

octet 2

octet 3

octet 4

NAS message container contents

octet n

Figure 9.11.3.33.1: NAS message container information element

Table 9.11.3.33.1: NAS message container information element

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

This IE can contain a REGISTRATION REQUEST message as defined in subclause 5.5.1, or a SERVICE REQUEST message as defined in subclause 5.6.1, or non-cleartext IEs of a CONTROL PLANE SERVICE REQUEST message as defined in subclause 5.6.1.

9.11.3.34 NAS security algorithms

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

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

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

8

7

6

5

4

3

2

1

NAS security algorithms IEI

octet 1

Type of ciphering algorithm

Type of integrity protection algorithm

octet 2

Figure 9.11.3.34.1: NAS security algorithms information element

Table 9.11.3.34.1: NAS security algorithms information element

Type of integrity protection algorithm (octet 2, bit 1 to 3)

Bits

4

3

2

1

0

0

0

0

5G integrity algorithm 5G-IA0 (null integrity protection algorithm)

0

0

0

1

5G integrity algorithm 128-5G-IA1

0

0

1

0

5G integrity algorithm 128-5G-IA2

0

0

1

1

5G integrity algorithm 128-5G-IA3

0

1

0

0

5G integrity algorithm 5G-IA4

0

1

0

1

5G integrity algorithm 5G-IA5

0

1

1

0

5G integrity algorithm 5G-IA6

0

1

1

1

5G integrity algorithm 5G-IA7

All other values are reserved.

Type of ciphering algorithm (octet 2, bit 5 to 7)

Bits

8

7

6

5

0

0

0

0

5G encryption algorithm 5G-EA0 (null ciphering algorithm)

0

0

0

1

5G encryption algorithm 128-5G-EA1

0

0

1

0

5G encryption algorithm 128-5G-EA2

0

0

1

1

5G encryption algorithm 128-5G-EA3

0

1

0

0

5G encryption algorithm 5G-EA4

0

1

0

1

5G encryption algorithm 5G-EA5

0

1

1

0

5G encryption algorithm 5G-EA6

0

1

1

1

5G encryption algorithm 5G-EA7

All other values are reserved.

9.11.3.35 Network name

See subclause 10.5.3.5a in 3GPP TS 24.008 [12].

9.11.3.36 Network slicing indication

The purpose of the Network slicing indication information element is to indicate additional information associated with network slicing in the generic UE configuration update procedure and the registration procedure, other than the user’s configured NSSAI, allowed NSSAI, pending NSSAI and rejected NSSAI information.

The Network slicing indication information element is coded as shown in figure 9.11.3.36.1 and table 9.11.3.36.1.

The Network slicing indication is a type 1 information element.

8

7

6

5

4

3

2

1

Network slicing indication IEI

0

Spare

0

Spare

DCNI

NSSCI

octet 1

Figure 9.11.3.36.1: Network slicing indication

Table 9.11.3.36.1: Network slicing indication

Network slicing subscription change indication (NSSCI) (octet 1, bit 1)

Bit

1

0

Network slicing subscription not changed

1

Network slicing subscription changed

Default configured NSSAI indication (DCNI) (octet 1, bit 2)

Bit

2

0

Requested NSSAI not created from default configured NSSAI

1

Requested NSSAI created from default configured NSSAI

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

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

Bits 3 and 4 are spare and shall be coded as zero.

9.11.3.36A Non-3GPP NW provided policies

See subclause 10.5.5.37 in 3GPP TS 24.008 [12].

9.11.3.37 NSSAI

The purpose of the NSSAI information element is to identify a collection of S-NSSAIs

The NSSAI information element is coded as shown in figure 9.11.3.37.1 and table 9.11.3.37.1.

The NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 146 octets.

NOTE: More than one S-NSSAIs in an NSSAI can have the same SST values, and optionally same SD values, which are associated with different mapped HPLMN SST values and optionally mapped HPLMN SD values.

8

7

6

5

4

3

2

1

NSSAI IEI

octet 1

Length of NSSAI contents

octet 2

S-NSSAI value 1

octet 3

octet m

S-NSSAI value 2

octet m+1*

octet n*

octet n+1*

octet u*

S-NSSAI value n

octet u+1*

octet v*

Figure 9.11.3.37.1: NSSAI information element

Table 9.11.3.37.1: NSSAI information element

Value part of the NSSAI information element (octet 3 to v)

The value part of the NSSAI information element consists of one or more S-NSSAI values. Each S-NSSAI value consists of one S-NSSAI and optionally one mapped S-NSSAI.

The recipient of this information element shall store the complete list received (NOTE 1, NOTE 2, NOTE 3). If the NSSAI information element conveys an allowed NSSAI and more than 8 S-NSSAI values are included in this information element, the UE shall store the first 8 S-NSSAI values and ignore the remaining octets of the information element.

If the NSSAI information element conveys a configured NSSAI or pending NSSAI and more than 16 S-NSSAI values are included in this information element, the UE shall store the first 16 S-NSSAI values and ignore the remaining octets of the information element.

S-NSSAI value:

S-NSSAI value is coded as the length and value part of S-NSSAI information element as specified in subclause 9.11.2.8 starting with the second octet.

NOTE 1: The total number of S-NSSAI values in a requested NSSAI shall not exceed eight.

NOTE 2: The number of S-NSSAI values in an allowed NSSAI shall not exceed eight.

NOTE 3: The number of S-NSSAI values in a configured NSSAI or pending NSSAI shall not exceed sixteen.

9.11.3.37A NSSAI inclusion mode

The purpose of the NSSAI inclusion mode information element is to indicate the NSSAI inclusion mode in which the UE shall operate.

The NSSAI inclusion mode is a type 1 information element.

The NSSAI inclusion mode information element is coded as shown in figure 9.11.3.37A.1 and table 9.11.3.37A.1.

8

7

6

5

4

3

2

1

NSSAI inclusion mode

IEI

0

spare

0

spare

NSSAI inclusion mode

octet 1

Figure 9.11.3.37A.1: NSSAI inclusion mode information element

Table 9.11.3.37A.1: NSSAI inclusion mode information element

NSSAI inclusion mode (octet 1, bit 1 to bit 2)

Bits

2

1

0

0

NSSAI inclusion mode A

0

1

NSSAI inclusion mode B

1

0

NSSAI inclusion mode C

1

1

NSSAI inclusion mode D

9.11.3.38 Operator-defined access category definitions

The purpose of the Operator-defined access category definitions information element is to provide the UE with the operator-defined access category definitions or to delete the operator-defined access category definitions at the UE.

The Operator-defined access category definitions information element is coded as shown in figure 9.11.3.38.1, figure 9.11.3.38.2 and table 9.11.3.38.1.

The Operator-defined access category definitions is a type 6 information element with a minimum length of 3 octets, and maximum length of 8323 octets.

8

7

6

5

4

3

2

1

Operator-defined access category definitions IEI

octet 1

Length of operator-defined access category definitions contents

octet 2

octet 3

Operator-defined access category definition 1

octet 4*

octet a*

Operator-defined access category definition 2

octet a+1*

octet b*

octet b+1*

octet g*

Operator-defined access category definition n

octet g+1*

octet h*

Figure 9.11.3.38.1: Operator-defined access category definitions information element

8

7

6

5

4

3

2

1

Length of operator-defined access category definition contents

octet 4

Precedence value

octet 5

PSAC

0

Spare

0

Spare

Operator-defined access category number

octet 6

Length of criteria

octet 7

Criteria

octet 8

octet a-1

0

Spare

0

Spare

0

Spare

Standardized access category

octet a*

Figure 9.11.3.38.2: Operator-defined access category definition

Table 9.11.3.38.1: Operator-defined access category definitions information element

Value part of the Operator-defined access category definitions information element (octet 4 to h)

The value part of the Operator-defined access category definitions information element consists of zero or no more than 32 operator-defined access category definition fields. Each operator-defined access category definition field is coded as described in figure 9.11.3.38.2. The length of each operator-defined access category definition field is determined by the length of operator-defined access category definition contents field.

Operator-defined access category definition (octet 4 to octet a):

Length of operator-defined access category definition contents (octet 4)

Length of operator-defined access category definition contents indicates binary coded length of the operator-defined access category definition value field (octet 5 to octet a).

Precedence value (octet 5)

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

0

Precedence value 0

to

1

1

1

1

1

1

1

1

Precedence value 255

Operator-defined access category number (bits 5 to 1 of octet 6)

Bits

5

4

3

2

1

0

0

0

0

0

Access category number 32

to

1

1

1

1

1

Access category number 63

Presence of standardized access category (PSAC) (bit 8 of octet 6)

PSAC field indicates whether the standardized access category field is present or absent.

Bit

8

0

Standardized access category field is not included

1

Standardized access category field is included

Length of criteria (octet 7)

Length of criteria field indicates binary coded length of the criteria field.

Criteria (octets 8 to octet a-1)

The criteria field contains one or more criteria components fields. Each criteria component field shall be encoded as a sequence of a one octet criteria type field and zero or more octets criteria value field. The criteria type field shall be transmitted first.

Criteria type

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

0

DNN type

0

0

0

0

0

0

0

1

OS id + OS App Id type

0

0

0

0

0

0

1

0

S-NSSAI type

All other values are reserved.

For "DNN type", the criteria value field shall be encoded as a sequence of one octet DNN length-value pair count field and one or more DNN length-value pair fields. The DNN length-value pair count field indicates the number of included DNN length-value pair fields. Each DNN length-value pair field is coded as a sequence of one octet DNN value length field and a DNN value field. The DNN value length field indicates the length in octets of the DNN value field. The DNN value field contains an APN as specified in 3GPP TS 23.003 [4].

For "OS Id + OS App Id type", the criteria value field shall be encoded as a sequence of one octet app id value count field and one or more app id value fields. The app id value count field indicates the number of included app id value fields. Each app id value field is coded as a sequence of a sixteen octet OS id value field, one octet OS app id value length field and an OS app id value field. The OS app id value length field indicates the length in octets of the OS app id value field. The OS id value field contains a Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 [35A]. The OS app id value field contains an OS specific application identifier. Coding of the OS app id value field is outside the scope of the present document.

For "S-NSSAI type", the criteria value field shall be encoded as a sequence of one octet S-NSSAI length-value pair count field and one or more S-NSSAI length-value value fields. The S-NSSAI length-value pair count field indicates the number of included S-NSSAI length-value pair fields. Each S-NSSAI length-value pair field is coded as a sequence of one octet S-NSSAI value length field and an S-NSSAI value field. The S-NSSAI value length field indicates the length in octets of the S-NSSAI value field. The S-NSSAI value field contains one octet SST field optionally followed by three octets SD field. The SST field contains a SST. The SD field contains an SD. SST and SD are specified in 3GPP TS 23.003 [4].

Standardized access category (bits 5 to 1 of octet a)

Standardized access category field indicates the access category number of the standardized access category that is used in combination with the access identities to determine the establishment cause.

Bits

5

4

3

2

1

0

0

0

0

0

Access category number 0

to

0

0

1

1

1

Access category number 7

All other values are reserved.

9.11.3.39 Payload container

The purpose of the Payload container information element is to transport one or multiple payloads. If multiple payloads are transported, the associated information of each payload are also transported together with the payload.

The Payload container information element is coded as shown in figure 9.11.3.39.1, figure 9.11.3.39.2, figure 9.11.3.39.3, figure 9.11.3.39.4 and table 9.11.3.39.1.

The Payload container is a type 6 information element with a minimum length of 4 octets and a maximum length of 65538 octets.

8

7

6

5

4

3

2

1

Payload container IEI

octet 1

Length of payload container contents

octet 2

octet 3

octet 4

Payload container contents

octet n

Figure 9.11.3.39.1: Payload container information element

8

7

6

5

4

3

2

1

Number of entries

octet 4

Payload container entry 1

octet 5

octet x2

Payload container entry 2

octet x2+1

octet x3

……

Payload container entry i

octet xi +1

octet n

Figure 9.11.3.39.2: Payload container contents with Payload container type "Multiple payloads"

8

7

6

5

4

3

2

1

Length of Payload container entry

octet xi +1

octet xi +2

Number of optional IEs

Payload container type

octet xi +3

Optional IE 1

octet xi +4

octet y2

Optional IE 2

octet y2+1

octet y3

Optional IE j

octet yj+1

octet z

Payload container entry contents

octet z+1

octet n

Figure 9.11.3.39.3: Payload container entry

8

7

6

5

4

3

2

1

Type of optional IE

octet xi +4

Length of optional IE

octet xi +5

Value of optional IE

octet xi +6

octet y2

Figure 9.11.3.39.4: Optional IE

Table 9.11.3.39.1: Payload container information element

Payload container contents (octet 4 to octet n); max value of 65535 octets

If the payload container type is set to "N1 SM information" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents contain a 5GSM message as defined in subclause 8.3.

If the payload container type is set to "SOR transparent container" and is included in the DL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the SOR transparent container IE (see subclause 9.11.3.51) for SOR data type is set to value "0" except that the first three octets are not included.

If the payload container type is set to "SOR transparent container" and is included in the UL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the SOR transparent container IE (see subclause 9.11.3.51) for SOR data type is set to value "1" except that the first three octets are not included.

If the payload container type is set to "UE policy container" and is included in the DL NAS TRANSPORT, UL NAS TRANSPORT or REGISTRATION REQUEST message, the payload container contents are coded as defined in subclause Annex D.

If the payload container type is set to "UE parameters update transparent container" and is included in the DL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the UE parameters update transparent container IE (see subclause 9.11.3.53A) for UE parameters update data type is set to value "0" except that the first three octets are not included.

If the payload container type is set to "UE parameters update transparent container" and is included in the UL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of the UE parameters update transparent container IE (see subclause 9.11.3.53A) for UE parameters update data type is set to value "1" except that the first three octets are not included.

If the payload container type is set to "SMS" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 in 3GPP TS 24.011 [13].

If the payload container type is set to "CIoT user data container" and is included in the UL NAS TRANSPORT, DL NAS TRANSPORT or CONTROL PLANE SERVICE REQUEST message, the payload container contents are coded the same way as the contents of the user data container IE (see subclause 9.9.4.24 in 3GPP TS 24.301 [15]) except that the first three octets are not included.

If the payload container type is set to "SMS" and is included in the CONTROL PLANE SERVICE REQUEST message, the payload container contents are coded the same way as the contents of the NAS message container IE (see subclause 9.9.3.22 in 3GPP TS 24.301 [15]) except that the first two octets are not included.

If the payload container type is set to "Location services message container" and is included in the UL NAS TRANSPORT, DL NAS TRANSPORT or CONTROL PLANE SERVICE REQUEST message, the payload container contents include location services message payload.

If the payload container type is set to "LTE Positioning Protocol (LPP) message container" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents include LPP message payload.

If the payload container type is set to "Service-level-AA container" and is included in the UL NAS TRANSPORT or DL NAS TRANSPORT message, the payload container contents are coded the same way as the contents of Service-level-AA container (see subclause 9.11.2.10).

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

If the payload container type is set to "Multiple payloads", the number of entries field represents the total number of payload container entries, and the payload container entry contents field is coded as a list of payload container entry according to figure 9.11.3.39.2, with each payload container entry is coded according to figure 9.11.3.39.3 and figure 9.11.3.39.4.

Payload container entry

For each payload container entry, the payload container type field represents the payload container type value as described in subclause 9.11.3.40, the coding of payload container contents field is dependent on the particular application, and the number of optional IEs field represents the total number of optional IEs associated with the payload container entry contents field in the payload container entry. The error handlings for optional IEs specified in subclauses 7.6.1, 7.6.3 and 7.7.1 shall apply to the optional IEs included in the payload container entry.

Optional IEs

Type of optional IE (octet xi +4)

This field contains the IEI of the optional IE.

Length of optional IE (octet xi+5)

This field indicates binary coded length of the value of the optional IE entry.

Value of optional IE (octet xi+6 to octet y2)

This field contains the value of the optional IE entry with the value part of the referred information element based on following optional IE reference. If the Request type is included, the value part of the Request type shall be encoded in the bits 1 to 4 and bits 5 to 8 shall be coded as zero.

IEI

Optional IE name

Optional IE reference

12

PDU session ID

PDU session identity 2 (see subclause 9.11.3.41)

24

Additional information

Additional information (see subclause 9.11.2.1)

58

5GMM cause

5GMM cause (see subclause 9.11.3.2)

37

Back-off timer value

GPRS timer 3 (see subclause 9.11.2.5)

59

Old PDU session ID

PDU session identity 2 (see subclause 9.11.3.41)

80

Request type

Request type (see subclause 9.11.3.47)

22

S-NSSAI

S-NSSAI (see subclause 9.11.2.8)

25

DNN

DNN (see subclause 9.11.2.1B)

F0

Release assistance indication

Release assistance indication (see subclause 9.11.3.46A)

A0

MA PDU session information

MA PDU session information (see subclause 9.11.3.31A)

9.11.3.40 Payload container type

The purpose of the Payload container type information element indicates type of payload included in the payload container information element.

The Payload container type information element is coded as shown in figure 9.11.3.40.1 and table 9.11.3.40.1.

The Payload container type is a type 1 information element.

8

7

6

5

4

3

2

1

Payload container type

IEI

Payload container type value

octet 1

Figure 9.11.3.40.1: Payload container type information element

Table 9.11.3.40.1: Payload container type information element

Payload container type value (octet 1)

Bits

4

3

2

1

0

0

0

1

N1 SM information

0

0

1

0

SMS

0

0

1

1

LTE Positioning Protocol (LPP) message container

0

1

0

0

SOR transparent container

0

1

0

1

UE policy container

0

1

1

0

UE parameters update transparent container

0

1

1

1

Location services message container (see 3GPP TS 23.273 [6B])

1

0

0

0

CIoT user data container

1

0

0

1

Service-level-AA container

1

1

1

1

Multiple payloads

All other values are reserved.

NOTE: The value "Multiple payloads" is only used when the Payload container contents in figure 9.11.3.39.1 contains multiple payloads as shown in figure 9.11.3.39.2.

9.11.3.41 PDU session identity 2

The purpose of the PDU session identity 2 information element is to indicate the identity of a PDU session in a 5GMM message.

The PDU session identity 2 information element is coded as shown in figure 9.11.3.41.1 and table 9.11.3.41.1.

The PDU session identity 2 is a type 3 information element with a length of 2 octets .

8

7

6

5

4

3

2

1

PDU session identity 2 IEI

octet 1

PDU session identity 2 value

octet 2

Figure 9.11.3.41.1: PDU session identity 2 information element

Table 9.11.3.41.1: PDU session identity 2 information element

PDU session identity 2 value (octet 2)

The coding of the DU session identity 2 value is identical to the coding of the PDU session identity value as defined in 3GPP TS 24.007 [11] .

9.11.3.42 PDU session reactivation result

The purpose of the PDU session reactivation result information element is to indicate the result of establishments of user-plane resources of PDU sessions.

The PDU session reactivation result information element is coded as shown in figure 9.11.3.42.1 and table 9.11.3.42.1.

The PDU session reactivation result is a type 4 information element with minimum length of 4 octets and maximum length of 34 octets.

8

7

6

5

4

3

2

1

PDU session reactivation result IEI

octet 1

Length of PDU session reactivation result

octet 2

PSI

(7)

PSI

(6)

PSI

(5)

PSI

(4)

PSI

(3)

PSI

(2)

PSI

(1)

PSI

(0)

octet 3

PSI

(15)

PSI

(14)

PSI

(13)

PSI

(12)

PSI

(11)

PSI

(10)

PSI

(9)

PSI

(8)

octet 4

0

0

0

0

0

0

0

0

Spare

octet 5* -34*

Figure 9.11.3.42.1: PDU session reactivation result information element

Table 9.11.3.42.1: PDU session reactivation result information element

PSI(x) shall be coded as follows:

PSI(0):

Bit 0 of octet 3 is spare and shall be coded as zero.

PSI(1) – PSI(15):

0 indicates establishment of user-plane resources of the PDU session was not requested in the Uplink data status IE or establishment of user-plane resources of the PDU session was not allowed in the Allowed PDU session status IE or establishment of user-plane resource of the PDU session is successful.

1 indicates either establishment of user-plane resources of the PDU session was requested in the Uplink data status IE but establishment of user-plane resource of the PDU session is not successful or indicates establishment of user-plane resources of the PDU session was allowed in the Allowed PDU session status IE but establishment of user-plane resource of the PDU session is either not performed or not successful.

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

9.11.3.43 PDU session reactivation result error cause

The purpose of the PDU session reactivation result error cause information element is to indicate error causes for PDU session ID(s) where there was a failure to establish the user-plane resources.

The PDU session reactivation result error cause information element is coded as shown in figure 9.11.3.43.1 and table 9.11.3.43.1.

The PDU session reactivation result error cause is a type 6 information element with a minimum length of 5 octets and a maximum length of 515 octets.

8

7

6

5

4

3

2

1

PDU session reactivation result error cause IEI

octet 1

Length of PDU session reactivation result error cause

octet 2

octet 3

PDU session ID

octet 4

cause value

octet 5

….

PDU session ID

octet 514*

cause value

octet 515*

Figure 9.11.3.43.1: PDU session reactivation result error cause information element

Table 9.11.3.43.1: PDU session reactivation result error cause information element

PDU session ID is coded same as PDU session ID IE (see subclause 9.4).

The cause value is coded same as second octet of 5GMM cause information element (see subclause 9.11.3.2).

9.11.3.44 PDU session status

The purpose of the PDU session status information element is to indicate the state of each PDU session that can be identified by a PDU session identity.

The PDU session status information element is coded as shown in figure 9.11.3.44.1 and table 9.11.3.44.1.

The PDU session status information element is a type 4 information element with minimum length of 4 octets and a maximum length of 34 octets.

8

7

6

5

4

3

2

1

PDU session status IEI

octet 1

Length of PDU session status contents

octet 2

PSI

(7)

PSI

(6)

PSI

(5)

PSI

(4)

PSI

(3)

PSI

(2)

PSI

(1)

PSI

(0)

octet 3

PSI

(15)

PSI

(14)

PSI

(13)

PSI

(12)

PSI

(11)

PSI

(10)

PSI

(9)

PSI

(8)

octet 4

0

0

0

0

0

0

0

0

octet 5*-

spare

34*

Figure 9.11.3.44.1: PDU session status information element

Table 9.11.3.44.1: PDU session status information element

PSI(x) shall be coded as follows:

PSI(0):

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

PSI(1) – PSI(15):

0 indicates that the 5GSM state of the corresponding PDU session is PDU SESSION INACTIVE.

1 indicates that the 5GSM state of the corresponding PDU session is not PDU SESSION INACTIVE

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

9.11.3.45 PLMN list

See subclause 10.5.1.13 in 3GPP TS 24.008 [12].

9.11.3.46 Rejected NSSAI

The purpose of the Rejected NSSAI information element is to identify a collection of rejected S-NSSAIs.

The Rejected NSSAI information element is coded as shown in figure 9.11.3.46.1, figure 9.11.3.46.2 and table 9.11.3.46.1.

The Rejected NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 42 octets.

8

7

6

5

4

3

2

1

Rejected NSSAI IEI

octet 1

Length of Rejected NSSAI contents

octet 2

Rejected S-NSSAI 1

octet 3

octet m

Rejected S-NSSAI 2

octet m+1*

octet n*

octet n+1*

octet u*

Rejected S-NSSAI n

octet u+1*

octet v*

Figure 9.11.3.46.1: Rejected NSSAI information element

8

7

6

5

4

3

2

1

Length of rejected S-NSSAI

Cause value

octet 3

SST

octet 4

SD

octet 5*

octet 7*

Figure 9.11.3.46.2: Rejected S-NSSAI

Table 9.11.3.46.1: Rejected NSSAI information element

Value part of the Rejected NSSAI information element (octet 3 to v)

The value part of the Rejected NSSAI information element consists of one or more rejected S-NSSAIs. Each rejected S-NSSAI consists of one S-NSSAI and an associated cause value. The length of each rejected S-NSSAI can be determined by the ‘length of rejected S-NSSAI’ field in the first octet of the rejected S-NSSAI.

The UE shall store the complete list received (NOTE 0). If more than 8 rejected S-NSSAIs are included in this information element, the UE shall store the first 8 rejected S-NSSAIs and ignore the remaining octets of the information element.

Rejected S-NSSAI:

Cause value (octet 3)

Bits

4

3

2

1

0

0

0

0

S-NSSAI not available in the current PLMN or SNPN

0

0

0

1

S-NSSAI not available in the current registration area

0

0

1

0

S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization

All other values are reserved.

Slice/service type (SST) (octet 4)

This field contains the 8 bit SST value. The coding of the SST value part is defined in 3GPP TS 23.003 [4]. (NOTE 2)

Slice differentiator (SD) (octet 5 to octet 7)

This field contains the 24 bit SD value. The coding of the SD value part is defined in 3GPP TS 23.003 [4]. (NOTE 3)

NOTE 0: The number of rejected S-NSSAI(s) shall not exceed eight.

NOTE 1: If octet 5 is included, then octet 6 and octet 7 shall be included.

NOTE 2: If the Cause value is "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", this field shall contain the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN.

NOTE 3: If the Cause value is "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", this field shall contain the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN.

9.11.3.46A Release assistance indication

See subclause 9.9.4.25 in 3GPP TS 24.301 [15].

9.11.3.47 Request type

The purpose of the Request type information element is to indicate the type of the 5GSM message.

The Request type information element is coded as shown in figure 9.11.3.47.1 and table 9.11.3.47.1.

The Request type is a type 1 information element.

8

7

6

5

4

3

2

1

Request type IEI

0

spare

Request type value

octet 1

Figure 9.11.3.47.1: Request type information element

Table 9.11.3.47.1: Request type information element

Request type value (octet 1, bit 1 to bit 4)

Bits

3

2

1

0

0

1

initial request

0

1

0

existing PDU session

0

1

1

initial emergency request

1

0

0

existing emergency PDU session

1

0

1

modification request

1

1

0

MA PDU request (NOTE)

1

1

1

reserved

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

NOTE: This value shall be interpreted as "initial request", if received by a network not supporting MA PDU sessions.

9.11.3.48 S1 UE network capability

See subclause 9.9.3.34 in 3GPP TS 24.301 [15].

9.11.3.48A S1 UE security capability

See subclause 9.9.3.36 in 3GPP TS 24.301 [15].

9.11.3.49 Service area list

The purpose of the Service area list information element is to transfer a list of allowed tracking areas for an allowed area or a list of non-allowed tracking areas for a non-allowed area 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 lists of type "11" indicate all TAIs of the PLMNs in the registration area are allowed area.

The Service area list information element is coded as shown in figure 9.11.3.49.1, figure 9.11.3.49.2, figure 9.11.3.49.3, figure 9.11.3.49.4, figure 9.11.3.49.5 and table 9.11.3.49.1.

The Service area list is a type 4 information element with a minimum length of 6 octets and a maximum length of 114 octets. The list can contain a maximum of 16 different tracking area identities.

8

7

6

5

4

3

2

1

Service area list IEI

octet 1

Length of service area list contents

octet 2

Partial service area list 1

octet 3

octet i

Partial service area list 2

octet i+1*

octet l*

octet l+1*

octet m*

Partial service area list p

octet m+1*

octet n*

Figure 9.11.3.49.1: Service area list information element

8

7

6

5

4

3

2

1

Allowed type

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 1 (continued)

octet 7

TAC k

octet 3k+2*

TAC k (continued)

octet 3k+3*

TAC k (continued)

octet 3k+4*

Figure 9.11.3.49.2: Partial service area list – type of list = "00"

8

7

6

5

4

3

2

1

Allowed type

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 1 (continued)

octet 7

Figure 9.11.3.49.3: Partial service area list – type of list = "01"

8

7

6

5

4

3

2

1

Allowed type

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 1 (continued)

octet 7

MCC digit 2

MCC digit 1

octet 8*

MNC digit 3

MCC digit 3

octet 9*

MNC digit 2

MNC digit 1

octet 10*

TAC 2

octet 11*

TAC 2 (continued)

octet 12*

TAC 2 (continued)

octet 13*

MCC digit 2

MCC digit 1

octet 6k-4*

MNC digit 3

MCC digit 3

octet 6k-3*

MNC digit 2

MNC digit 1

octet 6k-2*

TAC k

octet 6k*-1

TAC k (continued)

octet 6k*

TAC k (continued)

octet 6k+1*

Figure 9.11.3.49.4: Partial service area list – type of list = "10"

8

7

6

5

4

3

2

1

Allowed type

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

Figure 9.11.3.49.5: Partial service area list – type of list = "11"

Table 9.11.3.49.1: Service area list information element

Value part of the Service area list information element (octets 3 to n)

The value part of the Service area list information element consists of one or several partial service area lists. The length of each partial service area list can be determined from the ‘type of list’ field and the ‘number of elements’ field in the first octet of the partial service area list.

The "Allowed type" fields in all the partial service area lists shall have the same value. For allowed type "0", TAIs contained in all partial service area lists are in the allowed area. For allowed type "1", TAIs contained in all partial service area lists are in the non-allowed area.

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 service area list:

Allowed type (octet 1)

Bit

8

0

TAIs in the list are in the allowed area

1

TAIs in the list are in the non-allowed area

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)

1

1

All TAIs belonging to the PLMNs in the registration area are in the allowed area

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

to

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.

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

octets 2 to 4 contain the MCC+MNC, and

for j = 1, …, k:

octets 3j+2 to 3j+4 contain the TAC of the j-th TAI belonging to the partial list,

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

octets 2 to 4 contain the MCC+MNC, and

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

octets 6j-4 to 6j-2 contain the MCC+MNC, and

octets 6j-1 to 6j+1 contain the TAC of the j-th TAI belonging to the partial list.

For type of list = "11":

Allowed type shall be coded as "0" and number of elements shall be ignored, and octets 2 to 4 containing the MCC+MNC can be ignored.

If allowed type is coded as "1", it shall be interpreted as "0".

MCC, Mobile country code

The MCC field is coded as in ITU-T Recommendation E.212 [42], 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 the third 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 3 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. This type is not applicable in an SNPN.

9.11.3.50 Service type

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

The service type is a type 1 information element.

The service type information element is coded as shown in figure 9.11.3.50.1 and table 9.11.3.50.1.

8

7

6

5

4

3

2

1

Service type

IEI

Service type value

octet 1

Figure 9.11.3.50.1: Service type information element

Table 9.11.3.50.1: Service type information element

Service type value (octet 1)

Service type value

Bits

4

3

2

1

0

0

0

0

signalling

0

0

0

1

data

0

0

1

0

mobile terminated services

0

0

1

1

emergency services

0

1

0

0

emergency services fallback

0

1

0

1

high priority access

0

1

1

0

elevated signalling

0

1

1

1

unused; shall be interpreted as "signalling", if received by the network

1

0

0

0

unused; shall be interpreted as "signalling", if received by the network

1

0

0

1

unused; shall be interpreted as "data", if received by the network

1

0

1

0

unused; shall be interpreted as "data", if received by the network

1

0

1

1

unused; shall be interpreted as "data", if received by the network

All other values are reserved.

9.11.3.50A SMS indication

The purpose of the SMS indication information element is to indicate that the ability for the UE to use SMS over NAS has changed.

The SMS indication information element is coded as shown in figure 9.11.3.50A.1 and table 9.11.3.50A.1.

The SMS indication is a type 1 information element.

8

7

6

5

4

3

2

1

SMS indication IEI

0

Spare

0

Spare

0

Spare

SAI

octet 1

Figure 9.11.3.50A.1: SMS indication

Table 9.11.3.50A.1: SMS indication

SMS availability indication (SAI) (octet 1)

Bit

1

0

SMS over NAS not available

1

SMS over NAS available

Bits 2, 3 and 4 are spare and shall be coded as zero,

9.11.3.51 SOR transparent container

The purpose of the SOR transparent container information element in the REGISTRATION ACCEPT message is to provide the list of preferred PLMN/access technology combinations (or HPLMN indication that ‘no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided’), or a secured packet (see 3GPP TS 23.122 [5] annex C) and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI (or subscribed SNPN or HPLMN indication that ‘no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided’). The purpose of the SOR transparent container information element in the REGISTRATION COMPLETE message is to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the REGISTRATION ACCEPT message as well as to indicate the ME support of SOR-CMCI.

NOTE: When used in NAS transport procedure, the contents of the SOR transparent container information element in the Payload container IE of the DL NAS TRANSPORT message are used to provide the list of preferred PLMN/access technology combinations and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI. The contents of the SOR transparent container information element in the Payload container IE of the UL NAS TRANSPORT message are used to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the DL NAS TRANSPORT message as well as to indicate the ME support of SOR-CMCI.

The SOR transparent container information element is coded as shown in figure 9.11.3.51.1, figure 9.11.3.51.2, figure 9.11.3.51.3, figure 9.11.3.51.4, figure 9.11.3.51.5, figure 9.11.3.51.6, figure 9.11.3.51.7, figure 9.11.3.51.8, figure 9.11.3.51.9, figure 9.11.3.51.10, figure 9.11.3.51.11, figure 9.11.3.51.12, figure 9.11.3.51.13, table 9.11.3.51.1, table 9.11.3.51.2, table 9.11.3.51.3, table 9.11.3.51.4, table 9.11.3.51.5 and table 9.11.3.51.6.

The SOR transparent container is a type 6 information element with a minimum length of 20 octets.

8

7

6

5

4

3

2

1

SOR transparent container IEI

octet 1

Length of SOR transparent container contents

octet 2

octet 3

SOR header

octet 4

SOR-MAC-IAUSF

octet 5-20

CounterSOR

octet 21-22

Secured packet

octet 23* – n*

Figure 9.11.3.51.1: SOR transparent container information element for list type with value "0" and SOR data type with value "0"

8

7

6

5

4

3

2

1

SOR transparent container IEI

octet 1

Length of SOR transparent container contents

octet 2

octet 3

SOR header

octet 4

SOR-MAC-IAUSF

octet 5-20

CounterSOR

octet 21-22

PLMN ID and access technology list

octet 23*-m*

Figure 9.11.3.51.2: SOR transparent container information element for list type with value "1", SOR data type with value "0", and additional parameters with value "0"

8

7

6

5

4

3

2

1

SOR transparent container IEI

octet 1

Length of SOR transparent container contents

octet 2

octet 3

SOR header

octet 4

SOR-MAC-IAUSF

octet 5

octet 20

CounterSOR

octet 21

octet 22

Length of PLMN ID and access technology list

octet 23*

PLMN ID and access technology list

octet 24*

octet m*

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

SSSI

SSCMI

SI

octet o

SOR-CMCI

octet (o+1)*

octet p*

SOR-SNPN-SI

octet (p+1)*

octet u*

Figure 9.11.3.51.2A: SOR transparent container information element for list type with value "1", SOR data type with value "0", additional parameters with value "1"

PLMN ID 1

octet 23*- 25*

access technology identifier 1

octet 26*- 27*

PLMN ID n

octet (18+5*n)*-(20+5*n)*

access technology identifier n

octet (21+5*n)*-(22+5*n)*

Figure 9.11.3.51.3: PLMN ID and access technology list (m=22+5*n)

8

7

6

5

4

3

2

1

SOR transparent container IEI

octet 1

Length of SOR transparent container contents

octet 2

octet 3

SOR header

octet 4

SOR-MAC-IUE

octet 5 – 20

Figure 9.11.3.51.4: SOR transparent container information element for SOR data type with value "1"

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

AP

ACK

List type

List indication

SOR data type

octet 4

Figure 9.11.3.51.5: SOR header for SOR data type with value "0"

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

MSSI

SOR data type

octet 4

Figure 9.11.3.51.6: SOR header for SOR data type with value "1"

Table 9.11.3.51.1: SOR transparent container information element

SOR-MAC-IAUSF (see NOTE 1), SOR-MAC-IUE (see NOTE 2) and CounterSOR (see NOTE 1) are coded as specified in 3GPP TS 33.501 [24].

SOR data type (octet 4, bit 1)

0

The SOR transparent container carries steering of roaming information.

1

The SOR transparent container carries acknowledgement of successful reception of the steering of roaming information.

List indication (octet 4, bit 2) (see NOTE 1)

0

HPLMN indication that ‘no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided’

1

list of preferred PLMN/access technology combinations is provided

List type (octet 4, bit 3) (see NOTE 1)

0

The list type is a secured packet.

1

The list type is a "PLMN ID and access technology list".

Acknowledgement (ACK) value (octet 4, bit 4) (see NOTE 1)

0

acknowledgement not requested

1

acknowledgement requested

Additional parameters (AP) value (octet 4, bit 5)

Bit

5

0

Additional parameters not included

1

Additional parameters included (see NOTE 3)

If the SOR data type is set to value "0", the list type bit is set to value "1", and the additional parameters bit is set to value "1" then:
– the octet o is present.

– if the list indication bit is set to "0" then the PLMN ID and access technology list field and the length of PLMN ID and access technology list field are absent.

– if the list indication bit is set to "1" then the PLMN ID and access technology list field and the length of PLMN ID and access technology list field are present.

The secure packet is coded as specified in 3GPP TS 31.115 [22B]. (see NOTE 1)

The PLMN ID and access technology list consists of PLMN ID and access technology identifier and are coded as specified in 3GPP TS 31.102 [22] subclause 4.2.5. The PLMN ID and access technology identifier are provided in decreasing order of priority, i.e. PLMN ID 1 indicates highest priority and PLMN ID n indicates lowest priority. The PLMN ID and access technology list contains at minimum zero and at maximum 16 (decimal) PLMN IDs and access technology identifiers. (see NOTE 1)

ME support of SOR-CMCI indicator (MSSI) value (octet 4, bit 2) (see NOTE 2, NOTE 4)

0

SOR-CMCI not supported by the ME

1

SOR-CMCI supported by the ME

SOR-CMCI indicator (SI) value (octet o, bit 1)

Bit

1

0

SOR-CMCI absent

1

SOR-CMCI present

If the SOR-CMCI indicator bit is set to "SOR-CMCI present", the SOR-CMCI field is present. If the SI bit is set to "SOR-CMCI absent", the SOR-CMCI field is absent.

Store SOR-CMCI in ME indicator (SSCMI) value (octet o, bit 2)

Bit

2

0

Do not store SOR-CMCI in ME

1

Store SOR-CMCI in ME

SOR-CMCI (octet o+1 to octet p)

The SOR-CMCI field is coded according to figure 9.11.3.51.7 and table 9.11.3.51.2.

SOR-SNPN-SI indicator (SSSI) value (octet o, bit 3)

Bit

3

0

subscribed SNPN or HPLMN indication that ‘no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided’

1

SOR-SNPN-SI present

If the SSSI bit is set to "SOR-SNPN-SI present", the SOR-SNPN-SI field is present. If the SSSI bit is set to "subscribed SNPN or HPLMN indication that ‘no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided’", the SOR-SNPN-SI is absent.

NOTE 1: This bit or field applies for SOR header with SOR data type with value "0".

NOTE 2: This bit or field applies for SOR header with SOR data type with value "1".

NOTE 3: Additional parameters can be set to value "1" only when the ME supports SOR-CMCI or SOR-SNPN-SI, and the list type bit is set to value "1".

NOTE 4: The "SOR-CMCI supported by the ME" is not set by a UE compliant to an earlier release of the specification.

8

7

6

5

4

3

2

1

Length of SOR-CMCI contents

octet (o+1)

octet (o+2)

SOR-CMCI rule 1

octet (o+3)*

octet q*

SOR-CMCI rule 2

octet (q+1)*

octet r*

octet (r+1)*

octet s*

SOR-CMCI rule n

octet (s+1)*

octet p*

Figure 9.11.3.51.7: SOR-CMCI

Table 9.11.3.51.2: SOR-CMCI

SOR-CMCI rule:

The SOR-CMCI rule is coded according to figure 9.11.3.51.8 and table 9.11.3.51.3.

If the length of SOR-CMCI contents field indicates a length bigger than indicated in figure 9.11.3.51.7, receiving entity shall ignore any superfluous octets located at the end of the SOR-CMCI.

8

7

6

5

4

3

2

1

Length of SOR-CMCI rule contents

octet q+1

octet q+2

Tsor-cm timer value

octet q+3

Criterion type

octet q+4

Criterion value

octet (q+5)*

octet r*

Figure 9.11.3.51.8: SOR-CMCI rule

Table 9.11.3.51.3: SOR-CMCI rule

Tsor-cm timer value

The Tsor-cm timer value field is coded according to octet 2 of the GPRS timer information element as specified in 3GPP TS 24.008 [12] subclause 10.5.7.3 and indicates the Tsor-cm timer value. When the unit field of the Tsor-cm timer value field indicates that the timer is deactivated, the receiving entity shall consider that Tsor-cm timer value is set to the infinity value.

Criterion type

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 1 DNN

0 0 0 0 0 0 1 0 S-NSSAI SST

0 0 0 0 0 0 1 1 S-NSSAI SST and SD

0 0 0 0 0 1 0 0 IMS registration related signalling

0 0 0 0 0 1 0 1 MMTEL voice call

0 0 0 0 0 1 1 0 MMTEL video call

0 0 0 0 0 1 1 1 MO SMS over NAS or MO SMSoIP

0 0 0 0 1 0 0 0 SOR security check not successful

1 1 1 1 1 1 1 1 match all

All other values are spare.

The receiving entity shall ignore SOR-CMCI rule with criterion of criterion type set to a spare value.

For "DNN", the criterion value field shall be encoded as a DNN length-value pair field.

For "S-NSSAI SST", the criterion value field shall be encoded as one octet SST field.

For "S-NSSAI SST and SD", the criterion value field shall be encoded as a sequence of one octet SST field and three octets SD field. The SST field shall be transmitted first.

The DNN length-value pair field shall be encoded as a sequence of one octet DNN value length field and a DNN value field. The DNN value length field shall be transmitted first. The DNN value length field indicates the length in octets of the DNN value field. The DNN value field contains an APN as specified in 3GPP TS 23.003 [4].

The SST field contains SST of HPLMN’s S-NSSAI.

The SD field contains SD of HPLMN’s S-NSSAI.

For "match all", "SOR security check not successful", "IMS registration related signalling", "MMTEL voice call", "MMTEL video call", and "MO SMS over NAS or MO SMSoIP", the criterion value field is zero octets long.

If the length of SOR-CMCI rule contents field indicates a length bigger than indicated in figure 9.11.3.51.8, receiving entity shall ignore any superfluous octets located at the end of the SOR-CMCI rule.

The UE applies SOR-CMCI rules as described in 3GPP TS 23.122 [5] annex C.

8

7

6

5

4

3

2

1

Length of SOR-SNPN-SI contents

octet (p+1)

octet (p+2)

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

CLGI

CLSI

octet (p+3)

CH controlled prioritized list of preferred SNPNs

octet (p+4)*

octet t*

CH controlled prioritized list of GINs

octet (t+1)*

octet u*

Figure 9.11.3.51.9: SOR-SNPN-SI

Table 9.11.3.51.4: SOR-SNPN-SI

CH controlled prioritized list of preferred SNPNs indicator (CLSI) value (octet p+3, bit 1)

Bit

1

0

CH controlled prioritized list of preferred SNPNs absent

1

CH controlled prioritized list of preferred SNPNs present

If the CLSI bit is set to "CH controlled prioritized list of preferred SNPNs present", the CH controlled prioritized list of preferred SNPNs field is present. If the CLSI bit is set to "CH controlled prioritized list of preferred SNPNs absent", the CH controlled prioritized list of preferred SNPNs field is absent.

CH controlled prioritized list of GINs indicator (CLGI) value (octet p+3, bit 2)

Bit

2

0

CH controlled prioritized list of GINs absent

1

CH controlled prioritized list of GINs present

If the CLGI bit is set to "CH controlled prioritized list of GINs present", the CH controlled prioritized list of GINs field is present. If the CLGI bit is set to "CH controlled prioritized list of GINs absent", the CH controlled prioritized list of GINs field is absent.

If the length of SOR-SNPN-SI contents field indicates a length bigger than indicated in figure 9.11.3.51.9, receiving entity shall ignore any superfluous octets located at the end of the SOR-SNPN-SI.

8

7

6

5

4

3

2

1

Length of CH controlled prioritized list of preferred SNPNs contents

octet p+4

octet p+5

SNPN identity 1

octet (p+6)*

octet (p+14)*

SNPN identity 2

octet (p+15)*

octet (p+23)*

octet (p+24)*

octet (p+n*9-2)*

SNPN identity n

octet (p+n*9-3)*

octet (p+n*9+5)* = octet t*

Figure 9.11.3.51.10: CH controlled prioritized list of preferred SNPNs

8

7

6

5

4

3

2

1

MCC digit 2

MCC digit 1

octet p+15

MNC digit 3

MCC digit 3

octet p+16

MNC digit 2

MNC digit 1

octet p+17

0

Spare

0

Spare

0

Spare

0

Spare

NID assignment mode

octet p+18

NID value digit 2

NID value digit 1

octet p+19

NID value digit 4

NID value digit 3

octet p+20

NID value digit 6

NID value digit 5

octet p+21

NID value digit 8

NID value digit 7

octet p+22

NID value digit 10

NID value digit 9

octet p+23

Figure 9.11.3.51.11: SNPN identity

Table 9.11.3.51.5: CH controlled prioritized list of preferred SNPNs

Mobile country code (MCC):

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

Mobile network code (MNC):

The coding of MNC 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".

NID assignment mode

NID assignment mode is coded as specified in 3GPP TS 23.003 [4].

NID value

NID value is coded as specified in 3GPP TS 23.003 [4].

8

7

6

5

4

3

2

1

Length of CH controlled prioritized list of GINs contents

octet t+1

octet t+2

GIN 1

octet (t+3)*

octet (t+11)*

GIN 2

octet (t+12)*

octet (t+20)*

octet (t+21)*

octet (t+n*9-5)*

GIN n

octet (t+n*9-6)*

octet (t+n*9+2)* = octet u*

Figure 9.11.3.51.12: CH controlled prioritized list of GINs

8

7

6

5

4

3

2

1

MCC digit 2

MCC digit 1

octet t+12

MNC digit 3

MCC digit 3

octet t+13

MNC digit 2

MNC digit 1

octet t+14

0

Spare

0

Spare

0

Spare

0

Spare

NID assignment mode

octet t+15

NID value digit 2

NID value digit 1

octet t+16

NID value digit 4

NID value digit 3

octet t+17

NID value digit 6

NID value digit 5

octet t+18

NID value digit 8

NID value digit 7

octet t+19

NID value digit 10

NID value digit 9

octet t+20

Figure 9.11.3.51.13: GIN

Table 9.11.3.51.6: CH controlled prioritized list of GINs

Mobile country code (MCC):

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

Mobile network code (MNC):

The coding of MNC 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".

NID assignment mode

NID assignment mode is coded as specified in 3GPP TS 23.003 [4].

NID value

NID value is coded as specified in 3GPP TS 23.003 [4].

Editor’s note (WI eNPN, CR#3584): Whether the secured packet can contain SOR-SNPN-SI is FFS.

9.11.3.51A Supported codec list

See subclause 10.5.4.32 in 3GPP TS 24.008 [12].

9.11.3.52 Time zone

See subclause 10.5.3.8 in 3GPP TS 24.008 [12].

9.11.3.53 Time zone and time

See subclause 10.5.3.9 in 3GPP TS 24.008 [12].

9.11.3.53A UE parameters update transparent container

The purpose of the UE parameters update transparent container when sent from the network to the UE is to provide UE parameters update data, optional acknowledgement request and optional re-registration request. The purpose of the UE parameters update transparent container when sent from the UE to the network is to indicate the UE acknowledgement of successful reception of the UE parameters update transparent container.

The UE parameters update transparent container information element is coded as shown in figure 9.11.3.53A.1, figure 9.11.3.53A.2, figure 9.11.3.53A.3, figure 9.11.3.53A.4, figure 9.11.3.53A.5, figure 9.11.3.53A.6, figure 9.11.3.53A.7 and table 9.11.3.53A.1.

The UE parameters update transparent container is a type 6 information element with a minimum length of 20 octets.

8

7

6

5

4

3

2

1

UE parameters update transparent container IEI

octet 1

Length of UE parameters update transparent container contents

octet 2

octet 3

UE parameters update header

octet 4

UPU-MAC-IAUSF

octet 5-20

CounterUPU

octet 21-22

UE parameters update list

octet 23* – n*

Figure 9.11.3.53A.1: UE parameters update transparent container information element for UE parameters update data type with value "0"

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

0

Spare

UE parameters update data set 1 type

octet 23*

Length of UE parameters update data set 1

octet 24*-

25*

UE parameters update data set 1

octet 26*-

x*

0

Spare

0

Spare

0

Spare

0

Spare

UE parameters update data set n type

octet y*

Length of UE parameters update data set n

octet y+1*-

y+2*

UE parameters update data set n

octet y+3*-

n*

Figure 9.11.3.53A.2: UE parameters update list

8

7

6

5

4

3

2

1

Secured packet

octet a* – a+z*

Figure 9.11.3.53A.3: UE parameters update data set for UE parameters update data set type with value "0001"

8

7

6

5

4

3

2

1

Default configured NSSAI

octet b* –

c*

Figure 9.11.3.53A.4: UE parameters update data set for UE parameters update data set type with value "0010"

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

DREI

octet d*

Figure 9.11.3.53A.4A: UE parameters update data set for UE parameters update data set type with value "0011"

UE parameters update transparent container IEI

octet 1

Length of UE parameters update transparent container contents

octet 2

octet 3

UE parameters update header

octet 4

UPU-MAC-IUE

octet 5 – 20

Figure 9.11.3.53A.5: UE parameters update transparent container information element for UE parameters update data type with value "1"

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

REG

ACK

UPU data type

octet 4

Figure 9.11.3.53A.6: UE parameters update header for UE parameters update data type with value "0"

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

UPU data type

octet 4

Figure 9.11.3.53A.7: UE parameters update header for UE parameters update data type with value "1"

Table 9.11.3.53A.1: UE parameters update transparent container information element

UPU-MAC-IAUSF, UPU-MAC-IUE and CounterUPU are coded as specified in 3GPP TS 33.501 [24]

UPU data type (octet 4, bit 1)

0

The UE parameters update transparent container carries a UE parameters update list

1

The UE parameters update transparent container carries an acknowledgement of successful reception of a UE parameters update list

Acknowledgement (ACK) value (octet 4, bit 2)

0

acknowledgement not requested

1

acknowledgement requested

Re-registration (REG) value (octet 4, bit 3)

0

re-registration not requested

1

re-registration requested

UE parameters update data set type

Bits

4 3 2 1

0 0 0 1 Routing indicator update data

0 0 1 0 Default configured NSSAI update data

0 0 1 1 Disaster roaming information updating data

All other values are reserved

Disaster Roaming Enabled Indication (DREI) value (octet d*, bit 1)

Bit

1

Disaster roaming is disabled in the UE

Disaster roaming is enabled in the UE

The secured packet is coded as specified in 3GPP TS 31.115 [22B].

The default configured NSSAI is encoded as the value part of the NSSAI IE (see subclause 9.11.3.37).

9.11.3.54 UE security capability

The UE security capability information element is used by the UE and by the network to indicate which security algorithms are supported by the UE in N1 mode for NAS security as well as which security algorithms are supported over NR and E-UTRA connected to 5GCN for AS security.

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

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

Octets 5 to 10 are optional. If octet 5 is included, then also octet 6 shall be included.

If the UE does not support any security algorithm for AS security over E-UTRA connected to 5GCN, it shall not include octets 5 and 6. The UE shall not include octets 7 to 10.

If the UE does not support any security algorithm for AS security over E-UTRA connected to 5GCN, and if the network includes octets 7 to 10, then the network shall also include octets 5 to 6.

If the network includes octet 7, then it shall include also octet 8. If the network includes octet 9, then it shall include also octet 10.

8

7

6

5

4

3

2

1

UE security capability IEI

octet 1

Length of UE 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-IA0

128-

5G-IA1

128-

5G-IA2

128-

5G-IA3

5G-IA4

5G-IA5

5G-IA6

5G-IA7

octet 4

EEA0

128-

EEA1

128-

EEA2

128-

EEA3

EEA4

EEA5

EEA6

EEA7

octet 5*

EIA0

128-

EIA1

128-

EIA2

128-

EIA3

EIA4

EIA5

EIA6

EIA7

octet 6*

0

0

0

0

0

0

0

0

Spare

octet 7* -10*

Figure 9.11.3.54.1: UE security capability information element

Table 9.11.3.54.1: UE security capability information element

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

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 integrity algorithms supported (see NOTE 2) (octet 4)

5GS integrity algorithm 5G-IA0 supported (octet 4, bit 8)

0

5GS integrity algorithm 5G-IA0 not supported

1

5GS integrity algorithm 5G-IA0 supported

5GS integrity algorithm 128-5G-IA1 supported (octet 4, 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 4, 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 4, 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 4, bit 4)

0

5GS integrity algorithm 5G-IA4 not supported

1

5GS integrity algorithm 5G-IA4 supported

5GS integrity algorithm 5G-IA5 supported (octet 4, bit 3)

0

5GS integrity algorithm 5G-IA5 not supported

1

5GS integrity algorithm 5G-IA5 supported

5GS integrity algorithm 5G-IA6supported (octet 4, bit 2)

0

5GS integrity algorithm 5G-IA6 not supported

1

5GS integrity algorithm 5G-IA6 supported

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

0

5GS integrity algorithm 5G-IA7 not supported

1

5GS integrity algorithm 5G-IA7 supported

EPS encryption algorithms supported (see NOTE 3) (octet 5)

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

0

EPS encryption algorithm EEA0 not supported

1

EPS encryption algorithm EEA0 supported

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

0

EPS encryption algorithm 128-EEA1 not supported

1

EPS encryption algorithm 128-EEA1 supported

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

0

EPS encryption algorithm 128-EEA2 not supported

1

EPS encryption algorithm 128-EEA2 supported

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

0

EPS encryption algorithm 128-EEA3 not supported

1

EPS encryption algorithm 128-EEA3 supported

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

0

EPS encryption algorithm EEA4 not supported

1

EPS encryption algorithm EEA4 supported

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

0

EPS encryption algorithm EEA5 not supported

1

EPS encryption algorithm EEA5 supported

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

0

EPS encryption algorithm EEA6 not supported

1

EPS encryption algorithm EEA6 supported

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

0

EPS encryption algorithm EEA7 not supported

1

EPS encryption algorithm EEA7 supported

EPS integrity algorithms supported (see NOTE 4) (octet 6)

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

0

EPS integrity algorithm EIA0 not supported

1

EPS integrity algorithm EIA0 supported

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

0

EPS integrity algorithm 128-EIA1 not supported

1

EPS integrity algorithm 128-EIA1 supported

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

0

EPS integrity algorithm 128-EIA2 not supported

1

EPS integrity algorithm 128-EIA2 supported

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

0

EPS integrity algorithm 128-EIA3 not supported

1

EPS integrity algorithm 128-EIA3 supported

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

0

EPS integrity algorithm EIA4 not supported

1

EPS integrity algorithm EIA4 supported

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

0

EPS integrity algorithm EIA5 not supported

1

EPS integrity algorithm EIA5 supported

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

0

EPS integrity algorithm EIA6 not supported

1

EPS integrity algorithm EIA6 supported

EPS integrity algorithm EIA7 supported (octet 6, bit 1)

0

EPS integrity algorithm EIA7 not supported

1

EPS integrity algorithm EIA7 supported

For the UE not supporting any security algorithm for AS security over E-UTRA connected to 5GCN, all bits in octets 5 to 10 are spare and shall be ignored, if the respective octet is received with the information element.

For the UE supporting at least one security algorithm for AS security over E-UTRA connected to 5GCN all bits in octets 7 to 10 are spare and shall be ignored, if the respective octet is received with the information element.

If the AMF receives any of the octets 7 to 10 (NOTE 5), it shall store the octets as received and include them when sending the UE security capability information element to the UE.

NOTE 1: The code points in octet 3 are used to indicate support for 5GS encryption algorithms for NAS security in N1 mode and support for 5GS encryption algorithms for AS security over NR.

NOTE 2: The code points in octet 4 are used to indicate support for 5GS integrity algorithms for NAS security in N1 mode and support for 5GS integrity algorithms for AS security over NR.

NOTE 3: The code points in octet 5 are used to indicate support for EPS encryption algorithms for AS security over E-UTRA connected to 5GCN.

NOTE 4: The code points in octet 6 are used to indicate support for EPS integrity algorithms for AS security over E-UTRA connected to 5GCN.

NOTE 5: The AMF can receive this information element also from another AMF or MME during N1 mode to N1 mode or S1 mode to N1 mode handover preparation.

9.11.3.55 UE’s usage setting

The purpose of the UE’s usage setting information element is to provide the network with the UE’s usage setting as defined in 3GPP TS 24.301 [15]. The network uses the UE’s usage setting to select the RFSP index.

The UE’s usage setting information element is coded as shown in figure 9.11.3.55.1 and table 9.11.3.55.1.

The UE’s usage setting is a type 4 information element with a length of 3 octets.

8

7

6

5

4

3

2

1

UE’s usage setting IEI

octet 1

Length of UE’s usage setting contents

octet 2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

UE’s usage setting

octet 3

Figure 9.11.3.55.1: UE’s usage setting information element

Table 9.11.3.55.1: UE’s usage setting information element

UE’s usage setting (octet 3, bit 1)

0

voice centric

1

data centric

All other bits in the octet 3 are spare and shall be coded as zero,

9.11.3.56 UE status

The purpose of the UE status information element is to provide the network with information concerning aspects of the current UE registration status which is used for interworking with EPS.

The UE status information element is coded as shown in figure 9.11.3.56.1 and table 9.11.3.56.1.

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

8

7

6

5

4

3

2

1

UE status IEI

octet 1

Length of UE status contents

octet 2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

N1 mode reg

S1 mode reg

octet 3

Figure 9.11.3.56.1: UE status information element

Table 9.11.3.56.1: UE status information element

EMM registration status (S1 mode reg) (octet 3, bit 1)

0

UE is not in EMM-REGISTERED state

1

UE is in EMM-REGISTERED state

5GMM registration status (N1 mode reg) (octet 3, bit 2)

0

UE is not in 5GMM-REGISTERED state

1

UE is in 5GMM-REGISTERED state

All other bits in the octet 3 are spare and shall be coded as zero.

9.11.3.57 Uplink data status

The purpose of the Uplink data status information element is to indicate to the network which preserved PDU sessions have uplink data pending.

The Uplink data status information element is coded as shown in figure 9.11.3.57.1 and table 9.11.3.57.1.

The Uplink data status information element is a type 4 information element with minimum length of 4 octets a maximum length of 34 octets.

8

7

6

5

4

3

2

1

Uplink data status IEI

octet 1

Length of uplink data status contents

octet 2

PSI

(7)

PSI

(6)

PSI

(5)

PSI

(4)

PSI

(3)

PSI

(2)

PSI

(1)

PSI

(0)

octet 3

PSI

(15)

PSI

(14)

PSI

(13)

PSI

(12)

PSI

(11)

PSI

(10)

PSI

(9)

PSI

(8)

octet 4

0

0

0

0

0

0

0

0

spare

octet 5* -34*

Figure 9.11.3.57.1: Uplink data status information element

Table 9.11.3.57.1: Uplink data status information element

PSI(x) shall be coded as follows:

PSI(0):

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

PSI(1) – PSI(15):

0 indicates that no uplink data are pending for the corresponding PDU session identity or the PDU session is in PDU SESSION INACTIVE state or is in PDU SESSION ACTIVE state with user-plane resources already established.

1 indicates that uplink data are pending for the corresponding PDU session identity and the user-plane resources for the corresponding PDU session are not established.

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

9.11.3.58 Void

9.11.3.59 Void

9.11.3.60 Void

9.11.3.61 Void

9.11.3.62 Void

9.11.3.63 Void

9.11.3.64 Void

9.11.3.65 Void

9.11.3.66 Void

9.11.3.67 Void

9.11.3.68 UE radio capability ID

The purpose of the UE radio capability ID information element is to carry a UE radio capability ID.

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

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

8

7

6

5

4

3

2

1

UE radio capability ID IEI

octet 1

Length of UE radio capability ID contents

octet 2

UE radio capability ID

octet 3

octet n

Figure 9.11.3.68.1: UE radio capability ID information element

Table 9.11.3.68.1: UE radio capability ID information element

UE radio capability ID (octets 3 to n)

The UE radio capability ID contents contain the UE radio capability ID as specified in 3GPP TS 23.003 [4], with each hexadecimal digit coded over 4 bits, starting with the first hexadecimal digit coded in bits 4 to 1 of octet 3, the second hexadecimal digit coded in bits 8 to 5 of octet 3, and so on. If the UE radio capability ID contains an odd number of hexadecimal digits, bits 8 to 5 of the last octet (octet n) shall be coded as "1111".

9.11.3.69 UE radio capability ID deletion indication

The purpose of the UE radio capability ID deletion indication information element is to indicate to the UE that deletion of UE radio capability IDs is requested.

The UE radio capability ID deletion indication is a type 1 information element.

The UE radio capability ID deletion indication information element is coded as shown in figure 9.11.3.69.1 and table 9.11.3.69.1.

8

7

6

5

4

3

2

1

UE radio capability ID deletion indication

IEI

0

spare

Deletion request

octet 1

Figure 9.11.3.69.1: UE radio capability ID deletion indication information element

Table 9.11.3.69.1: UE radio capability ID deletion indication information element

Deletion requested (octet 1)

Bits

3

2

1

0

0

0

UE radio capability ID deletion not requested

0

0

1

Network-assigned UE radio capability IDs deletion requested

All other values are unused and shall be interpreted as "UE radio capability ID deletion not requested", if received by the UE.

9.11.3.70 Truncated 5G-S-TMSI configuration

The purpose of the Truncated 5G-S-TMSI configuration information element is to provide the size of the components of the truncated 5G-S-TMSI to the UE in NB-N1 mode to create the truncated 5G-S-TMSI.

The Truncated 5G-S-TMSI configuration information element is coded as shown in figure 9.11.3.70.1 and table 9.11.3.70.1.

The Truncated 5G-S-TMSI configuration is a type 4 information element with 3 octets length.

8

7

6

5

4

3

2

1

Truncated 5G-S-TMSI configuration IEI

octet 1

Length of Truncated 5G-S-TMSI configuration contents

octet 2

Truncated AMF Set ID value

Truncated AMF Pointer value

octet 3

Figure 9.11.3.70.1: Truncated 5G-S-TMSI configuration information element

Table 9.11.3.70.1: Truncated 5G-S-TMSI configuration information element

Truncated AMF Pointer value (bits 4 to 1 of octet 3)

This field represents the size of the least significant bits of the AMF Pointer.

Bits

4

3

2

1

0

0

0

0

reserved

0

0

0

1

1 least significant bit of the AMF Pointer

0

0

1

0

2 least significant bits of the AMF Pointer

0

0

1

1

3 least significant bits of the AMF Pointer

0

1

0

0

4 least significant bits of the AMF Pointer

0

1

0

1

5 least significant bits of the AMF Pointer

0

1

1

0

6 least significant bits of the AMF Pointer

All other values shall be interpreted as "6 least significant bits of the AMF Pointer" by this version of the protocol.

Truncated AMF Set ID value (bits 8 to 5 of octet 3)

This field represents the size of the least significant bits of the AMF Set ID.

Bits

4

3

2

1

0

0

0

0

reserved

0

0

0

1

1 least significant bit of the AMF Set ID

0

0

1

0

2 least significant bits of the AMF Set ID

0

0

1

1

3 least significant bits of the AMF Set ID

0

1

0

0

4 least significant bits of the AMF Set ID

0

1

0

1

5 least significant bits of the AMF Set ID

0

1

1

0

6 least significant bits of the AMF Set ID

0

1

1

1

7 least significant bits of the AMF Set ID

1

0

0

0

8 least significant bits of the AMF Set ID

1

0

0

1

9 least significant bits of the AMF Set ID

1

0

1

0

10 least significant bits of the AMF Set ID

All other values shall be interpreted as "10 least significant bits of the AMF Set ID" by this version of the protocol.

NOTE: Total sum of the "Truncated AMF Set ID value" and the "Truncated AMF Pointer value" in the Truncated 5G-S-TMSI configuration IE is specified in 3GPP TS 23.003 [4] and 3GPP TS 36.300 [25B].

9.11.3.71 WUS assistance information

See subclause 9.9.3.62 in 3GPP TS 24.301 [15].

9.11.3.72 N5GC indication

The purpose of the N5GC indication information element is to indicate to the network that the registration request by the W-AGF is on behalf of an N5GC device.

The N5GC indication information element is coded as shown in figure 9.11.3.72.1.

The N5GC indication is a type 1 information element.

8

7

6

5

4

3

2

1

N5GC indication IEI

0

Spare

0

Spare

0

Spare

N5GCREG

octet 1

Figure 9.11.3.72.1: N5GC indication

Table 9.11.3.72.1: N5GC indication

N5GC device indication bit (N5GCREG) (octet 1, bit 1)

Bit

1

0

N5GC device registration is not requested

1

N5GC device registration is requested

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

9.11.3.73 NB-N1 mode DRX parameters

The purpose of the NB-N1 mode DRX parameters information element is to indicate that the UE wants to use DRX in NB-N1 mode and for the network to indicate the DRX cycle value to be used at paging in NB-N1 mode.

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

The NB-N1 mode DRX parameters information element is coded as shown in figure 9.11.3.73.1 and table 9.11.3.73.1.

The value part of a DRX parameter information element is coded as shown in table 9.11.3.73.1.

8

7

6

5

4

3

2

1

NB-N1 mode DRX parameters IEI

octet 1

Length of NB-N1 mode DRX parameters contents

octet 2

0

0

0

0

NB-N1 mode DRX value

Spare

octet 3

Figure 9.11.3.73.1: NB-N1 mode DRX parameters information element

Table 9.11.3.73.1: NB-N1 mode DRX parameters information element

NB-N1 mode DRX value (octet 3, bits 1 to 4)

This field represents the DRX cycle parameter ‘T’, for NB-N1 mode, as defined in 3GPP TS 36.304 [25C].

Bits

4

3

2

1

0

0

0

0

DRX value not specified

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

1

DRX cycle parameter T = 1024

All other values shall be interpreted as "DRX value not specified" by this version of the protocol.

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

9.11.3.74 Additional configuration indication

The purpose of the Additional configuration indication information element is to indicate additional information associated with the generic UE configuration update procedure.

The Additional configuration indication information element is coded as shown in figure 9.11.3.74.1 and table 9.11.3.74.1.

The Additional configuration indication is a type 1 information element.

8

7

6

5

4

3

2

1

Additional configuration indication IEI

0

Spare

0

Spare

0

Spare

SCMR

octet 1

Figure 9.11.3.74.1: Additional configuration indication

Table 9.11.3.74.1: Additional configuration indication

Signalling connection maintain request (SCMR) (octet 1, bit 1)

Bit

1

0

no additional information

1

release of N1 NAS signalling connection not required

Bits 2 to 4 are spare and shall be coded as zero,

9.11.3.75 Extended rejected NSSAI

The purpose of the Extended rejected NSSAI information element is to identify a collection of rejected S-NSSAIs if UE supports extended rejected NSSAI.

The Extended rejected NSSAI information element is coded as shown in figure 9.11.3.75.1, figure 9.11.3.75.2 and table 9.11.3.75.1.

The Extended rejected NSSAI is a type 4 information element with a minimum length of 5 octets and a maximum length of 90 octets.

8

7

6

5

4

3

2

1

Extended rejected NSSAI IEI

octet 1

Length of Extended rejected NSSAI contents

octet 2

Partial extended rejected NSSAI list 1

octet 3

octet m

Partial extended rejected NSSAI list 2

octet m+1*

octet n*

octet n+1*

octet u*

Partial extended rejected NSSAI list n

octet u+1*

octet v*

Figure 9.11.3.75.1: Extended rejected NSSAI information element

8

7

6

5

4

3

2

1

spare

Type of list

Number of elements

octet 3

Rejected S-NSSAI 1

octet 4

octet j

Rejected S-NSSAI 2

octet j+1*

octet k*

octet k+1

octet p*

Rejected S-NSSAI n

octet p+1*

octet m*

Figure 9.11.3.75.2: Partial extended rejected NSSAI list – type of list = 000

8

7

6

5

4

3

2

1

spare

Type of list

Number of elements

octet 3

Back-off timer value

octet 4

Rejected S-NSSAI 1

octet 5

octet j

Rejected S-NSSAI 2

octet j+1*

octet k*

octet k+1*

octet p*

Rejected S-NSSAI n

octet p+1*

octet m*

Figure 9.11.3.75.3: Partial extended rejected NSSAI list – type of list = 001

8

7

6

5

4

3

2

1

Length of rejected S-NSSAI

Cause value

octet 4

SST

octet 5

SD

octet 6*

octet 8*

Mapped HPLMN SST

octet 9*

Mapped HPLMN SD

octet 10*

octet 12*

Figure 9.11.3.75.4: Rejected S-NSSAI

Table 9.11.3.75.1: Extended rejected NSSAI information element

Value part of the Extended rejected NSSAI information element (octet 3 to v)

The value part of the Extended rejected NSSAI information element consists of one or more partial extended rejected NSSAI lists. The length of each partial extended rejected NSSAI list can be determined from the ‘type of list’ field and the ‘number of elements’ field in the first octet of the partial extended rejected NSSAI list.

Each rejected S-NSSAI consists of one S-NSSAI and an associated cause value. Each rejected S-NSSAI also includes the mapped HPLMN S-NSSAI if available. The length of each rejected S-NSSAI can be determined by the ‘length of rejected S-NSSAI’ field in the first octet of the rejected S-NSSAI.

The UE shall store the complete list received (NOTE 0). If more than 8 rejected S-NSSAIs are included in this information element, the UE shall store the first 8 rejected S-NSSAIs and ignore the remaining octets of the information element.

Partial extended rejected NSSAI list:

Number of elements (octet 3, bits 1 to 4)

Bits

4

3

2

1

0

0

0

0

1 element

0

0

1

0

2 element

0

1

1

0

7 element

0

1

1

1

8 element

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

Type of list (octet 3, bits 5 to 7) (NOTE 7)

Bits

7

6

5

0

0

0

list of S-NSSAIs without any associated back-off timer value

0

0

1

list of S-NSSAIs with one associated back-off timer value that applies to all S-NSSAIs in the list

All other values are reserved.

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

Back-off timer value (octet 4):

Back-off timer value is coded as the value part of GPRS timer 3 in subclause 10.5.7.4a in 3GPP TS 24.008 [12].

Rejected S-NSSAI:

Cause value (octet 4)

Bits

4

3

2

1

0

0

0

0

S-NSSAI not available in the current PLMN or SNPN

0

0

0

1

S-NSSAI not available in the current registration area

0

0

1

0

S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization

0

0

1

1

S-NSSAI not available due to maximum number of UEs reached

All other values are reserved.

Slice/service type (SST) (octet 5)

This field contains the 8 bit SST value. The coding of the SST value part is defined in 3GPP TS 23.003 [4]. (NOTE 5)

Slice differentiator (SD) (octet 6 to octet 8)

This field contains the 24 bit SD value. The coding of the SD value part is defined in 3GPP TS 23.003 [4]. (NOTE 6)

If the SST encoded in octet 4 is not associated with a valid SD value, and the sender needs to include a mapped HPLMN SST (octet 8) and a mapped HPLMN SD (octets 9 to 11), then the sender shall set the SD value (octets 5 to 7) to "no SD value associated with the SST".

mapped HPLMN Slice/service type (SST) (octet 9)

This field contains the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SST value is mapped. The coding of the SST value part is defined in 3GPP TS 23.003 [4].

mapped HPLMN Slice differentiator (SD) (octet 10 to octet 12)

This field contains the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SD value is mapped. The coding of the SD value part is defined in 3GPP TS 23.003 [4].

NOTE 0: The number of rejected S-NSSAI(s) shall not exceed eight.

NOTE 1: Octet 4 and octet 5 shall always be included.

NOTE 2: If the octet 6 is included, then octet 7 and octet 8 shall be included.

NOTE 3: If the octet 9 is included, then octets 10, 11, and 12 may be included.

NOTE 4: If the octet 10 is included, then octet 11 and octet 12 shall be included.

NOTE 5: If the Cause value is "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", this field shall contain the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN and octets 9, 10, 11, and 12 shall not be included.

NOTE 6: If the Cause value is "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", this field shall contain the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN and octets 9, 10, 11, and 12 shall not be included.

NOTE 7: The partial extended rejected NSSAI with type of list = 001 shall only be used for rejected S-NSSAI(s) with the rejection cause "S-NSSAI not available due to maximum number of UEs reached".

9.11.3.76 UE request type

See subclause 9.9.3.65 in 3GPP TS 24.301 [15].

9.11.3.77 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.11.3.77.1, figure 9.11.3.77.2 and table 9.11.3.77.1.

The Paging restriction is a type 4 information element with a minimum length of 3 octets and a maximum length of 35 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.11.3.77.1: Paging restriction information element for Paging restriction type = "All paging is restricted" and for Paging restriction type = "All paging is restricted except voice"

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

PSI

(7)

PSI

(6)

PSI

(5)

PSI

(4)

PSI

(3)

PSI

(2)

PSI

(1)

PSI

(0)

octet 4

PSI

(15)

PSI

(14)

PSI

(13)

PSI

(12)

PSI

(11)

PSI

(10)

PSI

(9)

PSI

(8)

octet 5

0 0 0 0 0 0 0 0

spare

octet 6*-35*

Figure 9.11.3.77.2: Paging restriction information element for Paging restriction type = "All paging is restricted except for specified PDU session(s)" and for Paging restriction type = "All paging is restricted except for voice service and specified PDU session(s)"

Table 9.11.3.77.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 PDU session(s)

0

1

0

0

All paging is restricted except for voice service and specified PDU session(s)

All other values are reserved.

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

PSI(x) (bits 8 to 1 of octet 4 and octet 5):

This field indicates the PDU session identity of the PDU session for which paging is restricted.

PSI(0): (bit 1 of octet 4)

Spare and shall be coded as zero.

PSI(1) – PSI(15):

0 indicates that paging is restricted for the PDU session associated with the PDU session identity.

1 indicates that paging is not restricted for the PDU session associated with the PDU session identity.

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

9.11.3.78 Void

9.11.3.79 NID

See subclause 9.2.7 in 3GPP TS 24.502 [18].

9.11.3.80 PEIPS assistance information

The purpose of the PEIPS assistance information, information element is to transfer the required assistance information to indicate the paging subgroup used when paging the UE.

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

The PEIPS assistance information, information element is coded as shown in figure 9.11.3.80.1, figure 9.11.3.80.2 and table 9.11.3.80.1.

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

8

7

6

5

4

3

2

1

PEIPS assistance information IEI

octet 1

Length of PEIPS assistance information contents

octet 2

PEIPS assistance information type 1

octet 3

octet i

PEIPS assistance information type 2

octet i+1*

octet l*

octet l+1*

octet m*

PEIPS assistance information type p

octet m+1*

octet n*

Figure 9.11.3.80.1: PEIPS assistance information information element

8

7

6

5

4

3

2

1

Type of information

Paging subgroup ID value

octet 1

Figure 9.11.3.80.2: PEIPS assistance information type –type of information= "000"

Table 9.11.3.80.1: PEIPS assistance information information element

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

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

PEIPS assistance information type:

Type of information (octet 1, bits 6-8)

Bits

8

7

6

0

0

0

Paging subgroup ID

All other values are reserved.

Paging subgroup ID value: (octet 1, bits 1-5)

This field contains the value (in decimal) of paging subgroup ID that is assigned by the AMF for paging the UE. This field has a valid range of values from (0-7). All other values are reserved and shall be interpreted as 0 by this version of the protocol.

Editor’s Note: The exact range to be used for paging subgroup ID is FFS.

9.11.3.81 5GS additional request result

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

The 5GS additional request result information element is coded as shown in figure 9.11.3.81.1 and table 9.11.3.81.1.

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

8

7

6

5

4

3

2

1

5GS additional request result IEI

octet 1

Length of 5GS additional request result contents

octet 2

0 Spare

0 Spare

0 Spare

0 Spare

0 Spare

0 Spare

PRD

octet 3

Figure 9.11.3.81.1: 5GS additional request result information element

Table 9.11.3.81.1: 5GS 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.11.3.82 NSSRG information

The purpose of the NSSRG information information element is to identify one or more NSSRG values associated with each of the S-NSSAIs in a configured NSSAI.

The NSSRG information information element is coded as shown in TBD.

The NSSRG information is a type 4 information element.

Editor’s note: Coding of NSSRG information IE is FFS.

9.11.3.83 List of PLMNs to be used in disaster condition

The purpose of the list of PLMNs to be used in disaster condition information element is to provide the "list of PLMN(s) to be used in disaster condition" associated with the serving PLMN to the UE.

The list of PLMNs to be used in disaster condition information element is coded as shown in figures 9.11.3.83.1 and 9.11.3.83.2 and table 9.11.3.83.1.

The list of PLMNs to be used in disaster condition is a type 4 information element, with a minimum length of 2 octets.

8

7

6

5

4

3

2

1

List of PLMNs to be used in disaster condition list IEI

octet 1

Length of list of PLMNs to be used in disaster condition contents

octet 2

PLMN ID 1

octet 3*

octet 5*

PLMN ID 2

octet 6*

octet 8*

octet 9*

octet g*

PLMN ID n

octet g+1*

octet q+3*

Figure 9.11.3.83.1: List of PLMNs to be used in disaster condition information element

8

7

6

5

4

3

2

1

MCC digit 2

MCC digit 1

octet q+1

MNC digit 3

MCC digit 3

octet q+2

MNC digit 2

MNC digit 1

octet q+3

Figure 9.11.3.83.2: PLMN ID n

Table 9.11.3.83.1: List of PLMNs to be used in disaster condition information element

MCC, Mobile country code (octet q+1 and bits 1 to 4 octet q+2)

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

MNC, Mobile network code (bits 5 to 8 of octet q+2 and octet q+3)

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 q+2 shall be coded as "1111".

The contents of 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 [12].

NOTE: The PLMN IDs are provided in decreasing order of priority, i.e. PLMN ID 1 indicates highest priority and PLMN ID n indicates lowest priority.

9.11.3.84 Registration wait range

The purpose of the registration wait range information element is to provide the disaster roaming wait range or the disaster return wait range to the UE.

The registration wait range information element is coded as shown in figure 9.11.3.84.1 and table 9.11.3.84.1.

The registration wait range is a type 4 information element, with a length of 4 octets.

8

7

6

5

4

3

2

1

Registration wait range IEI

octet 1

Length of registration wait range

octet 2

Minimum registration wait time

octet 3

Maximum registration wait time

octet 4

Figure 9.11.3.84.1: Registration wait range information element

Table 9.11.3.84.1: Registration wait range information element

Minimum registration wait time (octet 3)

The minimum registration wait time contains the minimum duration of the registration wait time, encoded as octet 2 of the GPRS timer information element (see 3GPP TS 24.008 [12] subclause 10.5.7.3).

Maximum registration wait time (octet 4)

The maximum registration wait time contains the maximum duration of the registration wait time, encoded as octet 2 of the GPRS timer information element (see 3GPP TS 24.008 [12] subclause 10.5.7.3).

9.11.3.85 PLMN identity

The purpose of the PLMN identity information element is to provide a PLMN identity.

The PLMN identity information element is coded as shown in figures 9.11.3.85.1, and table 9.11.3.85.1.

The PLMN identity is a type 4 information element.

8

7

6

5

4

3

2

1

PLMN identity IEI

octet 1

Length of PLMN identity contents

octet 2

MCC digit 2

MCC digit 1

octet 3

MNC digit 3

MCC digit 3

octet 4

MNC digit 2

MNC digit 1

octet 5

Figure 9.11.3.85.1: PLMN identity information element

Table 9.11.3.85.1: PLMN identity information element

MCC, Mobile country code (octet 3, octet 4 bits 1 to 4)

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

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

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 6 shall be coded as "1111".

The contents of 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 [12].