Mobile core network assisted device-originated-autonomous (do-a) device-to-reader (D2R) traffic handling

WO2026213629A3PCT designated stage Publication Date: 2026-11-12FUTUREWEI TECHNOLOGIES INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/041231
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-08-14
Filing Date
2026-08-13
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G networks lack efficient radio resource management, periodic D2R transmission support, energy information, and failure detection mechanisms for Device-Originated-Autonomous (DO-A) capable AIoT devices, leading to inefficient resource allocation and increased signaling traffic.

Method used

The mobile core network provides DO-A assistance information to the RAN, including device type, D2R data size, traffic periodicity, and energy characteristics, enabling non-contention-based scheduling and synchronized timer-based mechanisms for autonomous D2R transmissions, with failure detection and handling.

Benefits of technology

This approach improves radio resource management, reduces signaling overhead, and enhances network efficiency by predicting and pre-allocating resources, ensuring timely and energy-aware scheduling, and handling device failures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026041231_12112026_PF_FP_ABST
    Figure US2026041231_12112026_PF_FP_ABST
Patent Text Reader

Abstract

In accordance with implementations, a first network function entity receives from an application function entity an ambient Internet of things (AIoT) service request for an AIoT service to an AIoT device supporting a device-originated-autonomous (DO-A) transmission capability. The AIoT service request comprises DO-A service assistance information. The first network function entity sends to a second network function entity, a request message for the AIoT service with second DO-A service assistance information related to the AIoT device. The second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.
Need to check novelty before this filing date? Find Prior Art

Description

METHODS AND SYSTEMS FORMOBILE CORE NETWORK ASSISTED DO-A D2R TRAFFIC HANDLING CROSS-REFERENCE TO RELATED APPLICATION

[0001] This patent application claims the benefit of U.S. Provisional Application No.63 / 864,134, filed on August 14, 2025, and entitled “Mechanism for Mobile Core Network Assisted DO-A D2R Traffic Handling,” application of which is hereby incorporated by reference herein as if reproduced in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communications, and, in particular implementations, to systems and methods for mobile core network assisted device-originated-autonomous (DO-A) AIoT device to AIoT reader (D2R) traffic handling.BACKGROUND

[0003] There are three types of ambient Internet of Things (loT) (AIoT) devices being evaluated / considered by the Third Generation Partnership Project (3GPP) for Release 20 (Rel-20).

[0004] The first type is Device 1. As standardized in the Rel-19 work item (WI) Ambient_IoT_Solutions, Device 1 has ~i pW peak power consumption, has energy storage, has initial sampling frequency offset (SFO) up to ioxppm, and has neither AIoT Reader to AIoT Device (R2D) nor D2R amplification in the device. Device l’s D2R transmission is backscattered on a carrier wave provided externally.

[0005] The second type is Device 2b. Device 2b has < a few hundred pW peak power consumption, has energy storage, intermediate frequency (IF) envelope detector receiver or zero IF (ZIF) receiver, initial SFO up to ioYppm, R2D and / or D2R amplification in the device. Device 2b’s D2R transmission is generated internally by the device.

[0006] The third type is Device C. Device C has < 1 mW to < 10 mW peak power consumption, has energy storage, IF envelope detector receiver or ZIF receiver, initial SFO up to ioYppm, R2D and / or D2R amplification in the device. Device C’s D2R transmission is generated internally by the device.

[0007] 3GPP radio access network (RAN) WG has identified two types of topologies for AIoT as defined in TR38.848. FIG. 1 shows AIoT Topology 1. FIG. 2 shows AIoT Topology 2. For AIoT Topology 2, the intermediate node can be a user equipment (UE) under the network control.FW 6000773PCT02 1[ooo8] 3GPP Rel-19 only supports AIoT Topology 1 and AIoT Device type 1. An active device (e.g., Device 2b and / or Device C) and Topology 2 will be supported by 3GPP in Rel-20. The device supports DO-A access.SUMMARY

[0009] Technical advantages are generally achieved, by implementations of this disclosure which describe methods, apparatus, and systems.

[0010] In accordance with implementations, a first network function entity receives from an application function entity an ambient Internet of things (AIoT) service request for an AIoT service to an AIoT device supporting a device-originated-autonomous (DO-A) transmission capability. The AIoT service request comprises DO-A service assistance information. The first network function entity sends to a second network function entity, a request message for the AIoT service with second DO-A service assistance information related to the AIoT device. The second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.

[0011] In some implementations, the request message may be sent in response to the AIoT service request.

[0012] In some implementations, the second DO-A service assistance information may further include periodicity information of transmitted data.

[0013] In some implementations, the periodicity information may indicate whether the transmitted data is initiated by the AIoT device periodically or polled periodically.

[0014] In some implementations, the transmitted data may be any data sent by the AIoT device.

[0015] In some implementations, the transmitted data may include at least one of a registration message or application level data.

[0016] In some implementations, the second DO-A service assistance information may be stored locally in the first network function entity or configured by the application function entity.

[0017] In some implementations, the first network function entity may send the request message to the second network function entity for a plurality of periodic D2R transmissions. The second network function entity may retain a periodic transmission schedule and allocate radio resources at each interval without a separate request from the first network function entity for each transmission.

[0018] In some implementations, the first network function entity may receive from the second network function entity AIoT timer information. The AIoT timer informationFW 6000773PCT02 2may define a common clock shared among the first network function entity, the second network function entity, and the AIoT device.

[0019] In some implementations, the second DO-A service assistance information may further indicate a waiting time threshold. The waiting time threshold may indicate a duration after which the second network function entity sends a notification to the first network function entity to indicate completion status of a task to receive D2R transmission from at least one AIoT device.

[0020] In some implementations, the notification may include a completion notification in response to receiving the D2R transmission from the at least one AIoT device within the duration.

[0021] In some implementations, the notification may include a failure notification in response to not receiving all of the D2R transmission from the at least one AIoT device within the duration.

[0022] In some implementations, the notification may be included in a dedicated container message being delivered between the AIoT device and the application function entity. The dedicated container message may be used for conveying application level information.

[0023] In some implementations, the second network function entity may comprise at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

[0024] In accordance with implementations, an AIoT device receives from a second network function entity device-originated-autonomous (DO-A) service configuration information for an AIoT service. The AIoT device supports a DO-A transmission capability. The AIoT device sends to the second network function entity a device-to-reader (D2R) message autonomously based on the DO-A service configuration information.

[0025] In some implementations, the DO-A service configuration information may comprise AIoT timer information defining a common clock shared among the AIoT device, the second network function entity, and a first network function entity. The AIoT device may send the D2R message at a time determined based on the common clock.

[0026] In some implementations, the AIoT timer information may comprise at least one of a transmission start time expressed in AIoT timer units or a periodic transmission interval expressed in the AIoT timer units.

[0027] In some implementations, the AIoT device may synchronize an internal clock of the AIoT device with the common clock based on broadcast AIoT timer information received from the second network function entity.FW 6000773PCT02 3

[0028] In some implementations, the AIoT device may send to the second network function entity a D2R notification message indicating an error status.

[0029] In some implementations, the second network function entity may comprise at least one of a next generation-radio access network (RAN) (NG-RAN) unit or an AIoT reader device.

[0030] In accordance with implementations, a second network function entity receives from a first network function entity, a request message for an ambient Internet of things (AIoT) service with second device-originated-autonomous (DO-A) service assistance information related to an AIoT device supporting a DO-A transmission capability. The second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.

[0031] In some implementations, the request message may be received in response to an AIoT service request received by the first network function entity.

[0032] In some implementations, the second DO-A service assistance information may further include periodicity information of transmitted data.

[0033] In some implementations, the periodicity information may indicate whether the transmitted data is initiated by the AIoT device periodically or polled periodically.

[0034] In some implementations, the transmitted data may be any data sent by the AIoT device.

[0035] In some implementations, the transmitted data may include at least one of a registration message or application level data.

[0036] In some implementations, the second DO-A service assistance information may be stored locally in the first network function entity or configured by an application function entity.

[0037] In some implementations, the second network function entity may receive the request message from the first network function entity for a plurality of periodic D2R transmissions. The second network function entity may retain a periodic transmission schedule and allocate radio resources at each interval without a separate request from the first network function entity for each transmission.

[0038] In some implementations, the second network function entity may send to the first network function entity AIoT timer information. The AIoT timer information may define a common clock shared among the first network function entity, the second network function entity, and the AIoT device.

[0039] In some implementations, the second DO-A service assistance information may further indicate a waiting time threshold. The waiting time threshold may indicate a duration after which the second network function entity sends a notification to the first FW 6000773PCT02 4network function entity to indicate completion status of a task to receive D2R transmission from at least one AIoT device.

[0040] In some implementations, the notification may include a completion notification in response to receiving the D2R transmission from the at least one AIoT device within the duration.

[0041] In some implementations, the notification may include a failure notification in response to not receiving all of the D2R transmission from the at least one AIoT device within the duration.

[0042] In some implementations, the notification may be included in a dedicated container message being delivered between the AIoT device and an application function entity. The dedicated container message may be used for conveying application level information.

[0043] In some implementations, the second network function entity may comprise at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

[0044] In accordance with implementations, a second network function entity sends to an ambient Internet of things (AIoT) device, device-originated-autonomous (DO-A) service configuration information for an AIoT service. The AIoT device supports a DO-A transmission capability. The second network function entity receives a device-to-reader (D2R) message sent by the AIoT device autonomously based on the DO-A service configuration information.

[0045] In some implementations, the DO-A service configuration information may comprise AIoT timer information defining a common clock shared among the AIoT device, the second network function entity, and a first network function entity. The second network function entity may receive the D2R message at a time determined based on the common clock.

[0046] In some implementations, the AIoT timer information may comprise at least one of a transmission start time expressed in AIoT timer units or a periodic transmission interval expressed in the AIoT timer units.

[0047] In some implementations, the AIoT device may synchronize an internal clock of the AIoT device with the common clock based on broadcast AIoT timer information sent by the second network function entity.

[0048] In some implementations, the second network function entity may receive from the AIoT device a D2R notification message indicating an error status.

[0049] In some implementations, the second network function entity comprises at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.FW 6000773PCT02 5

[0050] The disclosed techniques provide improved radio resource management and signaling efficiency for Ambient loT (AIoT) networks supporting Device-Originated-Autonomous (DO-A) capable devices. By enabling the AIoT network function to proactively deliver DO-A service assistance information (e.g., device type, D2R transmission data size, DO-A capability, traffic periodicity, energy characteristics, and / or failure handling parameters) to the RAN and AIoT reader, the disclosed techniques allow the network to predict and pre-allocate radio resources for autonomous D2R transmissions without requiring per-transmission triggers from the core network. The disclosed techniques further provide two non-contention-based scheduling mechanisms: a reader-driven polling scheme that eliminates repeated core network signaling for periodic transmissions, and a synchronized AIoT timer-based scheme that enables autonomous device-side scheduling without explicit per-transmission triggering from the network. Additionally, the disclosed techniques provide energy-aware resource scheduling by informing the RAN of device energy sources and availability, and introduce failure detection and handling mechanisms that allow the network to identify unresponsive DO-A devices and take corrective action, thereby reducing wasted radio resources and improving overall network efficiency.BRIEF DESCRIPTION OF THE DRAWINGS

[0051] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0052] FIG. 1 shows AIoT Topology 1;

[0053] FIG. 2 shows AIoT Topology 2;

[0054] FIG. 3 illustrates AIoT system architecture for Topology 1;

[0055] FIG. 4 illustrates a control plane based protocol stack for Topology 2;

[0056] FIGs.5A-5B show an example message flow for DO-A AIoT device deviceoriginated periodic D2R transmission with traffic assistance information, in accordance with some implementations;

[0057] FIGs. 6A-6B show an example message flow for DO-A AIoT device deviceoriginated event-driven D2R transmission with traffic assistance information, in accordance with some implementations;

[0058] FIG. 7 shows an example message flow for DO-A AIoT device deviceoriginated sensor data transmission with traffic assistance information, in accordance with some implementations;FW 6000773PCT02 6

[0059] FIGs. 8A-8B show an example message flow for device-originated sensor data transmission with energy assistance information, in accordance with some implementations;

[0060] FIG. 9 shows an example flow diagram performed by a base station (e.g., an NG-RAN) or an AIoT reader, in accordance with some implementations;

[0061] FIG. 10A illustrates an example flowchart of operations performed by a first network function entity, in accordance with some implementations;

[0062] FIG. 10B illustrates an example flowchart of operations performed by an AIoT device, in accordance with some implementations;

[0063] FIG. 10C illustrates an example flowchart of operations performed by a second network function entity, in accordance with some implementations;

[0064] FIG. 10D illustrates an example flowchart of operations performed by a second network function entity, in accordance with some implementations;

[0065] FIG. 11 illustrates an example communications system, in accordance with some implementations;

[0066] FIG. 12 illustrates an example communications system, in accordance with some implementations;

[0067] FIGs. 13A and 13B illustrate example devices that may implement the methods and teachings according to this disclosure, in accordance with some implementations; and

[0068] FIG. 14 is a block diagram of a computing system that may be used for implementing the devices and methods disclosed herein, in accordance with some implementations.

[0069] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The figures are drawn to clearly illustrate the relevant aspects of the implementations and are not necessarily drawn to scale.DETAILED DESCRIPTIONS

[0070] The first technical problem with the current systems is that the existing standard lacks efficient radio resource management for DO-A capable AIoT device (DO-A device). In Rel-19, DO-A access was not supported. One reason is that an AIoT type 1 Device backscatters D2R transmissions in response to receiving an R2D signal (e.g., a trigger signal) from AIoT reader.

[0071] However, in Rel-20, for a DO-A device, the existing AIoT reader or next generation RAN (NG-RAN) may not have knowledge of the incoming D2R transmission FW 6000773PCT02 7and cannot plan and schedule radio resources efficiently. A DO-A device can transmit D2R data to an AIoT reader autonomously without a trigger from AIoT reader. A DO-A device can use contention-based random access solutions to compete for a limited common D2R resource for D2R transmission, but this can significantly impact the access performance of the DO-A devices, especially when the DO-A devices compete for reasons when the number of AIoT devices is high (e.g., in one use case, a DO-A device (e.g., a fire sensor) has a high priority message that may take additional time / attempts to get access while there are large number of AIoT devices also trying to access the reader around the same time). On the other hand, overprovisioning the common D2R resources for better service quality can also lead to lower resource utilization rate and low-quality of service for other AIoT devices or other mobile services which share the same spectrum.

[0072] Another technical problem is that the existing mechanisms in the Rel-19 standards do not support periodic D2R transmission efficiently. The existing standard only supports the AIoT device D2R transmission based on the backscatter using the external carrier wave (CW). So, every D2R transmission requires a command message from the core network (e.g., AIoT Function (AIoTF)) to AIoT reader for each D2R transmission. Many DO-A use cases require periodic D2R transmission from an AIoT device without a trigger from core network for each of its D2R transmissions. So, if the existing mechanism is applied for such use cases, the AIoTF would send commands to trigger D2R transmission for each transmission cycle, which creates unnecessary signaling traffic in the network and impacts overall network performance, especially, considering that traffic is shared with other control messages for other mobile services in the control plane.

[0073] A third technical problem is the lack of energy information of the AIoT devices for the AIoT reader or NG-RAN to make better resource decisions.

[0074] Also, compared with Device 1 which has very limited energy storage, it is expected that an active device (e.g., Device 2b / C) has higher energy storage capability as well as support of different sources to harvest energy (in addition or besides RF energy). This extra energy storage capability and energy sources allows an AIoT device to rely less on the energy provided by the RAN or the AIoT readers. Because the RAN or the AIoT readers do not know the energy information of the devices, the AIoT readers or the RAN cannot treat those AIoT devices according to their energy status, which leads to low efficiency of the AIoT readers or the RAN resource allocation. For example, if a device harvests solar energy, it may be unavailable due to lack of energy during the night time. The AIoT reader may not allocate resources to try to reach the device until the daytime when the AIoT device can harvest solar energy.FW 6000773PCT02 8

[0075] The fourth technical problem is the lack of AIoT device failure detection and handling mechanism. Even if an AIoT device can send an indication of a device unavailability to the AIoT reader when it does not have enough energy for future D2R transmissions, there are no other mechanism for an AIoT reader to detect the failure of a DO-A AIoT device and take action accordingly. For example, an AIoT reader may periodically schedule resources and receive periodic sensing data from a DO-A enabled device, but there is no way for the AIoT reader to stop scheduling resources when a sensor has a failure and is unable to transmit data anymore. AIoT reader radio resources are wasted in this case.

[0076] There are no solutions in the current 5G network to support DO-A device and address the technical problems mentioned above.

[0077] This disclosure describes technical solutions for the mobile core network and the RAN / AIoT reader to coordinate on resource management for the D2R transmission from a DO-A device, with core network providing assistance information to the RAN regarding the DO-A device and the traffic characteristic and energy capability associated with the DO-A device, which can assist the RAN to plan and allocate resources for DO-A device.

[0078] A DO-A device can be supported in both Topology 1 and Topology 2 architectures. The system architecture for Topology 1 is defined in TS23.369 as illustrated in FIG. 3. In FIG. 3, the AIoT RAN 302 can be either an AIoT reader or contain AIoT reader functionality and other AIoT management functionalities. A potential control-plane based protocol stack for Topology 2 will most likely be defined in 3GPP release 20 based on the study conclusion of TR23.700.13, illustrated in FIG. 4.

[0079] In accordance with implementations, new DO-A assistance information can be delivered from an AIoTF to one or more AIoT reader(s) or NG-RAN(s) which are responsible for the radio resource allocation for the AIoT readers. The DO-A assistance information can include various information elements, which can be provided entirely or partially by the Application Function (AF), Operations Administration and Maintenance (OAM), or obtained from the AIoT Device Management Function (ADM) or Unified Data Management (UDM).

[0080] The DO-A assistance information contains the following information elements.

[0081] The D2R traffic time information includes the following.• Device type indication. This indication specifies the type of the AIoT device, such as Device 1, Device 2b, or Device C. This indication can also indicate inactive devices which backscatter on to the CW and the active AIoT device which creates its own carrier for transmission. The AIoT reader may utilize this information to allocate FW 6000773PCT02 9radio resources based on device type. For example, when a reader conducts inventory for a set of AIoT devices, the reader can group the AIoT devices based on their device types and send different group paging messages using R2D resources based on the device types.• DO-A capability indication. This indicates whether an AIoT device supports DO- A capabilities. It helps the RAN or the AIoT reader in appropriate resource scheduling. For example, a DO-A-capable device can be an active device which generates its own carrier for D2R transmission, while type 1 AIoT devices uses externally provided carrier waves for their backscattered transmissions.• Estimated DO-A D2R transmission data size. This information specifies the anticipated size of each D2R transmission. This estimate applies to both periodic transmissions and event-driven, one-time transmissions. There can be two types of data size, one is for periodic transmissions, and one is for one-time event-driven transmissions.

[0082] Number of DO-A AIoT Devices: This field indicates how many DO-A-enabled AIoT devices are involved in an AIoT service request which can be associated with a correlation ID. When there are multiple DO-A devices transmitting on allocated resources, conflicts or resource limitation can occur. A scheduling ordering information can be provided to the AIoT reader or the AIoTF based on the policy. This information can help the AIoT reader to schedule resource accordingly. The ordering information can include the priority of the AIoT device within this AIoT service, D2R transmission ordering for those devices. The other option to handle this high number of AIoT devices is that the AIoTF or the AIoT reader may group those AIoT devices into smaller subgroups, and schedule different D2R transmission intervals and resources accordingly. For example, if the interval for D2R transmission is once every 10 minutes, the AIoT reader may provide resources for those device every 5 minutes for different subgroup of AIoT devices, to separate the large number of D2R transmission into different intervals.

[0083] In accordance with implementations, two types of non-contention-based radio resource scheduling for DO-A D2R traffic can be provided.

[0084] The first type is Type 1 Scheduling. An AIoT reader initiates polling and resource allocation for DO-A devices via a paging message shortly before the device transmission time, similar to Device-Originated Dedicated Traffic Transmission (DO-DTT). This approach does not require the AIoT device to maintain periodic transmission schedules or internal clocks. Instead, the AIoT reader retains periodic transmission schedules and actively provides resources for device transmissions at each interval (compared to using the existing contention free random access (CFRA) message, a newFW 6000773PCT02 10dedicated command which provides contention resource to AIoT device at each interval can be introduced).

[0085] There can be another option for reader to schedule the resource for a DO-A enabled device. During the D2R transmission window, instead of using CFRA to allow resource for the D2R transmission for the specific AIoT device, the AIoT reader uses contention based random access (CBRA) to poll the AIoT devices for transmission. The DO-A-enabled device(s) first performs a contention based random access using resources reserved for DO-A devices from the reader and transmits D2R. If there is a segmentation bit set in the D2R message, a reader can provide additional resources using commands. This Type 1 Scheduling solution can be used for the case of event-driven D2R transmission, large sized D2R transmission, or expected large number of AIoT devices D2R transmission during the transmission window.

[0086] The second type is Type 2 Scheduling. The AIoT device, AIoT reader, and the AIoTF synchronize using a common clock. D2R transmissions are scheduled autonomously based on this synchronized timing. Under this solution, the AIoT device transmits periodically according to the common clock, utilizing pre-allocated radio resources without explicit triggering from the AIoT reader (e.g., every 10 AIoT clock units). Compared to the Type 1 Scheduling, the Type 2 Scheduling maybe more complex for the AIoT device to implement and may not be practical for inclusion in near-term 3GPP releases, such as Release 20.Type 1 Scheduling DO-A D2R transmission traffic pattern information

[0087] For Type 1 Scheduling, the following DO-A D2R transmission traffic pattern information is provided from an AIoT Function (AIoTF) to the AIoT reader or NG-RAN.

[0088] Expected DO-A D2R transmission traffic pattern information. A DO-A capable device generates its own transmissions without relying on external CW. A DO-A transmission can be one-time D2R transmission or periodic transmission for a defined period.

[0089] If the DO-A traffic is periodic traffic, the AIoTF can provide one AIoT-command service request to a DO-A AIoT device(s) and its AIoT reader to start the DO-A service. The DO-A device can then send data to the AIoT reader autonomously and periodically without a service request from the AIoTF for each period.

[0090] With this information, it not only helps the AIoT reader and the NG-RAN to better allocate the resource more efficiently and precisely by predicting the incoming traffic but also helps to significantly reduce the signaling traffic between core network and the NG-RAN / AIoT reader. This traffic pattern information can include the following.• Indication if the DO-A D2R transmission is a periodic transmission or not. The periodic D2R transmission can be either for the sensor to send collected data FW 6000773PCT02 11periodically, or for polling some monitoring device for status checking. If it is a periodic transmission, the following information can also be provided.• Expected DO-A D2R transmission cycle start time. This start time can be the approximate time when D2R transmissions from DO-A devices is expected (e.g., 12:30pm) or an offset starting from a defined point, such as 10 min after an inventory / command message sent to the AIoT device. The AIoT reader can use this time to start the paging procedure to trigger the DO-A transmission. If the DO-A D2R transmission is one time transmission, this start time information can be also provided to the AIoT reader from the AIoTF to indicate the approximate D2R transmission time.• Periodic D2R transmission interval. This information define the time interval between transmissions, enabling the AIoT reader to schedule resources and paging messages efficiently.• Expected DO-A D2R completion time. This information can be the approximate end time of the periodic DO-A service, or the total number of the D2R transmission cycles.If the transmission is a periodic transmission, the AIoT reader may select a long-lasting access stratum (AS) identifier (ID) for the AIoT message which can be used multiple times during one DO-A service, instead of changing the AS ID for each D2R transmission transaction.• Delayed transmission indication with delayed start time. This information indicates if the D2R traffic can be expected in a delayed window after an AIoT command or an AIoT inventory message being sent to the AIoT device. The command / inventory can trigger a DO-A device to send delayed D2R data, such as triggering a sensor AIoT device to collect required sensing data and send the data in a defined time.An expected D2R transmission start time is provided by AF or AIoTF and it can be associated with a correlation ID which is used by the command. AIoT reader and RAN can mark the time when the command is sent to AIoT device and polling and allocate the D2R resource for the AIoT device near the window-time expiration. • Indication of periodic polling for event-driven D2R transmission with optional assistance information. This information can include D2R transmission size and periodic polling interval information. This information is for the use cases in which a DO-A device transmits D2R after it is triggered by certain events, such as a smart grids sensor detecting an anomaly and alarm and sending a notification to the server (e.g., required detection-and-report time is in the range of 5-15 minutes and also several seconds for critical equipment) (TR 22.840). With this indication, the AIoTFW 6000773PCT02 12reader periodically polls the AIoT device for potential D2R transmission without allocating the radio resource for the D2R transmission resource according to the D2R transmission size. After receiving the confirmation from the AIoT device for D2R transmission, the AIoT reader allocates radio resources for the D2R transmission. The event-driven D2R transmission can be one-time transmission or multipletransmissions during the whole life-cycle of the AIoT service.Type 2 Scheduling DO-A D2R transmission traffic pattern information

[0091] For Type 2 Scheduling, there is similar DO-A D2R transmission traffic pattern information but the time is based on AIoT reader’s AIoT timer, whose parameters are provided to the AIoT reader / NG-RAN from AIoTF.

[0092] Due to the limited accuracy of the clock in the AIoT device, it is unrealistic to use the normal clock as defined in the existing standard for actual time. Instead, a new AIoT clock and time synchronization mechanism (more details are described below) is introduced to allow the DO-A device, the AIoT reader, and the network to be synchronized with a common AIoT timer with which DO-A device can transmit D2R data. One of the implementations of this AIoT timer can be the number of the fixed duration time slots that have elapsed since the timer started. The length or granularity of each time slot is defined by the AIoT reader which may need to coordinate with the RAN and the AIoTF (e.g., one timer slot can span multiple reader’s R2D transmission slots). The AIoTF can map the approximate AIoT device R2D transmission time to this AIoT timer and provide the expected transmission time slot information to the AIoT reader and the AIoT device(s).

[0093] There can be two types of AIoT timer-based D2R transmission.• 1. The expected transmission time using the reader AIoT timer when D2R transmission from devices is expected (e.g., 30,000 time units of reader AIoT timer). Because the AIoTF, the AIoT device, the RAN, as well as the AIoT reader have been synchronized with the AIoT synchronization timer, the AIoTF can translate the D2R transmission time from actual time into the AIoT transmission time slot using the AIoT synchronization timer and send this time slot information to the AIoT Reader / RAN and the AIoT device. Therefore, the RAN or the AIoT reader can prepare resources accordingly. If the D2R transmission is periodic traffic, the expected transmission time can indicate the first start time of the periodic transmission and the interval of each period.• 2. Delayed transmission indication with delayed start time using reader AIoT timer.The command / inventory service can trigger a DO-A device to send D2R data later in a defined delay time, such as triggering a sensor AIoT device to collect required sensing data and sending the data in 10 minutes. The start time can be associated FW 6000773PCT02 13with a correlation ID which is used by the command. The AIoT reader / RAN can prepare to start the wait time using AIoT timer when a command / inventory service with the same correlation ID is sent to a DO-A device in a specific time slot of the AIoT time. The AF may assign a time window for the DO-A device to collect and send back the data. The DO-A device can send the data after the time window expires. The AF can provide this time window information to the AIoTF which provides to RAN / AIoT reader as assistance information.

[0094] For the Type 2 Scheduling approach, the AIoT device receives the same traffic pattern information, allowing it to autonomously schedule D2R transmissions based on this information.

[0095] Failure handling information. This information provides guidance for reader / NG-RAN to handle error scenarios for the DO-A enabled device (e.g., no D2R transmission during the scheduled time for periodic transmission, or have not received any D2R transmission from the device for a defined period including no receiving unavailability indication from the AIoT device). The information can include the following.• The number of consecutive windows without a D2R transmission from a specific device for a periodic transmission AIoT service from a DO-A enabled device before AIoT reader sends failure notification to the AIoTF (e.g., the AIoT device does not transmit in five transmission windows). If the AIoT reader does not receive any D2R transmission from the DO-A enabled device for several consecutive windows, the AIoT reader can send a failure message to notify the AIoTF which can take corresponding actions based on the configured profile or subscription of the device, or the policy from the AF.• The waiting time for not receiving any D2R transmission from a DO-A enabled device, before the AIoT reader sends the failure notification to the AIoTF (e.g., 60 minutes of waiting time). For a DO-A enabled device whose D2R transmission is expected within a defined period (e.g., a sensor sending data periodic transmission or even-trigger sensor responding to periodic polling from network), an AIoT reader can consider it lost the connection with the AIoT device if there is no D2R transmission received from the device during this period. The AIoT reader can send failure notification to the AIoTF.

[0096] Energy information. The energy information can be also used for all types of AIoT devices, is not only restricted to a DO-A device. The energy information can include the following information.FW 6000773PCT02 14• Energy storage capability and capacity. This information provides details about how much energy an AIoT device can store and its overall energy capacity.• Energy Sources. This information specifies the types of energy sources supported by the AIoT device, such as solar power, batteries, or wireless energy harvesting. This information helps an AIoT reader or the RAN assess the device’s availability. For example, an AIoT reader may predict that a solar-powered device will be unavailable at night and consequently not schedule any paging and D2R transmission radio resources for the AIoT device during that period.• Wait time for re-connect. This is an indication provided by the AIoT device to the AIoT reader regarding if it is available for D2R transmission with sufficient energy for D2R transmission. If an indication shows that energy for communication is currently unavailable, the AIoT device or an AIoTF may provide an additional waiting time to the AIoT reader. This waiting time allows the AIoT reader to reschedule resources after the indicated period, during which the AIoT device can accumulate sufficient energy from available sources like solar or wireless harvesting.New AIoT DO-A synchronization time between AIoT device and AIoT reader for DO-A D2R transmission for type 2 radio resource scheduling

[0097] To prepare for predictable DO-A D2R traffic (such as periodic or prescheduled transmissions), AIoT devices, AIoT readers, and AIoTFs can synchronize their clocks. However, given the simplicity of AIoT devices, their clocks cannot achieve the same accuracy as more complex cellular devices, nor can they employ sophisticated synchronization mechanisms. To address this, a new more efficient AIoT timer and synchronization method are described herein.

[0098] The AIoT timer operates per AIoT reader and includes fixed-duration time slots configurable either by the network or specific implementation. Each time slot is identified by an index number. The AIoT reader (NG-RAN or intermediate node) broadcasts this AIoT timer information to each AIoT device within its coverage area. DO-A devices use this broadcasted timer information to synchronize their internal clocks with the AIoT reader. A detailed description of this solution is provided below.DO-A enabled device failure detection and handling

[0099] If a failure occurred in a DO-A device which is related to the communication with the mobile network, there can be several methods for reporting the failure to the mobile network or detecting the failure by the mobile network. Some corresponding actions can be taken based on the configured profile or subscription of the device, or the policy from the AF.FW 6000773PCT02 15[oioo] The AF can receive DO-A device status via the command status field in the command response message. If the failure in the AIoT device requires the termination of the service from this AIoT device, the AF can either use the existing standardized mechanism to disable the DO-A device permanently, or send a new type of command (command type: service termination) to the AIoTF and the DO-A device to terminate the service until the AF restarts the service for this DO-A device at a later time.

[0101] Unlike the existing mechanism in which a D2R message from an AIoT device is in response to the R2D message from an AIoT reader, a new AIoT D2R notification message is introduced for a DO-A device to be sent to an AIoT reader with or without the R2D message from the AIoT reader. This notification message is provided by DO-A device to report its status to the reader or the network. This report can be configured by the AF for periodic or event trigger transmission. The AIoTF can use the assistance information (defined above) to assist a reader to schedule the radio resources for the D2R transmission based on this notification message. The AIoT reader can set up a periodic contention-based transmission window for the DO-A enabled device to send urgent status report, and the DO-A device can use a contention-based mechanism to send the notification without the reader allocating the resource in advance if it is urgent. The AIoT reader or the AIoTF can use provisioned failure handle policy to handle the failure reported in the notification message.

[0102] If the AIoT device cannot send any failure indication to the reader, the AIoTF, or the AF, the AIoT reader can use the failure-handling assistance information defined above to handle the failure.

[0103] FIGs. 5A-5B show an example message flow for DO-A AIoT device deviceoriginated periodic D2R transmission with traffic assistance information (Type 1 Resource Scheduling), in accordance with some implementations.

[0104] At the operations 501, the AF 552 sends an AIoT service request for AIoT device 1552 (AIoT device 1, read command, (application data: report sensor data periodically, at the beginning of every hour), assistance information: device type C, DO-A capable, periodic type D2R, periodic D2R data size (2oobit), interval every 1 hour, 10 messages, start time (9am)). Instead of reusing the existing read command, there can be a new AIoT command to handle data collection from a DO-A device and that assistance information is included in the new AIoT command.

[0105] If this AIoT service request is for one time data collection from AIoT device 1, such as collect sensor data for one time, the assistance information can be (device type C, DO-A capable, one-time type D2R, D2R data size (2oobit). Delayed transmission with start time (1 hour after this message is received). For this example, periodic type D2R is assumed.FW 6000773PCT02 16[oio6] At the operation 502, the AIoTF 556 selects the NG-RAN A 558 as the reader, and assigns the correlation ID #79.

[0107] At the operation 503 (optional), the NG-RAN A 558 conducts an inventory operation for the AIoT device 1554 with the correlation ID (#79).

[0108] At the operation 504, after receiving the inventory result of the AIoT device 1 554, the AIoTF 556 sends an AIoT read command to the NG-RAN A 558 (AIoT device 1, read command, (application data: report sensor data periodically, transmit data every hour), assistance information: device type C, DO-A capable, periodic type D2R, periodic D2R data size (2oobit), interval every 1 hour, 10 messages, start time (9am), correlation ID (#79)).

[0109] At the operation 505, with the indication in the assistance information, the NG-RAN A 558 creates context for the AIoT device 1554 with the correlation ID #79 for periodic D2R traffic.

[0110] At the operation 506, the NG-RAN A 558 sends the AIoT read command to the AIoT device 1554.

[0111] At the operation 507, the AIoT device 1554 sends the D2R command response to acknowledge the receiving the command successfully.

[0112] At the operation 508, the NG-RAN A 558 sends the command response with the success indication to the AIoTF 556.

[0113] At the operation 509, the AIoTF 556 sends the command notification with success indication the AF 552.

[0114] At the operation 510, when it is 9 am, the NG-RAN A 558 prepares resources for the upcoming D2R transmission.

[0115] At the operation 511, the NG-RAN A 558 pages the AIoT device 1554 with the contention free access (CFA) indication with allocated D2R transmission resource for the AIoT device 1554.

[0116] At the operation 512, the AIoT device 1554 sends a D2R message as the read command response with collected data. The NG-RAN A 558 sends the read command response to the AIoTF 556 with correlation ID (#79).

[0117] At the operation 513, the AIoTF 556 sends the read command notification with data collected from the AIoT device 1554 to the AF 552.

[0118] At the operation 514, when it is closer to the every hour interval, the NG-RAN A 558 allocates the resource for the upcoming D2R transmission.

[0119] At the operation 515, following the same procedure as the operations 511-513, data collected by the AIoT device 1554 is transferred to the AF 552.

[0120] At the operation 516, after completing 10 D2R transmissions, the NG-RAN A 558 notifies the AIoTF 556 about the completion of the read service for this periodic dataFW 6000773PCT02 17collection. The AIoTF 556 also sends the service completion notification to the AF 552. After completing the service, the NG-RAN A 558 may reject any access attempt from the AIoT device 1554 if there is no further AIoT service request from the AIoTF 556 for the AIoT device 1554.

[0121] FIGs. 6A-6B show an example message flow for DO-A AIoT device deviceoriginated event-driven D2R transmission with traffic assistance information (Type 1 Resource Scheduling), in accordance with some implementations;

[0122] At the operation 601, the AF 652 sends an AIoT service request for AIoT device 1654 (AIoT device 1, read command, (application data: report sensor data when triggered by alarm), assistance information: device type C, DO-A capable, periodic transmission, periodic polling for event driven transmission, D2R data size (2oobit), polling interval 10 minutes, start time (9am)). There can be a new AIoT command being introduced to handle data collection from the DO-A device and that assistance information is included in the new AIoT command.

[0123] At the operation 602, the AIoTF 656 selects the NG-RAN A 658 as the reader and assigns the correlation ID (e.g., #79).

[0124] At the operation 603 (Optional), the NG-RAN A 658 conducts an inventory operation for AIoT device 1654 with the correlation ID (#79).

[0125] At the operation 604, after receiving inventory results from the AIoT device 1 654, the AIoTF 656 sends the AIoT read command to the NG-RAN A 658 (AIoT device 1, read command, (application data: report sensor data when triggered by alarm), assistance information: device type C, DO-A capable, periodic transmission, periodic polling for event driven transmission, D2R data size (200 bits), polling interval tomin, start time (9am), correlation ID (#79)).

[0126] At the operation 605, with the indication in the assistance information, the NG-RAN A 658 creates the context for AIoT device 1654 with correlation ID (#79) for periodic D2R traffic.

[0127] At the operation 606, the NG-RAN A 658 sends the AIoT read command to the AIoT device 1654.

[0128] At the operation 607, the AIoT device 1654 sends the command response to acknowledge receiving the command successfully.

[0129] At the operation 608, the NG-RAN A 658 sends the command response with success indication to the AIoTF 656.

[0130] At the operation 609, the AIoTF 656 sends the command notification with success indication the AF 652.

[0131] At the operation 610, the NG-RAN A 658 sends a paging message every 10 minutes to the AIoT device 1654 to poll if there is any D2R transmission.FW 6000773PCT02 18

[0132] At the operation 611, the AIoT device 1654 detects an alarm, prepares data for D2R transmission, and waits for the polling from the NG-RAN A 658. The AIoT device 1 654 receives the paging with polling from the NG-RAN A 658.

[0133] At the operation 612, the AIoT device 1654 responds to the paging with indication for D2R transmission.

[0134] At the operation 613, the NG-RAN A 658 pages the AIoT device 1654 with CFA indication with allocated D2R transmission resource for the AIoT device 1654.

[0135] At the operation 614, the AIoT device 1654 sends a D2R message as the read command response with the collected data.

[0136] At the operation 615, the NG-RAN A 658 sends a read-command-response to the AIoTF 656 with the correlation ID (#79).

[0137] At the operation 616, the AIoTF 656 sends the read command notification with data collected from the AIoT device 1654 to the AF 652.

[0138] FIG. 7 shows an example message flow for DO-A AIoT device deviceoriginated sensor data transmission with traffic assistance information (Type 2 Resource Scheduling), in accordance with some implementations.

[0139] At the operation 701, after the AIoT reader A 760 powers up and becomes ready for use as a reader, it broadcasts its AIoT timer information. The AIoT device 1754 synchronizes its clock with the AIoT reader A 760.

[0140] At the operation 702, after the AIoT reader A 760 is selected by the AIoTF 756 for a DO-A service, the AIoT reader A 760 provides its AIoT timer information which includes the timer start time and its interval (e.g., too ms).

[0141] At the operation 703, the AF 752 sends the DO-A command to the AIoTF 756 (read command, assistance information: device type C, DO-A capable, periodic type D2R, periodic D2R data size (200 bits), interval every 1 hour, cycle 10 times, start time (one hour after receiving this read command)).

[0142] At the operation 704, the AIoTF 756 selects the AIoT reader A 760 for the service. The AIoTF 756 also translates the 1 hour to 36000 AIoT timer of the AIoT reader A 760 to replace the cycle interval time in the AIoT service request from the AF 752, as well as calculate the start time based on AIoT reader A 760’s AIoT timer.

[0143] At the operation 705, the AIoTF 756 sends the DO-A AIoT command to the AIoT reader A 760 (read command, assistance information: device type G, DO-A capable, periodic type D2R, periodic D2R data size (200 bits), interval every 36000 AIoT time, cycle 10 times, start time (36000 AIoT time cycle after receiving this read command)).

[0144] At the operation 706, the AIoT reader A 760 sends the DO-A AIoT command to the AIoT device 1754 (read command, assistance information: device type C, DO-A capable, periodic type D2R, periodic D2R data size (200 bits), interval every 36000 FW 6000773PCT02 19AIoT time, cycle to times, start time (36000AI0T time cycle after receiving this read command), with information of pre-allocated radio resource for the AIoT device 1754 in 36000 time later).

[0145] At the operation 707, the AIoT device 1754 sends the command acknowledgement back. After receiving the acknowledgement, the AIoT reader A 760 marks the timestamp as the command message being sent to the AIoT device 1754 using the AIoT timer and prepares to schedule radio resource in 36000 AIoT time later.

[0146] At the operation 708, the AIoT reader A 760 schedules D2R radio resource for the AIoT device 1754 at command message send time stamp + 36000 AIoT time.

[0147] At the operation 709, the AIoT device 1754 transmits the D2R data at the pre-assigned AIoT time with the allocated radio resource.

[0148] At the operation 710, the AIoT reader A 760 forwards the received AIoT data to AIoTF 756, which forwards to the AF 752.

[0149] FIGs. 8A-8B show an example message flow for device-originated sensor data transmission with energy assistance information, in accordance with some implementations ;

[0150] At the operation 800, the AIoT device 1854 provides its energy status information to the AF 852 via application-level means. The energy status information can include average communication power (w) and unavailable energy threshold indicator to indicate if the energy level of the device is below the threshold for communication or not.

[0151] At the operation 801, the AF 852 sends the AIoT service request for the AIoT device 1854 (AIoT device 1, read command, (application data: report sensor data periodically, at the beginning of every hour), assistance information: device type C, DO-A capable, power source: solar power, waiting time upon receiving energy for communication unavailability indication ( 1 minute)).

[0152] At the operation 802, the AIoTF 856 selects the NG- RAN A 858 as the reader and assigns the correlation ID (#79).

[0153] At the operation 803 (optional), the NG-RAN A 858 conducts inventory operation for the AIoT device 1854 with the correlation ID (#79).

[0154] At the operation 804, after receiving the inventory7result of the AIoT device 1 854, the AIoTF 856 sends the AIoT read command to the NG-RAN A 858 (AIoT device 1, read command, (application data: report sensor data periodically, at the beginning of every hour), assistance information: device type C, DO-A capable, power source: solar power, waiting time upon receiving energy for communication unavailability indication^ minute)).FW 6000773PCT02 20

[0155] At the operation 805, with the indication in the assistance information, the NG-RAN A 858 creates context for the AIoT device 1854 with the correlation ID (#79) for periodic D2R traffic.

[0156] At the operation 806, the NG-RAN A 858 sends the AIoT read command to the AIoT device 1854, including an indication for request for energy status report.

[0157] At the operation 807, the AIoT device 1854 sends the command responses to acknowledge the receiving the command successfully.

[0158] At the operation 808, the NG-RAN A 858 sends the command response with success indication to the AIoTF 856.

[0159] At the operation 809, the AIoTF 856 sends the command notification with success indication to the AF 852.

[0160] At the operation 810, after collecting the data and the D2R time is up, the AIoT device 1854 sends collected data to the AF 852 via the AIoT reader (e.g., the NG-RAN A 858) and the AIoTF 856.

[0161] At the operation 811, during or after collecting the data, the energy level in the AIoT device 1854 drops to below the configured availability threshold for communication. The AIoT device 1854 sends D2R message to AIoT reader (e.g., the NG-RAN A 858) to indicate a failure with the energy-for-communication unavailabilityindication showing energy is unavailable.

[0162] At the operation 812, because it is daytime, the AIoT device 1854 may obtain sufficient energy using solar power, so the NG-RAN A 858 waits for 1 min, and prepares for the D2R traffic from the AIoT device 1854. If it is nighttime, the NG-RAN A 858 may consider the AIoT device 1854 will not be reachable for the whole night and will not try to connect it until the next day.

[0163] At the operations 813 and 814. the AIoT device 1854 sends collected data to the AF 852 via the AIoT reader (e.g., the NG-RAN A 858) and the AIoTF 856.

[0164] FIG. 9 shows an example flow diagram performed by a base station (e.g., an NG-RAN) or an AIoT reader, in accordance with some implementations. At the operation 902, the base station receives an AIoT service request from the AIoTF for a DO-A device. At the operation 904, the base station determines whether there is AIoT DO-A assistance information associated with the AIoT service request. If the answer is no, at the operation 906, the base station delivers the AIoT service per implementation. If the answer is yes, at the opeation 908, the base station schedules resource according to the assistance information. In some implementations, if the traffic pattern information is included in the assistance information, at the operation 910, the base station schedules the resource according to the traffic pattern information. In some implementations, if the energy information is included in the assistance information, at the operation 912, the base FW 6000773PCT02 21station uses the energy information when there is a receive unavailable information from the UE.

[0165] FIG. 10A illustrates an example of a flowchart of a method 1000 performed by a first network function entity, in accordance with some implementations. The first network function entity may include computer-readable code or instructions executing on one or more processors of the first network function entity. Coding of the software for carrying out or performing the method 1000 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 1000 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the first network function entity. In some implementations, the method 1000 may be performed by one or more units or modules (e.g., an integrated circuit) of the first network function entity, such as field programmable gate arrays (FPGAs) or applicationspecific integrated circuits (ASICs).

[0166] The method 1000 may start at the operation 1002, where the first network function entity receives from an application function entity an ambient Internet of things (AIoT) service request for an AIoT service to an AIoT device supporting a device-originated-autonomous (DO-A) transmission capability. The AIoT service request comprises DO-A service assistance information. At the operation 1004, the first network function entity sends to a second network function entity, a request message for the AIoT service with second DO-A service assistance information related to the AIoT device. The second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.

[0167] In some implementations, the request message may be sent in response to the AIoT service request.

[0168] In some implementations, the second DO-A service assistance information may further include periodicity information of transmitted data.

[0169] In some implementations, the periodicity information may indicate whether the transmitted data is initiated by the AIoT device periodically or polled periodically.

[0170] In some implementations, the transmitted data may be any data sent by the AIoT device.

[0171] In some implementations, the transmitted data may include at least one of a registration message or application level data.FW 6000773PCT02 22

[0172] In some implementations, the second DO-A service assistance information may be stored locally in the first network function entity or configured by the application function entity.

[0173] In some implementations, the first network function entity may send the request message to the second network function entity for a plurality of periodic D2R transmissions. The second network function entity may retain a periodic transmission schedule and allocate radio resources at each interval without a separate request from the first network function entity for each transmission.

[0174] In some implementations, the first network function entity may receive from the second network function entity AIoT timer information. The AIoT timer information may define a common clock shared among the first network function entity, the second network function entity, and the AIoT device.

[0175] In some implementations, the second DO-A service assistance information may further indicate a waiting time threshold. The waiting time threshold may indicate a duration after which the second network function entity sends a notification to the first network function entity to indicate completion status of a task to receive D2R transmission from at least one AIoT device.

[0176] In some implementations, the notification may include a completion notification in response to receiving the D2R transmission from the at least one AIoT device within the duration.

[0177] In some implementations, the notification may include a failure notification in response to not receiving all of the D2R transmission from the at least one AIoT device within the duration.

[0178] In some implementations, the notification may be included in a dedicated container message being delivered between the AIoT device and the application function entity. The dedicated container message may be used for conveying application level information.

[0179] In some implementations, the second network function entity may comprise at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

[0180] FIG. 10B illustrates an example of a flowchart of a method 1010 performed by an AIoT device, in accordance with some implementations. The AIoT device may include computer-readable code or instructions executing on one or more processors of the AIoT device. Coding of the software for carrying out or performing the method 1010 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 1010 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order.FW 6000773PCT02 23Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the AIoT device. In some implementations, the method 1010 may be performed by one or more units or modules (e.g., an integrated circuit) of the AIoT device, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0181] The method 1010 may start at the operation 1012, where the AIoT device receives from a second network function entity device-originated-autonomous (DO-A) service configuration information for an AIoT service. The AIoT device supports a DO-A transmission capability. At the operation 1014, the AIoT device sends to the second network function entity a device-to-reader (D2R) message autonomously based on the DO-A service configuration information.

[0182] In some implementations, the DO-A service configuration information may comprise AIoT timer information defining a common clock shared among the AIoT device, the second network function entity, and a first network function entity. The AIoT device may send the D2R message at a time determined based on the common clock.

[0183] In some implementations, the AIoT timer information may comprise at least one of a transmission start time expressed in AIoT timer units or a periodic transmission interval expressed in the AIoT timer units.

[0184] In some implementations, the AIoT device may synchronize an internal clock of the AIoT device with the common clock based on broadcast AIoT timer information received from the second network function entity.

[0185] In some implementations, the AIoT device may send to the second network function entity a D2R notification message indicating an error status.

[0186] In some implementations, the second network function entity may comprise at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

[0187] FIG. 10C illustrates an example of a flowchart of a method 1020 performed by a second network function entity, in accordance with some implementations. The second network function entity may include computer-readable code or instructions executing on one or more processors of the second network function entity. Coding of the software for carrying out or performing the method 1020 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 1020 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors maybe stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the FW 6000773PCT02 24second network function entity. In some implementations, the method 1020 may be performed by one or more units or modules (e.g., an integrated circuit) of the second network function entity, such as field programmable gate arrays (FPGAs) or applicationspecific integrated circuits (ASICs).

[0188] The method 1020 may start at the operation 1022, wherein the second network function entity receives from a first network function entity, a request message for an ambient Internet of things (AIoT) service with second device-originated-autonomous (DO-A) service assistance information related to an AIoT device supporting a DO-A transmission capability. The second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.

[0189] In some implementations, the request message may be received in response to an AIoT service request received by the first network function entity.

[0190] In some implementations, the second DO-A service assistance information may further include periodicity information of transmitted data.

[0191] In some implementations, the periodicity information may indicate whether the transmitted data is initiated by the AIoT device periodically or polled periodically.

[0192] In some implementations, the transmitted data may be any data sent by the AIoT device.

[0193] In some implementations, the transmitted data may include at least one of a registration message or application level data.

[0194] In some implementations, the second DO-A service assistance information may be stored locally in the first network function entity or configured by an application function entity.

[0195] In some implementations, the second network function entity may receive the request message from the first network function entity for a plurality of periodic D2R transmissions. The second network function entity may retain a periodic transmission schedule and allocate radio resources at each interval without a separate request from the first network function entity for each transmission.

[0196] In some implementations, the second network function entity may send to the first network function entity AIoT timer information. The AIoT timer information may define a common clock shared among the first network function entity, the second network function entity, and the AIoT device.

[0197] In some implementations, the second DO-A service assistance information may further indicate a waiting time threshold. The waiting time threshold may indicate a duration after which the second network function entity sends a notification to the firstFW 6000773PCT02 25network function entity to indicate completion status of a task to receive D2R transmission from at least one AIoT device.

[0198] In some implementations, the notification may include a completion notification in response to receiving the D2R transmission from the at least one AIoT device within the duration.

[0199] In some implementations, the notification may include a failure notification in response to not receiving all of the D2R transmission from the at least one AIoT device within the duration.

[0200] In some implementations, the notification may be included in a dedicated container message being delivered between the AIoT device and an application function entity. The dedicated container message may be used for conveying application level information.

[0201] In some implementations, the second network function entity may comprise at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

[0202] FIG. 10D illustrates an example of a flowchart of a method 1030 performed by a second network function entity, in accordance with some implementations. The second network function entity may include computer-readable code or instructions executing on one or more processors of the second network function entity. Coding of the software for carrying out or performing the method 1030 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 1030 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the second network function entity. In some implementations, the method 1030 may be performed by one or more units or modules (e.g., an integrated circuit) of the second network function entity, such as field programmable gate arrays (FPGAs) or applicationspecific integrated circuits (ASICs).

[0203] The method 1030 may start at the operation 1032, wherein the second network function entity sends to an ambient Internet of things (AIoT) device, device-originated-autonomous (DO-A) service configuration information for an AIoT service. The AIoT device supports a DO-A transmission capability. At the operation 1034, the second network function entity receives a device-to-reader (D2R) message sent by the AIoT device autonomously based on the DO-A service configuration information.

[0204] In some implementations, the DO-A service configuration information may comprise AIoT timer information defining a common clock shared among the AIoT FW 6000773PCT02 26device, the second network function entity, and a first network function entity. The second network function entity may receive the D2R message at a time determined based on the common clock.

[0205] In some implementations, the AIoT timer information may comprise at least one of a transmission start time expressed in AIoT timer units or a periodic transmission interval expressed in the AIoT timer units.

[0206] In some implementations, the AIoT device may synchronize an internal clock of the AIoT device with the common clock based on broadcast AIoT timer information sent by the second network function entity.

[0207] In some implementations, the second network function entity may receive from the AIoT device a D2R notification message indicating an error status.

[0208] In some implementations, the second network function entity comprises at least one of a next generation-radio access network (RAN) (NG-RAN) unit or an AIoT reader device.

[0209] While some claims presented herein are directed to operations performed by a user equipment (UE), it should be understood that corresponding complementary operations are performed by the network entity (e.g., base station, gNB, TRP). For each UE-side operation described in the claims, there is a corresponding network-side operation. The scope of this disclosure encompasses both the UE-side operations explicitly claimed and their corresponding network-side counterparts, including methods, systems, apparatus, and non-transitory computer-readable medium for performing such network-side operations.

[0210] The network entity described in this disclosure may include a base station, a network relay node, or a plurality of base stations each configured to perform at least one of the network entity operations described above. The network entity operations may be distributed among different base stations in any combination or configuration, without limitation to the specific examples provided herein.

[0211] FIG. 11 illustrates an example communications system 1100. Communications system 1100 includes an access node 1110 serving user equipments (UEs) with coverage not, such as UEs 1120. In a first operating mode, communications to and from a UE passes through access node 1110 with a coverage area not. The access node 1110 is connected to a backhaul network 1115 for connecting to the internet, operations and management, and so forth. In a second operating mode, communications to and from a UE do not pass through access node 1110, however, access node 1110 typically allocates resources used by the UE to communicate when specific conditions are met.Communications between a pair of UEs 1120 can use a sidelink connection (shown as two separate one-way connections 1125). In FIG. 11, the sidelink communication is occurring FW 6000773PCT02 27between two UEs operating inside of coverage area not. However, sidelink communications, in general, can occur when UEs 1120 are both outside coverage area not, both inside coverage area not, or one inside and the other outside coverage area not. Communication between a UE and access node pair occur over uni-directional communication links, where the communication links between the UE and the access node are referred to as uplinks 1130, and the communication links between the access node and UE is referred to as downlinks 1135.

[0212] Access nodes may also be commonly referred to as Node Bs, evolved Node Bs (eNBs), next generation (NG) Node Bs (gNBs), master eNBs (MeNBs), secondary eNBs (SeNBs), master gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on, while UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like. Access nodes may provide wireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE-A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and two UEs are illustrated for simplicity.

[0213] FIG. 12 illustrates an example communication system 1200. In general, the system 1200 enables multiple wireless or wired users to transmit and receive data and other content. The system 1200 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0214] In this example, the communication system 1200 includes electronic devices (ED) I2ioa-i2ioc, radio access networks (RANs) I22oa-i22ob, a core network 1230, a public switched telephone network (PSTN) 1240, the Internet 1250, and other networks 1260. While certain numbers of these components or elements are shown in FIG. 12, any number of these components or elements may be included in the system 1200.

[0215] The EDs I2ioa-i2ioc are configured to operate or communicate in the system 1200. For example, the EDs I2ioa-i2ioc are configured to transmit or receive via wireless or wired communication channels. Each ED I2ioa-i2ioc represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, FW 6000773PCT02 28fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, AIoT device (e.g., for asset management), or consumer electronics device.

[0216] The RANs I22oa-i22ob here include base stations I27oa-i27ob, respectively. Each base station I27oa-i27ob is configured to wirelessly interface with one or more of the EDs I2ioa-i2ioc to enable access to the core network 1230, the PSTN 1240, the Internet 1250, or the other networks 1260. For example, the base stations I27oa-i27ob may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNB), a Next Generation (NG) NodeB (gNB), a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs I2ioa-i2ioc are configured to interface and communicate with the Internet 1250 and may access the core network 1230, the PSTN 1240, or the other networks 1260.

[0217] In the embodiment shown in FIG. 12, the base station 1270a forms part of the RAN 1220a, which may include other base stations, elements, or devices. Also, the base station 1270b forms part of the RAN 1220b, which may include other base stations, elements, or devices. Each base station i27oa-i27ob operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multiple-input multiple-output (MIMO) technology may be employed having multiple transceivers for each cell.

[0218] The base stations I27oa-i27ob communicate with one or more of the EDs I2ioa-i2ioc over one or more air interfaces 1290 using wireless communication links. The air interfaces 1290 may utilize any suitable radio access technology.

[0219] It is contemplated that the system 1200 may use multiple channel access functionality, including such schemes as described above. In particular embodiments, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.

[0220] The RANs I22oa-i22ob are in communication with the core network 1230 to provide the EDs I2ioa-i2ioc with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs I22oa-i22ob or the core network 1230 may be in direct or indirect communication with one or more other RANs (not shown). The core network 1230 may also serve as a gateway access for other networks (such as the PSTN 1240, the Internet 1250, and the other networks 1260). In addition, some or all of the EDs I2ioa-i2ioc may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the FW 6000773PCT02 29EDs may communicate via wired communication channels to a service provider or switch (not shown), and to the Internet 1250.

[0221] Although FIG. 12 illustrates one example of a communication system, various changes may be made to FIG. 12. For example, the communication system 1200 could include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0222] FIGs. 13A and 13B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, FIG. 13A illustrates an example ED 1310, and FIG. 13B illustrates an example base station 1370. The ED 1310 and the base station 1370 may communicate over the air interface 1390. These components could be used in the system 1200 or in any other suitable system.

[0223] As shown in FIG. 13A, the ED 1310 includes at least one processing unit 1300. The processing unit 1300 implements various processing operations of the ED 1310. For example, the processing unit 1300 could perform signal coding, data processing, power control, input / output processing, or any other functionality enabling the ED 1310 to operate in the system 1200. The processing unit 1300 also supports the methods and teachings described in more detail above. Each processing unit 1300 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1300 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0224] The ED 1310 also includes at least one transceiver 1302. The transceiver 1302 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 1304. The transceiver 1302 is also configured to demodulate data or other content received by the at least one antenna 1304. Each transceiver 1302 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire. Each antenna 1304 includes any suitable structure for transmitting or receiving wireless or wired signals. One or multiple transceivers 1302 could be used in the ED 1310, and one or multiple antennas 1304 could be used in the ED 1310. Although shown as a single functional unit, a transceiver 1302 could also be implemented using at least one transmitter and at least one separate receiver.

[0225] The ED 1310 further includes one or more input / output devices 1306 or interfaces (such as a wired interface to the Internet 1250). The input / output devices 1306 facilitate interaction with a user or other devices (network communications) in the network. Each input / output device 1306 includes any suitable structure for providingFW 6000773PCT02 30information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0226] In addition, the ED 1310 includes at least one memory 1308. The memory 1308 stores instructions and data used, generated, or collected by the ED 1310. For example, the memory 1308 could store software or firmware instructions executed by the processing unit(s) 1300 and data used to reduce or eliminate interference in incoming signals. Each memory 1308 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and the like.

[0227] As shown in FIG. 13B, the base station 1370 includes at least one processing unit 1350, at least one transceiver 1352, which includes functionality for a transmitter and a receiver, one or more antennas 1356, at least one memory 1358, and one or more input / output devices or interfaces 1366. A scheduler, which would be understood by one skilled in the art, is coupled to the processing unit 1350. The scheduler could be included within or operated separately from the base station 1370. The processing unit 1350 implements various processing operations of the base station 1370, such as signal coding, data processing, power control, input / output processing, or any other functionality. The processing unit 1350 can also support the methods and teachings described in more detail above. Each processing unit 1350 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1350 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0228] Each transceiver 1352 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1352 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices. Although shown combined as a transceiver 1352, a transmitter and a receiver could be separate components. Each antenna 1356 includes any suitable structure for transmitting or receiving wireless or wired signals. While a common antenna 1356 is shown here as being coupled to the transceiver 1352, one or more antennas 1356 could be coupled to the transceiver(s) 1352, allowing separate antennas 1356 to be coupled to the transmitter and the receiver if equipped as separate components. Each memory 1358 includes any suitable volatile or non-volatile storage and retrieval device(s). Each input / output device 1366 facilitates interaction with a user or other devices (network communications) in the network. Each input / output device 1366 includes any suitable structure for providing information to orFW 6000773PCT02 31receiving / providing information from a user, including network interface communications.

[0229] FIG. 14 is a block diagram of a computing system 1400 that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vary from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1400 includes a processing unit 1402. The processing unit includes a central processing unit (CPU) 1414, memory 1408, and may further include a mass storage device 1404, a video adapter 1410, and an I / O interface 1412 connected to a bus 1420.

[0230] The bus 1420 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 1414 may comprise any type of electronic data processor. The memory 1408 may comprise any type of non-transitory system memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory 1408 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.

[0231] The mass storage 1404 may comprise any type of non-transitory storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 1420. The mass storage 1404 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.

[0232] The video adapter 1410 and the I / O interface 1412 provide interfaces to couple external input and output devices to the processing unit 1402. As illustrated, examples of input and output devices include a display 1418 coupled to the video adapter 1410 and a mouse, keyboard, or printer 1416 coupled to the I / O interface 1412. Other devices may be coupled to the processing unit 1402, and additional or fewer interface cards may be utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device.

[0233] The processing unit 1402 also includes one or more network interfaces 1406, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 1406 allow the processing unit 1402 to communicate with remote units via the networks. For example, the network interfaces FW 6000773PCT02 321406 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In an embodiment, the processing unit 1402 is coupled to a local-area network 1422 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0234] It should be appreciated that not all components in the devices described in FIGs. 11-14 are required. In a non-limiting example, the ED 1310 maybe implemented as an AIoT device 1310. But, the AIoT device 1310 may not include an input / output devices 1306 for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen. The transceiver 1302 of the AIoT device 1310 may be capable of transmitting by backscattering a radio wave received, instead of by generating the radio wave, for wireless communication purpose. In another non-limiting example, the system 1400 may be implemented as an AIoT device 1400 that does not include or use the mass storage device 1404, the video adapter 1410, the mouse, keyboard, or printer 1416, or the display 1418.

[0235] It should be appreciated that one or more steps of the embodiment methods provided herein maybe performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a performing unit or module, a generating unit or module, an obtaining unit or module, a setting unit or module, an adjusting unit or module, an increasing unit or module, a decreasing unit or module, a determining unit or module, a modifying unit or module, a reducing unit or module, a removing unit or module, or a selecting unit or module. The respective units or modules may be hardware, software, or a combination thereof. For instance, one or more of the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0236] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended toFW 6000773PCT02 33include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

[0237] DefinitionsAmbient loT device: An ambient power-enabled Internet of Things device is an loT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor).

[0238] Abbreviations• 5GC: fifth generation core• ADM: AIoT device Management• AIoT : Ambient loT• AIoTF: AIoT Function• AF: Application Function• AMF: Access Management Function• CBRA: Contention Based Random Access• CFA: Contention Free Access• CFRA: Contention Free Random Access• CP: Control Plane• CW: Carrier-wave• DO: Device-originated• DT : Device-terminated• DO -A: Device-originated - autonomous• D2R: AIoT Device to AIoT Reader• gNB: next-Generation Node B• NG-RAN: Next Generation-RAN• NEF: Network Exposure Function.• OAM: Operation and Administration Management• PCF: Policy Control Function• PDU: Protocol Data Unit• PLMN: Public Line Mobile Network• R2D: AIoT Reader to AIoT Device• RAN: Radio Access Network• RAT : Radio Access T echnology• SP: Service Provider• UDM: Unified Data Management• UDR: Unified Data Repository• UE: User EquipmentFW 6000773PCT02 34• SFO: sampling frequency offset• IF: intermediate frequency• ZIF: zero IFFW 6000773PCT02 35

Claims

WHAT IS CLAIMED IS:

1. A method comprising:receiving, by a first network function entity from an application function entity, an ambient Internet of things (AIoT) service request for an AIoT service to an AIoT device supporting a device-originated-autonomous (DO-A) transmission capability, wherein the AIoT service request comprises DO-A service assistance information; andsending, by the first network function entity to a second network function entity, a request message for the AIoT service with second DO-A service assistance information related to the AIoT device,wherein the second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.

2. The method of claim 1, wherein the request message is sent in response to the AIoT service request.

3. The method of any of claims 1-2, wherein the second DO-A service assistance information further includes periodicity information of transmitted data.

4. The method of claim 3, wherein the periodicity information indicates whether the transmitted data is initiated by the AIoT device periodically or polled periodically.

5. The method of claim 3, wherein the transmitted data includes at least one of a registration message or application level data.

6. The method of any of claims 1-5, wherein the second DO-A service assistance information is stored locally in the first network function entity or configured by the application function entity.

7. The method of any of claims 1-6, wherein the first network function entity sends the request message to the second network function entity for a plurality of periodic D2R transmissions, and wherein the second network function entity retains a periodic transmission schedule and allocates radio resources at each interval without a separate request from the first network function entity for each transmission.8 The method of any of claims 1-7, further comprising:receiving, by the first network function entity from the second network function entity, AIoT timer information, wherein the AIoT timer information defines a commonFW 6000773PCT02 36clock shared among the first network function entity, the second network function entity, and the AIoT device.

9. The method of any of claims 1-8, wherein the second DO-A service assistance information further indicates a waiting time threshold, and wherein the waiting time threshold indicates a duration after which the second network function entity sends a notification to the first network function entity to indicate completion status of a task to receive D2R transmission from at least one AIoT device.

10. The method of claim 9, wherein the notification includes a completion notification in response to receiving the D2R transmission from the at least one AIoT device within the duration; or wherein the notification includes a failure notification in response to not receiving all of the D2R transmission from the at least one AIoT device within the duration.

11. The method of claim 10, wherein the notification is included in a dedicated container message being delivered between the AIoT device and the application function entity, the dedicated container message being used for conveying application level information.

12. The method of any of claims 1-11, wherein the second network function entity comprises at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

13. A method comprising:receiving, by an ambient Internet of things (AIoT) device from a second network function entity, device-originated-autonomous (DO-A) service configuration information for an AIoT service, the AIoT device supporting a DO-A transmission capability; and sending, by the AIoT device to the second network function entity, a device-to-reader (D2R) message autonomously based on the DO-A service configuration information.

14. The method of claim 13, wherein the DO-A service configuration information comprises AIoT timer information defining a common clock shared among the AIoT device, the second network function entity, and a first network function entity, and wherein the sending the D2R message comprises:sending the D2R message at a time determined based on the common clock.

15. The method of claim 14, wherein the AIoT timer information comprises at least one of:FW 6000773PCT02 37a transmission start time expressed in AIoT timer units; or a periodic transmission interval expressed in the AIoT timer units.

16. The method of claim 14, further comprising:synchronizing, by the AIoT device, an internal clock of the AIoT device with the common clock based on broadcast AIoT timer information received from the second network function entity.

17. The method of any of claims 13-16, further comprising:sending, by the AIoT device to the second network function entity, a D2R notification message indicating an error status.

18. The method of any of claims 13-17, wherein the second network function entity comprises at least one of a next generation-radio access network (RAN) (NG-RAN) unit or an AIoT reader device.

19. A method comprising:receiving, by a second network function entity from a first network function entity, a request message for an ambient Internet of things (AIoT) service with second device-originated-autonomous (DO-A) service assistance information related to an AIoT device supporting a DO-A transmission capability,wherein the second DO-A service assistance information indicates at least one of a device type of the AIoT device, an estimated device-to-reader (D2R) data size, or capability of the AIoT device.

20. The method of claim 19, wherein the request message is received in response to an AIoT service request received by the first network function entity.

21. The method of any of claims 19-20, wherein the second DO-A service assistance information further includes periodicity information of transmitted data.

22. The method of claim 21, wherein the periodicity information indicates whether the transmitted data is initiated by the AIoT device periodically or polled periodically.

23. The method of claim 21, wherein the transmitted data includes at least one of a registration message or application level data.FW 6000773PCT02 3824- The method of any of claims 19-23, wherein the second DO-A service assistance information is stored locally in the first network function entity or configured by an application function entity.

25. The method of any of claims 19-24, wherein the second network function entity receives the request message from the first network function entity for a plurality of periodic D2R transmissions, and wherein the second network function entity retains a periodic transmission schedule and allocates radio resources at each interval without a separate request from the first network function entity for each transmission.

26. The method of any of claims 19-25, further comprising:sending, by the second network function entity to the first network function entity, AIoT timer information, wherein the AIoT timer information defines a common clock shared among the first network function entity, the second network function entity, and the AIoT device.

27. The method of any of claims 19-26, wherein the second DO-A service assistance information further indicates a waiting time threshold, and wherein the waiting time threshold indicates a duration after which the second network function entity sends a notification to the first network function entity to indicate completion status of a task to receive D2R transmission from at least one AIoT device.

28. The method of claim 27, wherein the notification includes a completion notification in response to receiving the D2R transmission from the at least one AIoT device within the duration; or wherein the notification includes a failure notification in response to not receiving all of the D2R transmission from the at least one AIoT device within the duration.

29. The method of claim 27, wherein the notification is included in a dedicated container message being delivered between the AIoT device and an application function entity, the dedicated container message being used for conveying application level information.

30. The method of any of claims 19-29, wherein the second network function entity comprises at least one of a next generation-radio access network (RAN) (NG-RAN) unit or an AIoT reader device.

31. A method comprisin :sending, by a second network function entity to an ambient Internet of things (AIoT) device, device-originated-autonomous (DO-A) service configuration information FW 6000773PCT02 39for an AIoT service, the AIoT device supporting a DO-A transmission capability; and receiving, by the second network function entity, a device-to-reader (D2R) message sent by the AIoT device autonomously based on the DO-A service configuration information.

32. The method of claim 31, wherein the DO-A service configuration information comprises AIoT timer information defining a common clock shared among the AIoT device, the second network function entity, and a first network function entity, and wherein the receiving the D2R message comprises:receiving the D2R message at a time determined based on the common clock.

33. The method of claim 32, wherein the AIoT timer information comprises at least one of:a transmission start time expressed in AIoT timer units; ora periodic transmission interval expressed in the AIoT timer units.

34. The method of claim 32, wherein the AIoT device synchronizes an internal clock of the AIoT device with the common clock based on broadcast AIoT timer information sent by the second network function entity.

35. The method of any of claims 31-34, further comprising:receiving, by the second network function entity from the AIoT device, a D2R notification message indicating an error status.

36. The method of any of claims 31-35, wherein the second network function entity comprises at least one of a next generation-radio access network (RAN) (NG- RAN) unit or an AIoT reader device.

37. A first network function entity comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the first network function entity to perform a method according to any of claims 1-12.

38. An ambient Internet of things (AIoT) device comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the AIoT device to perform a method according to any of claims 13-18.FW 6000773PCT02 4039- A second network function entity comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the second network function entity to perform a method according to any of claims 19-30.

40. A second network function entity comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the second network function entity to perform a method according to any of claims 31-36.

41. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a first network function entity, cause the first network function entity to perform a method according to any of claims 1-12.

42. A non-transitory computer-readable medium having instructions stored thereon that, when executed by an ambient Internet of things (AIoT) device, cause the AIoT device to perform a method according to any of claims 13-18.

43. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a second network function entity, cause the second network function entity to perform a method according to any of claims 19-30.

44. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a second network function entity, cause the second network function entity to perform a method according to any of claims 31-36.FW 6000773PCT02 41