Some of the V2X scenarios require group-based communication (e.g. platooning). Unlike V2X communication for safety scenarios where all V2X UEs in the communication range receive broadcasted communication, the group-based communication is expected to be received only by the V2X UEs of the members of that group. However in some scenarios the V2X UEs are required to be determined dynamically (with the assistance of the V2X application server or independently by the V2X UEs when they are not connected to the network) during the operation. Also each V2X application group has to be mapped to a ProSe Layer-2 group ID in order to avoid any interference during PC5 communications for the V2X application groups. The ProSe Layer-2 Group ID is only used in PC5 V2X group communication (without the involvement of the V2X application server).
Table 9.12.2.8-1 describes the information flow for dynamic group information update consent request from the VAE Server to the VAE client from whom consent is required.
Table 9.12.2.10-1 describes the information flow for dynamic group information update notification from the VAE server to the V2X application specific server.
The V2X application specific server is responsible for V2X dynamic group formation (including information like group ID assignment, group definition), membership management (e.g. user authorization). VAE layer supports V2X UEs in the Uu communication range assigning a ProSe Layer-2 Group ID for application layer V2X dynamic group formation.
The V2X application specific server requests the VAE server to configure dynamic group corresponding to the dynamic group information (e.g. dynamic group ID, group definition, group leader).
To enable PC5 communication, the VAE server assigns ProSe Layer-2 Group ID to the received dynamic group information from the available ProSe Layer-2 Group ID pool.
The V2X application specific client is responsible for V2X dynamic group information (including information like group ID assignment, group definition). VAE layer on the client supports assigning a ProSe Layer-2 Group ID for application layer V2X dynamic group formation.
The V2X application specific client 2 requests the VAE client 2 to configure dynamic group corresponding to the dynamic group information (e.g. dynamic group ID, group definition, group leader).
Each VAE client generates ProSe Layer-2 Group ID independently based on the provisioned ProSe Layer-2 Group ID(s) generation rules for its group information or the VAE client 2 assigns ProSe Layer-2 Group ID from the pool of configured ProSe Layer-2 Group IDs.
VAE client may further announce the dynamic group information including the corresponding ProSe Layer-2 Group ID to the other VAE clients within the PC5 communication proximity on a PC5 channel dedicated for V5-AE communications, enabling more V2X UEs to join the dynamic group.
Once the on-network dynamic group is created as defined in subclause 9.12.3, the VAE client notifies the VAE server about changes in the group (i.e. UE joins or leaves the group) and finally the V2X application specific server is notified with such information.
Upon receipt of the identity list notification from the VAE client, the VAE server further notifies the V2X application specific server about the newly joined or left group member(s).
The procedure for on-network dynamic group information (e.g. group leader) update is illustrated in Figure 9.12.6.2-1.
Pre-conditions:
The on network dynamic group has already been defined and V2X UE A and V2X UE B are members of the group;
V2X UE A is the current group leader; and
The V2X application specific client in V2X UE A has determined to update the group information (e.g., update group leader ID from identity of V2X UE A to identity of V2X UE B) and informed the updates and other relevant information about the update (e.g. if the update is temporary, like time bound, or permanent) to VAE client A to update the group information.
The VAE client A sends a Dynamic group information update request to the VAE server. The request includes the group-ID of the group for which group information update request is sent. The request also includes the updated group information (e.g. identity of V2X UE B as group leader ID) and other relevant information about the update (e.g. if the update to the group information are temporary and time bound or permanent).
Upon receiving the Dynamic group information update request from VAE client A, the VAE server checks for the V2X user authorization to update the group information. If required, the VAE server also checks validity of the updated group information (e.g. if the request is to update the group leader ID to V2X UE B, the VAE server checks with V2X application specific server about the capabilities of the proposed group leader V2X UE B to ensure it is capable of sufficient fuel, sensors and applications to communicate and coordinate with other group members to act as group leader). If required, then the VAE server consults with V2X application specific server to ratify the updated group information or seek changes to the requested update (e.g. a different V2X UE as group leader). If the authorization fails or if the updated group information is not valid, then steps 3 to 6 are skipped.
If the update in group information requires consent from other group member(s) (e.g. consent from the proposed new group leader, V2X UE B, to accept the role of group leader), then the VAE server obtains the consent from the user as specified in clause 9.12.6.4. This step is skipped if user consent is not required.
The VAE server sends the Dynamic group information update change response to VAE client A indicating success or failure. If:
the request was authorized but the updated group information was not valid, as determined in step 2; or
a reject response to the Dynamic group information update consent request was received from VAE client B;
then, the VAE server may include suggestions for the updated group information (e.g. identity of the V2X UE C as potential group leader). These suggestions are based on consultation with the V2X application specific server.
Upon successful update of the group document, the VAE server triggers a group information update notification to other group members and to the V2X application specific server.
The procedure for on-network dynamic group information (e.g. group leader) update is illustrated in Figure 9.12.6.3-1.
Pre-conditions:
The on network dynamic group has already been defined and V2X UE A and V2X UE B are members of the group;
V2X UE A is the current group leader; and
The V2X application specific server has determined to update the group information (e.g., update group leader ID from identity of V2X UE A to identity of V2X UE B) and informed the updates and other relevant information about the update (e.g. if the update is temporary, like time bound, or permanent) to the VAE server to update the group information.
If the update in group information requires consent from the group member(s) (e.g. consent from the proposed new group leader, V2X UE B, to accept the role of group leader), then the VAE server obtains the consent from the user as specified in clause 9.12.6.4. This step is skipped if user consent is not required.
If required (e.g. when group leader ID is being changed from V2X UE A to V2X UE B), the VAE server sends Dynamic group information update indication to the VAE client A about the possible update to group information.
Upon receiving the indication from the VAE server, the VAE client A notifies the V2X application specific client A about the possible update to group information.
Upon successful update of the group document, the VAE server triggers a Dynamic group information update notification to other group members and to the V2X application specific server.
The procedure for the VAE server to take consent form the user is illustrated in Figure 9.12.6.4-1.
Pre-conditions:
VAE client A has initiated dynamic group information update procedure as specified in clause 9.12.6.2, or the V2X application specific server has determined to update the dynamic group information.
If the update in group information requires consent from other group member(s) (e.g. consent from the proposed new group leader, V2X UE B, to accept the role of group leader), then the VAE server sends a dynamic group information update consent request to VAE client B. The request includes the group-ID of the group for which the request is sent. The request also includes other relevant information about the update (e.g. if the update to the group information are temporary and time bound or permanent).
The VAE client B notifies the V2X application specific client B about the Dynamic group information update consent request. The V2X application specific client or the V2X user decides to accept or reject the request.
The VAE client B sends a Dynamic group information update consent response to the VAE server. The response includes the decision whether the request is accepted or rejected.
This subclause provides procedures to update dynamic group information of an off-network V2X dynamic group.
The procedure for off-network dynamic group information update procedure is illustrated in Figure 9.12.7-1.
Pre-conditions:
The off network dynamic group has already been defined and V2X UE A and V2X UE B are members of the group;
V2X UE A is the current group leader;
The V2X application specific client in V2X UE A has determined to update the group information (e.g., update group leader ID from identity of V2X UE A to identity of V2X UE B) and informed the updates and other relevant information about the update (e.g. if the update is temporary, like time bound, or permanent) to the VAE client in V2X UE A to update the group information.
If the update in group information requires consent from other group member(s) (e.g. consent from the proposed new group leader, V2X UE B, to accept the role of group leader), then the VAE client sends a dynamic group information update consent request to VAE client B. The request includes the updated group information along with the group-ID of the group. The request also includes other relevant information about the update (e.g. if the update to the group information are temporary and time bound or permanent).
The VAE client B notifies the V2X application specific client B about the Dynamic group information update consent request and the V2X application specific client or the V2X user decides to accept or reject the request.
The VAE client B sends a Dynamic group information update response to the VAE client A. The response includes the decision whether the request is accepted or rejected.