hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.9.2 Procedures
| The DO-A procedure can be initiated by the AF to request the activation for one or more DO-A capable AIoT Devices or a group of DO-A capable AIoT Devices in an area to execute the autonomous registration and data transfer.
The DO-A procedure can be also activated based on configuration in the network. In this case, th... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.9.2.1 DO-A procedure for Topology 1
|
Figure 6.9.2.1-1: Device initiated Registration and Data Transfer procedure for Topology 1
1. The AF requests for the AIoT DO-A activation which may include the External Target Area information and/or information about the target AIoT Device(s) to the NEF.
Editor's note: How to handle and coordinate the requests fr... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.9.2.2 DO-A procedure for Topology 2
|
Figure 6.9.2.2-1: Device initiated Registration and Data Transfer procedure for Topology 2
1. During the registration, the UE indicates the support for the UE Reader Capability to the AMF. The AMF checks if the UE is authorized to act as a Reader based on subscription data. The AMF stores the mapping information bet... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.9.3 Impacts on services, entities and interfaces
| AIoT Device:
- Support to initiate the registration request message based on the access parameters broadcasted by the Reader.
- Support to receive the temporary ID to be used for subsequent autonomous message.
Reader (RAN / UE Reader):
- Support to broadcast access parameters for the DO-A capable AIoT Device(s).
-... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10 Solution #10: DO-A Data Delivery and Routing
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10.0 High-level Solution Principles
| The solution is based on the following general principles to support DO-A delivery from DO-A capable AIoT devices:
- The target address(es) of the AIoT device are stored in the AIoT Device Profile data, which are provided in the subscribe request from the AF.
- The DO-A capable AIoT devices sends DO-A data over AIoT ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10.1 Description
| This solution addresses KI#2 and focuses on the following aspects:
- How an AIoT Device sends data to the AIOTF autonomously.
- Support for routing the data received by AIOTF from an AIoT Device to an AF.
This solution assumes the AIoT device has registered towards the network (i.e. the AIOTF) and have the security ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10.2 Procedures
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10.2.1 Subscribe to DO-A Data Delivery
|
Figure 6.10.2.1-1 Subscribe to DO-A Data Delivery
Figure 6.10.2.1-1 depicts how the AF subscribes to the DO-A data delivery:
1. The AF sends Subscribe Request to the NEF for DO-A data delivery with the AF ID, target device information (AIoT Device Permanent IDs or Filtering Information) and target address (i.e. not... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10.2.2 DO-A Data Delivery
|
Figure 6.10.2.2-1 DO-A Data Delivery
Figure 6.10.2.2-1 depicts how DO-A data are delivered from the AIoT device towards the AF:
1. The AIoT Device sends AIoT NAS DO-A Delivery Request to the AIOTF with the Device ID and DO-A data.
For topology 1, the AIoT NAS message is delivered via the RAN reader inside NG-RAN ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.10.3 Impacts on Services, Entities and Interfaces
| The following NFs are impacted:
- AIOTF:
- AIoT NAS layer support for DO-A Data Delivery.
- Notify DO-A data to the target address(es) obtained from AIoT Device Profile Data in ADM.
- Support subscribe request towards the DO-A data delivery.
- Perform AF authorization for the subscribe request. If authorized, the ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.11 Solution #11: DO-A device registration and uplink data transmission
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.11.0 High-level Solution Principles
| The solution is based on the following general principles:
- The DO-A capable AIoT Device performs the active registration procedure towards the AIOTF.
- The NG-RAN selects the AIOTF based on the stored AIOTF information, or AIOTF information contained in the AIoT Device ID, or local configuration.
- ADM is enhanced... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.11.1 Description
| This solution mainly focuses on the DO-A capable device and includes two crucial parts: device-initiated registration procedure and the uplink DO-A data transmission from the Device to the AF. Some of the key procedures are listed below:
1) DO-A capable AIoT Device actively sends the device registration request to the... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.11.2 Procedures
|
Figure 6.11.2-1: DO-A Device registration and Uplink data transmission
0: AIoT Device obtains radio resource for D2R message.
Editor's note: How AIoT Device obtains radio resource for D2R message is FFS and is to be decided by RAN WGs.
1: AIoT Device sends a D2R message to NG-RAN with device registration request, ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.11.3 Impacts on Services, Entities and Interfaces
| AIOTF:
- Determine the target AF for sending the DO-A data from AIoT Device to the AF
- Support registration management of the AIoT Device
- Interaction with last serving AIOTF for Device context retrieval
NG-RAN:
- Determine the target AIOTF to forward the uplink message from AIoT Device
ADM:
- Store the subscr... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12 Solution #12: Enable DO-A traffic with MICO like mechanism
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.1 Description
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.1.1 High-level solution principles
| This solution applies to topology 1.
AIoT device can support inventory and command. In order to help the DO-A capable AIoT device with limited energy storage capability to save power, a DOO (device originated only) mode and DOO mode related Active Time is used.
The AF may request the network to configure a DO-A capab... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.1.2 Definition
| AF routing information: used to select NEF, for example AF ID, FQDN or IP address of the AF.
DO-A data: AIoT data related to the DO-A traffic.
DO-A NAS message: an AIOT NAS message that is sent from the AIoT device and includes the AIoT device ID and DO-A data.
DOO (Device Originated Only) mode: An AIoT device that ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.2 Procedures
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.2.1 Enhanced command procedure to configure AIoT device
|
Figure 6.12.2.1: Enhanced command procedure to configure AIoT device
0. The AIoT device supports inventory and command procedure.
1. The AF sends the Nnef_AIoT_Command message to NEF as specified in the step 1 of clause 6.2.3 TS 23.369 [3] with the following additional clarification:
The Nnef_AIoT_Command message... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.2.2 DO-A procedure
|
Figure 6.12.2.2-1: DO-A Procedure
0. The AIoT device capable of DO-A is configured with DOO mode indication, stores a DOO mode related Active time value, AIOTF ID, AF routing information and the DO-A network resource information using the device configuration procedure. It is assumed that the AIoT device has activat... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.12.3 Impacts on Services, Entities and Interfaces
| AIoT Device:
- Support device configuration procedure.
- Supports DO-A procedure.
- Supports timer;
NG-RAN(including AIoT Reader):
- Support device configuration procedure.
- Supports DO-A procedure.
AIOTF:
- Support device configuration procedure.
- Supports DO-A procedure.
ADM:
- Support AIoT Device profil... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.13 Solution #13: Network Triggered Initial Registration
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.13.0 High-level solution principles
| The key technical principles proposed in this solution are summarized below:
- Network triggers the AIoT Device to perform initial Register using Inventory procedure to trigger un-registered devices to register.
NOTE: Registration due to mobility or periodic registration is assumed to be autonomously done (using the ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.13.1 Description
| This solution proposes to reuse the Inventory procedure and command procedure to support Device registration to the network. This allows re-use of rel-19 security procedures i.e. authentication, privacy protection and command protection.
Key Procedures:
- AF invokes a new network service to register AIoT Device(s). T... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.13.2 Procedure
|
Figure 6.13.2-1: Procedure for network triggered registration
0. The AIoT device profile per AIoT Device is provisioned in the ADM.
1. The AF invokes Nnef_AIoT_Registration Request in service operation request to the NEF. The Request includes same parameters as Nnef_Inventory Request as specified in TS 23.369 [3].
... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.13.3 Impacts on Services, Entities and Interfaces
| NEF:
- Support new Nnef_AIoT_Registration service.
AIoT Device:
- Support Registration procedure including:
1. Verify whether it is registered in the specific network;
2. Receive Registration Accept message; and
3. Use the parameters included in the accept message and respond with a Register Complete message.
AI... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.14 Solution #14: DO-A capable AIoT Device Registration Procedure
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.14.0 High-level solution Principles
| DO-A capable AIoT devices possess the capability to transmit MO signalling and data. Furthermore, the AIoT device actively registers with the core network to notify it of its presence autonomously.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.14.1 Description
| This solution addresses KI#2, specifically concerning the method by which the DO-A capable AIoT device can autonomously notify the network of its presence for Topology 1.
In this solution, it is assumed:
- The AIoT device actively initiates the registration process with the network. The registration types include:
A... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.14.2 Procedures
|
Figure 6.14.2.1: DO-A capable AIoT Device Registration Procedure
0. The DO-A capable AIoT Device's subscription data is provisioned in the ADM.
Editor's note: The subscription data of a DO-A capable AIoT device is FFS.
1. The DO-A capable AIoT Device meets the following trigger conditions, then it will send a NAS ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.14.3 Impacts on Services, Entities and Interfaces
| AIOTF:
- Support Registration and Mobility Management.
NG-RAN:
- Supports the AIOTF selection and transferring NAS messages to and from the AIoT Device.
AIoT Device:
- Support performing the registration procedure.
ADM:
- Support new interface with AIOTF.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.15 Solution #15: Support reliable time-base Data Collection of DO-A AIoT sensor device with network trigger
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.15.0 High-level solution Principles
| This solution addresses KI #2 to support DO-A sensor data collection with network assistance, with the following key principles:
1. The AF starts the time-based (e.g. periodic or at certain time) data collection service from the DO-A sensor device(s) by sending the AIoT command request to NEF, with the assumption that... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.15.1 Description
| One of the key DO-A use cases is time-based (e.g. periodic ) data collection from AIoT sensor. Considering the nature of DO-A IoT device which is still a low energy and low complex device, keeping accurate and network-synchronized clock for periodic data transmission in the AIoT sensor is challenging. Although DO-A dev... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.15.2 Procedures
|
Figure 6.15.2-1: Periodic data collection
1. Step 1 to step 6 of Procedure for Command in clause 6.2.3 of TS 23.369 [3] with additional parameters. AF sends AIoT Command Request to NEF. In includes Device(s) Info, Location (External), AF Transaction ID, Command Type Read, Length, Periodic data collection indication,... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.15.3 Impacts on services, entities and interfaces
| Impacts on existing entities:
AIOTF:
- Receives time-based data collection information (e.g. periodic data collection information) from AF.
AIOTF:
- Add time-based data collection information to the assistance information, such as:
- periodic data collection: periodic data collection indication, interval of each d... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16 Solution #16: AIoT device DOA data detection and collection
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.0 High-level solution Principles
| This solution addresses the DOA traffic enabling aspects of KI#2. The solution proposes the procedures for the AIoT Readers and the network to detect and collect the AIoT device's DOA data. The solution assumes that the AIoT device broadcasts a signal ("Data Ready Indication") when it has DOA data to send. The nearby A... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.1 Description
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.1.1 Device broadcasted "Data Ready Indication"
| When a DOA capable device has data to send, it broadcasts a Data Ready Indication (DRI). The purpose of this broadcast information is to probe whether there is an AIoT Reader that is able to receive its DOA data. The radio resource used for the broadcast may be preconfigured in the device. If the broadcast indication i... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.1.2 Enhanced R19 AIoT Paging and Command procedures for collecting DOA data
| Once the AIoT Reader monitors the DRI broadcast, the Reader may initiate an AIoT Paging procedure to handshake with the device that has data to send and verify the device identifier. The AIoT paging message needs to carry a DOA indication so that only the device(s) that has DOA data to send may respond to the paging. T... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.1.3 Routing of DOA data
| When the AIoT Reader receives the DOA data from the AIoT device, it needs to forward it to the AIOTF which further forwards it to the AF. The determination of the AIOTF may be based on the Reader's configuration that maps a part of device identifier to an AIOTF. For UE Readers, this configuration may also reside in the... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.2 Procedures
|
Figure 6.16.2-1: DOA data detection and collection
1. The AIoT Reader monitors DRI broadcast on the preconfigured radio resource. If the Reader is a UE Reader, it may only monitor the DRI broadcast during the configured time windows which match the DOA data transmission pattern of the AIoT devices that the Reader is... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.16.3 Impacts on Services, Entities and Interfaces
| Editor's note: This clause captures impacts on existing services, entities and interfaces.
The proposed solution has impacts on the following entities:
AIoT Device:
- Support DRI signal generation and broadcast and related radio resource configuration.
- Support new "DOA Indication" in AIoT Paging message.
- Suppo... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.17 Solution #17: Service aspects for DO-A traffic in Ambient IoT networks
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.17.1 High-level solution principles
| The solution proposed in this paper is based on the following principles:
1. A new service type "DO-A support" for enabling DO-A traffic for a certain service within the network is introduced.
2. Network can simultaneously support devices that are capable of DO-A and DT traffic at the same time.
3. A-IoT readers pre... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.17.1 Description
| For supporting DO-A traffic within an Ambient IoT network, an AF should first enable the service for supporting DO-A traffic within the network. This is essential as the AIoT Readers collocated with gNB (topology 1), or UE (topology 2) may need to broadcast certain specific signals for supporting DO-A traffic. These si... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.17.2 Procedures
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.17.2.1 Configuring the network to support DO-A support as a service
| Figure 6.17.2.1-1 illustrates the call flow for enabling DO-A service in a AIoT Network.
Figure 6.17.2.1-1:Procedure for supporting DO-A as a service
The steps involved in the procedure are as follows:
1. The Application Function (AF) invokes Nnef_AIoT_Do-A Support (Service Descriptor, AF ID, [service type], [targ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.17.3 Impacts on Services, Entities and Interfaces
| The following impacts are envisioned on the existing network functions:
- AIOTF:
- For supporting DO-A traffic, AIOTF must support the mechanism to indicate to the Readers to enable any DO-A specific signalling.
- ADM:
- The AIOTF profile data in the ADM must be enhanced to also contain "AIoT Device Traffic Capabil... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18 Solution #18: AIoT Device Registration and data transmission Procedure
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.0 High-level solution Principles
| DO-A capable AIoT Devices have the ability to send MO originating signalling and data. The AIoT Device actively registers to the network to inform the network of its presence autonomously and once the AIoT Device is registered it can actively send data to the network autonomously without triggers from the network. The ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.1 Description
| This solution addresses KI#2 and includes how to enable the AIoT Device to inform the network of its presence autonomously for Topology 1, how to enable the device to perform DO-A data transmission and Inventory and Command Procedures.
It is assumed that the AIoT Device actively initiates the registration process with... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.2 Procedures
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.2.1 Registration Procedure
| The Registration procedure is used by an AIoT Device for Initial Registration or a Mobility Registration Update when it to moves outside of an AIoT Registration Area provided to it.
Figure 6.15.2.1-1: Registration Procedure
1. The AIoT Device sends a D2R message to NG-RAN, including D2R parameters and a NAS Registr... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.2.2 Configuration of MO data routing
| The procedure to configure the routing of uplink traffic from an AIoT Device is show in figure 6.18.2.2-1.
Figure 6.18.2.2-1: DO-A Target AF information configuration Procedure
1. The AF sends an Nnef_DOAconfiguration_Create Request message (AIoT Device information, AF Identifier, validity time) to the NEF. The val... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.2.3 DO-A traffic routing
| The procedure uses the routing information stored in the ADM to route DO-A traffic from an AIoT Device and is shown in figure 6.18.2.3-1.
Figure 6.18.2.3-1: DO-A Data Transmission Procedure
1. The AIoT Device sends D2R message to NG-RAN, including Temporary ID and AIoT UL NAS message (Temporary ID, DO-A Data).
2. ... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.2.4 Inventory Procedures
| The Inventory Procedure in clause 6.2.2 of TS 23.369 [3] is performed with following differences:
- In step 2, if the information about the target AIoT Device(s) has been provided, the NEF determines the corresponding serving AIOTFs by querying the ADM for the serving AIOTF based on the AIoT Device ID and uses that AI... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.2.5 Command Procedures
| The Command Procedure in clause 6.2.3 of TS 23.369 [3] is performed with following differences:
- In step 2, if the information about the target AIoT Device(s) has been provided, the NEF determines the corresponding serving AIOTFs by querying the ADM for the serving AIOTF based on the AIoT Device ID and uses that AIOT... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.18.3 Impacts on Services, Entities and Interfaces
| AIOTF:
- Support Registration and Mobility Management.
- Support DO-A data routing, including retrieval of AF Identifier from ADM.
- Register AIOTF ID into ADM as serving AIOTF of the AIoT Device.
NG-RAN:
- Supports AIOTF selection and transferring NAS messages to and from the AIoT Device.
AIoT Device:
- Support... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.19 Solution #19: AF activates/deactivates the DO-A traffic to the AIoT device
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.19.0 High-level solution Principles
| This solution addresses KI #2. It includes DO-A parameters configuration for DO-A traffic, the procedure of the AF initiates or stops the AIoT device reporting the DO-A data (e.g. sensing data) via the Activation/Deactivation Command.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.19.1 Description
| This solution is applicable to both the Direct Connectivity and the Indirect Connectivity architectures as defined in TS 23.369 [3].
The principles of this solution are as follows:
- The AIoT device registration: For an Ambient IoT devices of type 2b/c supporting DO-A traffic, the registration-like procedure should b... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.19.2 Procedures
| The procedure is shown in Figure 6.19.2-1. It includes the AIoT Service Request from AF to configure the parameters of the DO-A traffic, Activation/Deactivation Command request from AF to initiate or stop the DO-A traffic.
Figure 6.19.2-1: Procedure for DO-A traffic configuration and AF initiates/stops DO-A traffic
... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 6.19.3 Impacts on services, entities and interfaces
| Impacts on existing entities:
AIOTF:
- Receives DO-A Configuration Parameters for DO-A data reporting from AF.
- Performs Inventory procedure and sends AIoT Command Request with DO-A Configuration Parameters to the AIoT device.
- Receives DO-A traffic Activation/Deactivation Command request from AF and sends activa... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7 Interim agreements
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1 Agreed Principles
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1.1 Agreed Principles for KI#1
| 'Figure 7.1.1-1 depicts the AIoT System Architecture for Topology 2.
Figure 7.1.1-1: AIoT System Architecture for Topology 2
Figure 7.1.1-2 depicts the AIoT system architecture, using the reference point representation.
Figure 7.1.1-2: AIoT System Architecture for Topology 2 in reference point representation
Me... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1.2 Agreed Principles for KI#2
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1.2.1 DO-A capable Device Registration for topology 1
| NOTE 1: Coordination with RAN on support DO-A capable Device Registration will be in the normative work
General
A. The registration procedure is used by the DO-A capable AIoT Device to inform the network of its presence and get authenticated/authorized by the network. After successful registration, the AIoT Device an... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1.2.2 DO-A data transfer aspects
| The following principles have been agreed for DO-A data transfer aspects in KI#2:
- DO-A capable AIoT Devices initiates DO-A data transfer, triggered by the conditions which can be stored in local configuration or device implementation. The local configuration can be configured by the AF using the AIoT command procedu... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1.2.3 Support of Inventory and Command for DO-A capable Device
| NOTE 1: How to support the Inventory procedure for the DO-A capable Device will be determined in the normative phase.
If the DO-A capable Device has already performed the AIoT registration as specified in clause 7.1.2.1, the Command Procedure for DO-A Capable device is performed as following:
- In step 1, the AF make... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 7.1.2.4 Support of Power Saving for DO-A Capable AIoT Devices
| To optimize power consumption for AIoT Devices, the principles of MICO-like mode can be supported to enable AIoT Device originated traffic only (i.e. the AIoT Device does not need to monitor paging). The network can negotiate power-saving parameters with the AIoT Device during the Registration procedure.
NOTE 1: Wheth... |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8 Conclusions
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8.1 Conclusions for KI#1
| The agreed principles for KI#1 in clause 7.1.1 are used as basis for the normative work.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8.2 Conclusions for KI#2
| |
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8.2.1 DO-A capable Device Registration for topology 1
| The agreed principles in clause 7.1.2.1 to support DO-A capable Device Registration for topology 1 are used as basis for the normative work.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8.2.2 DO-A data transfer aspects
| The agreed principles in clause 7.1.2.2 for DO-A data transfer aspects in KI#2 are used as a basis for the normative work.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8.2.3 Support of Inventory and Command for DO-A capable Device
| The agreed principles for KI#2 in clause 7.1.2.3 to support Inventory and Command for DO-A capable Device are used as basis for the normative work.
|
3b819e7ca101098dd228a1012035e8ae | 23.700-30 | 8.2.4 Support of DO-A capable AIoT Devices in topology 2
| NOTE 1: TR conclusions from Key Issue #1 and TR conclusions to support of DO-A capable AIoT Devices in topology 1 will be the basis for support of DO-A capable AIoT Devices in topology 2.
NOTE 2: When to start the work in the normative phase will depend on the decision of the checkpoint in TSG SA plenary in September ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 1 Scope
| The present document studies system architecture for 6G mobile networks for improvement of existing services and support of new services, to meet the 6G system requirements as captured by TS 22.abc [x].
Editor's note: The above reference should be replaced with a reference to normative specification, when available. ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 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.
-... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 3 Definitions of terms, symbols and abbreviations
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 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].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify abstract r... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 3.3 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].
Abbreviation format (EW)
<ABBREVIATION> <Expansion>
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 4 Architectural Assumptions and Requirements
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 4.1 Architectural Assumptions
| Editor's note: This clause documents the common architecture assumptions identified for the study.
The following is assumed for 6GS architecture:
1. The framework of SBA specified for 5GC is assumed as a starting point for discussion.
2. This study assumes that control and user plane of the 6G RAN connects to a sing... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 4.2 Architectural Requirements
| The followings are architectural requirements of 6G System:
The 6G System shall:
1. Support roaming.
2. Support multi-vendor interoperable interfaces.
The 6G System should:
3. Follow design principles such as: utilization of cloud nativeness, improve sustainability and energy efficiency, robustness and resiliency.... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 5 Key Issues
| Editor's note: This clause identifies key issues to be addressed.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 5.1 Key Issue #1: Study the support for control signalling for 6G System
| Key Issue #1.1
1. Study the support for control signalling for 6G System, including at least the following:
a) Whether and how to enable the introduction of a new non-access stratum functionality with minimal or no impact to other non-access stratum functionalities.
NOTE 1: It is assumed that this key issue KI#1.1 b... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 5.2 Key Issue #2: SBA framework
| The following is key issue for SBA related work task.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 1 Study whether and how to optimize NF/NF service registration, discovery and selection for efficient message forwarding compared with 5G.
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 2 Study whether and how to improve NF/NF service resiliency, scalability, efficiency and load balancing, compared with 5G.
| NOTE: This WT covers generic aspects for SBA framework. The study of other WTs can also result in potential enhancements on the SBA framework and will be studied as part of respective WTs.
A.1.2.2 Network Slicing
The scope of the network slicing work task includes:
1. Study the overall design and functionalities of ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 5.3 Key Issue #3: Support of Network Slicing in the 6G system
| This Key Issue aims to study the support of Network Slicing in the 6G system, including the following aspects:
1. Study the overall design and functionalities of the network slicing in 6G assuming the network slicing in 5GS as starting point for discussions including the following:
a) Identify and address any areas o... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 5.4 Key Issue #4: User Plane Architecture
| In order to support 6G user plane for a diverse set of applications and traffic patterns, the following are studied taking the 5GS user plane framework as a starting point for discussion:
1. Whether and how to enhance CP-UP functional split and interaction for better multi-vendor interoperability.
2. Whether and how ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 5.5 Key Issue #5: QoS Framework for 6G
| This key issue is based on the WT#1.2 on the QoS Framework for 6G. This KI includes following aspects:
1. Investigate whether and what new functionality in 6G QoS framework is required considering, the emerging new traffic characteristics and application needs, e.g. AI/ML application traffic.
NOTE 1: Which working gr... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.