ETSI TS 124 546 V19.3.0 (2026-03)

5G; Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification (3GPP TS 24.546 version 19.3.0 Release 19)

RTS/TSGC-0124546vj30

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
Configuration management - Service Enabler Architecture
Layer for Verticals (SEAL);
Protocol specification
(3GPP TS 24.546 version 19.3.0 Release 19)

3GPP TS 24.546 version 19.3.0 Release 19 1 ETSI TS 124 546 V19.3.0 (2026-03)

Reference
RTS/TSGC-0124546vj30
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 2 ETSI TS 124 546 V19.3.0 (2026-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 3 ETSI TS 124 546 V19.3.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 7
1 Scope . 9
2 References . 9
3 Definitions of terms and abbreviations. 10
3.1 Terms . 10
3.2 Abbreviations . 11
4 General description. 11
5 Functional entities . 11
5.1 SEAL configuration management client (SCM-C) . 11
5.2 SEAL configuration management server (SCM-S) . 12
6 Configuration management procedures . 13
6.1 General . 13
6.2 On-network procedures . 13
6.2.1 General . 13
6.2.1.1 Authenticated identity in HTTP request . 13
6.2.1.2 Authenticated identity in CoAP request . 13
6.2.2 Common procedures . 13
6.2.2.1 Management of configuration update event subscription. 13
6.2.2.1.1 SIP based procedures . 13
6.2.2.1.2 HTTP based procedures. 15
6.2.2.1.3 CoAP based procedures . 16
6.2.2.2 Notifications . 17
6.2.2.2.1 SIP based procedures . 17
6.2.2.2.2 HTTP based procedures. 17
6.2.2.2.3 CoAP based procedures . 18
6.2.3 VAL UE configuration data . 18
6.2.3.1 SCM client HTTP procedure. 18
6.2.3.2 SCM server HTTP procedure . 18
6.2.3.3 SCM client CoAP procedure . 19
6.2.3.4 SCM server CoAP procedure . 19
6.2.4 VAL user profile data . 20
6.2.4.1 SCM client HTTP procedure. 20
6.2.4.2 SCM server HTTP procedure . 20
6.2.4.3 SCM client CoAP procedure . 20
6.2.4.4 SCM server CoAP procedure . 20
6.2.5 Update VAL user profile data . 21
6.2.5.1 SCM client HTTP procedure. 21
6.2.5.2 SCM server HTTP procedure . 21
6.2.5.3 SCM client CoAP procedure . 22
6.2.5.4 SCM server CoAP procedure . 22
6.2.6 Application satellite coverage information provisioning . 22
6.2.6.1 SCM client HTTP procedure. 22
6.2.6.2 SCM server HTTP procedure . 23
6.2.7 UE requesting the application satellite coverage availability information . 23
6.2.7.1 SCM client HTTP procedure. 23
6.2.7.2 SCM server HTTP procedure . 24
6.3 Off-network procedures . 24
7 Coding . 24
7.1 VAL user profile document . 24
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 4 ETSI TS 124 546 V19.3.0 (2026-03)
7.1.1 General . 24
7.1.2 Application unique ID . 24
7.1.3 Data structure . 24
7.1.4 XML Schema . 25
7.1.5 Semantics . 25
7.1.6 MIME type. 26
7.1.7 IANA registration template. 26
7.2 VAL UE configuration document . 28
7.2.1 General . 28
7.2.2 Application unique ID . 28
7.2.3 Data structure . 28
7.2.4 XML schema . 28
7.2.5 Semantics . 30
7.2.6 MIME type. 31
7.2.7 IANA registration template. 31
7.3 VAL UE satellite information document . 32
7.3.1 General . 32
7.3.2 Application unique ID . 32
7.3.3 Data structure . 32
7.3.4 XML schema . 33
7.3.5 Semantics . 35
7.3.6 MIME type. 36
7.3.7 IANA registration template. 36
Annex A (normative): Parameters for different operations . 38
A.1 Creating configuration update event subscription . 38
A.1.1 General . 38
A.1.2 Client side parameters . 38
A.1.3 Server side parameters . 38
A.2 Retrieve VAL UE configuration data . 38
A.2.1 Client side parameters . 38
Annex B (normative): Parameters for notifications . 40
B.1 General . 40
B.2 Configuration update notification . 40
Annex C (normative): CoAP resource representation and encoding . 41
C.1 General . 41
C.1.1 Resource URI structure . 41
C.1.2 Use of cache . 41
C.1.3 Error handling . 41
C.1.4 Data types applicable to multiple resource representations . 44
C.1.4.1 General . 44
C.1.4.2 Referenced structured data types . 44
C.1.4.3 Referenced simple data types and enumerations . 44
C.1.4.4 Common structured data types. 46
C.1.4.4.1 Type: ScheduledCommunicationTime . 46
C.1.4.4.2 Type: ProblemDetails. 46
C.1.4.4.3 Type: GeographicalCoordinates . 46
C.1.4.4.4 Type: GeographicArea . 47
C.1.4.4.5 Type: Point . 47
C.1.4.4.6 Type: PointUncertaintyCircle . 47
C.1.4.4.7 Type: PointUncertaintyEllipse . 47
C.1.4.4.8 Type: Polygon . 48
C.1.4.4.9 Type: PointAltitude . 48
C.1.4.4.10 Type: PointAltitudeUncertainty . 48
C.1.4.4.11 Type: EllipsoidArc . 48
C.1.4.4.12 Type: UncertaintyEllipse . 49
C.1.4.5 Common enumerations . 49
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 5 ETSI TS 124 546 V19.3.0 (2026-03)
C.1.4.5.1 Enumeration: SupportedGADShapes . 49
C.2 Resource representation and APIs for VAL user profile . 49
C.2.1 SU_UserProfile API . 49
C.2.1.1 API URI . 49
C.2.1.2 Resources . 50
C.2.1.2.1 Overview . 50
C.2.1.2.2 Resource: User Profiles . 50
C.2.1.2.2.1 Description . 50
C.2.1.2.2.2 Resource Definition . 50
C.2.1.2.2.3 Resource Standard Methods . 51
C.2.1.2.3 Resource: Individual User Profile . 52
C.2.1.2.3.1 Description . 52
C.2.1.2.3.2 Resource Definition . 52
C.2.1.2.3.3 Resource Standard Methods . 52
C.2.1.3 Data Model . 53
C.2.1.3.1 General . 53
C.2.1.3.2 Structured data types . 54
C.2.1.3.2.1 Type: ProfileDoc . 54
C.2.1.3.2.2 Type: ProfileInfo . 54
C.2.1.3.2.3 Type: ProfileConfig . 54
C.2.1.3.2.4 Type: ValTargetUe . 54
C.2.1.3.3 Simple data types and enumerations . 55
C.2.1.3.3.1 Enumeration: ConfigType . 55
C.2.1.4 Error Handling . 55
C.2.1.5 CDDL Specification . 55
C.2.1.5.1 Introduction . 55
C.2.1.5.2 CDDL document . 55
C.2.1.6 Media Type . 56
C.2.1.7 Media Type registration for application/vnd.3gpp.seal-user-profile-info+cbor. 56
C.3 Resource representation and APIs for UE configuration . 57
C.3.1 SU_UeConfig API . 57
C.3.1.1 API URI . 57
C.3.1.2 Resources . 57
C.3.1.2.1 Overview . 57
C.3.1.2.2 Resource: UE Configurations. 58
C.3.1.2.2.1 Description . 58
C.3.1.2.2.2 Resource Definition . 58
C.3.1.2.2.3 Resource Standard Methods . 58
C.3.1.2.3 Resource: Individual UE Configuration . 59
C.3.1.2.3.1 Description . 59
C.3.1.2.3.2 Resource Definition . 59
C.3.1.2.3.3 Resource Standard Methods . 60
C.3.1.3 Data Model . 61
C.3.1.3.1 General . 61
C.3.1.3.2 Structured data types . 62
C.3.1.3.2.1 Type: UeConfigDoc . 62
C.3.1.3.2.2 Type: UeConfig . 62
C.3.1.3.2.3 Type: ValUeIds . 62
C.3.1.3.2.4 Type: ImeiRange . 62
C.3.1.3.2.5 Type: SnrRange . 63
C.3.1.3.3 Simple data types and enumerations . 63
C.3.1.3.3.1 Simple data types . 63
C.3.1.4 Error Handling . 63
C.3.1.5 CDDL Specification . 63
C.3.1.5.1 Introduction . 63
C.3.1.5.2 CDDL document . 63
C.3.1.6 Media Type . 64
C.3.1.7 Media Type registration for application/vnd.3gpp.seal-ue-config-info+cbor . 64
Annex D (informative): Change history . 66
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 6 ETSI TS 124 546 V19.3.0 (2026-03)
History . 68

ETSI
3GPP TS 24.546 version 19.3.0 Release 19 7 ETSI TS 124 546 V19.3.0 (2026-03)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 8 ETSI TS 124 546 V19.3.0 (2026-03)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 9 ETSI TS 124 546 V19.3.0 (2026-03)
1 Scope
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 3GPP TS 23.434 [2], to the application server supporting the configuration management
server functionality as described in 3GPP TS 23.434 [2] and to the application server supporting the vertical application
server (VAL server) functionality as defined in specific vertical application service (VAL service) specification.
NOTE: The specification of the VAL server for a specific VAL service is out of scope for present document.
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional
architecture and information flows".
[3] IETF 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] 3GPP TS 24.547: "Identity management - Service Enabler Architecture Layer for Verticals
(SEAL); Protocol specification".
[6] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[7] IETF RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format".
[8] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP); Stage 3".
[9] IETF RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol
(XCAP) Diff Event Package".
[10] IETF RFC 6050: "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[11] IETF RFC 6665: "SIP-Specific Event Notification".
[12] IETF RFC 7252: "The Constrained Application Protocol (CoAP)".
[13] IETF RFC 7959: "Block-Wise Transfers in the Constrained Application Protocol (CoAP)".
[14] IETF RFC 7641: "Observing Resources in the Constrained Application Protocol (CoAP)".
[15] IETF RFC 8323: "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
[16] void
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 10 ETSI TS 124 546 V19.3.0 (2026-03)
[17] IETF RFC 8949: "Concise Binary Object Representation (CBOR)".
[18] IETF 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] IETF RFC 9290: "Concise Problem Details for Constrained Application Protocol (CoAP) APIs”.
[21] IETF RFC 9177: "Constrained Application Protocol (CoAP) Block-Wise Transfer Options
Supporting Robust Transmission".
[22] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[23] 3GPP TS 29.501: "Principles and Guidelines for Services Definition".
[24] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data
Networks and Applications".
[25] IETF RFC 3339: "Date and Time on the Internet: Timestamps".
[26] 3GPP TS 23.003: "Numbering, addressing and identification".
[27] Void
[28] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;
Stage 3".
[29] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".
[30] IETF RFC 9110: "HTTP Semantics".
[31] 3GPP TS 29.122: "T8 reference point for northbound Application Programming Interfaces
(APIs)".
[32] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[33] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC) protocol specification".
3 Definitions of terms and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term
defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
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 3GPP TS 23.434 [2] apply:
SEAL client
SEAL server
SEAL service
VAL server
VAL service
VAL user
Vertical
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 11 ETSI TS 124 546 V19.3.0 (2026-03)
Vertical application
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
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
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).
5 Functional entities
5.1 SEAL configuration management client (SCM-C)
The SCM-C functional entity acts as the application client for configuration related transactions.
To be compliant with the HTTP procedures in the present document the SCM-C:
- shall support the role of XCAP client as specified in IETF RFC 4825 [3];
- shall support the role of XDMC as specified in OMA OMA-TS-XDM_Core-V2_1 [4];
- shall support the procedures in clause 6.2.2;
- shall support the procedures in clause 6.2.3;
- shall support the procedures in clause 6.2.4;and
- shall support the procedures in clause 6.2.5.
To be compliant with the CoAP procedures in the present document the SCM-C:
- shall support the role of CoAP client as specified in IETF RFC 7252 [12];
- shall support the capability to observe resources as specified in IETF RFC 7641 [14];
- shall support the block-wise transfer as specified in IETF RFC 7959 [13];
- may support the robust block transfer as specified in IETF RFC 9177 [21];
- should support CoAP over TCP and Websocket as specified in IETF RFC 8323 [15];
- shall support CBOR encoding as specified in IETF RFC 8949 [17];
- shall support the procedures in clause 6.2.2;
- shall support the procedures in clause 6.2.3;
- shall support the procedures in clause 6.2.4;and
- shall support the procedures in clause 6.2.5
ETSI
3GPP TS 24.546 version 19.3.0 Release 19 12 ETSI TS 124 546 V19.3.0 (2026-03)
NOTE 1: The security mechanism to be supported for the CoAP procedures is described in 3GPP TS 24.547 [5].
NOTE 2: Support for TCP for the CoAP procedures is required if the client connects over the network which blocks
or impedes the use of UDP, e.g. when NATs are present in the communication path.
NOTE 3: The CoAP protocol suppor
...