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

5G; 5G System; Ambient IoT Function (AIOTF) Services; Stage 3 (3GPP TS 29.569 version 19.2.0 Release 19)

RTS/TSGC-0329569vj20

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 3 - Interworking with external networks (formely CN3)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System;
Ambient IoT Function (AIOTF) Services;
Stage 3
(3GPP TS 29.569 version 19.2.0 Release 19)

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

Reference
RTS/TSGC-0329569vj20
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.569 version 19.2.0 Release 19 2 ETSI TS 129 569 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.569 version 19.2.0 Release 19 3 ETSI TS 129 569 V19.2.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 7
2 References . 8
3 Definitions, symbols and abbreviations . 9
3.1 Definitions . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Overview . 9
5 Services offered by the AIOTF . 11
5.1 Introduction . 11
5.2 Naiotf_AIoT Service . 11
5.2.1 Service Description . 11
5.2.2 Service Operations . 11
5.2.2.1 Introduction . 11
5.2.2.2 Naiotf_AIoT_Inventory . 11
5.2.2.2.1 General . 11
5.2.2.2.2 AIoT Inventory Request . 12
5.2.2.3 Naiotf_AIoT_Command . 12
5.2.2.3.1 General . 12
5.2.2.3.2 AIoT Command Request . 13
5.2.2.4 Naiotf_AIoT_Notify . 14
5.2.2.4.1 General . 14
5.2.2.4.2 AIoT Operations Notification . 14
6 API Definitions . 15
6.1 Naiotf_AIoT Service API . 15
6.1.1 Introduction. 15
6.1.2 Usage of HTTP . 15
6.1.2.1 General . 15
6.1.2.2 HTTP standard headers . 15
6.1.2.2.1 General . 15
6.1.2.2.2 Content type . 15
6.1.2.3 HTTP custom headers . 15
6.1.3 Resources . 16
6.1.4 Custom Operations without associated resources . 16
6.1.4.1 Overview . 16
6.1.4.2 Operation: InventoryRequest . 16
6.1.4.2.1 Description . 16
6.1.4.2.2 Operation Definition . 16
6.1.4.3 Operation: CommandRequest . 17
6.1.4.3.1 Description . 17
6.1.4.3.2 Operation Definition . 18
6.1.5 Notifications . 19
6.1.5.1 General . 19
6.1.5.2 AIoT Operations Notification . 19
6.1.5.2.1 Description . 19
6.1.5.2.2 Target URI . 19
6.1.5.2.3 Standard Methods . 19
6.1.6 Data Model . 20
6.1.6.1 General . 20
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 4 ETSI TS 129 569 V19.2.0 (2026-03)
6.1.6.2 Structured data types . 21
6.1.6.2.1 Introduction . 21
6.1.6.2.2 Type: InventoryReq . 22
6.1.6.2.3 Type: InventoryResp . 22
6.1.6.2.4 Type: CommandReq . 23
6.1.6.2.5 Type: CommandResp . 25
6.1.6.2.6 Type: AIoTNotif . 26
6.1.6.2.7 Type: AIoTDevices . 26
6.1.6.2.8 Type: DevicesRepInfo . 27
6.1.6.2.9 Type: AIoTDeviceLoc . 27
6.1.6.3 Simple data types and enumerations . 28
6.1.6.3.1 Introduction . 28
6.1.6.3.2 Simple data types . 28
6.1.6.3.3 Enumeration: AIoTDevFailCause . 28
6.1.6.3.4 Enumeration: FailureCause . 28
6.1.6.4 Data types describing alternative data types or combinations of data types . 29
6.1.6.5 Binary data . 29
6.1.6.5.1 Binary Data Types . 29
6.1.7 Error Handling . 29
6.1.7.1 General . 29
6.1.7.2 Protocol Errors . 29
6.1.7.3 Application Errors . 29
6.1.8 Feature negotiation . 30
6.1.9 Security . 30
6.1.10 HTTP redirection . 31
Annex A (normative): OpenAPI specification . 32
A.1 General . 32
A.2 Naiotf_AIoT API . 33
Annex B (informative): Withdrawn API versions . 40
B.1 General . 40
B.2 Naiotf_AIoT API . 40
Annex C (normative): ABNF grammar for 3GPP SBI HTTP custom headers . 41
C.1 General . 41
Annex D (informative): Change history . 42
History . 43

ETSI
3GPP TS 29.569 version 19.2.0 Release 19 5 ETSI TS 129 569 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.569 version 19.2.0 Release 19 6 ETSI TS 129 569 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.569 version 19.2.0 Release 19 7 ETSI TS 129 569 V19.2.0 (2026-03)
1 Scope
The present document specifies the stage 3 protocol and data model for the Naiotf Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AIOTF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.369 [14], 3GPP TS 23.501 [2] and
3GPP TS 23.502 [3].
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].
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 8 ETSI TS 129 569 V19.2.0 (2026-03)
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] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[16] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[17] 3GPP TS 29.122: "T8 reference point for Northbound Application Programming Interfaces
(APIs)".
[18] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 9 ETSI TS 129 569 V19.2.0 (2026-03)
[19] 3GPP TS 24.369: "Ambient IoT Non-Access-Stratum (AIoT NAS) protocol for 5G System (5GS);
Stage 3".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions 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].
For the purpose of the present document, the terms and definitions given in clause 3 of 3GPP TS 23.369 [14] also apply,
including the ones referencing other specifications.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], 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] or 3GPP TS 23.369 [14].
4 Overview
In the frame of AIoT Services, the AIoT Function (AIOTF) provides services to NF service consumers (e.g., NEF, AF)
via the Naiotf service-based interface. The AIOTF supports for this purpose the functionalities defined in
3GPP TS 23.369 [14] to enable the management of AIoT services and their exposure to AIoT applications.
Figures°4-1 and 4.2 depict the AIoT related reference architecture of the AIOTF respectively in SBI representation and
reference point representation.

AIOTF
Naiotf
NEF AF
Figure 4-1: Reference model for the AIOTF Services – SBI representation
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 10 ETSI TS 129 569 V19.2.0 (2026-03)

AF
AIOTF
NEF
AIOT-4
Figure 4-2: Reference Model for the AIOTF Services – Reference point representation
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 11 ETSI TS 129 569 V19.2.0 (2026-03)
5 Services offered by the AIOTF
5.1 Introduction
The AIOTF provides the following services:
- Naiotf_AIoT
Table 5.1-1 summarizes the corresponding APIs defined in this specification.
Table 5.1-1: API Descriptions
OpenAPI Specification
Service Name Clause Description apiName Annex
File
Naiotf_AIoT 6.1 AIoT Service TS29569_Naiotf_AIoT.yaml naiotf-aiot A.2

5.2 Naiotf_AIoT Service
5.2.1 Service Description
The Naiotf_AIoT service exposed by the AIOTF enables an NF service consumer to:
- request to perform AIoT Inventory operations;
- request to perform AIoT Command operations; and
- receive AIoT operations related event(s) reporting.
5.2.2 Service Operations
5.2.2.1 Introduction
The service operations defined for the Naiotf_AIoT service are shown in table 5.2.2.1-1.
Table 5.2.2.1-1: Naiotf_AIoT Service Operations
Service Operation Name Description Initiated by
This service operation enables the NF service consumer to
Naiotf_AIoT_Inventory e.g., NEF, AF
request to perform an AIoT Inventory operation.
This service operation enables the NF service consumer to
Naiotf_AIoT_Command e.g., NEF, AF
request to perform an AIoT Command operation.
This service operation enables the NF service consumer to
Naiotf_AIoT_Notify AIOTF
receive AIoT operations related event(s) reporting.

5.2.2.2 Naiotf_AIoT_Inventory
5.2.2.2.1 General
This service operation is used by an NF service consumer to request to perform an AIoT Inventory operation at the
AIOTF.
The following procedures are supported by the "Naiotf_AIoT_Inventory" service operation:
- AIoT Inventory Request.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 12 ETSI TS 129 569 V19.2.0 (2026-03)
5.2.2.2.2 AIoT Inventory Request
Figure 5.2.2.2.2-1 depicts a scenario where an NF service consumer requests to perform an AIoT Inventory operation to
the AIOTF (see also clause 6.2.2 of 3GPP TS 23.369 [14]).
NF Service Consumer AIOTF
POST …/request-inv (InventoryReq)
2a. 200 OK (InventoryResp)
2b. 4xx/5xx
Figure 5.2.2.2.2-1: AIoT Inventory Request
1. In order to request to perform an AIoT Inventory operation, the NF service consumer shall send an HTTP POST
request message to the AIOTF targeting the URI of the corresponding custom operation (i.e.,
"InventoryRequest"), with the request body containing the InventoryReq data structure.
2a. Upon reception of the Inventory request from the NF service consumer:
- the AIOTF may perform the AF authorization for AIoT Services procedure as defined in
clauses 5.6 and 6.2.2 of 3GPP TS 23.369 [14]; and
- if the AF authorization for AIoT Services procedure is successful and upon successful processing of the
request, the AIOTF shall respond to the NF service consumer with an HTTP "200 OK" status code to
indicate that the AIoT Inventory request is successfully received and processed, with the response body
containing AIoT Inventory related information within the InventoryResp data structure.
2b. On failure, the AIOTF shall take proper error handling actions, as specified in clause 6.1.7, and respond to the
NF service consumer with an appropriate error status code. In particular:
- if AF authorization for AIoT Services procedure is not successful, the AIOTF shall reject the request with an
HTTP "403 Forbidden" status code with the response body including the ProblemDetails data structure
containing the "cause" attribute set to the "AF_NOT_AUTHORIZED" application error;
- if the target(s) of the AIoT Inventory request (e.g., target AIoT Device(s), filtering information) is/are not
supported and/or not allowed, the AIOTF shall reject the request with an HTTP "403 Forbidden" status code
with the response body including the ProblemDetails data structure containing the "cause" attribute set to the
"AIOT_TARGETS_ERROR" application error;
- if the provided time interval for results aggregation is invalid (e.g., the provided time interval is shorter than a
locally configured minimum interval at the AIOTF as defined in clause 5.9 of 3GPP TS 23.369 [14]), the
AIOTF shall reject the request with an HTTP "403 Forbidden" status code with the response body including
the ProblemDetails data structure containing the "cause" attribute set to the
"INVALID_AGGR_TIME_INVERTAVAL" application error; and
- if the AIOTF fails to process the AIoT Inventory request (e.g., failure to select the NG-RAN(s) or RAN
Reader(s) to handle the request), the AIOTF shall reject the request with an HTTP "500 Internal Server
Error" status code with the response body including the ProblemDetails data structure containing the "cause"
attribute set to the "UNSPECIFIED_FAILURE" application error.
5.2.2.3 Naiotf_AIoT_Command
5.2.2.3.1 General
This service operation is used by an NF service consumer to request to perform an AIoT Command operation at the
AIOTF.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 13 ETSI TS 129 569 V19.2.0 (2026-03)
The following procedures are supported by the "Naiotf_AIoT_Command" service operation:
- AIoT Command Request.
5.2.2.3.2 AIoT Command Request
Figure 5.2.2.3.2-1 depicts a scenario where an NF service consumer requests to perform an AIoT Command operation
to the AIOTF (see also clause 6.2.3 of 3GPP TS 23.369 [14]).
NF Service Consumer AIOTF
POST …/request-cmd (CommandReq)
2a. 200 OK (CommandResp)
2b. 4xx/5xx
Figure 5.2.2.3.2-1: AIoT Command Request
1. In order to request to perform an AIoT Command operation, the NF service consumer shall send an HTTP POST
request message to the AIOTF targeting the URI of the corresponding custom operation (i.e.,
"CommandRequest"), with the request body containing the CommandReq data structure.
2a. Upon reception of the Command request from the NF service consumer:
- the AIOTF may perform the AF authorization for AIoT Services procedure as defined in
clauses 5.6 and 6.2.3 of 3GPP TS 23.369 [14]; and
- if the AF authorization for AIoT Services procedure is successful and upon successful processing of the
request, the AIOTF shall respond to the NF service consumer with an HTTP "200 OK" status code to
indicate that the AIoT Command request is successfully received and processed, with the response body
containing AIoT Command related information within the CommandResp data structure.
2b. On failure, the AIOTF shall take proper error handling actions, as specified in clause 6.1.7, and respond to the
NF service consumer with an appropriate error status code. In particular:
- if AF authorization for AIoT Services procedure is not successful, the AIOTF shall reject the request with an
HTTP "403 Forbidden" status code with the response body including the ProblemDetails data structure
containing the "cause" attribute set to the "AF_NOT_AUTHORIZED" application error;
- if the target(s) of the AIoT Command request (e.g., target AIoT Device(s), filtering information) is/are not
supported and/or not allowed, the AIOTF shall reject the request with an HTTP "403 Forbidden" status code
with the response body including the ProblemDetails data structure containing the "cause" attribute set to the
"AIOT_TARGETS_ERROR" application error;
- if the provided length of application data is too long (e.g., above the allowed maximum value), the AIOTF
shall reject the request with an HTTP "403 Forbidden" status code with the response body including the
ProblemDetails data structure containing the "cause" attribute set to the "APP_DATA_TOO_LONG"
application error; and
- if the AIOTF fails to process the AIoT Command request (e.g., failure to select the NG-RAN(s) or RAN
Reader(s) to handle the request), the AIOTF shall reject the request with an HTTP "500 Internal Server
Error" status code with the response body including the ProblemDetails data structure containing the "cause"
attribute set to the "UNSPECIFIED_FAILURE" application error.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 14 ETSI TS 129 569 V19.2.0 (2026-03)
5.2.2.4 Naiotf_AIoT_Notify
5.2.2.4.1 General
This service operation is used by the AIOTF to notify a previously subscribed service consumer on:
- AIoT operations related event(s).
The following procedures are supported by the "Naiotf_AIoT_Notify" service operation:
- AIoT Operations Notification.
5.2.2.4.2 AIoT Operations Notification
Figure 5.2.2.4.2-1 depicts a scenario where the AIOTF sends a request to notify a previously subscribed NF service
consumer on AIoT operations related event(s) (see also clauses 6.2.2 and 6.2.3 of 3GPP TS 23.369 [14]).
NF Service Consumer AIOTF
POST {notifUri} (AIoTNotif)
2a. 204 No Content
2b. 4xx/5xx
Figure 5.2.2.4.2-1: AIoT Operations Notification
1. In order to notify a previously subscribed service consumer on AIoT operations related event(s), the AIOTF shall
send an HTTP POST request message to the NF service consumer with the request URI set to "{notifUri}",
where the "notifUri" variable is set to the value received from the NF service consumer as part of the request
used to trigger the corresponding AIoT service operation (e.g., Inventory, Command), as defined in
clause 5.2.2.2 or clause 5.2.2.3, and the request body including the AIoTNotif data structure.
2a. Upon success, the NF service consumer shall respond to the AIOTF with an HTTP "204 No Content" status
code.
2b. On failure, the NF service consumer shall take proper error handling actions, as specified in clause 6.1.7, and
respond to the AIOTF with an appropriate error status code.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 15 ETSI TS 129 569 V19.2.0 (2026-03)
6 API Definitions
6.1 Naiotf_AIoT Service API
6.1.1 Introduction
The Naiotf_AIoT shall use the Naiotf_AIoT API.
The API URI of the Naiotf_AIoT API shall be:
{apiRoot}//
The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the
Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}///
with the following components:
- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
- The shall be "naiotf-aiot".
- The shall be "v1".
- The shall be set as described in clauses 6.1.3 and 6.1.4.
6.1.2 Usage of HTTP
6.1.2.1 General
HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
The OpenAPI [6] specification of HTTP messages and content bodies for the Naiotf_AIoT API is contained in
Annex A.
6.1.2.2 HTTP standard headers
6.1.2.2.1 General
See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
6.1.2.2.2 Content type
JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as
specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type
"application/json".
"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and
shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13].
6.1.2.3 HTTP custom headers
The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and
the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported.
In this Release of the specification, no specific HTTP custom headers are defined for the Naiotf_AIoT API.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 16 ETSI TS 129 569 V19.2.0 (2026-03)
6.1.3 Resources
There are no resources defined for this API in this release of the specification.
6.1.4 Custom Operations without associated resources
6.1.4.1 Overview
The URI structure for Custom Operations without associated resources is shown in Figure 6.1.4.1-1.

{apiRoot}/naiotf-aiot/
/request-inv
/request-cmd
Figure 6.1.4.1-1: Custom operation URI structure of the Naiotf_AIoT API
Table 6.1.4.1-1 provides an overview of the custom operations and applicable HTTP methods defined for the
Naiotf_AIoT API.
Table 6.1.4.1-1: Custom operations without associated resources
Mapped
Custom operation name Custom operation URI HTTP Description
method
Enables to request to perform an AIoT
InventoryRequest /request-inv POST
Inventory operation.
Enables to request to perform an AIoT
CommandRequest /request-cmd POST
command operation.
The custom operations shall support the URI variables defined in table 6.1.4.1-2.
Table 6.1.4.1-2: URI variables for this custom operation
Name Data type Definition
apiRoot string See clause 6.1.1.

6.1.4.2 Operation: InventoryRequest
6.1.4.2.1 Description
The custom operation enables to request to perform an AIoT Inventory operation at the AIOTF.
6.1.4.2.2 Operation Definition
This operation shall support the response data structures and response codes specified in tables 6.1.4.2.2-1 and
6.1.4.2.2-2.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 17 ETSI TS 129 569 V19.2.0 (2026-03)
Table 6.1.4.2.2-1: Data structures supported by the POST Request Body on this resource
Data type P Cardinality Description
InventoryReq M 1 Contains the parameters to request to perform an AIoT Inventory operation.

Table 6.1.4.2.2-2: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response Description
codes
Successful case. The AIoT Inventory request is successfully
InventoryResp M 1 200 OK received and processed, and AIoT Inventory related
information is returned in the response body.
Temporary redirection.
307 Temporary
RedirectResponse O 0.1
Redirect
(NOTE 2)
Permanent redirection.
308 Permanent
RedirectResponse O 0.1
Redirect
(NOTE 2)
ProblemDetails O 0.1 403 Forbidden (NOTE 3)
500 Internal
ProblemDetails O 0.1 (NOTE 3)
Server Error
NOTE 1: The mandatory HTTP error status codes for the HTTP POST method listed in Table 5.2.7.1-1 of
3GPP TS 29.500 [4] shall also apply.
NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of
3GPP TS 29.500 [4]).
NOTE 3: Failure cases are described in clause 6.1.7.

Table 6.1.4.2.2-3: Headers supported by the 307 Response Code on this custom operation
Name Data type P Cardinality Description
Contains an alternative target URI located in an alternative
AIOTF (service) instance towards which the request is
redirected.
Location string M 1
For the case where the request is redirected to the same
target via a different SCP, refer to clause 6.10.9.1 of
3GPP TS 29.500 [4].
Contains the identifier of the target AIOTF (service) instance
3gpp-Sbi-Target-Nf-Id string O 0.1
towards which the request is redirected.

Table 6.1.4.2.2-4: Headers supported by the 308 Response Code on this custom operation
Name Data type P Cardinality Description
Contains an alternative target URI located in an alternative
AIOTF (service) instance towards which the request is
redirected.
Location string M 1
For the case where the request is redirected to the same
target via a different SCP, refer to clause 6.10.9.1 of
3GPP TS 29.500 [4].
Contains the identifier of the target AIOTF (service) instance
3gpp-Sbi-Target-Nf-Id string O 0.1
towards which the request is redirected.

6.1.4.3 Operation: CommandRequest
6.1.4.3.1 Description
The custom operation enables to request to perform an AIoT command operation.
ETSI
3GPP TS 29.569 version 19.2.0 Release 19 18 ETSI TS 129 569 V19.2.0 (2026-03)
6.1.4.3.2 Operation Definition
This operation shall support the response data structures and response codes specified in tables 6.1.4.3.2-1 and
6.1.4.3.2-2.
Table 6.1.4.3.2-1: Data structures supported by the POST Request Body on this resource
Data type P Cardinality Description
CommandReq M 1 Contains the parameters to request to perform an AIoT command operation.

Table 6.1.4.3.2-2: Data structures supported by the POST Response
...