WO2025123740A1 - Service d'ido-a de support - Google Patents

Service d'ido-a de support Download PDF

Info

Publication number
WO2025123740A1
WO2025123740A1 PCT/CN2024/112779 CN2024112779W WO2025123740A1 WO 2025123740 A1 WO2025123740 A1 WO 2025123740A1 CN 2024112779 W CN2024112779 W CN 2024112779W WO 2025123740 A1 WO2025123740 A1 WO 2025123740A1
Authority
WO
WIPO (PCT)
Prior art keywords
aiot
access
processor
procedure
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/112779
Other languages
English (en)
Inventor
Mingzeng Dai
Haiyan Luo
Jing HAN
Jie Hu
Lizhuo ZHENG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/112779 priority Critical patent/WO2025123740A1/fr
Publication of WO2025123740A1 publication Critical patent/WO2025123740A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • 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.
  • UE user equipment
  • AIoT ambient internet of things
  • 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) .
  • 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)) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • IoT Internet of Things
  • 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.
  • these devices are named as Ambient IoT (AIoT) devices.
  • AIoT Ambient IoT
  • an AIoT device is an IoT device powered by energy harvesting, with limited energy storage capability.
  • Topology 1 An AIoT device directly and bidirectionally communicates with a network entity.
  • 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.
  • a UE can act as the intermediate node which is under the network control.
  • 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) .
  • CP control plane
  • UP user plane
  • IDs AIOT device identities
  • IDs AIOT device identities
  • the present disclosure relates to UE, base station and methods supporting AIoT service.
  • 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.
  • 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) .
  • 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
  • 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.
  • 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.
  • 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.
  • 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 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 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 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the PDU session parameters comprise a dedicated data network name (DNN) and single network slice selection assistance information (S-NSSAI) .
  • DNN dedicated data network name
  • S-NSSAI single network slice selection assistance information
  • 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.
  • 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 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.
  • 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 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.
  • 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.
  • Figs. 11 and 12 illustrate a flowchart of a method that supports AIoT service in accordance with aspects of the present disclosure, respectively.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE transmits the message to a node in a CN.
  • 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.
  • 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.
  • the wireless communications system 100A may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network.
  • LTE-A LTE-advanced
  • the wireless communications system 100A may be a 5G network, such as an NR network.
  • 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.
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • 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.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • 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.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • 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.
  • 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.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • 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.
  • 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) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • 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) .
  • TRPs transmission-reception points
  • 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) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • 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.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • 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.
  • 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) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • 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.
  • NAS non-access stratum
  • 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.
  • APP application
  • 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) .
  • 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) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • 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 subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first subcarrier spacing e.g., 15 kHz
  • a time interval of a 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.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • 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.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • 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) .
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • 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) .
  • 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) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • Fig. 1B illustrates an example of a wireless communications system 100B that supports AIoT service in accordance with aspects of the present disclosure.
  • Fig. 1B illustrates network entities or network functions (NFs) in the core network 106 as shown in Fig. 1A.
  • NFs network functions
  • the core network 106 may comprise an AIoT function (AIoTF) 120, an AMF 122, a UPF 124 and an application function (AF) 130.
  • AIoTF AIoT function
  • AMF AMF
  • UPF UPF
  • AF application function
  • 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.
  • the AIoTF 120 may implement at least one of the following functions:
  • the wireless communications system 100B also comprises the network entity 102, the UE 104 as well as AIoT devices 130, 132 and 134.
  • 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.
  • the term “UE” may be used interchangeably with the terms “UE reader” , “reader” , “intermediate node” and “intermediate UE” .
  • 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.
  • 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.
  • 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.
  • each NF as described above is only exemplary.
  • the AIoTF 120 may be named differently.
  • 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.
  • the data transmission of the AIoT device 130 is carried by CP signalling exchange over an NAS layer of the UE 104.
  • 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.
  • 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.
  • the node in the CN 106 may comprise the AIoTF 120 in Fig. 1B.
  • the node in the CN 106 may comprise the AMF 122 which is co-located with the AIoTF 120.
  • 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.
  • the UE 104 triggers 310 an inventory procedure or a command procedure towards AIoT devices.
  • the UE 104 triggers an inventory procedure or a command procedure towards the AIoT devices 130, 132 and 134.
  • 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.
  • 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.
  • an ID of the AIoT device is also referred to as an AIoT device ID or device ID.
  • 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.
  • 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.
  • 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.
  • the UE 104 may aggregate the IDs of the AIoT devices 130, 132 and 134 into a single message.
  • the UE 104 may aggregate the data of the AIoT devices 130, 132 and 134 and the AIoT data into a single message.
  • the UE 104 transmits 360 the single message to the AIoTF 120.
  • 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.
  • signalling overhead may be reduced.
  • 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.
  • the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134.
  • 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.
  • the AIOT layer of the UE 104 when receiving all AIoT device IDs of the inventory procedure, 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.
  • 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.
  • the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 104 triggers an inventory procedure towards the AIoT devices 130, 132 and 134.
  • 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 NAS layer of the UE 104 forwards the device ID to the RRC layer of the UE 104.
  • 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.
  • 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.
  • 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
  • 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.
  • the upper layer of the UE 104 e.g., AIoT layer or NAS layer
  • the RRC layer of the UE 104 starts to aggregate all received AIOT device IDs into a single RRC message.
  • the RRC layer of the UE 104 arranges each AIoT device ID as a field or information element (IE) in the RRC message.
  • IE information element
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 104 stops the first timer if the UE 104 have transmitted the single message to the AIoTF 120.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 104 may transmit a first indication to the AIoTF 120.
  • the first indication indicates partial inventory failure.
  • the UE 104 may transmit a second indication to the AIoTF 120.
  • the second indication indicates partial command failure.
  • the UE 104 may transmit a third indication to the AIoTF 120.
  • the third indication indicates inventory failure.
  • the UE 104 may transmit a fourth indication to the AIoTF 120.
  • the fourth indication indicates command failure.
  • 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.
  • the AIoTF 120 may provide the number of AIoT device IDs to be collected in an inventory procedure to the UE 104.
  • the UE 104 shall treat the inventory procedure is ‘partial failure’a nd transmit the first indication to the AIoTF 120.
  • 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.
  • 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.
  • the AIoTF 120 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.
  • 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.
  • 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.
  • 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.
  • the node in the CN 106 may comprise the AIoTF 120 in Fig. 1B.
  • the node in the CN 106 may comprise the AMF 122 which is co-located with the AIoTF 120.
  • 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.
  • the AIoTF 120 transmits 510 an inventory request to the base station 102.
  • 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.
  • 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.
  • the inventory information may comprise the number of AIoT device IDs to be collected for an inventory procedure.
  • the inventory information may comprise a value of Q, where Q is an integer in the range of 0 to 15.
  • 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.
  • the AIoTF 120 may transmit, to the UE 104, the NAS PDU which comprises the explicit indication indicating it is an AIoT NAS PDU.
  • 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.
  • the indication may also indicate it is for inventory or for command or for both inventory and command.
  • the base station 102 Upon receiving the inventory request, the base station 102 transmits 520 the inventory request to the UE 104.
  • 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.
  • 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.
  • 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.
  • a downlink signal similar to Query or QueryRep signal in RFID
  • the AIoT device 130 performs 542 an AIoT message 1 transmission (Msg 1) .
  • 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’ .
  • RN Random Number
  • the AIoT device 130 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 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.
  • ACK acknowledgement
  • 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.
  • PC/XPC protocol control/eXtended protocol control
  • EPC electronic product code
  • CRC packet cyclic redundancy check
  • the UE 104 transmits 548 a message 4 (Msg4) to acknowledgement the reception of the ID of the AIoT device 130.
  • Msg4 message 4
  • the UE 104 stores 550 the ID of the AIoT device 130.
  • 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.
  • a downlink signal similar to Query or QueryRep in RFID
  • 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.
  • ACK acknowledgement
  • 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.
  • the AIoT device ID as PC/XPC, EPC, packet CRC in RFID
  • the UE 104 transmits 568 a message 4 (Msg4) to acknowledgement the reception of the ID of the AIoT device 132.
  • Msg4 message 4
  • the UE 104 aggregates 570 the IDs of the AIoT devices 130 and 132 into a single message.
  • 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.
  • the UE 104 transmits 580 the single message to the base station 102.
  • the base station 102 Upon receiving the single message, the base station 102 transmits 590 the single message to the AIoTF 120.
  • the UE 104 in RRC_CONNECTED state, 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.
  • RLM Radio Link Monitoring
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • the UE 104 declares Radio Link Failure (RLF) when one of the following criteria are met:
  • RLC radio link control
  • 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.
  • 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.
  • 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;
  • 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.
  • the UE 104 may resume the inventory procedure or the command procedure once the UE 104 reconnects to the base station 102.
  • the UE 104 may resume the inventory procedure by performing the following:
  • 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.
  • 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.
  • 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.
  • 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.
  • the AIoT device 132 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.
  • 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.
  • the UE 104 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.
  • the at least one second AIoT device e.g., the AIoT device 132
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 104 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.
  • 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.
  • the base station 102 may configure the UE 104 to report the IDs of the AIoT devices 130 and 132.
  • 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.
  • the access category related to AIoT is also referred to as an access category X.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • the UE 104 may perform, based on the at least one access control parameter, access barring check for the access category related to AIoT.
  • 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
  • ⁇ access baring for access identity which indicates whether the access attempt is allowed for each access identity.
  • 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.
  • the UE 104 determines whether the selected Access Identities in “access control parameters” is set to zero.
  • the UE 104 If the selected Access Identities in “access control parameters” is set to zero, the UE 104 considers the access attempt as allowed at 620.
  • 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” .
  • 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.
  • the UE 104 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.
  • the UE 104 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.
  • the UE 104 may draw a random number 'rand'that is uniformly distributed in a range of zero to one.
  • 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” .
  • the UE 104 If the timer Txxx is running for the access category X, the UE 104 considers the access attempt as barred.
  • 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.
  • the cause related to AIoT indicates that the ID or the AIoT data is available or ready to be transmitted.
  • the connection between the UPF 124 and the AIoTF 120 needs to be established for the data transmission of the specific PDU session.
  • the connection between the UPF 124 and the AIoTF 120 needs to be established for the data transmission of the specific PDU session.
  • 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.
  • 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.
  • PDU session establishment between the AIoTF 120 and the UE 104 is initiated by the AIoTF 120.
  • the AIoTF 120 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.
  • 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.
  • SUPI subscription permanent identifier
  • GPSI generic public subscription identifier
  • the AMF 122 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.
  • 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.
  • the user plane AIoT related PDU session parameters comprise a dedicated data network name (DNN) and single network slice selection assistance information (S-NSSAI) .
  • DNN dedicated data network name
  • S-NSSAI single network slice selection assistance information
  • the AMF 122 sends 740 the received acknowledgement to the AIoTF 120 via Namf_N1messageNotify service.
  • the UE 104 establishes a secured user plane connection with the AIoTF 120.
  • 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) .
  • 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.
  • 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.
  • PDU session establishment between the AIoTF 120 and the UE 104 is initiated by the UE 104.
  • 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.
  • 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.
  • the AIoTF 120 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.
  • the AMF 122 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.
  • the UE 104 establishes a 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.
  • the user plane AIoT related PDU session parameters comprise a dedicated DNN and S-NSSAI.
  • 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.
  • the AMF 122 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.
  • the UE 104 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.
  • the AIoTF 120 stores the AIoT-UP connection context as part of the context of the UE 104.
  • 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. 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.
  • 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.
  • 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.
  • 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) .
  • 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.
  • 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) .
  • the processor 902 may be configured to operate a memory array using a memory controller.
  • 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.
  • 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.
  • 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.
  • BIOS basic I/O system
  • 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.
  • the I/O controller 908 may represent a physical connection or port to an external peripheral.
  • the I/O controller 908 may utilize an operating system such as or another known operating system.
  • the I/O controller 908 may be implemented as part of a processor, such as the processor 906.
  • 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.
  • 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.
  • 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.
  • 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.
  • ALUs arithmetic-logic units
  • 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.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • 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) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • 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.
  • 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.
  • 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.
  • 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.
  • ALUs arithmetic logic units
  • 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) .
  • 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.
  • 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.
  • 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.
  • 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.
  • the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000) .
  • 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.
  • 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.
  • 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.
  • 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.
  • the operations of the method 1100 may be performed by the UE 104 as described herein.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the operations of the method 1200 may be performed by the base station 102 as described herein.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a list of items 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) .
  • 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.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent un UE, une station de base et des procédés prenant en charge un service d'IdO-A. Selon un aspect, un UE déclenche une procédure d'inventaire ou une procédure de commande vers des dispositifs d'IdO-A. L'UE reçoit au moins l'un des éléments suivants à partir d'au moins un premier dispositif d'IdO-A parmi les dispositifs d'IdO-A : un ID du ou des premiers dispositifs d'IdO-A ou des données d'IdO-A. Ensuite, l'UE agrège au moins l'un parmi l'ID et des données d'IdO-A en un seul message à l'un des éléments suivants : une couche d'IdO-A, une couche de NAS ou une couche de RRC de l'UE. Ensuite, l'UE transmet le message à un nœud dans un CN.
PCT/CN2024/112779 2024-08-16 2024-08-16 Service d'ido-a de support Pending WO2025123740A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/112779 WO2025123740A1 (fr) 2024-08-16 2024-08-16 Service d'ido-a de support

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/112779 WO2025123740A1 (fr) 2024-08-16 2024-08-16 Service d'ido-a de support

Publications (1)

Publication Number Publication Date
WO2025123740A1 true WO2025123740A1 (fr) 2025-06-19

Family

ID=96056387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/112779 Pending WO2025123740A1 (fr) 2024-08-16 2024-08-16 Service d'ido-a de support

Country Status (1)

Country Link
WO (1) WO2025123740A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026073253A1 (fr) * 2024-09-30 2026-04-02 Interdigital Patent Holdings, Inc. Procédés de fonctionnement aiot pendant la mobilité d'un lecteur d'ue

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230362881A1 (en) * 2020-09-30 2023-11-09 Lenovo (Beijing) Limited Methods and apparatuses for a relay reselection and data transmission handling procedure in a ue-to-network relay scenario
CN118283642A (zh) * 2022-12-29 2024-07-02 维沃移动通信有限公司 数据传输方法、装置、设备、系统及介质
CN118283105A (zh) * 2022-12-29 2024-07-02 维沃移动通信有限公司 传输方法及装置
CN118338247A (zh) * 2023-01-10 2024-07-12 维沃移动通信有限公司 信息获取、发送方法、装置及通信设备
WO2024148575A1 (fr) * 2023-01-12 2024-07-18 Nec Corporation Dispositif et procédé de communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230362881A1 (en) * 2020-09-30 2023-11-09 Lenovo (Beijing) Limited Methods and apparatuses for a relay reselection and data transmission handling procedure in a ue-to-network relay scenario
CN118283642A (zh) * 2022-12-29 2024-07-02 维沃移动通信有限公司 数据传输方法、装置、设备、系统及介质
CN118283105A (zh) * 2022-12-29 2024-07-02 维沃移动通信有限公司 传输方法及装置
CN118338247A (zh) * 2023-01-10 2024-07-12 维沃移动通信有限公司 信息获取、发送方法、装置及通信设备
WO2024148575A1 (fr) * 2023-01-12 2024-07-18 Nec Corporation Dispositif et procédé de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Discussion on Passive IoT for 5G-Advanced", 3GPP DRAFT; RP-221268, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), vol. TSG RAN, 6 June 2022 (2022-06-06), FR, XP052164429 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026073253A1 (fr) * 2024-09-30 2026-04-02 Interdigital Patent Holdings, Inc. Procédés de fonctionnement aiot pendant la mobilité d'un lecteur d'ue

Similar Documents

Publication Publication Date Title
WO2025156694A1 (fr) Messages de radiomessagerie multiples pour dispositif d'idoa
WO2025123740A1 (fr) Service d'ido-a de support
WO2025145681A1 (fr) Évitement de collision d'id temporaires d'as pour dispositifs aiot
WO2025036090A1 (fr) Dispositifs et procédés de communication
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2025035789A1 (fr) Détection et mise à jour de dispositif aiot
WO2025107663A1 (fr) Procédés et appareils d'un mécanisme d'optimisation de robustesse de mobilité (mro) pour une procédure ultérieure conditionnelle d'ajout ou de changement de cellule de groupe de cellules secondaires primaires (pscell) (cpac)
WO2025222941A1 (fr) Collecte de données pendant des événements de mobilité
WO2024082725A1 (fr) Dispositifs et procédés de communication
WO2026091673A1 (fr) Procédé et appareil de prise en charge de l'internet des objets (ido)
WO2025189796A1 (fr) Économies d'énergie
WO2025218251A1 (fr) Gestion de faisceau
WO2025236289A1 (fr) Accès aléatoire pour un dispositif a-iot
WO2024259991A1 (fr) Défaillance dans une communication par relais
WO2025060464A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2024199052A1 (fr) Procédure de défaillance de trajet indirect due à ltm de l'ue relais dans un trajet multiple
WO2026051364A1 (fr) Mappage entre dispositifs
WO2024244539A1 (fr) Transfert d'informations de radiomessagerie dans une communication relais
WO2024169254A1 (fr) Détermination d'un état de cellule
WO2025050684A1 (fr) Procédés et appareils pour une procédure de mobilité déclenchée par l1/l2 (ltm) et procédure de transfert conditionnel (cho)
WO2025236737A1 (fr) Communication de lp-wus
WO2025251726A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2024093337A1 (fr) Dispositifs et procédés de communication
WO2024234715A1 (fr) Dispositifs et procédés de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24902166

Country of ref document: EP

Kind code of ref document: A1