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*

5G ProSe-l2relay

5G ProSe-dc

5G ProSe-dd

ER-NSSAI

5G-EHC-CP CIoT

multipleUP

WUSA

CAG

octet 5*

PR

RPR

PIV

NCR

NR-PSSI

5G ProSe-l3rmt

5G ProSe-l2rmt

5G ProSe-l3relay

octet 6*

UN-PER

ESI

NSAG

Ex-CAG

SSNPNSI

EventNotification

MINT

NSSRG

octet 7*

spare

spare

spare

spare

spare

spare

UAS

SBNS

octet 8*

0

0

0

0

0

0

0

0

octet 9*-15*

Spare

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)

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)

Bit

3

0

LPP in N1 mode not supported

1

LPP in N1 mode supported (see 3GPP TS 37.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.

Bit

4

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.

Bit

5

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.

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 3, 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

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

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)

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.

Bit

2

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

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

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.

Bit

7

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)

Bit

8

0

RACS not supported

1

RACS supported

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

Bit

1

0

CAG not supported

1

CAG supported

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

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.

Bit

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

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.

Bit

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

This bit indicates the capability for 5G ProSe direct discovery.

Bit

6

0

5G ProSe direct discovery not supported

1

5G ProSe direct discovery supported

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

This bit indicates the capability for 5G ProSe direct communication.

Bit

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

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

Bit

8

0

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

1

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

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

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

Bit

1

0

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

1

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

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

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

Bit

2

0

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

1

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

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

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

Bit

3

0

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

1

Acting as a 5G 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

Bit

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 restriction not supported

1

paging restriction supported

NSSRG (octet 7, bit 1)

This bit indicates the capability to support the NSSRG.

Bit

1

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)

Bit

2

0

MINT not supported

1

MINT supported

Event notification (EventNotification) (octet 7, bit 3)

This bit indicates the capability to support event notification for upper layers

Bit

3

0

Event notification not supported

1

Event notification supported

4

0

SOR-SNPN-SI not supported

1

SOR-SNPN-SI supported

Extended CAG information list support (Ex-CAG) (octet 7, bit 5)

This bit indicates the capability to support extended CAG information list.

Bit

5

0

Extended CAG information list not supported

1

Extended CAG information list supported

NSAG (octet 7, bit 6)

This bit indicates the capability to support NSAG.

Bit

6

0

NSAG not supported

1

NSAG supported

Equivalent SNPNs indicator (ESI) (octet 7, bit 7)

This bit indicates the capability to support equivalent SNPNs.

Bit

7

0

Equivalent SNPNs not supported

1

Equivalent SNPNs supported

5GMM cause IEI

octet 1

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

0

0

0

0

Disaster roaming for the determined PLMN with disaster condition not allowed

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

0

Selected N3IWF is not compatible with the allowed NSSAI

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

5GS DRX parameters IEI

octet 1

Length of 5GS DRX parameters contents

octet 2

0

0

0

0

DRX value

spare

octet 3

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.

5GS identity type

IEI

0

spare

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.

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

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*

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

MSIN digit 2

MSIN digit 1

octet 12

…

MSIN digit n+1

MSIN digit n

octet x

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

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

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

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

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

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 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 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 or the ME, 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".

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*

UN-PER

PR

RPR

PIV

NCR

5G-EHC-CP CIoT

ATS-IND

5G-LCS

octet 5*

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

4

3

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

4

3

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

UN-PER (octet 5, bit 8)

This bit indicates the capability to support Unavailability period

Bit

8

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

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

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

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) (NOTE)

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

5GS registration type IEI

FOR

5GS registration type value

octet 1

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

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

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*

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*

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

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*

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.

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

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

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

ABBA IEI

octet 1

Length of ABBA contents

octet 2

ABBA contents

octet 3

octet n

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.

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

0

K_AMF derivation is not required

1

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

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

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.

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*

Configuration update indication IEI

0

Spare

0

Spare

RED

ACK

octet 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,

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*

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 m

octet q+4m+1*

octet q+4m+4*

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

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

Data type

DDX

PDU session identity

octet 3

Data contents

octet 4

octet 257

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

Data type

Spare

octet 3

Data contents

octet 4

octet n

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.

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*

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

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