9.15 PC5 Provisioning in multi-operator V2X scenarios
23.2863GPPApplication layer support for Vehicle-to-Everything (V2X) servicesFunctional architecture and information flowsRelease 18TS
9.15.1 General
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
9.15.2.1 V2X PC5 provisioning requirement
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
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
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.4 Void
9.15.2.5 Void
9.15.2.6 V2X PC5 provisioning requirement notification
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
9.15.3.1 General
This subclause describes the procedure for PC5 provisioning for multi-operator V2X services.
9.15.3.2 Procedure
Figure 9.11.3.2-1 illustrates the procedure where the VAE server supports the PC5 provisioning for multi-operator V2X services.
Pre-conditions:
1. The V2X UEs have connected to the V2X application server.
2. The V2X UEs are authorized by their corresponding PLMNs to use PC5 communication.
Figure 9.15.3.2-1: PC5 provisioning for multi-operator V2X services
1. The V2X application specific server provides a V2X PC5 provisioning requirement to the VAE server.
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.
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).
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.
NOTE: How the VAE server derives a merged set of PC5 policies is implementation dependent.
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.
NOTE: How the V2X UE selects which policy to apply is implementation dependent.
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.