ETSI TS 129 369 V19.2.0 (2026-03)

5G; 5G System; Ambient IoT Data Management Services; Stage 3 (3GPP TS 29.369 version 19.2.0 Release 19)

RTS/TSGC-0429369vj20

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System; Ambient IoT Data Management Services;
Stage 3
(3GPP TS 29.369 version 19.2.0 Release 19)


3GPP TS 29.369 version 19.2.0 Release 19 1 ETSI TS 129 369 V19.2.0 (2026-03)

Reference
RTS/TSGC-0429369vj20
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 29.369 version 19.2.0 Release 19 2 ETSI TS 129 369 V19.2.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 29.369 version 19.2.0 Release 19 3 ETSI TS 129 369 V19.2.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 and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Overview . 9
5 Services offered by the ADM . 9
5.1 Introduction . 9
5.2 Nadm_DM Service . 10
5.2.1 Service Description . 10
5.2.2 Service Operations . 10
5.2.2.1 Introduction . 10
5.2.2.2 Query . 10
5.2.2.2.1 General . 10
5.2.2.2.2 AIoT Device Profile Data Retrieval . 10
5.2.2.2.3 AF Authorization Data Retrieval . 11
5.2.2.2.4 Bundled AIoT Device Profile Data Retrieval . 11
5.2.2.3 Update . 12
5.2.2.3.2 AIoT Device Profile Data Update . 12
5.2.2.3.3 Bundled AIoT Device Profile Data Update . 12
5.3 Nadm_Sec Service . 13
5.3.1 Service Description . 13
5.3.2 Service Operations . 13
5.3.2.1 Introduction . 13
5.3.2.2 RAND_Get. 13
5.3.2.2.1 General . 13
5.3.2.2.2 RAND Retrieval . 14
5.3.2.3 Authentication_Get . 14
5.3.2.3.1 General . 14
5.3.2.3.2 Authentication Data Retrieval . 14
5.3.2.4 SessionKey_Get . 15
5.3.2.4.1 General . 15
5.3.2.5 TID_Get . 15
5.3.2.5.1 General . 15
5.3.2.5.2 TID Retrieval . 15
6 API Definitions . 16
6.1 Nadm_DM Service API . 16
6.1.1 Introduction. 16
6.1.2 Usage of HTTP . 17
6.1.2.1 General . 17
6.1.2.2 HTTP standard headers . 17
6.1.2.2.1 General . 17
6.1.2.2.2 Content type . 17
6.1.2.3 HTTP custom headers . 17
6.1.3 Resources . 17
6.1.3.1 Overview . 17
6.1.3.2 Resource: AiotDeviceProfileData . 18
6.1.3.2.1 Description . 18
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 4 ETSI TS 129 369 V19.2.0 (2026-03)
6.1.3.2.2 Resource Definition . 18
6.1.3.2.3 Resource Standard Methods . 19
6.1.3.3 Resource: AfAuthorizationData . 21
6.1.3.3.1 Description . 21
6.1.3.3.2 Resource Definition . 21
6.1.3.3.3 Resource Standard Methods . 22
6.1.3.4 Resource: BundledAiotDeviceProfileData . 23
6.1.3.4.1 Description . 23
6.1.3.4.2 Resource Definition . 23
6.1.3.4.3 Resource Standard Methods . 23
6.1.4 Custom Operations without associated resources . 26
6.1.5 Notifications . 26
6.1.6 Data Model . 26
6.1.6.1 General . 26
6.1.6.2 Structured data types . 27
6.1.6.2.1 Introduction . 27
6.1.6.2.2 Type: AiotDevProfileData . 28
6.1.6.2.3 Type: LastKnownAiotfInfo . 28
6.1.6.2.4 Type: IndividualAfAuthorizationData . 29
6.1.6.2.5 Type: AllowedTargetAiotDevice . 29
6.1.6.2.6 Type: AfAuthorizationData . 29
6.1.6.2.7 Type: TidHandlingInformation . 30
6.1.6.3 Simple data types and enumerations . 30
6.1.6.3.1 Introduction . 30
6.1.6.3.2 Simple data types . 30
6.1.6.3.3 Enumeration: AllowedServiceOperation . 30
6.1.6.3.4 Enumeration: TidType . 31
6.1.7 Error Handling . 31
6.1.7.1 General . 31
6.1.7.2 Protocol Errors . 31
6.1.7.3 Application Errors . 31
6.1.8 Feature negotiation . 31
6.1.9 Security . 31
6.1.10 HTTP redirection . 32
6.2 Nadm_Sec Service API . 32
6.2.1 Introduction. 32
6.2.2 Usage of HTTP . 32
6.2.2.1 General . 32
6.2.2.2 HTTP standard headers . 33
6.2.2.2.1 General . 33
6.2.2.2.2 Content type . 33
6.2.2.3 HTTP custom headers . 33
6.2.3 Resources . 33
6.2.3.1 Overview . 33
6.2.4 Custom Operations without associated resources . 33
6.2.4.1 Overview . 33
6.2.4.2 Operation: getRand . 34
6.2.4.2.1 Description . 34
6.2.4.2.2 Operation Definition . 34
6.2.4.3 Operation: getAuthentication . 34
6.2.4.3.1 Description . 34
6.2.4.3.2 Operation Definition . 34
6.2.4.4 Operation: getSessionKey . 35
6.2.4.4.1 Description . 35
6.2.4.4.2 Operation Definition . 35
6.2.4.5 Operation: getTid . 35
6.2.4.5.1 Description . 35
6.2.4.5.2 Operation Definition . 35
6.2.5 Notifications . 36
6.2.6 Data Model . 36
6.2.6.1 General . 36
6.2.6.2 Structured data types . 36
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 5 ETSI TS 129 369 V19.2.0 (2026-03)
6.2.6.2.1 Introduction . 36
6.2.6.2.2 Type: GetAuthenticationRequest . 37
6.2.6.2.3 Type: AuthData . 37
6.2.6.2.4 Type: AuthDataSet . 37
6.2.6.2.5 Type: GetAuthenticationResponse . 37
6.2.6.2.6 Type: GetSessionKeyRequest . 37
6.2.6.2.7 Type: GetSessionKeyResponse . 38
6.2.6.2.8 Type: GetTidRequest . 38
6.2.6.2.9 Type: GetTidResponse . 38
6.2.6.2.10 Type: GetRandResponse . 38
6.2.6.3 Simple data types and enumerations . 38
6.2.6.3.1 Introduction . 38
6.2.6.3.2 Simple data types . 38
6.2.7 Error Handling . 39
6.2.7.1 General . 39
6.2.7.2 Protocol Errors . 39
6.2.7.3 Application Errors . 39
6.2.8 Feature negotiation . 39
6.2.9 Security . 39
6.2.10 HTTP redirection . 40
Annex A (normative): OpenAPI specification . 41
A.1 General . 41
A.2 Nadm_DM API . 41
A.3 Nadm_Sec API . 47
Annex B (informative): Change history . 53
History . 54

ETSI
3GPP TS 29.369 version 19.2.0 Release 19 6 ETSI TS 129 369 V19.2.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 29.369 version 19.2.0 Release 19 7 ETSI TS 129 369 V19.2.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 29.369 version 19.2.0 Release 19 8 ETSI TS 129 369 V19.2.0 (2026-03)
1 Scope
The present document specifies the stage 3 protocol and data model for the Nadm Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the ADM.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and
3GPP TS 23.369[14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
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.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[7] 3GPP TR 21.900: "Technical Specification Group working methods".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11] IETF RFC 9113: "HTTP/2".
[12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13] IETF RFC 9457: "Problem Details for HTTP APIs".
[14] 3GPP TS 23.369: "Architecture support for Ambient power-enabled Internet of Things; Stage 2".
[15] IETF RFC 9110: "HTTP Semantics".
[16] IETF RFC 9111: "HTTP Caching".
[17] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
[18] 3GPP TS 33.369: " Security aspects of Ambient Internet of Things (AIoT) services for isolated
private networks".
[19] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 9 ETSI TS 129 369 V19.2.0 (2026-03)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and
3GPP TS 23.369 [14] 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].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and 3GPP TS 23.369 [14]
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].
4 Overview
Within the 5GC, the ADM offers services to the AIOTF, NEF via the Nadm service based interface (see
3GPP TS 23.369 [14]).
Figure 4-1 provides the reference model (in service based interface representation and in reference point
representation), with focus on the ADM:
AIOTF AIOT6 ADM
AIOT8
NEF
Figure 4-1: Reference model – ADM
The functionalities supported by the ADM are listed in clause 4.5.9 of 3GPP TS 23.369 [14].
5 Services offered by the ADM
5.1 Introduction
The ADM offers the following services via the Nadm interface:
- Nadm_DM Service
- Nadm_Sec
Table 5.1-1 summarizes the corresponding APIs defined for this specification.
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 10 ETSI TS 129 369 V19.2.0 (2026-03)
Table 5.1-1: API Descriptions
OpenAPI Specification
Service Name Clause Description apiName Annex
File
ADM Data
Nadm_DM 6.1 TS29369_Nadm_DM.yaml nadm-dm A.2
Management
Nadm_Sec 6.2 ADM Security Service TS29369_Nadm_Sec.yaml nadm-sec A.3

5.2 Nadm_DM Service
5.2.1 Service Description
The Nadm_DM service enables an NF to request AIoT device profile data or the AF authorization data or update the
AIoT device profile data in the ADM.
5.2.2 Service Operations
5.2.2.1 Introduction
The service operations defined for the Nadm_DM service are as follows:
- Query: It enables a consumer NF to request AIoT device profile data or the AF authorization data from the
ADM.
- Update: It enables a consumer NF to update the AIoT device profile data in the ADM.
5.2.2.2 Query
5.2.2.2.1 General
The following procedures using the Query service operation are supported:
- AIoT Device Profile Data Retrieval
- AF Authorization Data Retrieval
- Bundled AIoT Device Profile Data Retrieval
5.2.2.2.2 AIoT Device Profile Data Retrieval
Figure 5.2.2.2.2-1 shows a scenario where the NF service consumer (e.g. AIOTF or NEF) sends a request to the ADM
to receive the AIoT Device Profile Data of a given AIoT device (see 3GPP TS 23.369 [14]).
NF service
ADM
consumer
1. GET …/aiot-device-profile-data/{aiotDevPermId}
2a. 200 OK (AiotDevProfileData)
2b. 404 Not Found
Figure 5.2.2.2.2-1: Requesting AIoT Device Profile Data
1. The NF service consumer (e.g. AIOTF or NEF) sends a GET request to the resource …/aiot-device-profile-
data/{aiotDevPermId}, to get the AIoT Device Profile Data of a given AIoT device.
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 11 ETSI TS 129 369 V19.2.0 (2026-03)
2a. On success, the ADM responds with "200 OK" with the AIoT Device Profile Data.
2b. If there is no valid AIoT Device Profile Data for the AIoT device permanent identifier, HTTP status code "404
Not Found" shall be returned including additional error information in the response body (in the
"ProblemDetails" element).
On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error
information should be returned in the GET response body.
5.2.2.2.3 AF Authorization Data Retrieval
Figure 5.2.2.2.3-1 shows a scenario where the NF service consumer (e.g. AIOTF) sends a request to the ADM to
receive the AF Authorization Data (see 3GPP TS 23.369 [14]).
NF service
ADM
consumer
1. GET …/af-authorization-data
2a. 200 OK (AfAuthorizationData)
2b. 404 Not Found
Figure 5.2.2.2.3-1: Requesting AF Authorization Data
1. The NF service consumer (e.g. AIOTF) sends a GET request to the resource of the AF authorization data (…/af-
authorization-data), to get the Authorization Data of the AFs. The request may contain the target AF ID if the
authorization data for a specific AF is to be retrieved.
2a. On success, the ADM responds with "200 OK" with the Authorization Data of the target AF(s).
2b. If there is no valid AF Authorization Data available, HTTP status code "404 Not Found" shall be returned
including additional error information in the response body (in the "ProblemDetails" element).
On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error
information should be returned in the GET response body.
5.2.2.2.4 Bundled AIoT Device Profile Data Retrieval
Figure 5.2.2.2.4-1 shows a scenario where the NF service consumer (e.g. AIOTF or NEF) sends a request to the ADM
to receive the AIoT Device Profile Data for bundled AIoT Devices (see 3GPP TS 23.369 [14]).
NF service
ADM
consumer
1. GET …/aiot-device-profile-data?
2a. 200 OK (AiotDevProfileDataList)
2b. 404 Not Found
Figure 5.2.2.2.4-1: Requesting AIoT Device Profile Data for bundled AIoT Devices
1. The NF service consumer (e.g. AIOTF or NEF) sends a GET request to the resource URI "aiotDevPermId"
collection resource. The optional input filter criteria (a list of aiotDevPermId) for the retrieval request may be
included in the query parameters. All the aiotDevPermId included in the list are aggregated by the NF service
consumer (e.g. AIOTF) based on the the list of device IDs served by ADM, which can be retrieved from NRF
and included in the deviceIdList within AdmInfo.
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 12 ETSI TS 129 369 V19.2.0 (2026-03)
The NF service consumer (e.g. AIOTF) should not include the aiotDevPermId that are not served by the ADM
and after aggregation, the NF service consumer (e.g. AIOTF) shall bundle appropriate number of AIoT devices
based on deployment to avoid bundling huge number of requested devices.
2a. On success, the ADM responds with "200 OK". The response body shall contain the URI (conforming to the
resource URI structure as described in clause 5.2.2.2.2) of each aiotDevPermId in the ADM that satisfy the
retrieval filter criteria (a list of aiotDevPermId).
2b. If there is no valid AIoT Device Profile Data for all the AIoT device permanent identifiers listed in the input
filter criteria, HTTP status code "404 Not Found" shall be returned including additional error information in the
response body (in the "ProblemDetails" element).
On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error
information should be returned in the GET response body.
5.2.2.3 Update
5.2.2.3.1 General
The following procedures using the Update service operation are supported:
- AIoT Device Profile Data Update
- Bundled AIoT Device Profile Data Update
5.2.2.3.2 AIoT Device Profile Data Update
Figure 5.2.2.3.2-1 shows a scenario where the NF service consumer (e.g., AIOTF) sends a request to the ADM to
modify the AIoT Device Profile Data of a given AIoT device (see 3GPP TS 23.369 [14]). The request contains the
AIoT device permanent identifier and the modification instructions.
NF service
ADM
consumer
1. PATCH…/aiot-device-profile-data/{aiotDevPermId}
(AiotDevProfileData)
2a. 204 No Content
2b. 404 Not Found
Figure 5.2.2.3.2-1: Updating AIoT Device Profile Data
1. The NF service consumer (e.g. AIOTF) sends a PATCH request to the resource …/aiot-device-profile-
data/{aiotDevPermId}, to update the AIoT Device Profile Data of a given AIoT device.
2a. On success, the ADM responds with "204 No Content".
2b. If there is no valid AIoT Device Profile Data for the AIoT device permanent identifier, HTTP status code "404
Not Found" shall be returned including additional error information in the response body (in the
"ProblemDetails" element).
On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error
information should be returned in the PATCH response body.
5.2.2.3.3 Bundled AIoT Device Profile Data Update
Figure 5.2.2.3.3-1 shows a scenario where the NF service consumer (e.g., AIOTF) sends a request to the ADM to
modify the AIoT Device Profile Data for a bundled AIoT Devices (see 3GPP TS 23.369 [14]). The request contains the
the modification instructions.
ETSI
3GPP TS 29.369 version 19.2.0 Release 19 13 ETSI TS 129 369 V19.2.0 (2026-03)
NF service
ADM
consumer
1. PATCH…/aiot-device-profile-data(array(PatchItem))
2a. 204 No Content
2b. 404 Not Found
Figure 5.2.2.3.3-1: Updating AIoT Device Profile Data for bundled AIoT Devices
1. The NF service consumer (e.g. AIOTF) sends a PATCH request to the resource URI "aiotDevPermId" collection
resource. The content of the PATCH request shall contain the list of operations (add/delete/replace) to be applied
to the AIoT Device Profile Data for bundled AIoT Devices, these operations may be directed to bundled AIoT
Devices, where each of them directed to individual AIoT Device Profile Data parameters for a given AIoT
device permanent identifier or to all parameters offered by a given AIoT Device permanent identifier.
2a. On success, the ADM responds with "204 No Content".
2b. If there is no valid AIoT Device Profile Data for the AIoT device permanent identifier, HTTP status code "404
Not Found" shall be returned including additional error information in the response body (in the
"ProblemDetails" element).
On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error
infor
...