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 24.543  Word version:  18.0.0

Top   Top   None   None   Next
1…   7…   A… 
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  3.1 Terms  3.2 Abbreviations  4 General description  5 Edge applications over 3GPP services  6 Functional entities 
...

 

1  Scope  p. 10

The present document specifies the protocol aspects for the data delivery management capability of SEAL for the application content/data for vertical applications (e.g. V2X) over the 3GPP system as part of SEAL services specified in TS 23.434 and TS 23.433.
The present document is applicable to the user equipment (UE) supporting the data delivery management client functionality as described in TS 23.433, to the application server supporting the data delivery management server functionality as described in TS 23.433 and to the application server supporting the vertical application server (VAL server) functionality as defined in the specific vertical application service (VAL service) specifications.
Up

2  References  p. 10

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.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".
[3]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[4]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[5]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[6]
TS 24.546: "Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[7]
TS 24.547: "Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[8]
TS 24.558: "Enabling Edge Applications; Protocol specification".
[9]
TS 29.548: "Service Enabler Architecture Layer for Verticals (SEAL); SEAL Data Delivery (SEALDD) Server Services; Stage 3".
[10]
TS 29.558: "Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3".
[11]
RFC 3339:  "Date and Time on the Internet: Timestamps".
[12]
RFC 4825:  "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".
[13]
RFC 6750:  "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[14]
RFC 7252:  "The Constrained Application Protocol (CoAP)".
[15]
RFC 7641:  "Observing Resources in the Constrained Application Protocol (CoAP)".
[16]
RFC 7959:  "Block-Wise Transfers in the Constrained Application Protocol (CoAP) ".
[17]
RFC 8132:  "PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)".
[18]
RFC 8323:  "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
[19]
RFC 8610:  "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".
[20]
RFC 8949:  "Concise Binary Object Representation (CBOR)".
[21]
RFC 9110:  "HTTP Semantics".
[22]
RFC 9177:  "Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission".
[23]
OMA OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification".
Up

3  Definitions of terms, symbols and abbreviations  p. 11

3.1  Terms  p. 11

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.
Data delivery management SEAL client:
An entity that provides the client side functionalities corresponding to the data delivery management SEAL service.
Data delivery management SEAL server:
An entity that provides the server side functionalities corresponding to the data delivery management SEAL service.
For the purposes of the present document, the following terms and definitions given in TS 23.434 apply:
SEAL client
SEAL server
SEAL service
VAL user
VAL server
VAL service
Vertical
Vertical application
Up

3.2  Abbreviations  p. 11

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.
ACR
Application Context Relocation
API
Application Programming Interface
CDDL
Concise Data Definition Language
CoAP
Constrained Application Protocol
DNS
Domain Name System
EAS
Edge Application Server
ECS
Edge Configuration Server
EDN
Edge Data Network
EES
Edge Enabler Server
MIME
Multipurpose Internet Mail Extensions
NAS
Non Access Stratum
SEAL
Service Enabler Architecture Layer for verticals
SEALDD
SEAL Data Delivery
SDDM
SEAL Data Delivery Management
SDDM-C
SEAL Data Delivery Management Client
SDDM-S
SEAL Data Delivery Management Server
URI
Uniform Resource Identifier
URL
Uniform Resource Locator
URLLC
Ultra-Reliable Low Latency Communication
V2X
Vehicle-to-Everything
VAL
Vertical Application Layer
XCAP
XML Configuration Access Protocol
Up

4  General description  p. 12

Data delivery management is a SEAL service that provides the data delivery management related capabilities (data delivery and storage capabilities) to one or more vertical applications. The present document enables a SEAL data delivery management client (SDDM-C) and a VAL server to communicate with a SEAL data delivery management server (SDDM-S).

5  Edge applications over 3GPP services  p. 12

The SDDM-C and the SDDM-S can utilize edge applications over 3GPP services to support SDDM. The edge applications over 3GPP services are specified in TS 24.558 and TS 29.558. Interactions between the SDDM-C, the SDDM-S and the edge applications over 3GPP services are described in detail in clause 7.

6  Functional entities  p. 12

6.1  SEAL data delivery management client (SDDM-C)  p. 12

The SDDM-C functional entity acts as the application client for data delivery management related transactions. To be compliant with the procedures in the present document the SDDM-C:
  1. shall support the role of XCAP client as specified in RFC 4825;
  2. shall support the role of XDMC as specified in OMA OMA-TS-XDM_Core-V2_1 [23]; and
  3. shall support the data delivery management procedures in subclause 7.2.
To be compliant with the CoAP procedures in the present document the SDDM-C:
  1. shall support the role of CoAP client as specified in RFC 7252;
  2. shall support the capability to observe resources as specified in RFC 7641;
  3. shall support the block-wise transfer as specified in RFC 7959;
  4. may support the robust block transfer as specified in RFC 9177;
  5. shall support FETCH method of CoAP as specified in RFC 8132;
  6. should support CoAP over TCP and Websocket as specified in RFC 8323;
  7. shall support CBOR encoding as specified in RFC 8949; and
  8. shall support the procedures defined in clause 7.2.
Up

6.2  SEAL data delivery management server (SDDM-S)  p. 13

The SDDM-S is a functional entity used to provide data delivery management supported within the vertical application layer. To be compliant with the procedures in the present document the SDDM-S:
  1. shall support the role of XCAP server as specified in RFC 4825;
  2. shall support the role of XDMS as specified in OMA OMA-TS-XDM_Core-V2_1 [23]; and
  3. shall support the data delivery management procedures in subclause 7.2.
To be compliant with the CoAP procedures in the present document the SDDM-S:
  1. shall support the role of CoAP server as specified in RFC 7252;
  2. shall support the capability to observe resources as specified in RFC 7641;
  3. shall support the block-wise transfer as specified in RFC 7959;
  4. shall support the robust block transfer as specified in RFC 9177;
  5. shall support FETCH method of CoAP as specified in RFC 8132;
  6. shall support CoAP over TCP and Websocket as specified in RFC 8323;
  7. shall support CBOR encoding as specified in RFC 8949; and
  8. shall support the procedures defined in clause 7.2.
Up

Up   Top   ToC