5 Provisioning of parameters for V2X configuration

24.3863GPPProtocol aspectsRelease 17Stage 3TSUser Equipment (UE) to V2X control function

5.1 General

V2X communication is configured by the V2X configuration parameters.

5.2 Configuration and precedence of V2X configuration parameters

5.2.1 General

The V2X configuration parameters consist of:

a) configuration parameters for V2X provisioning as specified in subclause 5.2.3;

b) configuration parameters for V2X communication over PC5 as specified in subclause 5.2.4; and

c) configuration parameters for V2X communication over LTE-Uu as specified in subclause 5.2.5.

5.2.2 Precedence of the V2X configuration parameters

The V2X configuration parameters can be:

a) pre-configured in the ME;

b) configured in the USIM;

c) provided by the V2X control function to the ME using procedures specified in subclause 5.3.2, subclause 5.3.3 and subclause 5.3.4; or

d) any combination of the above.

The UE shall use the V2X configuration parameters in the following order of decreasing precedence:

a) the V2X configuration parameters provided by the V2X control function to the ME using procedures specified in subclause 5.3.2, subclause 5.3.3 and subclause 5.3.4;

b) the V2X configuration parameters configured in the USIM; and

c) the V2X configuration parameters pre-configured in the ME.

5.2.3 Configuration parameters for V2X provisioning

The configuration parameters for V2X provisioning consist of:

a) optionally a V2X control function address. The V2X control function address can be an FQDN or an IP address; and

b) optionally parameters of a PDN connection for communication with V2X control function.

5.2.4 Configuration parameters for V2X communication over PC5

The configuration parameters for V2X communication over PC5 consist of:

a) an expiration time for the validity of the configuration parameters for V2X communication over PC5;

b) a list of PLMNs in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRAN for V2X communication;

c) an indication of whether the UE is authorized to use V2X communication over PC5 when the UE is not served by E-UTRAN for V2X communication;

d) per geographical area:

1) radio parameters for V2X communication over PC5 applicable when the UE is not served by E-UTRAN for V2X communication and is located in the geographical area, with an indication of whether these radio parameters are "operator managed" or "non-operator managed";

e) a list of the V2X services authorized for V2X communication over PC5. Each entry of the list contains:

1) a V2X service identifier; and

2) a destination Layer-2 ID;

f) PPPP to PDB mapping rules between the ProSe Per-Packet Priority (PPPP) and the Packet Delay Budget (PDB) for V2X communication over PC5;

g) optionally, a default destination Layer-2 ID;

h) optionally, a configuration for the applicability of privacy for V2X communication over PC5, containing:

1) a T5000 timer indicating how often the UE shall change the source Layer-2 ID and source IP address (for IP data) self-assigned by the UE for V2X communication over PC5; and

2) a list of the V2X services which require privacy for V2X communication over PC5. Each entry in the list contains:

A) a V2X service identifier; and

B) optionally, one or more associated geographical areas;

i) optionally, V2X service identifier to V2X frequency mapping rules between the V2X service identifiers and the V2X frequencies with associated geographical areas for V2X communication over PC5;

j) optionally, a list of the V2X services authorized for ProSe Per-Packet Reliability (PPPR). Each entry of the list contains a V2X service identifier and a ProSe Per-Packet Reliability (PPPR) value;

k) optionally, V2X service identifier to Tx Profile mapping rules between the V2X service identifiers and the Tx Profile for V2X communication over PC5;

l) optionally, configuration parameters for V2X communication over NR-PC5, consisting of:

1) optionally, a list of V2X service identifier to V2X NR frequency mapping rules. Each mapping rule contains one or more V2X service identifiers and the V2X NR frequencies with associated geographical areas;

2) a list of V2X service identifier to destination layer-2 ID for broadcast mapping rules. Each mapping rule contains one or more V2X service identifiers and the destination layer-2 ID for broadcast;

3) optionally, a default destination layer-2 ID for broadcast;

4) a list of V2X service identifier to destination layer-2 ID for groupcast mapping rules. Each mapping rule contains one or more V2X service identifiers and the destination layer-2 ID for groupcast;

5) a list of V2X service identifier to default destination layer-2 ID for unicast initial signaling mapping rules. Each mapping rule contains one or more V2X service identifiers and the default destination layer-2 ID for initial signalling to establish unicast connection;

6) a list of V2X service identifier to PC5 QoS parameters mapping rules. The PC5 QoS parameters are specified in clause 5.4.2 of 3GPP TS 23.287 [26];

7) an AS configuration, including a list of SLRB mapping rules applicable when the UE is not served by E-UTRA and is not served by NR. Each SLRB mapping rule contains a PC5 QoS profile and an SLRB. The PC5 QoS profile contains the following parameters:

i) the PC5 QoS profile contains a PQI;

ii) if the PQI of the PC5 QoS profile identifies a GBR QoS, the PC5 QoS profile contains a PC5 flow bit rates consisting of a guaranteed flow bit rate (GFBR) and a maximum flow bit rate (MFBR);

iii) if the PQI of the PC5 QoS profile identifies a non-GBR QoS, the PC5 QoS profile contains the PC5 link aggregated bit rate consisting of a per link aggregate maximum bit rate (PC5 LINK-AMBR);

NOTE: PC5 link aggregated bit rate is only used for unicast mode communications over PC5.

iv) the PC5 QoS profile contains a range, which is only used for groupcast mode communications over PC5; and

v) the PC5 QoS profile can contain the priority level, the averaging window, and/or the maximum data burst volume. If one or more of the priority level, the averaging window or the maximum data burst volume are not contained in the PC5 QoS profile, their default values apply;

8) a list of V2X service identifier to default mode of communication mapping rules. Each mapping rule contains one or more V2X service identifiers and the default mode of communication (one of unicast, groupcast or broadcast);

9) a list of NR-PC5 unicast security policies. Each entry in the list contains an NR-PC5 unicast security policy composed of:

i) one or more V2X service identifiers;

ii) the signalling integrity protection policy for the V2X service identifier(s);

iii) the signalling ciphering policy for the V2X service identifier(s);

iv) the user plane integrity protection policy for the V2X service identifier(s);

v) the user plane ciphering policy for the V2X service identifier(s); and

vi) one or more geographical areas where the NR-PC5 unicast security policy applies;

10) for broadcast mode, groupcast mode and initial signalling of the PC5 unicast link establishment, PC5 DRX configurations (see 3GPP TS 38.331 [25]), including the mapping of PC5 QoS profile(s) to PC5 DRX cycle(s) and the default PC5 DRX configuration, when the UE is not served by E-UTRA and not served by NR; and

m) optionally, V2X service identifier to Tx Profile mapping rules between the V2X service identifiers and the Tx Profile for V2X communication over NR-PC5. The Tx Profile can be either:

1) NR Tx profile corresponding to the NR-PC5 for broadcast mode V2X communication over PC5 and groupcast mode V2X communication over PC5; or

2) NR Tx profile corresponding to transmitting and receiving initial signalling of the PC5 unicast link establishment.

5.2.5 Configuration parameters for V2X communication over LTE-Uu

The configuration parameters for V2X communication over LTE-Uu consist of:

a) an expiration time for the validity of the configuration parameters for V2X communication over LTE-Uu;

b) optionally parameters of a PDN connection for V2X communication over LTE-Uu using unicast; and

c) a list of PLMNs in which the UE is authorized to use V2X communication over LTE-Uu. For each PLMN, the list contains:

1) optionally a V2X AS MBMS configuration for receiving V2X application server information using MBMS consisting of:

A) a TMGI;

B) a list of service area identifiers (SAIs);

C) a frequency; and

D) an SDP encoded as specified in subclause 7.3;

2) for transfer of a V2X message of a V2X service not identified by a V2X service identifier:

A) optionally one or more V2X MBMS configuration(s) for receiving V2X communication over LTE-Uu using MBMS consisting of:

i) a TMGI;

ii) a list of service area identifiers (SAIs);

iii) a frequency; and

iv) an SDP body;

B) optionally one or more V2X application server address(es) applicable when the UE is registered to the PLMN. A V2X application server address can be an FQDN or an IP address; and

C) optionally per geographical area, one or more V2X application server address(es) applicable when the UE is registered to the PLMN and is located in the geographical area. A V2X application server address can be an FQDN or an IP address; and

3) for transfer of a V2X message of a V2X service identified by a V2X service identifier:

A) a list of the V2X services authorized for V2X communication over LTE-Uu. Each entry of the list contains:

i) a V2X service identifier;

ii) optionally one or more V2X MBMS configuration(s) for receiving V2X communication over LTE-Uu using MBMS consisting of:

– a TMGI;

– a list of service area identifiers (SAIs);

– a frequency; and

– an SDP body encoded as specified in subclause 7.2;

iii) optionally a V2X application server address for the unicast V2X communication over LTE-Uu applicable when the UE is registered to the PLMN. A V2X application server address consists of:

– an FQDN, or an IP address; and

– a UDP port, a TCP port for bidirectional transport or both of them; and

iv) optionally per geographical area, one or more V2X application server address(es) for the unicast V2X communication over LTE-Uu applicable when the UE is registered to the PLMN and is located in the geographical area. A V2X application server address consists of:

– an FQDN, or an IP address; and

– a UDP port, a TCP port for bidirectional transport or both of them;

B) optionally one or more default V2X MBMS configuration(s) for receiving V2X communication over LTE-Uu using MBMS consisting of:

i) a TMGI;

ii) a list of service area identifiers (SAIs);

iii) a frequency; and

iv) an SDP body encoded as specified in subclause 7.2;

C) optionally per type of data (IP and non-IP) and V2X message family (in case of non-IP), one or more default V2X application server addresses for the unicast V2X communication over LTE-Uu applicable when the UE is registered to the PLMN. Each V2X application server address consists of:

i) an FQDN, or an IP address; and

ii) a UDP port, a TCP port for bidirectional transport or both of them;

D) optionally per type of data (IP and non-IP), V2X message family (in case of non-IP) and a geographical area, one or more default V2X application server addresses for the unicast V2X communication over LTE-Uu applicable when the UE is registered to the PLMN. A V2X application server address consists of:

i) an FQDN, or an IP address; and

ii) a UDP port, a TCP port for bidirectional transport or both of them; and

E) a list of V2X service identifiers of the V2X services authorized for V2X communication over LTE-Uu using existing unicast routing.

5.3 Procedures

5.3.1 General

The procedures specified in remaining subclauses of the parent subclause of this subclause enable modification of the configuration parameters of the UE specified in subclause 5.2. The UE and the V2X control function shall support requirements for securing communication over V3 reference point as specified in 3GPP TS 33.185 [20].

5.3.2 V2X control function discovery procedure

In order to discover the V2X control function IP address, the UE shall proceed in following order of decreasing precedence:

a) if the V2X control function address specified in subclause 5.2.3 is provisioned and is an IP address, the UE shall use this IP address as the discovered V2X control function address;

b) if the V2X control function address specified in subclause 5.2.3 is provisioned and is an FQDN, the UE shall perform DNS lookup of the V2X control function FQDN as specified in IETF RFC 1035 [13] and shall use the resulting IP address as the discovered V2X control function address;

c) if the V2X control function address specified in subclause 5.2.3 is not provisioned and the UE is pre-configured with a V2X control function FQDN, the UE shall perform DNS lookup as specified in IETF RFC 1035 [13] of the V2X control function FQDN and shall use the resulting IP address as the discovered V2X control function address; and

d) if the V2X control function address specified in subclause 5.2.3 is not provisioned and the UE is not pre-configured with a V2X control function FQDN, the UE shall self-construct the V2X control function FQDN as specified in 3GPP TS 23.003 [14], shall perform DNS lookup as specified in IETF RFC 1035 [13] of the V2X control function FQDN and shall use the resulting IP address as the discovered V2X control function address.

5.3.3 V2X authorization procedure

5.3.3.1 General

The V2X authorization procedure enables the UE to retrieve V2X communication parameters from the V2X control function.

The UE shall initiate the V2X authorization procedure:

a) when the UE receives a request from upper layers to send or to receive using V2X communication over PC5 a V2X message of a V2X service identified by a V2X service identifier and:

1) the expiration time of validity of the configuration parameters for V2X communication over PC5 indicates a timer earlier than the current time; or

2) the V2X service identifier is not listed in an entry of the list of the V2X services authorized for V2X communication over PC5 and the registered PLMN is in the list of PLMNs in which the UE is authorized to use V2X communication over PC5 as specified in subclause 5.2.4;

b) when the UE is served by E-UTRAN for V2X communication and the UE changes its registered PLMN to a PLMN which is not listed in the list of PLMNs in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRAN for V2X communication;

c) when the UE is served by E-UTRAN for V2X communication and the UE changes its registered PLMN to a PLMN which is not listed in the list of PLMNs in which the UE is authorized to use V2X communication over LTE-Uu;

d) when the UE receives a request from upper layers to send or to receive using V2X communication over LTE-Uu a V2X message of a V2X service not identified by a V2X service identifier and the expiration time of validity of the configuration parameters for V2X communication over LTE-Uu indicates a timer earlier than the current time; or

e) when the UE receives a request from upper layers to send or to receive a V2X message using V2X communication over LTE-Uu of a V2X service identified by a V2X service identifier and:

1) the expiration time of validity of the configuration parameters for V2X communication over LTE-Uu indicates a timer earlier than the current time; or

2) the V2X service identifier is not listed in an entry of the list of the V2X services authorized for V2X communication over LTE-Uu and the registered PLMN is in the list of PLMNs in which the UE is authorized to use V2X communication over LTE-Uu as specified in subclause 5.2.5.

If the parameters of a PDN connection for communication with V2X control function specified in subclause 5.2.3 are configured:

a) if a PDN connection according to these parameters is not established yet, the UE shall establish a PDN connection according to these parameters; and

b) if a PDN connection according to these parameters is already established (due to application of the present specification or due to another application), the UE shall send and receive messages of the V2X authorization procedure via the PDN connection established according to these parameters.

The UE shall send messages of the V2X authorization procedure to the V2X control function IP address discovered as specified in subclause 5.3.2.

5.3.3.2 V2X authorization procedure initiation

In order to initiate the V2X authorization procedure, the UE shall request client-initiated provisioning of the management object specified in 3GPP TS 24.385 [3].

Upon receiving a request for client-initiated provisioning of the management object specified in 3GPP TS 24.385 [3], the V2X control function may update the management object specified in 3GPP TS 24.385 [3] in the UE.

5.3.3.3 V2X authorization procedure successful

If client-initiated provisioning of the management object specified in 3GPP TS 24.385 [3] successfully finishes, the UE and the V2X control function shall consider the V2X authorization procedure to be successfully completed.

5.3.3.4 V2X authorization procedure not successful

If the UE receives no response within an implementation dependent time after sending of the request for client-initiated provisioning of the management object specified in 3GPP TS 24.385 [3], the UE shall determine that the V2X authorization procedure is unsuccessfully completed.

5.3.4 V2X authorization update procedure

5.3.4.1 General

The V2X authorization update procedure enables the V2X control function to provide new V2X configuration parameters to the UE.

If the parameters of a PDN connection for communication with V2X control function specified in subclause 5.2.3 are configured:

a) if a PDN connection according to these parameters is not established yet, the UE shall establish a PDN connection according to these parameters; and

b) if a PDN connection according to these parameters is already established (due to application of the present specification or due to another application), the UE shall send and receive messages of the V2X authorization update procedure via the PDN connection established according to these parameters.

The UE shall send messages of the V2X authorization update procedure to the V2X control function IP address discovered as specified in subclause 5.3.2.

5.3.4.2 V2X authorization update procedure initiation

In order to initiate the V2X authorization update procedure, the V2X control function shall send a notification requesting the UE to initiate server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3] to the UE.

Upon receiving a notification requesting the UE to initiate server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3], the UE shall request server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3].

Upon receiving a request for server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3], the V2X control function shall update the management object specified in 3GPP TS 24.385 [3] in the UE.

5.3.4.3 V2X authorization update procedure successful

If server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3] successfully finishes, the UE and the V2X control function shall consider the V2X authorization update procedure to be successfully completed.

5.3.4.4 V2X authorization update procedure not successful

If the V2X control function does not receive a request for server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3] within an implementation dependent time after sending of the notification requesting the UE to initiate server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3], the V2X control function shall determine that the V2X authorization update procedure is unsuccessfully completed.

If the UE receives no response within an implementation dependent time after sending of the request for server-initiated provisioning of the management object specified in 3GPP TS 24.385 [3], the UE shall determine that the V2X authorization update procedure is unsuccessfully completed.