Content for TS 24.546 Word version: 17.5.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 General description
...
...
1 Scope p. 8
The present document specifies the protocol aspects for the configuration management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system.
The present document is applicable to the User Equipment (UE) supporting the configuration management client functionality as described in TS 23.434, to the application server supporting the configuration management server functionality as described in TS 23.434 and to the application server supporting the vertical application server (VAL server) functionality as defined in specific vertical application service (VAL service) specification.
2 References p. 8
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]
RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".
[4]
OMA OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification".
[5]
TS 24.547: "Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification;".
[6]
RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[7]
RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format".
[8]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[9]
RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[10]
RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[11]
RFC 6665 (July 2012): "SIP-Specific Event Notification".
[12]
RFC 7252: "The Constrained Application Protocol (CoAP)".
[13]
RFC 7959: "Block-Wise Transfers in the Constrained Application Protocol (CoAP) ".
[14]
RFC 7641: "Observing Resources in the Constrained Application Protocol (CoAP)".
[15]
RFC 8323: "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
[16]
RFC 8516: "Too Many Requests" Response Code for the Constrained Application Protocol".
[17]
RFC 8949: "Concise Binary Object Representation (CBOR)".
[18]
RFC 8610: "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".
[19]
Constrained RESTful Environments (CoRE) Parameters at IANA, https://www.iana.org/assignments/core-parameters/core-parameters.xhtml
[20]
RFC 9290: "Concise Problem Details for Constrained Application Protocol (CoAP) APIs.
[21]
draft-ietf-core-new-block-14 "Constrained Application Protocol (CoAP) Block-Wise Transfer Options Supporting Robust Transmission".
[22]
RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[23]
TS 29.501: "Principles and Guidelines for Services Definition".
[24]
TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications".
[25]
RFC 3339: "Date and Time on the Internet: Timestamps".
[26]
TS 23.003: "Numbering, addressing and identification".
[27]
RFC 8132: "PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)".
[28]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
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.
SEAL configuration management client:
An entity that provides the client side functionalities corresponding to the SEAL configuration management service.
SEAL configuration management server:
An entity that provides the server side functionalities corresponding to the SEAL configuration management 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 server
VAL service
VAL user
Vertical
Vertical application
3.2 Abbreviations p. 10
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.
MIME
Multipurpose Internet Mail Extensions
SCM-C
SEAL Configuration Management Client
SCM-S
SEAL Configuration Management Server
SEAL
Service Enabler Architecture Layer for verticals
4 General description p. 10
Configuration management is a SEAL service that provides the configuration management related capabilities to one or more vertical applications. The present document enables a SEAL configuration management client (SCM-C) and a VAL server to manage configuration data in a SEAL configuration management server (SCM-S).
