Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.286  Word version:  17.3.0

Top   Top   Up   Prev   Next
0…   4…   6…   7…   9…   9.2…   9.4…   9.6…   9.9…   9.11…   9.14…   9.17…   10…   A…

 

9.4  V2X message deliveryWord‑p. 38

9.4.1  GeneralWord‑p. 38

The VAE capabilities provide support for V2X message distribution originated from the V2X application specific layer. The message communication corresponding V2X applications and services are the responsibility of the V2X application specific layer entities. The VAE capabilities abstract the message distribution aspects from the V2X application specific layer.

9.4.2  Information flowsWord‑p. 38

9.4.2.1  V2X messageWord‑p. 38

Table 9.4.2.1-1 describes the information flow for a VAE server to deliver a V2X message to the VAE client.
Information Element Status Description
V2X UE IDMIdentifier of the destination V2X UE
V2X message payload (see NOTE)MV2X message payload carried by the V2X message (e.g. ETSI ITS DENM [15])
V2X service IDMThe V2X service ID to which the V2X message belongs to
GEO IDOGeographical area identifier
Reception report requiredOIndicates whether a reception report is required for the V2X message
NOTE:
The V2X message is V2X application/service specific and is not specified in this specification.
Up

9.4.2.2  V2X message reception reportWord‑p. 38

Table 9.4.2.2-1 describes the information flow for VAE client to respond to reception of a V2X message from the VAE server.
Information Element Status Description
ResultMResult from the VAE client in response to V2X message reception indicating success or failure
Up

9.4.2.3  V2X group messageWord‑p. 38

Table 9.4.2.3-1 describes the information flow for a VAE server to deliver a V2X message to a group of VAE clients.
Information Element Status Description
V2X group IDMThe group ID for which the V2X message is addressed
V2X message payload (see NOTE)MV2X message payload carried by the V2X message (e.g. ETSI ITS DENM [15])
V2X service IDMThe V2X service ID to which the V2X group message belongs to
Geo IDOGeographical area identifier
Reception report requiredOIndicates whether a reception report is required for the V2X group message
NOTE:
The V2X message is V2X application/service specific and is not specified in this specification.
Up

9.4.2.4  V2X uplink messageWord‑p. 39

Table 9.4.2.4-1 describes the information flow for a VAE client to transmit a V2X message to the VAE server.
Information Element Status Description
V2X UE IDMIdentifier of the sender V2X UE
V2X message payload (see NOTE)MV2X message payload carried by the V2X uplink message (e.g. ETSI ITS DENM [15])
V2X service IDMV2X service ID, the V2X UE is sending to the V2X AS
GEO ID (s)OGeographical area identifier of the originating V2X message from the V2X UE
Reception report requiredOIndicates whether a reception report is required for the uplink V2X message
NOTE:
The V2X message payload is V2X application/service specific and is not specified in this specification.
Up

9.4.2.5  V2X uplink message reception reportWord‑p. 39

Table 9.4.2.5-1 describes the information flow for a VAE server in response to a received V2X message from the VAE client.
Information Element Status Description
ResultMResult from the VAE server in response to V2X message indicating success or failure
Up

9.4.2.6  Subscribe V2X message delivery requestWord‑p. 39

Table 9.4.2.6-1 describes the information flow for a V2X application specific server to subscribe with VAE server for V2X messages.
Information Element Status Description
V2X application specific server identity informationMIdentity information of the V2X application specific server
V2X service IDMThe V2X service ID to which the V2X application-specific server registers to
GEO IDOThe geographical area identifier to which the V2X application-specific server registers to
Endpoint informationMInformation of the endpoint of the V2X application specific server to which the uplink messages have to be sent
Up

9.4.2.7  Subscribe V2X message delivery responseWord‑p. 40

Table 9.4.2.7-1 describes the information flow for a VAE server to provide a response to the V2X application specific server for subscription request for V2X uplink message delivery.
Information Element Status Description
Subscription identifier (NOTE)MThe subscription identifier corresponding to the request
ResultMResult from the VAE server indicating subscription success or failure
NOTE:
If Result indicates failure, the value of the subscription identifier in the response is ignored.
Up

9.4.2.8  Unsubscribe V2X message delivery requestWord‑p. 40

Table 9.4.2.8-1 describes the information flow for a V2X application specific server to unsubscribe with VAE server for V2X messages.
Information Element Status Description
Subscription identifierMThe subscription identifier provided by the VAE server
Up

9.4.2.9  Unsubscribe V2X message delivery responseWord‑p. 40

Table 9.4.2.9-1 describes the information flow for a VAE server to provide a response to the V2X application specific server for unsubscription request for V2X uplink message delivery.
Information Element Status Description
ResultMResult from the VAE server indicating unsubscription success or failure
Up

9.4.3  Message delivery to target geographical areas from the VAE serverWord‑p. 40

9.4.3.1  GeneralWord‑p. 40

This subclause describes the procedures for delivering V2X messages to registered V2X UEs at the VAE server in targeted geographical areas.

9.4.3.2  ProcedureWord‑p. 41

Pre-conditions:
  1. One or more VAE clients have registered with the VAE server as described in subclause 9.2.3;
  2. One or more VAE clients have subscribed to geographical area GEO ID;
  3. The VAE server has created a mapping between geographical area information and client identification as described in subclause 9.3.3; and
  4. The V2X application-specific server has subscribed with the VAE server as described in subclause 9.4.6.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.4.3.2-1: Procedure for delivering messages to target geographical areas from the VAE server
Up
Step 1.
The application-specific server sends a V2X message of a service with V2X Service ID (e.g. ETSI ITS DENM, ETSI ITS CAM) with target geographical area GEO ID.
Step 2.
The VAE server retrieves the list of registered and subscribed clients for the V2X message targeting geographical area GEO ID and determines the clients' identification V2X UE ID.
Step 3.
The VAE server transmits the message to each VAE client using the client identification.
Step 4.
The VAE client provides the V2X message to the application-specific client.
Step 5.
The VAE client provides a V2X message reception report to the VAE server if indicated in the V2X message.
Up

9.4.4  V2X group message distributionWord‑p. 41

9.4.4.1  GeneralWord‑p. 41

This subclause describes the procedures for V2X group delivery from the VAE server to the VAE clients.

9.4.4.2  ProcedureWord‑p. 41

Pre-conditions:
  1. The VAE client has registered for receiving V2X group messages as described in in subclause 10.3.8 of TS 23.434.
  2. The V2X application-specific server has subscribed with the VAE server as described in subclause 9.4.6.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.4.4.2-1: Procedure for delivering V2X group messages to VAE clients
Up
Step 1.
The V2X application-specific server provides a V2X message for distribution to V2X group with V2X Group ID.
Step 2.
The VAE server delivers the V2X message to all registered VAE clients with V2X Group ID.
Step 3.
The VAE client provides the V2X message to the V2X application-specific client.
Step 4.
The VAE client may provide a V2X message reception report to the VAE server.

9.4.5  Uplink V2X message deliveryWord‑p. 42

9.4.5.1  GeneralWord‑p. 42

This subclause describes the procedures for delivering V2X messages from the V2X UE to the V2X application server.

9.4.5.2  Procedure for uplink message deliveryWord‑p. 42

Pre-conditions:
  1. The VAE client has discovered the VAE server as described in subclause 9.1.2.
  2. The VAE client has registered to a V2X service identified by a V2X Service ID as described in subclause 9.2.
  3. The V2X application specific server has performed the subscription as specified in clause 9.4.6.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.4.5.2-1: Procedure for delivering messages from V2X UE to the V2X application server
Up
Step 1.
The V2X application-specific client sends a V2X uplink message to the VAE client.
Step 2.
The VAE client determines the VAE server for receiving the V2X uplink message with V2X Service ID.
Step 3.
The VAE client transmits the V2X uplink message to the VAE server.
Step 4.
The VAE server provides the V2X uplink message to the endpoint of V2X application-specific server(s).
Step 5.
The VAE server may provide a V2X uplink message reception report to the VAE client if indicated in the V2X uplink message.

9.4.6  Procedure for subscription to message deliveryWord‑p. 43

Pre-condition:
  • The V2X application specific server is configured with the VAE server information.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.4.6-1: Procedure for subscription to message delivery
Up
Step 1.
The V2X application-specific server sends a subscribe V2X message delivery request to the VAE server including the information of V2X service ID, GEO ID and the end point address at which the uplink messages from the V2X UE to the V2X application specific server are to be delivered.
Step 2.
The VAE server stores the subscription information and provides an acknowledgement via a subscribe V2X message delivery response message to the V2X application specific server.

9.5  File DistributionWord‑p. 43

9.5.1  GeneralWord‑p. 43

The VAE capabilities provide support for file distribution to the V2X application specific layer. The VAE capabilities abstract the aspects like file chunking, QoE management, file delivery from the V2X application specific layer.

9.5.2  Use of MBMS "files" session typeWord‑p. 43

The VAE server acts as a content provider and the VAE client acts as an MBMS client in the xMB reference model (subclause 4.1 in TS 26.348).
The VAE server makes use of the xMB procedures from TS 26.348 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 9.5.2-1 describes the mapping between the V2X parameters and the xMB API properties specified in TS 26.348.
V2X parameter Corresponding xMB API property
File transfer session indicatorSession Type: Files
List of files to be sent by the VAE server and their locationsFile List
Target geographical area for the V2X UEsGeographical Area
Information about the V2X application (e.g., software update, HD map download)Service Class
Maximum bitrate for the V2X applicationMax Bitrate
Maximum delay for the V2X applicationMax Delay
QoE metrics the VAE server is interested in receiving about the V2X applicationQoE Reporting
Local MBMS information or local MBMS activation indicationLocal MBMS information (NOTE)
NOTE:
The local MBMS information as the xMB API property is defined in TS 29.116.
Up

Up   Top   ToC