9.19 Session-oriented services
23.2863GPPApplication layer support for Vehicle-to-Everything (V2X) servicesFunctional architecture and information flowsRelease 18TS
9.19.1 General
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 flows
.19.2.1 Session-oriented service trigger request
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.
Table 9.19.2.1-1: Session-oriented service trigger request
|
Information element |
Status |
Description |
|
Remote V2X UE ID |
M |
Identity of the V2X UE (VAE client) which is the remote vehicle. |
|
V2X service ID |
M |
The V2X service ID for which application requirement corresponds to. |
|
V2X application specific server identity information |
M |
Identity information of the V2X application specific server. |
|
Session ID |
O |
The session identifier to be used for the session-oriented service. |
|
V2X application QoS requirements for the session |
O |
The application QoS requirements (reliability, delay, jitter) for the session-oriented service. |
9.19.2.2 Session-oriented service trigger response
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.
Table 9.19.2.2-1: Session-oriented service trigger response
|
Information element |
Status |
Description |
|
Acknowledgement |
M |
Acknowledgement for the request |
9.19.2.3 Session-oriented service establishment notification
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.
Table 9.19.2.3-1: Session-oriented service establishment notification
|
Information element |
Status |
Description |
|
Result |
M |
The result indicating success or failure to establish session-oriented service |
|
Remote V2X UE ID |
M |
Identity of the V2X UE (VAE client) which is the remote vehicle. |
|
Session ID |
O (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. |
||
9.19.2.4 Session-oriented change trigger request
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.
Table 9.19.2.4-1: Session-oriented change trigger request
|
Information element |
Status |
Description |
|
Session ID |
M |
The session identifier of the session-oriented service. |
|
V2X application QoS requirements for the session |
M |
The application QoS requirements (reliability, delay, jitter) for the session-oriented service that is to be updated. |
9.19.2.5 Session-oriented change trigger response
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.
Table 9.19.2.5-1: Session-oriented change trigger response
|
Information element |
Status |
Description |
|
Acknowledgement |
M |
Acknowledgement for the request |
9.19.2.6 Session-oriented service change notification
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.
Table 9.19.2.6-1: Session-oriented service change notification
|
Information element |
Status |
Description |
|
Result |
M |
The result indicating success or failure to change session-oriented service |
9.19.2.7 Session-oriented termination trigger request
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.
Table 9.19.2.7-1: Session-oriented termination trigger request
|
Information element |
Status |
Description |
|
Session ID |
M |
The session identifier of the session-oriented service. |
9.19.2.8 Session-oriented termination trigger response
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.
Table 9.19.2.8-1: Session-oriented termination trigger response
|
Information element |
Status |
Description |
|
Acknowledgement |
M |
Acknowledgement for the request |
9.19.2.9 Session-oriented service termination notification
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.
Table 9.19.2.9-1: Session-oriented service termination notification
|
Information element |
Status |
Description |
|
Result |
M |
The result indicating success or failure to terminate session-oriented service |
9.19.3 UE initiated session-oriented service
9.19.3.1 General
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 establishment
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).
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)
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).
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).
NOTE 1: The VAE server performs the procedure specified in clause 9.19.5.2 to establish session oriented service with VAE client (e.g. remote vehicle).
NOTE 2: The resulting application session occurs over IP connectivity (Uu based) between the remote controller and the remote vehicle.
9.19.3.3 UE initiated session-oriented service update
Pre-condition:
– The VAE client (remote controller) has established a session-oriented service with a VAE client (remote vehicle) via the VAE server.
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)
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).
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).
NOTE: The VAE server performs the procedure specified in clause 9.19.5.3 to change session oriented service with VAE client (e.g. remote vehicle).
9.19.3.4 UE initiated session-oriented service termination
Pre-condition:
– The VAE client (remote controller) has established a session-oriented service with the VAE client (remote vehicle).
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)
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.
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).
NOTE: The VAE server performs the procedure specified in clause 9.19.5.4 to terminate session oriented service with VAE client (e.g. remote vehicle).
9.19.4 V2X application specific server triggered session-oriented service
9.19.4.1 General
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 establishment
Pre-conditions:
– The V2X application-specific server has decided to trigger the session-oriented service.
NOTE: The reasons that the V2X application-specific server decides to trigger the V2X application specific layer session are out of scope of the present document.
Figure 9.19.4.2-1: Triggering of session-oriented service establishment
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.
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.
NOTE: The VAE server performs the procedure specified in clause 9.19.5.2 to establish session oriented service with VAE client (e.g. remote vehicle).
9.19.4.3 Triggering of session-oriented service update
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.
Figure 9.19.4.3-1: Triggering of session-oriented service update
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.
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.
NOTE: The VAE server performs the procedure specified in clause 9.19.5.3 to change session oriented service with VAE client (e.g. remote vehicle).
9.19.4.4 Triggering of session-oriented service termination
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.
Figure 9.19.4.4-1: Triggering of session-oriented service termination
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.
2. The VAE server provides a session-oriented service termination response to the V2X application-specific server that the session can be terminated.
NOTE: The VAE server performs the procedure specified in clause 9.19.5.4 to terminate session oriented service with VAE client (e.g. remote vehicle).
9.19.5 Session-oriented service
9.19.5.1 General
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 establishment
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.
Figure 9.19.5.2-1: Procedure for establishing a session-oriented service between the VAE server and the VAE client
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.
2. The VAE client sends a session-oriented service response to the VAE server indicating approval of session establishment request by the VAE server.
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.
4. The VAE client sends a session-oriented service establish notification to the V2X application-specific client.
9.19.5.3 Session-oriented service update
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.
Figure 9.19.5.3-1: Procedure for updating a session-oriented service between the VAE server and the VAE client
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).
2. The VAE client sends a change response to the VAE server indicating acceptance of the change request by the VAE server.
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.
4. The VAE client sends a session-oriented service change notification to the V2X application-specific client.
9.19.5.4 Session-oriented service termination
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.
Figure 9.19.5.4-1: Procedure for terminating a session-oriented service between the VAE server and the VAE client
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.
2. The VAE client sends a session-oriented termination response to the VAE server indicating acceptance of the termination request by the VAE server.
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.
4. The VAE client sends a session-oriented service termination notification to the V2X application-specific client.