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.6.0

Top   Top   None   None   Next
0…   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…   A… 
0 Introduction  1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Architectural requirements  4.1 General  4.2 V2X group communication  4.3 V2X dynamic groups  4.4 File distribution capability  4.5 V2X application message distribution  4.6 Service continuity  4.7 PC5 Provisioning in multi-operator V2X scenarios  4.8 Support for VRU zone configuration and operation  4.9 V2P communications requirements  5 Involved business relationships 
...

 

0  Introduction  p. 11

In order to ensure efficient use and deployment of V2X applications on 3GPP networks an architecture for V2X application layer consisting of V2X application enabler is specified in this document.
The V2X application enabler capabilities takes into consideration the study in TR 23.795, the existing stage 1 and stage 2 work within 3GPP related to V2X in TS 22.185, TS 22.186 and TS 23.285, as well as V2X application standards defined outside 3GPP (e.g. ETSI, SAE).
Up

1  Scope  p. 12

The present document specifies the functional architecture, procedures and information flows for V2X application enabler layer. This specification includes the capabilities of the application layer support for V2X services that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems. The VAE capabilities applies to EPS and 5GS.

2  References  p. 12

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.185: "Service requirements for V2X services; Stage 1".
[3]
TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
[4]
TS 23.280: "Common functional architecture to support mission critical services".
[5]
TS 23.285: "Architecture enhancements for V2X services".
[6]
TS 23.434: "Service enabler architecture layer for verticals; Functional architecture and information flows".
[7]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[8]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[9]
TR 23.795: "Study on application layer support for V2X services".
[10]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[11]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[12]
TS 29.214: "Policy and Charging Control over Rx reference point".
[13]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[14]
TS 36.300: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[15]
ETSI EN 302 637-3 (V1.3.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service".
[16]
ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionaryMultimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[17]
ETSI TS 102 965 (V1.4.1): "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID); Registration".
[18]
ISO TS 17419: "Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context".
[19]
TS 23.287: " Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[20]
TS 23.501: "System architecture for the 5G System (5GS)".
[21]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[22]
TS 29.116: "Representational state transfer over xMB reference point between Content Provider and BM-SC".
[23]
TS 23.003: "Numbering, Addressing and Identification".
[24]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[25]
TS 23.558: "Architecture for enabling Edge Applications".
Up

3  Definitions and abbreviations  p. 13

3.1  Definitions  p. 13

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
V2X group:
A defined set of V2X UEs configured for specific purpose in V2X service.
V2X dynamic group:
A V2X group where the V2X UEs are determined dynamically corresponding to a group criteria (e.g. proximity).
V2X service:
A service offered by a V2X application which supports the related communications between two entities (e.g. V2X UE and V2X UE, V2X UE and V2X application server).
Up

3.2  Abbreviations  p. 13

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5GS
5G System
AS
Application Server
AID
Application Object Identifier
CAPIF
Common API Framework for northbound APIs
E-UTRAN
Evolved Universal Terrestrial Radio Access Network
EPS
Evolved Packet System
ETSI
European Telecommunications Standards Institute
GPSI
Generic Public Subscription Identifier
LTE
Long-Term Evolution
MBMS
Multimedia Broadcast Multicast Service
PSID
Provider Service Identifier
SAE
Society of Automotive Engineers
SCEF
Service Capability Exposure Function
SCS
Services Capability Server
UE
User Equipment
USD
User Service Description
V2I
Vehicle-to-Infrastructure
V2N
Vehicle-to-Network
V2P
Vehicle-to-Pedestrian
V2V
Vehicle-to-Vehicle
V2X
Vehicle-to-Everything
VAE
V2X Application Enabler
Up

4  Architectural requirements  p. 14

4.1  General  p. 14

4.1.1  Description  p. 14

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

4.1.2  Requirements  p. 14

[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.
Up

4.2  V2X group communication  p. 14

4.2.1  Description  p. 14

This subclause specifies the V2X group communication related requirements.

4.2.2  Requirements  p. 14

[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  p. 15

4.3.1  Description  p. 15

This subclause specifies the V2X dynamic groups related requirements.

4.3.2  Requirements  p. 15

[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  p. 15

4.4.1  Description  p. 15

This subclause specifies the architectural requirements for file distribution.

4.4.2  Requirements  p. 15

[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  p. 15

4.5.1  Description  p. 15

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

4.5.2  Requirements  p. 15

[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.
Up

4.6  Service continuity  p. 16

4.6.1  Description  p. 16

This subclause specifies the V2X service continuity related requirements.

4.6.2  Requirements  p. 16

[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 |R17|  p. 16

4.7.1  Description  p. 16

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

4.7.2  Requirements  p. 16

[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 |R18|  p. 16

4.8.1  Description  p. 16

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

4.8.2  Requirements  p. 16

[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.

4.9  V2P communications requirements |R18|  p. 16

4.9.1  Description  p. 16

This subclause specifies the V2P communications related requirements.

4.9.2  Requirements  p. 16

[AR-4.9.2-a]
The VAE capabilities shall provide mechanisms (e.g. configurations) to support V2P communications.

5  Involved business relationships  p. 17

Figure 5-1 shows the business relationships that exist and that are needed to support a single V2X user.
Reproduction of 3GPP TS 23.286, Fig. 5-1: Business relationships for V2X services
Figure 5-1: Business relationships for V2X services
Up
The V2X user belongs to a V2X service provider based on a V2X service agreement between the V2X user and the V2X service provider. The V2X service provider can have V2X service agreements with several V2X users. The V2X user can have V2X service agreements with several V2X service providers. The V2X service provider can have V2X service provider agreements with several partner V2X service providers.
The V2X service provider and the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The home PLMN operator can have PLMN operator service arrangements with multiple V2X service providers and the V2X service provider can have PLMN operator service arrangements with multiple home PLMN operators. As part of the PLMN operator service arrangement between the V2X service provider and the home PLMN operator, PLMN subscription arrangements can be provided which allows the V2X UEs to register with home PLMN operator network.
The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators.
Up

Up   Top   ToC