4 Architectural requirements

23.2863GPPApplication layer support for Vehicle-to-Everything (V2X) servicesFunctional architecture and information flowsRelease 18TS

4.1 General

4.1.1 Description

This subclause specifies the general requirements for V2X application layer functional architecture.

4.1.2 Requirements

[AR-4.1.2-a] The VAE client and the VAE server shall support one or more V2X applications.

[AR-4.1.2-b] The VAE capabilities should be offered as APIs to the V2X applications.

[AR-4.1.2-c] The VAE capabilities shall enable V2X UEs to obtain the address of available V2X application servers associated with served geographical area information.

[AR-4.1.2-d] The VAE capabilities shall enable V2X UEs to obtain the information of available V2X services (e.g. identified byV2X service ID).

[AR-4.1.2-e] The VAE capabilities shall support obtaining information of the available V2X services (e.g. identified by V2X service ID) from the V2X application.

[AR-4.1.2-f] The VAE capabilities shall support obtaining information of the associated geographical area from the V2X application.

[AR-4.1.2-g] The VAE client shall be able to communicate to multiple VAE servers.

4.2 V2X group communication

4.2.1 Description

This subclause specifies the V2X group communication related requirements.

4.2.2 Requirements

[AR-4.2.2-a] The VAE capabilities shall enable configuring ProSe group communication parameters to the VAE clients.

[AR-4.2.2-b] The VAE capabilities shall enable broadcast of the group communication parameters.

[AR-4.2.2-c] The VAE capabilities shall enable VAE clients to generate the group communication parameters.

[AR-4.2.2-d] The VAE capabilities shall enable to prevent overlapping of group communication.

4.3 V2X dynamic groups

4.3.1 Description

This subclause specifies the V2X dynamic groups related requirements.

4.3.2 Requirements

[AR-4.3.2-a] The VAE capabilities shall enable V2X dynamic groups formation.

[AR-4.3.2-b] The VAE capabilities shall enable configuring dynamic group communication parameters to the VAE client.

[AR-4.3.2-c] The VAE capabilities shall enable switching from Uu to PC5-based communication.

[AR-4.3.2-d] The VAE capabilities shall enable determining V2X UEs in the proximity.

[AR-4.3.2-e] The VAE capabilities shall enable V2X dynamic group management (e.g. joining, adding or removing V2X UEs, split or merge).

4.4 File distribution capability

4.4.1 Description

This subclause specifies the architectural requirements for file distribution.

4.4.2 Requirements

[AR-4.4.2-a] The VAE capabilities shall be able to support delivery of large files using unicast.

[AR-4.4.2-b] The VAE capabilities shall be able to support delivery of large files using MBMS.

[AR-4.4.2-c] The VAE server shall enable the re-use of MBMS capabilities for file distribution.

[AR-4.4.2-d] The VAE capabilities shall be able to support local MBMS based MBMS data delivery.

4.5 V2X application message distribution

4.5.1 Description

This subclause specifies the V2X (e.g. ETSI ITS, SAE) message distribution requirements.

4.5.2 Requirements

[AR-4.5.2-a] The VAE server shall provide a mechanism to distribute V2X messages to all registered receivers in targeted geographical areas.

[AR-4.5.2-b] The VAE server shall enable the delivery of several V2X messages over the same connection.

[AR-4.5.2-c] The VAE client shall have the capability to register to V2X messages within one or more geographical area.

[AR-4.5.2-d] The VAE server shall have the capability to only forward V2X messages to authorized V2X UEs in target geographical areas.

[AR-4.5.2-e] The VAE server shall provide a mechanism for priority support of different V2X messages (e.g. safety message).

[AR-4.5.2-f] The VAE capabilities shall support the transmission of V2X messages from the V2X UE to the V2X application server.

[AR-4.5.2-g] The VAE layer shall provide a mechanism to support session-oriented services.

[AR-4.5.2-h] The VAE layer shall support the delivery of V2X messages over pre-established sessions.

4.6 Service continuity

4.6.1 Description

This subclause specifies the V2X service continuity related requirements.

4.6.2 Requirements

[AR-4.6.2-a] The VAE capabilities shall enable V2X UEs to continue receiving V2X service when changing geographical area.

4.7 PC5 Provisioning in multi-operator V2X scenarios

4.7.1 Description

This subclause specifies the PC5 Provisioning for multi-operator V2X services related requirements.

4.7.2 Requirements

[AR-4.7.2-a] The VAE capabilities shall support PC5 policy/parameter provisioning for V2X services provided by a single V2X service provider; and offered by more than one MNO (aka multi-operator V2X services).

4.8 Support for VRU zone configuration and operation

4.8.1 Description

This subclause specifies the VRU zone configuration and operation related requirements.

4.8.2 Requirements

[AR-4.8.2-a] The VAE capabilities shall support VRU zone configurations (e.g. distribution of VRU zone related configuration information) to the relevant V2X UEs.