hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.8.3 Impacts on Services, Entities and Interfaces
| AIOTF:
- Handle the AIoT data of AIoT Devices.
- Interact with the ADM to store the AIoT Device information.
- Store the subscription information.
NG-RAN:
- Select the AIOTF serving the AIoT Device.
- Route the messages between the AIoT Device and the AIOTF.
ADM:
- Store the AIoT Device information.
- Optionally store the subscription information.
AIoT Device:
- Send DO-A initiating messages.
- Send DO-A data transfer messages.
NEF:
- Route the messages between the AF and the AIOTF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.9 Solution #9: Autonomous registration and data transfer from AIoT Device
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.9.0 High-level solution Principles
| The following principles apply:
- The Reader broadcasts system information that defines contention-based uplink resources for initial access of AIoT Device.
- An AIoT Device, upon power-on or sensing an event to report, uses the broadcasted information to autonomously register and once registered to the network, it can transmit data to the AF via the network.
- The AIOTF is enhanced to support the AF request for the DO-A activation, handle registration and data transfer request from the DO-A capable AIoT Device forwarded by the Reader, authenticate and authorize the request, create device context, respond to the AIoT Device with the assigned temporary ID.
Editor's note: The need for the request from AIOTF to the NG-RAN for broadcasting access parameters is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.9.1 Description
| This solution addresses Key Issues #2 by defining the procedure for the DO-A capable AIoT Device applicable to both Topology 1 (using RAN Readers) and Topology 2 (using UE Readers). It enables a DO-A capable AIoT Device to trigger its own registration with the network to autonomously inform the network of its presence without a prior network command and to send data to the designated AF based on the AF requested DO-A activation.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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, the AIOTF is configured with information to select NG-RAN node(s) and optionally Readers and send DO-A activation request.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 from multiple AFs is FFS.
2. The NEF selects the AIOTF(s) as described in clause 5.3.1 of TS 23.369 [3] and sends the AIoT DO-A activation request from the AF to the selected AIOTF(s).
3. The AIOTF selects NG-RAN node(s) and optionally RAN readers based on the configured NG-RAN node selection information. The AIOTF may also consider the Target Area information and/or information about the target AIoT Device(s) if received in step 1 and the stored last known RAN Reader information if available e.g. by means of prior Inventory procedure.
4. The AIOTF sends the AIoT DO-A activation response to the AF via NEF.
5. The AIOTF sends the DO-A activation request to each selected NG-RAN node, either directly or through the selected AMF which may include the Requested Service Area Information and/or the AIoT Identification Information.
Editor's note: The detailed parameters to be included in the DO-A activation request is FFS.
6. The RAN Reader periodically broadcasts access parameters related to Random Access for AIoT Device for autonomous transmissions based on the DO-A activation request from the AIOTF.
NOTE 1: The mechanism for broadcasting access parameters needs coordination with RAN WGs.
7. The AIoT Device listens to access parameters from the RAN Reader and performs Random Access to establish the AS connection with the RAN Reader.
8. The AIoT Device transmits the AIoT Registration Request message including the AIoT Device Permanent Identifier. The RAN Reader receives the request and forwards the AIoT Registration Request to the AIOTF directly or via an AMF.
Editor's note: Whether and how the privacy protection for the AIoT Device Permanent Identifier applies is FFS.
9. The AIOTF validates the AIoT Registration Request message with DO-A capability of the AIoT Device and the target AF information in the AIoT Device Profile Data provisioned, the Target Area information and/or information about the target AIoT Device(s) configured or received in step 1.
If validation fails, the AIOTF issues failure response to the AIoT Device and the rest of the procedure is not performed.
Upon successful, the AIOTF updates the AIoT Device Profile Data in the ADM with the Last known AIOTF information.
The AIOTF retrieves the AIoT Device Temporary ID from the ADM, associating it with the last known Reader and the target AF and stores the mapping between the RAN Reader ID, AIoT Device Temporary ID and the AF ID in the AIoT Device context.
NOTE 2: The security aspects for authentication, authorization and the use of AIoT Device Temporary ID needs coordination with SA WG3.
10. The AIOTF sends an AIoT Registration Accept message back to the device via the RAN Reader. The message contains the assigned AIoT Device Temporary ID for the AIoT Device.
The AIoT Device receives the AIoT Registration Accept message and uses the AIoT Device Temporary ID for subsequent communication.
11. The AIoT Device sends the event-driven or periodic AIoT Data Transfer Request message including the assigned AIoT Device Temporary ID.
The AIOTF validates the request using the AIoT Device Profile and sends the message to the target AF found in the AIoT Device context directly or via NEF. The AIOTF sends the AIoT Data Transfer Response message to the AIoT Device via the RAN Reader including a new AIoT Device Temporary ID.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 between candidate UE Reader(s) and the NG-RAN in the local context.
2. 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) together with an indication for the use of the UE Reader to the NEF.
Editor's note: How to coordinate and handle requests from multiple AFs is FFS.
3. The NEF selects the AIOTF(s) as described in clause 5.3.1 of TS 23.369 [3] and sends the AIoT DO-A activation request from the AF to the selected AIOTF(s).
4. The AIOTF selects the AMF considering the Target Area information if received in step 2 or based on local configuration.
The AIOTF, based on the indication for the use of the UE Reader in the request or based on local configuration to select UE reader(s), retrieves/subscribes to the AMF to obtain the available UE Reader(s) for the selected NG-RAN and selects UE Reader(s). The AIOTF may also consider the stored last known UE Reader information if available e.g. by means of prior Inventory procedure.
5. The AIOTF sends the AIoT DO-A activation response to the AF via NEF.
6. The AIOTF sends the DO-A activation request to the selected AMF including the Requested Service Area Information and/or the AIoT Identification Information together with the authorized UE reader information (e.g. a list of RAN UE NGAP ID(s)).
Editor's note: The detailed parameters to be included in the DO-A activation request is FFS.
Editor's note: How the AIOTF gets the RAN UE NGAP ID(s) is FFS.
The AMF selects serving NG-RAN node corresponds to the UE Reader selected by the AIOTF.
NOTE 1: The aspects of NG-RAN selection and UE Reader selection depends on the outcome of KI#1 study.
7. The NG-RAN provides the authorized UE Reader with the access parameters related to Random Access based on the DO-A activation request from the AIOTF, which the UE Reader then periodically broadcasts access parameters related to Random Access for AIoT Device for autonomous transmissions.
NOTE 2: The mechanism for broadcasting access parameters needs coordination with RAN WGs.
8. The AIoT Device listens to access parameters from the UE Reader and performs Random Access to establish the AS connection with the UE Reader.
9. The AIoT Device transmits the AIoT Registration Request message including the AIoT Device Permanent Identifier to the UE Reader. The UE Reader receives the request and forwards the AIoT Registration Request to the NG-RAN and the NG-RAN, aware of which AIOTF the message from UE Reader is destined by step 6, sends the received request to the AIOTF via an AMF.
Editor's note: Whether and how the privacy protection for the AIoT Device Permanent Identifier applies is FFS.
10. The AIOTF validates the AIoT Registration Request message with DO-A capability of the AIoT Device and the target AF information in the AIoT Device Profile Data provisioned, the Target Area information and/or information about the target AIoT Device(s) configured or received in step 2.
If validation fails, the AIOTF issues failure response to the AIoT Device and the rest of the procedure is not performed.
Upon successful, the AIOTF updates the AIoT Device Profile Data in the ADM with the Last known AIOTF information.
The AIOTF retrieves the AIoT Device Temporary ID from the ADM, associating it with the last known UE Reader and the target AF and stores the mapping between the UE Reader ID, AIoT Device Temporary ID and the AF ID in the AIoT Device context.
NOTE 3: The security aspects for authentication, authorization and the use of AIoT Device Temporary ID needs coordination with SA WG3.
11. The AIOTF sends an AIoT Registration Accept message back to the AIoT Device via the AMF, NG-RAN and the UE Reader. The message contains the assigned AIoT Device Temporary ID for the AIoT Device.
The AIoT Device receives the AIoT Registration Accept message and uses the AIoT Device Temporary ID for subsequent communication.
12. The AIoT Device sends the event-driven or periodic AIoT Data Transfer Request message including the assigned AIoT Device Temporary ID.
The AIOTF validates the request using the AIoT Device Profile and sends the message to the target AF found in the AIoT Device context directly or via NEF. The AIOTF sends the AIoT Data Transfer Response message to the AIoT Device via the UE Reader including a new AIoT Device Temporary ID.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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).
- Support to receives AIoT Device initiated registration and data transfer messages and forwarding it to the AIOTF.
AIOTF:
- Support procedures for handling the AF request for the DO-A activation and DO-A capable AIoT Device initiated registration and data transfer.
- Support to validate requests from DO-A capable AIoT Device, context creation, authentication and authorization, temporary ID assignment.
- Support to route the message between the DO-A capable AIoT Device and the AF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.10 Solution #10: DO-A Data Delivery and Routing
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 NAS between the AIoT devices and the AIOTF.
- The AIOTF forwards the DO-A data to the target AF address(es) obtained from AIoT Device Profile data.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 contexts established between the AIoT devices and the AIOTF.
The AIOTF updates its supported domain information or AIoT Device Permanent ID ranges in the NF Profile to the NRF. The NRF supports the AIOTF discovery based on target device information.
The AF subscribes to the DO-A Data Delivery by sending a Subscribe Request to the AIOTF (optionally via the NEF). After receiving the Subscribe Request to the DO-A Data Delivery, the AIOTF performs AF authorization by checking the AF authorization data. If the AF request is authorized, the AIOTF updates the target address(es) provided in the Subscribe Request into the AIoT Device Profile Data in ADM.
The DO-A capable AIoT devices sends DO-A data over AIoT NAS between the AIoT devices and the AIOTF. For example, the AIoT Device sends NAS DO-A Delivery Request to the AIOTF containing the AIoT Device ID and DO-A data. The AIOTF acknowledges the AIoT Device by sending NAS DO-A Delivery Response. The NAS DO-A Delivery Request and DO-A Delivery Response are security protected.
NOTE: The form of AIoT Device ID and the security protection of the NAS DO-A Delivery Request/Response are to be addressed by SA WG3.
The AIOTF obtains the target address(es) from the AIoT Device Profile Data in ADM and forwards the DO-A data to the target address(es) together with the AIoT Device Permanent ID.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.10.2 Procedures
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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. notification endpoint of the AF). For AFs in trusted domain, the AF can send Subscribe Request to the AIOTF directly without involving the NEF.
2. The NEF discovers the AIOTF by providing target device information to the NRF or based on local configuration. The NEF sends the Subscribe Request to the AIOTF for DO-A data delivery with the AF ID, target device information and target address (i.e. notification endpoint of the NEF).
3. The AIOTF authorizes the AF request to check whether the AF is allowed to subscribe to DO-A delivery, based on the AF authorization data stored in the ADM.
4. If authorized, the AIOTF updates AIoT Device Profile data with the target address for the target devices. If the target device information from the AF is Filtering Information, the AIOTF needs to update the AIoT device profile data for each device in the group. Alternatively, the AIOTF may send the Filtering Information to the ADM and the ADM is responsible for the updating for each device in the group.
The target address is the notification endpoint of the NEF or the notification endpoint of the AF, depends on which NF sends the Subscribe Request.
5. The AIOTF sends Subscribe Response towards the NEF indicating the result of the subscribe. In case of failure, failure cause is included. In case of succeed, subscription correlation ID is included.
6. The NEF sends Subscribe Response to the AF indicating the result of the subscribe. In the case of failure, failure cause is included. In the case of success, subscription correlation ID is included.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 node. The NG-RAN node delivers the NAS message to the AIOTF directly or via the AMF.
For topology 2, the AIoT NAS message is delivered via the UE reader. The UE reader delivers the message to the NG-RAN node and the NG-RAN node delivers the NAS message to the AIOTF via the AMF.
NOTE 1: The details of AIoT Device ID and the security protection of the NAS DO-A Delivery Request/Response are to be addressed by SA3.
NOTE 2: The NG-RAN and the AMF are assumed to route the AIoT NAS DO-A Delivery Request to the AIOTF which holds the AIoT device contexts in the Registration Procedure.
Editor's note: If the request is routed to a new AIOTF, how the new AIOTF fetches the AIoT device contexts from the old AIOTF is FFS.
2. The AIOTF authenticates the AIoT device and sends the NAS DO-A Delivery Response to the AIoT Device. The result is included in the response message. In the case of failure, the failure cause is included.
NOTE 3: The authentication is to be addressed by SA3.
3. The AIOTF gets the target address(es) of the AIoT device from the AIoT Device Profile data. For each target address, step 4 to step 7 are executed individually.
4. The AIOTF sends Notify message to the NEF with the AIoT Device Permanent ID and DO-A data, if the target address is the notification endpoint of the NEF. If the target address is the notification endpoint of the AF, the AIOTF sends Notify Request to the AF directly without involving the NEF.
5. The NEF sends Notify message to the AF with the AIoT Device Permanent ID and DO-A data.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 AIOTF update the AIoT Device Profile data to include the target address provided in the subscribe request.
- ADM:
- Enhance AF authorization data for the subscribe request towards DO-A data delivery.
- Enhance AIoT Device Profile data for the target address(es).
- NEF:
- Support subscribe request towards the DO-A data delivery.
- Notify DO-A data to the AF.
- NRF:
- Support domain information or AIoT Device Permanent ID ranges in the NF Profile of the AIOTF.
- Support AIOTF discovery based on target device information.
- AIoT Device:
- AIoT NAS layer support for DO-A Data Delivery.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.11 Solution #11: DO-A device registration and uplink data transmission
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 with the allowed/subscribed AF information, which is used by the AIOTF to determine the target AF for the uplink data transmission from DO-A capable device.
- AIOTF can retrieve the AIoT Device context from the last serving AIOTF that further includes the service-related information.
It addresses the KI#2.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 network, that includes the Device ID, security parameters, registration type.
- Registration type: Similar to UE, AIoT Device can indicate to the network about its registration type, e.g. periodic registration, initial registration, mobility registration. Alternatively, the AIOTF or the NG-RAN/RAN reader can determine the registration type for the AIoT device based on the locally stored device context.
2) The AIOTF selection at the NG-RAN can be based on different options:
- NG-RAN selects the AIOTF based on OAM local configuration.
- NG-RAN selects the AIOTF based on locally stored AIOTF information, e.g. from the past procedures as device context.
- NG-RAN selects the AIOTF based on the Device ID, e.g. AIOTF ID included in the temporary Device ID.
3) The Routing from AIOTF to the AF can be based on two different options:
- AIOTF checks the information in the ADM that further includes the subscribed/allowed AF information (e.g. AF ID).
- AIoT Device sends the AF ID to the AIOTF.
4) Context management of the AIoT Device among AIOTF and ADM:
- AIOTF stores the device registration information that contains registration area and registration status and may also store it at ADM.
- AIOTF retrieves the device context from the last serving AIOTF, that including the security parameters, device last serving reader and service-related information (a.k.a. service context). The service context includes the requested AF ID, transaction ID, target area information and other service specific information, e.g. assistance information for inventory and command. The service context can be used by the AIOTF to autonomously initiate the service towards the AIoT Device if it just moves within its serving area, without further receiving the service request from the AF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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, that includes the Device ID, registration type (e.g. periodic registration, mobility registration, initial registration) and security parameters.
Editor's note: The details of the AIoT Device ID that is used in the registration request is FFS.
The trigger for the AIoT Device performing registration towards the network can be e.g. when device has data pending to report, or when periodic registration is needed (either triggered by device or by the Reader or AIOTF performing periodic inventory), or when mobility registration condition is met (e.g. based on the registration area).
Editor's note: The details for triggering the mobility registration of AIoT Device is FFS.
2: NG-RAN selects the AIOTF based on local configuration by OAM, or by checking the AIOTF information contained in the Device ID (e.g. temporary ID), or based on the locally stored AIOTF information from the past procedures associated with the AIoT Device, e.g. device context that contains the serving AIOTF information.
Editor's note: Whether the NG-RAN has the device context that contains the AIOTF information is FFS.
NOTE 1: The temporary ID design needs to be addressed by the SA WG3.
3: NG-RAN sends the registration request to the selected AIOTF, either directly, or via the AMF. If via the AMF, the AIOTF ID is also included.
4: Optionally, The AIOTF can retrieve the device context from the last serving AIOTF based on the last serving AIOTF information contained in the Temporary Device ID, or received from ADM. The retrieved device context can contain the security parameters, last serving reader information of the Device, service-related information (a.k.a. service context). The service context can include the AF ID (that sent the service request for the device before device moves to the serving area of the current AIOTF), transaction ID, target area information and other service specific information, e.g. assistance information for inventory and command.
5: AIOTF performs the verification of the AIoT Devices, checks whether the data transmission from the device is allowed and stores/updates the device profile information in the ADM, e.g. updating the serving AIOTF information for the AIoT Device. The AIOTF will store the device registration information either locally, or at the ADM, that includes the registration status (registered) and the device registration area.
Editor's note: Details of authentication procedures will be determined by SA3.
6: The ADM informs the old/last serving AIOTF (AIOTF2 in the Figure) with device ID that it is no longer the serving AIOTF for the AIoT Device and the device context can be released if any.
7: AIOTF sends the device registration response message to the NG-RAN and AIoT Device, either directly, or indirectly (via AMF). It contains the Device ID (can be a new temporary ID), registration accept/reject (with a cause and skip all the following messages), registration area for the device.
8: After receiving the registration response (that may include the data transmission accept indication), AIoT Device sends the DO-A message to the NG-RAN/RAN reader, that includes the Device ID, DO-A data, expected D2R message size (sent to RAN reader /NG-RAN for assistance of radio resource allocation), AF ID (optional), where the DO-A data is encrypted in the AIOT NAS message between the AIoT Device and AIOTF.
NOTE 2: The expected D2R message is sent from AIoT Device to the NG-RAN/RAN reader and can happen before the transmission of actual DO-A data and depends on RAN WG2 discussion.
Editor's note: Whether the AF ID can be provided by the AIoT Device to the network is FFS.
9: After selecting the AIOTF (as described in step 2), NG-RAN sends the DO-A message that contains the Device ID, reader ID, DO-A data, , target AF information (optional) and AIOTF ID (if AMF in between).
10: If no AF ID is explicitly sent by the AIoT Device, AIOTF can check the subscribed/allowed AF information from the ADM using Device ID as the key. It is assumed that the ADM is enhanced with the allowed/subscribed AF information, meaning it can receive the data from the DO-A capable device. The allowed/subscribed AF information is pre-configured in the ADM based on the SLA between the MNO and the 3rd party AF.
11: AIOTF sends the DO-A data, Device ID and AF information to the NEF.
Editor's note: The determination of NEF for routing the DO-A data from AIOTF to the AF is FFS.
12: The NEF forwards the AIoT Device ID, DO-A Data to the AF based on the AF information sent by the AIOTF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 subscribed/allowed AF information for the AIoT Device data report
AIoT Device:
- Performs the active registration procedure towards the network
- Sends the DO-A data to the AF via the network
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.12 Solution #12: Enable DO-A traffic with MICO like mechanism
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.12.1 Description
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 capable AIoT device to use the DOO mode and DOO mode related Active Time using enhanced command procedure with a new Command Type: Configure.
During the enhanced command procedure, the device could be configured to use the DOO mode and a DOO mode related Active Time value that is used to indicate the duration during which the device can send uplink AIoT traffic and receive the downlink AIoT traffic. During the enhanced command procedure the AIoTF ID and the AF routing information are sent from the AIoTF to the device to route the DO-A NAS message and DO-A data.
A timer corresponding to the DOO mode related Active Time value is started or restarted by the AIoT device when the uplink AIoT traffic is sent out from the device. After the timer expires the DOO mode is activated in the device. The DOO mode is deactivated when there is DO-A data to be sent out from the device. A counterpart timer is used in AIoTF.
NOTE: The AIoT devices configured with DOO mode are assumed not applicable for Inventory service from AF perspective.
Editor's note: Timer for the DOO mode related Active Time duration in this solution is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 has activated the DOO mode does not need to receive downlink AIoT traffic.
DOO mode related Active Time: An AIoT device that is in DOO mode related Active Time duration is able to receive downlink AIoT traffic and send uplink AIoT traffic.
NOTE: The feasibility of using timer in AIoT device depends on the RAN WGs.
downlink AIoT traffic: includes paging message related to the inventory procedure and NAS Command Request message.
uplink AIoT traffic: includes AIOT NAS message that responds to the paging message related to the inventory procedure, NAS Command Response message and DO-A NAS message.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.12.2 Procedures
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 additionally includes: a DO-A service indicator, a DOO mode indication and a DOO mode related Active time value. The DO-A service indicator is used to indicate that the AIoT device related with the device ID can initiate DO-A service. The DOO mode indication indicates the AF's preference for DOO mode for the AIoT device. The DOO mode related Active time value indicates how long the DOO mode related Active Time duration is.
The Command Type is set to Configure to request to negotiate and configure the DOO information (i.e. the DOO mode and the DOO mode related Active time value) for the AIoT device.
The NEF selects the AIOTF(s) as described in TS 23.369 [3].
The AIOTF authorize the AF, selects the AIoT reader(s) and response to the AF as described in TS 23.369 [3].
The AIOTF store the DO-A service indicator in the ADM, determine and store the DOO mode indication, the DOO mode related Active time value in the AIoT device profile related with device ID in the ADM based on the request from the AF, local configuration and the policy of the network.
2. Step 7 of Command Procedure specified in clause 6.2.3 of TS 23.369 [3].
3. Step 8 of Command Procedure in clause 6.2.3 of TS 23.369 [3] with the following additional clarification:
If the inventory reports include the device ID that corresponds to the device ID received by the AIOTF in step 1, the AIOTF sends Command Request message to the corresponding reader and the Command Request message additionally includes a DO-A service indication that is used to assist NG-RAN to provide DO-A service network resource information to the AIoT device.
The NAS Command Request includes a DOO mode indication, a DOO mode related Active time value, the AF routing information and the AIOTF ID.
4. Step 9 of Command Procedure in clause 6.2.3 of TS 23.369 [3] with the following additional clarification:
If the DO-A service indication is received in step 3, the AIoT Reader provides DO-A network resource information to the device in the AS R2D message.
5. After receiving the AS R2D message and the NAS Command Request in step 4:
The device stores DOO mode indication, the DOO mode related Active time value, the AIOTF ID and the AF routing information and the DO-A network resource information; and
The AIoT device shall set a timer corresponding to the DOO mode related Active Time value received.
6. Step 10 of Command Procedure in clause 6.2.3 of TS 23.369 [3] with the following clarification:
After the NAS Command Response is sent out, the AIoT device shall start the timer corresponding to the DOO mode related Active Time value if the DOO mode related Active Time value is not zero and the device stores DOO mode indication. If the Time value is zero and the device stores DOO mode indication the AIoT device activate DOO mode immediately.
When the timer expires (i.e. reaches the DOO mode related Active Time value) the AIoT device activates DOO mode and is not available for receiving downlink AIoT traffic.
7. Step 11~13 of Command procedure in clause 6.2.3 of TS 23.369 [3] with the following clarification:
After the NAS Command Response is received, the AIOTF shall start the timer corresponding to the DOO mode related Active Time value if the DOO mode related Active Time value is not zero and the device is indicated the DOO mode indication. If the Time value is zero and the device stores DOO mode indication the AIOTF can deduce that AIoT device has activated DOO mode. When the timer expires the AIOTF can deduce that the AIoT device has activated DOO mode and is not available for receiving downlink AIoT traffic.
Editor's note: The impact of the DOO mode to the AS layer in AIoT device is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 activated DOO mode.
1. When there is DO-A data needed to be sent to the network, the AIoT device deactivate the DOO mode and sends AS D2R message (AIOTF ID, DO-A NAS message) to the NG-RAN based on the stored DO-A network resource information. The AIOTF ID is used by NG-RAN to select AIOTF. DO-A NAS message includes AF routing information, device ID and DO-A data.
After the DO-A NAS message is sent out:
- if the device stores DOO mode indication and if the stored DOO mode related Active Time value is not zero, the AIoT device shall start the timer corresponding to the DOO mode related Active Time value;
- if the device stores DOO mode indication and if the stored Time value is zero, the AIoT device shall activate the DOO mode immediately.
2. NG-RAN selects the AIOTF based on the AIOTF ID received in step 1.
3. NG-RAN forward the DO-A NAS message to the selected AIOTF together with the reader ID and RAN AIoT Device NGAP ID.
4. The AIOTF authenticates the device corresponding to the device ID carried in the DO-A NAS message.
If the device is authenticated successfully:
- The AIOTF shall start the timer corresponding to the DOO mode related Active Time value if the DOO mode related Active Time value is not zero and the device is indicated to use DOO mode; and
- The AIOTF selects the NEF based on the AF routing information carried in the DO-A NAS message.
If the device failed the authentication, the DO-A NAS message is discarded by the AIoTF.
5. The AIOTF send the DO-A data, the device ID and AF routing information received in step 3 to the NEF. And NEF forward the DO-A data and device ID to the AF based on the AF routing information.
6. After receiving the DO-A data the AF may subsequently request AIoT service (e.g. Nnef_AIoT_Inventory, Nnef_AIoT_Command) for the corresponding device. The AIoT service request is sent to the AIOTF.
7. If the device ID related timer corresponding to the DOO mode related Active Time value is running, the AIOTF determines the device could receive the DL AIoT traffic and proceed with the AIoT service. If the device ID related timer expires or is not running and the device has been indicated to use the DOO mode, the AIOTF considers the device has activated the DOO mode and is not able to receive downlink AIoT traffic and may reject the AIoT service and then the step 8~9 is skipped.
8. The DL AIoT traffic is transferred to the device as described in the inventory and command procedure.
9. When the timer expires (i.e. reaches the DOO mode related Active Time value) the AIoT device activates DOO mode.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 profile including: DO-A service indicator, DOO mode indication, the DOO mode related Active time value.
Editor's note: Other impacts (e.g. impacts on NEF, etc.) is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.13 Solution #13: Network Triggered Initial Registration
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 DO-A procedure) by the AIoT Device after the AIoT Device has performed initial registration.
- Reuse of Rel-19 Inventory and Command procedure to support registration of an AIoT Device as specified in TS 23.369 [3]. A Registration Indicator is included in the Inventory Request and paging message.
- Reuse of Rel-19 security solution for authentication and command protection as specified in TS 33.369 [11].
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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). The AF may include e.g. External Target Area information to aid the network to select AIOTF and where perform Inventory to trigger initial registration for specific AIoT Devices.
- The AIOTF can trigger the initial registration without an AF service invocation. In this case the AIOTF determines the periodicity and selection of NG-RAN(s) based on AIOTF implementation. The AIOTF will not include the AIoT Identification Information in the Inventory Request message to trigger all AIoT Devices that are not registered.to respond.
- A Registration indication is included in the Inventory Request to restrict the responses to only from AIoT Devices that are not registered to the network.
- The AIOTF uses the Inventory procedure to trigger the AIoT Device to check if it is registered to the network. The PLMN ID or NID must be provided in the paging message (see the procedure below for more details).
- Un-registered AIoT Device(s) includes an indication to register in the Inventory Response message. As specified in rel-19 the Inventory Response message includes protected information that the network uses to derive the AIoT Device Permanent Identifier and to authenticate the AIoT Device.
- The AIOTF sends a Command (based on rel-19 functionality) with a Registration Accept message. This message includes the necessary information for the device to enable DO-A transmission. The details of the parameters and information will be identified in solutions for the DO-A transmission and security aspects specified by SA3 for DO-A transmissions.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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].
2. The NEF may further authorize the AF request, selects AIOTF and invokes the Naiotf_AIoT_Registration service operation towards each of the selected AIOTF(s). The Request includes same parameters as Naiotf_Inventory Request as specified in TS 23.369 [3].
3. The AIOTF receives the Naiotf_AIoT_Registration request and checks the parameters included in the request. The AIOTF may perform authorization of the AF as specified in clause 5.6 of TS 23.369 [3]. The AIOTF prepares the Inventory Request to be sent to the NG-RAN. The AIoT Identification Information to be included in the paging message includes the PLMN ID or NID, i.e. the Filtering Information includes the PLMN ID or NID part.
Editor's note: It is FFS whether and how to provide PLMN ID or NID when single AIoT Device is paged with a Temporary ID.
4. AIOTF sends the AIoT Registration Service Response to the NEF containing the accept or reject result for the AIoT service operation request based on step 3.
5. NEF sends the AIoT service operation response to the AF, containing the accept or reject result for the AIoT service operation request as specified in clause 8.3 of TS 23.369 [3].
6. Same as step 7 in the Inventory procedure specified in TS 23.369 [3] with the additional Registration Indicator included in the Inventory Request. If triggered by an AF the Inventory Request includes the AIoT Identification Information corresponding to the AF request.
This step can be performed by the AIOTF without receiving the service request from an AF, in this case the AIOTF determine the periodicity and selection of NG-RAN(s) based on AIOTF implementation. If AIOTF triggers the initial registration, then the Inventory Request will not include the AIoT Identification Information to trigger all AIoT Devices that are not registered.
7. Same as step 9 in the Inventory procedure specified in TS 23.369 [3] with the additional Registration Indicator included in the paging message.
8. The AIoT Device determines whether it matches the AIoT Identification Information as specified in step 9 of the Inventory procedure specified in TS 23.369 [3].
The AIoT Device checks the PLMN ID or NID and whether the AIoT Device is registered or not. In case the AIoT Device is not registered, the AIoT Device includes a Registration Request Indication in the AIOT NAS message. The AIOT NAS message also includes the parameters as specified in step 9 of the Inventory procedure specified in TS 23.369 [3].
9. Same as step 10 in the Inventory procedure specified in TS 23.369 [3].
10. Same as step 11 in the Inventory procedure specified in TS 23.369 [3].
11. For each successful Registration Request received, the AIOTF prepares a NAS Registration Accept message and includes the NAS Registration Accept message in the Command Request message. The rest of this step is as specified in step 8 in Command procedure specified in TS 23.369 [3].
NOTE 1: Detailed list of parameters to be included in the NAS Registration Accept message will be determined in coordination with SA3 to support DO-A message transmissions.
12. Same as specified in step 9 in Command procedure specified in TS 23.369 [3].
13. Same as specified in step 10 in Command procedure specified in TS 23.369 [3]. The Command Response includes the NAS Registration Complete message.
14. Same as specified in step 11 in Command procedure specified in TS 23.369 [3]. The Command Response includes the NAS Registration Complete message.
15. The AIOTF updates the AIoT Device Context and the AIoT device profile in the ADM that the AIoT device is registered with the network.
16. The AIOTF reports the result of the Naiotf_AIoT_Registration request to the NEF by sending the Naiotf_AIoT_Registration Notify message (a list of AIoT Device(s) response information (AIoT Device ID(s), Registration status and optionally location of each AIoT Device), AF ID, [Last Report Indication]). If multiple AIOTFs are involved in the procedure, the NEF may receive Naiotf_AIoT_Registration Notify messages from multiple AIOTFs.
NOTE 2: The above parameters are the same as included in the Naiotf_AIoT_Inventory Notify message.
NOTE 3: In case multiple AFs are included in the AIoT Device Profile, then all AFs will be notified about the initial registration event.
17. The NEF informs the AF of the result of the Nnef_AIoT_Registration request by sending the Nnef_AIoT_Registration Notify message (a list of AIoT Device(s) response information (AIoT Device ID(s), Registration status and optionally location of each AIoT Device), AF ID, [Last Report Indication]).
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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.
AIOTF:
- Support Registration service procedure:
1. Invocation of the service by the NEF/AF;
2. Receiving in the NAS Inventory Response and indication that the AIoT Device requests to register in the network;
3. Configure the AIoT Device with parameters included in the Registration Accept message.
ADM:
- Maintain the AIoT Device Profiles with registration status information.
NG-RAN:
- None.
AIoT Reader:
- None.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.14 Solution #14: DO-A capable AIoT Device Registration Procedure
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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. initial registration.
B. mobility registration update.
C. Periodic registration.
- ADM stores the DO-A capable AIoT device profile information.
- AIOTF handles NAS termination and device authentication for DO-A capable AIoT devices and manages registration and mobility for AIoT Devices.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 Registration Request to the core network.
The AIoT Device performs an Initial Registration if it is not registered with the network.
The AIoT Device performs Mobility Registration if it has moved outside of its AIoT Registration Area.
The AIoT Device performs periodic registration if it has registered on the network and remains in its AIoT Registration Area beyond the designated time period.
Editor's note: The details of the AIoT Registration Area need to align with the RAN WG
2. AIoT Device sends a message to NG-RAN, including a NAS Registration Request (Registration Type, Temporary ID, device information, security parameters). Registration can be initial registration, mobility registration, or periodic registration. Then, NG-RAN sends the Registration Request to the selected AMF.
3. The gNB discovers the serving AIOTF.
Editor's note: The details of how the gNB discover the serving AIOTF are FFS.
4. The gNB forwards the registration request to the serving AIOTF by either direct connection or indirect connection via the AMF.
5. [Conditional] The serving AIOTF determines the old AIOTF using the temporary ID and retrieves the AIoT Device context from the old AIOTF.
6. The AIOTF performs the Authentication/Security procedure and stores the security context.
Editor's note: Details of authentication/security procedures will be determined by the SA3 WG.
7. The AIOTF responds the Registration Accept to the AIoT device , including a new temporary ID assigned by the serving AIOTF, AIOT Registration Area and periodical registration timer.
8. The AIoT device responds to the AIOTF with Registration Complete via NG RAN and AMF.
9. The AMF forwards the Registration complete to the AIOTF.
10. The AIOTF notifies the ADM of the registration complete status about the AIoT device.
11. The ADM stores the serving AIOTF for the AIoT device.
12. [Conditional] If the ADM discovers that the serving AIOTF has changed, then it needs to initiate the context release procedure to the old AIOTF to delete the context in it.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.15 Solution #15: Support reliable time-base Data Collection of DO-A AIoT sensor device with network trigger
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 all the DO-A sensor device(s) for this operation have been registered with the 5G network before the service starts( e.g. DO-A sensor device can autonomously register to the network without the trigger from network)
NOTE 1: How the DO-A sensor device registers to the network is not covered in this solution and other DO-A device registration solutions can be applied.
2. The data collection pattern of the AIoT sensor device(s) (e.g. periodic and aperiodic time-based data collection) is configured and aware by the AF. The AF provides the data collection pattern information to the AIoTF, which also provides the information to the NG-RAN / AIoT reader(s) to coordinate the data collection.
3. The AIOTF provides the assistance information to the AIoT reader(s) or the NG-RAN to assist time-based (e.g. periodic or aperiodic) data collection (e.g. pre-allocate resource and send triggers for the DO-A sensor device(s)). The assistance information includes periodic data collection information (e.g. start or end time of data collection, interval between periodic data collection, or certain point of time when the data collection is needed, so on).
4. For periodic data collection, the AF and the AIOTF use single command procedure as defined in TS 23.369 [3] to start the time-based data collection operation from DO-A AIoT device(s), without sending read command for every periodical data collection cycle. The AIoT reader periodically trigger and allocated radio resource for the data collection of the AIoT sensor device(s), based on the assistance information from the AIOTF.
5. This solution only focuses on time-based (e.g. periodic or at certain time) data collection of DO-A device(s) and doesn't prevent DO-A device(s) transmitting data autonomously (e.g. event trigger transmission).
NOTE 2: The trigger and resource allocation mechanisms of AIoT reader are determined by RAN WGs and the coordination with RAN WGs is needed.
NOTE 3: Security consideration for periodic data collection operation will be determined by SA WG3.
Editor's note: How to support DO-A device mobility is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 device can autonomously sending data, a large number of AIoT sensor device sending periodic data at the proximity time without network coordination can cause serious race condition for the network resource which lead to low effective of data collection. This solution allows AIoT reader, with the time-based data collection assistance information provided by AIoTF, to periodically or at-certain point to pre-allocate radio resource and trigger the DO-A AIoT sensor device to send sensor data when the transmission time is come. With this solution, the DO-A sensor device doesn't need to maintain a timer which is need to be synchronized with network or AF for periodic transmission.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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, Approximate number of AIoT Devices and periodic data collection Parameters (periodic data collection start / end time, interval between each data collection cycle). NEF selects AIOTF and then NEF sends AIoT Command Request to AIOTF. AIOTF checks AF Authorization by retrieving AF Authorization Profile in ADM. AIOTF sends AIoT Command Response to NEF. It includes Status (Success/Failure), Transaction ID. NEF sends AIoT Command Response to AF. It includes Status (Success/Failure), AF Transaction ID.
2. Step 7 to step 10 of Procedure for Inventory in clause 6.2.2 of TS 23.369 [3].
3. AIOTF sends AIoT Command Request to AIoT Reader via NG-RAN. This includes Device ID, (Reader ID), Command Type Read, Correlation ID, Length and assistance information which includes Periodic data collection indication and periodic data collection Parameters (periodic data collection start / end time, interval between each data collection cycle). AIoT Reader stores Correlation ID with AIoT Device ID as context data as well as the assistance information.
4-5. When the periodic sensor data collection time starts, AIoT Reader sends AIoT Command Request to the AIoT Device. This includes Device ID, (Reader ID), Command Type Read, Correlation ID.
NOTE: AIoT reader or NG-RAN may allocate radio resource for the D2R command response from the DO-A Device. This is up to RAN WG decision.
6. AIoT Device sends AIoT Command Response to AIoT Reader. This includes Device ID and the data collected from the AIoT device(s).
7. AIoT Reader sends AIoT Command Response to AIOTF. This includes Device ID, Sensing Result and Correlation ID. AIoT Reader retrieves Correlation ID with AIoT Device ID from the stored context.
8. AIOTF sends AIoT Command Notify to NEF. This includes Device ID, Sensing Result and Transaction ID. AIOTF retrieves Transaction ID with Correlation ID from the stored context.
9. NEF sends AIoT Command Notify to AF. This includes Device ID, Sensing Result and AF Transaction ID. NEF retrieves AF Transaction ID with Transaction ID from the stored context.
10-14. Every Period, AIoT reader sends AIoT command Request to the AIoT Device. Repeat step 5-9.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 data collection cycle, start or end time of the periodic data collection.
- aperiodic data collection: time(s) when the data collection starts.
AIoT Reader:
- Maintain DO-A device context to conduct data collection procedure at certain point of time based on the assistance information.
- Supports periodically start AIoT Command-only read procedure to collect data from AIoT Device(s) with triggering AIoT device(s) to send data.
- For aperiodic data collection, supports triggering AIoT device to send data when the data collection time is up.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.16 Solution #16: AIoT device DOA data detection and collection
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 AIoT Readers that detects the signal may then use enhanced R19 Paging and Command procedures to handshake with the device and collect the DOA data from the device.
The solution also describes how the AIoT Reader that has collected DOA data from the device can route the data to the network (i.e. AIOTF) and the AF. The routing of DOA data is based on the AIoT Reader's local configuration that maps the AIoT identifier information to the AIOTF address.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.16.1 Description
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 is not immediately picked up by any AIoT Reader and the device doesn't receive response (e.g. Paging) from AIoT Readers, the device may repeat (e.g. periodically) the broadcast for a preconfigured time duration.
Editor's note: How the AIoT device broadcasts DRI depends on RAN WGs' design.
An DOA-capable AIoT Reader is preconfigured with the radio resource on which the DRI broadcast may be transmitted and monitors the DRI broadcast from the AIoT devices. If a Reader (e.g. a UE Reader) is not able to monitor this signal all the time, it may monitor the DRI broadcast only in configured time windows or time occasions. The time window/occasion configuration may be based on the DOA data transmission pattern of the target devices or device group. For example, if an AIoT sensor transmits data twice a day, say 5am in the morning and 11pm in the evening, the AIoT Readers assigned to collect the sensor data may be configured to monitor the sensor's DRI broadcast in a time window around 5am and 11pm.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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. The Reader and the network will also determine the device identifier and verify it during this procedure.
After the device identifier is verified, the Reader may initiate a Read Command procedure to collect the data from the device.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 NG-RAN or AMF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 supposed to serve.
2. The AIoT device has DOA data ready to be sent. The device broadcasts a DRI signal on the preconfigured radio resource. This signal may be picked up by one or multiple Readers that monitor the DRI broadcast.
3. The AIoT Reader that detects the DRI signal may initiate the AIoT Paging towards the device. The Reader includes the DOA Indication in the Paging message and there is no device identifier information in the Paging message.
4. The AIoT device that has DOA data to send receives the Paging message and sends the Paging Response message to the Reader. The Paging Response message includes the device's identifier and may include other information, such as the approximate size of the DOA data to be sent.
Other AIoT devices that receive the Paging but don't have DOA data to send should not respond to this Paging.
Editor's note: It is FFS how to handle the scenario that multiple AIoT Readers detect the DRI signal and send the AIoT Paging messages simultaneously.
NOTE 1: Step 2 – 4 are in the RAN WGs' scope.
5. The AIoT Reader forwards the device identifier information to a selected AIOTF for the purpose of verifying the device identifier. The AIOTF may work with the ADM to verify the device identifier and return the result to the Reader. If the Reader is a UE Reader, the UE Reader forwards the information via NG-RAN and AIOTF to the AIOTF.
Editor's note: It is FFS how to verify the device identifier if it is a temporary identifier and it may need coordination with SA WG3.
6a/6b. If the device ID is successfully verified, the AIOTF initiates Read Command procedure via the AIoT Reader towards the device to collect the device's DOA data.
7. The AIoT device sends the DOA data to the Reader in the Command Response message. Step 6 and 7 may repeat multiple times until all of the device's DOA data is collected.
In case that only the designated Reader can handle the device's DOA data, the device may also include a Reader Token that's calculated from the preconfigured security credentials and inputs (e.g. designated Reader ID). The purpose of Reader Token is to prevent non-designated Readers from handling the data. If the Reader Token is included in the message, the Reader should calculate its own Reader Token and compare it with the received token. If the tokens match the Reader may continue to handle the data, otherwise, it should discard the data. The use of Reader Token is not related to the data encryption.
Editor's note: The use of Reader Token needs coordination with SA WG3.
8. The Reader selects the AIOTF for the DOA data using the local configuration that maps device identifier information to an AIOTF address. Note that this AIOTF may be different from the one that performs the device identifier verification in step 5.
9. The Reader forwards the received DOA data to the selected AIOTF which further forwards it to the AF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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.
- Support Reader Token generation.
AIoT Reader:
- Support DRI signal monitoring and related radio resource configuration and time window configuration.
- Support Reader initiated Pagin and Command procedure (i.e. without receiving the Inventory/Command request from AIOTF).
- Support new "DOA Indication" in AIoT Paging message.
- Support AIOTF selection for routing DOA data to AIOTF and related configuration.
- Support Reader Token verification.
AIOTF:
- Support device identifier verification for DOA data.
- Support initiation of Command procedure.
- Support receiving DOA data from AIoT Readers and forward it to the AF.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.17 Solution #17: Service aspects for DO-A traffic in Ambient IoT networks
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 present in the network can have varying capabilities. Some of them are able to support both DO-A and DT traffic, others can only support DT traffic.
4. DO-A capable devices can be configured by the network to support both DO-A traffic and DT traffic or only DT traffic at a given time.
This solution is applicable for scenarios when the NG-RAN expects an indication from the core network regarding DO-A service.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 signals are used to typically allocate radio resource e.g. Random Access Channel (RACH) resources for enabling devices to access the network.
Enabling DO-A support as a service may help in energy saving in a twofold manner viz. 1). Energy Saving at the reader by reducing D2R signalling to support DO-A whenever DO-A capable devices are not present in the network or are disabled. 2) disabling a specific DO-A service for a device for supporting reduced energy consumption in the device.
Once DO-A service is enabled, a DO-A capable device(s) can register with the core network (AIOTF) with the service ID and is authenticated. It can then request for DO-A data transfer whenever it has some data to send.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.17.2 Procedures
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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], [target area], operation, [priority] [list of device IDs] [offset][duration]) service operation request to the NEF. Service Descriptor is an identifier for every service request that arrives at the AF. It shall be unique within particular AF. The service descriptor that is sent as part of this service operation request shall be the descriptor of the service that needs to be enabled, modified or cancelled. AF ID is the identifier for a given AF. Service type in this request would correspond to "DO-A support". Operation in this request could either enable or disable. The Priority field indicates the priority of the service request. The list of device IDs is an optional parameter in which the set of devices for which this service can be enabled/disabled is indicated. When not provided, the specified service is enabled for all the devices in the network. Similarly, offset and duration are optional parameters used for enabling/disabling a service at "offset" time interval from the point of receiving the request and "duration" is used to specify the duration of time for which the service remains enabled/disabled. When the duration is not provided, the service continues to stay enabled/disabled until a follow-up service request is issued.
NOTE 1: In case the AF is considered as a trusted AF, the AF may directly reach the AIOTF using the Naiotf_AIoT_Do-A Support Request (Service Descriptor, AF ID, [service type], [target area], operation, [priority] [list of device IDs] [offset][duration]).
2. The NEF may further authorize the AF request as specified in clause 5.6 of TS 23.369 [3]. The NEF determines the Target Area information and selects suitable AIOTF(s) that can support DO-A related traffic. The NEF determines AIOTF instances(s) by providing the NRF Target Area information along with the request for DO-A traffic support and the NRF returning AIOTF instance(s) that match the Target Area information and ability to support DO-A, or by using local configuration. Once the NEF authorizes the AF request, the NEF creates a Transaction Reference ID for transferring this request to the AIOTF and stores the AF Identifier along with the Transaction Reference ID.
3. The NEF invokes Naiotf_AIoT_Do-A Support request (Transaction ID, AF ID, [service type], [target area], operation, [Approximate number of Do-A AIoT Devices], [Approximate number of AIoT Devices], [priority] [offset][duration]) towards to the selected AIOTF(s). The Approximate number of Do-A AIoT devices is an optional parameter and could be used for resource allocation.
4. AIOTF receives the Naiotf_AIoT_Do-A Support request and checks the parameters included in the request. The AIOTF may perform checks as specified in clause 5.6 of TS 23.369 [3]. Also, AIOTF may select a set of NG-RAN nodes and reader(s) within the target area for supporting DO-A traffic. The NG-RAN nodes and readers can be selected based on several criteria such as ability to support DO-A traffic, load on the NG-RAN nodes or readers, number of actively connected devices (both 5G NR UEs and A-IoT devices), available radio resources etc. The selected readers allocate radio resources for supporting DO-A traffic. For example, certain trigger time instants may be allocated to only support DO-A traffic from A-IoT devices. These resources may be broadcasted by the A-IoT readers or can be pre-configured by the network while the device is deployed. In case, the Naiotf_AIoT_Do-A Support request cannot be serviced due to any reason e.g. non-availability of readers supporting Rel-20, not enough resources etc. the AIOTF rejects the AIoT service operation request with an appropriate cause code in step 5 and step 7 is skipped.
NOTE 2: The Naiotf_AIoT_Do-A Support is used to provide indication to the network that DO-A traffic may be expected within a certain time period. The necessity of this indication depends on RAN WGs.
5. AIOTF sends Naiotf_AIoT_Do-A Support Response to the NEF containing the accept or reject result for the Naiotf_AIoT_Do-A Support request based on step 4.
6. NEF sends Nnef_AIoT_Do-A Support Response to the AF, containing the accept or reject result for the AIoT service Cancel operation request as specified in clause 8.3 of TS 23.369 [3]. If the response was an accept, then DO-A enabled A-IoT devices are able to attempt successful registration with the network.
7. Any device capable of DO-A traffic support can now register with the network. Once registered with the network, it can initiate transmission of DO-A traffic whenever it has some data to transmit.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 Capability" which can identify whether device can support DT only or both DT and DO-A traffic type. When DO-A traffic can be supported by the device, then it also maintains whether DO-A is enabled/disabled for the device for a given service. Similarly, AF Authorization Profile should indicate the support for DO-A for a specific service.
- AF:
- For supporting DO-A, the functionality of AF is enhanced to enable or disable DO-A support for a specific service.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.18 Solution #18: AIoT Device Registration and data transmission Procedure
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 transferred data is included in AIoT NAS messages. The network is configured with a route for uplink data from the AIOT Device and the route is used when traffic is sent.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 the network and the data transmission procedure without any trigger from the network. The registration type can be an Initial Registration or a Mobility Registration Update when it to moves outside of an AIoT Registration Area. When an AIoT Device initially registers a context is created in the network for the AIoT Device and the AIoT Device is provided with an AIoT Registration Area.
Editor's note: It is FFS whether other registration type need to be supported.
AIoT Areas may span multiple Readers (and NG-RAN nodes) and a Reader may belong to multiple AIoT Areas. The granularity of the AIoT Areas and Readers can mean that the AIoT Device has to be provided with and store a large amount of information, or would have to perform Mobility Registration Updates frequently when the AIoT Device moves relatively small distances. While in some cases knowledge that the AIoT Device has moved a small distance is desirable, it is not a universal desire and may cause significant overhead to AIoT Devices and networks.
Therefore, to enable the difference scenarios the network is configured with AIoT Registration Areas. An AIoT Registration Area is provided to the AIoT Device and is:
- A Reader list, AIoT tracking area code (TAC), or an AIoT Area List. The AIoT Device performs Mobility Registration Update if it moves outside of the list, TAC or AIoT Area List.
- Be hierarchical and be the first part of a TAC or a partial TAC. The AIoT Device performs Mobility Registration Update if the supplied part of the TAC no longer matches the TAC where the AIoT Device is.
The hierarchical AIoT Registration Area will reduce the amount of storage required by an AIoT Device.
NOTE 1: The AIoT Registration Area is specific to Ambient IoT and does not need to be aligned with registration areas used by an AMF for NR. The AIoT tracking area code (TAC) is a different type of area identification from an AIoT Area List.
An AIOTF can subscribe to events for AIoT Device mobility, similar to those supported in 5GS for UEs, to be informed when the AIoT Device moves outside of its AIoT Registration Area.
According to TS 23.369 [3] and TS 33.369 [11], the AIOTF is the supports termination point of the AIoT NAS protocol within the network and supports the authentication of the AIoT Device. For a DO-A capable AIoT Devices the AIOTF remains the NAS termination point, including for device authentication and additionally supports registration management and mobility management.
NOTE 2: The Temporary ID used in the procedures for AIoT Device identification and AIOTF selection will need alignment with SA WG3.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.18.2 Procedures
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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 Registration Request (Registration Type, device information, security parameters).
The D2R parameters contains, e.g. a Temporary ID (if available), the selected PLMN ID and allows NG-RAN to route the request to the appropriate AIOTF.
NOTE 1: The details of the D2R parameters need to be coordinated with RAN WGs.
The Registration Type indicates if the AIoT Device is performing an Initial Registration or a Mobility Registration Update. The AIoT Device performs an Initial Registration if it is not registered with the network and performs a Mobility Registration if it has moved outside of its AIoT Registration Area.
2. NG-RAN selects an AIOTF based on the D2R parameters or local configuration and to send the NAS message received from the AIoT Device to. If Indirect Connectivity is used between NG-RAN and the AIOTF, NG-RAN sends the selected AIOTF ID to AMF which can then route the message to the selected AIOTF.
3. NG-RAN sends the Registration Request NAS Message, Temporary ID and selected PLMN ID from the D2R message and Reader information to the selected AIOTF. If the Temporary ID indicates another AIOTF assigned it, the selected AIOTF fetches the AIoT Device context from that AIOTF.
4. [Conditional] The new AIOTF may determine an old AIOTF using the Temporary ID and retrieves the AIoT Device context from the old AIOTF.
5. The AIOTF determines the ADM for the AIoT Device based on the AIoT Device's permanent ID.
6. The AIOTF performs authentication and security procedures and stores the security context.
NOTE 2: Details of authentication and security procedures will be determined by SA WG3.
7. The AIOTF registers itself with ADM as serving AIOTF for the AIoT Device and may retrieve the subscription data for the AIoT Device.
8. [Conditional] The ADM informs the old AIOTF using Nadm_SDM_unsubscribe that it is no longer the serving AIOTF for the AIoT Device.
9. The AIOTF sends the Registration Accept to the AIoT Device, which may include a new Temporary ID and AIoT Registration Area.
NOTE 3: This solution does not provide any power consumption parameters, but if they are defined by other solutions, it is expected they can be supplied to the AIoT Device in this procedure, if required.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 validity time is used to indicate the how long network maintains the DO-A configuration information. This subscribes the AF to notifications of received data, as described in clause 6.18.2.3.
2. The NEF selects an ADM based on the AIoT Device information received in step 1.
3. The NEF sends a Nadm_DOAConfiguration_Create Request message (AIoT Device information, AF Identifier, validity time) to the ADM.
4. The ADM validates the request from the NEF and stores the AF information for devices' DO-A data transmission, i.e. AF Identifier and validity time.
5. The ADM sends the Nadm_DOAConfiguration_Create Response message to NEF to confirm the route has been stored.
6. The NEF sends Nnef_DOAconfiguration_Create Response to the AF to acknowledge acceptance of the Nnef_DOAconfiguration_Create Request.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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. Based on the Temporary ID, NG-RAN selects an AIOTF and forwards the AIoT UL NAS message and the RAN AIoT Device NGAP ID to the selected AIOTF. If Indirect Connectivity is used between NG-RAN and the AIOTF, NG-RAN sends the selected AIOTF ID to AMF so it can route the messages to the AIOTF. The AIoT Device may provide NG-RAN with an indication that follow on NAS message(s) to or from the AIoT Device or AIOTF are expected. When NG-RAN receives a follow-on indication, it can ensure that subsequent messages can be sent from the AIoT Device.
3. The AIOTF obtains the target AF information for the AIoT Device through subscribing to the ADM.
4. The AIOTF forwards the AIoT Device ID, DO-A Data and the target AF information an NEF. The NEF does not have to be the same NEF that that AF used to provide the routing information to the network.
5. The NEF forwards the AIoT Device ID, DO-A Data to the AF based on the target AF information.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 AIOTF to perform the Inventory Procedure.
- In step 11, the AIOTF may find the serving AIOTF based on the Temporary ID and retrieve the AIoT Device ID from the serving AIOTF. The AIoT Device context is not transferred, therefore a new Temporary ID does not need to be provided to the AIoT Device.
NOTE: Power consumption parameters might need to be provided to NG-RAN when performing the Inventory Procedure and details are expected to described other solutions.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 AIOTF to perform inventory procedure.
- In step 7, the AIOTF may find the serving AIOTF based on routing information, e.g. from within the temporary ID and fetch AIoT Device contexts from the serving AIOTFs. It also registers/updates itself in the ADM as new Serving AIOTF.
If the serving AIOTF has changed, a new Temporary ID, needs be generated and provided to the AIoT Device so when it performs DO-A procedure the new AIOTF can be selected by NG-RAN.
- In step 8, the new Temporary ID, is provided to the AIoT Device along with the NAS Command Request message.
NOTE: Power consumption parameters might need to be provided to NG-RAN when performing the Command Procedure and details are expected to described other solutions.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 performing registration procedure.
ADM:
- Support storage of AIOTF ID as serving AIOTF for AIoT Device.
- Support storage of AF Identifier for AIoT Device.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 6.19 Solution #19: AF activates/deactivates the DO-A traffic to the AIoT device
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 be performed before the DO-A traffic configuration and sending DO-A data.
- The DO-A configuration of the DO-A traffic: The AF sends the configuration parameters of DO-A traffic to the AIoT device via AIoT Command.
- The DO-A data reporting method: DO-A data (e.g. sensing data) reporting method of the AIoT device includes periodical reporting (i.e. reporting with the specific period) and non-periodical reporting (i.e. event-triggered DO-A traffic, reporting when meets configured event. ).
- The DO-A traffic is initiated or stopped by the AF request: The AF initiates or stops the device reporting the DO-A data via the Activation/Deactivation Command separately.
NOTE: The Activation/Deactivation Command is only used to initiate or stop the DO-A traffic and is different from Enable/Permanent Disable Command.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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
0. The AIoT devices should perform the registration-like procedure to indicate the support of DO-A communication. Optionally, the AIOTF could indicate the presence of the AIoT device to corresponding AF.
Editor's note: The AIOTF could know the presence of the device via registration-like procedure initiated by the AIoT device or the AF. The details of the device registration-like procedure are FFS.
1. Step 1 to step 6 of Command Procedure in clause 6.2.3 of TS 23.369 [3] with additional DO-A configuration parameters.
The AF sends Nnef_AIoT_Command Request message to the NEF to configure the AIoT device for DO-A traffic. Nnef_AIoT_Command Request (Command type, the offset where to write DO-A Configuration Parameters, DO-A Configuration Parameters, [the offset where to store the DO-A data (e.g. sensing data) in the AIoT device], [the length of the DO-A data sent by the AIoT device] ). Excepting the above parameters for DO-A traffic, the Nnef_AIoT_Command Request also includes other necessary parameters specified in clause 6.2.3 of TS 23.369 [3].
The DO-A Configuration Parameters includes DO-A Period for reporting DO-A traffic if it is periodical DO-A traffic, DO-A Event (e.g. temperature threshold for the temperature sensor device) for reporting DO-A traffic if it is event-triggered DO-A traffic.
Editor's note: The DO-A Configuration Parameters should be visible to the CN. It is FFS the AF sends the DO-A Configuration Parameters to the AIoT device via Write Command or the new Command (e,g. DO-A Configure Command type).
NOTE 1: The offset where to store the DO-A data in the AIoT device and the length of the DO-A data sent by the AIoT device are optional IEs and could also be pre-configured in the AIoT device.
NOTE 2: There could be multiple sets of DO-A Configuration Parameters (e.g. Set A: DO-A Period=60s, Set B: DO-A Period=3600s).
The NEF selects the AIOTF and sends the Naiotf_AIoT_Command Request message to the selected AIOTF. The AIOTF checks the AF request and device capability to perform configuring the AIoT device for DO-A traffic.
2. This step is the procedure for Inventory in clause 6.2.2 of TS 23.369 [3]. It could be optionally performed if a NGAP connection for the AIoT device between the AIOTF and the NG-RAN exists (e.g. if the NGAP connection is established in AIoT device registration-like procedure.).
3. The AIOTF sends AIoT Command request to the NG-RAN. The AIOTF will encapsulate the DO-A Configuration Parameters in an AIOT NAS PDU. Some DO-A configuration parameters may be visible to the NG-RAN to assist resource scheduling in RAN (e.g. If the length of the DO-A data could be visible to the NG-RAN, the NG-RAN may allocate the AIoT DO-A radio resource to the AIoT device efficiently.) and the AIOTF will list them in NGAP message IE (e.g. the length of the DO-A data, DO-A Period).
Editor's note: Whether visible parameters are needed and what visible parameters are needed depend on RAN WGs.
4. The NG-RAN sends AIoT Command request to the AIoT reader over the RRC connection, if the AIoT reader is a UE reader. If the AIoT reader is the RAN reader, how the NG-RAN sends AIoT Command request to the AIoT reader is up to implementation.
5. The AIoT reader sends AIoT Command request to the AIoT Device. When the AIoT device receives DO-A Configuration Parameters, it sets the parameters to the device.
6. The AIoT device sends AIoT Command response to the AIoT reader to indicate DO-A Configuration Parameters are set successfully in the AIoT device.
7. The AIoT reader sends AIoT Command response to the NG-RAN over RRC connection, if the AIoT reader is a UE reader. If the AIoT reader is the RAN reader, how the AIoT reader sends AIoT Command response to the NG-RAN is up to implementation.
8. The NG-RAN sends AIoT Command response to the AIOTF to indicate the successful configuration in the AIoT Device. After this step, the NG-RAN could keep the connection as a long-term connection with the AIOTF until the terminate of the DO-A traffic.
9. The AIOTF reports the result of the AIoT Command request to the NEF.
10. The NEF informs the AF the result of the AIoT Command request. The DO-A traffic configuration procedure is complete.
Additionally, the AF can initiate or stop the AIoT device DO-A traffic via the Activation/Deactivation Command request in step 11 ~ step 23.
11. The AF sends Nnef_AIoT_Command Request message (Activation/Deactivation Command type, DO-A configuration set info, target AIoT device info) to the AIoT device via the NEF to initiate or stop the configured DO-A traffic. DO-A configuration set selection info is the optional IE and this information is only presented if there are multiple sets of DO-A Configuration Parameters.
Excepting the above parameters, the Nnef_AIoT_Command Request also includes other necessary parameters specified in clause 6.2.3 of TS 23.369 [3].
12. The NEF selects the AIOTF and sends the Naiotf_AIoT_Command Request message (Activation/Deactivation Command type, target AIoT device info) to the selected AIOTF.
13. The AIOTF checks the AF Authorization and device capability to perform DO-A traffic.
14. The AIOTF sends the Naiotf_AIoT_Command Response message (accept or reject, cause) to the NEF.
15. The NEF sends the Nnef_AIoT_Command Response message (accept or reject, cause) to the AF. If the response was a reject the procedure stops here.
16. The AIOTF sends AIoT Command request, including correlation ID and AIOT NAS PDU (the activation/deactivation indication), to the NG-RAN.
NOTE 3: After step 8, the NG-RAN keeps the connection as a long-term connection with the AIOTF so that the inventory procedure is not presented.
Editor's note: Whether the activation/deactivation indication is useful and visible to the NG-RAN is FFS.
17. The NG-RAN sends AIoT Command request, including AIOT NAS PDU (the activation/deactivation indication), to the AIoT reader over the RRC connection, if the AIoT reader is a UE reader. If the AIoT reader is the RAN reader, how the NG-RAN sends AIoT Command request to the AIoT reader is up to implementation.
18. The AIoT reader sends AIoT Command request, including AIOT NAS PDU (the activation/deactivation indication), to the AIoT Device.
19. The AIoT Device sends AIoT Command response, including AIOT NAS PDU (the activation/deactivation result), to the AIoT reader to indicate DO-A traffic is initiated successfully or stopped successfully.
NOTE 4: After sending the AIoT Command response, if the command type in step 13 is Activation, for the periodical DO-A traffic the AIoT device begins to calculate the sending timing according to the configured DO-A period.
Editor's note: How the AIoT Device supports timer is FFS.
20. The AIoT reader sends AIoT Command response, including AIOT NAS PDU (the activation/deactivation result), to the NG-RAN over the RRC connection, if the AIoT reader is a UE reader. If the AIoT reader is the RAN reader, how the AIoT reader sends AIoT Command response to the NG-RAN is up to implementation.
21. The NG-RAN sends AIoT Command response, including AIOT NAS PDU (the activation/deactivation result), to the AIOTF.
22. The AIOTF sends AIoT Command response to the NEF to indicate the result of activation/deactivation command.
23. The NEF sends AIoT Command response to the AF to indicate the result of activation/deactivation command.
After the activation procedure, the AIoT device generates the DO-A Data and send DO-A data with the AIoT device ID (e.g. AIoT device temporary ID) according to DO-A Configuration Parameters.
Editor's note: The details procedure of the routing of the AIoT device DO-A data is FFS.
Editor's note: It is FFS for whether there is response from the CN to the AIoT device.
After the deactivation procedure, the AIoT device stops to send the DO-A data until the AF sends activation command request.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 activation/deactivation indication to the AIoT device via AIOT NAS message.
- Receives DO-A data (e.g. sensing data) from AIoT device(s) through AIoT reader(s) and delivers it to the AF through the NEF or not.
ADM:
- Supports the AIoT device profile, including DO-A Capability.
NG-RAN:
- Supports DO-A procedure for AIoT Device(s).
- Supports to keep the connection as long-term connection with the AIOTF after the DO-A traffic configuration procedure.
AIoT reader:
- Supports DO-A procedure for AIoT Device(s).
AIoT Device:
- Supports DO-A procedure for DO-A data report.
- Supports to set DO-A Configuration Parameters and behave according to DO-A Configuration Parameters.
- Supports timer.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 7 Interim agreements
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 7.1 Agreed Principles
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 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
NOTE: Whether the interface between AIOTF and UDM is needed will be checked in later phase.
Message and protocol stack
- Messages between the UE Reader and the AIOTF are delivered using RRC between UE and NG-RAN and NGAP between NG-RAN and AMF and using an SBI interface between AMF and AIOTF. The related protocol stack is shown in Figure 7.1.1-3.
Figure 7.1.1-3: Protocol Stack for the RRC option
UE reader authorization and revocation part:
- Subscription aspects:
- The UE subscription in the UDM will be extended with UE Reader subscription information, which consists of the following:
- information indicating whether the UE is allowed to operate as a UE Reader.
Editor's note: Whether and what additional subscription information for the UE Reader is needed is FFS.
- UE Reader subscription information is available to AMF.
- If AMF receives, as part of the subscription information, the indication that the UE is authorized to operate as a UE Reader, AMF informs NG-RAN that the UE is authorized to operate as a UE Reader.
Editor's note: Whether to inform the UE about the authorization information is FFS.
Editor's note: Whether UE reader capability is provided to AMF is FFS.
- If the subscription information has been revoked, the indication that the UE is not authorized to operate as a UE Reader from the UDM, then the AMF informs NG-RAN that the UE is not authorized to operate as a UE Reader.
Editor's note: Whether and how UE Reader subscription information is provided to AIOTF is FFS.
- Radio resource management for UE Reader operation:
- If the gNB has received the indication that a UE is authorized to operate as a UE Reader, then the gNB may assign radio resources to the UE for UE Reader operation.
AIOTF Discovery and Selection for UE reader ID:
Editor's note: How to discover and select AIOTF when AF provides UE reader ID is FFS.
UE reader selection part:
Two scenarios will be supported for UE reader selection, AF providing UE reader ID case and AF providing Area case for all types of UE reader.
- For AF providing UE reader ID case:
- If UE Reader ID(s) is provided by the AF via the NEF for the operation, then that is used as the selected Reader(s) if authorized as UE reader. The AIOTF provides the selected UE Reader(s) to the NG-RAN.
Editor's note: How to select UE reader(s) based on the AF provided area information is FFS.
UE reader ID allocation:
Editor's note: Whether and how to allocate the UE reader ID is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 7.1.2 Agreed Principles for KI#2
| |
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 7.1.2.1 DO-A capable Device Registration for topology 1
| Initial registration
A. Initial registration is supported and 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 and the network establish a context which is used, for example, in the subsequent DO-A data transfer.
Editor’s note: It will be revisited whether or not to support initial registration in SA2#173.
B. The AIoT Device determines to perform the initial registration based on its implementation e.g. power on.
C. Following information is sent by the AIoT Device for initial registration:
1. An AIoT Device identifier, it is:
- if available, the AIoT temporary ID information;
- otherwise, a form of the permanent AIoT Device identifier.
2. AIoT NAS Registration Request message.
3. AIOTF routing information in AS, if available.
NOTE 1: Whether the AIoT Device identifier and AIOTF routing information are combined or are separate will be coordinated with SA WG3.
NOTE 2: The form of the permanent AIoT Device identifier will be coordinated with SA WG3.
D. NG-RAN selects an AIOTF based on the AIOTF routing information, if provided by the AIoT Device, or local configuration.
E. NG-RAN sends at least the NAS registration request message from the AIoT Device to the selected AIOTF. If Indirect Connectivity is used between NG-RAN and the AIOTF, NG-RAN sends the selected AIOTF ID to AMF which can then route the information to the selected AIOTF.
F. If the initial registration request from the AIoT Device is accepted, the serving AIOTF may allocate an updated AIoT temporary ID information. The AIOTF sends an AIoT NAS Registration Accept to the AIoT Device, including the updated AIoT temporary ID information and AIOTF routing information.
The AIoT Device acknowledges the AIOTF by sending a Registration Complete message.
G. The AIOTF considers the AIoT Device as registered when it has an AIoT Device context for the AIoT Device. The AIOTF stores its AIOTF ID in the AIoT Device profile data in the ADM as serving AIOTF for the AIoT Device.
H. The ADM informs the old AIOTF (if available) that it is no longer the serving AIOTF for the AIoT Device, and the old AIOTF removes the AIoT Device context locally.
Mobility registration
Editor's note: whether and how to support mobility registration is FFS.
Periodic registration
Editor's note: whether and how to support periodic registration is FFS.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 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 procedure.
Editor's note: It is FFS on the potential enhancement of Rel-19 command procedure to support configuration by the AF to the AIoT Device.
Editor's note: It is FFS to support the periodic data collection.
NOTE 1: The conditions in the local configuration are on application-level and out of scope of 3GPP.
- DO-A capable AIoT Devices send DO-A data to the AIOTF via AIoT NAS message. The AIoT NAS message is security protected.
NOTE 2: The details of security protection of AIoT NAS message will be determined by SA WG3.
Editor's note: Whether a NAS ACK response is needed is FFS, and it also depends on RAN WG2 to determine whether a NAS ACK response message is needed as an acknowledgement in MAC layer.
Editor's note: Other information provided by AIoT Devices is FFS, including temporary ID, AIOTF ID, AF information and follow-up message indication.
- After the AIOTF receives the AIoT NAS message, the AIOTF retrieves the target address from the AIoT Device Profile Data in ADM if not available locally.
- The AIOTF notifies the DO-A data and the AIoT Device Permanent ID to the AF(s), optionally via the NEF.
Editor's note: It is FFS on whether the AIOTF routes the DO-A data based on the AF information from AIoT Devices.
Editor's note: It is FFS on whether the AIoT Device Profile Data stores multiple target addresses.
- The AF subscribes to the AIOTF for the DO-A data delivery of AIoT Devices directly or via the NEF, with target address provided.
Editor's note: Whether subscription is used is FFS.
- The network performs AF authorization for the subscribe request from the AF. If authorized, the target address is stored in the AIoT Device Profile Data.
Editor's note: It is FFS on the OAM option and the configuration solution.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 7.2 Topics for further consideration
| 7.2.Z Topics for further consideration for KI#Z
Editor's note: This clause will include the topics for further consideration as work progresses for the specific KI#Z. Eventually this clause should only contain topics for further consideration that did not result in agreements (i.e. in agreed principle(s) in a clause 7.1.Z) and can either be then marked as not pursued or postponed to a future release.
|
e1a24e188a6c7563b060dc3d59e35fb2 | 23.700-30 | 8 Conclusions
| Editor's note: This clause will capture conclusions for the study.
Where there is consensus, interim agreements (e.g. solution principles descriptions) should be documented in the TR as soon as possible during a study.
These can be documented in the TR as "7.1.Y Agreed Principles for KI#Y" in the "Interim Agreements" clause. If the interim agreement has impacts on another clause in the TR and if there is consensus, that TR clause can be updated.
By consensus interim agreements can become part of the final conclusions of the study.
The Overall Evaluation clause previously used in TR skeletons should not be used.
There should be a Topics for further consideration clause per Key Issue. It is recommended that this is used e.g. to capture common issues that need to be resolved for multiple solutions.
Annex A:
Change History
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA2#170
S2-2506350
-
-
-
Proposed skeleton agreed at SA2#170
0.0.0
2025-08
SA2#170
-
-
-
-
Inclusion of documents approved in SA2#170:
S2-2507706, S2-2507707, S2-2507761, S2-2507764,S2-2507765, S2-2507766, S2-2507767, S2-2507796, S2-2507797
0.1.0
2025-10
SA2#171
-
-
-
-
Inclusion of documents approved in SA2#171:
S2-2509386, S2-2509387, S2-2509405, S2-2509407, S2-2509409, S2-2509411, S2-2509450, S2-2509451, S2-2509453, S2-2509454, S2-2509455, S2-2509456, S2-2509458, S2-2509459, S2-2509658, S2-2509829
0.2.0
2025-11
SA2#172
-
-
-
-
Inclusion of documents approved in SA2#172:
S2-2511046, S2-2511048
0.3.0
2025-12
SA#110
SP-251348
-
-
-
MCC Update for presentation to TSG SA#110 for information
1.0.0
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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. Until the normative work is available, the study can take into account progress made in SA WG1 and TSG RAN.
The study investigates the architectural requirements, assumptions, high-level principles, key issues, as well as solution and system architecture recommendations for 6G architecture.
The conclusions of this study will form the basis for the normative work.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 23.503: "Policies and Charging control architecture; Stage 2".
[5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[6] 3GPP TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions".
[7] RP-252912, "Revised SID: Study on 6G Radio", 3GPP TSG RAN Meeting #109, Beijing, China, September 15-18, 2025.
[8] 3GPP TS 22.101: "Service aspects; Service principles".
[9] 3GPP TS 22.261: "Service requirements for the 5G system".
[10] 3GPP TS 22.105: "Services and service capabilities".
[11] 3GPP TR 22.870: "Study on 6G Use Cases and Service Requirements".
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 3 Definitions of terms, symbols and abbreviations
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 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 rules by applying them literally.
6G Core Network (6G CN): In this study, it refers to the Core Network for the 6G System.
NOTE 1: To what degree 6G CN can be considered as evolution of 5GC or as a new Core Network will be determined during the study.
6G RAN: In this study, it refers to the radio access network for 6G radio access technology (6GR) being studied by 3GPP RAN WGs [7].
6G System (6GS): 3GPP System consisting of 6G RAN, 6G CN and UE and supports also connectivity of UEs via specific non-3GPP access(es).
NOTE 2: Which specific non-3GPP access(es) are supported is studied under WT#1.3.
Non-Access Stratum: The Non-Access Stratum (NAS) is the stratum for the control plane between the UE and the 6G CN.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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>
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 4 Architectural Assumptions and Requirements
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 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 single core network type, i.e. 6G CN. It is assumed that the 6G RAN is a single technology framework based on a stand-alone architecture.
NOTE: This does not exclude network sharing scenarios such as Multi-Operator Core Network.
3. The 6G system is assumed to maintain the RAN and CN functionality split as in 5GS.
4. The study aims to avoid duplication of functionality between 6G RAN and 6G CN.
5. Real-time voice and video services under operator’s control and in 3GPP scope (MMTel) will be provided by IMS.
6. The 6G system is assumed to natively support both Terrestrial Networks (TN) and Non-Terrestrial Networks (NTN).
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 4.2 Architectural Requirements
| Editor's note: This clause defines the architectural requirements that serve as the foundation for the study.
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.
4. Minimize inter dependencies between NFs when introducing a new feature or procedure for an NF.
The architectural requirements apply to all WTs and corresponding key issues in this study.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5 Key Issues
| Editor's note: This clause identifies key issues to be addressed.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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 bullet 1a covers 6G System procedures including functionalities such as mobility management, session management, NAS transport and UE NAS identifiers.
NOTE 2: For the above KI#1.1 bullet 1a, target would be not to impact other non-access stratum functionalities when introducing new non-access stratum functionalities. If this is not possible, objective is to minimize impact.
NOTE 3: 6G System Procedures will include interaction between RAN-CN, interaction within CN NFs. The signaling interaction between RAN-CN need coordination and alignment with RAN3.
NOTE 4: Overall Interworking and migration aspects are covered by key issues for WT#2 (KI#17). Impact to IWK due to features introduced by this key issue will be covered by this key issue in alignment with WT#2 (KI#17).
Key Issue #1.2
1. Study the support for control signalling for 6G System, including at least the following:
a) Whether and how to support generic mechanisms (e.g. service discovery, service authorization, transport mechanism) for UE to Core Network interaction to support operator services.
NOTE 5: This KI#1.2 bullet 1a can include any transport mechanism such as using NAS or UP or new plane. KI#1.2 bullet 1a can have dependency on other key issues defined for e.g. KI#1.1 bullet 1a, KI#18, KI#19, KI#20, KI#21, KI#22.
NOTE 6: 6G System Procedures will include interaction between RAN-CN, interaction within CN NFs. The signaling interaction between RAN-CN need coordination and alignment with RAN3.
NOTE 7: Overall Interworking and migration aspects are covered by key issues for WT#2 (KI#17). Impact to IWK due to features introduced by this key issue will be covered by this key issue in alignment with WT#2 (KI#17).
NOTE 8: This KI#1 covers operator services.
NOTE 9: Solutions may apply for only KI#1.1 or only KI#1.2 or both KI#1.1 and KI#1.2.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.2 Key Issue #2: SBA framework
| The following is key issue for SBA related work task.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1 Study whether and how to optimize NF/NF service registration, discovery and selection for efficient message forwarding compared with 5G.
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 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.1 Network Sharing in the 6G system
Study on how to support network sharing in 6G, including the following aspects:
- How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G.
Editor's note: It is FFS whether other aspects of network sharing in 6G can be added in this clause.
A.1.2.2 Scope on Network Slicing
The scope of the network slicing work task includes:
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 of possible improvement and simplification of network slicing.
b. Identify and address any improvements of the application traffic mapping to network slice(s)/user plane connection(s).
NOTE 1: Coordination between bullet 1b and the WT 1.2.x on Policy is expected.
2. Study impacts of the network slicing in 6G on the interworking and migration.
NOTE 2: Impacts to RAN are possible and coordination with RAN WGs is expected.
A.1.2.3 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 to enhance user plane flexibility (by user plane function (re)selection) for different service requirements, session continuity and mobility with consideration of user plane function capability and path performance between access network and data network.
NOTE 1: This work task may require coordination with RAN WG for user plane interface.
3. Whether and how to enhance resilience, scalability, and high availability of user plane function.
NOTE 2: The outcome of this study may include architectural requirements based on which stage 3 working group can work on the user plane protocols. The stage 3 protocol aspects, including how to design and select user plane protocols, are not in the scope of stage 2.
A.1.2.4 QoS Framework for 6G
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 groups will determine the characteristics of AI traffic is subject to SA plenary (SA#110) decision.
NOTE 2: Coordination with WT#3.2 may be needed.
2. Whether and how to enhance QoS mechanisms to:
a. support QoS targets fulfilling application’s QoS requirements (e.g., dynamic QoS requirements) in a less resource intensive manner than the existing GBR, Delay Critical-GBR.
3. Study whether and what enhancements are needed to adjust the QoS targets, in case the current QoS targets cannot be met, to minimize the impacts to application operation or user experience.
4. Study whether and how to support the UE, application and network QoS collaboration to improve awareness in the 6GS of application traffic needs, e.g., traffic pattern, dynamic QoS requirements and to improve awareness in the application/UE of what can be provided by the network, e.g., maximum bitrate.
NOTE 3: Applications consist of UE aspect and DN aspects.
5. Whether and how to enhance QoS monitoring, based on the identified needs, e.g., to determine the end-to-end per-packet delay, packet loss rate between the PSA-UPF and the UE for the verification of the QoS target fulfilment.
6. Study whether and what enhancements are needed to enforce QoS differentiation, e.g., in case of frequent address change of the server, application traffic with multiplexed media flows.
NOTE 4: QoS aspects of interworking will be considered based on the WT#2.
NOTE 5: This WT will coordinate with SA WG4 and RAN WGs.
NOTE 6: The content of the 5GS QoS Framework that will be used as a starting point for discussion on 6G QoS will be determined by moderated discussion.
NOTE 7: This WT may study impacts to the QoS for 6G based on the input identified and provided by other WTs.
A.1.2.5 Policy Framework
To support the Policy Framework in 6GS, the policy and charging control Framework defined in 5G for policies (i.e., SM Policy, UE Policy, AM Policy) is considered as starting point for discussion, the following aspects are to be studied:
1. Whether and how to simplify the policy control framework for 6G, including:
a. whether and how to reduce the number of policy control services e.g. the same policy control association for both AM and UE policies or the number of interactions to efficiently provide policies to the different policy enforcement points.
NOTE 1: The example above does not preclude that other examples are covered in the study phase if the reason for simplification is identified.
b. whether and how to support the UE to request UE policies from the 6G CN and/or the 6G CN to provide UE policies to the UE.
2. Whether and how to consider user preferences during UE policy evaluation at UE, without conflicting with network provided UE policies.
NOTE 2: the statement that refers to considering user preferences refers to the ability to influence the evaluation of UE policies.
3. Whether and how to improve the External Parameter Provisioning aspects of policy control for 6G.
NOTE 3: General Authorization of the external parameter provisioning is handled in the WT#1.2 Network Exposure.
4. Whether and how to improve events notification about policies to the AF (e.g. to notify the AF that e.g. charging key changed).
5. Whether and what parameters the UE can provide as input for PCC decision, e.g. related to QoS control to the 6G CN. The UE input for PCC decision related to QoS is based on the progress in WT#1.2 QoS.
NOTE 4: The example above does not preclude that other examples are covered in the study phase if those are identified.
NOTE 5: The AF input for session management defined in 5G can be treated as starting point for discussion.
NOTE 6: The UE can decide if and when to provide the above input the request to the network.
NOTE 7: The UE is not assumed to know whether AF input for QoS is available.
NOTE 8: Whether the UE can provide any input for PCC decisions as the AF provides for UE or AM policies are out of the scope of this bullet.
NOTE 9: The assumption is that either the AF or the UE provides input for PCC decision for e.g. QoS control.
The following notes are applicable to all bullets in this WT:
NOTE 10: If the energy related information, either based on 5G mechanisms, or 6G mechanisms, is available then this WT will study how to take energy efficiency and consumption aspects into account for policy decisions.
NOTE 11: This WT has IWK aspects that are scoped under WT#2.
NOTE 12: This WT can study potential enhancements to the policy control framework for 6G services based on the input identified and provided by other WTs.
NOTE 13: This WT depends on the overall 6G roaming architecture based on the output of WT#1.1. Solutions for this WT will address roaming if applicable.
NOTE 14: Any improvements of the application traffic mapping to network slice(s)/user plane connection(s) are out of the scope of this WT.
NOTE 15: Identify and address any feedback from markets where policy control framework technologies are already being commercially deployed.
A.1.2.6 Network Exposure
This work task is to study whether and how to support a common network exposure framework in 6G. The capabilities that are exposed via the framework fall into one of two categories.
1. The first category is new capabilities. New capabilities refer to capabilities that are not exposed in the 5G network. This category of exposed capabilities is dependent on other work tasks. This work task will include a review of exposure requirements that derive from other work tasks.
2. The second category refers to capabilities that are exposed in the 5G network and are used as a starting point for discussion of this work task. This category of exposed capabilities may be dependent on other work tasks.
Since this work task depends on other work tasks, time will not be allocated for solutions for this work task by SA2 before SA2 #175.
NOTE 1: This work task requires coordination with SA WG3, SA WG6, and SA WG5.
NOTE 2: This work task has dependency on service requirements to be specified by SA WG1.
NOTE 3: Information exposure is based on operator policies/SLAs.
NOTE 4: Authorization, Privacy protection and user consent aspects require coordination with SA WG3, and application layer user consent aspects may require coordination SA WG6.
Aspects that can be studied under this work task are:
1. How to support a common network exposure framework in 6G for the exposure of network capabilities to an AF.
a. Whether and how to support a common network exposure framework in 6G for the exposure of network capabilities to AFs, in an access independent manner (to the extent that exposure in an access independent manner is possible). The exposure framework of the 5GS (i.e. exposure via the NEF) is assumed to be the starting point for discussion of this work task.
b. Whether and how to support co-existence with the 5G exposure framework.
NOTE 5: The common network exposure framework in 6G in SA2 does not duplicate the SA WG6 Framework.
NOTE 6: Examples of network capabilities include information exposure such as information about UE related events, network events, analytics, and information provisioning such as UE related network configuration parameters and service specific parameters.
c. Whether and how to support privacy protection, user consent, data anonymization, and service authorization mechanisms.
d. Whether and how to restrict Network Exposure procedures in roaming, aiming to avoid information being sent between the home network and visited network when not allowed or when not necessary.
2. How to support Capability Exposure to the UE and Application Endpoints.
Depending on the outcome of WT#1.2 (QoS), this work task is about whether and how to integrate WT#1.2 (QoS) solutions for collaboration between the UE, applications and network in a common exposure framework. As a prerequisite for this work task, WT#1.2 (QoS) is expected to determine if specific information needs to be exchanged. This work task will cover:
a. Based on the work in WT#1.2 (QoS), whether and how to integrate solutions from WT#1.2 into a common exposure framework in 6G in order to improve awareness in applications and the UE of what information can be provided by the network.
NOTE 7: Exposure should be done in an operator-controlled manner.
NOTE 8: Solutions to this work task can be based on the control plane and/or user plane.
b. Whether there is a need to and how to have the common framework support how to discover what information can be provided by the network and authorize the network to provide specific information to the applications and the UE.
3. Whether and how to support Intent-Based Exposure.
a. Whether, how, and what intents should be supported on the northbound interface (i.e. the interface to an AF in a DN) of a common network exposure framework in 6G. The intent-based work in this work task is limited to the northbound interface of a common network exposure framework in 6G and needs to be coordinated with WT#3. AI aspects will be covered under WT#3 and will not be covered under this work task.
A.1.2.7 Network Sharing in the 6G system
Study on how to support network sharing in 6G, including the following aspects:
- How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G.
A.1.2.8 Localized service access
The scope of localized service access is to study the overall architecture design and enablers for localized service access in 6G, which consists of the following:
1. Whether and how to support localized service access provided via PLMN, and study how to perform authorization and authentication of UE for localized service access, and minimize service interruption during UE mobility, including
a. Whether, how and which aspects (e.g., provisioning, updating, retrieval) for the part of subscription (that is needed for localized service access) can be performed/managed via the NFs present locally in the network providing localized service access.
NOTE 1: Network selection and access control are not to be studied for bullet 1 and bullet 2.
NOTE 2: For the case when localized service access is provided via PLMN, solutions are expected not to introduce additional UE functionality that is specific for localized service access (i.e., anything that requires UE dependency beyond what is needed for general PLMN access).
NOTE 3: Authentication aspects need to be coordinated with SA3
2. Study whether and how to make use of 5G NPN (SNPN and PNI-NPN) for localized service access in 6G.
NOTE 4: Which of the existing features will be supported will be determined during the study.
NOTE 5: Access control principles defined for NPN (SNPN and PNI-NPN) in 5G are assumed to be reused. Network selection principles defined for SNPN are assumed to be re-used, but remit stays within CT1.
NOTE 6: Session and service continuity between PLMN and SNPN using direct interface between PLMN and SNPN is out of scope of this work task.
A.1.2.93 WT FWA Scope
Study support for Fixed Wireless Access in 6G:
1) Analyse issues encountered in 5G deployments to efficiently support FWA and determine requirements to be taken by other WT for 6G. The result of this analysis will serve as the basis for architectural requirements to relevant Key Issues related with WT 1.1 and WT 1.2.
NOTE: As the result of this analysis will serve as the basis for architectural requirements to Key Issues related with other Work Tasks, this analysis needs to conclude for June 2026.
A.1.3 Work Task 1.3: Non-3GPP access
Study whether and how to support and/or enhance non-3GPP access in 6G as well as session continuity between 3GPP access and non-3GPP access.
NOTE 1: The UE can access the 6G CN via non-3GPP access even if there is no 3GPP access available.
NOTE 2: Coordination with SA3 for authentication aspects will be needed for this WT.
NOTE 3: The dependency/interaction of non-3GPP access and 3GPP access should be minimized.
WT#1.3.1. For non-3GPP access:
1. Study how to support untrusted non-3GPP access in 6G System architecture.
2. Study how to support service continuity between 3GPP access and non-3GPP access in the above bullet(s).
3. Study how to support Interworking aspects between 5GS and 6GS related to non-3GPP access.
NOTE 4: Coordination with other WTs is needed.
NOTE 5: Solutions to above bullets may support connectivity via non-3GPP access only.
NOTE 6: Solution discussion on Simultaneous connectivity via 3GPP and non-3GPP access with only per flow granularity can only start from SA2#175, but with low priority at SA2#175 if time allows.
WT#1.3.2. For Non-Seamless WLAN Offload:
1. How to support UE policy necessary for Non-Seamless WLAN Offload (NSWO).
A.1.4 Work Task 1.4: 6G Essential Services
Study whether and how to support and/or enhance the essential/regulatory services (i.e. voice, Messaging, location services, Emergency services, MPS, Mission Critical services, PWS) in 6G.
A.2 Work Task 2: Migration and Interworking
Study migration and interworking, including
1. How to support migration to 6GS
2. How to support interworking with 5GS
3. Whether and how to support interworking with EPS
NOTE 1: Whether to support interworking with EPS will depend on SA1 requirement.
4. How to support interworking between 6GS and 4G/5G NTN/satellite access that use EPS/5GS.
NOTE 2: Interworking with 2G/3G are not considered in this study. Interworking between 6GS and 5GS is required to work even if the UE has previously registered in 2G, 3G or 4G.
NOTE 3: The detailed migration study scope and migration options will be coordinated and aligned with RAN.
NOTE 4: Additional migration options beyond stand-alone, MRSS and inter-RAT mobility between NR and 6GR, will be studied no earlier than June 2026 in alignment with TSG RAN (if needed).
NOTE 5: It is assumed that interworking for roaming is within the scope of this work task.
NOTE 6: This work task focuses on general interworking procedures. The specific interworking aspects studied in other WTs (if any) need to follow the general interworking procedures.
A.3 Work Task 3: AI
A.3.0 General
Study how to support and enable use of AI in 6G (e.g. AI agent, AI framework).
NOTE: The term AI agent refers to the general concept of agents autonomously performing tasks on behalf of users, systems, and/or applications. As the SA1 work is still in progress, adapting the definition of AI agent from SA1 and the use of the term AI agent will be determined as part of the study. AI agent does not imply any specific solution.
A.3.1 WT#3.1: AI for 6G architecture
The AI for the 6G architecture shall be multi-vendor interoperable, reliable and sustainable.
NOTE 1: It is assumed that operators can decide whether and which AI capabilities and technologies to deploy in their network.
Study whether and how to provide an architecture for AI to fulfil the following:
1. enable the 6G CN to leverage AI capabilities and technologies in the 6G CN (e.g. AI agent), subject to operator policies and configuration and using 6G CN functionalities available in the network:
1.1 determine how to fulfil requests from the UEs or AFs when intent is included and, in order to ensure interoperability of intents and supporting system test cases, determine the constraints on the use and expression of intents sent from the UEs and the AFs so that the intents can be processed and interpreted unambiguously by the AI capable entities in the 6G CN, and define the mechanisms required to support these constraints.
1.2 determine how to fulfil requests when intent is not included.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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 of possible improvement and simplification of network slicing.
b) Identify and address any improvements of the application traffic mapping to network slice(s)/user plane connection(s).
NOTE 1: Any feedback from network slicing deployments can be considered in order to facilitate improvements.
NOTE 2: Coordination between bullet 1b and the KI#6 on Policy is expected.
2. Study impacts of the network slicing in 6G on the interworking and migration.
NOTE 3: Impacts to RAN are possible and coordination with RAN WGs is expected.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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 to enhance user plane flexibility (by user plane function (re)selection) for different service requirements, session continuity and mobility with consideration of user plane function capability and path performance between access network and data network.
NOTE 1: This work task may require coordination with RAN WG for user plane interface.
3. Whether and how to enhance resilience, scalability, and high availability of user plane function.
NOTE 2: The outcome of this study may include architectural requirements based on which stage 3 working group can work on the user plane protocols. The stage 3 protocol aspects, including how to design and select user plane protocols, are not in the scope of stage 2.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 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 groups will determine the characteristics of AI traffic is subject to SA plenary (SA#110) decision.
NOTE 2: Coordination with KI#19 on 6G network for AI may be needed.
2. Whether and how to enhance QoS mechanisms to:
a) support QoS targets fulfilling application’s QoS requirements (e.g., dynamic QoS requirements) in a less resource intensive manner than the existing GBR, Delay Critical-GBR.
3. Study whether and what enhancements are needed to adjust the QoS targets, in case the current QoS targets cannot be met, to minimize the impacts to application operation or user experience.
4. Study whether and how to support the UE, application and network QoS collaboration to improve awareness in the 6GS of application traffic needs, e.g., traffic pattern, dynamic QoS requirements and to improve awareness in the application/UE of what can be provided by the network, e.g., maximum bitrate.
NOTE 3: Applications consist of UE aspect and DN aspects.
5. Whether and how to enhance QoS monitoring, based on the identified needs, e.g., to determine the end-to-end per-packet delay, packet loss rate between the PSA-UPF and the UE for the verification of the QoS target fulfilment.
6. Study whether and what enhancements are needed to enforce QoS differentiation, e.g., in case of frequent address change of the server, application traffic with multiplexed media flows.
NOTE 4: QoS aspects of interworking will be considered based on the KI#17 for migration and interworking.
NOTE 5: This KI will coordinate with SA WG4 and RAN WGs.
NOTE 6: The content of the 5GS QoS Framework that will be used as a starting point for discussion on 6G QoS will be determined by moderated discussion.
NOTE 7: This KI may study impacts to the QoS for 6G based on the input identified and provided by other KIs.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.6 Key Issue #6: Policy and charging control framework
| To support the Policy and charging control in 6GS, the policy and charging control framework defined in 5G for policies (i.e., SM Policy, UE Policy, AM Policy) is considered as starting point for discussion, the following aspects are to be studied:
1. Whether and how to simplify the policy and charging control framework for 6G, including:
a) whether and how to reduce the number of policy control services e.g. the same policy control association for both AM and UE policies or the number of interactions to efficiently provide policies to the different policy enforcement points.
NOTE 1: The example above does not preclude that other examples are covered in the study phase if the reason for simplification is identified.
b) whether and how to support the UE to request UE policies from the 6G CN and/or the 6G CN to provide UE policies to the UE.
2. Whether and how to consider user preferences during UE policy evaluation at UE, without conflicting with network provided UE policies.
NOTE 2: The statement that refers to considering user preferences refers to the ability to influence the evaluation of UE policies.
3. Whether and how to improve the External Parameter Provisioning aspects of policy control for 6G.
NOTE 3: General Authorization of the external parameter provisioning is handled in the KI#7 - Network Exposure.
4. Whether and how to improve events notification about policies to the AF (e.g. to notify the AF that policy and charging control, e.g. charging key changed).
5. Whether and what parameters the UE can provide as input for PCC decision, e.g. related to QoS control to the 6G CN. The UE input for PCC decision related to QoS is based on the progress in KI#5 – QoS.
NOTE 4: The example above does not preclude that other examples are covered in the study phase if those are identified.
NOTE 5: The AF input for session management defined in 5G can be treated as starting point for discussion.
NOTE 6: The UE can decide if and when to provide the above input the request to the network.
NOTE 7: The UE is not assumed to know whether AF input for QoS is available.
NOTE 8: Whether the UE can provide any input for PCC decisions as the AF provides for UE or AM policies are out of the scope of this bullet.
NOTE 9: The assumption is that either the AF or the UE provides input for PCC decision for e.g. QoS control.
The following notes are applicable to all bullets in this key issue:
NOTE 10: If the energy related information, either based on 5G mechanisms, or 6G mechanisms, is available then this key issue will study how to take energy efficiency and consumption aspects into account for policy decisions.
NOTE 11: This key issue has IWK aspects that are scoped under KI#17 – Migration and Interworking.
NOTE 12: This key issue can study potential enhancements to the policy control framework for 6G services based on the input identified and provided by other key issues.
NOTE 13: This key issue depends on the overall 6G roaming architecture based on the output of KI#1 - Support of 6G Control signalling. Solutions for this key issue will address roaming if applicable.
NOTE 14: Any improvements of the application traffic mapping to network slice(s)/user plane connection(s) are out of the scope of this key issue.
NOTE 15: Identify and address any feedback from markets where policy control framework technologies are already being commercially deployed.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.7 Key Issue #7: Network Exposure
| This key issue is to study whether and how to support a common network exposure framework in 6G. The capabilities that are exposed via the framework fall into one of two categories.
1. The first category is new capabilities. New capabilities refer to capabilities that are not exposed in the 5G network. This category of exposed capabilities is dependent on other key issues. This key issue will include a review of exposure requirements that derive from other key issues.
2. The second category refers to capabilities that are exposed in the 5G network and are used as a starting point for discussion of this key issue. This category of exposed capabilities may be dependent on other key issues.
Since this key issue depends on other key issues, time will not be allocated for solutions for this key issue by SA2 before SA2 #175.
NOTE 1: This key issue requires coordination with SA WG3, SA WG6, and SA WG5.
NOTE 2: This key issue has dependency on service requirements to be specified by SA WG1.
NOTE 3: Information exposure is based on operator policies/SLAs.
NOTE 4: Authorization, Privacy protection and user consent aspects require coordination with SA WG3, and application layer user consent aspects may require coordination SA WG6.
Aspects that can be studied under this key issue are:
1. How to support a common network exposure framework in 6G for the exposure of network capabilities to an AF.
a) Whether and how to support a common network exposure framework in 6G for the exposure of network capabilities to AFs, in an access independent manner (to the extent that exposure in an access independent manner is possible). The exposure framework of the 5GS (i.e. exposure via the NEF) is assumed to be the starting point for discussion of this key issue.
b) Whether and how to support co-existence with the 5G exposure framework.
NOTE 5: The common network exposure framework in 6G in SA WG2 does not duplicate the SA WG6 Framework.
NOTE 6: Examples of network capabilities include information exposure such as information about UE related events, network events, analytics, and information provisioning such as UE related network configuration parameters and service specific parameters.
c) Whether and how to support privacy protection, user consent, data anonymization, and service authorization mechanisms.
d) Whether and how to restrict Network Exposure procedures in roaming, aiming to avoid information being sent between the home network and visited network when not allowed or when not necessary.
2. How to support Capability Exposure to the UE and Application Endpoints.
Depending on the outcome of the QoS key issue, this key issue is about whether and how to integrate solutions from the QoS key issue for collaboration between the UE, applications and network in a common exposure framework. As a prerequisite for this key issue, the QoS key issue is expected to determine if specific information needs to be exchanged. This key issue will cover:
a) Based on the work in the QoS key issue, whether and how to integrate solutions from the QoS key issue into a common exposure framework in 6G in order to improve awareness in applications and the UE of what information can be provided by the network.
NOTE 7: Exposure should be done in an operator-controlled manner.
NOTE 8: Solutions to this key issue can be based on the control plane and/or user plane.
b) Whether there is a need to and how to have the common framework support how to discover what information can be provided by the network and authorize the network to provide specific information to the applications and the UE.
3. Whether and how to support Intent-Based Exposure.
a) Whether, how, and what intents should be supported on the northbound interface (i.e. the interface to an AF in a DN) of a common network exposure framework in 6G. The intent-based work in this key issue is limited to the northbound interface of a common network exposure framework in 6G and needs to be coordinated with the AI key issue. AI aspects will be covered under the AI key issues and will not be covered under this key issue.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.8 Key Issue #8: Network Sharing in the 6G system
| Study on how to support network sharing in 6G, including the following aspects:
1) How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.