ETSI TS 123 369 V19.3.0 (2026-03)

5G; Architecture support for Ambient power-enabled Internet of Things; Stage 2 (3GPP TS 23.369 version 19.3.0 Release 19)

RTS/TSGS-0223369vj30

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 2 - Architecture
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 13-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
Architecture support
for Ambient power-enabled Internet of Things;
Stage 2
(3GPP TS 23.369 version 19.3.0 Release 19)

3GPP TS 23.369 version 19.3.0 Release 19 1 ETSI TS 123 369 V19.3.0 (2026-03)

Reference
RTS/TSGS-0223369vj30
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 23.369 version 19.3.0 Release 19 2 ETSI TS 123 369 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 23.369 version 19.3.0 Release 19 3 ETSI TS 123 369 V19.3.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 7
2 References . 7
3 Definitions of terms and abbreviations. 7
3.1 Terms . 7
3.2 Abbreviations . 8
4 Architecture model and concepts . 8
4.1 General concept . 8
4.2 Architecture . 8
4.2.1 General . 8
4.2.2 Architecture for NG-RAN connectivity . 9
4.2.2.1 General . 9
4.2.2.2 Direct Connectivity between AIOTF and NG-RAN . 10
4.2.2.3 Indirect Connectivity between AIOTF and NG-RAN via an AMF . 11
4.3 Reference points . 12
4.4 Service-based interfaces . 12
4.5 Functional Entities . 13
4.5.1 AIoT Device . 13
4.5.2 NG-RAN . 13
4.5.3 AIOTF . 13
4.5.4 NEF . 14
4.5.5 AF . 14
4.5.6 NRF . 14
4.5.7 AMF. 14
4.5.8 UDR . 14
4.5.9 ADM . 14
4.6 Protocol Stacks . 15
4.6.1 General . 15
4.6.2 Protocol Stack between AIoT Device and AF . 15
4.6.2.1 General . 15
4.6.2.2 Protocol Stack between AF and AIoT Device for NG-RAN Direct Connectivity . 15
4.6.2.3 Protocol Stack between AF and AIoT Device for NG-RAN Indirect Connectivity. 16
5 High level functionality and features . 16
5.1 General . 16
5.2 AIoT Services . 16
5.2.0 General . 16
5.2.1 AIoT Inventory service . 16
5.2.2 AIoT Command service . 16
5.2.2.1 Overview . 16
5.2.2.2 Read and Write Commands. 17
5.2.2.3 Permanent Disable Command . 18
5.3 Discovery and Selection of AIoT node(s) . 18
5.3.1 AIOTF Discovery and Selection . 18
5.3.2 ADM Discovery and Selection . 18
5.3.3 NG-RAN Node and RAN Reader Selection . 19
5.3.4 AMF Discovery and Selection . 20
5.4 Assistance information provided to NG-RAN node . 20
5.5 AIoT Device Profile Management . 20
5.6 AF authorization for the AIoT Services . 21
5.7 Identifiers . 21
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 4 ETSI TS 123 369 V19.3.0 (2026-03)
5.7.1 General . 21
5.7.2 AIoT Device Permanent Identifier . 21
5.7.3 Correlation ID . 23
5.7.4 AIoT Device Temporary Identifier . 23
5.8 Filtering Information . 23
5.9 AIoT Service Operation Result Aggregation . 24
5.10 AIoT Device Location . 24
5.10.1 Overview . 24
5.11 AIoT Device Context in AIOTF . 24
6 AIoT Procedures . 25
6.1 General . 25
6.2 AIoT Service Procedures . 25
6.2.1 General . 25
6.2.2 Inventory Procedure . 25
6.2.3 Command Procedure. 28
6.2.4 Procedures between AIOTF and NG-RAN for Indirect Connectivity . 31
6.2.4.1 Overview . 31
6.2.4.2 Message delivery to NG-RAN . 31
6.2.4.3 Message delivery to AIOTF . 32
6.2.5 AIoT Session Release Procedure . 33
7 Network Functions Services . 34
7.1 General . 34
7.2 AIOTF services . 34
7.2.1 General . 34
7.2.2 Naiotf_AIoT_Inventory service operation . 35
7.2.3 Naiotf_AIoT_Command service operation . 35
7.2.4 Naiotf_AIoT_Notify service operation . 36
7.3 AMF services . 36
7.3.1 General . 36
7.3.2 Namf_AIoT_MessageDelivery service operation . 36
7.3.3 Namf_AIoT_Notify service operation . 37
7.4 NEF services . 37
7.4.1 General . 37
7.4.2 Nnef_AIoT_Inventory service operation . 37
7.4.3 Nnef_AIoT_Command service operation . 38
7.4.4 Nnef_AIoT_Notify service operation . 38
7.5 ADM services . 39
7.5.1 General . 39
7.5.2 Nadm_DM_Query service operation . 39
7.5.3 Nadm_DM_Update service operation . 39
7.5.4 Nadm_DM_Subscribe service operation . 39
7.5.5 Nadm_DM_Unsubscribe service operation . 40
7.5.6 Nadm_DM_Notify service operation. 40
7.6 UDR Services . 40
7.6.1 Nudr_DataManagement (DM) Service . 40
7.6.1.1 General . 40
Annex A (informative): Change history . 41
History . 42

ETSI
3GPP TS 23.369 version 19.3.0 Release 19 5 ETSI TS 123 369 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 23.369 version 19.3.0 Release 19 6 ETSI TS 123 369 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 23.369 version 19.3.0 Release 19 7 ETSI TS 123 369 V19.3.0 (2026-03)
1 Scope
The present document specifies architectural enhancements to the 5G system to support Ambient power-enabled
Internet of Things, complying to the requirements in TS 22.369 [2] applicable to the AIoT Device types, traffic types,
use cases and connectivity topologies defined in TS 38.300 [5].
In this Release, the AIoT system is defined as an isolated private network, such as SNPN, that does not interact with a
public network.
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 22.369: "Service requirements for Ambient power-enabled IoT".
[3] 3GPP TS 23.501: "System Architecture for the 5G System (5GS); Stage 2".
[4] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[5] 3GPP TS 38.300: "NR; Overall description; Stage-2".
[6] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[7] GS1 TDS Release 2.1: "EPC Tag Data Standard".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[9] 3GPP TS 33.369: "Security aspects of Ambient Internet of Things (AIoT) services for isolated
private networks".
[10] 3GPP TS 38.413: "NG Application Protocol (NGAP)".
[11] 3GPP TS 38.391: "Ambient IoT Medium Access Control Protocol specification".
[12] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[13] 3GPP TS 24.369: "Ambient IoT Non-Access-Stratum (AIoT NAS) protocol for 5G System (5GS);
Stage 3".
3 Definitions of terms and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in 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 TR 21.905 [1].
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 8 ETSI TS 123 369 V19.3.0 (2026-03)
AIoT Area: An area in which NG-RAN can perform Ambient IoT operations, see TS 38.300 [5], represented by an
AIoT Area identifier. There can be multiple NG-RAN nodes and multiple RAN Readers in a single AIoT Area. NG-
RAN nodes and RAN Readers can be part of multiple AIoT Areas.
AIoT Device: An Ambient IoT device is an IoT device powered by energy harvesting, with limited energy storage
capability.
External Area Identifier: An identifier for an AIoT service area used by the AF when requesting AIoT Service
Operations.
External Target Area: An area used between the NEF and AF in AIoT service operations, identified by a pre-
configured External Area Identifier or geographic location (e.g. a civic address or GAD shapes, see TS 23.032 [12]).
Target Area: An area in which a service operation request towards an AIOTF is intended to operate, identified by a list
of AIoT Areas.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 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
TR 21.905 [1].
ADM AIoT Data Management
AIoT Ambient IoT
AIOTF Ambient IoT Function
EPC Electronic Product Code
4 Architecture model and concepts
4.1 General concept
AIoT is a service that can be provided by the 5GS system to support Ambient power-enabled IoT devices that are
powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g. using a capacitor)
and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power
source.
The 5GS System architecture for AIoT include the following functions and procedures for:
- AIoT Device identification;
- AIoT Device inventory;
- Providing to, and obtaining from, an AIoT Device application data.
- Disabling AIoT Devices.
4.2 Architecture
4.2.1 General
The 5GS System architecture for AIoT includes core network functions, different AIoT Reader architectures and AIoT
Devices. The different AIoT Reader architectures allow for different deployment options. The following AIoT Reader
architectures are defined:
- NG- RAN (which supports AIoT Reader), which includes either a direct connectivity between NG-RAN and the
AIOTF or an indirect connectivity between NG-RAN and the AIOTF via an AMF.
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 9 ETSI TS 123 369 V19.3.0 (2026-03)
The NG-RAN in this specification refers to the gNB which supports AIoT related functionalities, as specified in
TS 38.300 [5]. The gNB may only support communication with AIoT Devices.
The architecture for Network Exposure Function, using reference point representation, defined in clause 4.2.3 of
TS 23.501 [3] is applicable for AIoT, with a southbound interface from the NEF to AIOTF.
4.2.2 Architecture for NG-RAN connectivity
4.2.2.1 General
5GS system architecture for AIoT supports the following connectivity to access an NG-RAN:
- Direct Connectivity: AIOTF communicates with NG-RAN directly.
- Indirect Connectivity via AMF: NG-RAN and the AIOTF communicate indirectly via an AMF.
Figure 4.2.2.1-1 depicts the complete non-roaming architecture showing the overall 5GS architecture for support of
AIoT, including both the Indirect Connectivity and Direct Connectivity.
NEF NRF AF
Nnef Nnrf Naf
Naiotf Namf Nadm
AIOTF AMF ADM
AIOT1 AIOT2 N2
AIoT
NG-RAN
Device
Figure 4.2.2.1-1: Non-roaming AIoT System Architecture
NOTE 1: For the sake of clarity and to depict the complete reference point architecture, the AMF, AIOT2 and N2
as depicted using dashed lines, as all deployments might not use them.
Figure 4.2.2.1-2 depicts the complete non-roaming AIoT system architecture, using the reference point representation.
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 10 ETSI TS 123 369 V19.3.0 (2026-03)
ADM AIOT8 NEF
AIOT6 AIOT4
AIOTF AIOT3 AMF
AIOT2 N2
AIOT1
AIoT
NG-RAN
Device
Figure 4.2.2.1-2: Non-roaming AIoT System Architecture (RAN Readers) in reference point
representation
NOTE 2: For the sake of clarity of the point-to-point diagrams, the AF and NRF have not been depicted. However,
all depicted Network Functions can interact with the NRF as necessary.
NOTE 3: For clarity, the UDR and its connections with ADM, are not depicted in the point-to-point and service-
based architecture diagrams. For more information on the ADM data storage architectures refer to
clause 4.5.8.
NOTE 4: For the sake of clarity and to depict the complete reference point architecture, the AMF, AIOT3, N2 and
AIOT2 as depicted using dashed lines, as all deployments might not use them.
The architectures in the following clauses showing parts of the overall AIoT architecture specific to each connectivity
option:
- Direct Connectivity: the AIOTF uses AIOT2 to access NG-RAN, and is described in clause 4.2.2.2.
- Indirect Connectivity via AMF: the AIOTF uses an AMF which uses N2 to access NG-RAN, and is described in
clause 4.2.2.3.
NOTE 5: A deployment that only uses, e.g. the Direct Connectivity only does not need to deploy the NFs, reference
points and service-based interfaces associated with the Indirect Connectivity, and vice-versa.
4.2.2.2 Direct Connectivity between AIOTF and NG-RAN
In the Direct Connectivity architecture, the AIOTF uses AIOT2 to communicate directly with NG-RAN.
Figure 4.2.2.2-1 depicts the AIoT architecture, using the service-based interfaces, showing only the parts of the AIoT
architecture for an AIOTF connecting to NG-RAN directly. The remaining parts of the AIoT architecture shown in
Figure 4.2.2.1-1 remain unchanged.
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 11 ETSI TS 123 369 V19.3.0 (2026-03)
Naiotf
AIOTF
AIOT1 AIOT2
AIoT
NG-RAN
Device
Figure 4.2.2.2-1: NG-RAN - AIOTF Direct Connectivity Architecture
Figure 4.2.2.2-2 depicts the AIoT architecture, using the reference point representation, showing only the parts of the
AIoT architecture for an AIOTF access NG-RAN. The remaining parts of the AIoT architecture shown in
Figure 4.2.2.1-2 remain unchanged.
AIOTF
AIOT1 AIOT2
AIoT
NG-RAN
Device
Figure 4.2.2.2-2: NG-RAN - AIOTF Direct Connectivity Architecture in reference point representation
4.2.2.3 Indirect Connectivity between AIOTF and NG-RAN via an AMF
Figure 4.2.2.3-1 depicts the AIoT architecture, using the service-based interfaces showing only the parts of the AIoT
architecture for an AIOTF connects indirectly to NG-RAN via an AMF. The remaining parts of the AIoT Architecture
shown in Figure 4.2.2.1-1 remain unchanged.
Naiotf Namf
AIOTF AMF
N2
AIOT1
AIoT
NG-RAN
Device
Figure 4.2.2.3-1: NG-RAN - AIOTF Indirect Connectivity Architecture
Figure 4.2.2.3-2 depicts the AIoT architecture, using the reference point representation showing only the parts of the
AIoT architecture for an AIOTF connects to NG-RAN via an AMF. The remaining parts of the AIoT architecture
shown in Figure 4.2.2.1-2 remain unchanged.
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 12 ETSI TS 123 369 V19.3.0 (2026-03)
AIOTF AIOT3 AMF
AIOT1 N2
AIoT
NG-RAN
Device
Figure 4.2.2.3-2: NG-RAN - AIOTF Indirect Connectivity Architecture in reference point representation
4.3 Reference points
The AIoT Architecture contains the following reference points:
AIOT1: Reference point between the AIoT Device and the AIOTF.
AIOT2: Reference point between the NG-RAN and the AIOTF.
The following reference points show the interactions that exist between the NF services in the NFs. These reference
points are realized by corresponding NF service-based interfaces and by specifying the identified consumer and
producer NF service as well as their interaction in order to realize a particular system procedure.
AIOT3: Reference point between the AIOTF and the AMF.
AIOT4: Reference point between the AIOTF and the NEF.
AIOT5: Reference point between the AIOTF and the NRF.
AIOT6: Reference point between the AIOTF and the ADM.
AIOT7: Reference point between the ADM and the UDR.
AIOT8: Reference point between the ADM and the NEF.
In addition to the relevant reference points defined in TS 23.501 [3], in the case of AIoT, these reference points are as
follows:
N2: Reference point between the NG-RAN and the AMF.
N33: Reference point between NEF and AF.
4.4 Service-based interfaces
Naiotf: Service-based interface exhibited by the AIOTF.
Nadm: Service-based interface exhibited by the ADM.
In addition to the relevant services defined in TS 23.501 [3] the following service-based interfaces are enhanced for
AIoT in this specification:
Namf: Service-based interface exhibited by AMF.
Nnef: Service-based interface exhibited by NEF.
Naf: Service-based interface exhibited by AF.
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 13 ETSI TS 123 369 V19.3.0 (2026-03)
Nnrf: Service-based interface exhibited by NRF.
4.5 Functional Entities
4.5.1 AIoT Device
The AIoT Device supports the following functionality:
- Support of AIoT NAS protocol with the AIOTF.
- Support of AIoT radio interface towards AIoT reader, as defined in TS 38.300 [5].
4.5.2 NG-RAN
The NG-RAN in this specification refers to the gNB which supports AIoT related functionalities as specified in
clause 4.2.1.
The NG-RAN supports the following functions:
- The NG-RAN communicates with the AIOTF either via a direct connectivity or indirectly connectivity.
- The NG-RAN serves one or more AIoT readers.
- The NG-RAN supports the inventory and command procedures.
- The NG-RAN supports the functionalities defined in TS 38.300 [5].
- The NG-RAN and AIoT readers may aggregate data collected from multiple AIoT Devices in accordance with
the assistance information as specified in clause 5.9.
4.5.3 AIOTF
The AIOTF supports the following functions:
- Termination of AIoT NAS protocol with AIoT Device.
- Connectivity with an NG-RAN via a direct interface reference point or via an AMF.
- Support of AIoT service operations towards the AIoT Devices(s):
- Providing an interface to the AF (or via NEF) for AIoT services and authorizing the trusted AF's AIoT
service operation request.
- Triggering the NG-RAN to perform AIoT service operations towards the AIoT Device(s), and optionally
determining and providing assistance information to the NG-RAN.
- Report the service operation results to AF (or via NEF) based on the local configuration or the AF request.
- NG-RAN selection and optionally a list of RAN Reader selection for AIoT service operations.
- AMF selection based on target area information when AIOTF connects the NG-RAN indirectly via an AMF.
- Correlation ID allocation corresponding to the AF service operation request.
- Retrieving AIoT Device profile data from ADM.
- Retrieving AF subscription data from ADM.
- Optionally AIoT Device context management.
- Perform aggregation of the AIoT service responses, determine and provide assistant for the AIoT aggregation in
NG-RAN.
NOTE: Authentication of AIoT Devices related to AIOTF is defined in TS 33.369 [9].
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 14 ETSI TS 123 369 V19.3.0 (2026-03)
4.5.4 NEF
In addition to the functions defined in TS 23.501 [3], the NEF performs the following functions:
- Providing a service exposure API to AFs of 3rd party for AIoT services.
- Interacting with AF of 3rd party and AIOTF.
- Selection of AIOTF for AIoT services.
- Authorization of the untrusted AF’s AIoT operation request.
4.5.5 AF
The AF performs the following functions to support AIoT services:
- Interacting with NEF for AIoT related service exposure for 3rd party .
- Interacting with AIOTF for AIoT related service exposure for trusted AF.
4.5.6 NRF
In addition to the functions defined in TS 23.501 [3], the NRF performs the following functions:
- Support of new NF type AIOTF and its corresponding NF profile. The NF profile includes the AIOTF ID,
FQDN or IP address, NF type and the serving area information of the AIOTF.
NOTE: The serving area information of the AIOTF is constructed by the sum of the supported AIoT serving area
of the NG-RAN nodes that are directly or indirectly connected to the AIOTF.
- Support of AIOTF discovery based on parameters Target Area information.
- Support of new NF type ADM and its corresponding NF profile. The NF profile includes the ADM ID, FQDN or
IP address, NF type, the supported domain information of AIoT Device Permanent Identifiers, the supported
AIoT Device Permanent Identifier ranges, and optionally the supported AF IDs.
- Support of ADM discovery based on parameters as specified in clause 5.3.2.
The AIOTF(s) and the ADM register or update its NF profile in the NRF by means of the method as defined in
clause 4.17.2 of TS 23.502 [4].
4.5.7 AMF
The AMF performs the following functions when the NG-RAN and the AIOTF communicate indirectly via an AMF:
- Relaying signalling for AIoT service (including e.g., inventory/command messages) between NG-RAN and
AIOTF transparently.
- Providing transparent transport for AIoT NAS messages between AIoT Device and AIOTF.
4.5.8 UDR
In addition to the functions defined in TS 23.501 [3], the UDR may support the following functions:
- Storage of Ambient IoT data, including:
- AIoT Device profile data.
- AF authorization data.
4.5.9 ADM
The ADM supports the following functions:
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 15 ETSI TS 123 369 V19.3.0 (2026-03)
- Management of AIoT Device profile data.
- Management of AIoT Device security data including device credentials as defined in clause 4.2.3 of
TS 33.369 [9].
- Management of AF authorization data.
The AIoT Device profile data and AF authorization data used by the ADM may be stored in the UDR.
4.6 Protocol Stacks
4.6.1 General
This clause specifies the protocol stacks among entities used for AIoT. The protocol stacks include the following:
- Protocol stacks between AIoT Device and AFs, including the protocol stacks among AIoT Device, NG-RAN,
AMF, AIOTF, NEF and AFs.
4.6.2 Protocol Stack between AIoT Device and AF
4.6.2.1 General
The NG-RAN communicates with AIOTF via one of the two connectivity options as following:
- Direct Connectivity: When the NG-RAN communicates with AIOTF directly, the protocol stack is specified in
clause 4.6.2.2.
- Indirect Connectivity: When the NG-RAN communicates with AIOTF indirectly via an AMF, the protocol stack
is specified in clause 4.6.2.3.
For both connectivity options, NG-RAN communicates with AIOTF or AMF via NGAP as specified in TS 38.413 [10].
The AIoT NAS protocol supports the Inventory and Command related procedures as defined in clause 6.
4.6.2.2 Protocol Stack between AF and AIoT Device for NG-RAN Direct Connectivity
AIoT AIoT
Data Data
Relay Relay
AIoT NAS
AIoT NAS
Relay
SBI SBI API API
NGAP AIOT NGAP AIOT
information information
NGAP
NGAP
AIoT AS AIoT AS
Layers Layers
Lower Lower Lower Lower
Layers Layers Layers
Layers
Lower Lower
Layers Layers
AIoT Device NG-RAN AIOTF NEF AF
AIOT2
Legend:
- AIoT Data: It is the application data exchanged between the AIoT Device and the AF.
- AIoT NAS: The NAS protocol between AIoT Device and the AIOTF.
- AIoT AS: It is between the AIoT Device and the NG-RAN as specified in TS 38.300 [5].
- NGAP: Application Layer Protocol between the AIOTF and the NG-RAN as defined in TS 38.413 [10].
- NGAP AIoT Information: It is the subset of NGAP information and is included in the NGAP messages
over AIOT2 reference point.
Figure 4.6.2.2-1: Protocol Stack between AF and AIoT Device for Direct Connectivity option
The AIoT NAS messages between the AIoT Device and the AIOTF are transferred via the NG-RAN transparently.
ETSI
3GPP TS 23.369 version 19.3.0 Release 19 16 ETSI TS 123 369 V19.3.0 (2026-03)
4.6.2.3 Protocol Stack between AF and AIoT Device for NG-RAN Indirect
Connectivity
AIoT AIoT
Data Data
Relay Relay
AIoT NAS
AIoT NAS
Relay
SBI SBI API API
NGAP AIOT
NGAP AIOT
information information
Relay
SBI
NGAP
NGAP SBI
AIoT AS AIoT AS
Layers Laye
...