D.6 Information elements coding

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

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

D.6.1 UE policy delivery service message type

Table D.6.1.1: UE policy delivery service message type

Bits
8	7	6	5	4	3	2	1
0	0	0	0	0	0	0	0	Reserved
0	0	0	0	0	0	0	1	MANAGE UE POLICY COMMAND message
0	0	0	0	0	0	1	0	MANAGE UE POLICY COMPLETE message
0	0	0	0	0	0	1	1	MANAGE UE POLICY COMMAND REJECT message
0	0	0	0	0	1	0	0	UE STATE INDICATION message
0	0	0	0	0	1	0	1	UE POLICY PROVISIONING REQUEST message (see NOTE)
0	0	0	0	0	1	1	0	UE POLICY PROVISIONING REJECT message (see NOTE)

All other values are reserved
NOTE: Coding and usage of UE POLICY PROVISIONING REQUEST message and UE POLICY PROVISIONING REJECT message are specified in 3GPP TS 24.587 [19B].

D.6.2 UE policy section management list

The purpose of the UE policy section management list information element is to transfer from the PCF to the UE a list of instructions to be performed at the UE for management of UE policy section stored at the UE.

The UE policy section management list information element is coded as shown in figure D.6.2.1, figure D.6.2.2, figure D.6.2.3, figure D.6.2.4, figure D.6.2.5, figure D.6.2.6, figure D.6.2.7 and table D.6.2.1.

The UE policy section management list information element has a minimum length of 12 octets and a maximum length of 65534 octets.

8	7	6	5	4	3	2	1
UE policy section management list IEI								octet 1
Length of UE policy section management list contents								octet 2 octet 3
UE policy section management list contents								octet 4 octet z

Figure D.6.2.1: UE policy section management list information element

8	7	6	5	4	3	2	1
UE policy section management sublist (PLMN 1)								octet 4 octet a
UE policy section management sublist (PLMN 2)								octet a+1 octet b
…								octet b+1 … octet c
UE policy section management sublist (PLMN N)								octet c+1 octet z

Figure D.6.2.2: UE policy section management list contents

8	7	6	5	4	3	2	1
Length of UE policy section management sublist								octet d octet d+1
				MCC digit 1				octet d+2
MCC digit 2
				MCC digit 3				octet d+3
MNC digit 3
				MNC digit 1				octet d+4
MNC digit 2
UE policy section management sublist contents								octet d+5 octet y

Figure D.6.2.3: UE policy section management sublist

8	7	6	5	4	3	2	1
Instruction 1								octet d+5 octet e
Instruction 2								octet e+1 octet f
…								octet f+1 … octet g
Instruction N								octet g+1 octet e

Figure D.6.2.4: UE policy section management sublist contents

8	7	6	5	4	3	2	1
Instruction contents length								octet d+5 octet d+6
UPSC								octet d+7 octet d+8
UE policy section contents								octet d+9 octet k

Figure D.6.2.5: Instruction

8	7	6	5	4	3	2	1
UE policy part 1								octet l octet m
UE policy part 2								octet m+1 octet n
…								octet n+1 … octet o
UE policy part N								octet o+1 octet p

Figure D.6.2.6: UE policy section contents

8	7	6	5	4	3	2	1
UE policy part contents length								octet q octet q+1
0	0	0	0	UE policy part type				octet q+2
Spare				UE policy part type				octet q+2
UE policy part contents								octet q+3 octet r

Figure D.6.2.7: UE policy part

Table D.6.2.1: UE policy section management list information element

Value part of the UE policy section management list information element (octets 4 to z)

The value part of the UE policy section management list information element consists of one or several UE policy section management sublists.

UE policy section management sublist:

Length of UE policy section management sublist (octets d to d+1)

This field contains the binary encoding of the length of the UE policy section management sublist in units of octets.

MCC, Mobile country code (octet d+2, and bits 4 to 1 of octet d+3)

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

MNC, Mobile network code (bits 8 to 5 of octet d+3, and octet d+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. If a network operator decides to use only two digits in the MNC, MNC digit 3 shall be coded as "1111".

UE policy section management sublist contents (octets d+5 to y)

The UE policy section management sublist contents consist of one or several instructions.

Instruction:

Instruction contents length (octets d+5 to d+6)

This field contains the binary encoding of the instruction contents length in units of octets.

UPSC (octets d+7 to d+8)

This field contains the binary encoding of the UPSC. The value of the UPSC is set by the PCF.

UE policy section contents (octets d+9 to k)

The UE policy section contents consist of one or several UE policy parts.

UE policy part:

UE policy part contents length (octets q to q+1)

This field contains the binary encoding of the UE policy part contents length in units of octets.

UE policy part type (bits 4 to 1 of octet q+2)
Bits
4	3	2	1
0	0	0	0	Reserved
0	0	0	1	URSP
0	0	1	0	ANDSP
0	0	1	1	V2XP
0	1	0	0	ProSeP
All other values are reserved.

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

UE policy part contents

This field contains a UE policy part encoded as specified in 3GPP TS 24.526 [19] for the UE policy part type field set to "URSP" or "ANDSP", in 3GPP TS 24.588 [19C] for the UE policy part type field set to "V2XP" and in 3GPP TS 24.555 [19F] for the UE policy part type field set to "ProSeP" respectively.

D.6.3 UE policy section management result

The purpose of the UE policy section management result information element is to transfer from the UE to the PCF information about instructions for UE policy section management which the UE could not execute successfully.

The UE policy section management result information element is coded as shown in figure D.6.3.1, figure D.6.3.2, figure D.6.3.3, figure D.6.3.4, figure D.6.3.5 and table D.6.3.1.

The UE policy section management result information element has a minimum length of 12 octets and a maximum length of 65534 octets.

8	7	6	5	4	3	2	1
UE policy section management result IEI								octet 1
Length of UE policy section management result contents								octet 2 octet 3
UE policy section management result contents								octet 4 octet z

Figure D.6.3.1: UE policy section management result information element

8	7	6	5	4	3	2	1
UE policy section management subresult (PLMN 1)								octet 4 octet a
UE policy section management subresult (PLMN 2)								octet a+1 octet b
…								octet b+1 … octet c
UE policy section management subresult (PLMN N)								octet c+1 octet z

Figure D.6.3.2: UE policy section management result contents

8	7	6	5	4	3	2	1
Number of results								octet d
				MCC digit 1				octet d+1
MCC digit 2
				MCC digit 3				octet d+2
MNC digit 3
				MNC digit 1				octet d+3
MNC digit 2
UE policy section management subresult contents								octet d+4 octet y

Figure D.6.3.3: UE policy section management subresult

8	7	6	5	4	3	2	1
Result 1								octet d+4 octet d+8
Result 2								octet d+9 octet d+13
…								octet d+14 … octet e
Result N								octet e+1 octet e+5

Figure D.6.3.4: UE policy section management subresult contents

8	7	6	5	4	3	2	1
UPSC								octet f octet f+1
Failed instruction order								octet f+2 octet f+3
Cause								octet f+4

Figure D.6.3.5: Result

Table D.6.3.1: UE policy section management result information element

Value part of the UE policy section management result information element (octets 4 to z)

The value part of the UE policy section management result information element consists of one or several UE policy section management subresults.


UE policy section management subresult:

Number of results (octet d)

This field contains the binary encoding of number of results included in the UE policy section management subresult.

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

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

MNC, Mobile network code (bits 8 to 5 of octet d+2, and octet d+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, MNC digit 3 shall be coded as "1111".

UE policy section management subresult contents (octets d+4 to y) The UE policy section management subresult contents consist of one or several results.


Result (octet f to f+4)

UPSC (octet f to f+1)

This field contains the binary encoding of the UPSC. The value of the UPSC is set by the PCF

Failed instruction order (octets f+2 to f+3)

This field contains the binary encoding of the order of the failed instruction in the UE policy section management sublist.

Cause (octet f+4)
Bits
8	7	6	5	4	3	2	1
0	1	1	0	1	1	1	1	Protocol error, unspecified
The receiving entity shall treat any other value as 0110 1111, "protocol error, unspecified".

D.6.4 UPSI list

The purpose of the UPSI list information element is to transfer from the UE to the PCF a list of UPSIs.

The UPSI list information element is coded as shown in figure D.6.4.1, figure D.6.4.2, and table D.6.4.1.

The UPSI list information element has a minimum length of 10 octets and a maximum length of 65532 octets.

8	7	6	5	4	3	2	1
UPSI list IEI								octet 1
Length of UPSI list contents								octet 2 octet 3
UPSI sublist (PLMN 1)								octet 4 octet a
UPSI sublist (PLMN 2)								octet a+1* octet b*
…								octet b+1* octet c*
UPSI sublist (PLMN N)								octet c+1* octet z*

Figure D.6.4.1: UPSI list information element

8	7	6	5	4	3	2	1
Length of UPSI sublist								octet d octet d+1
MCC digit 2				MCC digit 1				octet d+2
MNC digit 3				MCC digit 3				octet d+3
MNC digit 2				MNC digit 1				octet d+4
UPSC								octet d+5 octet d+6
UPSC								octet d+7* octet d+8*
…								octet d+9* octet e*
UPSC								octet e+1* octet e+2*

Figure D.6.4.2: UPSI sublist

Table D.6.4.1: UPSI list information element

MCC, Mobile country code (octet d+2, and bits 4 to 1 of octet d+3)

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

MNC, Mobile network code (bits 8 to 5 of octet d+3, and octet d+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. If a network operator decides to use only two digits in the MNC, MNC digit 3 shall be coded as "1111".

UPSC (octets d+5 to d+6)

This field contains the binary encoding of the UPSC. The value of the UPSC is set by the PCF.

D.6.5 UE policy classmark

The purpose of the UE policy classmark information element is to provide the network with information about the policy aspects of the UE.

The UE policy classmark information element is coded as shown in figure D.6.5.1 and table D.6.5.1.

The UE policy classmark is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets.

8	7	6	5	4	3	2	1
Policy information IEI								octet 1
Length of Policy information contents								octet 2
0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	SupportANDSP	octet 3
0	0	0	0	0	0	0	0	octet 4* -5*
Spare

Figure D.6.5.1: UE policy classmark information element

Table D.6.5.1: UE policy classmark information element

Support of ANDSP by the UE (SupportANDSP) (octet 3, bit 1)
Bit
1
0	ANDSP not supported by the UE
1	ANDSP supported by the UE


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

D.6.6 UE OS Id

The purpose of the UE OS Id information element is to provide the network with information about the OS of the UE.

The UE OS Id information element is coded as shown in figure D.6.6.1 and table D.6.6.1.

The UE OS Id is a type 4 information element with a minimum length of 18 octet and a maximum length of 242 octets.

8	7	6	5	4	3	2	1
OS Id IEI								octet 1
Length of OS Id information contents								octet 2
OS Id_1								octets 3 – 18
…								…
OS Id_15								octets 227* -242*

Figure D.6.6.1: UE OS Id information element

Table D.6.6.1: UE OS Id information element

OS Id:

The OS Id is coded as a sequence of a sixteen octet OS Id value field. The OS Id value field is defined as Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 [35A].

D.6.7 UE policy network classmark

The purpose of the UE policy network classmark information element is to provide the UE with information about the policy aspects of the network.

The UE policy network classmark information element is coded as shown in figure D.6.7.1 and table D.6.7.1.

The UE policy network classmark is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets.

8	7	6	5	4	3	2	1
UE policy network classmark IEI								octet 1
Length of UE policy network classmark contents								octet 2
0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	0 Spare	NSSUI	octet 3
0	0	0	0	0	0	0	0	octet 4* -5*
Spare

Figure D.6.7.1: UE policy network classmark information element

Table D.6.7.1: UE policy network classmark information element

Non-subscribed SNPN signalled URSP handling indication (NSSUI) (octet 3, bit 1) (see NOTE)
Bits
1
0		UE is allowed to accept URSP signalled by non-subscribed SNPNs
1		UE is not allowed to accept URSP signalled by non-subscribed SNPNs

All other bits in octet 3 to 5 are spare and shall be coded as zero, if the respective octet is included in the information element.
NOTE: Receiving entity shall ignore this bit, if received from the RPLMN which is not the HPLMN or from the RSNPN which is not the subscribed SNPN.