Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.549  Word version:  16.2.0

Top   Top   None   None   Next
1…   5…   7…   8…

 

1  ScopeWord‑p. 11

The present specification describes the APIs for the Service Enabler Architecture Layer for Verticals (SEAL). The SEAL and related stage 2 architecture, functional requirements and information flows are specified in TS 23.434.

2  References

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.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[3]
TS 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)".
[4]
RFC 6455:  "The Websocket Protocol".
[5]
RFC 7230:  "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
[6]
RFC 7231:  "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
[7]
RFC 7232:  "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests".
[8]
RFC 7233:  "Hypertext Transfer Protocol (HTTP/1.1): Range Requests".
[9]
RFC 7234:  "Hypertext Transfer Protocol (HTTP/1.1): Caching".
[10]
RFC 7235:  "Hypertext Transfer Protocol (HTTP/1.1): Authentication".
[11]
RFC 5246:  "The Transport Layer Security (TLS) Protocol Version 1.2".
[12]
RFC 7540:  "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[13]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[14]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[15]
Open API Initiative, "OpenAPI 3.0.0 Specification": https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md.
[16]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[17]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[18]
TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
[19]
RFC 6749:  "The OAuth 2.0 Authorization Framework".
[20]
TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
[21]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[22]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[23]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[24]
TR 21.900: "Technical Specification Group working methods".
[25]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[26]
TS 33.434: "Service Enabler Architecture Layer for Verticals (SEAL); Security Aspects".
Up

3  Definitions of terms and abbreviationsWord‑p. 12

3.1  Terms

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.
VAL service:
A generic name for any service offered by the VAL service provider to their VAL users.
SEAL service:
A generic name for a common service (e.g. group management, configuration management, location management) that can be utilized by multiple vertical applications.
SEAL provider:
Provider of SEAL service(s).
VAL server:
A generic name for the server application function of a specific VAL service.
SEAL server:
An entity that provides the server side functionalities corresponding to the specific SEAL service.
VAL system:
The collection of applications, services, and enabling capabilities required to support a VAL service.
VAL group:
A defined set of VAL UEs or VAL users configured for specific purpose in a VAL service.
VAL group home system:
The VAL system where the VAL group is defined.
VAL group member:
A VAL service user, whose VAL user ID is listed in a particular VAL group.
Vertical application:
An application catering to a specific vertical.
Up

3.2  Abbreviations

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
AEF
API Exposing Function
API
Application Programming Interface
JSON
JavaScript Object Notation
NDS
Network Domain Security
NDS/IP
NDS for IP based protocols
PLMN
Public Land Mobile Network
REST
Representational State Transfer
SCEF
Service Capability Exposure Function
SCS
Service Capability Server
SEAL
Service Enabler Architecture Layer for Verticals
TMGI
Temporary Mobile Group Identity
UE
User Equipment
VAL
Vertical Application Layer
Up

4  OverviewWord‑p. 13

3GPP has considered in TS 23.434 the development of Service enabler architecture layer for verticals (SEAL) over 3GPP networks to support vertical applications (e.g. V2X applications). It specifies the functional architecture for SEAL and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP systems. To ensure efficient use and deployment of vertical applications over 3GPP systems, SEAL services includes, group management, configuration management, location management, identity management, key management and network resource management.
3GPP TS 23.434, clause 6 specifies the functional entities and domains of the functional model, reference points descriptions and SEAL APIs for SEAL services.
The present document specifies the APIs needed to support SEAL.
Up

Up   Top   ToC