METHOD AND APPARATUS OF SUPPORTING INTERNET OF THINGS (IoT)
The CN entity in wireless communication systems initiates AIoT localization using RSRP-based methods and multi-RAN coordination to overcome the limitations of reader ID-based localization, achieving enhanced accuracy for diverse AIoT devices.
Patent Information
- Application Number
- PCT/CN2026/095383
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-19
AI Technical Summary
Existing wireless communication systems face challenges in accurately localizing Ambient Internet of Things (AIoT) devices with limited energy storage capabilities, requiring improved localization methods beyond reader ID-based techniques to achieve higher granularity.
Introduce a Core Network (CN) entity, such as AIoTF, to initiate device localization procedures for AIoT devices using methods like RSRP-based localization, and enable single-RAN or multi-RAN coordination, with synchronized uplink signal measurements among multiple RAN nodes.
Enhances localization accuracy for AIoT devices by supporting methods with higher granularity, ensuring efficient and precise positioning of both active and passive AIoT devices within wireless communication systems.
Smart Images

Figure CN2026095383_19112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS OF SUPPORTING INTERNET OF THINGS (IoT)TECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to techniques of supporting internet of things (IoT) , e.g., ambient internet of things (AIoT or A-IoT) .BACKGROUND
[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which 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, or the like) ) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .SUMMARY
[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ” Further, as used herein, including in the claims, a “set” may include one or more elements.
[0004] Some implementations of the methods and apparatuses described herein may further include a core network (CN) entity for wireless communication, which may include: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the CN entity to: determine, a localization method used for a device localization procedure initiated at least for an ambient internet of things (AIoT) device, based on at least one of device subscription data of the AIoT device, application function (AF) subscription data of an associated AF, a message from the AF or a local configuration of the CN entity; transmit, to one or multiple AIoT radio access network (RAN) nodes, a localization related request associated with the localization method; and receive, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.
[0005] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to further cause the CN entity to: determine whether to authorize the message from the AF by checking related data including at least one of the device subscription data or the AF subscription data, context of the AIoT device, or authorization data of the AF, wherein the related data includes at least one of: an allowed positioning indication; allowed localization methods for a device type, including at least one of an allowed reader identity based localization method or an allowed localization method with a granularity more finer than the reader identity based localization method; an allowed maximum number of devices to be localized; information indicating whether multiple RAN localization is allowed; an allowed maximum number of AIoT RAN nodes to be used for device localization; a mapping between device identity information and localization method; or a mapping between device type and localization method; and store part or all of information included in the message from the AF locally or at another CN entity if the message from the AF is authorized.
[0006] In some implementations of the methods and apparatuses described herein, the message from the AF includes at least one of: identity information of the AIoT device; a positioning indication; a device type; a requested localization method; localization accuracy; or a notification method.
[0007] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to further cause the CN entity to: determine to initiate the device localization procedure based on the message from the AF; or determine to initiate the device localization procedure based on at least one the AF subscription data, the device subscription data, authorization data of the AF, or context of the AIoT device.
[0008] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to further cause the CN entity to: receive a registration request message from the AIoT device; and determine to initiate the device localization procedure based on related data including at least one of the device subscription data, the AF subscription data, authorization data of the AF, or context of the AIoT device and the local configuration, wherein the related data includes at least one of: an indication that localization for the AIoT device is needed; an allowed positioning indication; allowed localization methods for a device type, including at least one of an allowed reader identity based localization method or an allowed localization method with a granularity more finer than the reader identity based localization method; information indicating whether multiple RAN localization is allowed; an allowed maximum number of devices to be localized; an allowed maximum number of AIoT RANs nodes to be used for localization; or a mapping between device identity information and localization method; or a mapping between device type and localization method.
[0009] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to further cause the CN entity to: transmit a registration response message to the AIoT device with a localization indication.
[0010] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to further cause the CN entity to: determine whether to use one AIoT RAN node or multiple AIoT RAN nodes for localizing the AIoT device based on at least one of the message from the AF, a last known location of the AIoT device, the device subscription data, the AF subscription data, authorization data of the AF or context of the AIoT device.
[0011] In some implementations of the methods and apparatuses described herein, the localization related request is transmitted to an AIoT RAN node of one or multiple RAN nodes selected for localizing the AIoT device; or transmitted to each of multiple AIoT RAN nodes selected for localizing the AIoT device.
[0012] In some implementations of the methods and apparatuses described herein, the localization related request to a serving AIoT RAN node selected for localizing the AIoT device includes at least one of: identity information of the AIoT device; task identity information; a positioning indication; identity information of other AIoT RAN nodes of multiple AIoT RAN nodes selected for localizing the AIoT device; a notification method; a coordination indication indicating the serving AIoT RAN node to select other AIoT RAN nodes for localizing the AIoT device; information indicating the localization method; or observing configuration parameters to synchronize uplink signal measurements performed by multiple AIoT RAN nodes selected for localizing the AIoT device, including at least time and frequency information parameters.
[0013] In some implementations of the methods and apparatuses described herein, the observing configuration parameters are generated by the CN entity based on radio configuration capability of each AIoT RAN node, or generated by another CN entity, or determined by the CN entity based on local configuration or AF request.
[0014] In some implementations of the methods and apparatuses described herein, the localization related request is carried in an inventory request message with information indicating the localization method, or a localization command request message with or without information indicating the localization method.
[0015] In some implementations of the methods and apparatuses described herein, only the localization related request to a serving AIoT RAN node of multiple AIoT RAN nodes selected for localizing the AIoT device is carried in an inventory request message with information indicating the localization method or a localization command request message with or without information indicating the localization method.
[0016] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to: determine a location of the AIoT device based on the localization related information; or transmit a message with the localization related information to another CN entity to request the another CN entity to determine the location of the AIoT device; and store the location of the AIoT device determined by the CN entity or received from the another CN entity, with associated AIoT RAN node information or RAN reader information.
[0017] In some implementations of the methods and apparatuses described herein, the another CN entity is an AIoT function (AIoTF) supporting the localization method, or a location management function (LMF) selected based on the local configuration or selected from network repository function (NRF) or access and mobility management function (AMF) based on at least one of a target area, information related to supporting of the localization method, last known location of the AIoT device, or RAN reader related information.
[0018] Some implementations of the methods and apparatuses described herein may further include a processor for wireless communication, which may include: at least one controller coupled with at least one memory and configured to cause the processor to: determine, a localization method used for a device localization procedure initiated at least for an AIoT device, based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF or a local configuration of the CN entity; transmit, to one or multiple AIoT RAN nodes, a localization related request associated with the localization method; and receive, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.
[0019] Some implementations of the methods and apparatuses described herein may further include an AIoT RAN node for wireless communication, which may include: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the AIoT RAN node to: receive, a localization related request for an AIoT device from a CN entity or a serving AIoT RAN node of the AIoT device, wherein the localization related request is associated with a localization method determined based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF, or a local configuration of the CN entity; and transmit, to the CN entity or the serving AIoT RAN node, localization related information associated with the AIoT device based on the localization related request.
[0020] In some implementations of the methods and apparatuses described herein, the AIoT RAN node is the serving AIoT RAN node and receives the localization related request from the CN entity, and if the localization related request includes identity information of other AIoT RAN nodes selected for localizing the AIoT device or a coordination indication indicating the serving AIoT RAN node to select other AIoT RAN nodes for localizing the AIoT device, the at least one processor is configured to further cause the AIoT RAN node to transmit the localization related request to the other AIoT RAN nodes to requesting uplink device to reader signal measurements for localizing the AIoT device.
[0021] In some implementations of the methods and apparatuses described herein, a message carrying the localization related request to the other AIoT RAN nodes includes at least one of: identity information of the AIoT device; task identity information; a positioning indication; a notification method; information indicating the localization method; observing configuration parameters to synchronize uplink signal measurements among the multiple AIoT RAN nodes for localizing the AIoT device, including at least the time and frequency information parameters; or identity information of the CN entity.
[0022] In some implementations of the methods and apparatuses described herein, the at least one processor is configured to further cause the AIoT RAN node to: receive the localization related information from the other AIoT RAN nodes; and transmit received localization related information to the CN entity.
[0023] In some implementations of the methods and apparatuses described herein, the AIoT RAN node is an AIoT RAN node of multiple AIoT RAN nodes selected for localizing the AIoT device, and the localization related information is transmitted to the CN entity if receiving the localization related request from the CN entity or from the serving AIoT RAN node with identity information of the CN entity, or to the serving AIoT RAN node if receiving the localization related request from the serving AIoT RAN node.
[0024] In some implementations of the methods and apparatuses described herein, the localization related information includes at least one of: identity information of the AIoT device; task identity information; identity information of corresponding AIoT RAN node; identity information of corresponding RAN reader; location information of the corresponding AIoT RAN node; location information of the corresponding RAN reader; a measured uplink device to reader signal strength value; or uplink transmission power of the AIoT device.
[0025] In some implementations of the methods and apparatuses described herein, the measured uplink device to reader signal strength value is a reference signal receiving power (RSRP) value associated with the AIoT device.
[0026] Some implementations of the methods and apparatuses described herein may further include a method performed by a CN entity, which may include: determining, a localization method used for a device localization procedure initiated at least for an AIoT device, based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF or a local configuration of the CN entity; transmitting, to one or multiple AIoT RAN nodes, a localization related request associated with the localization method; and receiving, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0028] Figure 2 illustrates an example of a procedure of supporting device localization in accordance with aspects of the present disclosure.
[0029] Figure 3 illustrates an example of a CN entity in accordance with aspects of the present disclosure.
[0030] Figure 4 illustrates an example of a processor in accordance with aspects of the present disclosure.
[0031] Figure 5 illustrates an example of an AIoT RAN node in accordance with aspects of the present disclosure.
[0032] Figure 6 illustrates a flowchart of method performed by a CN entity in accordance with aspects of the present disclosure.
[0033] Figure 7 illustrates a flowchart of method performed by an AIoT RAN node in accordance with aspects of the present disclosure.DETAILED DESCRIPTION
[0034] IoT has attracted much attention in wireless communication world, where IoT devices usually have a smaller size, lower complexity, lower power consumption and huger number (e.g., tens or even hundreds of billion IoT devices) than existing UEs. 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, for which the energy may be provided through the harvesting of radio waves, light, motion, heat, or any other power sources that are suitable for providing energy for the devices. For simplicity, such kind of IoT devices may be referred to as AIoT devices (or “tags, ” or just "devices" in some contexts) . In other words, an AIoT device may be an IoT device with limited energy storage capability and powered by energy harvesting.
[0035] Although 3rd generation partnership program (3GPP) Release 19 (R19) has achieved some preliminary agreements on AIoT, there are still some normative works needed to be pursued and studied for AIoT. For example, the list R20 AIoT work item description (WID) is to further study AIoT device localization or positioning to achieve a better granularity than reader identity (ID) level localization as already supported in R19 (e.g., TS 23.369) .
[0036] In accordance with various aspects of the present disclosure, a CN entity (or function or node or the like) , e.g., an AIoTF or the like may determine to initiate a device localization procedure at least for an AIoT device (e.g., referred to as a target device) based on an authorized message from an AF requesting localizing the AIoT device (e.g., referred to as an AF request message) or based on device related data (e.g., device subscription data and / or device context) and / or AF related data (e.g., AF subscription data and / or AF authorization data) .
[0037] Besides legacy AIoT device localization method, e.g., reader ID based localization method, at least a device localization method with a higher granularity than the read ID based localization method is introduced. For example, an uplink device to reader (D2R) signal strength based localization method is proposed for better localization granularity, e.g., including a RSRP based localization method or the like for RSRP level localization. That is, there may be multiple localization methods selectable for localizing the AIoT device. The AIoTF may determine a localization method used for the initiated device localization procedure based on at least one of device subscription data, device context, AF subscription data, AF request message, or a local configuration (e.g., local operator configuration) of the AIoTF.
[0038] The AIoTF may also determine whether to use one AIoT RAN node or multiple AIoT RAN nodes to perform the device localization, which may be respectively referred to as single-RAN based localization or multi-RAN based localization (or multi-RAN coordination localization or the like) . In some cases of multi-RAN coordination localization, the AIoTF may select all the AIoT RAN nodes, or only select the serving AIoT RAN node and request the serving AIoT RAN node to select other AIoT RAN node (s) .
[0039] The AIoTF may transmit, to at least one selected AIoT RAN node (directly or via the serving AIoT RAN node) , a localization related request associated with the localization method. The at least one AIoT RAN node may determine localization related information associated with the AIoT device and transmit the localization related information to the AIoTF (directly or via the serving AIoT RAN node) . The AIoTF may determine the location or position of the AIoT device by itself based on the received localization related information, or transmit the localization related information to another CN entity that is capable of determining the location of the AIoT device.
[0040] Considering 3GPP evolution, terminologies, especially the name of each NF entity (or NF) may change, and thus the related terminologies are only exemplary herein. In future, e.g., in 6G standardization, the network functions providing the same functionality / service may be differently named or may be incorporated or separated. Taking AIoTF as an example, it is assumed to be a dedicated CN network function to handle AIoT related traffics. An exemplary AIoTF may either be a standalone network function, or co-located with the AMF. The main functionalities of the AIoTF may include one or more of the following: Receive and transmit AIoT related data and / or signalling from and / or to the AIoT application server Select appropriate AIoT reader (e.g., UE or radio access network (RAN) ) for the transmission of AIoT data and / or signalling to the target location and / or area and / or AIoT device Receive the registration request from the reader and store the reader information and the associated ambient IoT devices information Establish an AIoT session with the A-IoT AF and / or access stratum (AS) for transmission Authentication and authorization for the device access, which triggers interaction with authentication server function (AUSF) and / or unified data management (UDM) Collect charging data and interact with charging function (CHF) for charging AIoT device and reader context management.
[0041] Aspects of the present disclosure are described in the context of a wireless communications system.
[0042] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
[0043] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN) , a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , 6G NodeB (aNB) or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0044] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN) . In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102. In some embodiments, the NEs 102 may include one or more relay nodes, integrated access and backhaul (IAB) nodes or wireless access backhaul (WAB) nodes which can provide wireless access services for UEs 104. A relay node (or an IAB node or a WAB node) can directly connect to a BS or hop through one or more relay nodes (or one or more IAB or WAB nodes) before reaching the BS.
[0045] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
[0046] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0047] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N3, or another network interface) . In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106) . In some implementations, one or more NE 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) .
[0048] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
[0049] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N3, or another network interface) . The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 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 CN 106 (e.g., one or more network functions of the CN 106) .
[0050] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0051] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0052] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0053] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0054] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0055] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.
[0056] There are various AIoT connectivity topologies, and the following two connectivity topologies are mainly studied: -Topology 1: BS (or the like) <--> AIoT Device; -Topology 2: BS (or the like) <--> intermediate node <--> AIoT Device. Under Topology 1, an exemplary reader is connected to a NE, RAN, RAN node or BS or the like, which may be referred to as next generation (NG) RAN or AIoT RAN etc. The reader connected to a NG RAN or AIoT RAN may be referred to as NE reader, RAN reader, or BS reader etc., and may be a RAN node or BS or NE itself. In some cases, a NG RAN may include one or more RAN readers or B S readers or the like. Communications between the BS reader and AIoTF may be via the AMF or not, which may be referred to direct path (no AMF) or indirect path (via an AMF) respectively. Under Topology 2, the intermediate node acts as an AIoT reader. An exemplary intermediate node may be a UE, which may be referred to as a UE reader. A NE, RAN, RAN node or BS or the like serving a UE reader is AIoT enabled, which may be referred to an AIoT enabled RAN node, AIoT enabled RAN, AIoT BS, NG RAN or the like..
[0057] In any topology, two kinds of services are considered for AIoT, i.e., inventory and command. Regarding command, it may include read, write, and permanently disable etc.
[0058] Different types of AIoT device may have different capabilities. For example, one type of AIoT device is: ~1 μW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, neither reader to device (R2D) nor D2R amplification in the device. The device's D2R transmission is backscattered on a carrier wave provided externally, which may be referred to as Device type 1 or Device 1. Another type of AIoT device is: ≤ a few hundred μW peak power consumption, has energy storage, initial SFO up to 10X ppm, both R2D and / or D2R amplification in the device. The device’s D2R transmission is backscattered on a carrier wave provided externally, which may be referred to as Device type 2a or Device 2a. Yet another type of AIoT device is: ≤ a few hundred μW peak power consumption, has energy storage, initial SFO up to 10X ppm, both R2D and / or D2R amplification in the device, wherein the device’s D2R transmission is generated internally by the device, which may be referred to as Device type 2b or Device 2b and Device C. In other words, for Device 1 and Device 2a, the D2R transmission or message is backscattered on a carrier wave provided externally; while for Device 2b and Device C, the D2R transmission can be started by device itself using its own internally generated carrier wave, and can be called DO-A capable AIoT Device.
[0059] An AIoT device can operate in different modes, e.g., device-terminated (DT) , device-originated -device-terminated triggered (DO-DTT) , or device originated autonomous (DOA) etc. For example, Device 1 and Device 2a or the like can operate in DT or DO-DTT mode, while Device 2b and Device C or the like can operate in DT or DO-DTT or DOA mode.
[0060] AIoT devices, e.g., DT or DO-DTT AIoT device that cannot initiate active message transmissions towards the network may be referred to as passive AIoT devices. For example, it is agreed that an inventory request is sent from a BS reader to the passive AIoT device, e.g., Device 1 or Device 2a or the like, so that the AIoT device can be triggered by the BS reader to perform the access towards the CN, e.g., 5GC etc.
[0061] AIoT devices, e.g., DO-A capable AIoT device that can initiate active message transmissions towards the network may be referred to as active AIoT devices. For example, different from Device 1 and Device 2a, Device type 2b and Device C can access the core network, e.g., 5GC, 6GC or higher generation CN before being inventoried by the core network, and may even decide to send the stored data, e.g., application-layer data via uplink messages without receiving the command (e.g., read) from the AF via the core network. That is, for active AIoT devices, the access device to reader (D2R) transmission can come from the device side without a trigger from the network side.
[0062] In accordance with aspects of the present disclosure, considering different types of AIoT devices with different capabilities, localization methods (or localization types or the like) supported by different types of AIoT devices may be different. For example, passive AIoT devices may only support reader ID based localization method (or reader ID based localization type or the like) , and active AIoT devices may support reader ID based localization method and uplink D2R signal strength based localization method and even more device localization method with a granularity higher than reader ID based localization method (referred to as device localization method with higher granularity) .
[0063] Since a device localization or positioning mechanism needs to support both active AIoT devices and passive AIoT devices simultaneously, it is essential to differentiate and determine which kind of device localization method will be used for localizing a target device, e.g., by the AIoTF at the CN side. In some cases, the association or mapping between device type (and / or device ID) and supported device localization method (s) may be provided at the CN side, e.g., stored at the ambient data management (ADM) or the like. When the target device supports multiple localization methods, the CN side, e.g., by the AIoTF or the like may also need to decide or select a localization method to be used.
[0064] If a device localization method with higher granularity, e.g., an uplink D2R signal strength based localization method is selected, which is based on the calculation of uplink D2R signal strength, how to support an initiated device localization procedure should also be studied. In accordance with aspects of the present disclosure, a device localization procedure may be based on an inventory or command service. When command service is considered, a new command type, e.g., localization command (or positioning command or the like) may be introduced.
[0065] In some cases, to pursue more finer localization results, multi-RAN coordination localization may be applied in accordance with aspects of the present disclosure, where coordination among multiple AIoT RAN nodes will be involved in the same device localization or positioning service. How to support the multi-RAN coordination localization for a single AIoT device also needs to be solved. For example, in accordance with aspects of the present disclosure, observing configuration parameters are introduced to synchronize uplink signal measurements among the multiple AIoT RAN nodes for localizing the AIoT device, which includes at least the time and frequency information parameters, e.g., time window and frequency band to observe and receive the uplink D2R signal.
[0066] More details on various aspects of the present disclosure are illustrated in the following in view of some exemplary implementations. Hereinafter, only taking RSRP based localization method as an example of device localization methods with higher granularity. Persons skilled in the art would determine and understand how to localize an AIoT device using other device localization methods with higher granularity based on the disclosure in view of RSRP based localization method.
[0067] Figure 2 illustrates an example of a procedure of supporting device localization in accordance with aspects of the present disclosure.
[0068] Referring to Figure 2, in some implementations of the present disclosure, an AF may request localizing an AIoT device (only one, e.g., device#1 as an example but not limited to one) via the CN, e.g., AIoTF (or the like) .
[0069] For example, the AF may send a message to AIoTF#1 at step 201, directly if trusted or via a network exposure function (NEF) (or the like) if not trusted, requesting localizing or positioning device#1 (or more) . Such an AF message may be a standalone message or together with (e.g., included in) an inventory or command request message, and include but not limited to part or all of: task ID information (e.g., transaction ID or the like) , target device ID information (or filtering information for a group of AIoT devices) , AF or NEF information as target notification address (e.g., AF ID information, AF address and / or fully qualified domain name FQDN (FQDN) etc. ) , target area, positioning indication, device type, requested (or preferred or the like) localization method (e.g., RSRP based localization method or reader ID based localization method, or a method with higher granularity than reader ID, etc. ) , localization accuracy (e.g., location accuracy, vertical accuracy, horizontal accuracy, and / or localization radius, etc. ) , and a notification method (e.g., periodic, one time, or event based etc. ) . Exemplary events (or conditions) that can be used for an event based notification method include but not limited to part or all of: a detected new registration of DO-A capable AIoT Device, or RSRP threshold, or reader change for the AIoT Device, and moving distance threshold etc. If the indicated event is triggered or met, the CN side needs to trigger or initiate a localization report to the AF (which may need to trigger a device localization procedure first in some cases) .
[0070] For example, in some cases, an exemplary AF message requesting device localization (hereinafter, AF request message, or a positioning request message from AF) may not include an explicit positioning indication, and a positioning request may be implicitly indicated by other information, e.g., localization type, localization accuracy and / or notification method etc. In some cases, an exemplary positioning request message from AF may not include information explicitly indicating the requested device localization method, and the requested device localization method may be implicitly indicated by the localization accuracy. For example, a high localization accuracy indicates that a localization method with a higher granularity, e.g., RSRP based localization method will be used, while a low localization accuracy indicates that a low granularity localization method, e.g., reader ID based localization method will be used.
[0071] It is assumed that AIoTFs have registered their capabilities on whether support AIoT device localization at the NRF and / or ADM. If the NEF receives the AF request message and authorizes the AF, the NEF may select an AIoTF, e.g., from NRF and / or ADM (or the like) or based on the local configuration thereof, and send the AF request message to the selected AIoTF, e.g., AIoTF#1. For example, if the AIoT device is a passive device, the NEF may select an AIoTF that is capable of determining AIoT device location. If the AIoT device is an active device, e.g., DO-A capable device, the NEF may select the serving AIoTF for device localization. If the severing AIoTF, e.g., AIoTF#1 is not capable of determining the AIoT device location, the NEF may also select another AIoTF that is capable of determining the AIoT device location, e.g., AIoTF#2 and send the information related to this AIoTF to the serving AIoTF.
[0072] The AIoTF may perform authorization of the AF request message (directly received or via the NEF) at step 203, e.g., by checking device related data and / or AF related data, e.g., using device ID and / or AF information as the key. The device related data and AF related data may be stored at the ADM (or other NF) or stored locally at AIOTF. For example, the data stored at the ADM may include AF authorization data, AF subscription data, and / or device subscription data (e.g., stored as device profile data) . The data locally stored may include device context, which may also be obtained from the last AIoTF associated with the AIoT device (e.g., last serving AIoTF) . In some cases, the AF authorization data and the AF subscription data may be stored as the same information element (IE) , e.g., both as AF authorization data or AF subscription data.
[0073] Exemplary device related data and / or AF related data used for the authorization may include but not limited to part or all of: an allowed positioning indication allowed localization methods for a device type, e.g., an allowed reader ID based localization method for a passive AIoT device, or allowed reader ID based localization method and allowed RSRP based localization method (or other localization method (s) with a more finer granularity than reader ID based localization method) for an active AIoT device an allowed maximum number of devices to be localized information indicating whether multiple RAN localization is allowed an allowed maximum number of AIoT RAN nodes to be used for device localization a mapping between device identity information and localization method a mapping between device type and localization method.
[0074] Based on the authorization result, the AIoTF may send a response message to the AF (e.g., via the NEF or directly) at step 205, indicating whether the positioning request from the AF for device localization is accepted or rejected, e.g., with a cause value if rejected, and task identity information (e.g., transaction ID) etc. Herein, it is assumed that the AF request message is authorized.
[0075] In some cases, at step 207, the AIoTF may store part or all information indicated in the authorized AF request message locally (e.g., as device context) , and / or in another CN entity, e.g., the ADM (e.g., as AF authorization data, AF subscription data and / or device subscription data etc. ) . For example, AIoTF#1 may store the notification target address (AF address, NEF address) and / or notification method at the ADM as AF subscription data, which may be associated with a device ID and transaction ID, and is used for Device localization.
[0076] At step 209, the AIoTF may determine to initiate or trigger a device localization procedure for the AIoT device, which may be based on the positioning request message from the AF, or based on the local configuration and retrieved data (e.g., checking at least one of the device related data (device subscription data and / or device context) or AF related data (AF subscription data and / or AF authorization data) , e.g., during a device registration procedure or due to other reasons) .
[0077] For example, it is assumed that device#1 is an active AIoT device, e.g., DO-A device, and may send a device registration request message to the AIoTF at step 202, including the device ID information, and / or registration type, etc. Similarly, part or all information included in the device registration request message may be stored, e.g., locally stored as device context at the AIoTF.
[0078] After receiving the device registration request message from the AIoT device, the AIoTF may check the locally stored data (e.g., device context) and / or data stored in the ADM or the like (e.g., device subscription data stored as device profile, AF subscription data and / or AF authorization data etc. ) . For example, besides the data illustrated at step 207, the device related data may further include an indication on whether localization for this AIoT device is needed. If this indication indicates that localization for this AIoT device is needed, the AIoTF may determine to initiate or trigger a device localization procedure for the AIoT device based on the local configuration and other device related data and / or AF related data.
[0079] For the device localization procedure initiated at least for this AIoT device, the AIoTF may need to determine various configurations and other information, e.g., determining the device localization method to be used at step 211 and determining the AIoT RAN nodes (and RAN readers) to be used at step 213 etc.
[0080] Specifically, in some implementations of the present disclosure, at step 211, for an AIoT device at least supporting a localization method with higher granularity and the reader ID based localization method, the AIoTF may determine or select the localization method to be used based on the AF request message, device subscription data, AF subscription data and / or local configuration.
[0081] For example, in some cases that the device localization procedure is initiated based on the AF request message indicating a requested localization method with higher granularity, e.g., a RSRP based localization method, the AIoTF may check whether the requested localization method is allowed for this AIoT device based on the AF subscription data and device subscription data. If any of the AF and AIoT device is not allowed to use the RSRP based localization method, the AIoTF may select an allowed localization method, e.g., the reader ID based localization, or reject the positioning request from the AF.
[0082] In some cases that the AF request message does not indicate the requested localization method or the device localization procedure is initiated based on the local configuration and retrieved data (e.g., device related data and / or AF related data) , the AIoTF may determine or select the localization method to be used based on the local configuration and the retrieved data, e.g., the device type and the allowed localization method for this device type etc.
[0083] In some cases that the AIoTF lacks the device ID information, e.g., the AF request message provides only the target area but not provide the device ID information. The AIoTF may page all AIoT devices within the target area by the inventory service. Then, based on the inventory results received from the associated AIoT RAN node or readers, the AIoTF may check the device subscription data or device context to determine the localization method to be used.
[0084] In some implementations of the present disclosure, at step 213, the AIoTF may determine whether to use one AIoT RAN node or multiple AIoT RAN nodes for localizing the AIoT device and select the AIoT RAN node (s) , which may be based on at least one of the AF request message, the last known location of the AIoT device, the device related data (e.g., device subscription data and / or device context) , or the AF related data (e.g., AF subscription data and / or AF authorization data) . In some cases, if an AIoT RAN node is selected, it means that all RAN readers of the AIoT RAN node are selected. In some cases, the AIoTF may further select part or all RAN readers of the AIoT RAN node used for device localization. In some cases, it depends on the selected AIoT RAN node to further select the RAN reader (s) for the device localization.
[0085] Foe example, the AIoTF may determine to select a single AIoT RAN node or multiple AIoT RAN nodes for the device localization based on the localization accuracy in the AF request message, the last know device location, AIoT RAN node related information and RAN reader related information (e.g., serving area information) .
[0086] Regarding the last known device location, the AIoTF may obtain it in various manners. For example, the AIoTF may retrieve the last known location of the AIoT device from the device subscription data stored in the ADM, or from the last serving AIoTF with the associated reader information (e.g., reader ID information and reader location information etc. ) .
[0087] In accordance with some aspects of the present disclosure, it is assumed that the AIoTF determines to use one AIoT RAN node, e.g., node#1 as one reader (e.g., reader#1) for localizing the AIoT device, that is, single-RAN based localization is used. The AIoTF may transmit a localization related request to the AIoT RAN node at step 215, and receive localization related information from the AIoT RAN node at step 217.
[0088] If a reader ID based localization method is determined for localizing the AIoT device, a legacy device positioning procedure will be applied and not repeat herein. If a localization method with higher granularity, e.g., RSRP based localization is to be used, several proposed solutions to perform the device localization in accordance with aspects of the present disclosure are illustrated in the following.
[0089] Firstly, a device localization procedure initiated based on an AF request message is illustrated as an example, wherein the localization related request may be the same as or different from on that indicated in the AF request message. For example, besides the localization method, in some cases, the notification method sent to the AIoT RAN node from the AIoTF may also be different from that received at the AIoTF, e.g., only including the periodic reporting with waiting time, one time reporting, or new device ID detected triggered reporting, etc.
[0090] In some cases, the device localization procedure is an inventory based procedure. In some cases, a new type of command, e.g., localization or positioning command is defined and the device localization procedure may be performed after receiving the inventory results of the AIoT device.
[0091] Taking an inventory based procedure as an example, the AIoTF may include a localization related request to the selected AIoT RAN node (including one or multiple selected RAN readers) in an inventory request message at least with information indicating the localization method at step 215. For example, an exemplary inventory request message for device localization may include information indicating the localization method, a positioning indication, device ID information, task ID information (e.g., correlation ID) and the notification method etc.
[0092] The AIoT RAN node (or the selected RAN reader (s) ) may page the AIoT device at step 216a and receive at least the device ID information via an uplink D2R signal or message at step 216b. The AIoT RAN node may determine the localization related information based on the uplink D2R signal, e.g., calculating the RSRP value based on the uplink D2R signal if RSRP based localization is used.
[0093] The AIoT RAN node may send the localization related information to the AIoTF at step 217, including the calculated RSRP value and other information including but not limited to part or all of device ID information, task ID information (e.g., correlation ID) , ID information of the AIoT RAN node (and / or selected RAN reader) , or location information of the AIoT RAN node (and / or selected reader (s) ) etc. In some cases, the localization related information may also include uplink transmission power, which denotes the power sent by the AIoT device and can be aware at the AIoT RAN node, e.g., via device notification, or via local configuration etc. Other assistance information for device localization may also be included in the localization related information to the AIoTF for determining the device location, e.g., path loss model and / or antenna gains etc.
[0094] When a localization command is used based on inventory results, it is similar to an inventory based localization procedure as illustrated above, mainly differing in the messages carrying the localization related request and localization related information are different. For example, the localization related request is carried in a command request message rather than an inventory request message to the AIoT RAN node at step 215, and sent to the AIoT device at step 216a. Although the localization command is associated with a localization method, the information indicating the localization command may be included in the command request message or not. The uplink D2R message to the AIoT RAN node at step 216b is a command related response rather than an inventory response, and the localization related information is sent to the AIoTF as a command related report at step 217.
[0095] For a device localization procedure initiated based on the local configuration and device related data and / or AF related data, the inventory based localization procedure or localization command service procedure is also applicable, and will not repeat.
[0096] In addition, in some cases, for a device localization procedure initiated during a device registration procedure, the localization related information may be obtained via another manner.
[0097] For example, besides sending the localization related request to the selected AIoT RAN node (and / or associated RAN reader (s) ) as illustrated at step 215, the AIoTF may also include the localization related request to the AIoT device in the registration response message at step 204, e.g., in an AIoT non-access stratum (NAS) message, including the information indicating the localization method and / or the positioning indication etc. Based on the localization related request, the AIoT device may send an uplink D2R message including the device ID information to the AIoT RAN node or associated RAN reader (s) at step 216b. Accordingly, the AIoT RAN node or associated RAN reader (s) may determine the localization related information based on the uplink D2R message, and transmit the localization related information to the AIoTF as illustrated at step 217.
[0098] In accordance with some aspects of the present disclosure, it is assumed that the AIoTF determines to use multiple AIoT RAN nodes for localizing the AIoT device, that is, multi-RAN based localization is used.
[0099] In some implementations of the present disclosure, the AIoTF may select or determine all the multiple AIoT RAN nodes (and / or the associated RAN readers) for localizing the AIoT device, and transmit localization related request to each selected AIoT RAN node (and / or the associated RAN readers) , which is the same as or similar to that illustrated in view of single-AIoT RAN localization and will not repeat. Observing configuration parameters may be provided by the AIoTF to each selected AIoT RAN node to synchronize the uplink measurement of RSRP among the multiple AIoT RAN nodes, which at least includes time and frequency domain resource parameters (or information parameters) . In some case, the AIoTF may firstly retrieve the radio configuration capability from each RAN node and generate the observing configuration parameters based on the retrieved radio configuration capabilities. In some cases, the observing configuration parameters may be retrieved by the LMF from the AIoT RAN nodes and send to the AIoTF, e.g., in response to the AIoTF request to LMF. In some cases, the observing configuration parameters may be determined by the AIoTF based on the local configuration, generated by operations administration and maintenance (OAM) and be locally aware at the AIoTF, or be based on the AF request that further includes, e.g., the positioning time window.
[0100] In some implementations of the present disclosure, it is assumed that only the serving AIoT RAN node of the AIoT device will send the inventory or command request message with the localization related request towards the AIoT device, while the other AIoT RAN node (s) (referred to as measurement AIoT RAN node (s) ) used for the device localization will perform localization related measurements and determine the localization related information accordingly, e.g., only monitoring and receiving the uplink D2R message from the AIoT device under the observing configuration parameters received from the AIoTF or serving AIoT RAN node.
[0101] For example, it is assumed that node#1 is the serving AIoT RAN node of the AIoT device. Compared with the case that only node#1 is selected for single-RAN localization, the localization related request towards the selected serving AIoT RAN node at step 215 may further include observing configuration parameters, e.g., observing time window and frequency band settings to synchronize uplink signal measurements performed by multiple AIoT RAN nodes selected for localizing the AIoT device.
[0102] In some cases, the AIoTF may select all AIoT RAN nodes for the device localization and provide the ID information of the other selected AIoT RAN nodes (measurement AIoT RAN nodes) with the localization related request. In some cases, the AIoTF may only decide to use multi-RAN based localization and select the serving AIoT RAN node. It is assumed that the serving AIoT RAN node is pre-configured with other RAN’s location and information. The AIoTF may request the serving AIoT RAN node to select the measurement AIoT RAN nodes (and corresponding RAN reader (s) ) , e.g., by sending a coordination indication indicating the serving AIoT RAN node to select other AIoT RAN nodes for localizing the AIoT device with the localization related request.
[0103] The serving AIoT RAN node may send a message carrying the localization related request to each measurement AIoT RAN node at step 219, e.g., via Xn interface, including but not limited to part or all of: ID information of the AIoT device; task ID information (e.g., correlation ID) ; a positioning indication; a notification method; information indicating the localization method; observing configuration parameters to synchronize uplink signal measurements among the multiple AIoT RAN nodes for localizing the AIoT device; and ID information of the AIoTF (e.g., AIoTF#1) . Herein, only node#2 (or reader#2) is shown as an example of a selected measurement AIoT RAN node.
[0104] When the AIoT device transmits the uplink D2R message in response to the received localization related request (e.g., carried in an inventory request message or command request message from the serving AIoT RAN node at step 216a, or in a device registration response message from the AIoTF at step 204 etc. ) , all the AIoT RAN nodes selected for the device localization may receive the uplink D2R message from the AIoT device. For example, node#2 or reader#2 may receive the uplink D2R message at step 216c. Similarly, each AIoT RAN node may determine the localization related information based on the uplink D2R message, e.g., measuring the RSRP value of the uplink D2R message and even the uplink transmission power.
[0105] In some cases, the measurement AIoT RAN nodes have the AIoTF ID information, e.g., provided at step 219. Each measurement AIoT RAN node may send the localization related information to the AIoTF directly, e.g., as shown at step 221a, which is the same as or similar to that illustrated in view of single-RAN based localization and will not repeat.
[0106] In some cases, the measurement AIoT RAN nodes do not have the AIoTF ID information. Each measurement AIoT RAN node may send the localization related information to the serving AIoT RAN node, e.g., at step 221b, and the serving AIoT RAN node may forward these messages carrying the localization related information to the AIoTF at step 221c.
[0107] At the AIoTF side, based on the localization related information from a single AIoT RAN node (e.g., single-RAN based localization) or multiple AIoT RAN nodes (e.g., multi-RAN based localization) , the AIoTF may determine the location of the AIoT device by itself at step 223a. In some cases, the uplink transmission power value may not be needed at the AIoTF, and the AIoTF may be locally pre-configured with a database that has the corresponding device location and the RSRP value mapping. For example, if fingerprint-based algorithm is adopted for calculating the device location, uplink transmission power value will not be needed and the AIoTF may determine the device location based on the mapping or association between device location and RSRP value.
[0108] In some cases, the AIoTF may not be capable of calculating location of the AIoT device with a specific localization method (e.g., RSRP based localization method or other localization method with higher granularity) . The AIoTF, e.g., AIoTF#1 may transmit the localization related information to another CN entity that is capable of calculate or determine the location of the AIoT device at step 223b, and request the another CN entity to determine the location of the AIoT device. The CN entity that is capable of determining the device location may calculate the device location and transmit the device location to the AIoTF at step 223c. An example of such a CN entity may be an LMF or another AIoTF that is capable of determining the device location, e.g., AIoTF#2, which may be selected and provided by the NEF when transferring the AF request message to the serving AIoTF as illustrated above.
[0109] For example, if the AIoTF decides to invoke LMF services to determine the AIoT device location, the AIoTF may select the LMF based on the local configuration, or from the NRF and / or AMF based on at least one of the target area, the support of localization method (e.g., support RSRP based localization and / or other localization method with higher granularity) , RAN reader location information, or AIoT RAN node location information. The AIoTF may transmit the localization related information to the selected LMF, e.g., by sending positioning result determination request to the LMF at step 223b, including the device ID, RSRP values associated with the AIoT device in view of the corresponding AIoT RAN node location information and / or RAN reader location information, uplink transmission power, and / or task ID information (e.g., correlation ID) etc. The LMF may calculate the location of the AIoT device as requested and send the calculated AIoT device location to the AIoTF at step 223c.
[0110] The AIoTF may store the location of the AIoT device at step 225, e.g., locally as device context, or at ADM, together with the associated AIoT RAN node and / or RAN reader information, and time stamp etc.
[0111] The AIoTF may also determine whether to report or notify the device location to the AF based on the notification method (e.g., the periodicity, the moving threshold, the changing reader etc. ) , and send the positioning report to the AF at step 227 according to the notification method, e.g., including the device ID, device location, time stamp and task ID information (e.g., transaction ID) etc.
[0112] Figure 3 illustrates an example of a CN entity 300 in accordance with aspects of the present disclosure. The CN entity 300 may include a processor 302, a memory 304, a controller 306, and a transceiver 308. The processor 302, the memory 304, the controller 306, or the transceiver 308, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0113] The processor 302, the memory 304, the controller 306, or the transceiver 308, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0114] The processor 302 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof) . In some implementations, the processor 302 may be configured to operate the memory 304. In some other implementations, the memory 304 may be integrated into the processor 302. The processor 302 may be configured to execute computer-readable instructions stored in the memory 304 to cause the CN entity 300 to perform various functions of the present disclosure.
[0115] The memory 304 may include volatile or non-volatile memory. The memory 304 may store computer-readable, computer-executable code including instructions when executed by the processor 302 cause the CN entity 300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 304 or another type of memory. 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.
[0116] In some implementations, the processor 302 and the memory 304 coupled with the processor 302 may be configured to cause the CN entity 300 to perform one or more of the functions described herein (e.g., executing, by the processor 302, instructions stored in the memory 304) . For example, the processor 302 may support wireless communication at the CN entity 300 in accordance with examples as disclosed herein. The CN entity 300 may be configured to support a means for determining, a localization method used for a device localization procedure initiated at least for an AIoT device, based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF or a local configuration of the CN entity; means for transmitting, to one or multiple AIoT RAN nodes, a localization related request associated with the localization method; and means for receiving, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.
[0117] The controller 306 may manage input and output signals for the CN entity 300. The controller 306 may also manage peripherals not integrated into the CN entity 300. In some implementations, the controller 306 may utilize an operating system such as or other operating systems. In some implementations, the controller 306 may be implemented as part of the processor 302.
[0118] In some implementations, the CN entity 300 may include at least one transceiver 308. In some other implementations, the CN entity 300 may have more than one transceiver 308. The transceiver 308 may represent a wireless transceiver. The transceiver 308 may include one or more receiver chains 310, one or more transmitter chains 312, or a combination thereof.
[0119] A receiver chain 310 may be configured to receive signals (e.g., control information, data and packets) over a wireless medium. For example, the receiver chain 310 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 310 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receiver chain 310 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 receiver chain 310 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.
[0120] A transmitter chain 312 may be configured to generate and transmit signals (e.g., control information, data and packets) . The transmitter chain 312 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 transmitter chain 312 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 transmitter chain 312 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0121] Figure 4 illustrates an example of a processor 400 in accordance with aspects of the present disclosure. The processor 400 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 400 may include a controller 402 configured to perform various operations in accordance with examples as described herein. The processor 400 may optionally include at least one memory 404, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 400 may optionally include one or more arithmetic-logic units (ALUs) 406. 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) .
[0122] The processor 400 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 400) 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.
[0123] The controller 402 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 400 to cause the processor 400 to support various operations in accordance with examples as described herein. For example, the controller 402 may operate as a control unit of the processor 400, generating control signals that manage the operation of various components of the processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0124] The controller 402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 404 and determine subsequent instruction (s) to be executed to cause the processor 400 to support various operations in accordance with examples as described herein. The controller 402 may be configured to track memory address of instructions associated with the memory 404. The controller 402 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 402 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 400 to cause the processor 400 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 402 may be configured to manage flow of data within the processor 400. The controller 402 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 400.
[0125] The memory 404 may include one or more caches (e.g., memory local to or included in the processor 400 or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. ) . In some implementations, the memory 404 may reside within or on a processor chipset (e.g., local to the processor 400) . In some other implementations, the memory 404 may reside external to the processor chipset (e.g., remote to the processor 400) .
[0126] The memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 400, cause the processor 400 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 402 and / or the processor 400 may be configured to execute computer-readable instructions stored in the memory 404 to cause the processor 400 to perform various functions. For example, the processor 400 and / or the controller 402 may be coupled with or to the memory 404, the processor 400, the controller 402, and the memory 404 may be configured to perform various functions described herein. In some examples, the processor 400 may include multiple processors and the memory 404 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.
[0127] The one or more ALUs 406 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 406 may reside within or on a processor chipset (e.g., the processor 400) . In some other implementations, the one or more ALUs 406 may reside external to the processor chipset (e.g., the processor 400) . One or more ALUs 406 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 406 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 406 may 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 406 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.
[0128] The processor 400 may support wireless communication in accordance with examples as disclosed herein. The processor 400 may be configured to or operable to support a means for determining, a localization method used for a device localization procedure initiated at least for an AIoT device, based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF or a local configuration of the CN entity; means for transmitting, to one or multiple AIoT RAN nodes, a localization related request associated with the localization method; and means for receiving, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.
[0129] Figure 5 illustrates an example of an AIoT RAN node 500 in accordance with aspects of the present disclosure. The AIoT RAN node 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0130] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0131] The processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof) . In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the AIoT RAN node 500 to perform various functions of the present disclosure.
[0132] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the AIoT RAN node 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 504 or another type of memory. 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.
[0133] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the AIoT RAN node 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504) . For example, the processor 502 may support wireless communication at the AIoT RAN node 500 in accordance with examples as disclosed herein. The AIoT RAN node 500 may be configured to support a means for receiving, a localization related request for an AIoT device from a CN entity or a serving AIoT RAN node of the AIoT device, wherein the localization related request is associated with a localization method determined based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF, or a local configuration of the CN entity; and means for transmitting, to the CN entity or the serving AIoT RAN node, localization related information associated with the AIoT device based on the localization related request.
[0134] The controller 506 may manage input and output signals for the AIoT RAN node 500. The controller 506 may also manage peripherals not integrated into the AIoT RAN node 500. In some implementations, the controller 506 may utilize an operating system such as or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.
[0135] In some implementations, the AIoT RAN node 500 may include at least one transceiver 508. In some other implementations, the AIoT RAN node 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.
[0136] A receiver chain 510 may be configured to receive signals (e.g., control information, data and packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receiver chain 510 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 receiver chain 510 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.
[0137] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data and packets) . The transmitter chain 512 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 transmitter chain 512 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 transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0138] Figure 6 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a CN entity as described herein. In some implementations, the CN entity may execute a set of instructions to control the function elements of the CN entity to perform the described functions.
[0139] At step 601, the method may include determining, a localization method used for a device localization procedure initiated at least for an AIoT device, based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF or a local configuration of the CN entity. The operations of step 601 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 601 may be performed by a CN entity as described with reference to Figure 3.
[0140] At step 603, the method may include transmitting, to one or multiple AIoT RAN nodes, a localization related request associated with the localization method. The operations of step 603 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 603 may be performed by a CN entity as described with reference to Figure 3.
[0141] At step 605, the method may include receiving, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request. The operations of step 605 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 605 may be performed by a CN entity as described with reference to Figure 3.
[0142] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0143] Figure 7 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by an AIoT RAN node (or RAN reader) as described herein. In some implementations, the AIoT RAN node may execute a set of instructions to control the function elements of the AIoT RAN node to perform the described functions.
[0144] At step 701, the method may include receiving, a localization related request for an AIoT device from a CN entity or a serving AIoT RAN node of the AIoT device, wherein the localization related request is associated with a localization method determined based on at least one of device subscription data of the AIoT device, AF subscription data of an associated AF, a message from the AF, or a local configuration of the CN entity. The operations of step 701 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 701 may be performed by an AIoT RAN node as described with reference to Figure 5.
[0145] At step 703, the method may include transmitting, to the CN entity or the serving AIoT RAN node, localization related information associated with the AIoT device based on the localization related request. The operations of step 703 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 703 may be performed by an AIoT RAN node as described with reference to Figure 5.
[0146] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0147] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A core network (CN) entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the CN entity to:determine, a localization method used for a device localization procedure initiated at least for an ambient internet of things (AIoT) device, based on at least one of device subscription data of the AIoT device, application function (AF) subscription data of an associated AF, a message from the AF or a local configuration of the CN entity;transmit, to one or multiple AIoT radio access network (RAN) nodes, a localization related request associated with the localization method; andreceive, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.2.The CN entity of claim 1, wherein the at least one processor is configured to further cause the CN entity to:determine whether to authorize the message from the AF by checking related data including at least one of the device subscription data or the AF subscription data, context of the AIoT device, or authorization data of the AF, wherein the related data includes at least one of:an allowed positioning indication;allowed localization methods for a device type, including at least one of an allowed reader identity based localization method or an allowed localization method with a granularity more finer than the reader identity based localization method;an allowed maximum number of devices to be localized;information indicating whether multiple RAN localization is allowed;an allowed maximum number of AIoT RAN nodes to be used for device localization;a mapping between device identity information and localization method; ora mapping between device type and localization method; andstore part or all of information included in the message from the AF locally or at another CN entity if the message from the AF is authorized.3.The CN entity of claim 2, wherein the message from the AF includes at least one of:identity information of the AIoT device;a positioning indication;a device type;a requested localization method;localization accuracy; ora notification method.4.The CN entity of claim 1, wherein the at least one processor is configured to further cause the CN entity to:determine to initiate the device localization procedure based on the message from the AF; ordetermine to initiate the device localization procedure based on at least one the AF subscription data, the device subscription data, authorization data of the AF, or context of the AIoT device.5.The CN entity of claim 1, wherein the at least one processor is configured to further cause the CN entity to:receive a registration request message from the AIoT device; anddetermine to initiate the device localization procedure based on related data including at least one of the device subscription data, the AF subscription data, authorization data of the AF, or context of the AIoT device and the local configuration, wherein the related data includes at least one of:an indication that localization for the AIoT device is needed;an allowed positioning indication;allowed localization methods for a device type, including at least one of an allowed reader identity based localization method or an allowed localization method with a granularity more finer than the reader identity based localization method;information indicating whether multiple RAN localization is allowed;an allowed maximum number of devices to be localized;an allowed maximum number of AIoT RANs nodes to be used for localization; ora mapping between device identity information and localization method; ora mapping between device type and localization method.6.The CN entity of claim 5, wherein the at least one processor is configured to further cause the CN entity to:transmit a registration response message to the AIoT device with a localization indication.7.The CN entity of claim 1, wherein the at least one processor is configured to further cause the CN entity to:determine whether to use one AIoT RAN node or multiple AIoT RAN nodes for localizing the AIoT device based on at least one of the message from the AF, a last known location of the AIoT device, the device subscription data, the AF subscription data, authorization data of the AF or context of the AIoT device.8.The CN entity of claim 1, wherein the localization related request is transmitted to an AIoT RAN node of one or multiple RAN nodes selected for localizing the AIoT device; or transmitted to each of multiple AIoT RAN nodes selected for localizing the AIoT device.9.The CN entity of claim 1, wherein the localization related request to a serving AIoT RAN node selected for localizing the AIoT device includes at least one of:identity information of the AIoT device;task identity information;a positioning indication;identity information of other AIoT RAN nodes of multiple AIoT RAN nodes selected for localizing the AIoT device;a notification method;a coordination indication indicating the serving AIoT RAN node to select other AIoT RAN nodes for localizing the AIoT device;information indicating the localization method; orobserving configuration parameters to synchronize uplink signal measurements performed by multiple AIoT RAN nodes selected for localizing the AIoT device, including at least time and frequency information parameters.10.The CN entity of claim 1, wherein the localization related request is carried in an inventory request message with information indicating the localization method, or a localization command request message with or without information indicating the localization method.11.The CN entity of claim 1, wherein the at least one processor is configured to:determine a location of the AIoT device based on the localization related information; or transmit a message with the localization related information to another CN entity to request the another CN entity to determine the location of the AIoT device; andstore the location of the AIoT device determined by the CN entity or received from the another CN entity, with associated AIoT RAN node information or AIoT reader information.12.A processor for wireless communication, comprising:at least one controller coupled with at least one memory and configured to cause the processor to:determine, a localization method used for a device localization procedure initiated at least for an ambient internet of things (AIoT) device, based on at least one of device subscription data of the AIoT device, application function (AF) subscription data of an associated AF, a message from the AF or a local configuration of the CN entity;transmit, to one or multiple AIoT radio access network (RAN) nodes, a localization related request associated with the localization method; andreceive, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.13.An ambient internet of things (AIoT) radio access network (RAN) node for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the AIoT RAN node to:receive, a localization related request for an AIOT device from a core network (CN) entity or a serving AIoT RAN node of the AIoT device, wherein the localization related request is associated with a localization method determined based on at least one of device subscription data of the AIoT device, application function (AF) subscription data of an associated AF, a message from the AF, or a local configuration of the CN entity; andtransmit, to the CN entity or the serving AIoT RAN node, localization related information associated with the AIoT device based on the localization related request.14.The AIoT RAN node of claim 13, wherein the AIoT RAN node is the serving AIoT RAN node and receives the localization related request from the CN entity, and if the localization related request includes identity information of other AIoT RAN nodes selected for localizing the AIoT device or a coordination indication indicating the serving AIoT RAN node to select other AIoT RAN nodes for localizing the AIoT device, the at least one processor is configured to further cause the AIoT RAN node to transmit the localization related request to the other AIoT RAN nodes to requesting uplink device to reader signal measurements for localizing the AIoT device.15.The AIoT RAN node of claim 14, wherein a message carrying the localization related request to the other AIoT RAN nodes includes at least one of:identity information of the AIoT device;task identity information;a positioning indication;a notification method;information indicating the localization method;observing configuration parameters to synchronize uplink signal measurements among the multiple AIoT RAN nodes for localizing the AIoT device, including at least the time and frequency information parameters; oridentity information of the CN entity.16.The AIoT RAN node of claim 14, wherein the at least one processor is configured to further cause the AIoT RAN node to:receive the localization related information from the other AIoT RAN nodes; andtransmit received localization related information to the CN entity.17.The AIoT RAN node of claim 13, wherein the AIoT RAN node is an AIoT RAN node of multiple AIoT RAN nodes selected for localizing the AIoT device, and the localization related information is transmitted to the CN entity if receiving the localization related request from the CN entity or from the serving AIoT RAN node with identity information of the CN entity, or to the serving AIoT RAN node if receiving the localization related request from the serving AIoT RAN node.18.The AIoT RAN node of claim 13, wherein the localization related information includes at least one of:identity information of the AIoT device;task identity information;identity information of corresponding AIoT RAN node;identity information of corresponding RAN reader;location information of the corresponding AIoT RAN node;location information of the corresponding RAN reader;a measured uplink device to reader signal strength value; oruplink transmission power of the AIoT device.19.The AIoT RAN node of claim 18, wherein the measured uplink device to reader signal strength value is a reference signal receiving power (RSRP) value associated with the AIoT device.20.A method performed by a core network (CN) entity, comprising:determining, a localization method used for a device localization procedure initiated at least for an ambient internet of things (AIoT) device, based on at least one of device subscription data of the AIoT device, application function (AF) subscription data of an associated AF, a message from the AF or a local configuration of the CN entity;transmitting, to one or multiple AIoT radio access network (RAN) nodes, a localization related request associated with the localization method; andreceiving, from the one or multiple AIoT RAN nodes, localization related information associated with the AIoT device in response to the localization related request.
