UE policy part contents length

octet 1

octet 2

0

0

0

0

UE policy part type={ProSeP}

octet 3

Spare

UE policy part contents={ProSeP contents}

octet 4

octet x

ProSeP info #1

octet 4

octet a

ProSeP info #2

octet (a+1)*

octet b*

…

octet (b+1)*

octet w*

ProSeP info #n

octet (w+1)*

octet x*

0

0

0

0

ProSeP info type

octet k

Spare

Length of ProSeP info contents

octet k+1

octet k+2

ProSeP info contents

octet k+3

octet l

UE policy part contents length field indicate the length of the ProSeP contents in octets.

ProSeP contents (octets 4 to x)

ProSeP contents consist of 1 or more ProSeP info(s) (see figure 5.2.2).

ProSeP info type (bit 1 to 4 of octet k) shall be set according to the following:

Bits

4

3

2

1

0

0

0

1

UE policies for 5G ProSe direct discovery

0

0

1

0

UE policies for 5G ProSe direct communications

0

0

1

1

UE policies for 5G ProSe UE-to-network relay UE

0

1

0

0

UE policies for 5G ProSe remote UE

0

1

0

1

UE policies for 5G ProSe usage information reporting

All other values are reserved.

Bits 8 to 5 of octet k are spare and shall be encoded as zero.

Length of ProSeP info contents (octets k+1 to k+2) indicates the length of the ProSeP info contents field.

ProSeP info contents (octets k+3 to l) can be UE policies for 5G ProSe direct discovery (see clause 5.3), UE policies for 5G ProSe direct communications (see clause 5.4), UE policies for 5G ProSe UE-to-network relay UE (see clause 5.5), UE policies for 5G ProSe remote UE (clause 5.6) or UE policies for 5G ProSe usage information reporting (clause 5.7).

0

0

0

0

ProSeP info type = {UE policies for 5G ProSe direct discovery}

octet k

Spare

Length of ProSeP info contents

octet k+1

octet k+2

Validity timer

octet k+3

octet k+7

Served by NG-RAN

octet k+8

octet o1

Not served by NG-RAN

octet o1+1

octet o2

ProSe direct discovery UE ID

octet o2+1

octet o2+3

Group member discovery parameters

octet o2+4

octet o3

ProSe identifiers

octet o3+1

octet o4

ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rules

octet o4+1

octet l

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

H5DAI

octet l+1

HPLMN 5G DDNMF address information

octet (l+2)*

octet m*

Length of ProSeP info contents (octets k+1 to k+2) indicates the length of ProSeP info contents.

Validity timer (octet k+3 to k+7):

The validity timer field provides the expiration time of validity of the UE policies for 5G ProSe direct discovery. The validity timer field is a binary coded representation of a UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

Served by NG-RAN (octet k+8 to o1):

The served by NG-RAN field is coded according to figure 5.3.2.2 and table 5.3.2.2, and contains configuration parameters for 5G ProSe direct discovery when the UE is served by NG-RAN.

Not served by NG-RAN (octet o1+1 to o2):

The not served by NG-RAN field is coded according to figure 5.3.2.6 and table 5.3.2.6, and contains configuration parameters for 5G ProSe direct discovery when the UE is not served by NG-RAN.

ProSe Direct Discovery UE ID (octet o2+1 to o2+3):

The ProSe Direct Discovery UE ID is a 24-bit long bit string.

Group member discovery parameters (octet o2+4 to o3):

The group member discovery parameters field is coded according to figure 5.3.2.12 and table 5.3.2.12 and contains group member discovery parameters.

ProSe identifiers (octet o3+1 to o4):

The ProSe identifiers field is coded according to figure 5.3.2.14 and table 5.3.2.14 and contains ProSe identifiers.

ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rules (octet o4+1 to o5):

The ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rules field is coded according to figure 5.3.2.15 and table 5.3.2.15 and contains ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rules.

If the length of ProSeP info contents field is bigger than indicated in figure 5.3.2.1, receiving entity shall ignore any superfluous octets located at the end of the ProSeP info contents.

HPLMN 5G DDNMF address information indicator (H5DAI) (octet l+1 bit 1 to bit 3): (NOTE)

Bits

3

2

1

0

0

0

HPLMN 5G DDNMF address information is absent

0

0

1

HPLMN 5G DDNMF FQDN is present

0

1

0

HPLMN 5G DDNMF IPv4 address is present

1

0

0

HPLMN 5G DDNMF IPv6 address is present

1

1

0

HPLMN 5G DDNMF IPv4 address and IPv6 address are present

All other values are reserved.

HLMN 5G DDNMF address information (octet l+2 to octet m):

The HPLMN 5G DDNMF address information field is coded according to figure 5.3.2.17 and table 5.3.2.17 and contains the 5G DDNMF address information in HPLMN.

NOTE: For backward compatibility with UEs compliant to earlier versions of present document, H5DAI values 011, 101 and 111 cannot be used.

Length of served by NG-RAN contents

octet k+8

octet k+9

Authorization for direct discovery info 1

octet k+10

octet o50

Authorization for direct discovery info 2

octet o50+1

octet o51

…

octet o51+1

octet o52

Authorization for direct discovery info n

octet o52+1

octet o1

Length of authorization for direct discovery info contents

octet o50+1

octet o50+2

0

spare

0

spare

0

spare

0

spare

0

spare

Role

Model

DDT

octet o50+3

Authorized PLMN info

octet o50+4

octet o51

Model (octet o50+3 bit 2):

Bit

2

0 A

1 B

If Model bit is set to "A",

Role (octet o50+3 bit 3):

Bit

3

0 Announcing

1 Monitoring

If Model bit is set to "B",

Role (octet o50+3 bit 3):

Bit

3

0 Discoverer

1 Discoveree

Authorized PLMN info (octet o50+4 to o51):

The authorized PLMN info field is coded according to figure 5.3.2.4 and table 5.3.2.4.

If the length of authorization for direct discovery info field is bigger than indicated in figure 5.3.2.3, receiving entity shall ignore any superfluous octets located at the end of the authorization for direct discovery info.

Length of authorized PLMN info contents

octet o50+4

octet o50+5

Authorized PLMN 1

octet (o50+6)*

octet (o50+8)*

Authorized PLMN 2

octet (o50+9)*

octet (o50+11)*

…

octet (o50+12)*

octet o150*

Authorized PLMN n

octet (o150+1)*

octet o51*

MCC digit 2

MCC digit 1

octet o50+6

MNC digit 3

MCC digit 3

octet o50+7

MNC digit 2

MNC digit 1

octet o50+8

Mobile network code (MNC) (octet o50+6 bit 5 to 8, octet o50+7):

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

Length of not served by NG-RAN contents

octet o1+1

octet o1+2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

PDNNI

octet o1+3

NR radio parameters per geographical area list

octet (o1+4)*

octet o10*

Default PC5 DRX configuration

octet (o10+1)*

octet o2*

NR radio parameters per geographical area list (octet o1+4 to o2):

If PNNI bit is set to "Authorized", the NR radio parameters per geographical area list field is present otherwise the NR radio parameters per geographical area list field is absent. It is coded according to figure 5.3.2.7 and table 5.3.2.7.

Default PC5 DRX configuration (octet o10+1 to o2):

If PDNNI bit is set to "Authorized", the default PC5 DRX configuration is present otherwise the default PC5 DRX configuration is absent. It is coded according to figure 5.3.2.11a and table 5.3.2.11a.

If the length of not served by NG-RAN contents field is bigger than indicated in figure 5.3.2.6, receiving entity shall ignore any superfluous octets located at the end of the not served by NG-RAN contents.

Length of radio parameters per geographical area list contents

octet o1+4

octet o1+5

Radio parameters per geographical area info 1

octet (o1+6)*

octet o6*

Radio parameters per geographical area info 2

octet (o6+1)*

octet o7*

…

octet (o7+1)*

octet o8*

Radio parameters per geographical area info n

octet (o8+1)*

octet o10*

Length of radio parameters per geographical area contents

octet o6+1

octet o6+2

Geographical area

octet o6+3

octet o9

Radio parameters

octet o9+1

octet o7-1

MI

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

octet o7

Radio parameters (octet o9 to o7-1):

The radio parameters field is coded according to figure 5.3.2.11 and table 5.3.2.11, applicable in the geographical area indicated by the geographical area field when not served by NG-RAN.

Managed indicator (MI) (octet o7 bit 8):

The managed indicator indicates how the radio parameters indicated in the radio parameters field in the geographical area indicated by the geographical area field are managed.

Bit

8

0 Non-operator managed

1 Operator managed

If the length of radio parameters per geographical area contents field is bigger than indicated in figure 5.3.2.8, receiving entity shall ignore any superfluous octets located at the end of the radio parameters per geographical area contents.

Length of geographical area contents

octet o6+3

octet o6+4

Coordinate 1

octet (o6+5)*

octet (o6+10)*

Coordinate 2

octet (o6+11)*

octet (o6+16)*

…

octet (o6+17)*

octet (o6-2+6*n)*

Coordinate n

octet (o6-1+6*n)*

octet (o6+4+6*n)* = octet o9*

Latitude

octet o6+11

octet o6+13

Longitude

octet o6+14

octet o6+17

Longitude:

The longitude field is coded according to clause 6.1 of 3GPP TS 23.032 [6].

Length of radio parameters contents

octet o9+1

octet o9+2

Radio parameters contents

octet o9+3

octet o7-1

Length of default PC5 DRX configuration contents

octet o10+1

octet o10+2

Default PC5 DRX configuration contents

octet o10+3

octet o2

Length of groupcast parameters contents

octet o2+4

octet o2+5

Application layer group info 1

octet (o2+6)*

octet o51*

Application layer group info 2

octet (o51+1)*

octet o52*

…

octet (o52+1)*

octet o53*

Application layer group info n

octet (o53+1)*

octet o3*

Length of application layer group info contents

octet o51+1

octet o51+2

Application layer group identifier

octet o51+3

octet o151

ProSe layer-2 group identifier

octet o151+1

octet o151+3

User info ID

octet o151+4

octet (o151+9) = octet o52

ProSe layer-2 group identifier (octet o151+1 to o151+3)

The ProSe layer-2 group identifier field is a binary coded layer-2 identifier.

User info ID (octet o151+4 to o52)

The value of the User info ID parameter is a 48-bit long bit string. The format of the User info ID parameter is out of scope of this specification.

If the length of application layer group info contents field is bigger than indicated in figure 5.3.2.13, receiving entity shall ignore any superfluous octets located at the end of the application layer group info contents.

Length of ProSe identifiers contents

octet o3+1

octet o3+2

ProSe identifier 1

octet (o3+3)*

octet o31*

ProSe identifier 2

octet (o31+1)*

octet o32*

…

octet (o32+1)*

octet o33*

ProSe identifier n

octet (o33+1)*

octet o34*

= octet o4*

NOTE: Further definition of the format of OS App ID is beyond the scope of this specification.

Length of ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rules contents

octet o4+1

octet o4+2

ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rule 1

octet (o4+3)*

octet o54*

ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rule 2

octet (o54+1)*

octet o55*

…

octet (o55+1)*

octet o56*

ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rule n

octet (o56+1)*

octet l*

Length of ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rule contents

octet o54+1

octet o54+2

ProSe identifiers

octet o54+3

octet o154

Destination layer-2 ID for initial discovery signalling

octet o154+1

octet (o154+3)

= octet o55

Destination layer-2 ID for initial discovery signalling (octet o154+1 to o55):

The destination layer-2 ID for initial discovery signalling field is a binary coded layer-2 identifier.

If the length of ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rule contents field is bigger than indicated in figure 5.3.2.16, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to default destination layer-2 ID for initial discovery signalling mapping rule contents.

Length of HPLMN 5G DDNMF address information contents

octet l+2

HPLMN 5G DDNMF address informationcontents

octet l+3

octet m

0

0

0

0

ProSeP info type = {UE policies for 5G ProSe direct communication}

octet k

Spare

Length of ProSeP info contents

octet k+1

octet k+2

Validity timer

octet k+3

octet k+7

Served by NG-RAN

octet k+8

octet o1

Not served by NG-RAN

octet o1+1

octet o2

Privacy config

octet o2+1

octet o4

5G ProSe direct communication in NR-PC5

octet o4+1

octet o5

ProSe application to path preference mapping rules

octet o5+1

octet o10

ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rules

octet o10+1

octet l

Length of ProSeP info contents (octets k+1 to k+2) indicates the length of ProSeP info contents.

Validity timer (octet k+3 to k+7):

The validity timer field provides the expiration time of validity of the UE policies for 5G ProSe direct communication. The validity timer field is a binary coded representation of a UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

Served by NG-RAN (octet k+8 to o1):

The served by NG-RAN field is coded according to figure 5.4.2.2 and table 5.4.2.2, and contains configuration parameters for 5G ProSe direct communication when the UE is served by NG-RAN.

Not served by NG-RAN (octet o1+1 to o2):

The not served by NG-RAN field is coded according to figure 5.4.2.5 and table 5.4.2.5, and contains configuration parameters for 5G ProSe direct communication when the UE is not served by NG-RAN.

Privacy config (octet o2+1 to o4):

The privacy config field is coded according to figure 5.4.2.11 and table 5.4.2.11, and contains configuration parameters for privacy configuration.

5G ProSe direct communication in NR-PC5 (octet o4+1 to o5):

The 5G ProSe direct communication in NR-PC5 field is coded according to figure 5.4.2.16 and table 5.4.2.16, and contains configuration parameters for 5G ProSe direct communication in NR-PC5.

ProSe application to path preference mapping rules (octet o5+1 to o10):

The ProSe application to path preference mapping rules field is coded according to figure 5.4.2.38 and table 5.4.2.38, and contains configuration parameters for ProSe application to path preference mapping rules.

ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rules (octet o10+1 to l):

The ProSe identifiers to NR Tx profiles for broadcast and groupcast mapping rules field is coded according to figure 5.4.2.41 and table 5.4.2.41, and contains configuration parameters for ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rules.

If the length of ProSeP info contents field is bigger than indicated in figure 5.4.2.1, receiving entity shall ignore any superfluous octets located at the end of the ProSeP info contents.

Length of served by NG-RAN contents

octet k+8

octet k+9

Authorized PLMN

octet k+10

octet o1

If the length of served by NG-RAN contents field is bigger than indicated in figure 5.4.2.2, receiving entity shall ignore any superfluous octets located at the end of the served by NG-RAN contents.

Length of authorized PLMN contents

octet k+10

octet k+11

PLMN ID 1

octet (k+12)*

octet (k+14)*

PLMN ID 2

octet (k+15)*

octet (k+17)*

…

octet (k+18)*

octet (k+8+n*3)*

PLMN ID n

octet (k+9+n*3)*

octet (k+11+n*3)* = octet o1*

MCC digit 2

MCC digit 1

octet k+15

MNC digit 3

MCC digit 3

octet k+16

MNC digit 2

MNC digit 1

octet k+17

Mobile network code (MNC) (octet k+16 bit 5 to 8, octet k+17):

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

Length of not served by NG-RAN contents

octet o1+1

octet o1+2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

PNNI

octet o1+3

NR radio parameters per geographical area list

octet (o1+4)*

octet o16*

PC5 DRX configuration for broadcast, groupcast and initial signalling of 5G ProSe direct link establishment

octet (o16+1)*

octet o2*

NR radio parameters per geographical area list (octet o1+4 to o16):

If PNNI bit is set to "Authorized", the NR radio parameters per geographical area list field is present otherwise the NR radio parameters per geographical area list field is absent. It is coded according to figure 5.4.2.6 and table 5.4.2.6.

PC5 DRX configuration for broadcast,groupcast and initial signalling of 5G ProSe direct link establishment (octet o16+1 to o2):

If PNNI bit is set to "Authorized", the PC5 DRX configuration for broadcast, groupcast and initial signalling of 5G ProSe direct link establishment field is present otherwise the PC5 DRX configuration for broadcast, groupcast and initial signalling of 5G ProSe direct link establishment field is absent. It is coded according to figure 5.4.2.10a and table 5.4.2.10a.

If the length of not served by NG-RAN contents field is bigger than indicated in figure 5.4.2.5, receiving entity shall ignore any superfluous octets located at the end of the not served by NG-RAN contents.

Length of radio parameters per geographical area list contents

octet o1+4

octet o1+5

Radio parameters per geographical area info 1

octet (o1+6)*

octet o6*

Radio parameters per geographical area info 2

octet (o6+1)*

octet o7*

…

octet (o7+1)*

octet o8*

Radio parameters per geographical area info n

octet (o8+1)*

octet o16*

Length of radio parameters per geographical area contents

octet o6+1

octet o6+2

Geographical area

octet o6+3

octet o9

Radio parameters

octet o9+1

octet o7-1

MI

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

octet o7

Radio parameters (octet o9 to o7-1):

The radio parameters field is coded according to figure 5.4.2.10 and table 5.4.2.10, applicable in the geographical area indicated by the geographical area field when not served by NG-RAN.

Managed indicator (MI) (octet o7 bit 8):

The managed indicator indicates how the radio parameters indicated in the radio parameters field in the geographical area indicated by the geographical area field are managed.

Bit

8

0 Non-operator managed

1 Operator managed

If the length of radio parameters per geographical area contents field is bigger than indicated in figure 5.4.2.7, receiving entity shall ignore any superfluous octets located at the end of the radio parameters per geographical area contents.

Length of geographical area contents

octet o6+3

octet o6+4

Coordinate 1

octet (o6+5)*

octet (o6+10)*

Coordinate 2

octet (o6+11)*

octet (o6+16)*

…

octet (o6+17)*

octet (o6-2+6*n)*

Coordinate n

octet (o6-1+6*n)*

octet (o6+4+6*n)* = octet o9*

Latitude

octet o6+11

octet o6+13

Longitude

octet o6+14

octet o6+17

Longitude:

The longitude field is coded according to clause 6.1 of 3GPP TS 23.032 [6].

Length of radio parameters contents

octet o9+1

octet o9+2

Radio parameters contents

octet o9+3

octet o7-1

Length of PC5 DRX configuration for broadcast, groupcast and initial signalling of 5G ProSe direct link establishment contents

octet o16+1

octet o16+2

PC5 QoS profile to PC5 DRX cycle mapping rules

octet o16+3

octet o17

Default PC5 DRX configuration

octet o17+1

octet o2

Default PC5 DRX configuration:

The default PC5 DRX configuration field is coded accoding to figure 5.3.2.11a and table 5.3.2.11a.

If the length of PC5 DRX configuration for broadcast, groupcast and initial signalling of 5G ProSe direct link establishment contents field indicates a length bigger than indicated in figure 5.4.2.5, receiving entity shall ignore any superfluous octets located at the end of the PC5 DRX configuration for broadcast, groupcast and initial signalling of 5G ProSe direct link establishment contents.

Length of PC5 QoS profile to PC5 DRX cycle mapping rules contents

octet o16+3

octet o16+4

PC5 QoS profile to PC5 DRX cycle mapping rule 1

octet (o16+5)*

octet o160*

PC5 QoS profile to PC5 DRX cycle mapping rule 2

octet (o160+1)*

octet o161*

…

octet (o161+1)*

octet o162*

PC5 QoS profile to PC5 DRX cycle mapping rule n

octet (o162+1)*

octet o17*

Length of PC5 QoS profile to PC5 DRX cycle mapping rule contents

octet o160+1

octet o160+2

PC5 QoS profile

octet o160+3

octet o1600

PC5 DRX cycle

octet o1600+1=o161

PC5 DRX cycle:

The PC5 DRX cycle field is coded as sl-DRX-GC-BC-Cycle-r17 in clause 6.3.5 of 3GPP TS 38.331 [7].

If the length of PC5 QoS profile to PC5 DRX cycle mapping rule contents field indicates a length bigger than indicated in figure 5.4.2.10b, receiving entity shall ignore any superfluous octets located at the end of the PC5 QoS profile to PC5 DRX cycle mapping rule contents.

Length of privacy config contents

octet o2+1

octet o2+2

ProSe applications requiring privacy

octet o2+3

octet o4-2

Privacy timer

octet o4-1

octet o4

Privacy timer (octet o4-1, octet o4):

The privacy timer field contains binary encoded duration, in units of seconds, after which the UE shall change the source layer-2 ID self-assigned by the UE while performing transmission of 5G ProSe direct communication when privacy is required.

If the length of privacy config contents field is bigger than indicated in figure 5.4.2.11, receiving entity shall ignore any superfluous octets located at the end of the privacy config contents.

Length of ProSe applications requiring privacy contents

octet o2+3

octet o2+4

ProSe application requiring privacy 1

octet (o2+5)*

octet o12*

ProSe application requiring privacy 2

octet (o12+1)*

octet o13*

…

octet (o13+1)*

octet o14*

ProSe application requiring privacy n

octet (o14+1)*

octet (o4-2)*

Length of ProSe application requiring privacy contents

octet o12+1

octet o12+2

ProSe identifiers

octet o12+3

octet o15

Geographical areas

octet o15+1

octet o13

Geographical areas (octet o15+1 to o13):

The geographical areas field is coded according to figure 5.4.2.15 and table 5.4.2.15.

If the length of ProSe applications requiring privacy contents field is bigger than indicated in figure 5.4.2.13, receiving entity shall ignore any superfluous octets located at the end of the ProSe applications requiring privacy contents.

Length of ProSe identifiers contents

octet o12+3

octet o12+4

ProSe identifier 1

octet (o12+5)*

octet o121*

ProSe identifier 2

octet (o121+1)*

octet o122*

…

octet (o122+1)*

octet o123*

ProSe identifier n

octet (o123+1)*

octet o124*

= octet o15*

NOTE: Further definition of the format of OS App ID is beyond the scope of this specification.

Length of geographical areas contents

octet o15+1

octet o15+2

Geographical area 1

octet (o15+3)*

octet o23*

Geographical area 2

octet (o23+1)*

octet o24*

…

octet (o24+1)*

octet o25*

Geographical area n

octet (o25+1)*

octet o13*

Length of 5G ProSe direct communication in NR-PC5 contents

octet o4+1

octet o4+2

0

Spare

PINFMRI

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

octet o4+3

ProSe identifier to ProSe NR frequency mapping rules

octet (o4+4)*

octet o45*

ProSe identifier to destination layer-2 ID for broadcast mapping rules

octet o108

(see NOTE)

octet o46

Groupcast parameters

octet o46+1

octet o47

ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rules

octet o47+1

octet o48

ProSe identifier to PC5 QoS parameters mapping rules

octet o48+1

octet o49

AS configuration

octet o49+1

octet o50

NR-PC5 unicast security policies

octet (o50+1) =

octet o93

octet o84

ProSe identifier to default mode of communication mapping rules

octet (o84+1)

octet o85 = octet l

ProSe identifier to ProSe NR frequency mapping rules (octet o4+4 to o45):

The ProSe identifier to ProSe NR frequency mapping rules field is coded according to figure 5.4.2.17 and table 5.4.2.17.

ProSe identifier to destination layer-2 ID for broadcast mapping rules (octet o108 to o46):

The ProSe identifier to destination layer-2 ID for broadcast mapping rules field is coded according to figure 5.4.2.22 and table 5.4.2.22.

Groupcast parameters (octet o46+1 to o47):

The groupcast parameters field is coded according to figure 5.4.2.24 and table 5.4.2.24.

ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rules (octet o47+1 to o48):

The ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rules field is coded according to figure 5.4.2.26 and table 5.4.2.26.

ProSe identifier to PC5 QoS parameters mapping rules (octet o48+1 to o49):

The ProSe identifier to PC5 QoS parameters mapping rules field is coded according to figure 5.4.2.28 and table 5.4.2.28.

AS configuration (octet o49+1 to o50):

The AS configuration field is coded according to figure 5.4.2.30 and table 5.4.2.30.

NR-PC5 unicast security policies (octet o93 to o84):

The NR-PC5 unicast security policies field is coded according to figure 5.4.2.34 and table 5.4.2.34.

ProSe identifier to default mode of communication mapping rules (o84+1 to l):

The ProSe identifier to default mode of communication mapping rules is coded according to figure 5.4.2.37 and table 5.4.2.37.

If the length of 5G ProSe direct communication over PC5 in NR-PC5 contents field is bigger than indicated in figure 5.4.2.16, receiving entity shall ignore any superfluous octets located at the end of the 5G ProSe direct communication over PC5 in NR-PC5 contents.

Length of ProSe identifier to ProSe NR frequency mapping rules contents

octet o4+4

octet o4+5

ProSe identifier to ProSe NR frequency mapping rule 1

octet (o4+6)*

octet o51*

ProSe identifier to ProSe NR frequency mapping rule 2

octet (o51+1)*

octet o52*

…

octet (o52+1)*

octet o53*

ProSe identifier to ProSe NR frequency mapping rule n

octet (o53+1)*

octet o45*

Length of ProSe identifier to ProSe NR frequency mapping rule contents

octet o51+1

octet o51+2

ProSe identifiers

octet o51+3

octet o54

ProSe NR frequencies with geographical areas list

octet o54+1

octet o52

ProSe NR frequencies with geographical areas list (octet o54+1 to o52):

The ProSe NR frequencies with geographical areas list field is coded according to figure 5.4.2.19 and table 5.4.2.19.

If the length of ProSe identifier to ProSe NR frequency mapping rule contents field is bigger than indicated in figure 5.4.2.18, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to ProSe NR frequency mapping rule contents.

Length of ProSe NR frequencies with geographical areas list contents

octet o54+1

octet o54+2

ProSe NR frequencies with geographical areas info 1

octet (o54+3)*

octet o55*

ProSe NR frequencies with geographical areas info 2

octet (o55+1)*

octet o56*

…

octet (o56+1)*

octet o57*

ProSe NR frequencies with geographical areas info n

octet (o57+1)*

octet o52*

Length of ProSe NR frequencies with geographical areas info contents

octet o55+1

octet o55+2

ProSe NR frequencies

octet o55+3

octet o58

Geographical areas

octet o58+1

octet o56

Geographical areas (octet o58+1 to o56):

The geographical areas field is coded according to figure 5.4.2.15 and table 5.4.2.15.

If the length of ProSe NR frequencies with geographical areas info contents field is bigger than indicated in figure 5.4.2.20, receiving entity shall ignore any superfluous octets located at the end of the ProSe NR frequencies with geographical areas info contents.

Length of ProSe NR frequencies contents

octet o55+3

octet o55+4

ProSe NR frequency 1

octet (o55+5)*

octet (o55+7)*

ProSe NR frequency 2

octet (o55+8)*

octet (o55+10)*

…

octet (o55+11)*

octet (o55+4+(n-1)*3)*

ProSe NR frequency n

octet (o55+5+(n-1)*3)*

octet (o55+4+n*3)* = octet o58*

Length of ProSe identifier to destination layer-2 ID for broadcast mapping rules contents

octet o108

octet o108+1

ProSe identifier to destination layer-2 ID for broadcast mapping rule 1

octet (o108+2)*

octet o59*

ProSe identifier to destination layer-2 ID for broadcast mapping rule 2

octet (o59+1)*

octet o60*

…

octet (o60+1)*

octet o61*

ProSe identifier to destination layer-2 ID for broadcast mapping rule n

octet (o61+1)*

octet o46*

Length of ProSe identifier to destination layer-2 ID for broadcast mapping rule contents

octet o59+1

octet o59+2

ProSe identifiers

octet o59+3

octet o62

Destination layer-2 ID for broadcast

octet o62+1

octet (o62+3)

= octet o60

Destination layer-2 ID for broadcast (octet o62+1 to o60):

The destination layer-2 ID for broadcast field is a binary coded layer-2 identifier.

If the length of ProSe identifier to destination layer-2 ID for broadcast mapping rule contents field is bigger than indicated in figure 5.4.2.23, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to destination layer-2 ID for broadcast mapping rule contents.

Length of groupcast parameters contents

octet o46+1

octet o46+2

Application layer group info 1

octet (o46+3)*

octet o63*

Application layer group info 2

octet (o63+1)*

octet o64*

…

octet (o64+1)*

octet o65*

Application layer group info n

octet (o65+1)*

octet 47*

Length of application layer group info contents

octet o63+1

octet o63+2

Application layer group identifier

octet o63+3

octet o163

IPv4

IPv4AI

IPv6

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

octet o163+1

ProSe layer-2 group identifier

octet o163+2

octet o163+4

ProSe group IP multicast address

octet o163+5

octet o164

IPv4 address

octet (o164+1)*

octet (o164+4)* = octet 64*

IPv4 (octet o163+1 bit 8):

Bit

8

0 IPv4 is not authorized

1 IPv4 is authorized

IPv4 address indicator (IPv4AI) (octet o163+1 bit 7):

Bit

7

0 IPv4 address is absent

1 IPv4 address is present

IPv6 (octet o163+1 bit 6):

Bit

6

0 IPv6 is not authorized

1 IPv6 is authorized

ProSe layer-2 group identifier (octet o163+2 to o163+4):

The ProSe layer-2 group identifier field is a binary coded layer-2 identifier.

ProSe group IP multicast address (octet o163+5 to o164):

The ProSe group IP multicast address field contains the IP multicast address for the group. If IPv4 field is set to "IPv4 is authorized" and IPv6 field is set to "IPv6 is not authorized", the ProSe group IP multicast address contains an IPv4 address. If IPv6 field is set to "IPv6 is authorized" and IPv4 field is set to "IPv4 is not authorized", the ProSe group IP multicast address contains an IPv6 address. If IPv4 field is set to "IPv4 is authorized" and IPv6 field is set to "IPv6 is authorized", the ProSe group IP multicast address contains an IPv4 address followed by an IPv6 address

IPv4 address (octet o164+1 to o164+4):

The IPv4 address field contains an IPv4 address as the source address for a specific group configured to operate using IPv4.

Length of ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rules contents

octet o47+1

octet o47+2

ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rule 1

octet (o47+3)*

octet o66*

ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rule 2

octet (o66+1)*

octet o67*

…

octet (o67+1)*

octet o68*

ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rule n

octet (o68+1)*

octet o48*

Length of ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rule contents

octet o66+1

octet o66+2

ProSe identifiers

octet o66+3

octet o81

Destination layer-2 ID for unicast initial signalling

octet o81+1

octet (o81+3)

= octet o67

Destination layer-2 ID for unicast initial signalling (octet o81+1 to o67):

The destination layer-2 ID for unicast initial signalling field is a binary coded layer-2 identifier.

If the length of ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rule contents field is bigger than indicated in figure 5.4.2.27, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to destination layer-2 ID for unicast initial signalling mapping rule contents.

Length of ProSe identifier to PC5 QoS parameters mapping rules contents

octet o48+1

octet o48+2

ProSe identifier to PC5 QoS parameters mapping rule 1

octet (o48+3)*

octet o70*

ProSe identifier to PC5 QoS parameters mapping rule 2

octet (o70+1)*

octet o71*

…

octet (o71+1)*

octet o72*

ProSe identifier to PC5 QoS parameters mapping rule n

octet (o72+1)*

octet o49*

Length of ProSe identifier to PC5 QoS parameters mapping rule contents

octet o70+1

octet o70+2

ProSe identifiers

octet o70+3

octet o74

GFBRI

MFBRI

PLAMBRI

RI

0

Spare

0

Spare

0

Spare

0

Spare

octet o74+1

PQI

octet o74+2

Guaranteed flow bit rate

octet (o74+3)*

octet (o74+5)*

Maximum flow bit rate

octet o94* (see NOTE)

octet (o94+2)*

Per-link aggregate maximum bit rate

octet o95* (see NOTE)

octet (o95+2)*

Range

octet o96* (see NOTE)

octet (o96+1)* = octet o71*

Guaranteed flow bit rate indicator (GFBRI) (octet o74+1 bit 8):

The GFBRI bit indicates presence of guaranteed flow bit rate field.

Bit

8

0 Guaranteed flow bit rate field is absent

1 Guaranteed flow bit rate field is present

Maximum flow bit rate indicator (MFBRI) (octet o74+1 bit 7):

The MFBRI bit indicates presence of maximum flow bit rate field.

Bit

7

0 Maximum flow bit rate field is absent

1 Maximum flow bit rate field is present

Per-link aggregate maximum bit rate indicator (PLAMBRI) (octet o74+1 bit 6):

The PLAMBRI bit indicates presence of per-link aggregate maximum bit rate field.

Bit

6

0 Per-link aggregate maximum bit rate field is absent

1 Per-link aggregate maximum bit rate field is present

Range indicator (RI) (octet o74+1 bit 5):

The RI bit indicates presence of range field.

Bit

5

0 Range field is absent

1 Range field is present

PQI (octet o74+2):

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

to Spare

0 0 0 1 0 1 0 0

0 0 0 1 0 1 0 1 PQI 21

0 0 0 1 0 1 1 0 PQI 22

0 0 0 1 0 1 1 1 PQI 23

0 0 0 1 1 0 0 0 PQI 24

0 0 0 1 1 0 0 1 PQI 25

0 0 0 1 1 0 1 0 PQI 26

0 0 0 1 1 0 1 1

to Spare

0 0 1 1 0 1 1 0

0 0 1 1 0 1 1 1 PQI 55

0 0 1 1 1 0 0 0 PQI 56

0 0 1 1 1 0 0 1 PQI 57

0 0 1 1 1 0 1 0 PQI 58

0 0 1 1 1 0 1 1 PQI 59

0 0 1 1 1 1 0 0 PQI 60

0 0 1 1 1 1 0 1 PQI 61

0 0 1 1 1 1 1 0

to Spare

0 1 0 1 1 0 0 1

0 1 0 1 1 0 1 0 PQI 90

0 1 0 1 1 0 1 1 PQI 91

0 1 0 1 1 1 0 0 PQI 92

0 1 0 1 1 1 0 1 PQI 93

0 1 0 1 1 1 1 0

to Spare

0 1 1 1 1 1 1 1

1 0 0 0 0 0 0 0

to Operator-specific PQIs

1 1 1 1 1 1 1 0

1 1 1 1 1 1 1 1 Reserved

If the UE receives a PQI value (excluding the reserved PQI values) that it does not understand, the UE shall choose a PQI value from the set of PQI values defined in this version of the protocol (see 3GPP TS 23.304 [2]) and associated with:

– GBR resource type, if the ProSe identifier to PC5 QoS parameters mapping rule includes the guaranteed flow bit rate field; and

– non-GBR resource type, if the ProSe identifier to PC5 QoS parameters mapping rule does not include the guaranteed flow bit rate field.

The UE shall use this chosen PQI value for internal operations only. The UE shall use the received PQI value in subsequent 5G ProSe direct communication over PC5 signalling procedures.

Guaranteed flow bit rate (octet o74+3 to o74+5):

The guaranteed flow bit rate field indicates guaranteed flow bit rate for both sending and receiving and contains one octet indicating the unit of the guaranteed flow bit rate followed by two octets containing the value of the guaranteed flow bit rate.

Unit of the guaranteed flow bit rate:

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 value is not used

0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Value of the guaranteed flow bit rate is binary coded value of the guaranteed flow bit rate in units defined by the unit of the guaranteed flow bit rate.

Maximum flow bit rate (octet o94 to o94+2):

The maximum flow bit rate field indicates maximum flow bit rate for both sending and receiving and contains one octet indicating the unit of the maximum flow bit rate followed by two octets containing the value of the maximum flow bit rate.

Unit of the maximum flow bit rate:

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 value is not used

0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Value of the maximum flow bit rate is binary coded value of the maximum flow bit rate in units defined by the unit of the maximum flow bit rate.

Per-link aggregate maximum bit rate (octet o95 to o95+2):

The per-link aggregate maximum bit rate field indicates per-link aggregate maximum bit rate for both sending and receiving and contains one octet indicating the unit of the per-link aggregate maximum bit rate followed by two octets containing the value of the per-link aggregate maximum bit rate.

Unit of the per-link aggregate maximum bit rate:

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 value is not used

0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Value of the per-link aggregate maximum bit rate is binary coded value of the per-link aggregate maximum bit rate in units defined by the unit of the per-link aggregate maximum bit rate.

Range (octet o96 to o71):

The range field indicates a binary encoded value of the range in meters.

If the length of ProSe identifier to PC5 QoS parameters mapping rule contents field is bigger than indicated in figure 5.4.2.28, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to PC5 QoS parameters mapping rule contents.

Length of AS configuration contents

octet o49+1

octet o49+2

SLRB mapping rules

octet o49+3

octet o50

Length of SLRB mapping rules contents

octet o49+3

octet o49+4

SLRB mapping rule 1

octet (o49+5)*

octet o75*

SLRB mapping rule 2

octet (o75+1)*

octet o76*

…

octet (o76+1)*

octet o77*

SLRB mapping rule n

octet (o77+1)*

octet o50*

Length of SLRB mapping rule contents

octet o75+1

octet o75+2

PC5 QoS profile

octet o75+3

octet o78

Length of SLRB

octet o78+1

octet o78+2

SLRB

octet o78+3

octet o76

SLRB (o78+3 to o76):

SLRB is defined as SL-PreconfigurationNR in clause 9.3 of 3GPP TS 38.331 [7].

If the length of SLRB mapping rule contents field is bigger than indicated in figure 5.4.2.32, receiving entity shall ignore any superfluous octets located at the end of the SLRB mapping rule contents.

Length of PC5 QoS profile contents

octet o75+3

octet o75+4

GFBRI

MFBRI

PLAMBRI

RI

PLOI

AWI

MDBVI

0

Spare

octet o75+5

PQI

octet o75+6

Guaranteed flow bit rate

octet (o75+7)*

octet (o75+9)*

Maximum flow bit rate

octet o97* (see NOTE)

octet (o97+2)*

Per-link aggregate maximum bit rate

octet o98* (see NOTE)

octet (o98+2)*

Range

octet o99* (see NOTE)

octet (o99+1)*

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

Priority level

octet o100*

(see NOTE)

Averaging window

octet o101*

(see NOTE)

octet (o101+1)*

Maximum data burst volume

octet o102*

(see NOTE)

octet (o102+1)* = octet o78*

Maximum flow bit rate indicator (MFBRI) (o75+5 bit 7):

The MFBRI bit indicates presence of maximum flow bit rate field.

Bit

7

0 Maximum flow bit rate field is absent

1 Maximum flow bit rate field is present

Per-link aggregate maximum bit rate indicator (PLAMBRI) (o75+5 bit 6):

The PLAMBRI bit indicates presence of per-link aggregate maximum bit rate field.

Bit

6

0 Per-link aggregate maximum bit rate field is absent

1 Per-link aggregate maximum bit rate field is present

Range indicator (RI) (o75+5 bit 5):

The RI bit indicates presence of range field.

Bit

5

0 Range field is absent

1 Range field is present

Priority level octet indicator (OPLI) (o75+5 bit 4):

The OPLI bit indicates presence of the octet of the priority level field.

Bit

4

0 The octet of the priority level is absent

1 The octet of the priority level is present

Averaging window indicator (AWI) (o75+5 bit 3):

The AWI bit indicates presence of averaging window field.

Bit

3

0 Averaging window field is absent

1 Averaging window field is present

Maximum data burst volume indicator (MDBVI) (o75+5 bit 2):

The MDBVI bit indicates presence of maximum data burst volume field.

Bit

2

0 Maximum data burst volume field is absent

1 Maximum data burst volume field is present

PQI (o75+6):

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

to Spare

0 0 0 1 0 1 0 0

0 0 0 1 0 1 0 1 PQI 21

0 0 0 1 0 1 1 0 PQI 22

0 0 0 1 0 1 1 1 PQI 23

0 0 0 1 1 0 0 0 PQI 24

0 0 0 1 1 0 0 1 PQI 25

0 0 0 1 1 0 1 0 PQI 26

0 0 0 1 1 0 1 1

to Spare

0 0 1 1 0 1 1 0

0 0 1 1 0 1 1 1 PQI 55

0 0 1 1 1 0 0 0 PQI 56

0 0 1 1 1 0 0 1 PQI 57

0 0 1 1 1 0 1 0 PQI 58

0 0 1 1 1 0 1 1 PQI 59

0 0 1 1 1 1 0 0 PQI 60

0 0 1 1 1 1 0 1 PQI 61

0 0 1 1 1 1 1 0

to Spare

0 1 0 1 1 0 0 1

0 1 0 1 1 0 1 0 PQI 90

0 1 0 1 1 0 1 1 PQI 91

0 1 0 1 1 1 0 0 PQI 92

0 1 0 1 1 1 0 1 PQI 93

0 1 0 1 1 1 1 0

to Spare

0 1 1 1 1 1 1 1

1 0 0 0 0 0 0 0

to Operator-specific PQIs

1 1 1 1 1 1 1 0

1 1 1 1 1 1 1 1 Reserved

If the UE receives a PQI value (excluding the reserved PQI values) that it does not understand, the UE shall choose a PQI value from the set of PQI values defined in this version of the protocol (see 3GPP TS 23.304 [2]) and associated with:

– GBR resource type, if the PC5 QoS profile includes the guaranteed flow bit rate field; and

– non-GBR resource type, if the PC5 QoS profile does not include the guaranteed flow bit rate field.

The UE shall use this chosen PQI value for internal operations only. The UE shall use the received PQI value in subsequent 5G ProSe direct communication over PC5 signalling procedures.

Guaranteed flow bit rate octet (o75+7 to o75+9):

The guaranteed flow bit rate field indicates guaranteed flow bit rate for both sending and receiving and contains one octet indicating the unit of the guaranteed flow bit rate followed by two octets containing the value of the guaranteed flow bit rate.

Unit of the guaranteed flow bit rate:

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 value is not used

0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Value of the guaranteed flow bit rate is binary coded value of the guaranteed flow bit rate in units defined by the unit of the guaranteed flow bit rate.

Maximum flow bit rate (o97 to o97+2):

The maximum flow bit rate field indicates maximum flow bit rate for both sending and receiving and contains one octet indicating the unit of the maximum flow bit rate followed by two octets containing the value of the maximum flow bit rate.

Unit of the maximum flow bit rate:

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 value is not used

0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Value of the maximum flow bit rate is binary coded value of the maximum flow bit rate in units defined by the unit of the maximum flow bit rate.

Per-link aggregate maximum bit rate (o98 to o98+2):

The per-link aggregate maximum bit rate field indicates per-link aggregate maximum bit rate for both sending and receiving and contains one octet indicating the unit of the per-link aggregate maximum bit rate followed by two octets containing the value of the per-link aggregate maximum bit rate.

Unit of the per-link aggregate maximum bit rate:

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 value is not used

0 0 0 0 0 0 0 1 value is incremented in multiples of 1 Kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 4 Kbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 16 Kbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 64 Kbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 256 Kbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 256 Gbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 1 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 4 Tbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 16 Tbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 1 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 1 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 1 0 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 1 0 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Value of the per-link aggregate maximum bit rate is binary coded value of the per-link aggregate maximum bit rate in units defined by the unit of the per-link aggregate maximum bit rate.

Range (o99 to o99+1):

The range field indicates a binary encoded value of the range in meters.

Priority level (octet o100 bit 1 to 3):

The priority level field contains a ProSe per-packet priority value.

Bits

3 2 1

0 0 0 PPPP value 1

0 0 1 PPPP value 2

0 1 0 PPPP value 3

0 1 1 PPPP value 4

1 0 0 PPPP value 5

1 0 1 PPPP value 6

1 1 0 PPPP value 7

1 1 1 PPPP value 8

Averaging window (o101 to o101+1):

The averaging window field indicates a binary representation of the averaging window for both sending and receiving in milliseconds.

Maximum data burst volume (o102 to o78):

The maximum data burst volume field indicates a binary representation of the maximum data burst volume for both sending and receiving in octets.

If the length of PC5 QoS profile contents field is bigger than indicated in figure 5.4.2.33, receiving entity shall ignore any superfluous octets located at the end of the PC5 QoS profile contents.

Length of NR-PC5 unicast security policies contents

octet o93

octet o93+1

NR-PC5 unicast security policy 1

octet (o93+2)*

octet o86*

NR-PC5 unicast security policy 2

octet (o86+1)*

octet o87*

…

octet (o87+1)*

octet o88*

NR-PC5 unicast security policy n

octet (o88+1)*

octet o84*

Length of NR-PC5 unicast security policy contents

octet o86+1

octet o86+2

ProSe identifiers

octet o86+3

octet o89

Security policy

octet o89+1

octet o89+2

Geographical areas

octet o89+3

octet o87

Security policy (o89+1 to o89+2):

The security policy field is coded according to figure 5.4.2.36 and table 5.4.2.36.

Geographical areas (o89+3 to o87):

The geographical areas field is coded according to figure 5.4.2.15 and table 5.4.2.15.

If the length of NR-PC5 unicast security policy contents field is bigger than indicated in figure 5.4.2.35, the receiving entity shall ignore any superfluous octets located at the end of the NR-PC5 unicast security policy contents.

0

spare

Signalling ciphering policy

0

spare

Signalling integrity protection policy

octet o89+1

0

spare

User plane ciphering policy

0

spare

User plane integrity protection policy

octet o89+2

Bits

3

2

1

0

0

0

Signalling integrity protection not needed

0

0

1

Signalling integrity protection preferred

0

1

0

Signalling integrity protection required

0

1

1

to Spare

1

1

0

1

1

1

Reserved

If the UE receives a signalling integrity protection policy value that the UE does not understand, the UE shall interpret the value as 010 "Signalling integrity protection required".

Signalling ciphering policy (octet o89+1 bit 5 to 7):

Bits

7

6

5

0

0

0

Signalling ciphering not needed

0

0

1

Signalling ciphering preferred

0

1

0

Signalling ciphering required

0

1

1

to Spare

1

1

0

1

1

1

Reserved

If the UE receives a signalling ciphering policy value that the UE does not understand, the UE shall interpret the value as 010 "Signalling ciphering required".

Bit 4 and 8 of octet o89+1 are spare and shall be coded as zero.

User plane integrity protection policy (octet o89+2 bit 1 to 3):

Bits

3

2

1

0

0

0

User plane integrity protection not needed

0

0

1

User plane integrity protection preferred

0

1

0

User plane integrity protection required

0

1

1

to Spare

1

1

0

1

1

1

Reserved

If the UE receives a user plane integrity protection policy value that the UE does not understand, the UE shall interpret the value as 010 "User plane integrity protection required".

User plane ciphering policy (octet o89+2 bit 5 to 7):

Bits

7

6

5

0

0

0

User plane ciphering not needed

0

0

1

User plane ciphering preferred

0

1

0

User plane ciphering required

0

1

1

to Spare

1

1

0

1

1

1

Reserved

If the UE receives a user plane ciphering policy value that the UE does not understand, the UE shall interpret the value as 010 "User plane ciphering required".

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

Length of ProSe identifier to default mode of communication mapping rules contents

octet o84+1

octet o84+2

ProSe identifier to default mode of communication mapping rule 1

octet (o84+3)*

octet o90*

ProSe identifier to default mode of communication mapping rule 2

octet (o90+1)*

octet o91*

…

octet (o91+1)*

octet o92*

ProSe identifier to default mode of communication mapping rule n

octet (o92+1)*

octet o85*

Length of ProSe identifier to default mode of communication mapping rule contents

octet o90+1

octet o90+2

ProSe identifiers

octet o90+3

octet o91-1

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

DMC

octet o91

Default mode of communication (DMC) (octet o91 bit 1 to 2):

The DMC field indicates the default mode of communication.

Bits

2 1

0 0 unicast

0 1 groupcast

1 0 broadcast

1 1 spare

If the DMC field is set to a spare value, the receiving entity shall ignore the ProSe application identifier to default mode of communication mapping rule.

If the length of ProSe identifier to default mode of communication mapping rule contents field is bigger than indicated in figure 5.4.2.37, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to default mode of communication mapping rule contents.

Length of ProSe application to path preference mapping rules contents

octet o5+1

octet o5+2

ProSe application to path preference mapping rule 1

octet (o5+3)*

octet o150*

ProSe application to path preference mapping rule 2

octet (o150+1)*

octet o151*

…

octet (o151+1)*

octet o152*

ProSe application to path preference mapping rule n

octet (o152+1)*

octet l*

NOTE: The ProSe application to path preference mapping rule field is prioritized in decreasing order according to the local configuration of the network. The ProSe application to path preference mapping rule field with the service indication field set to value 1 "For all ProSe services", if present, should be the last one of the ProSe application to path preference mapping rules.

Length of ProSe application to path preference mapping rule contents

octet o150+1

octet o150+2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

SI

PP

octet o151

ProSe identifiers

octet o152*

octet o18*

Path preference (PP) (octet o151 bit 1 to 2):

The PP field indicates the path preference.

Bits

2 1

0 0 No preference

0 1 PC5 preferred

1 0 Uu preferred

1 1 spare

If the PP field is set to a spare value, the receiving entity shall interpret as "00".

Service indication (SI) (octet o151 bit 3):

The SI field indicates whether the path preference is for all ProSe services or not.

Bits

3

1 For all ProSe services

0 Not for all ProSe services

If the length of ProSe application to path preference mapping rule contents field is bigger than indicated in figure 5.4.2.40, receiving entity shall ignore any superfluous octets located at the end of the ProSe application to path preference mapping rule contents.

Length of ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rules contents

octet o10+1

octet o10+2

ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rule 1

octet (o10+3)*

octet o103*

ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rule 2

octet (o103+1)*

octet o104*

…

octet (o104+1)*

octet o105*

ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rule n

octet (o105+1)*

octet l*

Length of ProSe identifiers to NR Tx profile for broadcast and groupcast mapping rule contents

octet o103+1

octet o103+2

ProSe identifiers

octet o103+3

octet o1030

NR Tx profile

octet o1030+1=o104

NR Tx profile:

The NR Tx profile field is coded as SL-TxProfile-r17 in clause 9.3 of 3GPP TS 38.331 [7].

0

0

0

PAI

ProSeP info type = {UE policies for 5G ProSe UE-to-network relay UE}

octet k

Spare

Length of ProSeP info contents

octet k+1

octet k+2

Validity timer

octet k+3

octet k+7

Served by NG-RAN

octet k+8

octet o1

Not served by NG-RAN

octet o1+1

octet o2

Default destination layer-2 IDs for sending the discovery signalling for announcement and additional information and for receiving the discovery signalling for solicitation

octet o2+1

octet o3

User info ID for discovery

octet o3+1

octet o3+6

RSC info list

octet o3+7

octet o4

5QI to PC5 QoS parameters mapping rules

octet o4+1

octet o5

ProSe identifier to ProSe application server address mapping rules

octet o5+1

octet o6

5G PKMF address information

octet (o6+1)*

octet l-2

Privacy timer

octet l-1

octet l

PKMF address indication (PAI) (bit 5 of octet k)

The PAI indicates whether the 5G PKMF address information is included in the IE or not

Bit

5

0 5G PKMF address information is not included

1 5G PKMF address information is included

Length of ProSeP info contents (octets k+1 to k+2) indicates the length of ProSeP info contents.

Validity timer (octet k+3 to k+7):

The validity timer field provides the expiration time of validity of the UE policies for 5G ProSe UE-to-network relay UE. The validity timer field is a binary coded representation of a UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

Served by NG-RAN (octet k+8 to o1):

The served by NG-RAN field is coded according to figure 5.5.2.2 and table 5.5.2.2, and contains configuration parameters for 5G ProSe UE-to-network relay UE when the UE is served by NG-RAN.

Not served by NG-RAN (octet o1+1 to o2):

The not served by NG-RAN field is coded according to figure 5.5.2.5 and table 5.5.2.5, and contains configuration parameters for 5G ProSe UE-to-network relay discovery and communication when the UE is not served by NG-RAN.

Default destination layer-2 IDs for sending the discovery signalling for announcement and additional information and for receiving the discovery signalling for solicitation (octet o2+1 to o3):

The default destination layer-2 IDs for sending the discovery signalling for announcement and additional information and for receiving the discovery signalling for solicitation is coded according to figure 5.5.2.11b and table 5.5.2.11b and contains a list of the default destination layer-2 IDs for the initial UE-to-network relay discovery signalling.

User info ID for discovery (octet o3+1 to o3+6):

The value of the User info ID parameter is a 48-bit long bit string. The format of the User info ID parameter is out of scope of this specification.

RSC info list (octet o3+7 to o4):

The RSC info list field is coded according to figure 5.5.2.12 and table 5.5.2.12 and contains the RSCs related paramters.

5QI to PC5 QoS parameters mapping rules (octet o4+1 to o5):

The 5QI to PC5 QoS parameters mapping rules field is coded according to figure 5.5.2.17 and table 5.5.2.17 and contains the 5QI to PC5 QoS parameters mapping rules.

ProSe identifier to ProSe application server address mapping rules (octet o5+1 to o6):

The ProSe identifier to ProSe application server address mapping rules field is coded according to figure 5.5.2.19 and table 5.5.2.19 and contains the ProSe identifier to ProSe application server address mapping rules.

Privacy timer (octet l-1 to l):

The privacy timer field contains binary encoded duration, in units of seconds, after which the UE shall change the source layer-2 ID self-assigned by the UE while performing transmission of 5G ProSe direct communication.

If the length of ProSeP info contents field is bigger than indicated in figure 5.5.2.1, receiving entity shall ignore any superfluous octets located at the end of the ProSeP info contents.

5G PKMF address information (octet o6+1 to l-2)

5G PKMF address information contains the IPv4 address(es), IPv6 address(es) and/or FQDN of the 5G PKMF and is coded according to figure 5.5.2.21, figure 5.5.2.22, figure 5.5.2.23 and table 5.5.2.21. At least one of the address parameters (FQDN, IPv4 address list or IPv6 address list) shall be included.

Length of served by NG-RAN contents

octet k+8

octet k+9

Authorized PLMN list for layer-3 relay UE

octet (k+10)*

octet o50*

Authorized PLMN list for layer-2 relay UE

octet (o50+1)*

octet o1*

Authorized PLMN list for layer-2 relay UE:

The authorized PLMN list for layer-2 relay UE field is coded according to figure 5.5.2.3 and table 5.5.2.3.

Authorized PLMN 1

octet (k+12)*

octet (k+14)*

Authorized PLMN 2

octet (k+15)*

octet (k+17)*

…

octet (k+18)*

octet (o50-3)*

Authorized PLMN n

octet (o50-2)*

octet o50*

MCC digit 2

MCC digit 1

octet k+15

MNC digit 3

MCC digit 3

octet k+16

MNC digit 2

MNC digit 1

octet k+17

Mobile network code (MNC) (octet k+16 bit 5 to 8, octet k+17):

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

Length of not served by NG-RAN contents

octet o1+1

octet o1+2

NR radio parameters per geographical area list for UE-to-network relay discovery

octet o1+3

octet o51

NR radio parameters per geographical area list for UE-to-network relay communication

octet o51+1

octet o10

Default PC5 DRX configuration for UE-to-network relay discovery

octet o10+1

octet o2

NR radio parameters per geographical area list for UE-to-network relay communication (octet o51+1 to o2):

The NR radio parameters per geographical area list for UE-to-network relay communication field is coded according to figure 5.5.2.7 and table 5.5.2.7.

Default PC5 DRX configuration for UE-to-network relay discovery (octet o10+1 to o2):

The default PC5 DRX configuration for UE-to-network relay discovery field is coded according to figure 5.5.2.11a and table 5.5.2.11a.

If the length of not served by NG-RAN contents field is bigger than indicated in figure 5.5.2.5, receiving entity shall ignore any superfluous octets located at the end of the not served by NG-RAN contents.

Length of NR radio parameters per geographical area list for UE-to-network relay discovery contents

octet o1+3

octet o1+4

Radio parameters per geographical area info 1

octet o1+5

octet o510

Radio parameters per geographical area info 2

octet (o510+1)*

octet o511*

…

octet (o511+1)*

octet o512*

Radio parameters per geographical area info n

octet (o512+1)*

octet o51*

Length of NR radio parameters per geographical area list for UE-to-network relay communication contents

octet o51+1

octet o51+2

Radio parameters per geographical area info 1

octet o51+3

octet o513

Radio parameters per geographical area info 2

octet (o513+1)*

octet o514*

…

octet (o514+1)*

octet o515*

Radio parameters per geographical area info n

octet (o515+1)*

octet o10*

Length of radio parameters per geographical area contents

octet o510+1

octet o510+2

Geographical area

octet o510+3

octet o5100

Radio parameters

octet o5100+1

octet o511-1

MI

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

octet o511

Radio parameters (octet o5100+1 to o511-1):

The radio parameters field is coded according to figure 5.3.2.11 and table 5.3.2.11, applicable in the geographical area indicated by the geographical area field when not served by NG-RAN.

Managed indicator (MI) (octet o511 bit 8):

The managed indicator indicates how the radio parameters indicated in the radio parameters field in the geographical area indicated by the geographical area field are managed.

Bit

8

0 Non-operator managed

1 Operator managed

If the length of radio parameters per geographical area contents field is bigger than indicated in figure 5.5.2.8, receiving entity shall ignore any superfluous octets located at the end of the radio parameters per geographical area contents.

Length of geographical area contents

octet o510+3

octet o510+4

Coordinate 1

octet (o510+5)*

octet (o510+10)*

Coordinate 2

octet (o510+11)*

octet (o510+16)*

…

octet (o510+17)*

octet (o510-2+6*n)*

Coordinate n

octet (o510-1+6*n)*

octet (o510+4+6*n)* = octet o5100*

Latitude

octet o510+11

octet o510+13

Longitude

octet o510+14

octet o510+17

Longitude (octet o510+14 to o510+17):

The longitude field is coded according to clause 6.1 of 3GPP TS 23.032 [6].

Length of radio parameters contents

octet o5100+1

octet o5100+2

Radio parameters contents

octet o5100+3

octet o511-1

Length of default PC5 DRX configuration for UE-to-network relay discovery contents

octet o10+1

octet o10+2

Default PC5 DRX configuration for UE-to-network relay discovery contents

octet o10+3

octet o2

Length of default destination layer-2 IDs for sending the discovery signalling for announcement and additional information and for receiving the discovery signalling for solicitation contents

octet o2+1

octet o2+2

Default destination layer-2 ID 1

octet o2+3

octet o2+5

Default destination layer-2 ID 2

octet (o2+6)*

octet (o2+8)*

…

octet (o2+9)*

octet (o3-3)*

Default destination layer-2 ID n

octet (o3-2)*

octet o3*

Length of RSC info list contents

octet o3+7

octet o3+8

RSC info 1

octet o3+9

octet o52

RSC info 2

octet (o52+1)*

octet (o53)*

…

octet (o53+1)*

octet (o54)*

RSC info n

octet (o54+1)*

octet o4*

Length of RSC info contents

octet o52+1

octet o52+2

RSC list

octet o52+3

octet o520

Security related parameters for discovery

octet o520+1

octet o511

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

CPSI

LI

octet o511+1

NR-PC5 UE-to-network relay security policies

octet (o511+2)

octet o530

PDU session parameters for layer-3 relay UE

octet (o530+1)*

octet o53*

Security related parameters for discovery (octet o520+1 to o511):

The security related parameters for discovery field contains the security related parameters for discovery used when the security procedure over control plane as specified in 3GPP TS 33.503 [13] is used and is coded according to figure 5.5.2.15 and table 5.5.2.15.

Layer indication (LI) (octet o511+1 bit 1 to 2):

Bits

2 1

0 1 Layer 3

1 0 Layer 2

The other values are reserved.

If LI is set to "Layer 3", the PDU session parameters for layer-3 relay UE is included in the RSC info, otherwise the PDU session parameters for layer-3 relay UE is not included.

Control plane security indication (CPSI) (octet o511+1 bit 3):

The control plane security indication field indicates whether to use the security procedure over control plane as specified in 3GPP TS 33.503 [13] or not.

Bit

3

0 security procedure over control plane is not used

1 security procedure over control plane is used

NR-PC5 UE-to-network relay security policies (octet o511+2 to o530):

The NR-PC5 UE-to-network relay security policies is coded as the NR-PC5 unicast security policies defined in figure 5.4.2.34 and table 5.4.2.34.

PDU session parameters for layer-3 relay UE (octet o530+1 to octet o53)

The PDU session parameters for layer-3 relay UE field is coded according to figure 5.5.2.16 and table 5.5.2.16.

Length of RSC list contents

octet o52+3

octet o52+4

RSC 1

octet o52+5

octet o52+7

RSC 2

octet (o52+8)*

octet (o52+10)*

…

octet (o52+11)*

octet (o520-3)*

RSC n

octet (o520-2)*

octet o520*

Security related parameters validity timer

octet o520+1

octet o520+5

Code-sending security parameters

octet (o520+6)*

octet o524*

Code-receiving security parameters

octet (o524+1)*

octet o511*

Spare

PDUCK

PDUIK

PDUSK

octet o520+6

DUSK

octet (o520+7)*

octet o521*

DUIK

octet (o521+1)*

octet o522*

DUCK

octet (o522+1)*

octet o523*

Encrypted bitmask

octet (o523+1)*

octet o524*

Spare

PDUCK

PDUIK

PDUSK

octet o524+1

DUSK

octet (o524+2)*

octet o525*

DUIK

octet (o525+1)*

octet o526*

DUCK

octet (o526+1)*

octet o527*

Encrypted bitmask

octet (o527+1)*

octet o511*

The security related parameters validity timer field provides the expiration time of validity of the security related parameters for discovery. The security related parameters validity timer field is a binary coded representation of a UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

Code-sending security parameters:

The code-sending security parameters field contains the security parameters needed by a sending UE to protect a 5G ProSe direct discovery message over PC5 interface as specified in 3GPP TS 33.503 [13].

Code-receiving security parameters

The code-receiving security parameters field contains the security parameters needed by a receiving UE to process a 5G ProSe direct discovery message over PC5 interface as specified in 3GPP TS 33.503 [13].

Presence of DUSK (PDUSK):

PDUSK indicates whether the DUSK field is present or not.

Bit

1

0 DUSK field is not included

1 DUSK field is included

Presence of DUIK (PDUIK):

PDUIK indicates whether the DUIK field is present or not.

Bit

2

0 DUIK field is not included

1 DUIK field is included

Presence of DUCK (PDUCK):

PDUCK indicates whether the DUCK field and the encrypted bitmask field are present or not.

Bot

3

0 DUCK and encrypted bitmask fields are not included

1 DUCK and encrypted bitmask fields are included

DUSK:

The DUSK field contains the value of the DUSK. The use of the DUSK is defined in 3GPP TS 33.503 [13].

DUIK:

The DUIK field contains the value of the DUIK. The use of the DUIK is defined in 3GPP TS 33.503 [13].

DUCK:

The DUCK field contains the value of the DUCK. The use of the DUCK is defined in 3GPP TS 33.503 [13].

Encrypted bitmask:

The encrypted bitmask field contains the value of the encrypted bitmask, which is a 184-bit bitmask which uses bit "1" to mark the positions of the bits for which the DUCK encryption is applied.

Length of PDU session parameters for layer-3 relay UE contents

octet o530+1

octet o530+2

Spare

PATP

PSSCM

PSNSSAI

PDNN

PDU session type

octet o530+3

DNN

octet (o530+4)*

octet o531*

S-NSSAI

octet (o531+1)*

octet (o53-1)*

Spare

Access type preference

SSC mode

octet o53*

Presence of DNN (PDNN) (bit 4 of octet o530+3)

PDNN indicates whether the DNN field is present or not.

Bit

4

0

DNN field is not included

1

DNN field is included

Presence of S-NSSAI (PSNSSAI) (bit 5 of octet o53+3)

PSNSSAI indicates whether the S-NSSAI field is present or not.

Bit

5

0

S-NSSAI field is not included

1

S-NSSAI field is included

Presence of SSC mode (PSSCM) (bit 6 of octet o530+3)

PSSCM indicates whether the SSC mode field is present or not.

Bit

6

0

SSC mode field is not included (NOTE)

1

SSC mode field is included

Presence of access type preference (PATP) (bit 7 of octet o530+3)

PATP indicates whether the access type preference mode field is present or not.

Bit

7

0

Access type preference field is not included (NOTE)

1

Access type preference field is included

DNN (octet o530+4 to o531):

The DNN field shall be encoded as a sequence of a one octet DNN length field and a DNN value field of a variable size. The DNN value contains an APN as defined in 3GPP TS 23.003 [10].

S-NSSAI (octet o531+1 to o53-1):

The S-NSSAI field shall be encoded as a sequence of a one octet S-NSSAI length field and an S-NSSAI value field of a variable size. The S-NSSAI value shall be encoded as the value part of the S-NSSAI information element defined in clause 9.11.2.8 of 3GPP TS 24.501 [4].

SSC mode (bits 3 to 1 of octet o53):

The SSC mode field shall be encoded as the value part of the SSC mode information element defined in clause 9.11.4.16 of 3GPP TS 24.501 [4].

Access type preference (bits 5 to 4 of octet o53):

The access type preference field shall be encoded as the value part of the access type information element defined in clause 9.11.2.1A of 3GPP TS 24.501 [4].

NOTE: Since SSC mode field and access type preference field are coded in the same octet, this octet is not included only when both PSSCM and PATP are set to 0.

Length of 5QI to PC5 QoS parameters mapping rules contents

octet o4+1

octet o4+2

5QI to PC5 QoS parameters mapping rule 1

octet o4+3

octet o55

5QI to PC5 QoS parameters mapping rule 2

octet (o55+1)*

octet o56*

…

octet (o56+1)*

octet o57*

5QI to PC5 QoS parameters mapping rule n

octet (o57+1)*

octet o5*

Length of 5QI to PC5 QoS parameters mapping rule contents

octet o55+1

octet o55+2

5QI

octet o55+3

PQI

octet o55+4

PDB adjustment factor

octet o55+5

RSC list

octet (o55+6)*

octet o56*

PQI (octet o55+4):

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

to Spare

0 0 0 1 0 1 0 0

0 0 0 1 0 1 0 1 PQI 21

0 0 0 1 0 1 1 0 PQI 22

0 0 0 1 0 1 1 1 PQI 23

0 0 0 1 1 0 0 0 PQI 24

0 0 0 1 1 0 0 1 PQI 25

0 0 0 1 1 0 1 0 PQI 26

0 0 0 1 1 0 1 1

to Spare

0 0 1 1 0 1 1 0

0 0 1 1 0 1 1 1 PQI 55

0 0 1 1 1 0 0 0 PQI 56

0 0 1 1 1 0 0 1 PQI 57

0 0 1 1 1 0 1 0 PQI 58

0 0 1 1 1 0 1 1 PQI 59

0 0 1 1 1 1 0 0 PQI 60

0 0 1 1 1 1 0 1 PQI 61

0 0 1 1 1 1 1 0

to Spare

0 1 0 1 1 0 0 1

0 1 0 1 1 0 1 0 PQI 90

0 1 0 1 1 0 1 1 PQI 91

0 1 0 1 1 1 0 0 PQI 92

0 1 0 1 1 1 0 1 PQI 93

0 1 0 1 1 1 1 0

to Spare

0 1 1 1 1 1 1 1

1 0 0 0 0 0 0 0

to Operator-specific PQIs

1 1 1 1 1 1 1 0

1 1 1 1 1 1 1 1 Reserved

PDB adjustment factor (octet o55+5):

The PDB adjustment factor field is a binary coded representation of a percentage of the standardized PDB identified by the PQI.

RSC list (octet o55+6 to o56):

The RSC list field is coded according to figure 5.5.2.14 and table 5.5.2.14.

Length of ProSe identifier to ProSe application server address mapping rules contents

octet o5+1

octet o5+2

ProSe identifier to ProSe application server address mapping rule 1

octet (o5+3)*

octet o150*

ProSe identifier to ProSe application server address mapping rule 2

octet (o150+1)*

octet o151*

…

octet (o151+1)*

octet o152*

ProSe identifier to ProSe application server address mapping rule n

octet (o152+1)*

octet (l-2)*

Length of ProSe identifier to ProSe application server address mapping rule contents

octet o150+1

octet o150+2

ProSe identifiers

octet o150+3

octet o1500

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

AT

octet o1500+1

ProSe application server address

octet o1500+2

octet l-2

Address type (AT) (octet o1500+1 bit 1 to 3):

The AT field indicates the ProSe application server address type.

Bits

3 2 1

0 0 1 IPv4

0 1 0 IPv6

0 1 1 FQDN

The other values are reserved.

If the AT indicates IPv4, then the ProSe application server address field contains an IPv4 address in 4 octets.

If the AT indicates IPv6, then the ProSe application server address field contains an IPv6 address in 16 octets.

If the AT indicates FQDN, then the ProSe application server address field contains a sequence of one octet FQDN length field and a FQDN value of variable size. The FQDN value field shall be encoded as defined in clause 28.3.2.1 in 3GPP TS 23.003 [10].

If the length of ProSe identifier to ProSe application server address mapping rule contents field is bigger than indicated in figure 5.5.2.19, receiving entity shall ignore any superfluous octets located at the end of the ProSe identifier to ProSe application server address mapping rule contents.

Length of 5G PKMF address information

octet o6+1

octet o6+2

0

Spare

octet o6+3

0

Spare

0

Spare

0

Spare

FQDN

IPv6add

IPv4add

IPv4 address list

octet (o6+4)*

octet o160*

IPv6 address list

octet (o160+1)*

octet (o161)*

FQDN

octet (o161+1)*

octet (l-2)*

Number of IPv4 addresses

octet o6+4

IPv4 address 1

octet o6+5

octet o6+8

IPv4 address 2

octet o6+9

octet o6+12

… …

IPv4 address N

octet o160-3

octet o160

Number of IPv6 addresses

octet o160+1

IPv6 address 1

octet o160+2

octet o160+17

IPv6 address 2

octet o160+18

octet o160+33

… …

IPv6 address N

octet o161-15

octet o161

IPv4 address list contains the IPv4 address(es) of the 5G PKMF and shall be encoded as defined in figure 5.5.2.20.

IPv6 address list (octet o160+1 to octet o161)

IPv6 address list contains the IPv6 address(es) of the 5G PKMF and shall be encoded as defined in figure 5.5.2.20.

FQDN (octet o161+1 to l)

FQDN field contains a sequence of one octet FQDN length field and a FQDN value of variable size. The FQDN value field shall be encoded as defined in clause 28.3.2.1 in 3GPP TS 23.003 [10].

NOTE 1: If multiple IPv4 addresses and/or IPv6 addresses are included, which one of these addresses is selected is implementation dependent.

NOTE 2: If the 5G PKMF supports the 5G PKMF Services with "https" URI scheme (i.e. use of TLS is mandatory), then the FQDN shall be used to construct the target URI.

0

0

NSII

PAI

ProSeP info type = {UE policies for 5G ProSe remote UE}

octet k

Spare

Length of ProSeP info contents

octet k+1

octet k+2

Validity timer

octet k+3

octet k+7

Served by NG-RAN

octet k+8

octet o1

Not served by NG-RAN

octet o1+1

octet o2

Default destination layer-2 IDs for sending the discovery signalling for solicitation and for receiving the discovery signalling for announcement and additional information

octet o2+1

octet o3

User info ID for discovery

octet o3+1

octet o3+6

RSC info list

octet o3+7

octet l

Privacy timer

octet l+1

octet l+2

N3IWF selection information for 5G ProSe layer-3 remote UE

octet (l+3)*

octet m*

5G PKMF address information

octet q*

(see NOTE)

octet p*

PKMF address indication (PAI) (bit 5 of octet k)

The PAI indicates whether the 5G PKMF address information is included in the IE or not

Bit

5

0 5G PKMF address information is not included

1 5G PKMF address information is included

N3IWF selection information indication (NSII) (bit 6 of octet k)

The NSII indicates whether the N3IWF selection information for 5G ProSe layer-3 remote UE is included in the IE or not

Bit

6

0 N3IWF selection information for 5G ProSe layer-3 remote UE is not included

1 N3IWF selection information for 5G ProSe layer-3 remote UE is included

Length of ProSeP info contents (octets k+1 to k+2) indicates the length of ProSeP info contents.

Validity timer (octet k+3 to k+7):

The validity timer field provides the expiration time of validity of the UE policies for 5G ProSe remote UE. The validity timer field is a binary coded representation of a UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).

Served by NG-RAN (octet k+8 to o1):

The served by NG-RAN field is coded according to figure 5.6.2.2 and table 5.6.2.2, and contains configuration parameters for 5G ProSe remote UE when the UE is served by NG-RAN.

Not served by NG-RAN (octet o1+1 to o2):

The not served by NG-RAN field is coded according to figure 5.6.2.5 and table 5.6.2.5, and contains configuration parameters for 5G ProSe UE-to-network relay discovery and communication when the UE is not served by NG-RAN.

Default destination layer-2 IDs for sending the discovery signalling for solicitation and for receiving the discovery signalling for announcement and additional information (octet o2+1 to o3):

The default destination layer-2 IDs for sending the discovery signalling for solicitation and for receiving the discovery signalling for announcement and additional information is coded according to figure 5.6.2.11b and table 5.6.2.11b and contains a list of the default destination layer-2 IDs for the initial UE-to-network relay discovery signalling.

User info ID for discovery (octet o3+1 to o3+6):

The value of the User info ID parameter is a 48-bit long bit string. The format of the User info ID parameter is out of scope of this specification.

RSC info list (octet o3+7 to l):

The RSC info list field is coded according to figure 5.6.2.12 and table 5.6.2.12 and contains the RSCs related paramters.

Privacy timer (octet m+1 to m+2):

The privacy timer field contains binary encoded duration, in units of seconds, after which the UE shall change the source layer-2 ID self-assigned by the UE while performing transmission of 5G ProSe direct communication.

N3IWF selection information for 5G ProSe layer-3 remote UE (octet l+3 to m):

The N3IWF selection information for 5G ProSe layer-3 remote UE field is coded according to figure 5.6.2.17 and table 5.6.2.17, and contains two parts: 1) N3IWF identifier configuration (either FQDN or IP address) for 5G ProSe layer-3 remote UE; 2) 5G ProSe layer-3 UE-to-network relay access node selection information.

5G PKMF address information (octet m+3 to p)

5G PKMF address information contains the IPv4 address(es), IPv6 address(es) and/or FQDN of the 5G PKMF and is coded according to figure 5.5.2.21, figure 5.5.2.22, figure 5.5.2.23 and table 5.5.2.21. At least one of the address parameters (FQDN, IPv4 address list or IPv6 address list) shall be included.

If the length of ProSeP info contents field is bigger than indicated in figure 5.6.2.1, receiving entity shall ignore any superfluous octets located at the end of the ProSeP info contents.

Length of served by NG-RAN contents

octet k+8

octet k+9

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

L3RI

octet (k+10)*

Authorized PLMN list for layer-2 remote UE

octet (k+11)*

octet o1*

Authorized PLMN list for layer-2 remote UE (octet k+11 to o1):

The authorized PLMN list for layer-2 remote UE field is coded according to figure 5.6.2.3 and table 5.6.2.3.

Length of authorized PLMN list contents

octet k+11

octet k+12

Authorized PLMN 1

octet (k+13)*

octet (k+15)*

Authorized PLMN 2

octet (k+16)*

octet (k+18)*

…

octet (k+19)*

octet (o50-3)*

Authorized PLMN n

octet (o50-2)*

octet o50*

MCC digit 2

MCC digit 1

octet k+16

MNC digit 3

MCC digit 3

octet k+17

MNC digit 2

MNC digit 1

octet k+18

Mobile network code (MNC) (octet k+17 bit 5 to 8, octet k+18):

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

Length of not served by NG-RAN contents

octet o1+1

octet o1+2

NR radio parameters per geographical area list for UE-to-network relay discovery

octet o1+3

octet o51

NR radio parameters per geographical area list for UE-to-network relay communication

octet o51+1

octet o10

Default PC5 DRX configuration for UE-to-network relay discovery

octet o10+1

octet o2

NR radio parameters per geographical area list for UE-to-network relay communication (octet o51+1 to o2):

The NR radio parameters per geographical area list for UE-to-network relay communication field is coded according to figure 5.6.2.7 and table 5.6.2.7.

Default PC5 DRX configuration for UE-to-network relay discovery (octet o10+1 to o2):

The default PC5 DRX configuration for UE-to-network relay discovery field is coded according to figure 5.6.2.11a and table 5.6.2.11a.

If the length of not served by NG-RAN contents field is bigger than indicated in figure 5.6.2.5, receiving entity shall ignore any superfluous octets located at the end of the not served by NG-RAN contents.

Length of NR radio parameters per geographical area list for UE-to-network relay discovery contents

octet o1+3

octet o1+4

Radio parameters per geographical area info 1

octet o1+5

octet o510

Radio parameters per geographical area info 2

octet (o510+1)*

octet o511*

…

octet (o511+1)*

octet o512*

Radio parameters per geographical area info n

octet (o512+1)*

octet o51*

Length of NR radio parameters per geographical area list for UE-to-network relay communication contents

octet o51+1

octet o51+2

Radio parameters per geographical area info 1

octet o51+3

octet o513

Radio parameters per geographical area info 2

octet (o513+1)*

octet o514*

…

octet (o514+1)*

octet o515*

Radio parameters per geographical area info n

octet (o515+1)*

octet o10*

Length of radio parameters per geographical area contents

octet o510+1

octet o510+2

Geographical area

octet o510+3

octet o5100

Radio parameters

octet o5100+1

octet o511-1

MI

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

octet o511

Radio parameters (octet o5100+1 to o511-1):

The radio parameters field is coded according to figure 5.3.2.11 and table 5.3.2.11, applicable in the geographical area indicated by the geographical area field when not served by NG-RAN.

Managed indicator (MI) (octet o511 bit 8):

The managed indicator indicates how the radio parameters indicated in the radio parameters field in the geographical area indicated by the geographical area field are managed.

Bit

8

0 Non-operator managed

1 Operator managed

If the length of radio parameters per geographical area contents field is bigger than indicated in figure 5.6.2.8, receiving entity shall ignore any superfluous octets located at the end of the radio parameters per geographical area contents.

Length of geographical area contents

octet o510+3

octet o510+4

Coordinate 1

octet (o510+5)*

octet (o510+10)*

Coordinate 2

octet (o510+11)*

octet (o510+16)*

…

octet (o510+17)*

octet (o510-2+6*n)*

Coordinate n

octet (o510-1+6*n)*