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.4.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.20 Monitoring and control of QoS for eV2X communications  9.20.1 General  9.20.2 Information flows  9.20.2.1 Service adaptation and QoS control subscription request  9.20.2.2 Service adaptation and QoS control subscription response  9.20.2.3 Service requirement adaptation notification request  9.20.2.4 Service requirement adaptation notification response  9.20.3 Subscription Procedure  9.20.4 Notification Procedure 
...

 

9.20  Monitoring and control of QoS for eV2X communications |R17|  p. 93

9.20.1  General  p. 93

5GS supports eV2X communications with extended QoS monitoring and reporting.The VAE layer utilizes these monitoring and reporting mechanisms to support control of QoS for eV2X communications. The V2X application specific server subscribes to service adaptation and QoS control events from the VAE layer and receives notifications about the relevant service requirement adaptations and corresponding QoS changes.

9.20.2  Information flows  p. 94

9.20.2.1  Service adaptation and QoS control subscription request |R18|  p. 94

Table 9.20.2.1-1 describes the information flow Service adaptation and QoS control subscription request from the V2X application specific server to the VAE server.
Information element Status Description
V2X group IDM (see NOTE)Identity of the V2X group for which the service adaptation and QoS control subscription is initiated.
V2X service IDM (see NOTE)The V2X service ID for which subscription corresponds to.
V2X UE IDM (see NOTE)The V2X UE ID for which subscription corresponds to.
NOTE:
Either of the information element should be present.
Up

9.20.2.2  Service adaptation and QoS control subscription response |R18|  p. 94

Table 9.20.2.2-1 describes the information flow for VAE server to respond for Service adaptation and QoS control subscription request from the V2X application specific server.
Information element Status Description
ResultMResult from the VAE server in response to subscription request indicating success or failure.
Subscription ID (see NOTE)OIdentifier of a successful subscription.
NOTE:
This IE is included when the Result indicates success
Up

9.20.2.3  Service requirement adaptation notification request |R18|  p. 94

Table 9.20.2.3-1 describes the information flow for service requirement adaptation notification request from VAE server to the V2X application specific server.
Information element Status Description
Subscription IDMIdentifier of the subscription for this notification.
List of V2X UEs informationOThe information of the V2X UEs which are affected by this service requirement adaptation notification.
> V2X UE IDMThe identifier of V2X UE.
QoS change informationMThe actual or expected QoS change information.
Up

9.20.2.4  Service requirement adaptation notification response |R18|  p. 94

Table 9.20.2.4-1 describes the information flow for service requirement adaptation notification response from V2X application specific server to the VAE server.
Information element Status Description
Subscription IDMIdentifier of the subscription for this notification.
Acknowledgement Result (see NOTE)MIndicates positive or negative acknowledgement.
List of V2X UEs information (see NOTE)OThe information of the V2X UEs which are affected by the service requirement adaptation and requires QoS change to be applied.
> V2X UE IDMThe identifier of V2X UE.
NOTE:
If Acknowledgement Result IE indicates positive, then List of V2X UEs information IE is included.
Up

9.20.3  Subscription Procedure  p. 95

Pre-conditions:
  1. The VAE server includes an Application Function (AF) functionality, as defined in TS 23.287.
  2. The VAE server has subscriptions with SEAL servers to receive V2X service-related information (e.g. UE IDs, location, group, configuration info, etc.).
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.20.3-1: Subscription for monitoring and control of QoS for eV2X communications
Figure 9.20.3-1: Subscription for monitoring and control of QoS for eV2X communications
(⇒ copy of original 3GPP image)
Up
Step 1.
The V2X application specific server sends a service adaptation and QoS control subscription request to the VAE server.
Step 2.
The VAE server, who acts as an AF, subscribes to QoS monitoring service from 5GS (e.g. PCF/NWDAF). This subscription may be active for a certain period of time or a given geographical area. The monitoring may either include the request for QoS sustainability events as specified in TS 23.288, or can include a QoS change notification requests as provided by SMF and specified in TS 23.287. The reporting may be configured by the application enabler layer for a given area, time, periodicity etc taking into account the service requirement and other parameters (e.g. expected congestion in certain area, time of the day, road conditions).
Step 3.
The VAE server sends a service adaptation and QoS control subscription response indicating success or failure of subscription.
Up

9.20.4  Notification Procedure  p. 95

Pre-condition:
  1. The subscription procedure specified in clause 9.20.3 is performed.
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.20.4-1: Notification for monitoring and control of QoS for eV2X communications
Figure 9.20.4-1: Notification for monitoring and control of QoS for eV2X communications
(⇒ copy of original 3GPP image)
Up
Step 1.
Based on the subscription, as specified in TS 23.287, 5GS provides the extended QoS monitoring report, over N33 interface. This report may come either from NWDAF or SMF via PCF/NEF.
Step 2.
The VAE server, based on the monitoring events (step 1) for one or multiple V2X-UEs within one service or across multiple services, may trigger a service requirement adaptation (step 3) based on the actual or expected QoS change for one or more V2X services.
Step 3.
The VAE server sends a service requirement adaptation notification request to V2X application specific server to identify the action which is needed, based on the actual or expected QoS change. This could be the adaptation of the Level of Automation (LoA) for one or more V2X-UEs or V2X services.
Step 4.
The V2X application specific server decides whether to adapt the service requirement based on step 3.
Step 5.
The V2X application specific server sends a response to VAE server with a positive or negative acknowledgment. Optionally, this may include the list of a sub-set of V2X-UEs within a service for which the requirement change should be applied
Step 6.
If no QoS adaptation is required, V2X application layer may adapt based on the adapted service requirements; and steps 7-10 are optional.
Step 7.
If a QoS adaptation is required, the VAE server, triggers the adaptation of QoS for the affected V2X-UE(s) within the service or across multiple services in close vicinity.
Step 8.
The VAE server performs network resource adaptation by interacting with the NRM server as specified in the TS 23.434.
Step 9.
The VAE server also notifies about the QoS adaptation to the V2X application specific server.
Up

Up   Top   ToC