Content for TS 23.286 Word version: 18.4.0

0… 4… 6… 7… 9… 9.2… 9.3… 9.4… 9.5… 9.6… 9.7… 9.8… 9.9… 9.10… 9.11… 9.12… 9.13… 9.14… 9.15… 9.16… 9.17… 9.18 9.19… 9.20… 9.21… 9.22… 10… 10.2.8… A B… C… D…

9.15 PC5 Provisioning in multi-operator V2X scenarios 9.15.1 General 9.15.2 Information flows 9.15.2.1 V2X PC5 provisioning requirement 9.15.2.2 PC5 provisioning status request 9.15.2.3 PC5 provisioning status response 9.15.2.6 V2X PC5 provisioning requirement notification 9.15.3 PC5 provisioning for multi-operator V2X services 9.15.3.1 General 9.15.3.2 Procedure
...

9.15 PC5 Provisioning in multi-operator V2X scenarios |R17| p. 72

9.15.1 General p. 72

The VAE server provides PC5 provisioning for multi-operator V2X services, based on the requirement received by the V2X application specific server.

9.15.2 Information flows p. 72

9.15.2.1 V2X PC5 provisioning requirement p. 72

Table 9.15.2.1-1 describes the information flow V2X PC5 provisioning requirement from the V2X application specific server to the VAE server.

Table 9.15.2.1-1: V2X PC5 provisioning requirement

Information Element	Status	Description
V2X UE ID	M (NOTE)	Identity of the V2X UE for which V2X application requirement is initiated
V2X group ID	M (NOTE)	Identity of the V2X group for which the V2X application requirement is initiated
V2X service ID	M	The V2X service ID for which application requirement corresponds to
PLMN ID list	O	The list of the PLMN identities for the PLMNs which offer the V2X service
V2X application QoS requirements	O	The application QoS requirements (reliability, delay, jitter) for the V2X service
NOTE: Either of the information element should be present.

9.15.2.2 PC5 provisioning status request p. 73

Table 9.15.2.2-1 describes the information flow PC5 provisioning status request from the VAE server to the VAE client.

Table 9.15.2.2-1: PC5 provisioning status request

Information Element	Status	Description
VAE Server ID	M	Identity of the VAE server which is requester of the PC5 parameters status
V2X service ID	M	The V2X service ID for which the VAE server's request corresponds to
PC5 provisiong status report configuration	O	The configuration of the VAE-client reporting related to the PC5 Policy/Parameters status, and optionally PC5 events like PC5 unavailability, PQI load/congestion info

9.15.2.3 PC5 provisioning status response p. 73

Table 9.15.2.3-1 describes the information flow PC5 provisioning status response from the VAE client to the VAE server.

Table 9.15.2.3-1: PC5 provisioning status response

Information Element	Status	Description
Result	M	The result of the PC5 provisioning status request
PC5 Policy/Parameters status report	M	The report based on the PC5 Policy/Parameters status request. This includes up-to-date policies/parameters: selected PQI attributes for the V2X service PQI load information communication range for the V2X service a RAT /interface (NR-PC5, LTE-PC5) preference an expected RAT availability / unavailability indication an expected V2X-UE moving out of coverage indication

9.15.2.6 V2X PC5 provisioning requirement notification p. 74

Table 9.15.2.6-1 describes the information flow V2X PC5 provisioning requirement notification from the VAE server to the V2X application specific server.

Table 9.15.2.6-1: V2X PC5 provisioning requirement notification

Information Element	Status	Description
Result	M	The result corresponding to the V2X PC5 provisioning requirement

9.15.3 PC5 provisioning for multi-operator V2X services p. 74

9.15.3.1 General p. 74

This subclause describes the procedure for PC5 provisioning for multi-operator V2X services.

9.15.3.2 Procedure p. 74

Figure 9.11.3.2-1 illustrates the procedure where the VAE server supports the PC5 provisioning for multi-operator V2X services.

Pre-conditions:

The V2X UEs have connected to the V2X application server.
The V2X UEs are authorized by their corresponding PLMNs to use PC5 communication.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.15.3.2-1: PC5 provisioning for multi-operator V2X services

Figure 9.15.3.2-1: PC5 provisioning for multi-operator V2X services
(⇒ copy of original 3GPP image)

Step 1.

The V2X application specific server provides a V2X PC5 provisioning requirement to the VAE server.

Step 2.

Optionally, the VAE Server sends a PC5 provisioning status request to the VAE Client (within the multi-operator V2X service) to receive up-to-date information on the per PLMN provisioning policies/ parameters.

Step 3.

Optionally, upon receiving the request as in Step 2, the VAE Client sends a PC5 provisioning status response to VAE server, which includes a report on the up-to-date policies /parameters per PLMN (e.g. application QoS - to - PQI mapping, range, radio parameters) and optionally PC5 related events (PC5 expected link downgrade).

Step 4.

The VAE Server determines the updated PC5 provisioning policies/parameters to be jointly used across the V2X-UEs within the multi-operator V2X service.

Step 5.

The VAE Server provides the PC5 parameter provisioning information to the V2X UE via V1-AE reference point for V2X communication on PC5 as specified in clause 9.6.4.

Step 6.

VAE Server sends a V2X PC5 provisioning requirement notification to the V2X application specific server to inform on the result of the multi-operator PC5 provisioning.