This subclause describes the procedures for the VAE server to provide service requirements to the 3GPP network system. The Service Capability Exposure Function (SCEF) can be used for this purpose. As described in TS 23.682, the SCEF provides a means to expose the services and capabilities provided by 3GPP network interfaces and provides a means for the discovery of the exposed services and capabilities.
The information flow Background data transfer request from VAE server (acting as SCS/AS) to SCEF over T8 reference point is specified in clause 5.9 in TS 23.682 (resource management for background data transfer).
The procedure uses the APIs defined in subclause 5.8 in TS 23.682, 5.9 in TS 23.682 and 5.11 in TS 23.682 for setting up an AS session with required QoS procedure. This procedure defines the information elements that need to be exchanged between the VAE server (acting as SCS/AS) and the SCEF function during service negotiation.
The procedure notification generation by the SCEF function in response to the service requirements from the VAE server. The SCEF function notifies the VAE server if the service requirements can be satisfied. This procedure uses the APIs defined in subclause 5.8 in TS 23.682 for informing about potential network issues.
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.
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).
The V2X application specific server can be responsible for managing HD maps and providing the HD map information to the V2X application specific client on V2X UE (e.g host vehicle controlled by advanced/remote driving). As per a proximity range set by the application layer, the VAE layer support providing the dynamic information (i.e. location information) required for HD maps management to the V2X application specific server.
This feature is feasible for scenarios where host vehicle (V2X UE) is in advanced/remote driving mode with slow to moderate speed and deployed in areas like campus (e.g. autonomous shuttle vehicles), factories or ports (e.g. autonomous/remotely controlled guided vehicles).
This feature utilizes the following procedures:
V2X application specific server subscription for host vehicle's HD map dynamic information with VAE server.
VAE server tracking host vehicle's UE location with support from SEAL's location management server.
VAE server management of dynamic UE location based group.
VAE server obtaining dynamic information from the UEs in proximity range of the host vehicle.
VAE server notification of host vehicle's HD map dynamic information to V2X application specific server.
The V2X application specific server sends a subscribe HD map dynamic information request to the VAE server 1. The request includes the V2X UE ID of the host vehicle, application defined proximity range information.
VAE server 1 uses its associated LMS 1 to obtain the dynamic UE list and the corresponding location information in the proximity area of the host vehicle by providing the application defined proximity range and the UE location of the host vehicle as specified in clause 9.3.10 of TS 23.434.
For each VAE server determined in step 4, VAE server 1 requests the dynamic UE list and its corresponding location information for the application defined proximity range by providing the UE location of the host vehicle.
If VAE server 1 has no dynamic UE location group for the V2X UE ID, the VAE server 1 creates a dynamic UE location based group with the UE list received from its LMS and other VAE server(s) 2..N. Further VAE server 1 stores the dynamic UE location based group. Otherwise, the VAE server 1 updates the dynamic UE location group with the latest UE information. The V2X UEs whose locations are no more within the application defined proximity range are removed from the dynamic UE location group.
The VAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the VAE clients who are part of the dynamic UE location group. These VAE clients (V2X UEs) belong to the same V2X SP as the host vehicle. The request consists of reporting configuration (e.g. frequency of reporting, event based).
The VAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the VAE server(s) who's V2X UEs are part of the dynamic UE location group. The request consists of temporary V2X UE IDs, reporting configuration (e.g. frequency of reporting, event based).
As per subscription procedure in clause 18.104.22.168 and clause 22.214.171.124, the VAE client(s) and VAE server 2 (of another V2X SP) send notification of dynamic information to the VAE server 1. The notification includes the nearby UE information (e.g. vehicles, pedestrians), distance with nearby UEs, UEs location information. As per agreement between V2X SPs, if V2X UE IDs are not shareable, then VAE server 2 includes the temporary V2X UE IDs in the notification.
The VAE server 1 sends notification of HD map dynamic information to the V2X application specific server. The notification includes the aggregated information of all the UEs in the application defined proximity range of the host vehicle and the location of the host vehicle.