Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.286  Word version:  18.5.0

Top   Top   Up   Prev   Next
0…   4…   6…   7…   9…   9.2…   9.3…   9.4…   9.5…   9.6…   9.7…   9.8…   9.9…   9.10…   9.11…   9.12…   9.13…   9.14…   9.15…   9.16…   9.17…   9.18   9.19…   9.20…   9.21…   9.22…   10…   10.2.8…   A   B…   C…   D… 
9.17 V2X groupcast/broadcast configuration by VAE layer  9.17.1 General  9.17.2 Information flows  9.17.2.1 V2V configuration requirement request  9.17.2.2 V2V configuration requirement response  9.17.2.3 V2X groupcast/broadcast configuration request  9.17.2.4 V2X groupcast/broadcast configuration response  9.17.2.5 UE-to-UE groupcast/broadcast configuration request  9.17.2.6 UE-to-UE groupcast/broadcast configuration response  9.17.2.7 VAE message  9.17.3 V2X groupcast/broadcast configuration by VAE layer  9.17.3.1 General  9.17.3.2 Procedure  9.17.4 V2X groupcast/broadcast delivery by VAE layer  9.17.4.1 General  9.17.4.2 Procedure 
...

 

9.17  V2X groupcast/broadcast configuration by VAE layer |R17|  p. 81

9.17.1  General  p. 81

The VAE client configures policies for the UE-to-UE broadcast/groupcast delivery, based on the requirement received by the VAE server, to reduce V2X broadcast flooding, while ensuring meeting the KPIs for one or more V2X services in a service area.
Following procedures are provided for this feature:
  • the UE-to-UE broadcast/groupcast configuration by VAE client as specified in clause 9.17.3; and
  • the UE-to-UE delivery which is handled by VAE clients over V5-AE as specified in clause 9.17.4.
Up

9.17.2  Information flows  p. 81

9.17.2.1  V2V configuration requirement request  p. 81

Table 9.17.2.1-1 describes the information flow V2V configuration requirement request from the V2X application specific server to the VAE server.
Information Element Status Description
V2X group IDM (NOTE)Identity of the V2X group for which the V2X application requirement is initiated
V2X service IDM (NOTE)The V2X service ID for which application requirement corresponds to
Candidate Relay V2X-UE ID listOList of identities of the V2X UEs, which are candidate to serve as application layer relays
V2X application QoS requirementsOThe application QoS requirements (reliability, delay, jitter) for the V2X service
NOTE:
Either of the information element should be present.
Up

9.17.2.2  V2V configuration requirement response  p. 81

Table 9.17.2.2-1 describes the information flow V2V configuration requirement response from the VAE server to the V2X application specific server.
Information Element Status Description
ResultMThe result corresponding to the V2V configuration requirement request
Up

9.17.2.3  V2X groupcast/broadcast configuration request  p. 82

Table 9.17.2.3-1 describes the information flow V2X groupcast/broadcast configuration request from the VAE server to the VAE client.
Information Element Status Description
VAE Server IDMIdentity of the VAE server which is requester of the V2X groupcast/broadcast configuration
V2X group IDM (NOTE)Identity of the V2X group for which the V2X groupcast/broadcast configuration is requested
V2X service IDM (NOTE)The V2X service ID for which the groupcast/broadcast configuration is requested
PC5 Provisioning policies/ parametersMPC5 provisioning policies/parameters to be used by the V2X-UEs within the V2X service (list provided in TS 23.287)
Relay V2X-UE ID listOList of identities of the V2X UEs to serve as application layer relays
Minimum number of re-transmissionsOMinimum Number of allowed re-transmissions for the V2X message delivery
Up

9.17.2.4  V2X groupcast/broadcast configuration response  p. 82

Table 9.17.2.4-1 describes the information flow V2X groupcast/broadcast configuration response from the VAE client to the VAE server.
Information Element Status Description
ResultMThe result corresponding to the V2X groupcast/broadcast configuration request
Up

9.17.2.5  UE-to-UE groupcast/broadcast configuration request  p. 82

Table 9.17.2.5-1 describes the information flow UE-to-UE groupcast/broadcast configuration request from a VAE client to another VAE client within the group or the V2X service.
Information Element Status Description
VAE client IDMIdentity of the VAE client which is requester of the UE-to-UE groupcast/broadcast configuration
V2X group IDM (NOTE)Identity of the V2X group for which the UE-to-UE groupcast/broadcast configuration is requested
V2X service IDM (NOTE)The V2X service ID for which the UE-to-UE groupcast/broadcast configuration is requested
UE-to-UE groupcast/broadcast configuration policies/ parametersMThe requested configuration policies to be applied for the UE-to-UE broadcast/groupcast communications. The policies / parameters may be the following:
  • activation / de-activation of the application relaying capability
  • adaptation of the application QoS parameters of the PC5 session
  • adaptation of the frequency and number of re-transmissions of the application messages
  • activation / de-activation of bundling of V2X messages to containers
Up

9.17.2.6  UE-to-UE groupcast/broadcast configuration response  p. 83

Table 9.17.2.6-1 describes the information flow UE-to-UE groupcast/broadcast configuration response from a VAE client to another VAE client within the group or the V2X service.
Information Element Status Description
ResultMThe result corresponding to the UE-to-UE groupcast/broadcast configuration request
Up

9.17.2.7  VAE message  p. 83

Table 9.17.2.7-1 describes the information flow for a VAE client to deliver a VAE message to another VAE client.
Information Element Status Description
VAE client IDMIdentity of the VAE client which provides the V2X message
V2X group IDM (NOTE 1)Identity of the V2X group (for groupcast delivery)
V2X service IDM (NOTE 1)Identity of the V2X service (for broadcast delivery)
V2X Message ID(s)OIdentity of the V2X message(s) within the VAE message (CPM, PCM, MCM, DENM)
Management ContainerOManagement Container provides basic information about the transmitter, including the V2X-UE type (e.g. vehicle or RSU) and position
VAE payloadMV2X message(s) payload carried by the VAE message
NOTE 1:
Either of the information element should be present.
NOTE 2:
One or more V2X messages may be carried within a VAE payload (e.g. CPM, PCM, MCM, DENM) depending on whether V2X message bundling is activated
Up

9.17.3  V2X groupcast/broadcast configuration by VAE layer  p. 84

9.17.3.1  General  p. 84

This subclause describes the procedure for V2X groupcast/broadcast configuration by the VAE layer.

9.17.3.2  Procedure  p. 84

Figure 9.17.3.2-1 illustrates the procedure where the VAE client configures policies for the UE-to-UE broadcast/ groupcast delivery to other VAE clients (within the V2X group or the V2X service), based on the requirement received by the VAE server.
Pre-conditions:
  1. The V2X UEs have connected to the V2X application server.
  2. VAE client 1 is registered with VAE server.
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.17.3.2-1: V2V groupcast/broadcast configuration by VAE layer
Figure 9.17.3.2-1: V2V groupcast/broadcast configuration by VAE layer
(⇒ copy of original 3GPP image)
Up
Step 1.
The V2X application specific server provides an V2V configuration requirement request to the VAE server to manage the UE-to-UE broadcast/groupcast communication. The VAE server may also provide within the request the list of V2X-UEs which are capable to serve as application layer relays.
Step 2.
The VAE server sends a V2V configuration requirement response to the V2X application specific server.
Step 3.
The VAE server provides a V2V broadcast/groupcast configuration request to VAE client 1. The VAE server may also provide within the request the list of V2X-UEs to serve as application layer relays based on the candidate list of relay V2X-UEs provided in step 1.
Step 4.
The VAE client 1 selects and stores one or more UE-to-UE groupcast/broadcast configuration policies per V2X application for the UE-to-UE broadcast/groupcast communications.
Step 5.
The VAE client 1 sends a V2V broadcast/groupcast configuration response to VAE server to notify on the result.
Step 6.
The VAE client 1 sends a request to VAE client N (can be any VAE client within the V2X group or V2X service) with the requested UE-to-UE groupcast/broadcast configuration policies for the UE-to-UE broadcast/groupcast communications.
Step 7.
The VAE client 1 receives a response from the VAE client 2, which includes either a positive or a negative acknowledgement of the message.
Up

9.17.4  V2X groupcast/broadcast delivery by VAE layer  p. 85

9.17.4.1  General  p. 85

This subclause describes the procedure for V2X groupcast/broadcast delivery by the VAE layer.

9.17.4.2  Procedure  p. 85

Figure 9.17.4.2-1 illustrates the procedure where the VAE client delivers the VAE message based on the configured policies (based on the procedure in clause 9.17.3).
Pre-conditions:
  • The VAE clients of the V2X-UEs have received and stored the UE-to-UE broadcast/groupcast configuration policies per V2X application.
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.17.4.2-1: V2X groupcast/broadcast delivery by VAE layer
Figure 9.17.4.2-1: V2X groupcast/broadcast delivery by VAE layer
(⇒ copy of original 3GPP image)
Up
Step 1.
The V2X application specific client of the V2X UE 1 sends to the VAE client 1, the V2X message to be broadcasted/groupcasted. This message may be for example a PCM, CPM, MCM, DENM.
Step 2.
The VAE client 1 retrieves the mapping for the V2X service and configuration policy related to the V2X message. The VAE client 1 forms a VAE message, based on the V2X message(s) and the applied configuration policy.
Step 3.
The VAE message is sent from the transmitting V2X-UE 1 to the receiving V2X-UE N (which may be application relay or destination V2X-UEs). For the case when a V2X-UE acts as application relay, the message is relayed towards the destination VAE client.
Step 4.
The V2X message is provided from the destination VAE client to the corresponding V2X application specific client. In case of message bundling, the receiving VAE client first un-bundles the V2X message and then sends to the V2X application specific client.
Up

Up   Top   ToC