hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.4 Reference Architecture and NFs | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.4.1 Pure Control Plane | Figure 6.4.1.4.1-1: The example of reference architecture which supporting topology 1 & 2
Up to different deployment, the above NF may be collocated or standalone. The above reference architecture can be separate into the following alternatives:
- Alternative1: a standalone network supporting AIoT functionality only.
-... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.4.2 User Plane of UE reader | Figure 6.4.1.4.2-1 An example of reference architecture for discovering UE reader via control plane and AIoT device related data delivery via UE reader user plane |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.5 Protocol Stack | Both the App layer and the AIoT layer are beyond the AIoT AS layer and belongs to non-access layer.
- The App layer are used to transmit the information between the AIoT device and the Server.
- The AIoT layer is used to transmit the information between the AIoT device and UE reader / CN.
Figure 6.4.1.5-1: protocol sta... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.2.1 Purely via control plane: Inventory procedure | Figure 6.4.2.1-1: Inventory Service Flow
1. AF sends Inventory Operation Request with the following information: the number of AIoT devices, target area for the operation, client which requests the operation, match information which is used to filter and discover the target AIoT devices for the operation. The number of... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.2.2 Purely via control plane: Command procedure | Figure 6.4.2.2-1: Command Service Flow
1. AF sends a command request along with the following information: the number of AIoT devices (if the AF have it), target area for the operation, client which requests the command operation, match information which is used to filter and discover the target AIoT devices for the op... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.2.3 Discover UE reader via UE reader control plane and AIoT device related data delivery via UE reader user plane | Figure 6.4.2.3-1: Procedure flow of user plane data delivery for multiple AIoT devices
NOTE 1: In this procedure, it is assumed serving network is responsible to provide resource for reader, but the authentication happens among AIoT device, UE reader and Application Server.
Editor's note: Whether there is a need to val... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.2.4 UE reader activation | Figure 6.4.2.4-1: Service Flow
0. During Registration Request, the UE reader provide its capability as UE reader.
1. The AMF obtains the UE subscription data during the interaction with UDM.
2-3. Based on the UE subscription, the AMF authorizes the UE as a reader and notifies the authorization information to the RAN no... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.3 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing services, entities and interfaces. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.5 Solution #5: NAS-based information transfer for Ambient IoT Services | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.5.1 Description | The solution applies to the Key Issue#1 "Architecture support of Ambient IoT Devices", the Key Issue #2 "Identification, Subscription, Registration and Connection management" and the Key Issue #3 "Support of Ambient IoT Services". This solution applies to Topology 1 as defined in TR 38.848 [7].
The Figure 6.5.1-1 illus... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.5.2 Procedures | Depicted in Figure 6.5.2-1 is the procedure for NAS-based information transfer for Ambient IoT Services.
Figure 6.5.2-1: Procedure for NAS-based information transfer for Ambient IoT Services
1. AF sends an AIoT Service Request (AF Identifier, Device ID, requested service operation, area information) message to the NEF.... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.5.3 Impacts on services, entities and interfaces | NEF:
- The NEF authorizes AF request, retrieves the served AMF/AIoTF information or maps the area information to the corresponding AMF/AIoTF, and forwards service request/response between AF and AMF/AIoTF.
AMF/AIoTF:
- The AMF/AIoTF selects BS and delivers service request to the AIoT Device via BS, and receives service... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.6 Solution #6: AIoT device authentication, ID validation and AIoT communication | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.6.1 Key Issue mapping | This solution addresses the following requirements:
- from Key Issue #1 the requirement:
- System architecture identified along with the solutions for KI#2 and KI#3.
- Validation of the Ambient IoT Device identifier.
- Whether and how to secure device operations and services for an Ambient IoT Device or a group of Ambi... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.6.2 Functional Description | The security protection of AIoT data can be categorized in the following way:
- Application layer security between the AIoT device and AIoT server. The application layer security is outside the scope of 3GPP.
- Network layer security between the AIoT device and network (NG-RAN and 5GC). The AIoT data/signalling transmi... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.6.3 Procedures | The Figure 6.6.3-1 describes the signalling flow for the authentication and ID validation of AIoT devices and secure AIoT communication.
Figure 6.6.3.1-1: Signalling flow for the authentication and ID validation of AIoT devices and secure AIoT communication
The detailed description of the steps is provided as follows:
... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.6.4 Impacts on existing services, entities and interfaces | The following NFs and interfaces are impacted:
- AIoT-GW: a new NF with the functionality described in clause 6.6.2. AIoT-GW can support the functionality to aggregate the UL data of the devices with the same group and provide the aggregated data to the AF.
- AIoT reader (BS or UE as intermediate node): supporting 1) A... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.7 Solution #7: Bulk Introduction of Devices to the Network | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.7.1 Description | This solution is targeting KI#2 Identification, Subscription, Registration and Connection management. It is related with KI#1 as well.
Regarding the Registration, the following should be considered.
- AIoT Devices have ultra-low complexity/power/cost and are resource-constrained.
- The network needs to support a huge n... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.7.2 Procedures | Bulk Introduction of Devices to the Network procedure for Ambient IoT ID is depicted in Figure 6.7.2-1.
Figure 6.7.2-1: Bulk Introduction of Devices to the Network procedure for Ambient IoT
0. Before deployment, Registration of Group of Ambient IoTs via AF is done. AF stores all the credentials of Ambient IoTs per a se... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.7.3 Impacts on services, entities and interfaces | AF:
- Performs Bulk Introduction of Devices to the Network with the PLMN. This Registration of devices can be done before deployment.
- Stores all the credentials of Ambient IoTs per a service.
NEF:
- Supports signalling for Bulk Introduction of Devices to the Network between AF and AMF.
AMF:
- Supports Bulk Introducti... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.8 Solution #8: Inventory for AIoT Devices using AIOTF | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.8.1 Description | This solution addresses subscription, registration and connection management aspect of Key Issue #2, which is based on the following system architecture.
The functional entities defined in TS 23.501 [4] are reused with the exception for the following additions:
- Ambient IoT Function (AIOTF): AIOTF is introduced to sup... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.8.2 Procedures | NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.8.2.1 Application Inventory Procedure | The application inventory procedure is initiated by the AF to discover one or more AIoT devices in a specific area.
Figure 6.8.2.1-1: Inventory Procedure
1. The AF sends Inventory Message Request to the NEF, containing the area information, device information, optional inventory strategy information, and optional repor... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.8.2.2 Periodic Inventory Procedure | The periodic inventory procedure is initiated by the CN or A-RAN, which follows the instructions from the AF,
Figure 6.8.2.2-1: Periodic Inventory Procedure
The AIOTF or the A-RAN may initiate the periodic inventory procedure based on the inventory strategy information provided by the AF, to enable the AIoT devices to ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.8.3 Impacts on services, entities and interfaces | Editor's note: The services, entities and interfaces are FFS. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.9 Solution #9: Information Transfer without a PDU Session | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.9.1 Description | This solution is to address the KI#1, KI#2 and KI#3. This solution is to support the DO-DTT and DT traffic type and an enhancement to the 5GS to support the AIoT Device. The main points are as following:
- The AIoT Device still performs the initial registration procedure, and after the initial registration procedure, t... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.9.2 Procedures | Figure 6.9.2-1 shows the signalling flow for the DT traffic (e.g command) delivery and DO-DTT data reporting.
Figure 6.9.2-1 Signalling flow for Information Transfer
1. AF performs the service configuration. This service configuration can provide the AIoT Device ID(s) information to the AIoT NF. The AIoT NF can further... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.9.3 Impacts on services, entities and interfaces | Editor's note: The impacts on services, entities and interfaces are FFS. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.10 Solution #10: Registration procedure for Ambient IoT Devices | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.10.1 Description | This solution is for Key Issue #2 "Identification, Subscription, Registration and Connection management".
As depicted in Architecture Requirements, the DT and DO-DTT traffic types will be studied in this stage. The Ambient IoT devices could be driven by the network for Topology1 or UE for topology 2 before registering ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.10.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.10.2.1 Procedures for AF triggered Registration for Topology 1 | The following figure presents a procedure of AF triggered registration for Topology 1.
Figure 6.10.2-1: AF triggered Registration Procedure for Topology 1
0.a. The Ambient IoT devices are pre-configured with default AIoT device ID and default credentials. TID (See GS1 TDS Release 2.1 [10]) is configured by AIoT manufac... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.10.2.2 Procedures for AF triggered Registration for Topology 2 | The registration may be triggered by AF via the UE reader. The UE reader interacts with AMF /New Ambient IoT NF via NG-RAN, which could be regarded as an AF triggered registration procedure for topology 2.
Figure 6.10.2-2: AF triggered Registration Procedure for Topology 2
1. The UE Reader performs the registration pro... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.10.3 Impacts on services, entities and interfaces | NEF:
- Capability to authentication and authorization to the third ambient IoT AF.
- Capability to support verification on operator ID list.
AMF/Ambient IoT NF:
- The AMF/Ambient IoT NF selects the NG-RAN reader and/or UE reader based on the TA list, Location, and AF ID.
- Capability to aggregate the Ambient IoT device... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.11 Solution #11: 5GC support for AF to communicate with AIoT devices | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.11.1 Description | This solution address aspects of key issue #3 on Support of Ambient IoT Services.
This solution enables the AF to communicate with the target AIoT devices for DO-DTT and DT traffic types via 5GC, dedicated for only Topology 2.
This solution considers scenarios in which an application service provider has prior informat... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.11.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.11.2.1 Communication with AIoT devices | The procedure for communicating with AIoT devices based on AF request is depicted in figure 6.11.2.1-1.
Figure 6.11.2.1-1: Information Flow for AIoT data retrieval
To facilitate communication between an external AF with AIoT devices for data retrieval, this solution proposes certain measures to be taken:
0. It is assum... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.11.2.2 Selection of intermediate nodes | The selection of the intermediate node can be performed based on the geographical location of the target AIoT devices or the identity of the intermediate node from AF. The procedure for selection of intermediate nodes based on geographical location is depicted in figure 6.11.2.2-1.
Figure 6.11.2.2-1: Information Flow f... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.11.3 Impacts on services, entities and interfaces | Impacts on existing entities:
NEF:
- Supports exposing a new API to AF for AIoT services.
UDM:
- Supports validating if a UE is authorized to act as an I-node.
AMF:
- Supports forwarding the AIOTF requests to gNB.
gNB:
- Supports handling new AIoT related services.
- Supports making the final selection of the I-node.
U... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.12 Solution #12: UE Function Delegation in Intermediate Node for AIoT Device | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.12.1 Description | This solution applies to those AIoT devices that are not capable of direct communication with a 5G network, and instead, may communicate with the network through an Intermediate Node (IN), or "IN-UE". The AIoT device and the IN-UE may communicate with each other using backscattering communication or other sidelink tech... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.12.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.12.2.1 UFDM instantiation and provisioning | Figure 6.12.2.1-1: UFDM instantiation and provisioning
1. The IN-UE is authorized as a IN. This may happen during the IN-UE Registration based on IN-UE capabilities and subscription information. The AIoT devices that the IN-UE can act as IN may be preconfigured in the UE and provided by the network during the authoriza... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.12.2.2 UFDM Registration | UFDM acts as a separate "UE" towards the network so it performs Registration procedures similar to what a normal UE would do. However, to avoid unnecessary signalling, some of the UFDM's Registration procedures (e.g. periodical Registration update or mobility Registration update) may be combined with the IN UE's own Re... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.12.3 Impacts on services, entities and interfaces | UE:
- Supports UFDM instantiation and management.
- Supports forwarding UFDM NAS signalling as payload of IN UE NAS messages.
- Supports AIoT data forwarding as UFDM data.
AMF:
- Supports handling UFDM NAS messages as IN NAS payload.
- Supports handling AIoT Device Provisioning procedure.
- Supports maintaining associa... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.13 Solution #13: Multi-level Device ID management | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.13.1 Description | When it comes to Ambient IoT Device ID Management, it is likely that different Device ID formats are expected depending on the procedures to be followed between Ambient IoT Device, Reader, Controller and Application Function.
On highest level, a Permanent ID is expected to enable uniquely identifying Ambient IoT Device... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.13.2 Procedures | At least, two levels of temporary IDs are proposed:
- Long temporary ID: A long temporary Device ID to be used between the Controller and the Reader for command procedures (similar to paging) for certain Ambient IoT Device(s):
- A set of long temporary IDs can be assigned and pre-provisioned by the Controller to the Re... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.13.3 Impacts on services, entities and interfaces | Controller:
- Assign and pre-provision a set of long temporary IDs per Reader.
- Use long temporary ID as part of command procedures towards the Reader(s) for certain Ambient IoT Devices.
- Maintain the mapping between long temporary ID and unique Ambient IoT Device identifier (e.g. based on the Permanent ID) based on ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.14 Solution #14: AIoT Device ID with consideration on credential holder, service provider and mobile network | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.14.1 Description | This solution addresses the KI#2 and the aspect about how to identify Ambient IoT Device and how to format the identifier.
In this solution, the following terms have been used:
- AIoT Device ID: the identifier used to identify the AIoT Device;
- Serving network: PLMN network which includes the Reader and the radio/core... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.14.2 Procedures | This clause is to describe the high-level procedure including configuration and provisioning for 2 cases as specified in clause 6.14.1. Other details how to utilize the AIoT Device ID are specified in other solutions.
Case 1:
Figure 6.14.2-1: High-level procedure for case 1
1. If the AF is in the 3rd party, then the 3r... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.14.3 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing services, entities and interfaces. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.15 Solution #15: Ambient IoT Device States | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.15.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.15.1.1 Overview | This solution addresses KI#2, KI#3 and proposes new states and sub-states for AIoT devices that may assist the AIoT services the AIoT device supports in any particular moment. In particular, the solution consists of the following aspects:
- A new set of states or mode of operations are defined for the AIoT device, whic... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.15.1.2 New AIoT Device States | AIoT device states can be useful for the application and/or the network to be aware of which AIoT devices are already operating and which function they may be performing, which may in turn assist in their management and monitoring. As an example, the reliability of inventory taking results would be higher when all the ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.15.2 Procedure for State Toggling in AIoT Devices | An AIoT device may operate in any of the states described in clause 6.15.1.2. This clause proposes a method by which the network can toggle the AIoT device state by issuing a command such that the AIoT device will transition from one state to another. Toggling the state of an AIoT device may be useful e.g. after the AI... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.15.3 Impacts on services, entities and interfaces | Editor's note: Impacts are FFS. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.16 Solution #16: AIoT Registration/Onboarding | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.16.1 Description | This solution addresses the part of KI#2 related to the AIoT device registration/onboarding. The first bullet and NOTE 1 in solution#1 of clause 6.1.2 mention the onboarding and parameter provisioning. This solution provides a procedure to achieve this.
The relation between this solution and solution 1, is that this so... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.16.2 Procedures | CN NF is used to name the network function that performs the necessary task to register/onboard an AIoT device to the network. The CN NF will be defined together with the system architecture design to support the Ambient IoT in 5GC.
Figure 6.16.2-1: Registration/onboarding procedure for an AIoT device.
0. It is assumed... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.16.3 Impacts on services, entities and interfaces | Impacts on existing entities:
CN NF:
- Configure/trigger the Reader to broadcast Registration poll message.
- Retrieve device owner information and device unique onboarding information.
- Accept or reject the AIoT device registration/onboarding request.
AIoT device:
- Receive a Registration poll message.
- Transmit a R... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17 Solution #17: Enable Ambient IoT Management within 5GC to support AIoT services | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.1.1 General | This solution addresses the key issues in terms of architecture enhancements, Ambient IoT (AIoT) Device management and AIoT services, i.e. for KI#1, KI#2 and KI#3. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.1.2 Architecture Principles | This solution proposes to introduce enhancements in the 5GS to support AIoT Device management and AIoT services. In particular,
- AIoT specific NAS, to support transfer of AIoT data (AIoT Device Operation commands and responses) between AIoT Device and 5GC directly via the gNB.
- Ambient IoT Management Function (AIoTMF... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.1.3 Function Principles | Inventory: collect the AIoT Device ID(s) of all or a subset of AIoT Devices discovered and selected with MASK.
AIoT Service: the network capability that utilizes the NEF exposure capability towards AF and utilises the AIoT Device Operations towards AIoT Device to support AIoT use cases.
AIoT Device Operation: the opera... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.2.1 General | This clause provides end to end high-level information flow for support of AIoT service (Inventory, Command [Read/Write], Disable) over 5GS as specified in clause 6.17.2.2, as well as the NEF service operations as specified in clause 6.17.2.3. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.2.2 AIoT Service High-Level Information Flow | Figure 6.17.2.2-1: AIoT Service High-Level Information Flow
1. During the node-level AIoT-NGAP association establishment procedure, the RAN reports the RAN's AIoT information (e.g. RAN ID, Reader ID(s), coverage area of the Reader(s)) to the AIoTMF.
2. Upon reception of the RAN's AIoT information, the AMF/AIoTMF aggreg... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.2.3 NEF AIoT Service | The NEF supports a new Nnef_AIoT service with the operations described in table 6.17.2.3-1.
Table 6.17.2.3-1: AIoT Service provided by NEF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nnef_AIoT_Service
Inventory
Request/Response
AF
Read
Request/Response
AF
Write
Request/Response
AF
Disable
Re... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.17.3 Impacts on services, entities and interfaces | UDM:
- Support subscription-like information for AIoT Devices and service control information as in clause 6.17.1.2.
NEF:
- Support AIoT services as in clause 6.17.2.3.
(New) AIoTMF:
- Support logic handling of AIoT services and AIoT NAS as in clause 6.17.1.2.
AIoT NAS:
- Support transfer of AIoT data (AIoT Device inve... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.18 Solution #18: Solution for support of Ambient IoT services | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.18.1 Description | This solution resolves Key Issue #3 about the Support of Ambient IoT Services. The following two connectivity topologies as defined in TR 38.848 [7] are to be studied:
- Topology 1: BS <--> Ambient IoT Device;
- Topology 2: BS <--> intermediate node <--> Ambient IoT Device: Only a UE can act as an intermediate node tha... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.18.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.18.2.1 Ambient IoT service - Network initiated Ambient IoT service procedure | Figure 6.18.2.1-1: Network Initiated Ambient IoT service procedure
1. Ambient IoT devices perform activation and registration procedures. Ambient IoT devices will have the EPC info and device ID, and UDM will have the Ambient IoT device profile info indexed by device ID after successful Ambient IoT devices activation a... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.18.3 Impacts on services, entities, and interfaces | This solution impacts the following entities:
NEF:
- Capability to support the selection of the serving AMF or serving new Ambient IoT NF based on location information.
- Capability to aggregate the retrieved Ambient IoT devices' EPC contents based on transaction ID.
- Capability to support Ambient IoT service-related ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19 Solution #19: AIoT communication for connectivity topology 1 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.1 Key Issue mapping | This solution addresses the following requirements:
- from Key Issue #1 the requirement:
- System architecture identified along with the solutions for KI#2 and KI#3.
- from Key Issue #3 the requirements:
- Study how to support information transfer for Ambient IoT services and related system functionality, including the... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.2 Functional Description | This solution focuses on the Topology 1. It is proposed that the AIoT is a new radio access technology (RAT) type supported in the Base Station (BS). The BS nodes supporting the AIoT RAT establish N2' association with the 5GC (specifically with the AIoT function, AIoTF). The N2' association is independent of the N2 ass... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.3 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.3.0 General | Two procedures are shown to explain the concept of this solution:
- the procedure for N2' association establishment for AIoT data/signalling transmission for connectivity topology 1; and
- the procedure for and AIoT service-based session establishment between the AIoTF and the AIoT AF/AS and AIoTF and the BS AIoT Reade... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.3.1 N2' association establishment | The Figure 6.19.3.1-1 describes the signalling flow of the N2-like (N2') association establishment between of AIoT capable BSs for reader functionality (called "BS AIoT Reader)" and the AIoTF.
The Figure 6.19.3.1-1 shows AIoTF1 and AIoTF2 to express the optional flexibility that a BS AIoT Reader can establish N2' assoc... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.3.2 AIoT session establishment between the AIoTF and the AIoT AF/AS and AIoTF and the BS AIoT Reader | The Figure 6.19.3.2-1 describes the signalling flow of the AIoT session establishment between the AIoTF and the AIoT AF/AS and between the AIoTF and the BS AIoT Reader via the N2' association. Such AIoT session is established for a particular AIoT service, e.g. inventory service or command/response service to AIoT devi... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.19.4 Impacts on existing services, entities and interfaces | The following NFs and interfaces are impacted:
- AIoTF: a new NF with the functionality described in clause 6.19.2.
- BS AIoT Reader: 1) supporting AIoT capabilities to communication with the AIoT devices and 2) capabilities to select an AIoTF and to establish N2' association with the AIoTF.
- NEF: expose a new API for... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.20 Solution #20: E2E handling for interaction of AIoT Device related information | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.20.1 Description | The solution is to address KI#1#2#3.
The interaction for AIoT Device related information may happen between AIoT device and AIoT function or AF. Those AIoT Device related information includes:
- Device UL info which is from AIoT device and will be sent to AIoT function or AF.
- Device DL info which is from AIoT functio... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.20.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.20.2.1 The interaction for AIoT Device among AIoT device, reader and AIoT Function | Figure 6.20.2.1-1: Service Flow
1. An AF requests AIoT operation to the AIoT Function directly or via NEF.
2. AIoT Function allocates an AIoT operation session ID used for the once invoked AIoT operation request and it is used to associate the information related to AIoT operation during the AIoT operation session. The... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.20.2.2 The interaction for AIoT Device among AIoT device, reader, AIoT Function and AF | Figure 6.20.2.2-1: Service Flow
Steps 1-8 are the same as steps1-8 as described in clause 6.20.2.2-1.
9. If Device-A UL Info is for AF, the AIoT function forward it the AF with the AIoT operation session ID.
NOTE 1: Device-A present one AIoT device.10. Optionally, the AF may send to the AIoT function the Device-A DL In... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.20.3 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing services, entities and interfaces. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.21 Solution #21: Architecture enhancement to support AIoT services for topology 2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.21.1 Description | The solution applies to the Key Issue#1 "Architecture support of Ambient IoT Devices", the Key Issue #2 "Identification, Subscription, Registration and Connection management" and the Key Issue #3 "Support of Ambient IoT Services". This solution applies to Topology 2 as defined in TR 38.848 [7].
The Figure 6.21.1-1 illu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.