hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.21.2 Procedures | Depicted in Figure 6.21.2-1 is the procedure to support AIoT Services for Topology 2.
Figure 6.21.2-1: Procedure to support AIoT Services for Topology 2
1. UE performs Registration procedure as defined in TS 23.502 [5]. The UE includes AIoT Communication Indication in the Registration Request message and the AIoT Commu... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.21.3 Impacts on services, entities and interfaces | AIoTF:
- AIoTF is introduced to support transfer of service request from AF (via NEF) to UE via AMF, and transfer of service response from UE via AMF to AF (via NEF).
NEF:
- NEF is enhanced to support transfer of service request from AF to AIoTF, and transfer of service response from AIoTF to AF.
UDM:
- UDM is enhanced... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22 Solution #22: AF Based Solution for Topology 2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.1.0 General | This solution proposes an AF based solution, which addresses KI#1, KI#2 and KI#3.
In this solution, it is AF who is in charge of the intermediate UE for the Ambient IoT operations, including communicating with and determining intermediate UEs, sending operation commands to and receiving results from intermediate UEs. A... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.1.1 Reference Architecture | The Figure 6.22.1.1-1 illustrates the architecture for AF based solution:
Figure 6.22.1.1-1: System Architecture of AF Based Solution
This solution focuses on Topology 2.
Editor's note: It is FFS whether and how the solution can be evolved for Topology 1.
The functional entities defined in TS 23.501 [4] are reused with... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.1.2 Protocol Stack | The Figure 6.22.1.2-1 illustrates the protocol stack for AF based solution over user plane:
Figure 6.22.1.2-1: Protocol Stack for AF Based Solution (over user plane)
Within the protocol stack:
- UE AIoT layer: between AF and UE reader. AF provides Ambient IoT operation commands to Intermeidate UEs via UE AIoT layer.
- ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.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.22.2.1 AIoT Service Authorization for Intermediate UE | The Registration procedure for UE is performed as defined in clause 4.2.2.2 of TS 23.502 [5] with the following additions:
- UE includes the AIoT Intermediate node capability as part of "5GMM capability" in Registration Request message.
- The AMF obtains the AIoT Subscription data as part of the user subscription data ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.2.2 Inventory Procedure | The Inventory procedure can be initiated by the AF to discover one or more AIoT devices in a specific area via Intermediate UEs.
Figure 6.22.2.2-1: Inventory Procedure
1. Via the Intermediate UE's PDU session user plane or control plane, the Intermediate UE communicates with the AF to transport UE AIOT layer messages, ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.2.3 Command Procedure | The Command procedure is initiated by the AF to request one or more AIoT devices in a specific area to execute a command via Intermediate UEs. The device may or may not send back the command results depends on the command.
Figure 6.22.2.3-1: Command Procedure
1. Via the Intermediate UE's PDU session user plane or contr... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.22.3 Impacts on services, entities and interfaces | The following NFs are impacted:
- UDM/UDR:
- Store the authorization information of Intermediate UE for AIoT.
AMF:
- Receive AIoT capability information from UE and authorize based on the subscription data in UDM/UDR.
NG-RAN:
- Provide spectrum information towards authorized intermediate UE.
- Intermediate UE:
- Provid... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23 Solution #23: UE reader selection for inventory procedure | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23.1.1 Definition | AIoT device capability: e.g. inventory frequency, etc. Different AIoT devices may support different inventory frequency.
reader: part of the intermediate node UE, which can communicate with the AIoT device via radio interface.
UE reader capability: e.g. inventory frequency, etc. Different readers may support different ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23.1.2 General | This solution applies to Key issue #3 in terms of selecting the reader used for Ambient IoT inventory service.
This solution applies to the following scenario:
- The AF (i.e. third party) uses a bulk of AIoT devices that have the same AIoT device capabilities, e.g. the same inventory frequency, etc.;
- the AF holds the... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23.1.3 Architecture and Principles | Figure 6.23.1.3-1: Reference architecture
The principles of the solution:
- AF provides the AIoT device capability to the Ambient IoT Function (AIoTF);
- the selection of the intermediate node UE will be based on: the AIoT device capability, the inventory area wherein the AIoT devices are supposed to be, and the the UE... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23.2 Procedures | This clause provides how to select the UE readers that will be used for the inventory procedure.
Figure 6.23.2-1: UE reader selection procedure
1. The intermediate node UE performs the registration procedure. The AIoT UE reader capabilities (e.g. supported inventory frequency) will be transmitted to the AMF via the NAS... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.23.3 Impacts on services, entities and interfaces | NEF:
- NEF is enhanced to support transfer of AIoT service request from AF to AIoTF.
AIoTF:
- AIoTF is introduced to support mapping the AIoT related information from the third party defined format to the 3GPP defined format;
- Supports selecting intermediate node.
AMF:
- Supports providing the information of the inter... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.24 Solution #24: Availability Reporting without Ambient IoT Device Timers | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.24.1 Functional Description | This solution focuses on the registration management and/or connection management aspects of Key Issue #2 "Identification, Subscription, Registration and Connection management".
The main principle of the proposal is that the architecture should support a way for the Ambient IoT Device to determine when it needs to perf... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.24.2 Procedures | Figure 6.24.2-1 shows the procedure.
Figure 6.24.2-1: Procedure for Ambient IoT Device Availability Reporting
1. Upon network or IN trigger (e.g. activation signal, inventory request, not shown in the figure) the Ambient IoT Device sends a control plane request to the network. For example, it may be a device Registrati... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.24.3 Impacts on existing services, entities and interfaces | Network:
- Sends a time value to the Ambient IoT Device.
RAN/Intermediate Node UE:
- Broadcast time information.
Ambient IoT Device:
- Receives and stores a time value from the network.
- Reads broadcasted time information.
- Compares the broadcasted time information with the value that was received from the network an... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.25 Solution #25: Subscription Management for Ambient IoTs | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.25.1 Description | This solution is targeting KI#2 Identification, Subscription, Registration and Connection management. It is related with KI#1 as well.
Regarding the subscription management for Ambient IoTs, the following should be considered.
- No USIM (UICC): No Root Key (e.g. LTE K):
- Not available existing EPS-AKA, EAP-AKA', 5G AK... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.25.2 Procedures | Overall Procedures of Subscription for Ambient IoT is as depicted in Figure 6.25.2-1.
Figure 6.25.2-1: Subscription procedures for Ambient IoT Devices
1. AF sends AmbientIoT Subscription Request to NEF. It contains AF ID, Usage ID, List of Ambient IoT ID(s) which take part in this TASK, TASK information.
2. NEF sends A... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.25.3 Impacts on services, entities and interfaces | AF:
- Performs Online-subscription management for Ambient IoTs with the PLMN.
UDM:
- Supports Online-subscription management of Ambient IoTs.
AMF/SMF:
- Supports pre-Configuration based on the request from the AF. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26 Solution #26: Unified API for Topology 1 and Topology 2 for an AF | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.1.1 General | There are two connectivity topologies are studied:
- Topology 1: BS <--> Ambient IoT Device;
- Topology 2: BS <--> intermediate node <--> Ambient IoT Device: Only a UE can act as an intermediate node which is under the network control.
Different topologies will use different types of reader (BS Reader or UE Reader) to ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.1.2 Example Target Sets | The Target Sets can be constructed between the operator and the AF and allows the AF to target specific cases. For example, consider deployment such as shown in Figure 6.26.1.2-1, there can be many different areas an AF may wish to target with a, for example, inventory.
Figure 6.26.1.2-1: Example Target Sets Plan
For e... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.1.2 NEF IoT Services | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.1.2.0 Overview | This solution takes the NEF Inventory service operation captured in Solution #17 as baseline/example to illustrate how the Target Set parameter can be provided to 5GC and how 5GC could additionally provide additional information in the responses. The principle can be applied to any solution. In the example service oper... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.1.2.1 Inventory service operation | 6.26.1.2.1.1 Nnef_AIoT_Inventory service operation
Service operation name: Nnef_AIoT_Inventory
Description: The inventory operations for the Nnef_AIoT service allows the consumer to request to perform an inventory device operation for an AIoT device or a group of AIoT devices via a set of reader(s).
Inputs, Required: N... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.2 Procedures | The example procedure below shows how 5GC determines the readers requested in the AFs request and depending on type interacts with a BS Reader or UE Reader or both types to fulfil the request.
Figure 6.26.2-1: Procedure for unified API between 5GC and AF to support AIoT service
1. AF sends a service request to NEF to t... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.26.3 Impacts on services, entities and interfaces | 5GC:
- The service operations exposed need to include a Target Set ID
- 5GC needs to determine which readers are used based on the Target Set
RAN/BS Readers:
- None.
UE Reader:
- None.
AIoT Device:
- None. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.27 Solution #27: AIoT service operation with privacy and authentication protection. | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.27.1 Description | This solution address KI#3 and proposes procedures that provides privacy and authentication protected Ambient IoT service (Command and Inventory) for both the operator and the AIoT device. The AIoT device must know that the Reader (UE or Base station) is an authorized Reader to receive e.g. sensor information from the ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.27.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.27.2.1 Inventory procedure | The name CN NF is used to name the network function that performs the necessary operation for an AIoT device when the network provides the AIoT service operation. The CN NF will be defined together with the system architecture design to support the Ambient IoT in 5GC. The Reader can be a base station Reader or UE Reade... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.27.2.2 Command procedure | The name CN NF is used to name the network function that performs the necessary operation for an AIoT device when the network provides the AIoT service operation. The CN NF will be defined together with the system architecture design to support the Ambient IoT in 5GC. The Reader can be a base station Reader or UE Reade... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.27.3 Impacts on services, entities and interfaces | Impacts on existing entities:
CN NF:
- Receive Inventory/Command request from AF.
- Select and trigger the Reader(s) to broadcast Inventory trigger or send Command message based on the information received by the AF.
- Receive response(s) from the AIoT device(s) and authenticate that the response(s) originate from regi... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.28 Solution #28: Device-Reader Binding Information | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.28.1 Description | The network stores the binding information between devices and their serving readers. For Topology 1 in which RAN acts as a reader, the Device-Reader binding information includes Device ID and the identity of RAN serving the device; for Topology 2 in which an intermediate node UE acts as a reader, the Device-Reader bin... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.28.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.28.2.1 Device-Reader Binding Information Storage | Figure 6.28.2.1-1 depicts a flow diagram for Device-Reader binding information acquirement and storage.
Figure 6.28.2.1-1: Device-Reader binding information storage
The steps in the Device-Reader binding information storage procedure are as follows:
1. AIoT AF initiates inventory service to NEF. The inventory request i... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.28.2.2 Device-Reader Binding Information Usage | Figure 6.28.2.2-1 depicts a flow diagram regarding the usage of Device-Reader binding information.
Figure 6.28.2.2-1: Device-Reader binding information usage
The steps in the Device-Reader binding information usage procedure are as follows:
1. AIoT AF sends Ambient IoT service request to NEF; the service could be Comma... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.28.3 Impacts on Existing Nodes and Functionality | AIoTMF/AMF:
- Fetch and cache Device-Reader binding information.
- Store Device-Reader binding information into UDM.
- Obtain Device-Reader binding information from UDM.
- Share Device-Reader binding information with other AIoTMF/AMFs.
UDM:
- Store and provide Device-Reader binding information.
NEF:
- Receive AIoT serv... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29 Solution #29: Periodic triggered Ambient IoT Devices for registration update in Topology-1 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.1 Description | This solution is targeting KI#2 Identification, Subscription, Registration and Connection management. It is related with KI#1 as well.
It is assumed each Ambient IoT device has and is identified with a unique internal ID (e.g. EPC ID), and is capable of DO-DTT transmission only. It is assumed each the BS serves a regis... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.2.1 Periodic triggered AIoT devices to perform Registration Update | The procedure of Periodic Registration Update that serves also as Mobility Registration Update is as depicted in Figure 6.29.2.1-1.
Figure 6.29.2.1-1: Periodic triggered AIoT devices to perform Registration Update
0. Periodic notification timer (e.g. 1 hour) set by BS#1 (AIoT RA#1) expires.
1. BS#1 (AIoT RA#1) broadcas... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.2.2 Periodic triggered AIoT devices to perform Registration Update (Continued) | The procedure of Periodic Registration update that serves also as Mobility Registration Update continues as depicted in Figure 6.29.2.2-1.
Figure 6.29.2.2-1: Periodic triggered AIoT devices to perform Registration Update (Continued)
0. It is assumed that AIoT device#2 has moved to the coverage of BS#1 (AIoT RA#1). Anot... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.2.3 BS relocation according the update of the latest registration area of AIoT device | The procedure of Periodic Registration update that serves also as Mobility Registration Update when Ambient IoT device moves is as depicted in Figure 6.29.2.3-1.
Figure 6.29.2.3-1: BS relocation according the update of the latest registration area of AIoT device
0. It is assumed that after 3 hours, AIoT device#1 moves ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.2.4 Deregistration | The procedure of Deregistration is as depicted in Figure 6.29.2.4-1.
Figure 6.29.2.4-1: Deregistration
1. After that, it is assumed that another 7 hours have passed, and there is no notification from AIoT device#1. Due to the expiration of AIoT Mobile Reachable Timer for AIoT device #1, AMF sets AIoT Implicit De-regist... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.29.3 Impacts on services, entities and interfaces | UDM:
- Supports the registration management for AIoT devices based on the AIoT device identifier.
AMF:
- Storing RA of AIoT device and supports controlling contexts for the registration management stored in BS (i.e. removing them when needed).
- Supports setting AIoT Mobile Reachable Timer and AIoT Implicit de-registra... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30 Solution #30: Support AIoT Devices using AIOTF for Topology 2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.1.0 Introduction | This solution proposes a complementary solution to Solution #8. It enables the support of Ambient IoT devices for topology 2, which addresses KI#1, KI#2 and KI#3. Together with Solution #8 which focus on Topology 1, the solutions can support AIoT devices for both Topologies.
In this solution, it is AIOTF who is in char... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.1.1 Reference Architecture | The Figure 6.30.1.1-1 illustrates the architecture for supporting AIoT Devices using AIOTF for Topology 2:
Figure 6.30.1.1-1: System Architecture of Supporting AIoT Devices using AIOTF for Topology 2
This solution focuses on Topology 2, which works together with Solution #8 addressing Topology 1.
The functional entitie... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.1.2 Protocol Stack | The Figure 6.30.1.2-1 illustrates the protocol stack:
Figure 6.30.1.2-1: Protocol Stack for Supporting AIoT Devices using AIOTF for Topology 2
Within the protocol stack, the AIOT Device NAS layer, AIOT AS layer and App layer are defined as Solution #8.
As UE reader is used in Topology 2, which is different from the RAN... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.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.30.2.1 AIoT Service Authorization for Intermediate UE | The Registration procedure for UE is performed as defined in clause 4.2.2.2 of TS 23.502 [5] with the following additions:
- UE includes the AIoT Intermediate node capability as part of "5GMM capability" in Registration Request message.
- The AMF obtains the AIoT Subscription data as part of the user subscription data ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.2.2 AIOTF Keep Track of Intermediate UE | For authorized Intermediate UEs (Those Ambient IoT Capable UEs which have been authorized by the AMF as described in clause 6.30.2.1), in Initial Registration procedure as defined in clause 4.2.2.2 of TS 23.502 [5] with the following additions:
- The AMF sends Create UE Context Request to the AIOTF for the Intermediate... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.2.3 Application Inventory Procedure | The Inventory procedure can be initiated by the AF to discover one or more AIoT devices in a specific area via Intermediate UEs.
Figure 6.30.2.3-1: Inventory Procedure
1. AF sends Inventory Request to the AIOTF, which is the same as step 1 - 4 in Figure 6.8.2.1-1 in Solution #8.
2a. The AIOTF generates the candidate UE... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.2.4 Periodic Inventory | The periodic inventory may be requested by the AF, so that network can trigger the inventory periodically without the request from the AF directly.
Considering the movement of the Intermediate UE, and the inventory is based on area information, the periodic inventory should be initiated by the CN (i.e. the AIOTF), whic... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.2.5 Command Procedure | The command procedure is initiated by the AF to request one or more specific AIoT devices or a group of AIoT devices in an area to execute the command. The command can be read, write, enable, disable, or execution request from the AF. The command result from the devices may or may not be required.
Editor's note: The co... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.30.3 Impacts on services, entities and interfaces | Editor's note: The services, entities and interfaces are FFS. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.31 Solution #31: fixed type of UE reader solution for Ambient IoT services | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.31.1 Description | This solution resolves Key Issue #3 about the Support of Ambient IoT Services. As we know, 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 intermedi... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.31.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.31.2.1 Reader UE registration procedure with UE reader type info, Location, and AF ID | Figure 6.31.2.1-1: Reader UE registration procedure with UE reader type info, location, and AF ID
1. The UE reader initiates the registration procedure to 5GC:
UE reader initiates registration request with UE reader type - fixed or mobile, Location, and AF ID. These parameters will be used by the core network to choose... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.31.2.2 Ambient IoT service - Network initiated Ambient IoT service procedure with fixed UE reader | Figure 6.31.2.2-1: Network initiated ambient IoT service procedure with fixed UE reader
1. The UE Reader performs the registration procedure, including the fixed or mobile type of UE reader, Location, and AF ID.
2. The third Ambient AF has the store's location information and relevant AIoT serving operator info. The th... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.31.3 Impacts on services, entities, and interfaces | This solution impacts the following entities:
- AMF or New Ambient IoT NF:
- Capability to combine response content from both Base Station Reader readers and fixed UE readers
- Capability to choose fixed UE readers based on UE reader Type, TA, AF ID, and Location
- UE:
- Capability to register UE reader type to 5GC
- U... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.32 Solution #32: AIoT communication for connectivity topology 2 and AIoT data transmission in the UP of PDU Session | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.32.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.32.2 Functional Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.32.2.1 General | This solution focuses on the Topology 2. A UE, which is capable of AIoT transmissions towards AIoT devices, is called "UE AIoT Reader". The UE AIoT Reader indicates its AIoT capability during the registration with the network.
This solution proposes that the AIoT data/information transfer between the AIoT application s... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.32.2.2 Protocol Stack | The Figure 6.32.2.2-1 shows the protocol stack for AIoT communication between the AIoT device and AIoTF. The AIoT data is transmitted over the user plane of a PDU Session established by the UE AIoT Reader.
Figure 6.32.2-1: Protocol Stack for AF Based Solution (over user plane)
The following is applicable:
- App layer: ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.32.3 Procedures | Two procedures are shown in Figure 6.32.3-1 to explain the concept of this solution:
- the Registration procedure of the UE AIoT Reader with the network and the AIoTF; and
- the PDU Session establishment procedure for the transmission of the AIoT data/signalling via the U-plane.
Figure 6.32.3-1: Signalling flow of the ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.32.4 Impacts on existing services, entities and interfaces | The following NFs and interfaces are impacted:
- AIoTF: optionally, a new function on the N6 interface can be introduced.
- UE AIoT Reader: 1) supporting AIoT capabilities to communication with the AIoT devices and 2) capabilities to receive configuration information from the SMF to initiate application layer communica... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33 Solution #33: Solution for different Ambient IoT Device Types | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.1.1 Introduction | RAN has considered three types of AIoT devices (according to TR 38.848 [7]). The capabilities of these devices, vary quite significantly in terms of their baseband capabilities, storage, form factor from read-only devices to devices with writable memory, varying cost, complexity etc. As such it may not be possible to h... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.1.2 Functional Description | The solution for type A AIoT device is based on the following principles.
- The type A AIoT devices are ultra-low complexity devices with ultra-low power consumption for very-low end AIoT applications with limited or no energy storage capability, wherein UL transmission is backscattered, and the solution applies for bo... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.1.3 Reference Architecture | Figure 6.33.1.3-1: Reference Architecture to support Ambient IoT
The figure 6.33.1-3.1 shows the example reference architecture to support AIoT devices (both type A and type B) for Topology 2 wherein the UE (intermediate node) acts as the Reader. The same architecture also applies for Topology 1 (without the UE interme... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.1.4 Protocol Stack | Figure 6.33.1.4-1: Protocol Stack to support Ambient IoT
The figure 6.33.1.4.1 shows the example protocol stack to support AIoT devices (both type A and type B) for Topology 2. The Reader supports the A-Uu air interface with AIoT device. The AIoT C is the optional control protocol between AIoT device and the Reader and... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.2.1 AIoT Service Operation Procedure for Type A AIoT Device | This clause describes the procedure for service operation (inventory, command, etc.) for a type A AIoT device as indicated in Figure 6.33.2.1-1. The procedure in general applies to both Topology 1 and Topology 2 configurations.
Figure 6.33.2.1-1: AIoT Service Operation Procedure for Type A AIoT Device
1. The type A AIo... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.2.2 AIoT Service Operation Procedure for Type B AIoT Device | This clause describes the procedure for service operation (inventory, command, etc.) for a type B AIoT device as indicated in Figure 6.33.2.1-2.
1-2. These are same as in clause 6.33.2.1. The type B AIoT device may have a UICC.
3. The Reader triggers the paging like procedure for the type B AIoT Device. The type B AIoT... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.33.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.34 Solution #34: UE assisted paging for AIoT Devices | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.34.1 Functional Description | This solution applies to Key Issue #2 "Identification, Subscription, Registration and Connection management".
This solution proposes that a UE Reader (i.e. intermediate node) handles paging and communication on behalf of AIoT devices using a network-assigned virtual TMSI (VTMSI). The UE receives the VTMSI when register... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.34.2 Procedures | The figures below describe the procedures (Registration, PDU Session establishment, network triggered Service Request) with enhancements to support AIoT devices paging and communication assistance by an UE.
Figure 6.34.2-1 shows the UE Registration and PDU Session establishment procedures for an UE.
Figure 6.34.2-1: UE... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.34.3 Impacts on existing services, entities, and interfaces | UDM/UDR:
- Stores/Provides: AIoT Assistance Authorization information.
PCF:
- Provisions UE with AIoT Assistance Authorization policy.
AMF:
- Checks for AIoT Assistance Authorization from UDM.
- Allocates and Sends VTMSI to authorized UE (Registration Accept).
- Pages UE using VTMSI.
UE (AIoT Assistant):
- Receives fro... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.35 Solution #35: An compatible format of AIoT device | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.35.1 Description | The solution addresses Key Issue 2.
In RFID domain, EPC has been well used. In AIoT scenario, the AIoT device may be owned by the 3rd party but can be operated by an operator network. So it is possible for a AIoT device without operator allocated device ID before it being operated by any reader in the operator network.... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.35.2 EPC format | The format of the EPC can be referred to GS1 TDS Release 2.1 [10]: "EPC Tag Data Standard". The structure of the EPC guarantees worldwide uniqueness of the EPC across all types of 920 physical objects and applications. The EPC URI is a string having the following form which is referred to clause 6 of GS1 TDS Release 2.... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.35.3 Design AIoT device ID | In this alternative, the AIoT device ID still reuse NAI, i.e. the form of username@realm.
For the realm part, it contains the following information:
- The Scheme present the scheme of the AIoT device ID:
- If the AIoT device ID is mapped by EPC, it is the EPC scheme.
- If the AIoT device ID is 3GPP operator-defined, it... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.35.4 Procedure | The procedure is described below:
1. The reader sends signalling for Inventory to AIoT device.
2. When AIoT device response to the signalling for Inventory, it provides AIoT device ID, the AIoT device ID may be 3GPP allocated ID or the EPC mapped ID.
3. The other steps are not repeated here. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.