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.17  V2X groupcast/broadcast configuration by VAE layer |R17|Word‑p. 80

9.17.1  GeneralWord‑p. 80

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 flowsWord‑p. 80

    9.17.2.1  V2V configuration requirement requestWord‑p. 80

    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 responseWord‑p. 80

    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 requestWord‑p. 81

    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 responseWord‑p. 81

    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 requestWord‑p. 81

    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 responseWord‑p. 82

    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 messageWord‑p. 82

    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 layerWord‑p. 83

    9.17.3.1  GeneralWord‑p. 83

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

    9.17.3.2  ProcedureWord‑p. 83

    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, Figure 9.17.3.2-1: V2V groupcast/broadcast configuration by VAE layer
    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 layerWord‑p. 84

    9.17.4.1  GeneralWord‑p. 84

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

    9.17.4.2  ProcedureWord‑p. 84

    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, Figure 9.17.4.2-1: V2X groupcast/broadcast delivery by VAE layer
    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

    9.18  Local MBMS support |R17|Word‑p. 85

    For local MBMS based MBMS data delivery as defined in TS 23.285, the BM‑SC can be provided with the local MBMS information (i.e. M1 interface information including transport network IP Multicast Address, IP address of multicast source and C-TEID, as well as MB2‑U or xMB‑U interface information including IP address and UDP port number for the user plane) from the V2X application plane. Such local MBMS information can be pre-configured in the VAE server based on service requirements or deployment needs. The VAE server may request SEAL NRM server to establish the MBMS bearers by providing the local MBMS information as described in subclause 14.3.4.3.2 of TS 23.434 and subclause 14.3.4.3.2 of TS 23.434.
    Up

    9.19  Session-oriented services |R17|Word‑p. 85

    9.19.1  GeneralWord‑p. 85

    The VAE layer provides support at the application layer for V2X application specific server and V2X UE to initiate session-oriented services by providing mechanisms for establishing, updating and terminating sessions.

    9.19.2  Information flowsWord‑p. 85

    9.19.2.1  Session-oriented service trigger requestWord‑p. 85

    Table 9.19.2.1-1 describes the information flow session-oriented service trigger request from the V2X application specific server to the VAE server.
    Information element Status Description
    Remote V2X UE IDMIdentity of the V2X UE (VAE client) which is the remote vehicle.
    V2X service IDMThe V2X service ID for which application requirement corresponds to.
    V2X application specific server identity informationMIdentity information of the V2X application specific server.
    Session IDOThe session identifier to be used for the session-oriented service.
    V2X application QoS requirements for the sessionOThe application QoS requirements (reliability, delay, jitter) for the session-oriented service.
    Up

    9.19.2.2  Session-oriented service trigger responseWord‑p. 85

    Table 9.19.2.2-1 describes the information flow session-oriented service trigger response from the VAE server to the V2X application specific server.
    Information element Status Description
    AcknowledgementMAcknowledgement for the request
    Up

    9.19.2.3  Session-oriented service establishment notificationWord‑p. 85

    Table 9.19.2.3-1 describes the information flow session-oriented service establishment notification from the VAE server to the V2X application specific server.
    Information element Status Description
    ResultMThe result indicating success or failure to establish session-oriented service
    Remote V2X UE IDMIdentity of the V2X UE (VAE client) which is the remote vehicle.
    Session IDO (NOTE)The session identifier to be used for the session-oriented service.
    NOTE:
    This IE is present when Result is success. It is generated by the VAE server if not provided by the requester.
    Up

    9.19.2.4  Session-oriented change trigger requestWord‑p. 86

    Table 9.19.2.4-1 describes the information flow session-oriented change trigger request from the V2X application specific server to the VAE server.
    Information element Status Description
    Session IDMThe session identifier of the session-oriented service.
    V2X application QoS requirements for the sessionMThe application QoS requirements (reliability, delay, jitter) for the session-oriented service that is to be updated.
    Up

    9.19.2.5  Session-oriented change trigger responseWord‑p. 86

    Table 9.19.2.5-1 describes the information flow session-oriented change trigger response from the VAE server to the V2X application specific server.
    Information element Status Description
    AcknowledgementMAcknowledgement for the request
    Up

    9.19.2.6  Session-oriented service change notificationWord‑p. 86

    Table 9.19.2.6-1 describes the information flow session-oriented service change notification from the VAE server to the V2X application specific server.
    Information element Status Description
    ResultMThe result indicating success or failure to change session-oriented service
    Up

    9.19.2.7  Session-oriented termination trigger requestWord‑p. 86

    Table 9.19.2.7-1 describes the information flow session-oriented termination trigger request from the V2X application specific server to the VAE server.
    Information element Status Description
    Session IDMThe session identifier of the session-oriented service.
    Up

    9.19.2.8  Session-oriented termination trigger responseWord‑p. 87

    Table 9.19.2.8-1 describes the information flow session-oriented termination trigger response from the VAE server to the V2X application specific server.
    Information element Status Description
    AcknowledgementMAcknowledgement for the request
    Up

    9.19.2.9  Session-oriented service termination notificationWord‑p. 87

    Table 9.19.2.9-1 describes the information flow session-oriented service termination notification from the VAE server to the V2X application specific server.
    Information element Status Description
    ResultMThe result indicating success or failure to terminate session-oriented service
    Up

    9.19.3  UE initiated session-oriented serviceWord‑p. 87

    9.19.3.1  GeneralWord‑p. 87

    The VAE layer provides support at the application layer for V2X UE to initiate session-oriented services by providing mechanisms for establishing, updating and terminating sessions.

    9.19.3.2  UE initiated session-oriented service establishmentWord‑p. 87

    Pre-conditions:
    • The V2X UE (acting as remote controller) has been authenticated for using session-oriented services and has connected to the VAE server.
    • The V2X application-specific client has triggered the VAE client to establish a session with the remote V2X UE (vehicle).
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.3.2-1: Procedure for establishing a UE initiated session-oriented service between the VAE client (remote controller) and the VAE client (remote vehicle)
    Up
    Step 1.
    The VAE client (acting as remote controller) sends a trigger request to the VAE server to establish a session-oriented service with one or more V2X UEs (remote vehicle). It may include the identity of the VAE client, the identity of the service session, the V2X service ID, the "type" or "QoS requirements" of the session, service information (e.g. geo-referenced information for tele-operated driving service in the form of geographical area where the service is expected to be delivered or in the form of expected/planned vehicle trajectory, or time interval during which the service is expected) and requirements (e.g. reporting configuration).
    Step 2.
    The VAE server checks whether the VAE client is authorized to establish session-oriented service with one or more V2X UEs (remote vehicles). The VAE server provides a session-oriented service trigger response to the VAE client indicating the ability or inability of VAE server to initiate a session-oriented service with the VAE client. The VAE server performs the procedure to establish session oriented service with VAE client (e.g. remote vehicle).
    Up

    9.19.3.3  UE initiated session-oriented service updateWord‑p. 88

    Pre-condition:
    • The VAE client (remote controller) has established a session-oriented service with a VAE client (remote vehicle) via the VAE server.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.3.3-1: Procedure for updating an UE initiated session-oriented service between the VAE client (remote controller) and the VAE client (remote vehicle)
    Up
    Step 1.
    The VAE client (acting as remote controller) sends a change trigger request to the VAE server to update the session-oriented service to one or more VAE clients (remote vehicle) including the identity of the service session, updates to service information (e.g. activated services, updates to vehicle trajectory), requirements (e.g. change of network/QoS requirements), or server information (e.g. change of VAE server).
    Step 2.
    The VAE server provides a session-oriented change trigger response to the VAE client indicating the ability or inability of VAE server to continue the session-oriented service with the VAE client with the updated conditions. The VAE server performs the procedure to change session oriented service with VAE client (e.g. remote vehicle).
    Up

    9.19.3.4  UE initiated session-oriented service terminationWord‑p. 88

    Pre-condition:
    • The VAE client (remote controller) has established a session-oriented service with the VAE client (remote vehicle).
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.3.4-1: Procedure for terminating an UE initiated session-oriented service between the VAE client (remote controller) and the VAE client (remote vehicle)
    Up
    Step 1.
    The VAE client (acting as remote controller) sends a session-oriented termination trigger request to the VAE server to terminate the session (e.g. end of session with VAE server or requirements for session-oriented service not satisfied) with one or more V2X UEs (remote vehicles) including the identity of the service session.
    Step 2.
    The VAE server sends a session-oriented termination trigger response to the VAE client indicating the result of the session-oriented service termination with one or more V2X UEs (remote vehicles). The VAE server performs the session-oriented service termination procedure to terminate session oriented service with VAE client (e.g. remote vehicle).
    Up

    9.19.4  V2X application specific server triggered session-oriented serviceWord‑p. 89

    9.19.4.1  GeneralWord‑p. 89

    The VAE layer provides support at the application layer for V2X application specific server triggered session-oriented services by providing mechanisms for establishing, updating and terminating sessions.

    9.19.4.2  Triggering of session-oriented service establishmentWord‑p. 89

    Pre-conditions:
    • The V2X application-specific server has decided to trigger the session-oriented service.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.4.2-1: Triggering of session-oriented service establishment
    Up
    Step 1.
    The V2X application-specific server triggers the VAE server to initiate a session-oriented service to the VAE client. This request can include information such as the identity of the VAE client, the identity of the V2X application specific server, the identity of the service session, the V2X service ID and the "type" or "QoS requirements" of the session.
    Step 2.
    The VAE server provides a session-oriented service trigger response to the V2X application-specific server indicating the ability or inability of VAE server to initiate a session-oriented service with the VAE client.
    Up

    9.19.4.3  Triggering of session-oriented service updateWord‑p. 89

    Pre-conditions:
    • The VAE server has established a session-oriented service with the VAE client as described in clause 9.19.5.2.
    • The V2X application-specific server needs to update parameters of the session.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.4.3-1: Triggering of session-oriented service update
    Up
    Step 1.
    The V2X application-specific server provides the VAE server with the identity of the session and the update of session parameters, e.g. change of QoS requirements of the session.
    Step 2.
    The VAE server provides a session-oriented service update response to the V2X application specific server including the ability or inability to continue the session-oriented service with the VAE client with the updated conditions.

    9.19.4.4  Triggering of session-oriented service terminationWord‑p. 90

    Pre-conditions:
    • The VAE server has established a session-oriented service with the VAE client as described in clause 9.19.5.2.
    • The V2X application specific server has decided to terminate the session-oriented service.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.4.4-1: Triggering of session-oriented service termination
    Up
    Step 1.
    The V2X application-specific server provides the VAE server with a request to terminate the session-oriented service with the VAE client. It may include the identity of the service session.
    Step 2.
    The VAE server provides a session-oriented service termination response to the V2X application-specific server that the session can be terminated.

    9.19.5  Session-oriented serviceWord‑p. 90

    9.19.5.1  GeneralWord‑p. 90

    The VAE layer provides support at the application layer for session-oriented services by providing mechanisms for establishing, updating and terminating sessions.

    9.19.5.2  Session-oriented service establishmentWord‑p. 90

    Pre-conditions:
    • The V2X UE has been authenticated for using session-oriented services and has connected to the V2X application server.
    • The VAE server has agreed to establish a session upon the request from the V2X application specific server or from the VAE client.
    • The V2X application specific client has subscribed with the VAE client to receive notifications related to session-oriented service and the V2X application specific server has subscribed with VAE server to receive notifications related to session-oriented service.
    • The V2X application specific client for the terminating V2X UE has been informed about the already negotiated session oriented service to VAE client.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.5.2-1: Procedure for establishing a session-oriented service between the VAE server and the VAE client
    Up
    Step 1.
    The VAE server sends a request to one or more VAE clients to establish a session-oriented service including identity of the VAE client, identity of the session, V2X service ID and reporting configuration.
    Step 2.
    The VAE client sends a session-oriented service response to the VAE server indicating approval of session establishment request by the VAE server.
    Step 3.
    If V2X application specific server has triggered then, the VAE server sends a session-oriented service establish notification to the V2X application-specific server.
    Step 4.
    The VAE client sends a session-oriented service establish notification to the V2X application-specific client.
    Up

    9.19.5.3  Session-oriented service updateWord‑p. 91

    Pre-condition:
    • The VAE server has established a session-oriented service with the VAE client.
    • The VAE server has received a session-oriented service update from the V2X application-specific server or from the VAE client or a change in QoS and network conditions from 3GPP network system.
    • The V2X application specific client has subscribed with the VAE client to receive notifications related to session-oriented service and the V2X application specific server has subscribed with VAE server to receive notifications related to session-oriented service.
    • The VAE server has agreed to continue the session-oriented service with the VAE client with the updated conditions upon the request from the V2X application specific server or from the VAE client.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.5.3-1: Procedure for updating a session-oriented service between the VAE server and the VAE client
    Up
    Step 1.
    The VAE server sends a change request to one or more VAE clients including the identity of the session, updates requirements (e.g. change of network/QoS requirements), or server information (e.g. change of VAE server).
    Step 2.
    The VAE client sends a change response to the VAE server indicating acceptance of the change request by the VAE server.
    Step 3.
    If V2X application specific server has triggered then, the VAE server sends a session-oriented service change notification to the V2X application-specific server.
    Step 4.
    The VAE client sends a session-oriented service change notification to the V2X application-specific client.
    Up

    9.19.5.4  Session-oriented service terminationWord‑p. 92

    Pre-condition:
    • The VAE server has established a session-oriented service with the VAE client.
    • The VAE server has received a session-oriented service termination request from the V2X application-specific server or from the VAE client or a change in QoS or network conditions from 3GPP network system that prevents the VAE server from continuing the session-oriented service.
    • The V2X application specific client has subscribed with the VAE client to receive notifications related to session-oriented service and the V2X application specific server has subscribed with VAE server to receive notifications related to session-oriented service.
    • The VAE server has indicated to terminate the session-oriented service with the VAE client upon the request from the V2X application specific server or from the VAE client.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.19.5.4-1: Procedure for terminating a session-oriented service between the VAE server and the VAE client
    Up
    Step 1.
    The VAE server sends a session-oriented termination request to the VAE client to terminate the session (e.g. end of session with VAE server or requirements for session-oriented service not satisfied) including the identity of the session.
    Step 2.
    The VAE client sends a session-oriented termination response to the VAE server indicating acceptance of the termination request by the VAE server.
    Step 3.
    If V2X application specific server has triggered then, the VAE server sends a session-oriented service termination notification to the V2X application-specific server.
    Step 4.
    The VAE client sends a session-oriented service termination notification to the V2X application-specific client.
    Up

    9.20  Monitoring and control of QoS for eV2X communications |R17|Word‑p. 92

    9.20.1  GeneralWord‑p. 92

    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 flowsWord‑p. 93

    9.20.3  Subscription ProcedureWord‑p. 93

    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, Figure 9.20.3-1: Subscription for monitoring and control of QoS for eV2X communications
    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 ProcedureWord‑p. 93

    Pre-condition:
    1. The subscription procedure specified in clause 9.20.3 is performed.
    Copy of original 3GPP image for 3GPP TS 23.286, Figure 9.20.4-1: Notification for monitoring and control of QoS for eV2X communications
    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