5 Services offered by the V2X Application Enabler

29.4863GPPRelease 18Stage 3TSV2X Application Enabler (VAE) Services

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 Introduction

The table 5.1-1 shows the services provided by the VAE server and corresponding Service Operations:

Table 5.1-1 List of services provided by the VAE Server

Service Name	Service Operations	Operation Semantics	Example Consumer(s)
VAE_MessageDelivery	Deliver_DL_Message	Request/Response	V2X application specific server
	Deliver_UL_Message	Subscribe/Notify	V2X application specific server
	V2X_MessageDelivery_Subscribe		V2X application specific server
	V2X_MessageDelivery_Unsubscribe		V2X application specific server
VAE_FileDistribution	Distribute_File	Request/ Response	V2X application specific server
VAE_ApplicationRequirement	Reserve_NetworkResource	Subscribe/Notify	V2X application specific server
VAE_ApplicationRequirement	Notify_NetworkResource	Subscribe/Notify	V2X application specific server
VAE_DynamicGroup	Configure_DynamicGroup	Subscribe/Notify	V2X application specific server
VAE_ServiceContinuity	Query_ServiceContinuity	Request/Response	VAE server
VAE_HDMapDynamicInfo	Subscribe_HDMapDynamicInfo	Subscribe/Notify	V2X application specific server
VAE_SessionOrientedService	Establish_Session	Subscribe/Notify	V2X application specific server
	Notify_Establish_Session
	Update_Session
	Notify_Update_Session
	Terminate_Session
	Notify_Terminate_Session
VAE_V2VConfigRequirement	Request_V2VConfigRequirement	Request/Response	V2X application specific server
VAE_PC5ProvisioningRequirement	Config_PC5ProvisioningRequirement	Subscribe/Notify	V2X application specific server
VAE_PC5ProvisioningRequirement	Notify_PC5ProvisioningRequirement	Subscribe/Notify	V2X application specific server

Table 5.1-2 summarizes the corresponding APIs defined in this specification.

Table 5.1-2: API Descriptions

Service Name	Clause	Description	OpenAPI Specification File	apiName	Annex
VAE_MessageDelivery	6.1	VAE Message Delivery Service	TS29486_VAE_MessageDelivery.yaml	vae-message-delivery	A.2
VAE_FileDistribution	6.2	VAE File Distribution Service	TS29486_VAE_FileDistribution.yaml	vae-file-distribution	A.3
VAE_ApplicationRequirement	6.3	VAE Application Requirement Provision Service	TS29486_VAE_ApplicationRequirement.yaml	vae-app-req	A.4
VAE_DynamicGroup	6.4	VAE Configure Dynamic Group Information Service	TS29486_VAE_DynamicGroup.yaml	vae-dynamic-group	A.5
VAE_ServiceContinuity	6.5	VAE Service Continuity Service	TS29486_VAE_ServiceContinuity.yaml	vae-service-continuity	A.6
VAE_HDMapDynamicInfo	6.6	VAE_HDMapDynamicInfo Service	TS29486_VAE_HDMapDynamicInfo.yaml	vae-hdmap-dynamic-info	A.7
VAE_SessionOrientedService API	6.7	VAE_SessionOrientedService	TS29486_VAE_SessionOrientedService.yaml	vae-session-oriented-service	A.8
VAE_V2VConfigRequirement	6.8	VAE_SessionOrientedService	TS29486_VAE_V2VConfigRequirement.yaml	vae-v2v-config-req	A.9
VAE_PC5ProvisioningRequirement	6.9	VAE_PC5ProvisioningRequirement	TS29486_VAE_PC5ProvisioningRequirement.yaml	vae-pc5-prov-req	A.19

5.2 VAE_MessageDelivery Service

5.2.1 Service Description

This service enables a NF service consumer to communicate with the VAE server to exchange V2X messages with the V2X UEs.

5.2.2 Service Operations

5.2.2.1 Introduction

The VAE_MessageDelivery service supports following service operations:

– V2X_MessageDelivery_Subscribe;

– V2X_MessageDelivery_Unsubscribe;

– Deliver_DL_Message; and

– Deliver_UL_Message.

5.2.2.2 V2X_MessageDelivery_Subscribe

5.2.2.2.1 General

The V2X_MessageDelivery_Subscribe service operation is used to create a subscription for V2X messages delivery between the V2X application specific server and VAE server.

5.2.2.2.2 Message Delivery Subscribe

Figure 5.2.2.2.2-1: Message delivery subscribe

When the NF service consumer (e.g. V2X application specific server) needs to receive the message from the V2X UE and/or send the message to the V2X UE, the NF service consumer shall send the POST method as step 1of the figure 5.2.2.2.2-1 to request to create an "Individual Message Delivery Subscription".

The NF service consumer shall include MessageDeliverySubscriptionData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual Message Delivery Subscription" resource. The "Individual Message Delivery Subscription" resource is created as described below.

The NF service consumer within MessageDeliverySubscriptionData data structure shall include:

– The identity of the V2X application specific server within the "appSerId" attribute;

– The V2X service ID within the "serviceId" attribute;

– The notification URI within the "notifUri" attribute; and

– The supported features with the "suppFeat" attribute;

and may include

– The geographical area identifier within the "geoId" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual Message Delivery Subscription", addressed by a URI as defined in clause 6.1.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

If errors occur when processing the HTTP POST request, the VAE server shall apply error handling procedures as specified in clause 6.1.7.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual Message Delivery Subscription".

5.2.2.3 V2X_MessageDelivery_Unsubscribe

5.2.2.3.1 General

The V2X_MessageDelivery_Unsubscribe service operation is used to remove the V2X messages delivery subscription.

5.2.2.3.2 Message Delivery Unsubscribe

Figure 5.2.2.3.2-1: message delivery unsubscribe

When the NF service consumer (e.g. V2X application specific server) needs to remove an existing subscription for receiving the message from the V2X UE or sending the message to the V2X UE, the NF service consumer shall send the DELETE method as step 1of the figure 5.2.2.3.2-1 to request to delete an "Individual Message Delivery Subscription".

Upon the reception of the HTTP DELETE request, if the VAE Server successfully processed and accepted the received HTTP DELETE request, the VAE Server shall:

– remove the corresponding subscription; and

– send an HTTP "204 No Content" response.

If errors occur when processing the HTTP POST request, the VAE Server shall send an HTTP error response as specified in clause 6.1.7.

5.2.2.4 Deliver_DL_Message

5.2.2.4.1 General

The Deliver_DL_Message service operation is used to deliver the V2X messages to the V2X UEs.

The following procedures using the Deliver_DL_Message service operation are supported:

– Downlink Message Delivery;

– Termination of Downlink Message Delivery.

5.2.2.4.2 Downlink Message Delivery

Figure 5.2.2.4.2-1: Downlink Message Delivery

When the NF service consumer (e.g. V2X application specific server) needs to send the message to the V2X UE, the NF service consumer shall send the HTTP POST method as step 1of the figure 5.2.2.4.2-1 to request to create an "Individual Downlink Message Delivery".

The NF service consumer shall include DownlinkMessageDeliveryData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual Downlink Message Delivery" resource. The "Individual Downlink Message Delivery" resource is created as described below.

The NF service consumer within the DownlinkMessageDeliveryData data structure shall include:

– Either the V2X UE ID within the "ueId" attribute or the V2X Group ID within the "groupId" attribute;

– V2X message payload carried by the V2X message within the "payload" attribute;

and may include:

– The duration within the "duration" attribute; and

– The geographical area identifier within the "geoId" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual Downlink Message Delivery", addressed by a URI as defined in clause 6.1.3.5.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual Downlink Message Delivery".

If errors occur when processing the HTTP POST request, the VAE Server shall apply error handling procedures as specified in clause 6.1.7.

After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in clause 6.5.2.4 or 6.5.2.5 of 3GPP TS 24.486 [28] to send the message to the VAE Client.

When the VAE Server received the reception report from the VAE Client as defined in clause 6.5.2.2 of 3GPP TS 24.486 [28], the VAE Server shall send an HTTP POST message to the NF service consumer identified by the notification URI received during the message delivery subscribed if the "ReceptionReport" feature is supported. Upon receipt of the request, the SCS/AS shall acknowledge the notification with an HTTP 204 No Content response.

5.2.2.4.3 Termination of Downlink Message Delivery

Figure 5.2.2.4.3-1: Termination of Downlink Message Delivery

When the NF service consumer (e.g. V2X application specific server) needs to terminate the message delivery to the V2X UE, the NF service consumer shall send the DELETE method as step 1of the figure 5.2.2.4.3-1 to request to delete the "Individual Downlink Message Delivery" resource.

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the Individual Downlink Message Delivery resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message.

When the message delivery duration expires, the VAE server may remove the associated Individual Downlink Message Delivery resource locally.

If errors occur when processing the HTTP DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.1.7.

5.2.2.5 Deliver_UL_Message

5.2.2.5.1 General

The Deliver_UL_Message service operation is used to deliver the uplink message to the NF service consumer (e.g. V2X application specific server).

5.2.2.5.2 Deliver Uplink Message

Figure 5.2.2.5.2-1: Deliver Uplink Message

If the VAE Server receives the uplink message for a V2X UE which an NF service consumer has subscribed to or a V2X UE belongs to a V2X group which the NF service consumer has subscribed to from the VAE Client as defined in clause 6.5.2.1 of 3GPP TS 24.486 [28], the VAE Server shall send an HTTP POST request with "{notifUri}" as previously provided by the NF service consumer within the corresponding subscription as URI and UplinkMessageDeliveryData data structure as request body that shall include:

– resource URI of the individual Message Delivery Subscription related to the notification within the "resourceUri" attribute;

– The V2X UE ID within the "ueId" attribute;

– V2X message payload carried by the V2X message within the "payload" attribute; and

– The geographical area identifier within the "geoId" attribute if available.

Upon the reception of the HTTP POST message, if the NF service consumer successfully processed and accepted the received HTTP POST request, the NF service consumer shall send an "204 No Content" HTTP response for a succesfull processing.

If errors occur when processing the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in clause 6.1.7.

When the VAE Server receives the response from the NF service consumer, the VAE Service shall send the response to the VAE Client as defined in clause 6.5.2.4 of 3GPP TS 24.486 [28].

5.3 VAE_FileDistribution Service

5.3.1 Service Description

This API enables the V2X application specific server to communicate with the VAE server to initiate file distribution to the V2X UEs.

5.3.2 Service Operations

5.3.2.1 Introduction

The VAE_FileDistribution service supports following service operations:

– Distribute_File

5.3.2.2 Distribute_File

5.3.2.2.1 General

The Distribute_File service operation is used to distribute files to the V2X UEs.

The following procedures using the Distribute_File service operation are supported:

– File Distribution;

– Termination of File Distribution.

5.3.2.2.2 File Distribution

Figure 5.3.2.2.2-1: File Distribution

When the NF service consumer (e.g. V2X application specific server) needs to distribute the file to the V2X UEs, the NF service consumer shall send the POST method as step 1 of the figure 5.3.2.2.2-1 to request to create an "Individual File Distribution".

The NF service consumer shall include FileDistributionData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual File Distribution" resource. The "Individual File Distribution" resource is created as described below.

The NF service consumer within the FileDistributionData data structure shall include:

– The file lists within the "fileLists" attribute;

– The geographical area within the "geoArea" attribute;

– maximum bitrate for the V2X application within the "maxBitrate" attribute; and

– maximum delay for the V2X application within the "maxDelay" attribute;

and may include:

– The V2X Group ID within the "groupId" attribute;

– The serving class within the "serviceClass" attribute;

– The duration within the "duration" attribute; and

– The local MBMS information within the "localMbmsInfo" attribute or the "localMbmsActInd" set to true if the "LocalMBMS" feature is supported.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual File Distribution", addressed by a URI as defined in clause 6.2.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

The VAE Server shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual File Distribution".

If errors occur when processing the HTTP POST or DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.2.7.

The VAE server makes use of the xMB procedures as defined 3GPP TS 29.116 [19] to create MBMS sessions whose type is set to "files" and to request the delivery of files over these sessions. Before provisioning files to the BM‑SC, the VAE server prepares the file for distribution, which may include partition of large files into smaller files or encryption.

The VAE server is responsible for translating the parameters related to the V2X application triggering the file delivery into corresponding xMB parameters. Table 5.3.2.2.2-1 describes the mapping between the VAE_FileDistribution API attribute and the xMB API properties specified in 3GPP TS 29.116 [19].

Table 5.3.2.2.2-1: Mapping between VAE_FileDistribution API and xMB API

V2X parameter	Corresponding xMB API property
serviceClass	service-class
fileLists	file-list
geoArea	geographical-area
maxBitrate	max-bitrate
maxDelay	max-delay
localMbmsInfo or localMbmsActInd	local-mbms-delivery-information

NOTE: The list of V2X parameters needed for file delivery is not exhaustive and can be updated based on the specific V2X application requirements.

5.3.2.2.3 Termination of File Distribution

Figure 5.3.2.2.3-1: Termination of File Distribution

When the NF service consumer (e.g. V2X application specific server) needs to terminate the File Distribution to the V2X UE, the NF service consumer shall send the DELETE method as step 1of the figure 5.3.2.2.3-1 to request to delete the "Individual File Distribution" resource.

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the Individual File Distribution resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message.

If errors occur when processing the DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.2.7.

When the message delivery duration expires, the VAE server may remove the associated Individual File Distribution resource locally.

5.4 VAE_ApplicationRequirement Service

5.4.1 Service Description

This API enables the V2X application specific server to communicate with the VAE server to provide V2X application requirement to the underlying 3GPP network.

5.4.2 Service Operations

5.4.2.1 Introduction

The VAE_ApplicationRequirement service supports following service operations:

– Reserve_NetworkResource

– Notify_NetworkResource

5.4.2.2 Reserve_NetworkResource

5.4.2.2.1 General

The Reserve_NetworkResource service operation is used to provide V2X application requirement to underlying 3GPP network.

The following procedures using the Reserve_NetworkResource service operation are supported:

– Network Resource Reservation;

– Termination of Network Resource Reservation

5.4.2.2.2 Network Resource Reservation

Figure 5.4.2.2.2-1: Network Resource Reservation

When the NF service consumer (e.g. V2X application specific server) needs to provide V2X application requirement to the underlying 3GPP network, the NF service consumer shall send the POST method as step 1 of the figure 5.4.2.2.2-1 to request to create an "Individual Application Requirement".

The NF service consumer shall include ApplicationRequirementData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual Application Requirement" resource. The "Individual Application Requirement" resource is created as described below.

The NF service consumer within the ApplicationRequirementData data structure shall include:

– Either the V2X Group ID within the "groupId" attribute or the V2X UE ID within the "ueId" attribute;

– notification URI within the "notifUri" attribute;

– The service Id within the "serviceId" attribute; and

– V2X application requirement within the "appRequirement" attribute;

and may include:

– The duration within the "duration" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual Application Requirement", addressed by a URI as defined in clause 6.3.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource. The VAE Server shall interact with the SEAL NRM server as specified in the 3GPP TS 29.549 [29] for the V2X application requirement received in step 1.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual Application Requirement".

If errors occur when processing the HTTP POST or DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.3.7.

5.4.2.2.3 Termination of Network Resource Reservation

Figure 5.4.2.2.3-1: Termination of Network Resource Reservation

When the NF service consumer (e.g. V2X application specific server) needs to terminate network resource reservation, the NF service consumer shall send the DELETE method as step 1of the figure 5.4.2.2.3-1 to request to delete the "Individual Application Requirement" resource.

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the Individual Application Requirement resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message.

If errors occur when processing the HTTP DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.3.7.

When the message delivery duration expires, the VAE server may remove the associated Individual Application Requirement resource locally.

5.4.2.3 Notify_NetworkResource

5.4.2.3.1 General

The Notify_NetworkResource service operation is used to notify the result of network resource adaptation corresponding to the V2X application requirement.

5.4.2.3.2 Notify Network Resource

Figure 5.4.2.3.2-1: Notify Network Resource

If the VAE Server receives the result of network resource adaptation corresponding to the V2X application requirement from the SEAL NRM server as specified in the 3GPP TS 29.549 [29], the VAE Server shall send an HTTP POST request with "{notifUri}" as previously provided by the NF service consumer within the corresponding subscription as URI and AppReqNotification data structure as request body that shall include:

– resource URI of the individual Application Requirement related to the notification within the "resourceUri" attribute;

– the result of the network resource adaptation corresponding to the V2X application requirement within the "result" attribute.

If errors occur when processing the HTTP POST request, the VAE Server shall send an HTTP error response as specified in clause 6.3.7.

5.5 VAE_DynamicGroup Service

5.5.1 Service Description

This API enables the V2X application specific server to communicate with the VAE server to configure dynamic group information.

5.5.2 Service Operations

5.5.2.1 Introduction

The VAE_DynamicGroup service supports following service operations:

– Configure_DynamicGroup

– Notify_DynamicGroup

5.5.2.2 Configure_DynamicGroup

5.5.2.2.1 General

The Configure_DynamicGroup service operation is used to configures the dynamic group information at the VAE server.

The following procedures using the Configure_DynamicGroup service operation are supported:

– Dynamic Group Configuration;

– Termination of Dynamic Group Configuration.

5.5.2.2.2 Dynamic Group Configuration

Figure 5.5.2.2.2-1: Dynamic Group Configuration

When the NF service consumer (e.g. V2X application specific server) needs to configures the dynamic group information at the VAE server, the NF service consumer shall send the POST method as step 1 of the figure 5.5.2.2.2-1 to request to create an "Individual Group Configuration".

The NF service consumer shall include GroupConfigurationData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual Group Configuration" resource. The "Individual Group Configuration" resource is created as described below.

The NF service consumer within GroupConfigurationData data structure shall include:

– The dynamic Group ID within the "groupId" attribute;

– The group definition within the "definition" attribute;

– The group leader Id within the "leaderId" attribute; and

– The notification URI within the "notifUri" attribute.

and may include:

– The duration within the "duration" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual Group Configuration", addressed by a URI as defined in clause 6.4.3.2.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource. Then the VAE Server shall interact with the VAE Client to notify the dynamic group information as specified in the 3GPP TS 24.486 [28].

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual Group Configuration".

If errors occur when processing the HTTP POST or DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.4.7.

5.5.2.2.3 Termination of Dynamic Group Configuration

Figure 5.5.2.2.3-1: Termination of Dynamic Group Configuration

When the NF service consumer (e.g. V2X application specific server) needs to terminate the Dynamic Group Configuration at the VAE server, the NF service consumer shall send the DELETE method as step 1of the figure 5.5.2.2.3-1 to request to delete the "Individual Group Configuration" resource.

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the Individual Group Configuration resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message.

If errors occur when processing the HTTP DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.4.7.

When the message delivery duration expires, the VAE server may remove the associated Individual Group Configuration resource locally.

5.5.2.3 Notify_DynamicGroup

5.5.2.3.1 General

The Notify_DynamicGroup service operation is used to notify the dynamic group information (i.e. group member joins or leaves) at the VAE server.

5.5.2.3.2 Notify Dynamic Group

Figure 5.5.2.3.2-1: Notify Dynamic Group

If the VAE Server receives the dynamic group information (i.e. group member joins or leaves) from the VAE Client as specified in the 3GPP TS 24.486 [28], the VAE Server shall send an HTTP POST request with "{notifUri}" as previously provided by the NF service consumer within the corresponding subscription as URI and DynamicGroupNotification data structure as request body that shall include:

– resource URI of the individual Application Requirement related to the notification within the "resourceUri" attribute;

– one or more joined group member within the "joinedUeIds" attribute if available; and

– one or more left group member within the "leftUeIds" attribute if available.

Upon the reception of the HTTP POST message, the NF service consumer shall send an "204 No Content" HTTP response for a succesfull processing.

If errors occur when processing the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in clause 6.4.7.

5.6 VAE_ServiceContinuity Service

5.6.1 Service Description

This service provided by the VAE server enables exposing information to facilitate the V2X service continuity.

5.6.2 Service Operations

5.6.2.1 Introduction

The VAE_ServiceContinuity service supports following service operations:

– Query_ServiceContinuity

5.6.2.2 Query_ServiceContinuity

5.6.2.2.1 General

The Query_ServiceContinuity service operation is used to query the VAE server whether it can support the desired V2X service in the designated geographical area.

5.6.2.2.2 Query service continuity

Figure 5.6.2.2.2-1: Query service continuity

When the NF service consumer (e.g. V2X server) needs to query service continuity information (e.g. receives the local service information request from the VAE Client as specified in the 3GPP TS 24.486 [28]), the NF service consumer shall send an HTTP GET request as step 1 of the figure 5.6.2.2.2-1 to the "Individual Geographical Area" resource with query parameter V2X service id in "service-id". When the VAE Server receives the HTTP GET request from the NF service consumer, the VAE Server shall perform the query.

On success, "200 OK" shall be returned as step 2 of the figure 5.6.2.2.2-1 to indicate that the VAE server can support the desired V2X service for the target "Individual Geographical Area" resource. The response body shall contain the "Individual Geographical Area" resource including the requested V2X service id.

If errors occur when processing the HTTP POST request, the VAE Server shall apply error handling procedures as specified in clause 6.5.7.

5.7 VAE_HDMapDynamicInfo Service

5.7.1 Service Description

This API enables the V2X application specific server to communicate with the VAE server to subscribe for the HD map dynamic information.

5.7.2 Service Operations

5.7.2.1 Introduction

The VAE_HDMapDynamicInfo service supports following service operations:

– Subscribe_HDMapDynamicInfo

– Notify_HDMapDynamicInfo

5.7.2.2 Subscribe_HDMapDynamicInfo

5.7.2.2.1 General

The Subscribe_HDMapDynamicInfo service operation is used to subscribe for the HD map dynamic information.

5.7.2.2.2 Subscribe HD Map Dynamic Information

Figure 5.7.2.2.2-1: Subscribe HD Map Dynamic Information

When the NF service consumer (e.g. V2X application specific server) needs to subscribe for the HD map dynamic information, the NF service consumer shall send the POST method as step 1 of the figure 5.7.2.2.2-1 to request to create an "Individual HdMap DynamicInfo Subscription".

The NF service consumer shall include HdMapDynamicInfoData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual HdMap DynamicInfo Subscription" resource. The "Individual HdMap DynamicInfo Subscription" resource is created as described below.

The NF service consumer within the HdMapDynamicInfoData data structure shall include:

– notification URI within the "notifUri" attribute;

– the V2X UE ID within the "ueId" attribute; and

– application defined proximity range information within the "range" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual HdMap DynamicInfo_Subscription", addressed by a URI as defined in clause 6.6.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual HdMap DynamicInfo Subscription".

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the Individual HdMap DynamicInfo Subscription resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message.

If errors occur when processing the HTTP POST or DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.6.7.

5.7.2.3 Notify_HDMapDynamicInfo

5.7.2.3.1 General

The Notify_HDMapDynamicInfo service operation is used to notify the HD map dynamic information.

5.7.2.3.2 Notify HD Map Dynamic Information

Figure 5.7.2.3.2-1: Notify HD Map Dynamic Information

When the VAE Server prepared the HD map dynamic informaiton including the aggregate information from different VAE Clients, the VAE Server shall send an HTTP POST request with "{notifUri}" as previously provided by the NF service consumer within the corresponding subscription as URI and HdMapDynamicInfoNotification data structure as request body that shall include:

– resource URI of the Individual HdMap DynamicInfo Subscription related to the notification within the "resourceUri" attribute;

– the HD map dynamic information corresponding within the "hdMapDynaInfo" attribute.

If errors occur when processing the HTTP POST request, the VAE Server shall send an HTTP error response as specified in clause 6.6.7.

5.8 VAE_SessionOrientedService Service

5.8.1 Service Description

This API enables the V2X application specific server to communicate with the VAE server to trigger establishment, update and termination of session-oriented service.

5.8.2 Service Operations

5.8.2.1 Introduction

The VAE_SessionOrientedService service supports following service operations:

– Establish_Session

– Notify_Establish_Session

– Update_Session

– Notify_Update_Session

– Terminate_Session

– Notify_Terminate_Session

NOTE: Notify_Terminate_Session is implemented by including the result of the termination of session-oriented service received from the VAE client within the response to termination session as defined in clause 5.8.2.6.2.

5.8.2.2 Establish_Session

5.8.2.2.1 General

The Establish_Session service operation is used to trigger the establishment of the session-oriented service by the VAE server.

5.8.2.2.2 Establish Session

Figure 5.8.2.2.2-1: Establish Session

When the NF service consumer (e.g. V2X application specific server) needs to trigger the establishment of the session-oriented service by the VAE server, the NF service consumer shall send the POST method as step 1 of the figure 5.8.2.2.2-1 to request to create an "Individual Session Oriented Service Subscription".

The NF service consumer shall include SessionOrientedData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual Session Oriented Service Subscription" resource. The "Individual Session Oriented Service Subscription" resource is created as described below.

The NF service consumer within the SessionOrientedData data structure shall include:

– notification URI within the "notifUri" attribute;

– the remote V2X UE ID within the "ueId" attribute;

– the V2X service ID within the "serviceId" attribute;

– the identity of the V2X application specific server within the "appSerId" attribute; and

– application QoS requirements for the session within the "appQosReq" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual Session Oriented Service Subscription", addressed by a URI as defined in clause 6.7.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual Session Oriented Service Subscription".

After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to establish a session-oriented service with VAE client.

If errors occur when processing the HTTP POST request, the VAE Server shall apply error handling procedures as specified in clause 6.7.7.

5.8.2.3 Notify_Establish_Session

5.8.2.3.1 General

The Notify_Establish_Session service operation is used to notify the establishment of the session-oriented service by the VAE server.

5.8.2.3.2 Notify Establish Session

Figure 5.8.2.3.2-1: Notify Establish Session

When the VAE Server response from the VAE client indicating the result of session establishment requested by the VAE server as defined in 3GPP TS 24.486 [28], the VAE Server shall send an HTTP POST request with "{notifUri}" as previously provided by the NF service consumer within the corresponding subscription as URI and Notification data structure as request body that shall include:

– resource URI of the Individual Session Oriented Service Subscription related to the notification within the "resourceUri" attribute;

– the value "ESTABLISHMENT" with the "action" attribute; and

– the result of session establishment within the "result" attribute.

If errors occur when processing the HTTP POST request, the VAE Server shall send an HTTP error response as specified in clause 6.7.7.

5.8.2.4 Update_Session

5.8.2.4.1 General

The Update_Session service operation is used to trigger the update to the session-oriented service by the VAE server.

5.8.2.4.2 Update Session

Figure 5.8.2.4.2-1: Update Session

When the NF service consumer (e.g. V2X application specific server) needs to trigger the update to the session-oriented service by the VAE server, the NF service consumer shall send the PUT method as step 1 of the figure 5.8.2.4.2-1 to request to update the "Individual Session Oriented Service Subscription".

The NF service consumer shall include SessionOrientedData data structure in the payload body of the HTTP PUT to update the "Individual Session Oriented Service Subscription" resource. The remote V2X UE ID, the V2X service ID and the identity of the V2X application specific server shall remain unchanged from previous values.

When the VAE Server receives the HTTP PUT request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall update the "Individual Session Oriented Service Subscription" and respond to the NF service consumer with a 200 OK or 204 No Content status code.

After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to update the session-oriented service with VAE client.

If errors occur when processing the HTTP PUT request, the VAE Server shall apply error handling procedures as specified in clause 6.7.7.

5.8.2.5 Notify_Establish_Session

5.8.2.5.1 General

The Notify_Update_Session service operation is used to notify the update to the session-oriented service by the VAE server.

5.8.2.5.2 Notify Update Session

When the VAE Server response from the VAE client indicating the result of session update requested by the VAE server, the VAE Server invoke the procedure defined in clause 5.8.2.3 with the difference that the VAE Server includes the value "UPDATE" within the "action" attribute.

5.8.2.6 Terminate_Session

5.8.2.6.1 General

The Terminate_Session service operation is used to trigger the termination of the session-oriented service by the VAE server.

5.8.2.6.2 Terminate Session

Figure 5.8.2.6.2-1: Terminate Session

When the NF service consumer (e.g. V2X application specific server) needs to trigger the termination of the session-oriented service by the VAE server, the NF service consumer shall send the DELETE method as step 1 of the figure 5.8.2.6.2-1 to request to delete the "Individual Session Oriented Service Subscription".

When the VAE Server receives the HTTP DELETE request from the NF service consumer, the VAE server shall authorize the request from the NF service consumer. If the authorization is successful, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to delete the session-oriented service with VAE client. If the VAE server receives the successful response from the VAE client, the VAE Server shall delete the "Individual Session Oriented Service Subscription" and respond to the NF service consumer with a 204 No Content status code.

If errors occur when processing the DELTE request, the VAE Server shall apply error handling procedures as specified in clause 6.7.7.

5.9 VAE_V2VConfigRequirement Service

5.9.1 Service Description

This API enables the V2X application specific server to provide a V2V configuration requirement to the VAE server to manage the UE-to-UE broadcast/groupcast communication.

5.9.2 Service Operations

5.9.2.1 Introduction

The VAE_V2VConfigRequirement service supports following service operations:

– Request_V2VConfigRequirement operation

5.9.2.2 Request_V2VConfigRequirement

5.9.2.2.1 General

The Request_V2VConfigRequirement service operation is used to provide a V2V configuration requirement request to the VAE server to manage the UE-to-UE broadcast/groupcast communication by the V2X application specific server.

5.9.2.2.2 Request V2V Configuration Requirement

Figure 5.9.2.2.2-1: Request_V2VConfigRequirement

When the NF service consumer (e.g. V2X application specific server) needs to provide a V2V configuration requirement, the NF service consumer shall send the POST method as step 1 of the figure 5.9.2.2.2-1 to request to create an "Individual V2V Configuration".

The NF service consumer shall include V2vConfigurationData data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual V2V Configuration" resource. The "Individual V2V Configuration" resource is created as described below.

The NF service consumer within the V2vConfigurationData data structure shall include:

– either the V2X group ID within the "groupId" attribute or the V2X service ID within the "serviceId" attribute;

and may include:

– candidate Relay V2X-UE ID list within the "canUeIds" attribute; and

– application QoS requirements for the session within the "appQosReq" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual V2V Configuration" resource, addressed by a URI as defined in clause 6.8.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual Session Oriented Service Subscription".

After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to provide the V2V configuration infomation to the VAE client. The VAE server may also provide the list of V2X-UEs to serve as application layer relays based on the candidate list of relay V2X-UEs received form the NF service consumer.

The NF service consumer may include the V2vConfigurationData data structure in the payload body of the HTTP PUT to update the "Individual V2V Configuration" resource. The V2X group ID and the V2X service ID shall remain unchanged from previous values. When the VAE Server receives the HTTP PUT request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall update the "Individual V2V Configuration" and respond to the NF service consumer with a 200 OK or 204 No Content status code. After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to provide the upated infomation to the VAE client.

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the "Individual V2V Configuration" resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message. After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to delete the V2V configuration information from the VAE client.

If errors occur when processing the HTTP POST, HTTP PUT or HTTP DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.8.7.

5.10 VAE_PC5ProvisioningRequirement Service

5.10.1 Service Description

This API enables the V2X application specific server to communicate with the VAE server to request from VAE server the PC5 provisioning service in multi-operator V2X scenarios.

5.10.2 Service Operations

5.10.2.1 Introduction

The VAE_PC5ProvisioningRequirement service supports following service operations:

– Config_PC5ProvisioningRequirement

– Notify_PC5ProvisioningRequirement

5.10.2.2 Config_PC5ProvisioningRequirement

5.10.2.2.1 General

The Config_PC5ProvisioningRequirement service operation is used by the V2X application specific server to provide a V2X PC5 provisioning requirement to the VAE server.

5.10.2.2.2 Config_PC5ProvisioningRequirement

Figure 5.10.2.2.2-1: Config_PC5ProvisioningRequirement

When the NF service consumer (e.g. V2X application specific server) needs to provide a V2X PC5 provisioning requirement to the VAE server, the NF service consumer shall send the POST method as step 1 of the figure 5.10.2.2.2-1 to request to create an "Individual PC5 Provisioning Requirement Subscription".

The NF service consumer shall include ProvisioningRequirement data structure in the payload body of the HTTP POST to request a creation of representation of the "Individual PC5 Provisioning Requirement Subscription" resource. The "Individual PC5 Provisioning Requirement Subscription" resource is created as described below.

The NF service consumer within the ProvisioningRequirement data structure shall include:

– notification URI within the "notifUri" attribute;

– either the remote V2X UE ID within the "ueId" attribute or the V2X group ID within the "groupId" attribute;

– the V2X service ID within the "serviceId" attribute;

– application QoS requirements for the session within the "appQosReq" attribute;

and may include:

– the PLMN ID list within the "plmnList" attribute.

When the VAE Server receives the HTTP POST request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall create a new resource, which represents "Individual PC5 Provisioning Requirement Subscription", addressed by a URI as defined in clause 6.9.3.3.2 and contains a VAE Server created resource identifier. The VAE Server shall respond to the NF service consumer with a 201 Created message, including Location header field containing the URI for the created resource.

The NF service consumer shall use the URI received in the Location header in subsequent requests to the VAE Server to refer to the "Individual PC5 Provisioning Requirement Subscription".

After the VAE Server responded to the NF service consumer, the VAE Server may invoke the procedure defined in 3GPP TS 24.486 [28] to send a PC5 provisioning status request to VAE client(within the multi-operator V2X service) to receive up-to-date information on the per PLMN provisioning policies/ parameters.

The NF service consumer may include the ProvisioningRequirement data structure in the payload body of the HTTP PUT to update the "Individual PC5 Provisioning Requirement Subscription" resource. The remote V2X UE ID, the V2X service ID and the V2X service ID shall remain unchanged from previous values When the VAE Server receives the HTTP PUT request from the NF service consumer, the VAE server shall make an authorization based on the information received from the NF service consumer. If the authorization is successful, the VAE Server shall update the "Individual PC5 Provisioning Requirement Subscription" and respond to the NF service consumer with a 200 OK or 204 No Content status code. After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to provide the upated infomation to the VAE client.

Upon receipt of the HTTP DELETE message from the NF service consumer, the VAE Server shall check if the "Individual PC5 Provisioning Requirement Subscription" resource identified by the URI already exists. If the resource exists, the VAE Server shall delete the resource and respond to the NF service consumer with a 204 No Content success message. After the VAE Server responded to the NF service consumer, the VAE Server shall invoke the procedure defined in 3GPP TS 24.486 [28] to delete the PC5 provisioning status request from the VAE client.

If errors occur when processing the HTTP POST, HTTP PUT or HTTP DELETE request, the VAE Server shall apply error handling procedures as specified in clause 6.9.7.

5.10.2.3 Notify_PC5ProvisioningRequirement

5.10.2.3.1 General

The Notify_PC5ProvisioningRequirement service operation is used to notify the result of multi operation PC5 provisioning requirement to the V2X UEs by the VAE server.

5.10.2.3.2 Notify_PC5ProvisioningRequirement

Figure 5.10.2.3.2-1: Notify_PC5ProvisioningRequirement

After the VAE Server determines the updated PC5 provisioning policies/parameters to be jointly used across the V2X-UEs within the multi-operator V2X service, the VAE Server shall send an HTTP POST request with "{notifUri}" as previously provided by the NF service consumer within the corresponding subscription as URI and Notification data structure as request body that shall include:

– resource URI of the Individual PC5 Provisioning Requirement Subscription related to the notification within the "resourceUri" attribute;

– the result of V2X PC5 provisioning requirement within the "result" attribute.

If errors occur when processing the HTTP POST request, the VAE Server shall send an HTTP error response as specified in clause 6.9.7.