Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  19.0.0

Top   Top   None   None   Next
0…   4…   5   6…   6.4…   6.5…   6.5.3…   7…   8…   8.2.2…   9…   9.3…   9.3.2.21…   9.3.3…   9.3.6…   9.3.11…   9.3.13…   9.3.14…   9.4…   9.4.6…   9.5…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.3.10…   10.4…   11…   11.3…   11.3.3…   11.4…   12…   12.3…   13…   14…   14.2.2.2…   14.3…   14.3.2.20…   14.3.2.40…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6   14.3.4.7…   14.3.4A…   14.3.4A.3…   14.3.4A.4…   14.3.4A.6…   14.3.4A.8…   14.3.4A.9…   14.3.4A.10…   14.3.5…   14.3.6…   14.3.9…   14.3.12…   14.4…   15…   16…   17…   18…   A   B…

 

0  Introductionp. 18

This document specifies a functional architecture for service enabler architecture layer (SEAL) over 3GPP networks to support vertical applications (e.g. V2X applications). This functional architecture will include common application plane and signalling plane entities. A set of common services (e.g. group management, configuration management, location management) specified in this document can be shared across vertical applications.
The SEAL functional architecture takes into consideration the common capabilities to support mission critical and other vertical applications.
Up

1  Scopep. 19

The present document specifies the functional architecture for service enabler architecture layer (SEAL) and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system. The present document is applicable to vertical applications using E-UTRAN or NR access based on the EPS or 5GS architecture defined in TS 23.401, TS 23.246, TS 23.468, TS 23.501, and TS 23.247. To ensure efficient use and deployment of vertical applications over 3GPP systems this specification for SEAL services includes the group management, configuration management, location management, identity management, key management, network resource management, notification management, network slice capability enablement, data delivery and application data analytics enablement.
Up

2  Referencesp. 19

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.104: "Service requirements for cyber-physical control applications in vertical domains".
[3]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[4]
TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[5]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[6]
TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[7]
TS 23.286: "Application layer support for V2X services; Functional architecture and information flows".
[8]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[9]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[10]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[11]
TS 23.502: "Procedures for the 5G System; Stage 2".
[12]
TS 23.303: "Proximity-based services (ProSe); Stage 2".
[13]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[14]
TS 23.002: "Network Architecture".
[15]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[16]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[17]
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[18]
TS 23.203: "Policy and charging control architecture".
[19]
TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[20]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[21]
TS 29.214: "Policy and charging control over Rx reference point".
[22]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[23]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[24]
RFC 6733  (October 2012): "Diameter Base Protocol".
[25]
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".
[26]
ETSI TS 102 965 (V1.4.1): "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID); Registration".
[27]
ISO TS 17419: "Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context".
[28]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[29]
TS 33.434: "Service Enabler Architecture Layer (SEAL); Security aspects for Verticals".
[30]
TS 29.549: "Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage3".
[31]
TS 23.285: "Architecture enhancements for V2X services".
[32]
RFC 7252:  "The Constrained Application Protocol (CoAP)".
[33]
RFC 8323:  "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
[34]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[35]
IEEE Std 802.1Qcc-2018: "Standard for Local and metropolitan area networks - Bridges and Bridged Networks - Amendment: Stream Reservation Protocol (SRP) Enhancements and Performance Improvements".
[36]
IEEE 802.1Q-2018: "IEEE Standard for Local and Metropolitan Area Networks-Bridges and Bridged Networks".
[37]
IEEE Std 802.1CB-2017: "Frame Replication and Elimination for Reliability".
[38]
TS 23.003: "Numbering, Addressing and Identification".
[39]
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[40]
TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[41]
TS 28.531: "Management and orchestration; Provisioning".
[42]
TS 28.533: "Management and orchestration; Architecture framework".
[43]
TS 28.530: "Management and orchestration; Concepts, use cases and requirements".
[44]
TS 28.532: "Management and orchestration; Generic management services".
[45]
TS 28.552: "Management and orchestration; 5G performance measurements".
[46]
TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[47]
TS 28.104: "Management and orchestration; Management Data Analytics".
[48]
TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".
[49]
TS 23.436: "Procedures for Application Data Analytics Enablement Service".
[50]
TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2"
[51]
TS 29.572: "5G System; Location Management Services; Stage 3"
[52]
TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[53]
TS 37.355: "LTE Positioning Protocol (LPP)".
[54]
TS 29.122: "T8 reference point for Northbound APIs".
[55]
TS 23.545: "Application layer support for Factories of the Future (FF)".
→ to date, still a draft
Up

3  Definitions, symbols and abbreviationsp. 21

3.1  Definitionsp. 21

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.
VAL user:
An authorized user, who can use a VAL UE to participate in one or more VAL services.
VAL user ID:
A generic name for the user ID of a VAL user within a specific VAL service.
VAL UE:
A UE that can be used to participate in one or more VAL services.
VAL client:
An entity that provides the client side functionalities corresponding to the vertical applications.
SEAL client:
An entity that provides the client side functionalities corresponding to the specific SEAL service.
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.
Primary VAL system:
VAL system where the VAL user profiles of a VAL user are defined.
Partner VAL system:
A VAL system that has a business relationship with the primary VAL system such that service can be offered to primary VAL system users.
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.
VAL stream:
A time sensitive communication stream is used to transport a time sensitive data flow, and is defined by a stream specification (which identifies a source and destination of the data flow) and a traffic specification (which defines the characteristics of the data flow). VAL stream is identified by a VAL stream ID.
Vertical:
See vertical domain.
Vertical application:
An application catering to a specific vertical.
MBS session announcement:
Mechanism to provide the necessary information to the NRM client to enable the reception of the VAL service data via the MBS session.
For the purposes of the present document, the following terms and definitions given in TS 22.104 apply:
Vertical domain
Up

3.2  Abbreviationsp. 22

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
5GVN
5G Virtual Network
CAPIF
Common API Framework for northbound APIs
CNC
Centralized Network Configuration
CRUDN
Create, Retrieve, Update, Delete and Notify
EPC
Evolved Packet Core
GPSI
Generic Public Subscription Identifier
LWP
Light-weight Protocol
NEF
Network Exposure Function
NR
New Radio
NOP
Network Operator
NSaaS
Network Slice as a Service
PCC
Policy and Charging Control
SCEF
Service Capability Exposure Function
SEAL
Service Enabler Architecture Layer for Verticals
SEAL-UU
Service Enabler Architecture Layer for Verticals, Universal UE-network interface
TSC
Time Sensitive Communication
TSN
Time Sensitive Networking
VAL
Vertical Application Layer
Up

Up   Top   ToC