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 29.486  Word version:  18.3.0

Top   Top   None   None   Next
1…   5…   6…   7… 
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  3.1 Terms  3.2 Symbols  3.3 Abbreviations  4 Overview 
...

 

1  Scope  p. 16

The present document specifies the stage 3 protocol and data model for Vs interface between the V2X application specific server and VAE server and VAE-E interface between VAE servers. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the VAE server. The Vs, VAE-E interfaces and the related stage 2 functional requirements are defined in TS 23.286.
The stage 2 application layer architecture, functional requirements, procedures and information flows necessary for enabling Vehicle-to-Everything (V2X) are specified in TS 23.286.
The common protocol and interface aspects for API definition are specified in clause 5.2 of TS 29.122.
Up

2  References  p. 16

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 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[3]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[4]
TS 23.286: "Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows".
[5]
RFC 9113:  "HTTP/2".
[6]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[7]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[8]
TR 21.900: "Technical Specification Group working methods".
[11]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[12]
RFC 9112:  " HTTP/1.1".
[13]
RFC 9110:  "HTTP Semantics".
[14]  Void.
[15]  Void.
[16]
RFC 9111:  "HTTP: Caching".
[17]  Void.
[18]
RFC 5246:  "The Transport Layer Security (TLS) Protocol Version 1.2".
[19]
TS 29.116: "Representational state transfer over xMB reference point between Content Provider and BM-SC".
[20]
TS 29.572: "5G System; Location Management Services; Stage 3".
[21]
RFC 6455:  "The Websocket Protocol".
[22]
TS 29.122: "T8 reference point for Northbound APIs".
[23]
RFC 6749:  "The OAuth 2.0 Authorization Framework".
[24]
RFC 5246:  "The Transport Layer Security (TLS) Protocol Version 1.2".
[25]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[26]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[27]
TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
[28]
TS 24.486: "Vehicle-to-Everything (V2X) Application Enabler (VAE) layer; Protocol aspects; stage 3".
[29]
TS 29.549: "Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage 3".
[30]
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[31]
TS 33.536: "Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services".
[32]
TS 33.501: "Security architecture and procedures for 5G system".
[33]
TS 29.520: "5G System; Network Data Analytics Services; Stage 3".
[34]
TS 29.522: "Network Exposure Function Northbound APIs; Stage 3".
[35]
TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
Up

3  Definitions of terms, symbols and abbreviations  p. 18

3.1  Terms  p. 18

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.
For the purpose of the present document, the terms and definitions specified in clause 3.1 of TS 23.286 also apply, including the ones referencing other specifications.
Up

3.2  Symbols  p. 18

For the purposes of the present document, the following symbols apply:
Void

3.3  Abbreviations  p. 18

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.
CAPIF
Common API Framework
NRM
Network Resource Management
V2X
Vehicle-to-Everything
VASS
V2X Application Specific Server
VAE
V2X Application Enabler

4  Overview  p. 19

The Vs interface is between the VASS and the VAE Server. It specifies RESTful APIs that allow the VASS to access the services and capabilities provided by VAE Server.
The stage 2 level requirements and signalling flows for the Vs interface are defined in TS 23.286.
The Vs interface supports the following APIs:
  • VAE_MessageDelivery
  • VAE_FileDistribution
  • VAE_ApplicationRequirement
  • VAE_DynamicGroup
  • VAE_HDMapDynamicInfo
  • VAE_SessionOrientedService
  • VAE_V2VConfigRequirement
  • VAE_PC5ProvisioningRequirement
  • VAE_ServiceAndQoSControlInfo
  • VAE_VRUZoneManagement
  • VAE_V2PApplicationRequirement
The VAE-E interface is between VAE Servers. It specifies RESTful APIs that allow the VAE server to access the services and capabilities provided by other VAE Server.
The stage 2 level requirements and signalling flows for the VAE-E interface are defined in TS 23.286.
The VAE-E interface supports the following APIs:
  • VAE_ServiceContinuity
Up

Up   Top   ToC