ETSI TS 124 550 V19.1.0 (2026-03)

5G; Digital asset, Spatial mapping and Spatial anchors server - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; (3GPP TS 24.550 version 19.1.0 Release 19)

RTS/TSGC-0124550vj10

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;
Digital asset, Spatial mapping and Spatial anchors server -
Service Enabler Architecture Layer for Verticals (SEAL);
Protocol specification;
(3GPP TS 24.550 version 19.1.0 Release 19)


3GPP TS 24.550 version 19.1.0 Release 19 1 ETSI TS 124 550 V19.1.0 (2026-03)

Reference
RTS/TSGC-0124550vj10
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.550 version 19.1.0 Release 19 2 ETSI TS 124 550 V19.1.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.550 version 19.1.0 Release 19 3 ETSI TS 124 550 V19.1.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 8
2 References . 8
3 Definitions of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Overview . 9
5 Digital Asset, Spatial Anchor and Spatial Map Services . 9
5.1 Introduction . 9
5.2 Spatial Anchor Services . 10
5.2.1 SS_SAnManagement Service . 10
5.2.1.1 Service Description . 10
5.2.1.2 Service Operations . 10
5.2.1.2.1 Introduction . 10
5.2.1.2.2 SS_SAnManagement_Create . 10
5.2.1.2.3 SS_SAnManagement_Update . 11
5.2.1.2.4 SS_SAnManagement_Delete . 12
5.2.1.2.5 SS_SAnManagement_Subscribe . 12
5.2.1.2.6 SS_SAnManagement_UpdateSubscription . 12
5.2.1.2.7 SS_SAnManagement_Unsubscribe . 13
5.2.1.2.8 SS_SAnManagement_Notify . 13
5.2.1.2.9 SS_SAnManagement_Retrieve . 14
5.2.1.2.10 SS_SAnUsage_Report . 14
5.2.2 SS_SAnDiscovery Service . 15
5.2.2.1 Service Description . 15
5.2.2.2 Service Operations . 15
5.2.2.2.1 Introduction . 15
5.2.2.2.2 SS_SAnDiscovery_Request . 15
5.3 Spatial Map Services . 16
5.3.1 SS_SmManagement Service . 16
5.3.1.1 Service Description . 16
5.3.1.2 Service Operations . 16
5.3.1.2.1 Introduction . 16
5.3.1.2.2 SS_SmManagement_Create . 16
5.3.1.2.3 SS_SmManagement_Update . 17
5.3.1.2.4 SS_SmManagement_Delete . 18
5.3.1.2.5 SS_SmManagement_Retrieve . 18
5.3.1.2.6 SS_SmManagement_Subscribe . 18
5.3.1.2.7 SS_SmManagement_UpdateSubscription . 19
5.3.1.2.8 SS_SmManagement_Unsubscribe . 19
5.3.1.2.9 SS_SmManagement_Notify . 20
5.3.1.2.10 SS_SmLocalization_Request . 20
5.3.2 SS_SmDiscovery Service . 21
5.3.2.1 Service Description . 21
5.3.2.2 Service Operations . 21
5.3.2.2.1 Introduction . 21
5.3.2.2.2 SS_SmDiscovery_Request . 21
5.3.3 SS_SmDataSourceRegistration Service . 22
5.3.3.1 Service Description . 22
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 4 ETSI TS 124 550 V19.1.0 (2026-03)
5.3.3.2 Service Operations . 22
5.3.3.2.1 Introduction . 22
5.3.3.2.2 SS_SmDataSourceRegistration_Request . 22
5.3.3.2.3 SS_SmDataSourceRegistration_Update . 22
5.3.3.2.4 SS_SmDataSourceRegistration_Deregister . 23
5.3.3.2.5 SS_SmDataSourceDiscovery_Notify . 23
5.4 Digital Asset Services . 24
5.4.1 SS_DADiscovery Service . 24
5.4.1.1 Service Description . 24
5.4.1.2 Service Operations . 24
5.4.1.2.1 Introduction . 24
5.4.1.2.2 SS_DADiscovery_Request . 24
5.4.2 SS_DAProfileManagement Service . 25
5.4.2.1 Service Description . 25
5.4.2.2 Service Operations . 25
5.4.2.2.1 Introduction . 25
5.4.2.2.2 SS_DAProfileManagement_Create . 25
5.4.2.2.3 SS_DAProfileManagement_Update . 26
5.4.2.2.4 SS_DAProfileManagement_Delete . 26
5.4.2.2.5 SS_DAProfileManagement_Retrieve . 26
5.4.3 SS_DAMediaManagement Service . 27
5.4.3.1 Service Description . 27
5.4.3.2 Service Operations . 27
5.4.3.2.1 Introduction . 27
5.4.3.2.2 SS_DAMediaManagement_Upload . 27
5.4.3.2.3 DA client downloading digital asset media request at DA server using

SS_DAMediaManagement_Download operation . 28
5.4.3.2.4 SS_DAMediaManagement_Update . 28
5.4.3.2.5 SS_DAMediaManagement_Delete. 29
6 API Definitions . 29
6.1 Spatial Anchor Server APIs. 29
6.2 Spatial Map Server APIs . 29
6.2.1 SS_SmDataSourceRegistration Service API . 29
6.2.1.1 Introduction . 29
6.2.1.2 Usage of HTTP and common API related aspects . 30
6.2.1.3 Resources . 30
6.2.1.3.1 Overview . 30
6.2.1.3.2 Resource: Spatial Map Data Source Registration Lists . 30
6.2.1.4 Resource: Individual Spatial Map Data Source registration . 32
6.2.1.4.1 Description . 32
6.2.1.4.2 Resource Definition . 32
6.2.1.4.3 Resource Standard Methods . 32
6.2.1.5 Notifications . 35
6.2.1.5.1 General . 36
6.2.1.5.2 Spatial Maps Data Source Notification . 36
6.2.1.6 Data Model . 37
6.2.1.6.1 General . 37
6.2.1.6.2 Structured data types . 38
6.2.1.6.3 Simple data types and enumerations . 39
6.2.1.6.4 Data types describing alternative data types or combinations of data types . 40
6.2.1.6.5 Binary data . 40
6.2.1.7 Error Handling . 40
6.2.1.7.1 General . 40
6.2.1.7.2 Protocol Errors . 40
6.2.1.7.3 Application Errors . 40
6.2.1.8 Feature negotiation . 40
6.3 Digital Asset Server APIs . 40
6.3.1 SS_DADiscovery Service API . 40
6.3.1.1 Introduction . 40
7 Using Common API Framework . 41
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 5 ETSI TS 124 550 V19.1.0 (2026-03)
Annex A (normative): Spatial Anchor Server OpenAPI specification . 42
A.1 General . 42
A.2 SS_SAnManagement API . 42
Annex B (normative): Spatial Map Server OpenAPI specification . 43
B.1 General . 43
B.2 SS_SmManagement API . 43
B.3 SS_SmDataSourceRegistration API . 43
Annex C (informative): Change history . 49
History . 50

ETSI
3GPP TS 24.550 version 19.1.0 Release 19 6 ETSI TS 124 550 V19.1.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.550 version 19.1.0 Release 19 7 ETSI TS 124 550 V19.1.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.550 version 19.1.0 Release 19 8 ETSI TS 124 550 V19.1.0 (2026-03)
1 Scope
The present document specifies the protocol aspects and APIs for the metaverse application over the 3GPP network for
SAn-UU, SM-UU, and DA-UU reference points. The APIs are specified as RESTful APIs except for custom operations
wherever required.
The present document is applicable to the user equipment (UE) supporting the digital asset as described in
3GPP TS 23.438 [3], spatial mapping and spatial anchor client functionalities as described in 3GPP TS 23.437 [2], to
the application server supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial
anchor server functionalities as described in 3GPP TS 23.437 [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 of the 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.437: "Service Enabler Architecture Layer for Verticals (SEAL); Spatial map and
Spatial anchors; Stage 2".
[3] 3GPP TS 23.438: "Service Enabler Architecture Layer for Verticals (SEAL); Digital assets Stage
2".
[4] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[5] 3GPP TS 24.545: "Location Management - Service Enabler Architecture Layer for Verticals
(SEAL); Protocol specification".
[6] 3GPP TS 29.437: "Service Enabler Architecture Layer for Verticals (SEAL); Metaverse
Enablement Services; Stage 3".
[7] 3GPP TS 29.549: "Service Enabler Architecture Layer for Verticals (SEAL); Application
Programming Interface (API) specification; Stage 3".
[8] 3GPP TS 29.122: "T8 reference point for Northbound APIs".
[9] 3GPP TS 29.558: "Enabling Edge Applications; Application Programming Interface (API)
specification; Stage 3".
3 Definitions of terms, symbols 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].
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 9 ETSI TS 124 550 V19.1.0 (2026-03)
3.2 Symbols
Void.
3.3 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].
DA Digital Asset
SAn-C Spatial Anchor Client
SAn-S Spatial Anchor Server
SEAL Service Enabler Architecture Layer for verticals
SM-C Spatial Map Client
SM-S Spatial Map Server
VAL Vertical Application Layer
4 Overview
Spatial anchor, spatial mapping and digital assets are the SEAL services that provides the spatial anchor, spatial
mapping and digital asset related capabilities to one or more vertical applications. The present document enables the:
a) SEAL spatial anchor client (SAn client) to interact with the SEAL spatial anchor server (SAn server) over the
SAn-UU interface as defined in 3GPP TS 23.437 [2] for below services;
1) spatial anchor management and usage reporting as specified in clause 5.2.1; and
2) spatial anchor discovery as specified in clause 5.2.2;
b) SEAL spatial map client (SM client) to interact with the SEAL spatial map server (SM server) over the SM-UU
interface as defined in 3GPP TS 23.437 [2] for below services;
1) spatial map management and spatial map localization as specified in clause 5.3.1;
2) spatial map discovery as specified in clause 5.3.2; and
3) spatial map data soruce management as specified in clause 5.3.3;
c) SEAL digital asset client (DA client) to interact with the SEAL digital asset server (DA server) over the DA-UU
interface as defined in 3GPP TS 23.438 [3] for below services;
1) digital asset discovery as specified in clause 5.4.1;
2) digital asset profile management as specified in clause 5.4.2; and
3) digital asset media management as specified in clause 5.4.3.
5 Digital Asset, Spatial Anchor and Spatial Map
Services
5.1 Introduction
Table 5.1-x summarizes the corresponding APIs defined for this specification.
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 10 ETSI TS 124 550 V19.1.0 (2026-03)
Table 5.1-x: API Descriptions
OpenAPI Specification
Service Name Clause Description API Name Annex
File
clause> included in the the URI> Annex
OpenAPI file> >
NOTE: When 3GPP TS 29.122 [8] is referenced for the common protocol and interface aspects for API definition
in the clauses under clause 5, the service producer (i.e. ) takes the role of
the SCEF and the service consumer (e.g. ) takes the role of the SCS/AS.
5.2 Spatial Anchor Services
5.2.1 SS_SAnManagement Service
5.2.1.1 Service Description
The SS_SAnManagement API, as defined in 3GPP TS 23.437 [2], allows the SAn client via SSAn-Uu interface to
create, update the spatial anchor at a given SAn server.
5.2.1.2 Service Operations
5.2.1.2.1 Introduction
The service operation defined for SS_SAnManagement API is shown in the table 5.2.1.2.1-1.
Table 5.2.1.2.1-1: Operations of the SS_SAnManagement API
Service operation name Description Initiated by
SS_SAnManagement_Create This service operation is used by the SAn client to SAn client, VAL
create the spatial anchor on SAn server. Server
SS_SAnManagement_Update This service operation is used by the SAn client to SAn client
update the spatial anchor on SAn server.
SS_SAnManagement_Delete This service operation is used by the SAn client to SAn client
delete the spatial anchor resource on SAn server.
SS_SAnManagement_Subscribe This service operation is used by the SAn client to SAn client
subscribe for the spatial anchor related notifications on
SAn server.
SS_SAnManagement_UpdateSubscrip This service operation is used by the SAn client to SAn client
tion update a subscription for the spatial anchor related
notifications on SAn server.
SS_SAnManagement_Unsubscribe This service operation is used by the SAn client to SAn client
unsubscribe for the spatial anchor related notifications
on SAn server.
SS_SAnManagement_Retrieve This service operation is used by SAn client to retrieve SAn client
to spatial anchor information from the SAn server.
SS_SAnManagement_Notify This service operation is used by the spatial anchor SAn server
server to notify the spatial anchor(s) related
notifications to the spatial anchor client.
SS_SAnUsage_Report This service operation is used by SAn client to report SAn client
the spatial anchor usage to the SAn server.

5.2.1.2.2 SS_SAnManagement_Create
5.2.1.2.2.1 General
This service operation is used by SAn client to create the spatial anchor at a given SAn server.
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 11 ETSI TS 124 550 V19.1.0 (2026-03)
5.2.1.2.2.2 SAn client creating spatial anchor on SAn server
Upon receiving the request from the VAL client for the creation of spatial anchor(s), the SAn client shall send an HTTP
POST request to the SAn server on the resource URI identifying the "Spatial Anchors Lists" collection resource as
specified in 3GPP TS 29.437 [6] in clause 6.1.1.3.2. The body of the HTTP POST request shall include the
"SpatialAnchorsList" data structure as specified in 3GPP TS 29.437 [6] in clause 6.1.1.6.2.2.
Upon reception of the HTTP POST message from the SAn client, the SAn server shall:
a) process the spatial anchor create request;
b) verifiy and check if the SAn client is authorized to create the spatial anchor; and
c) if the requestor is authorized, shall perform the creation of the spatial anchor(s). If the create operation:
1) is successful, then the SAn server shall further generate a globally unique spatial anchor identifier for each of
the newly created spatial anchor. The SAn server shall send the POST response with HTTP "201 Created"
status code and the POST response body including the "SpatialAnchorsList" data structure, which includes
the spatial anchor identifier(s) of newly created spatial anchor(s); and
NOTE: Associating the spatial anchor identifier with the VAL service information and requestor identifier is up
to implementation.
2) fails, then the SAn server shall send the POST response set with the appropriate HTTP status code indicating
the "failure" and the data structure as specified in 3GPP TS 29.437 [6] in clause 6.1.1.7.
5.2.1.2.3 SS_SAnManagement_Update
5.2.1.2.3.1 General
This service operation is used by SAn client to update the spatial anchor resource at a given SAn server.
5.2.1.2.3.2 SAn client updating spatial anchor on SAn server
Upon receiving the request from the VAL client to update the spatial anchor resource, the SAn client shall send:
a) an HTTP PATCH request (for partial update) to the SAn server on the resource URI identifying the "Individual
Spatial Anchors List" resource with the "SpatialAnchorsListPatch" data structure in the request message as
specified in 3GPP TS 29.437 [6] in clause 6.1.1.3.3.3.4; or
b) an HTTP PUT request (for full replacement) to the SAn server on the resource URI identifying the "Individual
Spatial Anchors List" resource with the "SpatialAnchorsList" data structure in request message as specified in
3GPP TS 29.437 [6] in clause 6.1.1.3.3.3.2.
Upon reception of the HTTP PATCH or PUT request from the SAn client, the SAn server shall:
a) validate if the SAn client is authorized to update the spatial anchor; if the SAn client is unauthorized, the HTTP
"403 Forbidden" response is sent; or
b) if the SAn client is authorized, then SAn server shall check for the spatial anchor resources. If the matching
spatial anchor resource is:
1) found, the SAn server shall:
i) update the "valServInfo", "anchors" attribute(s) of the matching spatial anchor resource with the received
spatial anchor information for the case of HTTP PATCH request;
ii) replace the matching spatial anchor resource with the received spatial anchor information for the case of
HTTP PUT request; and
iii) the SAn server shall send the HTTP "204 No Content" response to the SAn client; or
2) not found, return the HTTP "404 Not Found" response to the SAn client.
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 12 ETSI TS 124 550 V19.1.0 (2026-03)
5.2.1.2.4 SS_SAnManagement_Delete
5.2.1.2.4.1 General
This service operation is used by SAn client to delete the spatial anchor resource at a given SAn server.
5.2.1.2.4.2 SAn client deleting spatial anchor on SAn server
Upon receiving the request from the VAL client to delete the spatial anchor resource, the SAn client shall send an
HTTP DELETE request to the SAn server on the resource URI identifying the "Individual Spatial Anchors List"
resource as specified in 3GPP TS 29.437 [6] in clause 6.1.1.3.3.3.3.
Upon reception of the HTTP DELETE request from the SAn client, the SAn server shall:
a) validate if the SAn client is authorized to delete the spatial anchor; if the SAn client is unauthorized, the HTTP
"403 Forbidden" response is sent; or
b) if the SAn client is authorized, then SAn server shall check for the spatial anchor resources. If the matching
spatial anchor resource is:
1) not found, return "404 Not Found" response to the SAn client; or
2) found, delete the identified spatial anchor resource and shall send the HTTP "204 No Content" response to
the SAn client.
5.2.1.2.5 SS_SAnManagement_Subscribe
5.2.1.2.5.1 General
This service operation is used by SAn client to subscribe with the SAn server to receive notifications related to spatial
anchors.
5.2.1.2.5.2 SAn client subscribe for spatial anchor related notifications on SAn server
Upon receiving the request from the VAL client to subscribe for the spatial anchors related notifications, the SAn client
shall send an HTTP POST message to the SAn server on the resource URI identifying the "Spatial Anchors
Subscriptions" resource as specified in 3GPP TS 29.437 [6] in clause 6.1.1.3.4. The body of the HTTP POST request
shall include the "SpatialAnchorsSub" data structure as specified in 3GPP TS 29.437 [6] in clause 6.1.1.6.2.11.
Upon reception of the HTTP POST request from the SAn client, the SAn server shall:
a) validate if the SAn client is authorized to subscribe for the spatial anchors related notifications; if the SAn client
is unauthorized, the HTTP "403 Forbidden" response is sent; or
b) if the SAn client is authorized, then the SAn server shall create the subscription. If the creation of the
subscription by the SAn server:
1) is successful, then the SAn server shall further generate a globally unique spatial anchor subscription
identifier for the newly created subscription. The SAn server shall send the POST response with HTTP "201
Created" status code and the POST response body including the "SpatialAnchorsSub" data structure as
described in 3GPP TS 29.437 [6] in clause 6.1.1.6.2.11, which includes the subscription identifier(s) of newly
created subscription; or
2) fails, then the SAn server shall send the POST response set with the appropriate HTTP status code indicating
the "failure" and the data structure as specified in 3GPP TS 29.437 [6] in clause 6.1.1.7.
5.2.1.2.6 SS_SAnManagement_UpdateSubscription
5.2.1.2.6.1 General
This service operation is used by SAn client to update a subscription with the SAn server to receive notifications related
to spatial anchors.
ETSI
3GPP TS 24.550 version 19.1.0 Release 19 13 ETSI TS 124 550 V19.1.0 (2026-03)
5.2.1.2.6.2 SAn client update subscription for spatial anchor related notifications on SAn server
Upon receiving the request from the VAL client to update the subscription for the spatial anchors related notifications,
the SAn client shall send an HTTP PATCH request (for partial update) or HTTP PUT request (for full replacement) to
the SAn server on the resource URI identifying the "Individual Spatial Anchors Subscriptions" resource with the data
structure "SpatialAnchorsSubPatch" in the request as specified in 3GPP TS 29 437 [6] in clause 6.1.1.3.5.3.4 with the
data structure for an HTTP PATCH request and the "Individual Spatial Anchors Subscriptions" resource with the data
structure "SpatialAnchorsSub" in the request as specified in 3GPP TS 29.437 [6] in clause 6.1.1.3.5.3.2 for an HTTP
PUT request.
Upon reception of the HTTP PATCH or PUT request from the SAn client, the SAn server shall:
a) validate if the SAn client is authorized to update the subscription resource for spatial anchor related notifications;
if the SAn client is unauthorized, the HTTP "403 Forbidden" response is sent; or
b) if the SAn client is authorized, then SAn server shall check for the subscription resource. If the matching
subscription resource is:
1) found, the SAn server shall:
i) update the matching subscription resource in accordance with the spatial anchor subscription update
information received within the HTTP PATCH or PUT request; and
ii) send the HTTP "204 No Content" response to the SAn client; or
2) not found, return the
...