Method of acquiring data and location of ambient IoT devices

Abstract

Requesting data from ambient Internet of Things (AIoT) devices. At steps 302-304, an application function (AF) transmits an AIoT read message to a 5G core and at step 305 a gNB selects the appropriate

Description

FIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, to a method of acquiring data and location of ambient Internet of things (loT) devices. BACKGROUND

[0002] Ambient Internet of things (loT) may refer to loT devices powered by energy harvesting, making them either battery-less or equipped with limited energy storage capabilities (e.g., using a capacitor). Ambient loT may be utilized to complement existing loT technologies (e.g, narrowband loT / enhanced machine type communication (NB-IoT / eMTC) and / or new radio reduced capability (NR RedCap)) described, for example in the third generation partnership project (3GPP) specifications. Ambient loT may, for example, cover use cases that demand more cost-effective, power-efficient, and particularly battery-less functionalities. SUMMARY

[0003] In an aspect of the present disclosure, a method includes receiving, by a user equipment (UE), an indication message from a first apparatus, the indication message including an indication of one or more identifiers for one or more Internet of things (loT) devices from which to expect requested data. The UE receives a first backscatter data message from a first loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the first backscatter data message including the requested data from the first loT device, and transmits a forward message to the first apparatus, the forward message including the requested data.

[0004] In an aspect of the method, the report message is transmitted upon an expiration of a timer.

[0005] In an aspect of the method, the method further includes receiving, by the UE, a second backscatter data message from a second loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the second backscatter data message including the requested data from the second loT device.

[0006] In an aspect of the method, the requested data includes location data of the one or more loT devices.

[0007] In an aspect of the method, the requested data includes data stored in the one or more loT devices.

[0008] In an aspect of the method, the first apparatus is a gNodeB.

[0009] In an aspect of the method, the one or more loT devices are backscattering ambient loT devices.

[0010] In an aspect of the method, at least one backscattering ambient loT device of the backscattering ambient loT devices does not store energy.

[0011] In an aspect of the method, the at least one of the one or more backscattering ambient loT devices is a passive or semi-passive ambient loT device.

[0012] In an aspect of the method, the method further includes receiving, by the UE, an activating request from the first apparatus, the activating request including one or more identifiers of the one or more loT devices from which to request data, a requested data, and a request type; and transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

[0013] In an aspect of the method, the method further includes transmitting, by the UE, a report message to the first apparatus, the report message including one or more identifiers of loT devices from which expected requested data was not received.

[0014] In an aspect of the present disclosure, a method includes receiving, by a user equipment (UE), an activating request from a first apparatus, the activating request including one or more identifiers of one or more Internet of things (loT) devices from which to request data, a requested data, and a request type; and transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

[0015] In an aspect of the method, the requested data includes location data of the one or more loT devices.

[0016] In an aspect of the method, the requested data includes data stored in the one or more loT devices.

[0017] In an aspect of the method, the first apparatus is a gNodeB.

[0018] In an aspect of the method, the one or more loT devices are backscattering ambient loT devices.

[0019] In an aspect of the method, at least one backscattering ambient loT device of the backscattering ambient loT devices does not store energy.

[0020] In an aspect of the method, at least one of the one or more backscattering ambient loT devices is a passive or semi-passive ambient loT device.

[0021] In an aspect of the present disclosure, a method includes receiving, by a first apparatus, a first message from a second apparatus, the first message including a request for data associated with one or more loT devices, a request type, and at least one of the following: one or more identifiers for the one or more Internet of things (loT) devices, or location information of each of the one or more loT devices. The first apparatus transmits a second message to at least one third apparatus, the second message including the at least one of the one or more identifiers for the one or more loT devices, the request for data associated with the one or more loT devices, the location information of each of the one or more loT devices, or the request type. The first apparatus receives a forward report message from the at least one third apparatus, the forward report message including at least one identifier from a first loT device of the one or more loT devices, data associated with the first loT device and the request for data, and location information of the first loT device, stores the location information of the first IOT device of the one or more loT devices in association with the at least one identifier of the first loT device of the one or more loT devices, and transmits a notification message to the second apparatus, the notification message including at least one of the at least one identifier from the first loT device of the one or more loT devices, the data associated with the first loT device and the request for data, and the location information of the first loT device.

[0022] In an aspect of the method, the location information of an loT device of the one or more loT devices corresponds to a respective set of individual candidate locations, wherein individual candidate locations of the respective set of individual candidate locations are associated with a priority order.

[0023] In an aspect of the method, an individual candidate location of the set of individual candidate locations corresponds to one of the following: a 3GPP defined location; or an identifier of a user equipment that is assumed to be proximate the loT device.

[0024] In an aspect of the method, the method further includes receiving an indication of a mobility management function to use to contact a user equipment that is assumed to be proximate an loT device of the one or more loT devices.

[0025] In an aspect of the method, the request corresponds to at least one of the following: a request to read data from the one or more loT devices, a request to write data to the one or more loT devices, or a request to locate the one or more loT devices.

[0026] In an aspect of the method, the method further includes determining the at least one third apparatus to which to transmit the request for data associated with the one or more loT devices.

[0027] In an aspect of the method, the first apparatus is an ambient Internet of things function (AIoTF).

[0028] In an aspect of the method, the requested data includes data stored in the one or more devices.

[0029] In an aspect of the present disclosure, a user equipment includes at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the user equipment at least to perform any of the foregoing methods.

[0030] In an aspect of the present disclosure, an apparatus includes at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to perform any of the foregoing methods.

[0031] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0032] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Some example embodiments will now be described with reference to the accompanying drawings.

[0034] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system, a user equipment (UE) and one or more devices, according to one illustrated aspect of the disclosure;

[0035] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0036] FIG. 3 is a diagram of an example embodiment of signals and operations among one or more devices, a UE, a gNB, a 5G core, and an AF, according to one illustrated aspect of the disclosure;

[0037] FIG. 4 is a diagram of an example embodiment of signals and operations among one or more gNBs, one or more AMFs, a UDR, an AIoTF, a UDM, an NEF, and an AF, according to one illustrated aspect of the disclosure; and

[0038] FIG. 5 is a diagram of an example embodiment of components of a UE or of a network apparatus, according to one illustrated aspect of the present disclosure. DETAILED DESCRIPTION

[0039] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0040] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described m connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined m any suitable manner in one or more aspects.

[0041] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0042] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0043] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0044] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5G NR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0045] FIG. 1 also shows one or more devices 160 (e.g., 160a / DEVl and 160b / DEV2) that the UE 150 may be in communication with. In various embodiments, the UE 150 and devices 160 may implement and be connected via a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.15 radio technology. However, one skilled in the art will understand that the devices 160 and UE 150 may be connected by other technologies.

[0046] In various embodiments, the devices 160 may include ambient Internet of things (loT) devices, such as identifier / identity ID tags, sensors (e.g., temperature, humidity, etc.), healthcare devices (e.g., for monitoring personal medical information), and / or logistics tracking devices (e.g. for tracking objects). One skilled in the art will understand and appreciate additional example ambient loT devices the devices 160 may include.

[0047] The following description provides further details of examples of network nodes. In a 5GNR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0048] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer. Layer 2 (L2), and Layer 3 (L3).

[0049] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.: o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0050] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 VI6.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0051] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), sendee data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0052] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0053] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 5 below.

[0054] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0055] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0056] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 4. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0057] With continuing reference to FIG. 1, m the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0058] FIG. 1 provides an example and is merely illustrative of a network system 100, devices 160 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. I and will understand that other user equipment may be in communication with the network system 100.

[0059] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0060] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a sendee “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0061] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SAIF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0062] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223. In various embodiments, the core network 210 may includes an ambient Internet of things function (AIOTF), which may be collocated with the NEF 215 or separate from it. The AIOTF provides communication and control functions for ambient loT devices.

[0063] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data, being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0064] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data, unit (PDU) session management, as well as manages session context with the UPF 226.

[0065] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0066] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0067] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The OAM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0068] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0069] Although further detail will be provided below, as mentioned above, ambient loT devices may be powered by energy harvesting, making them either battery-less or equipped with limited energy storage capabilities (e.g., using a capacitor). Ambient loT may be utilized to complement existing loT technologies (e.g, narrowband loT / enhanced machine type communication (NB-IoT / eMTC) and / or new radio reduced capability (NR RedCap)) described, for example in the third generation partnership project (3GPP) specifications. Ambient loT may, for example, cover use cases that demand more cost-effective, power-efficient, and particularly battery-less functionalities.

[0070] As mentioned above, ambient loT devices may include devices such as identifier / identity ID tags, sensors (e.g., temperature, humidity, etc ), healthcare devices (e.g., for monitoring personal medical information), and / or logistics tracking devices (e.g. fortracking objects).

[0071] In order to retrieve data from ambient loT (AIoT) devices, an activator and / or reader may be utilized. In various embodiments, an activator (or illuminator) may include a device that sends an activation signal for backscattering. In various embodiments, a reader (or receiver) may include a device that listens and detects the backscattered signals. The reader may or may not be collocated with the activator (e.g., within the same UE).

[0072] In various embodiments, AIoT devices may be categorized into different categories. For example, passive devices may include pure battery-less devices with no energy storage capability at all, that are incapable of independent signal generation / amplification (e.g., only capable of backscattering). Passive devices may rely completely on the availability of an external source of energy.

[0073] Semi-passive devices, for example, may include AIoT devices with limited energy storage capability' that do not require manual replacement or recharging. They do not generate independent signals but may utilize backscattering with potential reflection gain.

[0074] Active devices, for example, may include AIoT devices actively transmitting with limited energy storage capabilities based on ambient energy sources.

[0075] In various embodiments, AIoT devices may engage in varying operating scenarios. For example, AIoT devices may exhibit varying communication patterns depending on the available power for communication, such as harvesting capabilities, the presence of storage capacity, or specific use cases. In some embodiments, AIoT devices may have continuous or at least significant power availability. This can be achieved through continuous energy harvesting or a combination of continuous harvesting with limited energy storage (e.g., capacitor) to overcome momentary variations in harvested power. In this operating scenario (e.g., normal operation), the processor and communication module in the AIoT device can remain continuously active. The device's communication module can periodically listen to the network to check for mobile-terminated traffic (e.g., triggering messages) and transmit relevant data when necessary.

[0076] In some embodiments, AIoT devices may have intermittent energy availability. For example, an AIoT device may only be active for short periods. Due to limited energy, the AIoT device may be unable to listen to the network for mobile-terminated traffic over extended durations, which can impact service aspects like provisioning.

[0077] In some embodiments, the 5G network may trigger the AIoT device to communicate in a relevant manner. Here, the network may be responsible for initiating communication, and the device itself may not be able to determine when to communicate. In various embodiments, upon the network waking up the AIoT device, it can be accompanied by a trigger to perform a specific action (e.g., take measurements) or initiate communication (e.g., send an identifier). The waking-up process may also involve the AIoT device starting to listen to the network for further instructions.

[0078] Although further detail is provided below, briefly, in various embodiments, described herein is a method of acquiring data and location of AIoT devices. In various embodiments, a UE (e.g., UE 150) may include an activator and / or reader that transmits a message to an AIoT device (e.g., devices 160) to query the device for data and receive the data, for example, via backscattering, which in various embodiments includes reflecting transmitted signals back in the direction they were received. Persons of skill in the art will appreciate and understand various examples of backscattering and other example methods for transmitting information.

[0079] As used herein, a communication with a radio access network (RAN) may refer to and mean a communication with a portion of a RAN, such as with a network node (e g., a DU and / or a CU), or another portion of a RAN. As used herein, a communication with a core network may refer to and mean a communication with one or more services / applications of the core network, such as AMF or another service of a core network.

[0080] As used herein, the terms “first” and “second”, or the like, may refer to a first or second instance of a message being transmitted / received by a component (e.g., UE, apparatus, etc.), or a first or second component in a sequence of described components. As such, the terms are used in a non-limiting manner, and can refer to any message, operation, device, component, or the like.

[0081] In accordance with the brief description, FIG. 3 is a diagram of an example embodiment of signals and operations among one or more devices, a UE, a gNB, a 5G core, and an AF, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 3 may correspond to similar components described above in FIGS. 1 and 2. The following paragraphs will describe various signals and operations. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0082] At operation 300, the AF may be configured with information relating to the identities / identifiers (IDs) of activators and readers, as well as locations of target AIoT devices from which the AF may desire to acquire data. For example, in various embodiments, passive types of AIoT devices, may not include subscriber identity module (SIM) cards that allow the AIoT devices to register with, for example, a 5G network. Accordingly, in various embodiments, such AIoT devices are prevented from being registered with the 5G core (5GC), and the 5GC cannot identify these AIoT devices or retrieve their location information. At operation 300, it is assumed that the AF requesting the 5GC to read data, from or get location information of specific AIoT devices possesses their device IDs, (e.g., defined by the device manufacturer or the AF itself), along with candidate / target locations of the AIoT devices or information (e.g., external ID) of the activator and reader (e.g., UE) m communication with the target AIoT devices.

[0083] At operation 301a, the reader (RD) registers with the 5GC and at operation 301b, the activator registers with the 5GC. In various embodiments, the activator and the reader may include UEs with the capability to send activating signals to AIoT devices and receive backscattered signals from the AIoT devices, respectively. Both the activator and the reader register to the 5GC. The UE (or UEs) may indicate support of the capability to act as an AIoT device activator or reader.

[0084] At operation 302, the AF transmits an AIoT read message to the 5GC (e.g., the NEF), and the 5GC receives the AIoT read message. In various embodiments, an application protocol interface ( API ) referred to as AIoT_Read may be utilized to activate the target AIoT devices for the purpose of data reading and / or location determination. In various embodiments, the AF’s request may include one or more of the following example parameters: target AIoT device IDs, a request type indicating the request is for reading data, location retrieval or both, candidate locations denoting possible locations of the target AIoT devices, external IDs of the activator and the reader, which are supposed to accompany the target AIoT devices, or requested target data in case the Request type is for reading data indicating the target data the AF intends to retrieve.

[0085] Although additional detail may be provided below with respect to FIG. 4, at operation 303, upon receiving the AIoT read message, the 5GC authorizes the AF, the activator and reader (if applicable), and finds the serving AMF(s) and gNB(s) by leveraging the provided location information or the information of the activator and reader, for example.

[0086] At operation 305, the gNB selects the activator and reader capable of direct communication with the target AIoT devices. In various embodiments, this selection maybe determined by internal logic in the gNB. During this decision-making process, the gNB may consider the information about the activator and reader provided by the 5GC, When the activator and the reader are not served by the same gNB, the 5GC instead of the gNB may select the activator and the reader.

[0087] At operation 306, the gNB transmits a message including the expected AIoT devices to be read to the reader UE and the reader UE receives the message including the expected AIoT devices to be read. In various embodiments, the message including the expected AIoT devices to be read includes target AIoT devices that are expected to respond to an activating signal / message.

[0088] At operation 307, the gNB transmits an activating request message to the activator UE and the activator UE receives the activating request message. In various embodiments, the activating request message includes the target AIoT devices to wake up, the request type if the request is for data reading, and the requested target data, for example.

[0089] Upon receiving the activating request message, at operation 308, the activator UE transmits an activating signal / message to an AIoT device (e.g., a target AIoT device). In various embodiments, at operation 308, the activating message may be tn the form of a broadcast message that includes, for example, one or more of the following: the target AIoT device IDs, the request type, or the requested target data. For example, as depicted in FIG. 3, at operation 308a, the activator UE transmits an activating signal / message to an AIoT device DEV2, and at operation 308b, activator UE transmits an activating signal / message to an AIoT device DEVI.

[0090] At operation 309, AIoT devices that receive the activating message from the activator UE, compare the target AIoT device ID to their ID to determine if there is a match. As described below, if there is no match, the AIoT device takes no action, and if there is a match, the AIoT device takes action.

[0091] For example, at operation 309a, the AIoT device DEV2 determines that the target AIoT device ID does not match its own. Accordingly, the AIoT device DEV2 does not react (e.g., takes no action).

[0092] At operation 309b, for example, the AIoT device DEVI determines that the target AIoT device ID marches its own. Accordingly, at operation 309b, the AIoT device DEV 1 transmits a backscattering message to the reader UE and the reader UE receives the backscattering message. In various embodiments, the backscattering message may include information based upon the activating message received from the activator UE. For example, the AIoT device DEV 1 checks the request type, if any, included in the activating message. If there is no request type included in the activating message, the AIoT device DEVI transmits a backscattering message containing solely its device ID to the reader UE. If the activating message does include a request type that is set for either data or both data and location, the AIoT device DEVI checks the presence of requested target data within the activating message. If it is absent, the AIoT device DEVI sends a backscattering message incorporating its device ID alongside all available data. If the requested target data is present, the AIoT device DEVI sends a backscattering message including its device ID and only the data requested to the reader UE.

[0093] Upon receipt of the backscattering message, at operation 310, the reader UE transmits a message forwarding the received information in the backscattering message to the gNB and the gNB receives the message including the forwarded information. In various embodiments, the reader UE monitors a channel through which AloT devices transmit their messages. If the AloT device ID within the received message corresponds to any of the target AloT device IDs received at operation 306, the reader UE assesses which AloT devices, from the list of expected AloT devices, have provided a response. The reader UE forwards this information, encompassing AloT device data (if applicable) and the AloT device ID, to the gNB.

[0094] At operation 311, the gNB transmits a report message to the 5GC and the 5GC (e.g., the AMF) receives the report message. In various embodiments, the report message includes the AloT device ID that has responded, alongside its associated data if the requested type was for data reading or both data reading and location determination. If the request type was for both or location determination, the gNB also includes the location information of the activator UE and the reader UE in the report message. In various embodiments, depending on its local configuration, the gNB transmits the report message to the 5GC either for each ind ividual AloT device or as a group, encompassing a collection of the target AloT devices.

[0095] At operation 312, the 5GC transmits a notification message to the AF and the AE receives the notification message. In various embodiments, the notification message includes the AloT devices from the list of target AloT devices that have responded, providing the associated data if it was requested. The notification also includes the location information of the activator UE and the reader UE that communicated with each AloT device. In various embodiments, the AF utilizes the location information of the activator UE and the reader UE to approximate the positions of the targeted AloT devices. In various embodiments, the separation between the AloT devices and the activator / reader UEs to be able to directly communicate may include an approximate range of 100 meters.

[0096] At operation 313, the reader UE waits for the expected AloT devices to reply until the expiration of a predefined tinier. If some of the expected AloT devices do not reply before the timer ends, they are considered missing. Accordingly, at operation 314a the reader UE transmits a report message to the gNB and the gNB receives the report message. The report message includes the device IDs of target AIoT devices that did not respond to the activating message. At operation 314b, the gNB forwards the report message to the 5GC and the 5GC receives the forwarded report message. At operation 314c, the 5GC transmits a notification message to the AF of the target AIoT devices that did not respond to the activating message and the AF receives the notification message.

[0097] At operation 315, the 5GC stores the most recent location of each AIoT device for tracking and improving signaling efficiency. In various embodiments, the 5GC might begin searching for the AIoT devices starting from their last known locations in future instances.

[0098] At operation 316, the 5GC tracks the AIoT devices to determine whether they remain in the last known location or have moved to a different place outside of the candidate locations. In various embodiments, the 5GC verifies if any missing devices have been newly discovered. At operation 317, the 5GC transmits a notification message to the AF the includes information relating to changes in location, and the AF receives the notification message.

[0099] The operations of FIG. 3 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated m FIG. 3. In embodiments, the operations may not include every operation illustrated in FIG. 3. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 3. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in the diagram shown in FIG. 3.

[00100] In accordance with the brief description, FIG. 4 is a diagram of an example embodiment of signals and operations among one or more gNBs, one or more AMFs, a UDR, an AIOTF, a UDM, an NEF, and an AF, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 4 may correspond to similar components described above in FIGS. 1 and 2. The following paragraphs will describe various signals and operations. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[00101] At operation 401, the AF transmits an AloT read request message to the NEF and the NEF receives the AloT read request message. In various embodiments, the AloT read request message may utilize the API referred to as AIoT_Read to activate the target AloT devices for the purpose of data reading and / or location determination. In various embodiments, the AF’s read request message may include one or more of the following parameters: the target AloT device IDs, candidate locations denoting possible locations of the target AloT devices, the request type indicating the request is for reading data, location retrieval or both, external IDs of the activator UE and the reader UE, which may be m communication with the target AloT devices, or the requested target data in case the request type is for reading data indicating the target data the AF intends to retrieve. In other words, the request may correspond to at least one of the following: a request to read data from the one or more loT devices, a request to write data to the one or more loT devices, or a request to locate the one or more loT devices.

[00102] In various embodiments, the AF may provide an activator UE and the reader UE (e.g. in the case where the AloT Device may be m a vessel / truck with a known inbound activator / reader UE). In various embodiments, the target AloT device may be in a warehouse / shop with a known inbound activator / reader LIE.

[00103] At operation 402, the NEF authorizes the request received from the AF at operation 401. In various embodiments the NEF bases the authorization on a service level agreement (SLA).

[00104] In various embodiments, at operation 403, the NEF may translate the generic public subscription identifiers (GPSIs) of the activator UE and the reader UE, if provided, to the subscription permanent identifiers (SUPIs) via. the UDM. In various embodiments, the NEF translates the location provided by the AF into 3GPP based location information (e.g., tracking areas TA(s), cell ID(s), etc.).

[00105] In various embodiments, at operation 405, the NEF identifies the serving AMF(s) via the UDM by utilizing the SUPIs of the activator and reader UEs, if applicable, by considering the candidate locations or by retrieving the last known location of the AloT device(s) from a central database (e.g., as stored as part of a previous context with the AIoT device). For a given AIoT device, the NEF may provide multiple candidate locations, with a priority of one location over another. For example, the location information of an loT device of the one or more loT devices may correspond to a respective set of individual candidate locations (wherein individual candidate locations of the respective set of individual candidate locations may be associated with a priority order). An individual candidate location of the set of individual candidate locations may correspond to one of the following: a 3GPP defined location (e.g., geographical information); or an identifier of a user equipment that is assumed to be proximate the loT device. For example, the NEF may receive an indication of a mobility management function to use to contact a user equipment that is assumed to be proximate an loT device(s) of one or more loT devices.

[00106] At operation 406, the NEF selects an AIoTF (e.g., a standalone NF or collocated with the NEF), and transmits an AIoT read (AIoT Read) request message to the AIoTF, and the AIoTF receives the AIoT Read request message. The AIoTRead request message, includes, in various embodiments, one or more of the following parameters: the target AIoT devices, the request type, candidate locations, the serving AMF(s), IDs (e.g. SUPI(s)) of both the activator UE and the reader UE, or requested target data. Accordingly, the NEF is able to determine AIoTF device to which to transmit the request for data associated with the one or more loT devices and to transmit such a request.

[00107] At operation 407, the AIoTF stores the received target / candidate locations per the AIoT device ID. In various embodiments, the locations may be stored locally or within a centralized database (e.g., via the UDR).

[00108] At operation 408, the AIoTF transmits an AIoT read request message to the AMF(s) to initiate communication and the AMF(s) receive the AIoT read request message. In various embodiments, the AIoT read request message may include one or more of the following: the target AIoT devices, the candidate locations, external IDs of both the activator UE and the reader UE, requested target data, or the request type. For a given AIoT device, the AIoTF may issue multiple simultaneous or consecutive AMF requests when it has received multiple candidate locations (with possibly a priority between these locations).

[00109] At operation 409, the AMF(s) identifies the serving gNB(s) by utilizing the SUPls of the activator UE and the reader UE, if applicable, or by considering the candidate locations.

[00110] At operation 410, the AMF(s) translates the SUPls of both the activator UE and the reader UE into the next generation application protocol (NGAP) IDs, and transmits the AIoT_Read message to the serving gNB(s), which receive the AIoT_Read message. In various embodiments, the AIoT Read message includes one or more of the following: the target AIoT devices, the NGAP IDs of both the activator UE and the reader UE, the requested target data, or the request type.

[00111] At operation 411, the gNB selects the activator UE and the reader UE capable of direct communication with the target AIoT devices. In various embodiments, this selection may be determined by use of internal logic. During this decision-making process, the gNB considers the information about the activator UE and the reader UE provided by the 5GC. If the activator UE and the reader UE are not served by the same gNB, the 5GC may select the activator UE and the reader UE.

[00112] At operation 412a, the gNB transmits a report message to the AMF(s) and the AMF(s) receive the report message. In various embodiments, the report message may include one or more of the following: the AIoT device ID that has responded, associated data if the requested type was for data reading or both data reading and location determination. In the case that the request type was for both or location determination, the gNB also includes the location information of the activator UE and the reader UE.

[00113] At operation 412b, the AMF(s) forwards the report message to the AIoTF and the AIoTF receives the forwarded report message. Upon receipt of the forwarded report message, at operation 413, the AIoTF, in various embodiments, may store the last found location for the purpose of tracking per the AIoT device ID, either locally or within a centralized data base, such as the UDR.

[00114] At operation 414a, the AIoTF transmits a notification message about the list of AIoT devices that responded to the activating command (e.g., at operation 308 in FIG. 3) to the NEF and the NEF receives the notification message. In various embodiments, the notification message may also includes the location information of the activator UE and the reader UE that communicated with each AIoT device. In various embodiments, the AF utilizes the location information of the activator UE and the reader UE to approximate the positions of the targeted AIoT devices. In various embodiments, the separation between the AIoT devices and the activator / reader UEs to be able to directly communicate may include an approximate range of 100 meters.

[00115] Upon receipt of the notification message at operation 414a, at operation 414b, the NEF forwards the notification message to the AF and the AF receives the forwarded notification message.

[00116] For example the process described in FIG. 4 may be implemented in a network deployment where there is a Service based interface between the RAN and the Core; In that case operations 401 to 407 are supported as described above but then the AIoTF directly interfaces to the RAN (e.g. gNB), for example when no target UE are identified in the request it has received at operation 406. In that case a) the AIOTF identifies the serving RAN nodes (e.g. gNB(s)) by considering the candidate locations and using possible a gNB service repository and b) operations 408 and 409 are not carried out. At operation 410’, the AIoTF (and not the AMF) transmits an AIoT read request message to the RAN (e.g. gnb). In various embodiments, the AIoT_Read message includes one or more of the following: the target AIoT devices, the requested target data, or the request type. Step 411 takes place as described above. At step 412’, the gNB transmits a report message to the AIoTF and the AIoTF receives the report message. In various embodiments, the report message may include one or more of the following: the AIoT device ID that has responded, associated data if the requested type was for data reading or both data reading and location determination. In the case that the request type was for both or location determination, the gNB also includes the location information of the activator UE and the reader UE. Then steps 413 to 414b take place as described above.

[00117] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill m the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 4.

[00118] The following describes operations from the perspective of a UE as a reader. From such a perspective, a method may include receiving, by the UE, an indication message from a first apparatus, the indication message including an indication of one or more identifiers for one or more loT devices from which to expect requested data. The UE receives a first backscatter data message from a first loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the first backscatter data message including the requested data from the first loT device, and transmits a forward message to the first apparatus, the forward message including the requested data.

[00119] The following describes operation from the perspective of a UE as an activator. From such a perspective, a method may include receiving, by the UE, an activating request from a first apparatus, the activating request including one or more identifiers of one or more loT devices from which to request data, a requested data, and a request type, and transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

[00120] The following describes operation from the perspective of a first apparatus, which in some embodiments, may include an AIoTF. From such a perspective, a method may include receiving, by the first apparatus, a first read message from a second apparatus, the first read message including one or more identifiers for one or loT devices, a request for data associated with the one or more loT devices, a location of each of the one or more loT devices, and a request type. The first apparatus stores the locations of the one or more loT devices, and transmits a second read message to a third apparatus, the second read message including the one or more identifiers for the one or more loT devices, the request for data associated with the one or more loT devices, the location of each of the one or more loT devices, and the request type. The first apparatus receives a forward report message from the third apparatus, the forward report message including at least one identifier from a first loT device of the one or more loT devices, the requested data associated with the first loT device, and the location of the first loT device, and transmits a notification message to the second apparatus, the notification message including the at least one identifier from a first loT device of the one or more loT devices, the requested data associated with the first loT device, and the location of the first loT device.

[00121] Referring now to FIG. 5, there is shown a block diagram of example components of a UE or a network apparatus (e.g., of a RAN or a core network). The apparatus includes an electronic storage 510, a processor 520, a network interface 540, and a memory 550. The various components may be communicatively coupled with each other. The processor 520 may be and may include any type of processor, such as a single-core central processing unit (CPU), a multicore CPU, a microprocessor, a digital signal processor (DSP), a System-on-Chip (SoC), or any other type of processor. The memory 550 may be a volatile type of memory, e.g., RAM, or a non-volatile type of memory, e.g., NAND flash memory. The memory 550 includes processor-readable instructions that are executable by the processor 520 to cause the apparatus to perform various operations, including those mentioned herein, such as the operations of FIGS. 3-4.

[00122] The electronic storage 510 may be and include any type of electronic storage used for storing data, such as hard disk drive, solid state drive, optical disc, and / or other non-transitory computer-readable mediums, among other types of electronic storage. The electronic storage 510 stores processor-readable instructions for causing or configured for causing the apparatus to perform its operations and also stores data associated with such operations, such as storing data relating to 5G NR standards, among other data. The network interface 540 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[00123] The components shown in FIG. 5 are merely examples, and persons skilled in the art will understand that an apparatus includes other components not illustrated and may include multiples of any of the illustrated components. Such and other embodiments are contemplated to be within the scope of the present disclosure. For example, a transmitter and a receiver may be included as components for transmitting and receiving signals.

[00124] Further embodiments of the present disclosure include the following examples.

[00125] Example 1.1. A user equipment (UE), comprising: means for receiving, by a user equipment (UE), an indication message from a first apparatus, the indication message including an indication of one or more identifiers for one or more Internet of things (loT) devices from which to expect requested data; means for receiving, by the UE, a first backscatter data message from a first loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the first backscatter data message including the requested data from the first loT device; and means for transmitting, by the UE, a forward message to the first apparatus, the forward message including the requested data.

[00126] Example 1.2. The UE of example 1.1, wherein the report message is transmitted upon an expiration of a timer.

[00127] Example 1.3. The UE of example 1.1, further comprising means for receiving, by the UE, a second backscatter data message from a second loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the second backscatter data message including the requested data from the second loT device.

[00128] Example 1.4. The UE as in any one of examples 1.1-1.3, wherein the requested data includes location data of the one or more loT devices.

[00129] Example 1.5. The UE as in any one of examples 1.1-1.4, wherein the requested data includes data stored in the one or more loT devices.

[00130] Example 1.6. The UE as in any one of examples 1.1-1.5, wherein the first apparatus is a gNodeB.

[00131] Example 1.7. The UE as in any one of examples 1.1-1.6, wherein the one or more loT devices are backscattering ambient loT devices.

[00132] Example 1.8. The UE of example 1.7, wherein at least one backscattering ambient loT device of the backscattering ambient loT devices does not store energy.

[00133] Example 1.9. The UE of example 1.7, wherein the at least one of the one or more backscattering ambient loT devices is a passive or semi-passive ambient loT device.

[00134] Example 1.10. The UE of example 1.1, further comprising: means for receiving, by the UE, an activating request from the first apparatus, the activating request including one or more identifiers of the one or more loT devices from which to request data, a requested data, and a request type; and means for transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

[00135] Examplel.il. The UE of example 1.1, further comprising means for transmitting, by the UE, a report message to the first apparatus, the report message including one or more identifiers of loT devices from which expected requested data was not received.

[00136] Example 2.1. A user equipment (UE) comprising: means for receiving an activating request from a first apparatus, the activating request including one or more identifiers of one or more Internet of things (loT) devices from which to request data, a requested data, and a request type; and means for transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type-

[00137] Example 2.2. The UE of example 2.1, wherein the requested data includes location data of the one or more loT devices.

[00138] Example 2.3. The UE as in any of examples 2.1-2.2, wherein the requested data includes data stored in the one or more loT devices.

[00139] Example 2.4. The UE as in any of examples 2.1 -2.3, wherein the first apparatus is a gNodeB.

[00140] Example 2.5. The UE as in any of examples 2.1-2.4, wherein the one or more loT devices are backscattering ambient loT devices.

[00141] Example 2.6. The UE of example 2.5, wherein at least one backscattering ambient loT device of the backscattering ambient loT devices does not store energy.

[00142] Example 2.7. The UE of example 2.5, wherein at least one of the one or more backscattering ambient loT devices is a passive or semi-passive ambient loT device.

[00143] Example 3.1. An apparatus, comprising: means for receiving, by a first apparatus, a first message from a second apparatus, the first message including a request for data associated with one or more loT devices, a request type, and at least one of the following: one or more identifiers for the one or more Internet of things (loT) devices, or location information of each of the one or more loT devices; means for transmitting, by the first apparatus, a second message to at least one third apparatus, the second message including the at least one of the one or more identifiers for the one or more loT devices, the request for data associated with the one or more loT devices, the location information of each of the one or more loT devices, or the request type; means for receiving, by the first apparatus, a forward report message from the at least one third apparatus, the forward report message including at least one identifier from a first loT device of the one or more loT devices, data associated with the first loT device and the request for data, and location information of the first loT device; means for storing, by the first apparatus, the location information of the first IOT device of the one or more loT devices in association with the at least one identifier of the first loT device of the one or more loT devices; and means for transmitting, by the first apparatus, a notification message to the second apparatus, the notification message including at least one of the at least one identifier from the first loT device of the one or more loT devices, the data associated with the first loT device and the request for data, and the location information of the first loT device.

[00144] Example 3.2. The apparatus of example 3.1, wherein the location information of an loT device of the one or more loT devices corresponds to a respective set of individual candidate locations, wherein individual candidate locations of the respective set of individual candidate locations are associated with a priority order).

[00145] Example 3.3. The apparatus of example 3.2, wherein an individual candidate location of the set of individual candidate locations corresponds to one of the following: a 3GPP defined location; or an identifier of a user equipment that is assumed to be proximate the loT device.

[00146] Example 3.4. The apparatus of example 3.1, further comprising means for receiving an indication of a mobility management function to use to contact a user equipment that is assumed to be proximate an loT device of the one or more loT devices.

[00147] Example 3.5. The apparatus of example 3.1, wherein the request corresponds to at least one of the following: a request to read data from the one or more loT devices, a request to write data to the one or more loT devices, or a request to locate the one or more loT devices.

[00148] Example 3.6. The apparatus of example 3.1, further comprising means for determining the at least one third apparatus to which to transmit the request for data associated with the one or more loT devices.

[00149] Example 3.7. The apparatus of example 3.1, wherein the first apparatus is an ambient Internet of things function (AIoTF).

[00150] Example 3.8. The apparatus as in any one of examples 3.1-3.7, wherein the requested data includes data stored in the one or more devices.

[00151] Example 4.1. A user equipment (UE) comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the user equipment at least to perform: receiving, by the UE, an indication message from a first apparatus, the indication message including an indication of one or more identifiers for one or more Internet of things (loT) devices from which to expect requested data; receiving, by the UE, a first backscatter data message from a first loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the first backscatter data message including the requested data from the first loT device; and transmitting, by the UE, a forward message to the first apparatus, the forward message including the requested data.

[00152] Example 5.1. A user equipment (UE) comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the user equipment at least to perform: receiving, by the UE, an activating request from a first apparatus, the activating request including one or more identifiers of one or more Internet of things (loT) devices from which to request data, a requested data, and a request type; and transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

[00153] Example 6.1. An apparatus comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the apparatus at least to perform: receiving, by a first apparatus, a first message from a second apparatus, the first message including a request for data associated with one or more loT devices, a request type, and at least one of the following: one or more identifiers for the one or more Internet of things (loT) devices, or location information of each of the one or more loT devices; transmitting, by the first apparatus, a second message to at least one third apparatus, the second message including the at least one of the one or more identifiers for the one or more loT devices, the request for data associated with the one or more loT devices, the location information of each of the one or more loT devices, or the request type; receiving, by the first apparatus, a forward report message from the at least one third apparatus, the forward report message including at least one identifier from a first loT device of the one or more loT devices, data associated with the first loT device and the request for data, and location information of the first loT device; storing, by the first apparatus, the location information of the first IOT device of the one or more loT devices in association with the at least one identifier of the first loT device of the one or more loT devices; and transmitting, by the first apparatus, a notification message to the second apparatus, the notification message including at least one of the at least one identifier from the first loT device of the one or more loT devices, the data associated with the first loT device and the request for data, and the location information of the first loT device.

[00154] Example 8.1. A processor-readable medium storing instructions which, when executed by at least one processor of a user equipment (UE), causes the UE at least to perform: receiving, by the UE, an indication message from a first apparatus, the indication message including an indication of one or more identifiers for one or more Internet of things (loT) devices from which to expect requested data; receiving, by the UE, a first backscatter data message from a first loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the first backscatter data message including the requested data from the first loT device; and transmitting, by the UE, a forward message to the first apparatus, the forward message including the requested data.

[00155] Example 9.1. A processor-readable medium storing instructions which, when executed by at least one processor of a user equipment (UE), causes the UE at least to perform: receiving, by the UE, an activating request from a first apparatus, the activating request including one or more identifiers of one or more Internet of things (loT) devices from which to request data, a requested data, and a request type; and transmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

[00156] Example 10.1. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, causes the apparatus at least to perform: receiving, by a first apparatus, a first message from a second apparatus, the first message including a request for data associated with one or more loT devices, a request type, and at least one of the following: one or more identifiers for the one or more Internet of things (loT) devices, or location information of each of the one or more loT devices; transmitting, by the first apparatus, a second message to at least one third apparatus, the second message including the at least one of the one or more identifiers for the one or more loT devices, the request for data associated with the one or more loT devices, the location information of each of the one or more loT devices, or the request type; receiving, by the first apparatus, a forward report message from the at least one third apparatus, the forward report message including at least one identifier from a first loT device of the one or more loT devices, data associated with the first loT device and the request for data, and location information of the first loT device; storing, by the first apparatus, the location information of the first IOT device of the one or more loT devices in association with the at least one identifier of the first loT device of the one or more loT devices; and transmitting, by the first apparatus, a notification message to the second apparatus, the notification message including at least one of the at least one identifier from the first loT device of the one or more loT devices, the data associated with the first loT device and the request for data, and the location information of the first loT device.

[00157] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[00158] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[00159] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[00160] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) ”

[00161] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, 5 PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a 10 program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[00162] While aspects of the present disclosure have been shown in the drawings, it is not 15 intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

1. A method, comprising:receiving, by a user equipment (UE), an indication message from a first apparatus, the indication message including an indication of one or more identifiers for one or more Internet of things (loT) devices from which to expect requested data;receiving, by the UE, a first backscatter data message from a first loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the first backscatter data message including the requested data from the first loT device; andtransmitting, by the UE, a forward message to the first apparatus, the forward message including the requested data.

2. The method of claim 1, wherein the report message is transmitted upon an expiration of a timer.

3. The method of claim 1, further comprising receiving, by the UE, a second backscatter data message from a second loT device of the one or more loT devices associated with an identifier of the one or more identifiers, the second backscatter data message including the requested data from the second loT device.

4. The method as in any one of claims 1-3, wherein the requested data includes location data of the one or more loT devices.

5. The method as in any one of claims 1 -4, wherein the requested data includes data stored in the one or more loT devices.

6. The method as in any one of claims 1 -5, wherein the first apparatus is a gNodeB.

7. The method as in any one of claims 1 -6, wherein the one or more loT devices arebackscattering ambient loT devices.

8. The method of claim 7, wherein at least one backscattering ambient loT device of the backscattering ambient loT devices does not store energy.

9. The method of claim 7, wherein the at least one of the one or more backscattering ambient loT devices is a passive or semi-passive ambient loT device.

10. The method of claim 1, further comprising:receiving, by the UE, an activating request from the first apparatus, the activating request including one or more identifiers of the one or more loT devices from which to request data, a requested data, and a request type; andtransmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

11. The method of claim 1, further comprising transmitting, by the UE, a report message to the first apparatus, the report message including one or more identifiers of loT devices from which expected requested data was not received.

12. A method comprising:receiving, by a user equipment (UE), an activating request from a first apparatus, the activating request including one or more identifiers of one or more Internet of things (loT) devices from which to request data, a requested data, and a request type; andtransmitting, by the UE, an activation message to the one or more loT devices, the activation message including the one or more identifiers, the requested data, and the request type.

13. The method of claim 12, wherein the requested data includes location data of the one or more loT devices.

14. The method as in any one of claims 12-13, wherein the requested data includes data stored in the one or more loT devices.

15. The method as in any one of claims 12-14, wherein the first apparatus is a gNodeB.

16. The method as in any one of claims 12-15, wherein the one or more loT devices are backscattering ambient loT devices.

17. The method of claim 16, wherein at least one backscattering ambient loT device of the backscattering ambient loT devices does not store energy.

18. The method of claim 16, wherein at least one of the one or more backscattering ambient loT devices is a passive or semi-passive ambient loT device.

19. A method comprising:receiving, by a first apparatus, a first message from a second apparatus, the first message including a request for data associated with one or more loT devices, a request type, and at least one of the following: one or more identifiers for the one or more Internet of things (loT) devices, or location information of each of the one or more loT devices;transmitting, by the first apparatus, a second message to at least one third apparatus, the second message including the at least one of the one or more identifiers for the one or more loT devices, the request for data associated with the one or more loT devices, the location information of each of the one or more loT devices, or the request type;receiving, by the first apparatus, a forward report message from the at least one third apparatus, the forward report message including at least one identifier from a first loT device of the one or more loT devices, data associated with the first loT device and the request for data, and location information of the first loT device;storing, by the first apparatus, the location information of the first IOT device of the one or more loT devices in association with the at least one identifier of the first loT device of the one or more loT devices; andtransmitting, by the first apparatus, a notification message to the second apparatus, the notification message including at least one of the at least one identifier from the first loT device of the one or more loT devices, the data associated with the first loT device and the request for data, and the location information of the first loT device.

20. The method of claim 19, wherein the location information of an loT device of the one or more loT devices corresponds to a respective set of individual candidate locations, wherein individual candidate locations of the respective set of individual candidate locations are associated with a priority order).

21. The method of claim 20, wherein an individual candidate location of the set of individual candidate locations corresponds to one of the following:a 3GPP defined location; oran identifier of a user equipment that is assumed to be proximate the loT device.

22. The method of claim 19, further comprising receiving an indication of a mobility management function to use to contact a user equipment that is assumed to be proximate an loT device of the one or more loT devices.

23. The method of claim 19, wherein the request corresponds to at least one of the following:a request to read data from the one or more loT devices,a request to write data to the one or more loT devices, ora request to locate the one or more loT devices.

24. The method of claim 19, further comprising determining the at least one third apparatus to which to transmit the request for data associated with the one or more loT devices.

25. The method of claim 19, wherein the first apparatus is an ambient Internet of things function (AIoTF).

26. The method as in any one of claims 19-25, wherein the requested data includes data stored in the one or more devices.

27. A user equipment (UE), comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the user equipment at least to perform a method as in any of claims 1-18.

28. An apparatus, comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to perform a method as in any of claims 19-26.

29. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1-26.

Images