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.11  V2X application resource managementWord‑p. 57

9.11.1  GeneralWord‑p. 57

The VAE server utilizes the NRM server of the SEAL to support the network resource management aspects towards the V2X applications. The VAE server supports the V2X UEs connected to EPS networks of different PLMN operators.

9.11.2  Information flowsWord‑p. 57

9.11.2.1  V2X application requirement requestWord‑p. 57

Table 9.11.2.1-1 describes the information flow V2X application requirement request from the V2X application specific server to the VAE server.
Information Element Status Description
V2X UE IDM (NOTE)Identity of the V2X UE for which V2X application requirement is initiated
V2X group IDM (NOTE)Identity of the V2X group for which the V2X application requirement is initiated
V2X service IDMThe V2X service ID for which application requirement corresponds to
V2X application requirementMThe requirement for application change. E.g. service levels for application service
End point informationMThe end point information to which the notification shall be sent
NOTE:
Either of the information element should be present.
Up

9.11.2.2  V2X application requirement responseWord‑p. 58

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

9.11.2.3  V2X application requirement notificationWord‑p. 58

Table 9.11.2.3-1 describes the information flow V2X application requirement notification from the VAE server to the V2X application specific server.
Information Element Status Description
ResultMThe result of the network resource adaptation corresponding to the V2X application requirement
Up

9.11.3  V2X application resource adaptationWord‑p. 58

9.11.3.1  GeneralWord‑p. 58

This subclause describes the procedure for V2X application resource adapation where the VAE server maps the V2X application requirement to network resource request for single or groups of V2X UEs.

9.11.3.2  ProcedureWord‑p. 58

Figure 9.11.3.2-1 illustrates the procedure where the VAE server supports V2X application resource adaptation.
Pre-conditions:
  1. The VAE server has the KPI information for the V2X services.
  2. The VAE server is provided with the network monitoring information as per the subclause A.3.
  3. The VAE server is configured with the NRM server information.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.11.3.2-1: V2X application resource adaptation
Up
Step 1.
The V2X application specific server sends a V2X application requirement request to the VAE server for an adaptation of the V2X service operation per V2X UE or per group of UEs.
Step 2.
The VAE server translates the V2X application requirement to different network resource requirement for group of users, which may be a subset of V2X UEs within the V2X group that will be affected by application adaptation.
Step 3.
If the V2X application requirement is successfully translated to the network resource requirement, the VAE server sends a V2X application requirement response to the V2X application specific server.
Step 4.
The VAE server performs network resource adaptation by interacting with the NRM server as specified in the TS 23.434 for the V2X application requirement received in step 1.
Step 5.
Based on the result of the network resource adaptation in step 4 corresponding to step 1, the VAE server sends a V2X application requirement notification to the V2X application specific server.
Up

9.12  Dynamic group managementWord‑p. 59

9.12.1  GeneralWord‑p. 59

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).
Up

9.12.2  Information flowsWord‑p. 59

9.12.2.1  Push Layer-2 group ID mappingWord‑p. 59

Table 9.12.2.1-1 describes the information flow push layer-2 group ID mapping from the VAE server to the VAE client and between the VAE clients.
Information Element Status Description
Dynamic group informationMGroup information including dynamic group ID, group definition, group leader ID
ProSe Layer-2 Group IDMProSe Layer-2 Group ID corresponding to the dynamic group information
Up

9.12.2.2  Configure dynamic group requestWord‑p. 60

Table 9.12.2.2-1 describes the information flow for configure dynamic group request from the V2X application specific sever to the VAE server.
Information Element Status Description
Dynamic group informationMGroup information including dynamic group ID, group definition, group leader ID
Endpoint informationMEnd point information to which the configure dynamic group notification has to be sent
Up

9.12.2.3  Configure dynamic group responseWord‑p. 60

Table 9.12.2.3-1 describes the information flow for configure dynamic group response from the VAE server to the V2X application specific sever.
Information Element Status Description
ResultMResult from the VAE server in response to the configure dynamic group request
Up

9.12.2.4  Configure dynamic group notificationWord‑p. 60

Table 9.12.2.4-1 describes the information flow for configure dynamic group notification from the VAE server to the V2X application specific sever.
Information Element Status Description
Dynamic group informationMGroup information including dynamic group ID, UE ID (joined or left UE(s))
Up

9.12.2.5  Identity list notificationWord‑p. 60

Table 9.12.2.5-1 describes the information flow identity list notification from the VAE client to the VAE server.
Information Element Status Description
Dynamic group informationMGroup information including dynamic group ID, UE ID (joined or left UE(s))
Up

9.12.2.6  Dynamic group information update request |R17|Word‑p. 60

Table 9.12.2.6-1 describes the information flow for dynamic group information update request from the VAE Client to the VAE server.
Information element Status Description
Dynamic group information to updateMDynamic group information to update, e.g. group leader ID
Endpoint informationMEnd point information to which response has to be sent
Up

9.12.2.7  Dynamic group information update response |R17|Word‑p. 61

Table 9.12.2.7-1 describes the information flow for dynamic group information update response from the VAE server to the VAE client.
Information element Status Description
ResultMResult from the VAE server in response to the Dynamic group information update request.
Up

9.12.2.8  Dynamic group information update consent request |R17|Word‑p. 61

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.
Information element Status Description
Information for consentMDynamic group information for consent, e.g. group leader ID
Up

9.12.2.9  Dynamic group information update consent response |R17|Word‑p. 61

Table 9.12.2.9-1 describes the information flow for dynamic group information update consent response from the VAE client to the VAE server.
Information element Status Description
ResultMResult from the VAE server in response to the Dynamic group information update consent request.
Up

9.12.2.10  Dynamic group information update notification |R17|Word‑p. 61

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.
Information element Status Description
Dynamic group informationMDynamic group information which has been updated, e.g. group leader ID
Up

9.12.2.11  Dynamic group information update indication |R17|Word‑p. 61

Table 9.12.2.11-1 describes the information flow for group information update indication from the VAE server to the VAE client.
Information element Status Description
Dynamic group informationMDynamic group information for which update request has been received, e.g. group leader ID
Up

9.12.2.12  Dynamic group information update consent request (Off network) |R17|Word‑p. 62

Table 9.12.2.12-1 describes the information flow for group information update request from the VAE client to the VAE client.
Information element Status Description
Information for consentMDynamic group information for consent, e.g. group leader ID
Up

9.12.2.13  Dynamic group information update consent response (Off network) |R17|Word‑p. 62

Table 9.12.2.13-1 describes the information flow for group information update consent response from the VAE client to the VAE server.
Information element Status Description
ResultMResult from the VAE server in response to the Dynamic group information update consent request.
Up

9.12.3  On-network dynamic group creationWord‑p. 62

9.12.3.1  GeneralWord‑p. 62

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.

9.12.3.2  ProcedureWord‑p. 62

The procedure for on-network dynamic group creation is illustrated in Figure 9.12.3.2-1.
Pre-condition:
  1. V2X application dynamic group is defined at the V2X application specific server with V2X UE assigned as dynamic group leader.
  2. VAE server has a pool of the ProSe Layer-2 Group IDs that can be assigned to dynamic groups
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.3.2-1: On-network dynamic group creation
Figure 9.12.3.2-1: On-network dynamic group creation
(⇒ copy of original 3GPP image)
Up
Step 1.
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).
Step 2.
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.
Step 3.
The VAE server responds to the V2X application specific server for the request to configure dynamic group.
Step 4.
The VAE server triggers a push request including ProSe Layer-2 Group ID corresponding to the dynamic group information to the VAE client.
Step 5.
The VAE client stores the received PC5 communication parameters corresponding to the dynamic group information received from the VAE server.
Up

9.12.4  Off-network dynamic group creationWord‑p. 63

9.12.4.1  GeneralWord‑p. 63

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.

9.12.4.2  ProcedureWord‑p. 63

The procedure for off-network dynamic group creation is illustrated in Figure 9.12.4.2-1.
Pre-condition:
  1. VAE clients are provisioned ProSe Layer-2 Group ID(s) generation rules corresponding to the group information or
  2. VAE client(s) are configured with the unique pool of ProSe Layer-2 Group IDs, when they are in coverage area of the VAE server.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.4.2-1: Off-network dynamic group creation
Up
Step 1.
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).
Step 2.
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.
Step 3.
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.
Step 4.
The VAE client stores the PC5 communication parameters corresponding to the dynamic group information received from another VAE client.
Up

9.12.5  On-network dynamic group notificationWord‑p. 64

9.12.5.1  GeneralWord‑p. 64

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.

9.12.5.2  ProcedureWord‑p. 64

The procedure for on-network dynamic group notification is illustrated in Figure 9.12.5.2-1.
Pre-condition:
  1. V2X application dynamic group is created as defined in subclause 9.12.3.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.5.2-1: On-network dynamic group notification
Up
Step 1.
The VAE client sends identity list notification to the VAE server about group member changes.
Step 2.
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).

9.12.6  On network dynamic group information update procedure |R17|Word‑p. 65

9.12.6.1  GeneralWord‑p. 65

This subclause provides procedures to update dynamic group information of an on-network V2X dynamic group.

9.12.6.2  VAE client initiated on network dynamic group information update procedureWord‑p. 65

The procedure for on-network dynamic group information (e.g. group leader) update is illustrated in Figure 9.12.6.2-1.
Pre-conditions:
  1. The on network dynamic group has already been defined and V2X UE A and V2X UE B are members of the group;
  2. V2X UE A is the current group leader; and
  3. 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.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.6.2-1: VAE client initiated on network dynamic group information update procedure
Up
Step 1.
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).
Step 2.
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.
Step 3.
If the request from the VAE client is authorized and the updated group information is valid, the VAE server acknowledges the VAE client A.
Step 4.
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.
Step 5.
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.
Step 6.
If the group information update request was successful, the VAE server updates the group document.
Step 7.
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.
Up

9.12.6.3  VAE server initiated on network dynamic group information update procedureWord‑p. 67

The procedure for on-network dynamic group information (e.g. group leader) update is illustrated in Figure 9.12.6.3-1.
Pre-conditions:
  1. The on network dynamic group has already been defined and V2X UE A and V2X UE B are members of the group;
  2. V2X UE A is the current group leader; and
  3. 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.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.6.3-1: VAE server initiated on network dynamic group information update procedure
Up
Step 1.
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.
Step 2.
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.
Step 3.
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.
Step 4.
If group leader information update request is successful, the VAE server updates the group document.
Step 5.
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.
Up

9.12.6.4  VAE Server taking consent from userWord‑p. 67

The procedure for the VAE server to take consent form the user is illustrated in Figure 9.12.6.4-1.
Pre-conditions:
  1. 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.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.6.4-1: VAE Server taking consent from user procedure
Up
Step 1.
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).
Step 2.
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.
Step 3.
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.
Up

9.12.7  Off network dynamic group information update procedure |R17|Word‑p. 68

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:
  1. The off network dynamic group has already been defined and V2X UE A and V2X UE B are members of the group;
  2. V2X UE A is the current group leader;
  3. 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.
Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.12.7-1: Off network dynamic group information update procedure
Up
Step 1.
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).
Step 2.
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.
Step 3.
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.
Step 4.
If the group information update consent request is successful, then the VAE client A sends notification to other group members.
Up

9.13  Network situation and QoS monitoring and reportingWord‑p. 69

9.13.1  GeneralWord‑p. 69

The VAE server supports monitoring of 3GPP systems' network situation for V2X services. The VAE server receives and processes access network-related monitoring events/reports from SCEF (EPS entity of the 3GPP network system) as specified in TS 23.682. The monitoring events/report may also include RAN-related resource/traffic situation information and QoS related notifications per UE or group of UEs. The VAE server initiates monitoring of the QoS for single or aggregately for groups of vehicles (supporting a V2X service and being in proximity) having ongoing sessions. The information from V2X UE related to monitoring events (e.g. location, groups, resource usage) can be available at the VAE server using the network resource management and location management services of the SEAL.
Up

9.13.2  Information flowsWord‑p. 70

9.13.2.1  Monitoring requestWord‑p. 70

The information flow monitoring request from VAE server (acting as SCS/AS) to SCEF over T8 reference point is specified in clause 5.6 in TS 23.682 and clause 5.8 in TS 23.682 (when monitoring request comprises Network Status Request).

9.13.2.2  Monitoring responseWord‑p. 70

The information flow monitoring response from SCEF to VAE server (acting as SCS/AS) over T8 reference point is specified in clause 5.6 in TS 23.682 and clause 5.8 in TS 23.682 (when monitoring request comprises Network Status Response).

9.13.2.3  Monitoring reportWord‑p. 70

The information flow monitoring report from the SCEF to the VAE server over T8 reference point is specified in clause 5.6 of TS 23.682, clause 5.8 of TS 23.682(when monitoring report comprises Network Status Information Report) and clause 5.11 of TS 23.682(when monitoring report comprises notification of QoS/bearer level events).
Up

9.13.3  ProcedureWord‑p. 70

The VAE server acts as SCS/AS and initiates the procedure for monitoring with the SCEF as specified in the clause 5.6 in TS 23.682 and clause 5.8 in TS 23.682 by including the V2X application information corresponding to one or many V2X UEs.
The SCEF provides the monitoring reports (including the RAN related network situation information and QoS notification information for the corresponding V2X application, V2X UE or group of V2X UEs) to the VAE server as specified in the clause 5.6 in TS 23.682, clause 5.8 in TS 23.682 and clause 5.11 in TS 23.682.
Up

Up   Top   ToC