WO2025123740A1

WO2025123740A1 - Support aiot service

Info

Publication number: WO2025123740A1
Application number: PCT/CN2024/112779
Authority: WO
Inventors: Mingzeng Dai; Haiyan Luo; Jing HAN; Jie Hu; Lizhuo ZHENG
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2024-08-16
Filing date: 2024-08-16
Publication date: 2025-06-19
Anticipated expiration: 2027-02-16

Abstract

Various aspects of the present disclosure relate to UE, base station and methods supporting AIoT service. In one aspect, a UE triggers an inventory procedure or a command procedure towards AIoT devices. The UE receives at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data. In turn, the UE aggregates at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE. Then, the UE transmits the message to a node in a CN.

Description

SUPPORT AIOT SERVICE

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to user equipment (UE) , base station and methods supporting ambient internet of things (AIoT) service.

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)) .

Internet of Things (IoT) has attracted much attention in the wireless communication world, where the IoT device has smaller size, lower complexity, lower power consumption and huger number (e.g., tens or even hundreds of billion IoT devices) than the existing UE.

The IoT devices are typically battery less devices with no energy storage capability, or devices with energy storage that do not need to be replaced or recharged manually, where the energy is provided through the harvesting of radio waves, light, motion, heat, or any other power source that could be seen suitable. For simplicity, these devices are named as Ambient IoT (AIoT) devices. In other words, an AIoT device is an IoT device powered by energy harvesting, with limited energy storage capability.

Two connectivity topologies for AIoT are to be studied. In Topology 1, an AIoT device directly and bidirectionally communicates with a network entity. In Topology 2, an AIoT device communicates bidirectionally with an intermediate node between the AIoT device and a base station. The intermediate node transfers AIoT data and/or signalling between the base station and the AIoT device. In Topology 2, a UE can act as the intermediate node which is under the network control.

In Topology 2, there are two possible options of protocol stack for data transmission, one of which is based on control plane (CP) and the other is based on user plane (UP) . For a solution based on CP, there is a need to study how to aggregate the received AIOT device identities (IDs) and/or AIOT data in one message.

SUMMARY

The present disclosure relates to UE, base station and methods supporting AIoT service. With the present disclosure, the UE may transmit at least one of the ID or the AIoT data to the node in the CN via a single message. Signalling overhead may be reduced.

Some implementations of a UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: trigger an inventory procedure or a command procedure towards AIoT devices; receive at least one of the following via the transceiver from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data; and aggregate at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a non-access stratum (NAS) layer or a radio resource control (RRC) layer of the UE;and transmit the message via the transceiver to a node in a core network (CN) .

In some implementations, the processor is configured to aggregate at least one of the ID or the AIoT data into the single message by one of the following: aggregating at least one of the ID or the AIoT data into a single AIoT message; aggregating at least one of the ID or the AIoT data into a single NAS PDU at the NAS layer; and aggregating at least one of the ID or the AIoT data into a single RRC message at the RRC layer.

In some implementations, the processor is configured to aggregate at least one of the ID or the AIoT data into the NAS PDU at the NAS layer by: obtaining, at the NAS layer from the AIoT layer, assistance information about start and end of the inventory procedure or about start and end of the command procedure; and aggregating at least one of the ID or the AIoT data into the NAS PDU based on the assistance information.

In some implementations, the processor is configured to aggregate at least one of the ID or the AIoT data into the NAS PDU at the RRC layer by: obtaining, at the RRC layer from the AIoT layer, assistance information about start and end of the inventory procedure or about start and end of the command procedure; and aggregating at least one of the ID or the AIoT data into the RRC message based on the assistance information.

In some implementations, the processor is further configured to: start a first timer upon receiving an inventory request or a command request via the transceiver from the node in the CN or upon triggering the inventory procedure or the command procedure; and stop the first timer based on determining one of the following: the UE receives all of IDs of the AIoT devices for the inventory procedure, the UE receives all of AIoT data for the command procedure, the UE have transmitted the message to the node in the CN, a higher layer of the UE provides all of the IDs of the AIoT devices to a lower layer of the UE, or a higher layer of the UE provides all of the AIoT data to a lower layer of the UE.

In some implementations, the processor is further configured to: based on determining that only part of the IDs of the AIoT devices for the inventory procedure is received upon expiration of the first timer, transmit a first indication via the transceiver to the node in the CN, wherein the first indication indicates partial inventory failure; or based on determining that only part of the AIoT data for the command procedure is received upon expiration of the first timer, transmit a second indication via the transceiver to the node in the CN, wherein the second indication indicates partial command failure.

In some implementations, the processor is further configured to: based on determining that none of the IDs of the AIoT devices for the inventory procedure is received upon expiration of the first timer, transmit a third indication via the transceiver to the node in the CN, wherein the third indication indicates inventory failure; or based on determining that none of the AIoT data for the command procedure is received upon expiration of the first timer, transmit a fourth indication via the transceiver to the node in the CN, wherein the fourth indication indicates command failure.

In some implementations, the processor is further configured to: start a second timer upon aggregating at least one of the ID or the AIoT data into the single message; and based on determining that the UE is not able to transmit the message to the node in the CN upon expiration of the second timer, delete the at least one of the ID or the AIoT data.

In some implementations, the processor is further configured to: based on determining that the UE is able to transmit the message to the node in the CN upon expiration of the second timer, store the at least one of the ID or the AIoT data, and retry to perform access attempt to a base station.

In some implementations, the processor is further configured to: based on detection of radio link failure between the UE and a base station, suspend the inventory procedure or the command procedure in an air interface between the UE and at least one second AIoT device among the AIoT devices.

In some implementations, the processor is configured to suspend the inventory procedure by: stopping transmitting a downlink signal to trigger the at least one second AIoT device to report an ID of the at least one second AIoT device; maintaining a latest value of a slot counter; and storing the ID of the at least one first AIoT device received from the at least one first AIoT device.

In some implementations, the processor is further configured to: transmit a fifth indication via the transceiver to the at least one second AIoT device, wherein the fifth indication indicates that the inventory procedure or the command procedure is suspended.

In some implementations, the processor is further configured to: resume the inventory procedure or the command procedure once the UE reconnects to the base station.

In some implementations, the processor is configured to resume the inventory procedure by: starting to transmit the downlink signal to trigger the at least one second AIoT device to report the ID of the at least one second AIoT device; and transmitting a sixth indication via the transceiver to the at least one second AIoT device, wherein the sixth indication indicates that the inventory procedure is resumed.

In some implementations, the processor is further configured to: based on detection of radio link failure, continue the inventory procedure or the command procedure in an air interface between the UE and at least one second AIoT device among the AIoT devices, and store at least one of the following: the ID of the at least one first AIoT device, an ID of the at least one second AIoT device, or the AIoT data.

In some implementations, the processor is further configured to: try to transmit at least one of the following to the node in the CN once the UE reconnects to the base station: the ID of the at least one first AIoT device, an ID of the at least one second AIoT device, or the AIoT data.

In some implementations, the processor is further configured to: transmitting an eighth indication via the transceiver to the base station, wherein the eighth indication indicates that there is at least one of the following available to be reported to the base station: the ID of the at least one first AIoT device, an ID of the at least one second AIoT device, or the AIoT data.

In some implementations, the processor is further configured to: based on determining that an RRC connection reestablishment procedure fails after radio link failure between the UE and a base station, perform an access attempt to transmit at least one of the ID or the AIoT data.

In some implementations, the processor is configured to perform the access attempt by: receiving, via the transceiver from the base station or a further base station, at least one access control parameter for an access category related to AIoT; and performing, based on the at least one access control parameter, access barring check for the access category related to AIoT.

In some implementations, the at least one access control parameter for the access category related to AIoT comprises at least one of the following: access barring factor which represents a probability that the access attempt would be allowed during the access barring check, access barring time which indicates average time before a new access attempt is to be performed after the access attempt was barred at the access barring check for the access category, or access baring for access identity which indicates whether the access attempt is allowed for each access identity.

In some implementations, the processor is configured to perform the access barring check by: drawing a random number uniformly distributed in a range of zero to one; determining whether the random number is lower than a value indicated by an access barring factor for the access category among the at least one access control parameter; based on determining that the random number is lower than a value indicated by the access barring factor, considering access attempt as allowed; and based on determining that the random number is equal to or higher than the value indicated by the access barring factor, considering the access attempt as barred.

In some implementations, the access category is associated with a first type of access attempt, wherein the first type of access attempt is related to one of the following: signaling transmission originated from the NAS layer or the AIoT layer of the UE, or data transmission originated from the NAS layer or the AIoT layer of the UE.

In some implementations, the access category is associated with at least one of the following: the NAS layer or the AIoT layer of the UE has the ID available to be transmitted, or the NAS layer or the AIoT layer of the UE has the AIoT data available to be transmitted.

In some implementations, the processor is further configured to: based on determining the NAS layer or the AIoT layer of the UE has the ID or the AIoT data available to be transmitted, provide, from the NAS layer or the AIoT layer to the RRC layer, a cause related to AIoT for triggering an RRC state transition from an RRC_INACTIVE state to an RRC_CONNECTED state.

In some implementations, the cause related to AIoT indicates that the ID or the AIoT data is available to be transmitted.

In some implementations, the processor is further configured to: receive, via the transceiver from the node in the CN, user plane information about the node and an ID of an user plane AIoT connection; and transmit, via the transceiver to the node in the CN, PDU session parameters related to user plane AIoT for establishment of a PDU session for at least one of the inventory procedure or the command procedure.

In some implementations, the PDU session parameters comprise a dedicated data network name (DNN) and single network slice selection assistance information (S-NSSAI) .

Some implementations of a base station described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: determine at least one access control parameter for an access category related to AIoT; and transmit the at least one access control parameter via the transceiver to a UE.

Some implementations of a method described herein may include: triggering an inventory procedure or a command procedure towards AIoT devices; receiving at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data; aggregating at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE; and transmitting the message to a node in a CN.

Some implementations of a method described herein may include: determining at least one access control parameter for an access category related to AIoT; and transmitting the at least one access control parameter to a UE.

Some implementations of a processor described herein may include at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: trigger an inventory procedure or a command procedure towards AIoT devices; receive at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data; and aggregate at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE; and transmit the message to a node in a CN.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Figs. 1A and 1B illustrate an example of a wireless communications system that supports AIoT service in accordance with aspects of the present disclosure, respectively;

Fig. 2A illustrates an example of a protocol stack based on CP for AIoT Topology 2 in accordance with aspects of the present disclosure;

Fig. 2B illustrates an example of a protocol stack based on UP for AIoT Topology 2 in accordance with aspects of the present disclosure;

Fig. 3 illustrates a signaling diagram illustrating an example process that supports AIoT service and update in accordance with aspects of the present disclosure;

Fig. 4A illustrates an example of aggregating the IDs of the AIoT devices into a single AIoT message in accordance with aspects of the present disclosure;

Fig. 4B illustrates an example of aggregating the IDs of the AIoT devices into a single NAS PDU in accordance with aspects of the present disclosure;

Fig. 4C illustrates an example of aggregating the IDs of the AIoT devices into a single RRC message in accordance with aspects of the present disclosure;

Fig. 5 illustrates a signaling diagram illustrating an example process that supports AIoT service and update in accordance with aspects of the present disclosure;

Fig. 6 illustrates a flowchart of a method that supports AIoT service in accordance with aspects of the present disclosure;

Figs. 7 and 8 illustrate a signaling diagram illustrating an example process that supports AIoT service in accordance with aspects of the present disclosure, respectively;

Fig. 9 illustrates an example of a device that supports AIoT service in accordance with some aspects of the present disclosure;

Fig. 10 illustrates an example of a processor that supports AIoT service in accordance with aspects of the present disclosure; and

Figs. 11 and 12 illustrate a flowchart of a method that supports AIoT service in accordance with aspects of the present disclosure, respectively.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As described above, in Topology 2, there are two possible options of protocol stack for data transmission, one of which is based on CP and the other is based on UP. For the solution based on CP, there is a need to study how to aggregate the received AIOT device IDs and/or AIOT data in one message.

In view of the above, the present disclosure provides a solution that supports AIoT service. In this solution, a UE triggers an inventory procedure or a command procedure towards AIoT devices. The UE receives at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data. In turn, the UE aggregates at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE. Then, the UE transmits the message to a node in a CN. With this solution, the UE may transmit at least one of the ID or the AIoT data to the node in the CN via a single message. Signalling overhead may be reduced.

Aspects of the present disclosure are described in the context of a wireless communications system.

Fig. 1A illustrates an example of a wireless communications system 100A that supports AIoT service and update in accordance with aspects of the present disclosure. The wireless communications system 100A may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100A may support various radio access technologies. In some implementations, the wireless communications system 100A may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network. In some other implementations, the wireless communications system 100A may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100A may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100A may support radio access technologies beyond 5G. Additionally, the wireless communications system 100A may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. Hereinafter, some implementations of the present disclosure will be described by taking a base station as an example of the network entity 102. Thus, the network entity 102 may be used interchangeably with the base station 102.

The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100A. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100A. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100A. In some other implementations, a UE 104 may be mobile in the wireless communications system 100A.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100A.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU)) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU may be connected to one or more DUsor RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application (APP) server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100A, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100A (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100A, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100A. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100A, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100A may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

Fig. 1B illustrates an example of a wireless communications system 100B that supports AIoT service in accordance with aspects of the present disclosure.

Generally, Fig. 1B illustrates network entities or network functions (NFs) in the core network 106 as shown in Fig. 1A.

As shown in Fig. 1B, the core network 106 may comprise an AIoT function (AIoTF) 120, an AMF 122, a UPF 124 and an application function (AF) 130.

In some implementations, the AIoTF 120 may be a dedicated NF in the 5GC that handles the AIoT service. Alternatively, the AIoTF 120 may be co-located with the AMF 122.

In some implementations, the AIoTF 120 may implement at least one of the following functions:

-Receive and transmit AIoT related data/signalling from/to the AIoT APP server 132;

-Select appropriate UE/RAN reader for the transmission of AIoT data/signalling to the target location/area;

-Receive a registration request from the reader (such as the UE 104) and store information about the reader and information about the associated AIoT devices; or

-Establish an AIoT session with the AIoT AF/AS for transmission.

-Establish an AIoT session with the UE/RAN reader for transmission.

-Authorize and authenticate the AIoT device and reader by interacting with UDM and AUSF.

As shown in Fig. 1B, the wireless communications system 100B also comprises the network entity 102, the UE 104 as well as AIoT devices 130, 132 and 134.

In some implementations, the AIoT device 130 communicates bidirectionally with an intermediate node between the AIoT device 130 and the network entity 102. The intermediate node transfers AIoT data and/or signalling between the base station 102 and the AIoT device 130. The UE 104 may act as the intermediate node between the AIoT device 130 and the base station 102. Hereinafter, the term “UE” may be used interchangeably with the terms “UE reader” , “reader” , “intermediate node” and “intermediate UE” .

Similarly, in some implementations, the AIoT device 132 communicates bidirectionally with an intermediate node between the AIoT device 132 and the network entity 102. The intermediate node transfers AIoT data and/or signalling between the base station 102 and the AIoT device 132. The UE 104 may act as the intermediate node between the AIoT device 132 and the base station 102.

Similarly, in some implementations, the AIoT device 134 communicates bidirectionally with an intermediate node between the AIoT device 134 and the network entity 102. The intermediate node transfers AIoT data and/or signalling between the base station 102 and the AIoT device 134. The UE 104 may act as the intermediate node between the AIoT device 134 and the base station 102.

In some implementations, the AF 126 may support interaction with the core network 106 to provide services, such as influencing data routing decisions, policy control functions or providing third-party services to the network.

It shall be noted that the name of each NF as described above is only exemplary. For example, the AIoTF 120 may be named differently.

It shall be also noted that although two AIoT devices are shown in Fig. 1B by way of example, the wireless communications system 100B may comprise more or less AIoT devices.

Fig. 2A illustrates an example of a protocol stack based on CP for AIoT Topology 2 in accordance with aspects of the present disclosure. In the example of Fig. 2A, the data transmission of the AIoT device 130 is carried by CP signalling exchange over an NAS layer of the UE 104. As shown in Fig. 2A, there may be a direct connection between the UE 104 and the AIoTF 120 via an AIoT Layer. Based on this, once the UE 104 has registered at the AIoTF 120 via the AMF 122, they can communicate with each other directly, i.e., the AMF 122 transparently transfers a message between the AIoTF 120 and the UE 104.

Fig. 2B illustrates an example of a protocol stack based on UP for AIoT Topology 2 in accordance with aspects of the present disclosure. In the example of Fig. 2B, the data transmission of the AIoT device 130 is carried by a PDU session of the UE 104.

Fig. 3 illustrates a signaling diagram illustrating an example process 300 that supports AIoT service in accordance with aspects of the present disclosure. The process 300 may involve the AIoT device 130, the AIoT device 132, the AIoT device 134, the UE 104, and a node in the CN 106.

In some implementations, the node in the CN 106 may comprise the AIoTF 120 in Fig. 1B. Alternatively, the node in the CN 106 may comprise the AMF 122 which is co-located with the AIoTF 120. For the purpose of discussion, the process 300 will be described with reference to Fig. 1B. The process 300 may involve the AIoT device 130, the AIoT device 132, the AIoT device 134, the UE 104 and the AIoTF 120 in Fig. 1B.

As shown in Fig. 3, the UE 104 triggers 310 an inventory procedure or a command procedure towards AIoT devices. For example, the UE 104 triggers an inventory procedure or a command procedure towards the AIoT devices 130, 132 and 134.

Then, the UE 104 receives at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data. For example, the UE 104 receives 320, from the AIoT device 130, an ID of the AIoT device 130 and/or AIoT data. The UE 104 receives 330, from the AIoT device 132, an ID of the AIoT device 132 and/or AIoT data. The UE 104 receives 340, from the AIoT device 134, an ID of the AIoT device 134 and/or AIoT data. Hereinafter, an ID of the AIoT device is also referred to as an AIoT device ID or device ID.

In some implementations, an inventory procedure may be used for identifying individual AIoT devices. If the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134, the UE 104 may receive the IDs of the AIoT devices 130, 132 and 134 from the AIoT devices 130, 132 and 134.

In some implementations, a command procedure may be used for communication with an identified AIoT device to perform an operation of the AIoT device, such as reading (read data from the AIoT device) , writing (write data to the AIoT device) , or disabling (disable the AIoT device temporarily or permanently) . If the UE 104 triggers a command procedure towards the AIoT devices 130, 132 and 134, the UE 104 may receive, from the AIoT devices 130, 132 and 134, the data of the AIoT devices 130, 132 and 134 and AIoT data.

In turn, the UE 104 aggregates 350 the IDs of the AIoT devices 130, 132 and 134 and/or AIoT data into a single message at one of the following: an AIoT layer of the UE 104, a NAS layer of the UE 104 or an RRC layer of the UE 104.

In some implementations, if the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134, the UE 104 may aggregate the IDs of the AIoT devices 130, 132 and 134 into a single message.

In some implementations, if the UE 104 triggers a command procedure towards the AIoT devices 130, 132 and 134, the UE 104 may aggregate the data of the AIoT devices 130, 132 and 134 and the AIoT data into a single message.

Then, the UE 104 transmits 360 the single message to the AIoTF 120.

With the process 300, the UE 104 may transmit the IDs of the AIoT devices 130, 132 and 134 and/or AIoT data to the node in the CN 106 via a single message. Thus, signalling overhead may be reduced.

In some implementations, the UE 104 may aggregate the IDs of the AIoT devices 130, 132 and 134 and/or AIoT data into a single AIoT message at the AIOT layer of the UE 104. This will be described with reference to Fig. 4A.

Fig. 4A illustrates an example of aggregating the IDs of the AIoT devices into a single AIoT message in accordance with aspects of the present disclosure. In the example of Fig. 4A, the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134. In turn, the UE 104 receives IDs of the AIoT devices 130, 132 and 134 from the AIoT devices 130, 132 and 134. The IDs of the AIoT devices 130, 132 and 134 are represented by Device ID 1, Device ID 2 and Device ID 3, respectively. The UE 104 aggregates the Device ID 1, Device ID 2 and Device ID 3 into a single AIoT message.

Specifically, when receiving all AIoT device IDs of the inventory procedure, the AIOT layer of the UE 104 aggregates all of the Device ID 1, Device ID 2 and Device ID 3 into a single message at the AIOT layer. And the AIOT layer of the UE 104 sends the message to a NAS layer of the UE 104. The NAS layer of the UE 104 generates a NAS PDU accordingly and forwards the NAS PDU to an RRC layer of the UE 104. The RRC layer of the UE 104 sends the NAS PDU to the base station 102. The identity for identifying the invention procedure may be also provided together with the aggregated device IDs.

Alternatively, in some implementations, the UE 104 may aggregate the IDs of the AIoT devices 130, 132 and 134 and/or AIoT data into a single NAS PDU at the NAS layer of the UE 104. This will be described with reference to Fig. 4B.

Fig. 4B illustrates an example of aggregating the IDs of the AIoT devices into a single NAS PDU in accordance with aspects of the present disclosure. In the example of Fig. 4B, the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134. In turn, the UE 104 receives IDs of the AIoT devices 130, 132 and 134 from the AIoT devices 130, 132 and 134. The IDs of the AIoT devices 130, 132 and 134 are represented by Device ID 1, Device ID 2 and Device ID 3, respectively. The UE 104 aggregates the Device ID 1, Device ID 2 and Device ID 3 into a single NAS PDU at the NAS layer of the UE 104.

The AIOT layer of the UE 104 may provide assistance information about start and end of the inventory procedure to the NAS layer of the UE 104. The NAS layer of the UE 104 aggregates the Device ID 1, Device ID 2 and Device ID 3 into a NAS PDU based on the assistance information. For example, the AIOT layer of the UE 104 may provide an indication to indicate all AIOT device IDs have been collected to the NAS layer of the UE 104. When receiving the indication, the NAS layer of the UE 104 starts to aggregate all received AIOT device IDs into a single NAS PDU, e.g., a single NAS information element or a NAS message. The identity for identifying the invention procedure may be also provided together with the aggregated device IDs.

Alternatively, in some implementations, the UE 104 may aggregate the IDs of the AIoT devices 130, 132 and 134 and/or AIoT data into a single RRC message at the RRC layer of the UE 104. This will be described with reference to Fig. 4C.

Fig. 4C illustrates an example of aggregating the IDs of the AIoT devices into a single RRC message in accordance with aspects of the present disclosure. In the example of Fig. 4C, the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134. In turn, the UE 104 receives IDs of the AIoT devices 130, 132 and 134 from the AIoT devices 130, 132 and 134. The IDs of the AIoT devices 130, 132 and 134 are represented by Device ID 1, Device ID 2 and Device ID 3, respectively. The UE 104 aggregates the Device ID 1, Device ID 2 and Device ID 3 into a single NAS PDU at the NAS layer of the UE 104.

Specifically, when receiving one device ID, the NAS layer of the UE 104 forwards the device ID to the RRC layer of the UE 104. For example, when receiving Device ID 1, the NAS layer of the UE 104 forwards the Device ID 1 to the RRC layer of the UE 104 via a NAS PDU 1. When receiving Device ID 2, the NAS layer of the UE 104 forwards the Device ID 2 to the RRC layer of the UE 204 via a NAS PDU 2. When receiving Device ID 3, the NAS layer of the UE 104 forwards the Device ID 3 to the RRC layer of the UE 304 via a NAS PDU 3.

The RRC layer of the UE 104 stores the Device ID 1, Device ID 2 and Device ID 3. The upper layer of the UE 104 (e.g., AIoT layer or NAS layer) may provide assistance information about start and end of the inventory procedure to the RRC layer of the UE 104. The RRC layer of the UE 104 aggregates the Device ID 1, Device ID 2 and Device ID 3 into an RRC message based on the assistance information. For example, the upper layer of the UE 104 (e.g., AIoT layer or NAS layer) provides an indication to indicate all AIOT device IDs have been collected to the RRC layer of the UE 104. When receiving the indication, the RRC layer of the UE 104 starts to aggregate all received AIOT device IDs into a single RRC message. For example, the RRC layer of the UE 104 arranges each AIoT device ID as a field or information element (IE) in the RRC message. The identity for identifying the invention procedure may be also provided together with the aggregated device IDs.

It shall be noted that although some implementations of aggregating the IDs of the AIoT devices into a single message have been described by taking the inventory procedure for example, the UE 104 may aggregating the IDs of the AIoT devices and AIoT data into a single message for the command procedure in a similar way. Details of these implementations are omitted for brevity.

In some implementations, the UE 104 may configured with a first timer. The first timer is used to determine whether the inventory procedure or the command procedure is successful or not.

In some implementations, the UE 104 may start the first timer upon receiving an inventory request or a command request from the AIoTF 120. Alternatively, the UE 104 may start the first timer upon triggering the inventory procedure or the command procedure towards the AIoT devices.

In some implementations, the UE 104 stops the first timer if the UE 104 receives all of IDs of the AIoT devices for the inventory procedure or the UE 104 receives all of AIoT data for the command procedure.

Alternatively, in some implementations, the UE 104 stops the first timer if the UE 104 have transmitted the single message to the AIoTF 120.

Alternatively, in some implementations, the UE 104 stops the first timer if a higher layer of the UE 104 provides all of the IDs of the AIoT devices to a lower layer of the UE 104. For example, the UE 104 stops the first timer if the NAS layer of the UE 104 provides all of the IDs of the AIoT devices to the RRC layer of the UE 104.

Alternatively, in some implementations, the UE 104 stops the first timer if a higher layer of the UE 104 provides all of the AIoT data to a lower layer of the UE 104. For example, the UE 104 stop the first timer if the NAS layer of the UE 104 provides all of the AIoT data to the RRC layer of the UE 104.

In some implementations, if only part of the IDs of the AIoT devices for the inventory procedure is received upon expiration of the first timer, the UE 104 may transmit a first indication to the AIoTF 120. The first indication indicates partial inventory failure.

Alternatively, in some implementations, if only part of the AIoT data for the command procedure is received upon expiration of the first timer, the UE 104 may transmit a second indication to the AIoTF 120. The second indication indicates partial command failure.

In some implementations, if none of the IDs of the AIoT devices for the inventory procedure is received upon expiration of the first timer, the UE 104 may transmit a third indication to the AIoTF 120. The third indication indicates inventory failure.

In some implementations, if none of the AIoT data for the command procedure is received upon expiration of the first timer, the UE 104 may transmit a fourth indication to the AIoTF 120. The fourth indication indicates command failure.

In some implementations, the UE 104 may determine the number of AIoT device IDs to be collected for an inventory procedure according to the slot counter 2^Q-1, where Q is an integer in the range of 0 to 15. The number of AIoT device IDs to be collected may be equal to or smaller than the slot counter 2^Q-1.

In some implementations, the AIoTF 120 may provide the number of AIoT device IDs to be collected in an inventory procedure to the UE 104. When the first timer expiries, if the number of AIoT device IDs that has been collected is less than the number of AIoT Device IDs to be collected, the UE 104 shall treat the inventory procedure is ‘partial failure’a nd transmit the first indication to the AIoTF 120.

In some implementations, the UE 104 may transmit at least one of the first indication, the second indication, the third indication and the fourth indication to the AIoTF 120 by an explicit or implicit indication. For example, the UE 104 may transmit a message comprising the first indication to the AIoTF 120. Alternatively, the UE 104 may transmit a message to the AIoTF 120 and the message itself indicates partial inventory failure.

Alternatively, in some implementations, the first timer can be maintained in the node in the CN 106. The node in the CN 106 can be the AIoTF 120 or the AMF 122 which is integrated with AIoT function.

In such implementations, when the AIoTF 120 sends the inventory request to the UE 104, the AIoTF 120 starts the first timer. When the UE 104 collects all the device IDs of the inventory procedure, the AIoTF 120 stops the first timer. When the first timer expiries, if the AIoTF 120 has not received all AIOT devices IDs, the AIoTF 120 shall treat the inventory procedure as partial failure. If none of AIoT device IDs has received by the AIoTF 120, the AIoTF 120 shall treat the inventory procedure as failure.

In some implementations, the UE 104 may start a second timer upon or when aggregating at least one of the ID of the at least one first AIoT device or the AIoT data into the single message. If the UE 104 is not able to transmit the single message to the AIoTF 120 upon expiration of the second timer, the UE 104 may delete the at least one of the ID of the at least one first AIoT device or the AIoT data. If the UE 104 is able to transmit the single message to the AIoTF 120 upon expiration of the second timer, the UE 104 may store the at least one of the ID of the at least one first AIoT device or the AIoT data, and retry to perform access attempt to the base station 102.

For example, when the second timer expires, if the UE 104 is not able to transmit the AIOT device IDs to the base station 102 due to radio link problem between the UE 104 and the base station 102, the UE 104 may delete the received AIOT device IDs and treat the inventory procedure as failed. Otherwise, the UE 104 may store the received AIOT device IDs and retry to access attempt to the base station 102.

In some implementations, the second timer may be maintained in the AIOT layer, NAS layer or RRC layer of the UE 104 respectively.

Fig. 5 illustrates a signaling diagram illustrating an example process 500 that supports AIoT service in accordance with aspects of the present disclosure. The process 500 may be considered as an example implementation of the process 500. The process 500 may involve the AIoT device 130, the AIoT device 132, the UE 104, the base station 102 and the node in the CN 106.

In some implementations, the node in the CN 106 may comprise the AIoTF 120 in Fig. 1B. Alternatively, the node in the CN 106 may comprise the AMF 122 which is co-located with the AIoTF 120. For the purpose of discussion, the process 500 will be described with reference to Fig. 1B. The process 500 may involve the AIoT device 130, the AIoT device 132, the UE 104, the base station 102 and the AIoTF 120 in Fig. 1B.

As shown in Fig. 5, the AIoTF 120 transmits 510 an inventory request to the base station 102. For example, the AIoTF 120 may transmit the inventory request by transmitting a NAS PDU. The NAS PDU may comprise the inventory information for AIoT devices. The purpose of Inventory is to identify individual AIoT devices, i.e., for collection of AIoT device IDs.

In some implementations, the inventory information may comprise device information. The device information may be device ID, device group ID, and/or device type. The device type refers to type 1, 2A or 2B.

In some implementations, the inventory information may comprise the number of AIoT device IDs to be collected for an inventory procedure.

Alternatively or additionally, in some implementations, the inventory information may comprise a value of Q, where Q is an integer in the range of 0 to 15.

In some implementations, the UE 104 may need to distinguish whether the NAS PDU is a normal NAS PDU (that should be treated by legacy NAS Mobility Management (MM) or NAS SM) or a AIoT NAS PDU (that carries signalling or data for AIoT device) . The AIoTF 120 may transmit, to the UE 104, an explicit or implicit indication to indicate it is an AIoT NAS PDU. For example, the AIoTF 120 may transmit, to the UE 104, the NAS PDU which comprises the explicit indication indicating it is an AIoT NAS PDU. Alternatively, the AIoTF 120 may transmit the NAS PDU to the UE 104 and the NAS PDU itself may indicate it is an AIoT NAS PDU.

Furthermore, in some implementations, the indication may also indicate it is for inventory or for command or for both inventory and command.

Upon receiving the inventory request, the base station 102 transmits 520 the inventory request to the UE 104.

In some implementations, upon receiving the inventory request, the UE 104 may trigger the inventory procedure towards AIoT devices by transmitting a paging message. For example, the UE 104 may transmit 530 a paging message to the AIoT device 130 and transmit 532 the paging message to the AIoT device 132.

In some implementations, the UE 104 may perform the inventory procedure based on the inventory request by triggering a random access procedure for each of the AIoT devices 130 and 132.

In some implementations, following the Slotted ALOHA-based random access procedure in Radio Frequency Identification (RFID) , the random access procedure in 5G system for the AIoT device 130 may comprise the following actions.

The UE 104 transmits 540 a downlink signal (similar to Query or QueryRep signal in RFID) to trigger the AIoT device 130 to perform access.

The AIoT device 130 performs 542 an AIoT message 1 transmission (Msg 1) .

Once receiving the Query signal, the AIoT device 130 shall preload into its slot number a value between 0 and 2^Q-1, where Q is an integer in the range of 0 to 15. The AIoT device 132 decrement its slot counter every time it receives a Query signal and trigger to report the device ID when the slot counter reaches ‘0000’ .

For example, the AIoT device 130 joining this access round randomly selects one slot number j among N=fun. (Q) slots. If j=0, the AIoT device 130 performs UL transmission based on the scheduling information indicated by the UE 104, including at least a Random Number (RN) 16.

In another example, when the AIoT device 130 receives the paging message for inventory, the AIoT device 130 that is subjected for the inventory procedure starts a timer. When the timer expires and the AIoT device 130 has not received the Query signal or has not provided the device ID to the UE 104, the AIoT device 130 terminates the inventory procedure and deletes the context for the inventory (e.g., the stored slot counter and etc. ) .

The UE 104 transmits 544 an Access Response (Msg 2) . The UE 104 transmits acknowledgement (ACK) with the same RN16 to acknowledge the successful reception and scheduling information for next UL transmission.

The AIoT device 130 performs 546 AIoT Device ID Reporting (Msg 3) . Based on the Msg2, the AIoT device 130 transmits corresponding parameters asked by paging for inventory, i.e., the AIoT device ID, as protocol control/eXtended protocol control (PC/XPC) , electronic product code (EPC) , packet cyclic redundancy check (CRC) in RFID, this is referred to Msg3.

Optionally, the UE 104 transmits 548 a message 4 (Msg4) to acknowledgement the reception of the ID of the AIoT device 130.

In addition, the UE 104 stores 550 the ID of the AIoT device 130.

Similarly, the random access procedure in 5G system for the AIoT device 132 may comprise the following actions.

The UE 104 transmits 560 a downlink signal (similar to Query or QueryRep in RFID) to trigger the AIoT device 132 to perform access.

The AIoT device 132 performs 562 an AIoT message 1 transmission (Msg 1) . Each AIoT device joining this access round randomly selects one slot number j among N=fun. (Q) slots. If j=0, the AIoT device 132 performs UL transmission based on the scheduling information indicated by the UE 104, including at least an RN16.

The UE 104 transmits 564 an Access Response (Msg 2) . The UE 104 transmits acknowledgement (ACK) with the same RN16 to acknowledge the successful reception and scheduling information for next UL transmission.

The AIoT device 132 performs 566 AIoT Device ID Reporting (Msg 3) . Based on the Msg2, the AIoT device 132 transmits corresponding parameters asked by paging for inventory, i.e., the AIoT device ID, as PC/XPC, EPC, packet CRC in RFID, this is referred to Msg3.

Optionally, the UE 104 transmits 568 a message 4 (Msg4) to acknowledgement the reception of the ID of the AIoT device 132.

In turn, the UE 104 aggregates 570 the IDs of the AIoT devices 130 and 132 into a single message.

In some implementations, the UE 104 may aggregates all AIoT Device IDs into the single message when the inventory procedure is complete. For example, when the UE 104 have performed 2^Q-1 Query procedure successfully, the UE 104 may determine the inventory procedure is complete and aggregate the AIoT device IDs. For example, once performing Query procedure once, the UE 104 shall set 2^Q = 2^Q-1. When the 2^Q is equal to 0, the UE 104 may determine the inventory procedure is complete and aggregate the AIoT device IDs. The value of Q can be provided by the AIoTF 120.

In some implementations, the UE 104 may aggregate the IDs of the AIoT devices 130 and 132 by performing the actions in any of the examples in Figs. 4A, 4B and 4C.

Then, the UE 104 transmits 580 the single message to the base station 102.

Upon receiving the single message, the base station 102 transmits 590 the single message to the AIoTF 120.

In some implementations, in RRC_CONNECTED state, the UE 104 performs Radio Link Monitoring (RLM) in the active bandwidth part (BWP) based on reference signals (synchronization signal block (SSB) /channel state information reference signal (CSI-RS) ) and signal quality thresholds configured by the base station. The UE 104 declares Radio Link Failure (RLF) when one of the following criteria are met:

‐ Expiry of a radio problem timer started after indication of radio problems from the physical layer (if radio problems are recovered before the timer is expired, the UE stops the timer) ; or

‐ Expiry of a timer started upon triggering a measurement report for a measurement identity for which the timer has been configured while another radio problem timer is running; or

‐ radio link control (RLC) failure.

If the UE 104 suffers RLF, the UE 104 shall select a suitable cell and perform RRC re-establishment. If the UE 104 cannot select a suitable cell, the UE 104 shall enter to RRC_IDLE state. In this case, the UE 104 is not able to transmit or receive data or signalling to/from the base station 102. But towards AIoT devices, there may be an ongoing inventory procedure between the UE 104 and the AIoT devices. Thus, in case of radio link failure between UE 104 and the base station 102, there is a need to study how to handle the ongoing inventory procedure.

Hereinafter, some implementations of handling the ongoing inventory procedure in case of radio link failure will be described.

In some implementations, when the UE 104 detects radio link failure between the UE 104 and the base station 102, the UE 104 may suspend the inventory procedure or the command procedure in an air interface between the UE 104 and at least one second AIoT device among the AIoT devices.

In some implementations, the UE 104 may suspend the inventory procedure by performing the following:

‐ stopping transmitting a downlink signal to trigger the at least one second AIoT device to report an ID of the at least one second AIoT device; or terminating the ongoing random access procedure for AIoT device IDs;

‐ maintaining a latest value of a slot counter 2^Q; and

‐ storing the ID of the at least one first AIoT device received from the at least one first AIoT device.

In some implementations, the UE 104 may transmit a fifth indication to the at least one second AIoT device. The fifth indication indicates that the inventory procedure or the command procedure is suspended.

In some implementations, the UE 104 may resume the inventory procedure or the command procedure once the UE 104 reconnects to the base station 102.

In some implementations, the UE 104 may resume the inventory procedure by performing the following:

‐ starting to transmit the downlink signal to trigger the at least one second AIoT device to report the ID of the at least one second AIoT device; and

‐ transmitting a sixth indication to the at least one second AIoT device, wherein the sixth indication indicates that the inventory procedure is resumed.

Consider the example of Fig. 5. The UE 104 may detect radio link failure between the UE 104 and the base station 102 after receiving 546 the ID of the AIoT device 130. When the UE 104 detects radio link failure, the UE 104 may suspend the inventory procedure in an air interface between the UE 104 and the AIoT device 132.

For example, in order to suspend the inventory procedure, the UE 104 stops transmitting 560 the downlink signal to trigger the AIoT device 132 to report an ID of the AIoT device 132, maintains a latest value of a slot counter 2^Q and stores 550 the ID of the AIoT device 130 received from the AIoT device 130.

For another example, the UE 104 may detect radio link failure between the UE 104 and the base station 102 after transmitting 560 the downlink signal to trigger the AIoT device 132 to report an ID of the AIoT device 132. In this example, when the UE 104 detects radio link failure, the UE 104 may suspend the inventory procedure in an air interface between the UE 104 and the AIoT device 132 by terminating the ongoing random access procedure for the ID of the AIoT device 132.

The UE 104 may transmit the fifth indication to the AIoT device 132. The fifth indication indicates that the inventory procedure is suspended.

When the AIoT device 132 receives the fifth indication, the AIoT device 132 that has not reported a device ID to the UE 104 stores the latest slot number and stops monitoring the Query or QuerRep signal or Query like signal.

Once the UE 104 reconnects to the base station 102, the UE 104 may resume the inventory procedure. For example, in order to resume the inventory procedure, the UE 104 may start to transmit 560 the downlink signal to trigger the AIoT device 132 to report the ID of the AIoT device 132 by using using the stored value of the slot counter 2^Q. In addition, the UE 104 transmits the sixth indication to the AIoT device 132. The sixth indication indicates that the inventory procedure is resumed.

In some implementations, if the UE 104 is not able to recover from radio link failure, e.g., the UE 104 cannot find a suitable cell and enters RRC_IDLE state, the UE 104 shall terminate the inventory procedure. For example, the UE 104 may release all the context related to the inventory procedure and discard all stored device IDs. In addition, the UE 104 may send an indication or physical layer signal to inform the at least one second AIoT device (e.g., the AIoT device 132) that the inventory procedure is terminated. The at least one second AIoT device can treat the inventory procedure is terminated and corresponding context is released.

Alternatively, in some implementations, when the UE 104 detects radio link failure, the UE 104 may continue the inventory procedure or the command procedure in an air interface between the UE 104 and at least one second AIoT device among the AIoT devices, and store at least one of the following: the ID of the at least one first AIoT device, an ID of the at least one second AIoT device, or the AIoT data.

In some implementations, the UE 104 may try to transmit at least one of the following to the AIoTF 120 once the UE 104 reconnects to the base station 102: the ID of the at least one first AIoT device, an ID of the at least one second AIoT device, or the AIoT data.

In some implementations, the UE 104 may transmit an eighth indication to the base station 102. The eighth indication indicates that there is at least one of the following available to be reported to the base station 102: the ID of the at least one first AIoT device, the ID of the at least one second AIoT device, or the AIoT data. When receiving the eighth indication, the base station 102 may configure the UE 104 to report at least one of the following: the ID of the at least one first AIoT device, the ID of the at least one second AIoT device, or the AIoT data.

In some implementations, if the UE 104 is not able to recover from radio link failure, e.g., the UE 104 cannot find a suitable cell and enters RRC_IDLE state, the UE 104 shall terminate the inventory procedure. For example, the UE 104 may release all the context related to the inventory procedure and discard all stored device IDs.

Consider the example of Fig. 5. The UE 104 may detect radio link failure between the UE 104 and the base station 102 after receiving 546 the ID of the AIoT device 130. When the UE 104 detects radio link failure, the UE 104 may continue the inventory procedure in an air interface between the UE 104 and the AIoT device 132. The UE 104 may store the IDs of the AIoT devices 130 and 132.

The UE 104 may try to transmit the IDs of the AIoT devices 130 and 132 to the AIoTF 120 once the UE 104 reconnects to the base station 102.

The UE 104 may transmit an eighth indication to the base station 102. The eighth indication indicates that there are the IDs of the AIoT devices 130 and 132 available to be reported to the base station 102. When receiving the eighth indication, the base station 102 may configure the UE 104 to report the IDs of the AIoT devices 130 and 132.

In some implementations, the UE 104 performs an RRC Connection Reestablishment procedure after radio link failure. If the RRC Connection Reestablishment procedure fails, the UE 104 enters to RRC_IDLE state. If there is ongoing inventory procedure in the air interface between the UE 104 and the AIoT devices, e.g., in the AIoT layer of the UE 104, the UE 104 shall trigger an RRC connection setup procedure to report the received AIoT device IDs in the upper layer. In the RRC Connection Setup procedure, an access category related to AIoT and RRC cause related to AIoT should be defined.

Hereinafter, some implementations of the access category and RRC cause related to AIoT will be described. The access category related to AIoT is also referred to as an access category X.

In some implementations, the access category related to AIoT is associated with a first type of access attempt. The first type of access attempt is related to one of the following: signaling transmission originated from the NAS layer or the AIoT layer of the UE 104, or data transmission originated from the NAS layer or the AIoT layer of the UE 104.

In some implementations, the access category related to AIoT is associated with at least one of the following: the NAS layer or the AIoT layer of the UE 104 has the ID of the at least one first AIoT device available to be transmitted, or the NAS layer or the AIoT layer of the UE 104 has the AIoT data available to be transmitted.

In some implementations, if an RRC connection reestablishment procedure fails after radio link failure between the UE 104 and the base station 102, the UE 104 may perform an access attempt to transmit at least one of the ID of the at least one first AIoT device or the AIoT data.

In some implementations, in order to select or determine the access category applicable for the access attempt, the NAS layer or the AIoT layer of the UE 104 may check rules in Table 1 and use the access category for which there is a match for access barring check. The access category X related to AIoT is defined. The mapping rule is defined for the access category X as shown in Table 1.

Table 1: Mapping table for access category related to AIoT

In some implementations, the UE 104 may receive, from the base station 102 or a further base station, at least one access control parameter for the access category related to AIoT. The further base station may be different from the base station 102. In turn, the UE 104 may perform, based on the at least one access control parameter, access barring check for the access category related to AIoT.

In some implementations, the at least one access control parameter for the access category related to AIoT comprises at least one of the following:

‐ access barring factor which represents a probability that the access attempt would be allowed during the access barring check,

‐ access barring time which indicates average time before a new access attempt is to be performed after the access attempt was barred at the access barring check for the access category, or

‐ access baring for access identity which indicates whether the access attempt is allowed for each access identity.

In some implementations, when the UE 104 requests the RRC Connection Setup procedure, the UE 104 may perform access barring check as shown in Fig. 6.

Fig. 6 illustrates a flowchart of a method 600 for access barring check in accordance with aspects of the present disclosure. The method 600 may be considered as an example implementation of the action 360 in Fig. 3 or 580 in Fig. 5.

As shown in Fig. 6, at 610, the UE 104 determines whether the selected Access Identities in “access control parameters” is set to zero.

If the selected Access Identities in “access control parameters” is set to zero, the UE 104 considers the access attempt as allowed at 620.

If the selected Access Identities in “access control parameters” is not set to zero, the UE 104 draws or determine, at 630, a random number uniformly distributed in a range of zero to one. The random number is represented by “rand” .

At 640, the UE 104 determines whether the random number “rand” is lower than a value indicated by an access barring factor for the access category X among the at least one access control parameter.

If the random number “rand” is lower than the value indicated by the access barring factor, the UE 104 considers access attempt as allowed at 650.

If the random number “rand” is equal to or higher than the value indicated by the access barring factor, the UE 104 considers the access attempt as barred at 660.

In some implementations, if the access attempt is considered as barred, the UE 104 may draw a random number 'rand'that is uniformly distributed in a range of zero to one. In addition, the UE 104 may start a timer Txxx for the access category X with the timer value calculated as follows, using the access barring time included in “access control parameters” . For example, the UE 104 may calculate the timer value based on the following:
Txxx = (0.7+ 0.6 *rand) *access barring time (1) .

If the timer Txxx is running for the access category X, the UE 104 considers the access attempt as barred.

In some implementations, if the NAS layer or the AIoT layer of the UE 104 has the ID of the at least one first AIoT device or the AIoT data available to be transmitted, the UE 104 may provide, from the NAS layer or the AIoT layer to the RRC layer, a cause related to AIoT for triggering an RRC state transition from an RRC_INACTIVE state to an RRC_CONNECTED state.

In some implementations, the cause related to AIoT indicates that the ID or the AIoT data is available or ready to be transmitted.

In some implementations, in case of UP based solution, the connection between the UPF 124 and the AIoTF 120 needs to be established for the data transmission of the specific PDU session. Thus, there is a need to study how to establish the connection between the UPF 124 and the AIoTF 120.

For the PDU session establishment, the AIoTF 120 needs to provide its user plane information to the UE 104. The UE 104 establishes a PDU session towards an SMF by providing PDU session parameters related to user plane AIoT. The SMF selects proper UPF based on PDU session parameters and establish the connection between the UPF 124 and the AIoTF 120. Hereinafter, PDU session parameters related to user plane AIoT are also referred to as user plane AIoT related PDU session parameters. This will be described with reference to Figs. 7 and 8.

Fig. 7 illustrates a signaling diagram illustrating an example process 700 that supports AIoT service in accordance with aspects of the present disclosure. The process 700 may involve the UE 104, the base station 102, the AMF 122, the UPF 124 and the AIoTF 120 in Fig. 1B.

Generally, in the process 700, PDU session establishment between the AIoTF 120 and the UE 104 is initiated by the AIoTF 120.

As shown in Fig. 7, if the AIoTF 120 decides to utilize a PDU session of the UE 104 for AIoT inventory and/or command and there is no established secure user plane connection between the UE 104 and the AIoTF 120, the AIoTF 120 invokes 710 Namf_communication_N1N2MessageTransfer service operation to send the user plane information about the AIoTF 120 to the AMF 122 in a NAS container to indicate utilization of user plane for A-IOT inventory and/or command.

In some implementations, the user plane information about the AIoTF 120 includes at least one of the user plane address of the AIoTF 120 and security related information. The AIoTF 120 allocates an ID, i.e. the AIoT UP connection ID to be used to associate the user plane connection to be established with the UE 104 and includes this AIoT UP connection ID in the user plane information. The AIoTF 120 associates the target UE identity (subscription permanent identifier (SUPI) and/or generic public subscription identifier (GPSI) ) with this AIoT UP connection ID.

When the AMF 122 receives the user plane information from the AIoTF 120, the AMF 122 720 sends it to the UE 104 via a DL NAS TRANSPORT message.

If there is no established applicable PDU session for the user plane AIoT service, the UE 104 uses the URSP as defined in TS 23.503 which includes user plane AIoT related PDU session parameters to establish the PDU session for A-IOT inventory and/or command. The UE 104 may send 730 an acknowledgement to the AIoTF 120 through the AMF 122 to indicate a success of utilization of a user plane connection for AIoT inventory and/or command or a failure to utilize the user plane connection, e.g. no suitable PDU session established.

In some implementations, the user plane AIoT related PDU session parameters comprise a dedicated data network name (DNN) and single network slice selection assistance information (S-NSSAI) .

The AMF 122 sends 740 the received acknowledgement to the AIoTF 120 via Namf_N1messageNotify service.

In this way, the UE 104 establishes a secured user plane connection with the AIoTF 120. If the AIoTF 120 send its fully qualified domain name (FQDN) to the UE 104, a DNS server/resolver is used to resolve the IP address of the AIoTF 120 (e.g. EASDF or local DNS for local AIoTF address resolution) . After the secured user plane connection has been established successfully, the UE 104 sends the AIoT UP connection ID received in the action 710 to the AIoTF 120 via the secured user plane connection to enable the AIoTF 120 to perform the correlation of the UE 104 with the secured user plane connection.

The AIoTF 120 indicates 750 the AMF 122 in the Nlmf_AIoT_UPNotify message that user plane connection between the UE 104 and the AIoTF 120 has been established.

The AIoTF 120 stores the AIoT-UP connection context as part of the context of the UE 104.

After the secure user plane connection is established, if the AIoTF 120 determines to utilize the user plane connection for AIoT service, AIoT inventory and/or Command messages are transferred between the UE 104 and the AIoTF 120 for data/signalling transmission for AIoT inventory/Command of AIoT devices which are connected with the UE 104.

Fig. 8 illustrates a signaling diagram illustrating an example process 800 that supports AIoT service in accordance with aspects of the present disclosure. The process 800 may involve the UE 104, the base station 102, the AMF 122, the UPF 124 and the AIoTF 120 in Fig. 1B.

Generally, in the process 800, PDU session establishment between the AIoTF 120 and the UE 104 is initiated by the UE 104.

As shown in Fig. 8, the UE 104 sends 810 a user plane establishment request to the AIoTF 120 via NAS Message if UE 104 decides to request a user plane connection for A-IOT inventory and/or command.

If the UE 104 is authorized based on UE Subscription to use the user plane for AIoT inventory and/or command, the AMF 122 selects 820 an AIoTF (e.g., the AIoTF 120) which capable to establish a user plane session for AIoT with the UE 104. The AMF 122 may either query the NRF or based on local configuration to discover and select a proper AIoTF.

The AMF 122 sends 830 a Nalotf_AIoT_UPConfig Request towards the AIoTF 120 to request set up of an AIoT-UP connection. The AMF 122 shall include the target UE identity (SUPI and/or GPSI) in the request.

If the AIoTF 120 accepts to utilize user plane for AIoT service and there is no established secure user plane connection between the UE 104 and the AIoTF 120, the AIoTF 120 sends 840 the user plane information about the AIoTF 120 to the AMF 122 to indicate UE 104 to accept and utilize user plane for A-IOT service.

The user plane information may include the user plane AIoT address of the AIoTF 120 and security related information. The AIoTF 120 allocates an AIoT UP connection ID to associate the user plane connection to be established with the target UE 104 and includes the AIoT UP connection ID in the user plane information. The AIoTF 120 associates the target UE identity (SUPI and/or GPSI) with the AIoT UP connection ID.

When the AMF 122 receives the user plane information from the AIoTF 120, the AMF 122 forwards 850 it to the UE 104 via a DL NAS TRANSPORT message.

If there is no established secure user plane connection, the UE 104 establishes a secured user plane connection with the AIoTF 120.

In order to establish the secured user plane connection with the AIoTF 120, the UE 104 may transmit 860 the user plane AIoT related PDU session parameters to the AMF 122 via a UL NAS Transfer message.

In some implementations, the user plane AIoT related PDU session parameters comprise a dedicated DNN and S-NSSAI.

In some implementations, the UE 104 uses the user plane AIoT address of the AIoTF 120, together with the information in the URSP, to determine the PDU session parameters including DNN and S-NSSAI. The UE 104 uses the PDU session parameter to establish the PDU session. When the AMF 122 receives the request, it selects a proper UPF (e.g., the UPF 124) based on the DNN and S-NSSAI, and establishes the connection between the UPF 124 and the AIoTF 120.

After the secured user plane connection has been established successfully, the UE 104 sends the AIoT UP connection ID received in the action 850 to the AIoTF 120 via the secured user plane connection to enable the AIoTF 120 to perform the correlation of the UE 104 with this secured user plane connection.

The AIoTF 120 responds 870 to the AMF 122 that user plane connection between the UE 104 and the AIoTF 120 has been established.

Fig. 9 illustrates an example of a device 900 that supports AIoT service in accordance with aspects of the present disclosure. The device 900 may be an example of a network entity 102 as described herein. The device 900 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 900 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 902, a memory 904, a transceiver 906, and, optionally, an I/O controller 908. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 902, the memory 904, the transceiver 906, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904) .

For example, the processor 902 may support wireless communication at the device 900 in accordance with examples as disclosed herein. The processor 902 may be configured to operable to support a means for performing the following: triggering an inventory procedure or a command procedure towards AIoT devices; receiving at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data; and aggregating at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE; and transmitting the message to a node in a CN.

Alternatively, in some implementations, the processor 902 may be configured to operable to support a means for performing the following: determining at least one access control parameter for an access category related to AIoT; and transmitting the at least one access control parameter to a UE.

The processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 902 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 904) to cause the device 900 to perform various functions of the present disclosure.

The memory 904 may include random access memory (RAM) and read-only memory (ROM) . The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 902 cause the device 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 902 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 904 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 908 may manage input and output signals for the device 900. The I/O controller 908 may also manage peripherals not integrated into the device 900. In some implementations, the I/O controller 908 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 908 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 908 may be implemented as part of a processor, such as the processor 906. In some implementations, a user may interact with the device 900 via the I/O controller 908 or via hardware components controlled by the I/O controller 908.

In some implementations, the device 900 may include a single antenna 910. However, in some other implementations, the device 900 may have more than one antenna 910 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 906 may communicate bi-directionally, via the one or more antennas 910, wired, or wireless links as described herein. For example, the transceiver 906 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 906 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 910 for transmission, and to demodulate packets received from the one or more antennas 910. The transceiver 906 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 910 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 910 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

Fig. 10 illustrates an example of a processor 1000 that supports AIoT service in accordance with aspects of the present disclosure. The processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein. The processor 1000 may optionally include at least one memory 1004, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 1002 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. For example, the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction (s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein. The controller 1002 may be configured to track memory address of instructions associated with the memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1002 may be configured to manage flow of data within the processor 1000. The controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1000.

The memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000) . In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000) .

The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1002 and/or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions. For example, the processor 1000 and/or the controller 1002 may be coupled with or to the memory 1004, the processor 1000, the controller 1002, and the memory 1004 may be configured to perform various functions described herein. In some examples, the processor 1000 may include multiple processors and the memory 1004 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 1006 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000) . In some other implementations, the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000) . One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1006 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1006 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.

The processor 1000 may support wireless communication at the device 900 in accordance with examples as disclosed herein. The processor 1000 may be configured to operable to support a means for performing the following: triggering an inventory procedure or a command procedure towards AIoT devices; receiving at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data; and aggregating at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE; and transmitting the message to a node in a CN.

Alternatively, in some implementations, the processor 1000 may be configured to operable to support a means for performing the following: determining at least one access control parameter for an access category related to AIoT; and transmitting the at least one access control parameter to a UE.

Fig. 11 illustrates a flowchart of a method 1100 that supports AIoT service in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by the UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1110, the method may include triggering an inventory procedure or a command procedure towards AIoT devices. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to Fig. 1A or 1B.

At 1120, the method may include receiving at least one of the following from at least one first AIoT device among the AIoT devices: an ID of the at least one first AIoT device or AIoT data. The operations of 1120 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1120 may be performed by a device as described with reference to Fig. 1A or 1B.

At 1130, the method may include aggregating at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a NAS layer or an RRC layer of the UE. The operations of 1130 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1130 may be performed by a device as described with reference to Fig. 1A or 1B.

At 1140, the method may include transmitting the message to a node in a CN. The operations of 1140 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1140 may be performed by a device as described with reference to Fig. 1A or 1B.

Fig. 12 illustrates a flowchart of a method 1200 that supports AIoT service in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or its components as described herein. For example, the operations of the method 1200 may be performed by the base station 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1210, the method may include determining at least one access control parameter for an access category related to AIoT. The operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by a device as described with reference to Fig. 1A or 1B.

At 1220, the method may include transmitting the at least one access control parameter to a UE. The operations of 1220 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1220 may be performed by a device as described with reference to Fig. 1A or 1B.

It shall be noted that implementations of the present disclosure which have been described with reference to Figs. 1 to 8 are also applicable to the device 900, the processor 1000 as well as the methods 1100 and 1200.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

trigger an inventory procedure or a command procedure towards ambient internet of things (AIoT) devices;

receive at least one of the following via the transceiver from at least one first AIoT device among the AIoT devices: an identity (ID) of the at least one first AIoT device or AIoT data; and

aggregate at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a non-access stratum (NAS) layer or a radio resource control (RRC) layer of the UE; and

transmit the message via the transceiver to a node in a core network (CN) .
The UE of claim 1, wherein the processor is further configured to:

start a first timer upon receiving an inventory request or a command request via the transceiver from the node in the CN or upon triggering the inventory procedure or the command procedure; and

stop the first timer based on determining one of the following:

the UE receives all of IDs of the AIoT devices for the inventory procedure,

the UE receives all of AIoT data for the command procedure,

the UE have transmitted the message to the node in the CN,

a higher layer of the UE provides all of the IDs of the AIoT devices to a lower layer of the UE, or

a higher layer of the UE provides all of the AIoT data to a lower layer of the UE.
The UE of claim 2, wherein the processor is further configured to:

based on determining that only part of the IDs of the AIoT devices for the inventory procedure is received upon expiration of the first timer, transmit a first indication via the transceiver to the node in the CN, wherein the first indication indicates partial inventory failure; or

based on determining that only part of the AIoT data for the command procedure is received upon expiration of the first timer, transmit a second indication via the transceiver to the node in the CN, wherein the second indication indicates partial command failure.
The UE of claim 2, wherein the processor is further configured to:

based on determining that none of the IDs of the AIoT devices for the inventory procedure is received upon expiration of the first timer, transmit a third indication via the transceiver to the node in the CN, wherein the third indication indicates inventory failure; or

based on determining that none of the AIoT data for the command procedure is received upon expiration of the first timer, transmit a fourth indication via the transceiver to the node in the CN, wherein the fourth indication indicates command failure.
The UE of claim 1, wherein the processor is further configured to:

start a second timer upon aggregating at least one of the ID or the AIoT data into the single message; and

based on determining that the UE is not able to transmit the message to the node in the CN upon expiration of the second timer, delete the at least one of the ID or the AIoT data.
The UE of claim 5, wherein the processor is further configured to:

based on determining that the UE is able to transmit the message to the node in the CN upon expiration of the second timer,

store the at least one of the ID or the AIoT data, and

retry to perform access attempt to a base station.
The UE of claim 1, wherein the processor is further configured to:

based on detection of radio link failure between the UE and a base station, suspend the inventory procedure or the command procedure in an air interface between the UE and at least one second AIoT device among the AIoT devices.
The UE of claim 7, wherein the processor is configured to suspend the inventory procedure by:

stopping transmitting a downlink signal to trigger the at least one second AIoT device to report an ID of the at least one second AIoT device;

maintaining a latest value of a slot counter; and

storing the ID of the at least one first AIoT device received from the at least one first AIoT device.
The UE of claim 7, wherein the processor is further configured to:

transmit a fifth indication via the transceiver to the at least one second AIoT device, wherein the fifth indication indicates that the inventory procedure or the command procedure is suspended.
The UE of claim 7, wherein the processor is further configured to:

resume the inventory procedure or the command procedure once the UE reconnects to the base station.
The UE of claim 10, wherein the processor is configured to resume the inventory procedure by:

starting to transmit the downlink signal to trigger the at least one second AIoT device to report the ID of the at least one second AIoT device; and

transmitting a sixth indication via the transceiver to the at least one second AIoT device, wherein the sixth indication indicates that the inventory procedure is resumed.
The UE of claim 1, wherein the processor is further configured to:

based on detection of radio link failure,

continue the inventory procedure or the command procedure in an air interface between the UE and at least one second AIoT device among the AIoT devices, and

store at least one of the following: the ID of the at least one first AIoT device, an ID of the at least one second AIoT device, or the AIoT data.
The UE of claim 12, wherein the processor is further configured to:

try to transmit at least one of the following to the node in the CN once the UE reconnects to the base station:

the ID of the at least one first AIoT device,

an ID of the at least one second AIoT device, or

the AIoT data.
The UE of claim 1, wherein the processor is further configured to:

based on determining that an RRC connection reestablishment procedure fails after radio link failure between the UE and a base station, perform an access attempt to transmit at least one of the ID or the AIoT data.
The UE of claim 14, wherein the processor is configured to perform the access attempt by:

receiving, via the transceiver from the base station or a further base station, at least one access control parameter for an access category related to AIoT; and

performing, based on the at least one access control parameter, access barring check for the access category related to AIoT.
The UE of claim 15, wherein the at least one access control parameter for the access category related to AIoT comprises at least one of the following:

access barring factor which represents a probability that the access attempt would be allowed during the access barring check,

access barring time which indicates average time before a new access attempt is to be performed after the access attempt was barred at the access barring check for the access category, or

access baring for access identity which indicates whether the access attempt is allowed for each access identity.
The UE of claim 15, wherein the processor is configured to perform the access barring check by:

drawing a random number uniformly distributed in a range of zero to one;

determining whether the random number is lower than a value indicated by an access barring factor for the access category among the at least one access control parameter;

based on determining that the random number is lower than a value indicated by the access barring factor, considering access attempt as allowed; and

based on determining that the random number is equal to or higher than the value indicated by the access barring factor, considering the access attempt as barred.
A base station comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

determine at least one access control parameter for an access category related to ambient internet of things (AIoT) ; and

transmit the at least one access control parameter via the transceiver to a user equipment (UE) .
A processor for wireless communication, comprising:

at least one memory; and

a controller coupled with the at least one memory and configured to cause the controller to:

trigger an inventory procedure or a command procedure towards ambient internet of things (AIoT) devices;

receive at least one of the following from at least one first AIoT device among the AIoT devices: an identity (ID) of the at least one first AIoT device or AIoT data; and

aggregate at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a non-access stratum (NAS) layer or a radio resource control (RRC) layer of the UE; and

transmit the message to a node in a core network (CN) .
A method performed by a user equipment (UE) , comprising:

triggering an inventory procedure or a command procedure towards ambient internet of things (AIoT) devices;

receiving at least one of the following from at least one first AIoT device among the AIoT devices: an identity (ID) of the at least one first AIoT device or AIoT data; and

aggregating at least one of the ID or the AIoT data into a single message at one of the following: an AIoT layer, a non-access stratum (NAS) layer or a radio resource control (RRC) layer of the UE; and

transmitting the message to a node in a core network (CN) .