Content for TS 23.286 Word version: 17.3.0
9.6 Provisioning 3GPP system information by VAE server
9.6.1 General
9.6.2 Information flows
9.6.3 V2X USD provisioning
9.6.4 PC5 parameters provisioning
9.7 Network monitoring by the V2X UE
9.7.1 General
9.7.2 Information flows
9.7.3 V2X UE subscription for network monitoring information
9.7.4 Notifications for network monitoring information
9.8 Switching modes of operations for V2V communications
9.8.1 General
9.8.2 Information flows
9.8.3 Assistance for V2V communication mode switching
...
...
9.6 Provisioning 3GPP system information by VAE server Word‑p. 44
9.6.1 General Word‑p. 44
The VAE server can provision network related information like multicast (e.g. V2X USD) to the V2X UE to further enable V2X UE to consume V2X service based on the location and connection with the VAE server.
9.6.2 Information flows Word‑p. 44
9.6.2.1 V2X USD announcement Word‑p. 44
Table 9.6.2.1-1 describes the information flow V2X USD announcement from the VAE server to the VAE client.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | O | Identity of the V2X UE to which the configuration is required |
| V2X USD configuration data | M | The V2X USD configuration data as specified in TS 23.285 |
9.6.2.2 Set PC5 parameters request Word‑p. 44
Table 9.6.2.2-1 describes the information flow set PC5 parameters request from the VAE server to the VAE client.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | O | Identity of the V2X UE to which the configuration is required |
| PC5 parameters configuration data | M | The PC5 parameters configuration data as specified in TS 23.285 and TS 23.287. For PC5 provisioning in multi-operator V2X services (as specified in clause 9.15), these parameters may be the joint provisioning policies/parameters to be used by the V2X-UEs within the V2X service. |
9.6.2.3 Set PC5 parameters response Word‑p. 45
Table 9.6.2.3-1 describes the information flow set PC5 parameters response from the VAE client to the VAE server.
| Information Element | Status | Description |
|---|---|---|
| Result | M | The result whether setting the PC5 parameters received by the VAE server was successful or not |
9.6.3 V2X USD provisioning Word‑p. 45
9.6.3.1 General Word‑p. 45
This subclause describes the procedure for VAE server provisioning the V2X USD information to V2X UE via V1-AE reference point for V2X communication using MBMS.
9.6.3.2 Procedure Word‑p. 45
Figure 9.6.3.2-1 illustrates the procedure for provisioning V2X USD to the V2X UE via V1-AE reference point.
Pre-conditions:
- The V2X UE has connected to the VAE server.
- If multicast delivery mode is used, the MBMS bearer being used is activated by the VAE server.
Step 1.
The VAE server is triggered for providing V2X USD to V2X UE.
Step 2.
The VAE server sends the V2X USD announcement to the VAE client in the V2X UE with the information of the V2X USDs corresponding to the V2X applications. The V2X USD information consists of TMGI, list of SAIs, frequency and SDP information for V2X applications' communication using MBMS. The details of V2X USD are specified in subclause 4.4.7.2 in TS 23.285. This message can be sent via unicast or multicast.
Step 3.
Upon receiving the V2X USD announcement, the VAE client of the V2X UE stores the received V2X USDs.
Step 4.
The VAE client of the V2X UE provides an acknowledgement to the VAE server of the V2X AS. This step is optional when the announcement is sent via multicast.
9.6.4 PC5 parameters provisioning Word‑p. 46
9.6.4.1 General Word‑p. 46
This subclause describes the procedure for the VAE server provisioning the PC5 parameter provisioning information to the V2X UE via V1-AE reference point for V2X communication on PC5. The configuration information includes the configuration parameters specified in TS 23.285, TS 23.287 and additional application related configuration parameters.
9.6.4.2 Procedure Word‑p. 46
Figure 9.6.4.2-1 illustrates the procedure for provisioning PC5 parameters to the V2X UE via V1 reference point.
Pre-conditions:
- The V2X UE has discovered and connected to the VAE server.
- If multicast delivery mode is used, the MBMS bearer being used is activated by the VAE server.
Step 1.
The VAE server sends the set PC5 parameters request to the VAE client with the information of the PC5 parameters. The PC5 parameters information are specified in subclause 4.4.1.1.2 in TS 23.285 and in subclause 5.1.2.1 in TS 23.287. This message can be sent via unicast or multicast.
Step 2.
Upon receiving the set PC5 parameters request, the VAE client stores the received PC5 parameters in the V2X UE.
Step 3.
The VAE client provides an acknowledgement by sending the set PC5 parameters response to the VAE server.
9.7 Network monitoring by the V2X UE Word‑p. 46
9.7.1 General Word‑p. 46
The V2X UE subscribes for network monitoring information from the VAE server. Such network monitoring information may be used by the V2X UE for network connectivity adaptations (e.g. switching between different modes of operations for V2V communications).
9.7.2 Information flows Word‑p. 46
9.7.2.1 Network monitoring information subscription request Word‑p. 46
Table 9.7.2.1-1 describes the information flow network monitoring information subscription request from the VAE client to the VAE server.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identity of the V2X UE subscribing for the network monitoring information |
| Subscription event | M | Identify one or multiple network monitoring events (e.g. uplink degradation, congestion, overload, coverage) |
| Triggering criteria | M | Identify when the VAE server will send the monitoring reports to the VAE client |
| Area information | O | Identify the area where the event is subscribed |
| V2X service ID(s) | O | Identify the V2X service which is related with the event |
9.7.2.2 Network monitoring information subscription response Word‑p. 47
Table 9.7.2.2-1 describes the information flow network monitoring information subscription response from the VAE server to the VAE client.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identity of the V2X UE |
| Result | M | Indicates success or failure |
9.7.2.3 Network monitoring information notification Word‑p. 47
Table 9.7.2.3-1 describes the information flow network monitoring information notification from the VAE server to the VAE client.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identity of the subscribed V2X UE |
| Network monitoring information | M | This includes information on network status for the triggering criteria, and may include the following parameters:
|
|
NOTE:
With respect to the congestion information acquired from 5GC, it may be exact values for congestion status reported by NWDAF to NEF or abstracted values e.g. (High, Medium, Low) which can be reported by the NEF.
|
||
9.7.3 V2X UE subscription for network monitoring information Word‑p. 48
9.7.3.1 General Word‑p. 48
This subclause describes the procedure for V2X UE subscription for network monitoring information.
9.7.3.2 Procedure Word‑p. 48
Figure 9.7.3.2-1 illustrates the procedure where the V2X UE subscribes for the network monitoring information from the VAE server.
Pre-condition:
- The VAE client of the V2X UE is connected to the VAE server and is authorized to access the network monitoring information.
Figure 9.7.3.2-1: V2X UE subscription for network monitoring information
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The VAE client sends a network monitoring information subscription request to the VAE server.
Step 2.
The VAE server checks for the authorization of the VAE client to access the network monitoring information and if allowed, stores the subscription information corresponding to the V2X UE.
Step 3.
The VAE server sends a network monitoring information subscription response to the VAE client including the result of the subscription (i.e. success or failure).
9.7.4 Notifications for network monitoring information Word‑p. 48
9.7.4.1 General Word‑p. 48
This subclause describes the procedure for notification of network monitoring information from the VAE server.
9.7.4.2 Procedure Word‑p. 48
Figure 9.7.4.2-1 illustrates the procedure where the VAE server sends notification of the network monitoring information to the V2X UEs.
Pre-conditions:
- The VAE server acting as a SCS/AS is configured with the SCEF information and is authorized to exchange information with the SCEF as specified in subclause 4.9 in TS 23.682. The VAE server has subscribed to QoS notification service from 5GS (e.g. PCF/NWDAF). The notification may either include the request for QoS sustainability events as specified in TS 23.288 or can include a QoS change notification requests as provided by SMF and specified in TS 23.287;
- The V2X UE1 and V2X UE2 have subscribed for the network monitoring information at the VAE server.
- The VAE server may be aware of the RAT type the V2X UE supports from the registration of VAE client.
Step 1.
The VAE server communicates with the SCEF to receive network monitoring information as per the procedure in subclause 4.9 of TS 23.682, and/or communicates with NEF or NWDAF to receive QoS monitoring information and/or data analytics information of 5GS as defined in TS 23.288. The VAE server may determine to receive network monitoring information from EPC or 5GC or both considerting the RAT type provided by the UE. The VAE server subscription to QoS monitoring service from 5GS (e.g. PCF/NWDAF) may be active for a certain period of time or a given geographical area. The monitoring may either include the request for QoS sustainability events as specified in TS 23.288, or can include a QoS change notification requests as provided by SMF and specified in TS 23.287. The reporting may be configured by the application enabler layer for a given area, time, periodicity etc taking into account the service requirement and other parameters (e.g. expected congestion in certain area, time of the day, road conditions). Based on the subscription, as specified in TS 23.287, 5GS provides the extended QoS monitoring report, over N33 interface. This report may come either from NWDAF or SMF via PCF/NEF.
Step 2.
The network monitoring information (e.g. uplink or downlink link degradations, congestions, etc.) available at the VAE server about the on-going V2V session(s) and the network status is based on the original network monitoring information provided by the SCEF in step 1, and/or based on QoS monitoring report or data analytics from 5GS as specified in step 1. The VAE server determines the network monitoring information to send to the UE.
Step 3.
The monitoring information is sent to the subscribed V2X UEs via network monitoring information notification.
9.8 Switching modes of operations for V2V communications Word‑p. 49
9.8.1 General |R17| Word‑p. 49
The V2X services need to support different modes of operation for V2V (PC5 and Uu) communications. The V2X UE makes the decision to switch between different modes of operation for V2V communications considering the V2V service KPIs as specified in TS 22.186. The V2X application layer may provide the network monitoring information or recommendation for the communication mode to assist the V2X UE in making the switching decision for the operation modes selection.
The V2X UE determines switching of the mode of operation for V2V sessions based on several factors including the received network monitoring information as specified in subclause 9.7 and the PC5 communication quality information and assistance information received from the VAE server. The V2X UE switches the mode of operation and engages in either direct (PC5) or indirect (Uu) session as specified in subclause 23.14 of TS 36.300.
9.8.2 Information flows |R17| Word‑p. 49
9.8.2.1 Communication status request Word‑p. 49
Table 9.8.2.1-1 describes the information flow of communication status request from the VAE server to the VAE client.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identity of the V2X UE requested for communication status |
| V2X service ID | O | Identity of the V2X service being requested |
9.8.2.2 Communication status response Word‑p. 50
Table 9.8.2.2-1 describes the information flow of communication status response from the VAE client to the VAE server.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identity of the V2X UE |
| V2V communication mode | M | V2V communication mode supported by the V2X UE (e.g. LTE PC5, NR PC5) |
| V2X service ID | O | Identify of the V2X service corresponding to the communication status |
| Cell information | O | Cell information (e.g. NR cell, E-UTRA cell) of which the V2X UE is located |
| Communication link status information | O | Communication status of the V2X UE (e.g. uplink/downlink data rates, packet loss and etc.) |
9.8.2.3 V2V communication assistance info Word‑p. 50
Table 9.8.2.3-1 describes the information flow of V2V communication assistance info from the VAE server to the VAE client.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identity of the V2X UE |
| V2X service ID | O | Identify of the V2X service corresponding to the recommendation information |
| V2V communication assistance information | M | Assistance information for V2V communication mode switching to the V2X UE (e.g. recommended V2V communication mode, location, V2X service type, time validity, V2X service status, V2X application requirement, etc.) |
9.8.3 Assistance for V2V communication mode switching |R17| Word‑p. 50
9.8.3.1 General Word‑p. 50
The VAE server provides assistance information for V2V communication mode switching to the V2X UE. To provide the assistance the VAE server may acquire the application requirements, the communication staus of the V2X UEs and the network monitoring information from the 3GPP network.
9.8.3.2 Procedure Word‑p. 50
Figure 9.8.3.2-1 illustrates the procedure of assistance for V2V communication mode switching.
Pre-conditions:
- The VAE server is aware of the RAT type the V2X UE supports.
Step 1.
The VAE server may have acquired the application requirement from the V2X application specific server. The application requirements may include the conditions corresponding to the V2V communication modes (e.g. network status, UE's location, QoS, V2X service type, and other influential parameters for V2V communication mode).
Step 2.
The VAE server may send the communication status request to the VAE client to acquire the current communication status of the UE.
Step 3.
The VAE client responses to the VAE server with the communication status information (e.g. the current V2V communication mode, communication link quality and etc.)
Step 4.
The VAE server may have received the network monitoring information from the 3GPP network.
Step 5.
Based on information acquired above the VAE server generates assistance information (configuration or recommendation) for V2V communication mode switching.
Step 6.
The VAE server sends the V2V communication assistance information to the VAE client.
