Content for TS 24.486 Word version: 18.3.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 General description
5 SEAL services
...
...
1 Scope p. 7
The present document specifies the protocols for application layer support for V2X services as specified in TS 23.286 for:
- V2X application communication among UEs (over the V5-AE interface); and
- V2X application communication between the UE and the V2X application server (over the V1-AE interface).
2 References p. 7
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 23.003: "Numbering, addressing and identification".
[3]
TS 23.032: "Universal Geographical Area Description (GAD)".
[4]
TS 23.286: "Application layer support for V2X services; Functional architecture and information flows".
[5]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[6]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[7]
TS 24.385: "V2X services Management Object (MO)".
[8]
TS 24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3".
[9]
TS 24.544: "Group Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[10]
TS 24.545: "Location Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[11]
TS 24.546: "Configuration Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[12]
TS 24.547: "Identity Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[13]
TS 24.548: "Network Resource Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[14]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[15]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[16]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2".
[17]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".
[18]
ETSI TS 102 965: "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID); Registration".
[19]
RFC 9110:"HTTP Semantics".
[20]
ISO TS 17419: "Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context".
[21]
TS 23.285: "Architecture enhancements for V2X services".
[22]
TS 29.486: "V2X Application Enabler (VAE) Services; Stage 3".
[23]
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".
[24]
RFC 9112: "HTTP/1.1".
[25]
ISO TS 17419 ITS-AID AssignedNumbers: http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf .
[26]
TS 24.588: "Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3".
[27]
CCSA YD/T 3707-2020: "Technical requirements of network layer of LTE-based vehicular communication".
[28]
TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Protocol aspects; Stage 3".
[29]
TS 24.543: "Data Delivery Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
3 Definitions of terms and abbreviations p. 9
3.1 Terms p. 9
For the purposes of the present document, the terms 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 application enabler client:
An entity that provides the client side functionalities corresponding to the V2X application enabler layer.
V2X application enabler server:
An entity that provides the server side functionalities corresponding to the V2X application enabler layer.
V2X service identifier:
An identifier of a V2X service, e.g. PSID, ITS-AID, or AID of the V2X application.
For the purposes of the present document, the following terms and definitions given in TS 23.286 apply:
V2X group
V2X dynamic group
V2X service
For the purposes of the present document, the following terms and definitions given in TS 23.285 apply:
Application Identifier (AID)
Intelligent Transport Systems (ITS)
ITS Application Identifier (ITS-AID)
Provider Service Identifier (PSID)
For the purposes of the present document, the following terms and definitions given in TS 23.434 apply:
SEAL service
3.2 Abbreviations p. 9
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.
AS
Application Server
SEAL
Service Enabler Architecture Layer for Verticals
SEALDD
SEAL Data Delivery
USD
User Service Description
V2P
Vehicle-to-Pedestrian
V2X
Vehicle-to-Everything
VAE
V2X Application Enabler
VAE-C
V2X Application Enabler Client
VAE-S
V2X Application Enabler Server
VRU
Vulnerable Road User
4 General description p. 9
The UE can contain a VAE client (VAE-C). The VAE-C communicates with the VAE server (VAE-S) over the V1-AE interface (see TS 23.286). Furthermore, the VAE-C of a UE can communicate with the VAE-C of another UE over the V5-AE interface (see TS 23.286). Both the VAE-C and the VAE-S can act as an HTTP client or an HTTP server (see RFC 9112). The HTTP protocol interactions are described in detail in clause 6 and 7.
The VAE layer supports UEs in the LTE-Uu communication range assigning a ProSe Layer-2 Group ID for application layer V2X dynamic group formation (on-network dynamic group creation procedure as defined in clause 6.10).
Additionally, the VAE layer supports UEs in assigning a ProSe Layer-2 Group ID for application layer V2X dynamic group formation (off-network dynamic group creation procedure as defined in clause 6.10).
By means of using the V1-AE interface:
- V2X UE registration and de-registration towards the VAE-S can be provided as defined by clause 6.2 and 6.3;
- application level location tracking can be provided as defined by clause 6.4;
- V2X message delivery can be provided as defined by clause 6.5;
- V2X service discovery information can be provided as defined by clause 6.6;
- V2X service continuity can be provided as defined by clause 6.7;
- dynamic local service information for V2X service continuity can be obtained as defined by clause 6.8;
- network monitoring by the V2X UE can be provided as defined by clause 6.9;
- V2X USD provisioning can be provided as defined by clause 7.2; and
- PC5 parameters provisioning can be provided as defined by clause 7.3.
5 SEAL services p. 10
The VAE layer utilizes SEAL services to support V2X services. The SEAL services are specified in TS 24.544, TS 24.545, TS 24.546, TS 24.547, TS 24.548 and TS 24.543. Interactions between the VAE layer and the SEAL services are described in detail in clause 6.
