10 VAE layer APIs
23.2863GPPApplication layer support for Vehicle-to-Everything (V2X) servicesFunctional architecture and information flowsRelease 18TS
10.1 General
The following VAE capabilities are offered as APIs:
– VAE server APIs;
The following SEAL service APIs are specified in 3GPP TS 23.434 [6]:
– Group management server APIs;
– Location management server APIs;
– Configuration management server APIs;
– Identity management server APIs; and
– Key management server APIs.
10.2 VAE server APIs
10.2.1 General
Table 10.2.1-1 illustrates the VAE server APIs.
Table 10.2.1-1: List of VAE server APIs
|
API Name |
API Operations |
Known Consumer(s) |
Communication Type |
|
VAE_MessageDelivery API |
Deliver_DL_Message |
V2X application specific server |
Request/ Response |
|
Deliver_UL_Message |
V2X application specific server |
Subscribe/notify |
|
|
VAE_FileDistribution API |
Distribute_File |
V2X application specific server |
Request/ Response |
|
VAE_ApplicationRequirement API |
Reserve_NetworkResource |
V2X application specific server |
Subscribe/notify |
|
Notify_NetworkResource |
|||
|
VAE_DynamicGroup API |
Configure_DynamicGroup |
V2X application specific server |
Request/Response |
|
Notify_DynamicGroup |
|||
|
VAE_ServiceContinuity API |
Query_ServiceContinuity |
VAE server |
Request/Response |
|
VAE_HDMapDynamicInfo API |
Subscribe_HDMapDynamicInfo |
V2X application specific server |
Subscribe/notify |
|
Notify_HDMapDynamicInfo |
|||
|
VAE_SessionOrientedService API |
Establish_Session |
V2X application specific server |
Subscribe/notify |
|
Notify_Establish_Session |
|||
|
Update_Session |
|||
|
Notify_Update_Session |
|||
|
Terminate_Session |
|||
|
Notify_Terminate_Session |
|||
|
VAE_PC5ProvisioningRequirement API |
Config_PC5ProvisioningRequirement |
V2X application specific server |
Subscribe/notify |
|
Notify_PC5ProvisioningRequirement |
|||
|
VAE_V2VConfigRequirement API |
Request_V2VConfigRequirement |
V2X application specific server |
Request/Response |
The SEAL server(s) APIs available via SEAL-S reference point as specified in 3GPP TS 23.434 [6] are consumed by the V2X application specific server via the VAE server (acting as a VAL server) over the Vs reference point. When V2X application specific server invokes a SEAL server API via the VAE server over the Vs reference point, the VAE server shall interact with the corresponding SEAL server over the SEAL-S reference point for the API invocation request and response.
NOTE: When V2X application specific server invokes a SEAL server API directly, the V2X application specific server acting as VAL server shall interact with the corresponding SEAL server over the SEAL-S reference point for the API invocation request and response as specified in 3GPP TS 23.434 [6].
Editor’s note: Whether the VAE_DynamicGroup API is to be moved to SEAL is FFS.
10.2.2 VAE_MessageDelivery API
10.2.2.1 General
API description: This API enables the V2X application specific server to subscribe/unsubscribe to the VAE server and communicate with the VAE server to send and receive V2X messages to and from the V2X UEs (including V2X groups).
10.2.2.2 Deliver_DL_Message operation
API operation name: Deliver_DL_Message
Description: Delivers the V2X messages to the V2X UEs.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.4.2.1, 9.4.2.3.
Outputs: None.
See subclause 9.4.3 and subclause 9.4.4 for the details of usage of this API operation.
10.2.2.3 Deliver_UL_Message operation
API operation name: Deliver_UL_Message
Description: Delivers the uplink V2X messages from the V2X UEs to the V2X application specific server.
Known Consumers: V2X application specific server.
Inputs: None
Outputs: Refer subclause 9.4.2.4.
See subclause 9.4.5 for the details of usage of this API operation.
10.2.2.4 V2X_MessageDelivery_Subscribe operation
API operation name: V2X_MessageDelivery_Subscribe
Description: Subscribe to the VAE server for sending and receiving V2X messages.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.4.2.6.
Outputs: Refer subclause 9.4.2.7.
See subclause 9.4.6 for the details of usage of this API operation.
10.2.2.5 V2X_MessageDelivery_Unsubscribe operation
API operation name: V2X_MessageDelivery_Unsubscribe
Description: Unsubscribe to the VAE server for sending and receiving V2X messages.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.4.2.8.
Outputs: Refer subclause 9.4.2.9.
See subclause 9.4.6 for the details of usage of this API operation.
10.2.3 VAE_FileDistribution API
10.2.3.1 General
API description: This API enables the V2X application specific server to communicate with the VAE server to initiate file distribution to the V2X UEs.
10.2.3.2 Distribute_File operation
API operation name: Distribute_File
Description: Distributes files to the V2X UEs.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.5.2.
Outputs: Refer subclause 9.5.2.
See subclause 9.5.2 for the details of usage of this API operation.
10.2.4 VAE_ApplicationRequirement API
10.2.4.1 General
API description: This API enables the V2X application specific server to communicate with the VAE server to provide V2X application requirement to the underlying 3GPP network.
10.2.4.2 Reserve_NetworkResource operation
API operation name: Reserve_NetworkResource
Description: Provides V2X application requirement to underlying 3GPP network.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.11.2.1
Outputs: Refer subclause 9.11.2.2
See subclause 9.11.3 for the details of usage of this API operation.
10.2.4.3 Notify_NetworkResource operation
API operation name: Notify_NetworkResource
Description: Notify the result of network resource adaptation corresponding to the V2X application requirement.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.11.2.3
Outputs: None
See subclause 9.11.3 for the details of usage of this API operation.
10.2.5 VAE_DynamicGroup API
10.2.5.1 General
API description: This API enables the V2X application specific server to communicate with the VAE server to configure dynamic group information.
10.2.5.2 Configure_DynamicGroup operation
API operation name: Configure_DynamicGroup
Description: Configures the dynamic group information at the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.12.2.2.
Outputs: Refer subclause 9.12.2.3.
See subclause 9.12.3 for the details of usage of this API operation.
10.2.5.3 Notify_DynamicGroup operation
API operation name: Notify_DynamicGroup
Description: Notify the dynamic group information (i.e. group member joins or leaves) at the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.12.2.4.
Outputs: None.
See subclause 9.12.5 for the details of usage of this API operation.
10.2.6 VAE_ServiceContinuity API
10.2.6.1 General
API description: This API enables the VAE server to query whether the target VAE server can serve the GEO ID and V2X Service ID for service continuity.
10.2.6.2 Query_ServiceContinuity operation
API operation name: Query_ServiceContinuity
Description: Query the service continuity information.
Known Consumers: VAE server.
Inputs: Refer subclause 9.10.2.1.
Outputs: Refer subclause 9.10.2.2.
See subclause 9.10.3 for the details of usage of this API operation.
10.2.7 VAE_HDMapDynamicInfo API
10.2.7.1 General
API description: This API enables the V2X application specific server to communicate with the VAE server to subscribe and receive notifications for HD map dynamic information.
10.2.7.2 Subscribe_HDMapDynamicInfo operation
API operation name: Subscribe_HDMapDynamicInfo
Description: Subscribes for the HD map dynamic information at the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.16.2.1.
Outputs: Refer subclause 9.16.2.2.
See subclause 9.16.3 for the details of usage of this API operation.
10.2.7.3 Notify_HDMapDynamicInfo operation
API operation name: Notify_HDMapDynamicInfo
Description: Notify the HD map dynamic information at the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.16.2.3.
Outputs: None.
See subclause 9.16.6 for the details of usage of this API operation.
10.2.8 VAE_SessionOrientedService API
10.2.8.1 General
API description: This API enables the V2X application specific server to communicate with the VAE server to trigger establishment, update and termination of session-oriented service.
10.2.8.2 Establish_Session operation
API operation name: Establish_Session
Description: Triggers the establishment of the session-oriented service by the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.19.2.1.
Outputs: Refer subclause 9.19.2.2.
See subclause 9.19.4.2 for the details of usage of this API operation.
10.2.8.3 Notify_Establish_Session operation
API operation name: Notify_Establish_Session
Description: Notification about the establishment of the session-oriented service by the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.19.2.3.
Outputs: None.
See subclause 9.19.5.2 for the details of usage of this API operation.
10.2.8.4 Update_Session operation
API operation name: Update_Session
Description: Triggers the update to the session-oriented service by the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.19.2.4.
Outputs: Refer subclause 9.19.2.5.
See subclause 9.19.4.3 for the details of usage of this API operation.
10.2.8.5 Notify_Update_Session operation
API operation name: Notify_Update_Session
Description: Notification about the update to the session-oriented service by the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.19.2.6.
Outputs: None.
See subclause 9.19.5.3 for the details of usage of this API operation.
10.2.8.6 Terminate_Session operation
API operation name: Terminate_Session
Description: Triggers the termination of the session-oriented service by the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.19.2.7.
Outputs: Refer subclause 9.19.2.8.
See subclause 9.19.5.4 for the details of usage of this API operation.
10.2.8.7 Notify_Terminate_Session operation
API operation name: Notify_Terminate_Session
Description: Notification about the termination of the session-oriented service by the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.19.2.9.
Outputs: None.
See subclause 9.19.5.4 for the details of usage of this API operation.
10.2.9 VAE_PC5ProvisioningRequirement API
10.2.9.1 General
API description: This API enables the V2X application specific server to communicate with the VAE server to request from VAE server the PC5 provisionng service in multi-operator V2X scenarios.
10.2.9.2 Config_PC5ProvisioningRequirement operation
API operation name: Config_PC5ProvisioningRequirement
Description: The V2X application specific server provides a V2X PC5 provisioning requirement to the VAE server.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.15.2.1
Outputs: Acknowledgement message.
See subclause 9.15.3 for the details of usage of this API operation.
10.2.9.3 Notify_PC5ProvisioningRequirement operation
API operation name: Notify_ PC5ProvisioningRequirement
Description: Notify the result of multi operation PC5 provisioning requirement to the V2X UEs.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.15.2.6
Outputs: None
See subclause 9.15.3 for the details of usage of this API operation.
10.2.10 VAE_V2VConfigRequirement API
10.2.10.1 General
API description: This API enables the V2X application specific server to provide a V2V configuration requirement to the VAE server to manage the UE-to-UE broadcast/groupcast communication.
10.2.10.2 Request_V2VConfigRequirement operation
API operation name: Request_V2VConfigRequirement
Description: The V2X application specific server provides a V2V configuration requirement request to the VAE server to manage the UE-to-UE broadcast/groupcast communication.
Known Consumers: V2X application specific server.
Inputs: Refer subclause 9.17.2.1
Outputs: Refer subclause 9.17.2.2
See subclause 9.17.3 for the details of usage of this API operation.
Annex A (informative):
Detailed V2X application layer functional model
Figure A-1 illustrates the detailed V2X application layer functional model including all the functional entities of the VAE layer and the functional entities of the SEAL as specified in 3GPP TS 23.434 [6].
Figure A-1: Detailed V2X application layer functional model
Annex B (informative):
Functionalities with SA2 dependency
B.1 Service negotiation with underlying 3GPP network
B.1.1 General
The following information flows for service negotiation with the 3GPP network are not supported in 3GPP TS 23.682 [8].
B.1.2 Information flows
B.1.2.1 Supporting information request
Table B.1.2.1-1 describes the information flow for a VAE server to provide the network with supporting information for service negotitation with the 3GPP network.
Table B.1.2.1-1: Supporting information request
|
Information element |
Status |
Description |
|
Supporting Information |
O |
Indicating supporting information by the VAE server to increase the network awareness related to the service. Example of supporting information is planned/expected UE trajectory, which can be provided in the form of waypoints (GPS coordinates) and associated timestamps. |
Editor’s note: Reference to the appropriate SA2 specification is needed and corresponding information flow table can be removed.
Editor’s note: Need to verify with SA2 specifications on the exact support provided to this feature.
B.1.2.2 Supporting information response
Table B.1.2.2-1 describes the information flow for a network to provide a response associated to a supporting information request.
Table B.1.2.2-1: Supporting information response
|
Information element |
Status |
Description |
|
Result |
M |
Response from the network if supporting information is supported by the 3GPP network. |
Editor’s note: Reference to the appropriate SA2 specification is needed and corresponding information flow table can be removed.
B.1.2.3 Void
B.1.2.4 Void
B.1.3 Void
B.1.4 Void
B.2 Void
Annex C (normative):
V2X application enabler related configuration data
C.1 General
This Annex provides information about the static data needed for configuration for the V2X application enabler service, which belongs to one of the following categories:
– VAE client configuration data (see subclause C.2); and
– VAE server configuration data (see subclause C.3).
C.2 VAE client configuration data
The procedure of VAE client related configuration are specified in 3GPP TS 23.434 [6]. Data in tables C.2-1 has to be known by the VAE client.
Data in table C.2-1 can be configured using the CM-UU reference point as specified in 3GPP TS 23.434 [6].
Table C.2-1: VAE client related configuration data
|
Reference |
Parameter description |
|
Clause 8.1 and clause 9.1.2.2 |
V2X user/UE identity |
|
Clause 9.1.2.2 |
V2X service ID |
|
Clause 9.1.2.2 |
V2X server USD |
|
Clause 9.2.3 and Clause 9.1.2.3 |
IP address and port information of the initial VAE server serving the VAE client |
|
Clause 9.3.3 |
GEO ID information |
C.3 VAE server configuration data
The procedure of VAE server related configuration are specified in 3GPP TS 23.434 [6]. Data in tables C.3-1 has to be known by the VAE server.
Data in table C.3-1 can be configured using the CM-S reference point as specified in 3GPP TS 23.434 [6].
Table C.3-1: VAE server related configuration data
|
Reference |
Parameter description |
|
Clause 8.1 |
List of V2X user identities |
|
Clause 9.7.4.2 |
IP address of the EPS entity SCEF |
|
Clause 9.10.3.2 |
List of IP addresses of the neighboring VAE servers |
|
Clause 9.11.3.2 |
IP address of the NRM server |
|
Clause 9.12.3.2 |
Unique pool of ProSe Layer-2 Group IDs |
|
Clause 9.5.2 |
BM-SC information |
Annex D (normative):
Utilization of edge computing
The application architecture for supporting edge applications are specified in 3GPP TS 23.558 [25]. The V2X application layer functional model as specified in clause 6 may be deployed in edge computing environment.
Figure D-1 illustrates a V2X application layer deployment in edge computing environments.
Figure D-1: Utilization of edge computing
Figure D-1 illustrates the utilization of edge computing for V2X application layer based on edge enabler layer specified in 3GPP TS 23.558 [25].
At UE side, V2X Application Specific client(s) and VAE client interact with the Edge Enabler Client (EEC) via EDGE‑5 reference point. In an Edge Data Network (EDN), V2X Application Specific Server and VAE server assume the role of EAS (Edge Application Server) and interacts with the Edge Enabler Server (EES) via EDGE-3 reference point, for instance, to register its profile into the EES. Upon service provisioning, the EEC interacts with the EES via EDGE-1 reference point, for instance, to discover V2X Application Specific Server(s) and VAE Server and further the EEC provides the discovered V2X Application Specific Server(s) and VAE server to the V2X Application Specific client and VAE client respectively. The interactions between the entities and 5GS are not shown for the sake of simplicity.
In an EDN, there could be several EES(s) provided by the same or different ECSP. The V2X application specific server(s), VAE server(s) and SEAL servers (e.g. GMS, NRMS, ADAES) shall be able to discover and register into an appropriate EES. If CAPIF is used, this can be done by utilizing the AEF serving area and/or the AEF location as described in 3GPP TS 23.222 [x]; otherwise, local configuration of the EES endpoint may be used.
The services provided by EES over EDGE-3 are not re-exposed by the VAE server or SEAL servers to the V2X application specific server but are directly consumed by the SEAL servers, VAE server and V2X application specific server(s).
NOTE: This clause illustrates an example edge deployment using edge enabler layer and there can be other valid edge deployments enabled for V2X application layer.
Annex D:
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-10 |
SA6#26 |
TS skeleton |
0.0.0 |
||||
|
2018-10 |
SA6#26 |
Implementation of the following pCRs approved by SA6: S6-181488, S6-181489, S6-181490, S6-181548, S6-181549, S6-181554, S6-181555, S6-181556, S6-181575, S6-181576, S6-181583, S6-181589, S6-181591 |
0.1.0 |
||||
|
2018-12 |
SA6#27 |
Implementation of the following pCRs approved by SA6: S6-181693, S6-181777, S6-181779, S6-181781, S6-181783, S6-181785, S6-181836, S6-181837, S6-181838, S6-181839 |
0.2.0 |
||||
|
2019-01 |
SA6#28 |
Implementation of the following pCRs approved by SA6: S6-190137, S6-190144, S6-190219, S6-190221, S6-190222, S6-190223, S6-190224, S6-190271, S6-190298 |
0.3.0 |
||||
|
2019-03 |
SA6#29 |
Implementation of the following pCRs approved by SA6: S6-190364, S6-190368, S6-190372, S6-190460, S6-190461, S6-190462, S6-190463, S6-190464, S6-190465, S6-190466, S6-190467, S6-190508 |
0.4.0 |
||||
|
2019-03 |
SA#83 |
SP-190062 |
Presentation for information at SA#83 |
1.0.0 |
|||
|
2019-04 |
SA6#30 |
Implementation of the following pCRs approved by SA6: S6-190641, S6-190643, S6-190644, S6-190651, S6-190652, S6-190755, S6-190756, S6-190757, S6-190758, S6-190760, S6-190762, S6-190827, S6-190828, S6-190829, S6-190830, S6-190831 |
1.1.0 |
||||
|
2019-05 |
SA6#31 |
Implementation of the following pCRs approved by SA6: S6-191020, S6-191021, S6-191030, S6-191032, S6-191126, S6-191028, S6-191129, S6-191130, S6-191131, S6-191191133, S6-191136, S6-191138, S6-191139, S6-191194, S6-191195, S6-191196 |
1.2.0 |
||||
|
2019-05 |
SA#84 |
SP-190472 |
Presentation for Approval at SA#84 |
2.0.0 |
|||
|
2019-06 |
SA#84 |
SP-190472 |
MCC Editorial update for publication after TSG SA approval (SA#84) |
16.0.0 |
|||
|
2019-09 |
SA#85 |
SP-190734 |
0001 |
2 |
F |
Remove EN GeoIDs |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0002 |
3 |
F |
Functionalities with SA2 dependency |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0003 |
F |
Update to functional model |
16.1.0 |
|
|
2019-09 |
SA#85 |
SP-190734 |
0004 |
1 |
F |
Update to network QoS and situation monitoring aligned with SA2 |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0005 |
2 |
F |
Dynamic group API |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0006 |
1 |
F |
Correction to push layer-2 group ID mapping information flow |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0007 |
4 |
F |
Corrections on notifications for network monitoring procedure |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0008 |
1 |
F |
Addition of missing VAE server APIs |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190734 |
0009 |
1 |
F |
Update the configurations information |
16.1.0 |
|
2019-12 |
SA#86 |
SP-191112 |
0010 |
2 |
F |
CR Message Delivery |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191112 |
0011 |
F |
Update API names |
16.2.0 |
|
|
2019-12 |
SA#86 |
SP-191112 |
0012 |
3 |
F |
Update to uplink message delivery procedure |
16.2.0 |
|
2020-03 |
SA#87-E |
SP-200115 |
0013 |
F |
Add VAE application requirement notification |
16.3.0 |
|
|
2020-03 |
SA#87-E |
SP-200115 |
0014 |
1 |
F |
Add VAE service continuity API |
16.3.0 |
|
2020-03 |
SA#87-E |
SP-200115 |
0015 |
1 |
F |
Correct Group Management procedure |
16.3.0 |
|
2020-03 |
SA#87-E |
SP-200115 |
0016 |
1 |
F |
Align with TS 23.434 |
16.3.0 |
|
2020-03 |
SA#87-E |
SP-200115 |
0017 |
1 |
F |
Clarifications on V2X USD |
16.3.0 |
|
2020-03 |
SA#87-E |
SP-200115 |
0018 |
1 |
F |
Correction of the usage of SEAL services by the V2X application specific server |
16.3.0 |
|
2020-09 |
SA#89-E |
SP-200842 |
0019 |
F |
Correct Geo id |
16.4.0 |
|
|
2020-09 |
SA#89-E |
SP-200842 |
0020 |
1 |
F |
Correction to de-registration procedure |
16.4.0 |
|
2020-12 |
SA#90-E |
SP-200992 |
0033 |
1 |
F |
Clarifications for network monitoring information notification |
16.5.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0021 |
2 |
B |
PC5 Provisioning in multi-operator V2X scenarios |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0022 |
1 |
B |
V2X application layer architecture enhancement |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0023 |
1 |
B |
Business relationships between V2X service providers |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0024 |
1 |
B |
V2X service discovery across multiple V2X service providers |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0025 |
1 |
B |
Support for HD map dynamic information |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0026 |
1 |
B |
Support CAPIF |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0027 |
2 |
B |
Support local MBMS |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0028 |
2 |
B |
UE-to-UE broadcast/groupcast configuration by VAE layer |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0030 |
1 |
B |
V2V communication mode switching |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0031 |
1 |
B |
Support for local MBMS delivery |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0032 |
2 |
B |
V2X UE registration enhancement |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0034 |
2 |
B |
Network monitoring procedure enhancement |
17.0.0 |
|
2020-12 |
SA#90-E |
SP-200998 |
0036 |
1 |
F |
Clarifications for netwok monitoring information notification |
17.0.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0037 |
2 |
F |
Clarifications on network monitoring |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0038 |
1 |
B |
Dynamic local service information in multiple V2X service provider |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0039 |
1 |
B |
UE initiated session oriented service |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0040 |
1 |
B |
Monitoring and control of QoS for eV2X communications |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0041 |
2 |
B |
Support for enhancements to V2X group management and group communication |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0042 |
1 |
B |
Session oriented services |
17.1.0 |
|
2021-04 |
SA#91-E |
SP-210182 |
0043 |
B |
Update to VAE server APIs |
17.1.0 |
|
|
2021-04 |
SA#91-E |
SP-210182 |
0044 |
F |
V2X UE identity |
17.1.0 |
|
|
2021-06 |
SA#92-E |
SP-210488 |
0046 |
2 |
F |
Network resource management service of SEAL for V2X application |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0049 |
D |
Editorial changes for references |
17.2.0 |
|
|
2021-06 |
SA#92-E |
SP-210488 |
0049 |
B |
Resolving editor notes in session oriented services |
17.2.0 |
|
|
2021-06 |
SA#92-E |
SP-210488 |
0054 |
1 |
F |
Editorial corrections for HDMap feature |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0055 |
1 |
B |
Information flows and API definitions for session-oriented service |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0056 |
1 |
B |
Requirements for message distribution |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0057 |
1 |
B |
Alignment of Get V2X UE service discovery response with request |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0058 |
1 |
B |
Alignment of information flows for local service information |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0060 |
1 |
B |
Resolve EN on V2X groupcast/broadcast configuration |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0061 |
1 |
B |
Resolve EN on PC5 provisioning for multi-operator V2X services |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0062 |
1 |
B |
Update of VAE server APIs |
17.2.0 |
|
2021-06 |
SA#92-E |
SP-210488 |
0064 |
B |
Updates to usage of SEAL for V2X application layer |
17.2.0 |
|
|
2021-09 |
SA#93-E |
SP-210965 |
0066 |
2 |
F |
Clarifications for RAT Type usage in network monitoring procedure |
17.3.0 |
|
2021-09 |
SA#93-E |
SP-210965 |
0067 |
F |
Clarifications for RAT Type usage in network monitoring procedure |
17.3.0 |
|
|
2021-09 |
SA#93-E |
SP-210965 |
0068 |
F |
Alignment with SEAL key managment |
17.3.0 |
|
|
2021-09 |
SA#93-E |
SP-210965 |
0069 |
1 |
F |
Corrections to HDMap procedures |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220474 |
0071 |
1 |
F |
Add location reference in HDmap |
17.4.0 |
|
2022-12 |
SA#98-e |
SP-221252 |
0072 |
2 |
B |
V2X application layer architecture support for edge deployments |
18.0.0 |
|
2022-12 |
SA#98-e |
SP-221252 |
0073 |
2 |
C |
Enhancement to network monitoring |
18.0.0 |
|
2022-12 |
SA#98-e |
SP-221252 |
0074 |
2 |
B |
Support for VRU zone configuration and operation |
18.0.0 |