Ambient IoT device information and procedures
Processing circuitry in ambient IoT devices manages operations and identifiers to address complexity limitations, enabling efficient communication and privacy-protected integration with networks.
Patent Information
- Application Number
- PCT/US2026/027286
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Ambient Internet of Things (IoT) devices, being low complexity and energy-harvesting devices, face challenges in performing operations comparable to more complex user equipment due to their minimal complexity and limited resources.
The introduction of processing circuitry in ambient IoT devices to manage operations such as generating and transmitting identifiers, processing inventory and command requests, and handling temporary identifiers to enhance device privacy and network communication.
Enables efficient communication and management of ambient IoT devices by ensuring authorized operations and privacy protection, facilitating seamless integration with existing network infrastructure.
Smart Images

Figure 00000056_0000 
Figure 00000057_0000 
Figure 00000058_0000
Abstract
Description
Attorney Docket No. 30164 / 105502Ref. No. P72271WO1Ambient loT Device Information and Procedures Inventors: Vivek G Gupta and Haij ing HuBackground
[0001] A network may support ambient Internet of Things (A-loT ) devices. Ambient-IoT devices may be low complexity devices, e. g., no internal power supply, limited memory, etc. For example, ambient loT devices may harvest energy from the ambient environment, e. g., radio waves may serve as an energy source for an ambient loT device. This feature provides cost and / or size reduction benefits that may enable a variety of different use cases. However, because ambient-IoT devices are low complexity devices, ambient-IoT devices may not be able to perform the same operations as more complex user equipment (UE ). Thus, there is a need to develop information and procedures for ambient-IoT devices that account for the minimal complexity of the devices.Summary
[0002] Some example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to process, based on signaling from a reader, a paging message comprising ambient-internet of Things (A-IoT ) identification information, determine the A-IoT identification information matches at least a portion of information stored in an ambient-internet of Things (A-IoT ) device permanent identifier of an A-IoT device, generate, for transmission to the reader, a response to the paging message and generate, for transmission to a network, an inventory report comprising the A-IoT device permanent identifier of the A-IoT device or an A-IoT temporary identifier of the A-IoT device.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0003] Other example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to process, based on signaling from a network function, an inventory request for one or more ambientinternet of Things (A-IoT) devices, the inventory request comprising one or more of an identification of an application function (AF) that generated the inventory request, external target area information, information about the one or more A-IoT devices, a number of the one or more A-IoT devices, whether location information is requested as part of the inventory request or a service operation request, determine the AF that generated the inventory request is authorized to receive results of the inventory request and generate, for transmission to the network function, an indication that the AF that generated the inventory request is authorized to receive the results of the inventory request.
[0004] Still further example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to process, based on signaling from a network function, a command request for one or more ambient- Internet of Things (A-IoT) devices, the command request comprising a command type to be performed by the one or more A-loT devices and an application function (AF) that generated the command request, wherein the command type comprises one of read, write or disable, determine the AF that generated the command request is authorized to invoke the command request for the one or more A-IoT devices and generate, for transmission to the network function, an indication that the AF that generated the command request is authorized to invoke the command request for the one or more A-IoT devices.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0005] Additional example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to store, in the memory, an ambient- Internet of Things (A-IoT) device permanent identifier of an A-IoT device comprising one or more of (a) a public land mobile network (PLMN) identifier corresponding to a mobile country code (MCC) or a mobile network code (MNC) of a mobile operator on which the A-IoT device has been configured to operate, (b) a network identifier corresponding to a Stand-Alone Non-Public Network (SNPN) on which the A-IoT device been configured to operate, (c) a third party identifier corresponding to a third party that operates the A-IoT device or (d) a group identifier corresponding to a group to which the A-loT device been configured to belong and determine an A-IoT temporary identifier of the A-IoT device based at least in part on the stored A-IoT permanent identifier.
[0006] More example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to process, based on signaling from a first network function, a service reguest comprising a first temporary identifier of an ambient-internet of Things (A-IoT) device, a first random number generated by the first network function and a second random number generated by a second network function, derive a temporary key based on a preconfigured key and the second random number generated by the second network function, generate, for transmission to the first network function, a Medium Access Control (MAC) element comprising the first temporary identifier and the first random number generated by the first network function.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0007] Further example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to generate a temporary key based on a preconfigured key that is stored in the memory and a random number, wherein at least a portion of the memory is memory allocated for an application function (AF), generate a first temporary identifier for an ambient- Internet of Things (A-loT ) device based on the temporary key and a permanent identifier of the A-IoT device and generate, for transmission to a network function, a service request comprising the first temporary identifier, the temporary key and the random number.
[0008] Addit ional example embodiments are related to an apparatus having processing circuitry coupled to memory, the processing circuitry configured to process, based on signaling from a network function, a first service request comprising a first temporary identifier of an ambient-internet of Things (A-loT ) device, a temporary key and a first random number, generate, for transmission to the A-IoT device, a second service request comprising the first temporary identifier of the A-IoT device, the first random number and a second random number, process, based on signaling from the A-IoT device, a Medium Access Control (MAC) element comprising the temporary key, the first temporary identifier and the second random number, derive, based on the MAC element, the temporary key, authenticate the MAC element based on the temporary key derived from the MAC element and the temporary key received in the first service request and generate, for transmission to the network function, a service response comprising the first temporary identifier of the A-IoT device and the second random number.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1Brief Description of the Drawings
[0009] Fig. 1 shows a first example deployment scenario according to various example embodiments.
[0010] Fig. 2 shows a second example deployment scenario according to various example embodiments.
[0011] Fig. 3 shows an example wireless device according to various example embodiments.
[0012] Fig. 4 shows an example user equipment (UE) according to various example embodiments.
[0013] Fig. 5 shows an example base station according to various example embodiments.
[0014] Fig. 6 shows an example ambient loT architecture according to various example embodiments.
[0015] Fig. 7 shows a control plane protocol stack for an A-I0T device according to various example embodiments.
[0016] Fig. 8 shows an example of an A-IoT Device Permanent Identifier according to various example embodiments.
[0017] Fig. 9 shows an example signaling diagram for an A-IoT inventory procedure according to various example embodiments.
[0018] Fig. 10 shows an example signaling diagram for an A-loT command procedure according to various example embodiments.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0019] Fig. 11 shows an example signaling diagram for A-IoT temporary identification generation according to various example embodiments.Detailed Description
[0020] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments disclose various information and operations for ambient Internet of Things (A-loT ) device operation. The information and operations may be stored / perf ormed at the A-IoT device, at a radio access network (RAN) node ( e. g., a reader) or at one or more core network functions.
[0021] The example embodiments are described with regard to ambient loT devices. An ambient loT device refers to a Third Generation Partnership Proj ect ( 3GPP) loT device that is smaller than other types of loT devices and provides cost-efficient solutions to various types of use cases such as, but not limited to, tracking and monitoring obj ects. Throughout this description, the terms "wireless device" or "tag" may be used to generally refer to an ambient loT device or any other type of smaller wireless device that is equipped with similar capabilities and configured with the hardware, software, and / or firmware to exchange information and data with a network.Therefore, the terms "ambient loT device, " "wireless device" and "tag" as described herein is used to represent any appropriate electronic component.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0022] The example embodiments are further described with regard to different device types including device type 1, device type 2a and device type 2b. The term "device type 1" may refer to a wireless device that possesses one or more of the following characteristics: a peak power consumption of approximately 1 microwatt (pW), energy storage capabilities, an initial sampling frequency offset (SFO) up to 10xparts per million (ppm) where x could be as high as 5, neither downlink nor uplink amplification in the wireless device and uplink transmissions that are backscattered on a carrier wave provided externally to the wireless device.
[0023] The term "device type 2a" may refer to a wireless device that possesses one or more of the following characteristics: a peak power consumption equal to or less than (<) a few hundred microwatt (pW), energy storage capabilities, an initial SFO up to 10xppm where x could be same or lower than that of device type 1, downlink and / or uplink amplification in the wireless device and uplink transmissions that are backscattered on a carrier wave provided externally to the wireless device.
[0024] The term "device type 2b" may refer to a wireless device that possesses one or more of the following characteristics: a peak power consumption of equal to or less than (<) a few hundred microwatt (pW), energy storage capabilities, an initial SFO up to 10xppm where x could be same or lower than that of device type 1, downlink and / or uplink amplification in the wireless device and uplink transmissions that are generated internally by the wireless device. However, any reference to a particular device type (e. g., device type 1,Attorney Docket No. 30164 / 105502Ref. No. P72271WO12a, eb, etc. ) is merely provided for illustrative purposes.Different entities may refer to similar concepts in a different manner.
[0025] The example embodiments are also described with regard to a 5G New Radio (NR) network. However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any network that may establish a connection to a wireless device and exchange information and data with the wireless device ( e. g., 5G-Advanced networks, 6G networks, etc. ).
[0026] The example embodiments are further described with regard to different types of deployment scenarios. In some examples, the wireless device ( e. g., ambient loT device) may communicate over the air with a base station of the network. In other examples, the wireless device may communicate over the air with a user eguipment (UE ) that acts as an intermediate node, under network control, between the wireless device and the base station. Throughout this description, the term "reader" may refer to the node that is communicating over the air with the wireless device. Therefore, a reader may refer to a base station or a UE depending on the applicable deployment scenario. Thus, in the example embodiments, communications may be referred to as reader to device (R2D) communications where the transmitter is the reader and the receiver is the ambient loT device.Similarly, device to reader (D2R) communications refer to the scenario where the transmitter is the ambient loT device and the receiver is the reader.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0027] According to some aspects, the example embodiments introduce information stored in an A-IoT device permanent identifier. According to other aspects, the example embodiments introduce an A-IoT device temporary identifier for protecting A-loT device privacy. According to further aspects, procedures are introduced to generate the A-IoT device temporary identifier, use the A-IoT device temporary identifier and / or the A-IoT device permanent identifier in inventory or command procedures. These and other example embodiments are described in greater detail below.
[0028] The example embodiments may be used independently from one another, in conjunction with currently implemented inventory procedures for A-IoT devices, in conjunction with future implementations of inventory procedures for A-IoT devices, or independently from other inventory procedures for A-IoT devices.
[0029] Fig. 1 shows a first example deployment scenario 100 according to various example embodiments. The example deployment scenario 100 includes multiple wireless devices 112A - 112N. The wireless devices 112A - 112N may be ambient loT devices or any other appropriate type of electronic component that is configured to communicate via a network. An actual deployment scenario may include any number of wireless devices being used by any number of users.
[0030] The example deployment scenario 100 also includes a UE 110. The UE 110 may be any type of electronic component that is configured to communicate via a network, e. g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things ( loT ) devices,Attorney Docket No. 30164 / 105502Ref. No. P72271WO1etc. An actual deployment scenario may include any number o f UEs being used by any number o f users. Thus, the example o f a s ingle UE 110 i s merely provided for i llustrative purposes.
[0031] The example deployment scenario 100 al so includes a 5G new radio (NR) radio access network (RAN) 120. However, the example embodiments may apply to other types o f networks ( e. g., s ixth generation ( 6G ) RAN, 5G cloud RAN, a next generation RAN (NG-RAN), a long-term evolution ( LTE ) RAN, a legacy cellular network, a wireles s local area network (WLAN), etc. ).
[0032] The 5G NR RAN 120 may be a portion o f a cel lular network that may be deployed by a network carrier ( e. g., Veri zon, AT & T, T-Mobile, etc. ). The 5G NR RAN 120 may include base stations or acces s nodes (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocel l s, microcel l s, small cel ls, femtocells, etc. ) that are conf igured to send and receive traf f ic from devices that are equipped with the appropriate cellular chip set. In the example deployment scenario 100, the 5G NR RAN 120 deploys a gNB 120A.
[0033] In the example deployment scenario 100, the UE 110 may be conf igured to operate as an intermediate node between the wireles s devices 112A - 112N and the network. Thus, the UE 110 may be conf igured as a reader and communicate with the wireles s devices 112A - 112N over the air. The wireles s devices 112A -112N may al so send mes sages directly to the UE 110. The channel s between the reader ( e. g., UE 110 ) and the wireles s devices 112A - 112N may be re ferred to as a phys ical device-to-reader data channel ( PDRCH ) for upl ink ( D2R) communication and aAttorney Docket No. 30164 / 105502Ref. No. P72271WO1physical reader-to-device data channel ( PRDCH) for downlink communication and / or control (R2D).
[0034] Fig. 2 shows a second example deployment scenario 200 according to various example embodiments. The example deployment scenario 100 includes multiple wireless devices 112A - 112N, similar to the example deployment scenario 100. The wireless devices 112A - 112N may be ambient ToT devices or any other appropriate type of electronic component that is configured to communicate via a network.
[0035] The example deployment scenario 200 also includes a 5G new radio (NR) radio access network (RAN) 120 similar to the deployment scenario 100. The 5G NR RAN 120 deploys a gNB 120A. In the example deployment scenario 200, the wireless devices 112A - 112N communicate directly with the gNB 120A, e. g., there is no intermediate UE. Thus, the gNB 120A may be configured as a reader and communicate with the wireless devices 112A - 112N over the air. The wireless devices 112A - 112N may also send messages directly to the gNB 120A. The channels between the reader ( e. g., gNB 120A) and the wireless devices 112A - 112N may also be referred to as the PDRCH for uplink communication and PRDCH for downlink communication and / or control.
[0036] Fig. 3 shows an example wireless device 112 according to various example embodiments, e. g., any of the wireless devices 112A - 112N of the example deployments 100 or 200. The wireless device 112 may include a processor 305, a memory arrangement 310, a transceiver 315 and other components 320. The other components may include, for example, an audio output device, a power supply, energy storage, ports to electricallyAttorney Docket No. 30164 / 105502Ref. No. P72271WO1connect the wireless device 112 to other electronic components, etc.
[0037] The processor 305 may be comprised of processing circuitry that is configured to execute a plurality of engines of the wireless device 112. For example, the engines may include an ambient loT engine 335. The ambient I0T engine 335 may perform various operations related to operations for A-IoT devices, including but not limited to, storing an A-IoT device permanent identifier, generating and storing an A-IoT device temporary identifier and performing inventory or command procedures using the A-IoT device permanent identifier and / or A-loT device temporary identifier. These and other operations are described in greater detail below.
[0038] The above referenced engine 335 being an application ( e. g., a program) executed by the processor 305 is merely provided for illustrative purposes. The functionality associated with the processor 305 and / or engine 335 may also be represented as a separate incorporated component of the wireless device 112 or may be a modular component coupled to the wireless device 112, e. g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engine may also be embodied as one application or separate applications. In addition, in some devices, the functionality described for the processor 305 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a wireless device.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0039] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the wireles s device 112. In some examples, the memory arrangement 310 may include non-volatile memory (NVM) that i s used to permanently store certain types of information ( e. g., device ID, etc. ) and regi sters for temporarily storing information whi le energy i s avai lable in energy storage. However, reference to NVM and regi sters is merely provided for il lustrative purposes. The example embodiments may be implemented in any o f these or other configurations of a memory arrangement.
[0040] The transceiver 315 may be a hardware component configured to communicate with the 5G NR-RAN 120, an LTE-RAN ( not pictured), a legacy RAN ( not pictured), a WLAN ( not pictured), etc. Accordingly, the transceiver 315 may operate on a variety o f di f ferent frequencies or channel s ( e. g., set o f consecutive frequencies ). The transceiver 315 includes circuitry configured to transmit and / or receive s ignals ( e. g., control s ignal s, data signal s ). Such s ignal s may be encoded with information implementing any one o f the methods described herein. The proces sor 305 may be operably coupled to the transceiver 315 and conf igured to receive from and / or transmit s ignal s to the transceiver 315. The proces sor 305 may be configured to encode, decode and / or proces s s ignals ( e. g., s ignal ing from a reader ) for implementing any one o f the techniques described herein.
[0041] Fig. 4 shows an example UE 110 according to various example embodiments. The UE 110 wi l l be described with regard to the example deployment 100 o f Fig. 1. The UE 110 may include aAttorney Docket No. 30164 / 105502Ref. No. P72271WO1processor 405, a memory arrangement 410, a display device 415, an input / output ( I / O) device 420, a transceiver 425 and other components 430. The other components 430 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, etc.
[0042] The processor 405 may be comprised of processing circuitry that is configured to execute a plurality of engines for the UE 110. For example, the engines may include an ambient loT engine 435. The ambient IOT engine 435 may perform various operations related to operations for A-IoT devices, including but not limited to, performing inventory or command procedures for the A-IoT devices. These and other operations are described in greater detail below.
[0043] The above referenced engine 435 being an application ( e. g., a program) executed by the processor 405 is merely provided for illustrative purposes. The functionality associated with the engine 435 may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e. g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engine may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor 405 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0044] The memory arrangement 410 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 415 may be a hardware component configured to show data to a user while the I / O device 420 may be a hardware component that enables the user to enterinputs. The display device 415 and the I / O device 420 may be separate components or integrated together such as a touchscreen.
[0045] The transceiver 425 may be a hardware component configured to exchange data with the wireless device 112, the 5G NR RAN 120 and / or any other appropriate type of network.Accordingly, the transceiver 425 may operate on a variety of different freguencies or channels (e. g., set of consecutive frequencies). The transceiver 425 includes circuitry configured to transmit and / or receive signals (e. g., control signals, data signals). Such signals may be encoded with information implementing any one of the methods described herein. The processor 405 may be operably coupled to the transceiver 425 and configured to receive from and / or transmit signals to the transceiver 425. The processor 405 may be configured to encode, decode and / or process signals (e. g., signaling from a base station of a network or from an ambient loT device) for implementing any one of the techniques described herein.
[0046] Fig. 5 shows an example base station 500 according to various example embodiments. The base station 500 may represent the gNB 120A of the deployment scenario 100 or 200 or any other type of access node.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0047] The base station 500 may include a processor 505, a memory arrangement 510, an input / output ( I / O) device 515, a transceiver 520, and other components 525. The other components 525 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the base station 500 to other electronic devices and / or power sources, transceiver chains, antenna elements, antenna panels, etc.
[0048] The processor 505 may be comprised of processing circuitry that is configured to execute a plurality of engines for the base station 500. For example, the engines may include an ambient loT engine 535. The ambient IOT engine 535 may perform various operations related to operations for A-IoT devices, including but not limited to, performing inventory or command procedures for the A-IoT devices. These and other operations are described in greater detail below.
[0049] The above noted engine 535 being an application ( e. g., a program) executed by the processor 505 is only an example. The functionality associated with the engine 535 may also be represented as a separate incorporated component of the base station 500 or may be a modular component coupled to the base station 500, e. g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. In addition, in some base stations, the functionality described for the processor 505 is split among a plurality of processors ( e. g., a baseband processor, an applications processor, etc. ). The exampleAttorney Docket No. 30164 / 105502Ref. No. P72271WO1embodiments may be implemented in any of these or other configurations of a base station.
[0050] The memory arrangement 510 may be a hardware component configured to store data related to operations performed by the base station 500. The I / O device 515 may be a hardware component or ports that enable a user to interact with the base station 500.
[0051] The transceiver 520 may be a hardware component configured to exchange data with the UE 110 and / or the wireles s devices 112A - 112N. The transceiver 520 may operate on a variety o f di f ferent frequencies or channels ( e. g., set o f consecutive frequencies ). There fore, the transceiver 520 may include one or more components to enable the data exchange with the various networks, UEs and wireles s devices. The transceiver 520 includes circuitry configured to transmit and / or receive s ignal s ( e. g., control s ignal s, data signals ). Such s ignal s may be encoded with information implementing any one of the methods described herein. The proces sor 505 may be operably coupled to the transceiver 520 and conf igured to receive from and / or transmit signals to the transceiver 520. The proces sor 505 may be conf igured to encode, decode and / or proces s s ignal s ( e. g., s ignal ing from a UE, an ambient loT device, etc. ) for implementing any one of the methods described herein.
[0052] Fig. 6 shows an example ambient loT architecture 600 according to various example embodiments. The example ambient loT architecture 600 may be for the example deployment scenario 200, e. g., where the gNB 120A acts as the reader. However, a s imilar architecture may be used for the example deploymentAttorney Docket No. 30164 / 105502Ref. No. P72271WO1scenario 100. The various A-IoT device information and procedures may be described with reference to the various components shown in the example ambient loT architecture 600. As shown in Fig. 6, all the components within the dashed box may be core network functions. However, as described below, some of these functions may be located outside of the core network in some example embodiments.
[0053] The example ambient loT architecture 600 shows an A-loT device 605 and a reader 610 (e. g., the gNB 120A). The reader communicates with an A-IoT function (AIoTF) 615 of the core network. The AIoTF 615 may communicate with the service bus of the core network using an Naiotf interface. In some architectures, the AIoTF 615 may be integrated with an access and mobility function (AMF) 620. The AIoTF 615 may act as a network layer security termination point. Credentials ( including device ID and authentication credentials ) for the A-IoT device 605 authentication may be owned by an operator ( e. g., a network operator) or by a third party. Command request and response messages may be confidentiality, integrity and relay protected based on a pre-shared key and freshness parameter or session keys. Some examples of this protection are described in greater detail below.
[0054] The example ambient loT architecture 600 also includes A-IoT Data Management (ADM) 635. The ADM 635 may manage an A-IoT device profile data and an application function (AF) 630 subscription data. The ADM 635 may store an operator' s subscription data for the A-IoT device 605 used in the network. Some examples of the A-IoT device 605 data that are stored in the A-IoT device profile data are described below.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0055] Fig. 7 shows a control plane protocol stack 700 for an A-IOT device according to various example embodiments. The control plane protocol stack 700 includes the A-IoT device 705, the reader ( e. g., NG-RAN 710 ), the AIoTF 715, a network exposure function (NEF) 725 and an application function (AF) 730. As shown in Fig. 7, A-IoT data 750 interfaces with the AF 730 of the core network and the A-IoT non-access stratum (NAS ) 760 interfaces with the AIoTF 715.
[0056] In the example embodiments, ambient-IoT devices may be assigned an A-IoT device permanent identifier. Fig. 8 shows an example of an A-IoT Device Permanent Identifier 800 according to various example embodiments. The A-IoT Device Permanent Identifier 800 may be a globally unique identifier allocated to each A-IoT device by an operator or a third party. The A-IoT Device Permanent Identifier 800 may be, for example, 12, 16 or 24 octets in length. However, other lengths are possible.
[0057] The A-IoT Device Permanent Identifier 800 includes an A-IoT Device ID Type 810 that indicates whether the A-IoT Device Permanent Identifier 800 contains various domain information. This information may include a Public Land Mobile Network ( PLMN) ID 820, a network identifier 830, a third party identifier 840, a group identifier 850, or A-IoT Device Identification Information 860. The A-IoT Device Permanent Identifier 800 is not required to include all the information described above but may only include some of the information. In addition, other information not described herein may also be included in the A-loT Device Permanent Identifier 800.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0058] The PLMN ID 820 may compri se a PLMN identi f ier corresponding to a mobi le country code (MCC ), a mobi le network code (MNC ), etc. o f a mobile operator that manages or operates the A- IoT device. The network identi f ier 830 may identi fy a Stand-Alone Non-Publ ic Network ( SNPN) as speci f ied in 3GPP Technical Speci fication ( TS ) 23. 003 clause 12. 7 i f the A- IoT device i s managed or operated by a private network provider. The third party identi f ier 840 may identi fy a third party that manages or operates the A- IoT device. In some cases, the network identi f ier 830 and the third party identi f ier 840 may be the same but in other cases, they may be di f ferent. The group identi f ier 850 may identi fy a group to which the A- IoT device may belong. For example, each A- IoT device in a deployment may be as sociated with a particular product, e. g., cars. In some examples, the group may include al l A- IoT devices as sociated with a car. In another example, the group may be further subdivided, e. g., a first group may include al l A- IoT devices as sociated with a sedan, a second group may include al l A- IoT devices associated with an SUV, etc. The A- IoT devices may be grouped in any manner and the group ID 850 may identi fy the group to which the A- IoT device belongs.
[0059] The A- IoT Device Identi f ication information 860 may be used to identi fy the device and di stingui sh it from other A- IoT devices ( e. g., an actual identi fication number or symbol ) within the scope o f the Domain Information. For example, the A- IoT Device Identi f ication information 8 60 may include an evolved packet core ( EPC ) tag as def ined in GS 1 TDS Release 2. 1: " EPC Tag Data Standard" or other unstructured information.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0060] The example embodiments also provide for A-IoT temporary identifiers that are used to protect A-IoT device privacy, e. g., the A-IoT device permanent identifiers may be protected by use of the A-IoT temporary identifiers. The A-IoT temporary identifiers allow for unambiguous identification of the A-IoT device and also support a mechanism to re-synchronize and de-synchronize with the network (AIoTF).
[0061] In some example embodiments, the A-IoT temporary identifiers may be allocated by the network. For example, the network may generate the A-IoT temporary ID and provision the A-loT temporary ID to each A-IoT device. In some example embodiments, the AIoTF 615 supports the A-IoT temporary ID generation and provisioning. A command procedure (e. g., write operation) may be used by the AIoTF 615 to provision the A-IoT temporary ID to the A-IoT device 605. The A-IoT temporary ID may be sent in an encrypted A-IoT NAS message, e. g., as shown in NAS messaging 760 of Fig. 7. The AIoTF 615 may trigger the allocation of the A-IoT temporary ID to each A-IoT device. The A-IoT device 605 may store the allocated A-IoT temporary ID in non-volatile memory, and acknowledges receipt of the A-IoT temporary ID to the network. I f the A-IoT device 605 has an old A-IoT temporary ID, the A-IoT device 605 may overwrite the old A-IoT temporary ID with the new A-IoT temporary ID. The AIoTF 615 may consider the success of temporary ID when the acknowledgement is received from the A-IoT device 605. I f the AIoTF 615 does not receive the acknowledgement from the A-IoT device 605, the AIoTF 615 may re-try the allocation for a configured number of attempts. When the allocation is successful, the AIoTF 615 stores the newly allocated A-IoT temporary ID in a device data profile ( e. g., in the ADM 635 ),Attorney Docket No. 30164 / 105502Ref. No. P72271WO1but in the unsucces s ful case the AIoTF 615 may store both the new and old A- IoT temporary ID in the device data pro f ile.
[0062] In other example embodiments, the A- IoT temporary ID may be al located by the A- IoT device 605. For example, the A- IoT device 605 may autonomous ly generate the A- IoT temporary ID local ly based on a pre-configured parameter, e. g., a preconfigured key and the A- IoT Device Permanent Identi f ier.
[0063] Fig. 11 shows an example s ignal ing diagram for A- IoT temporary identi f ier generation 1100 according to various example embodiments. The signal ing diagram shows signaling between an A- IoT device 1101, a reader 1102, an AMF 1103, an AIoTF 1104, a Uni f ied Data Management (UDM) / Authentication Server Function (AUS F) / ADM 1105, an NRF 1106, an NEF 1107 and an AF 1108. The A- IoT temporary identi f ication generation 1100 i s described for the second example deployment scenario 200, e. g., where a base station i s a reader. However, the A- IoT temporary identi f ication generation 1100 may be modi f ied to be used with the first example deployment scenario 100.
[0064] At 1110, the A- IoT device 1101 and the AF 1108 have been pre-conf igured with information that may include the A- IoT device permanent ID 800 ( e. g., one or more of the PLMN ID, network ID 830, third party ID 840, group ID 850, A- IOT device ID, etc. ) and any appropriate credential s to access the network ( e. g., key K).
[0065] At 1115, the reader 1102 regi sters as a reader with the AIoTF 1104. Thi s regi stration may include the reader ID of the reader 1102. As described above, in some exampleAttorney Docket No. 30164 / 105502Ref. No. P72271WO1embodiments, the AIoTF 1104 may be integrated with the AMF 903. In 1120, the AIoTF 1104 may register with the NRF 1106. This registration may include the AIoTF ID of the AIoTF 1104.
[0066] In 1125, the AF 1108 may generate a temporary key (e. g., KATOT ) using the key K that was preconfigured to the AF 1108 and a random number (e. g., RANDAF). The AF 1108 also generates a Temp AIoT Dev Id 1 using KA-IOT and the A-IoT device permanent ID in the first instance. In subsequent instances, a different device ID may be used. In 1130, the AF 1108 sends a service request to the AIoTF 1104 to provision the A-IoT device 1101 with the A-IoT temporary identifier. The service request includes the Temp AIoT Dev Id 1, the temporary key KA-IO? and the R NDAF •
[0067] At 1135, the AIoTF 1104 sends the service request to the A-IoT device 1101 using NAS signaling. The service request sent by the AIoTF 1104 includes the some of the information from the service request sent by the AF 1108 (e. g., theTemp AIoT Dev Id 1 and the RANDAF) but also may include another random number RANDA-TO- generated by the AIoTF 1104.
[0068] At 1140, the A-IoT device 1101 derives the key KA-IOT using the key K that was preconfigured to the A-IoT device 1101 and the random number RANDAF received in the service request to generate a Medium Access Control (MAC) element. The MAC element may include the key KA-TOT derived by the A-IoT device 1101 and the Temp AIoT Dev Id 1 and the random number RA DA-IOT received in the service request. At 1145, the A-IoT device 1101 transmits an A-IoT service response comprising the MAC element to the AIoTF 1104.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0069] At 1150, the AIoTF 1104 derives the key KA-IOT from the Temp_AIoT_Dev_Id_l to veri fy the authenticity o f the MAC element, e. g., the AIoTF 1104 may derive the key K -ICT from the MAC and compare it to the key K -IOT received from the AF 1108. I f the two key KA-TOT match, then the MAC is authenticated. At 1155, the AIoTF 1104 sends an A- IoT service response indicating whether the MAC element has been authenticated.
[0070] I f the MAC element has been authenticated, as described above, the A- IoT temporary identi fier may be generated by the network ( e. g., AF 1108 ) or the A- IoT device 1101. As shown in Fig. 11, at 11 60 and / or 11 65, the AF 1108 or the A- IoT device 1101, respectively, may generate the A- IoT temporary identi f ier ( e. g., Temp_AIoT_Dev_ID_2 ) from the key KATOT, a random number ( RANDAIOT ) and the Temp AIoT Dev ID 1.
[0071] In some example embodiments, the A- IoT temporary ID may be used in an inventory procedure that may be a group inventory or a single device inventory. For group inventory, the AIoTF 615 may provide fi ltering information ( e. g., MASK or Group Identi f ier ) to a reader ( e. g., reader 610 ) for paging. The f i ltering information may be generated based on the A- IoT device permanent identi f ier. When the network al locates the A- IoT temporary ID, upon receiving the f i ltering information ( e. g., MASK or Group Identi fier ) in the paging message, the A- IoT device 605 matches the f i ltering information with the A- IoT permanent ID, and i f matched the A- IoT device 605 reports the A-loT temporary ID to the network. The AIoTF 615 may then derive the A- IoT device permanent ID from the A- IoT temporary ID, based on the mapping stored in the device data prof i le in the ADM 635.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1When the A- IoT device 605m al locates the A- IoT temporary ID, the A- IoT device 605m matches the f iltering information with the A-loT permanent ID and generates the A- IoT temporary ID local ly and reports the A- IoT temporary ID to the network.
[0072] A s ingle device inventory means the AIoTF 615 provides the A- IoT temporary ID to the reader 610 for paging. On receiving the paging, the A- IoT device 605 matches the f i ltering information with the provisioned A- IoT temporary ID, and reports the A- IoT temporary ID to the network in an inventory response mes sage.
[0073] An example s ignaling diagram o f an inventory procedure i s provided below with respect to Fig. 9 to describe an example inventory procedure in greater detai l.
[0074] The A- IoT device pro f ile ( e. g., that i s stored in the ADM 635 ) may include the A- IoT device permanent identi fier, device credential s, the last known AIoTF that served the A- IoT device ( e. g., IP addres s o f AIoTF), any subscription related information, device status ( active or permanently di sabled), etc. I f the A- IoT device 605 i s managed by the network, then the pro fi le data for an A- IoT device 605 is stored in the network. When the credential s ( including device ID and authentication credential ) i s owned by the operator, the authentication credentials o f an A- IoT device 605 may be conf igured and securely stored in the network. When the credential s ( including device ID and authentication credential ) i s owned by a third party, the device prof i le data ( e. g., Device ID or credentials ) may be stored external to the network.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0075] The A-IoT device permanent ID may be used by the AIoTF 615 together with the local configuration or third party related context to locate the entity that stores the profile data of an A-IoT device. The A-IoT device permanent ID may be the primary key for the A-IoT device profile data in the ADM 635.
[0076] The AIoTF 615 may store and manage the A-IoT device related information (also known as device context information) locally (e. g., separate from the data profile stored at the ADM 635 ) that includes, e. g. the A-IoT device permanent ID, the last known reader information of the A-IoT device, etc. The last known reader information may be used to support the AIoTF 615 to select the serving reader to forward messages towards the specific A-IoT device ( s ). When the AIoTF 615 receives an inventory report from the A-IoT RAN 610, the AIoTF 615 extracts the inventory response A-IoT NAS message sent from an A-IoT device 605 and determines the A-IoT device permanent ID. The AIoTF 615 may also obtain the A-IoT RAN reader 610 ID that represents the A-IoT device 605 location at a reader ID granularity. I f there is no available A-IoT device context for this A-IoT device 605, the AIoTF 615 may retrieve the A-IoT device profile data from the ADM 635 and checks the A-IoT device permanent ID against the A-IoT device profile. I f validated, the AIoTF 615 may generate the A-IoT device context to locally store the A-IoT device permanent ID and the last known A-IoT RAN reader information. Otherwise, the AIoTF 615 checks the A-IoT device permanent ID against the local A-IoT device context. The AIoTF 615 may update the last known A-IoT RAN reader information in the A-IoT device context.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0077] When the AIoTF 615 selects the A-IoT RAN node and / or reader 610 using the last known A-IoT RAN reader information in the A-IoT device context but does not find the target A-IoT device through the inventory process under the last known A-IoT RAN reader, then the AIoTF 615 deletes the available A-IoT device context of the target A-IoT device.
[0078] If an A-IoT 605 device has registered with the network and has been inventoried, then the A-IoT device 605 is authorized to use the network resources when the device profile data is retrieved.
[0079] If an A-IoT device 605 is to be permanently disabled (e. g., on request by the third party AF), then the network is no longer required to store the device profile data for such an A-loT device 605. The network may purge the profile data for such an A-IoT device 605. The network may trigger the "permanent disable" command towards such an A-IoT device 605. When the AIoTF 615 receives the permanent disable request from AF 630, the AIoTF 615 sets the device status to "to be disabled" in the A-IoT device profile data at the ADM 635. When the AIoTF 615 confirms the successful disabling of an A-IoT device 605, this sets the device status to "disabled" in A-IoT device profile data at the ADM 635. The ADM 635 may delete the corresponding profile data in the ADM 635 based on the "disabled" device status. This deletion may occur at any time based on operator implementation after the "disabled" device status has been set.
[0080] When an AIoTF 615 attempts to retrieve the device profile data (e. g., in an inventory procedure after the AIoTF 615 receives the inventory response from the A-IoT device 605),Attorney Docket No. 30164 / 105502Ref. No. P72271WO1the AIoTF 615 retrieves the device profile data to perform the validation of the device. In this case, the A-IoT device permanent ID or domain information may be used for ADM discovery and selection.
[0081] When the AIoTF 615 updates the last known AIoTF for the A-IoT device 605, after the validation of the device, the AIoTF 615 may further update the last known AIoTF if there is a serving AIoTF change. In this case, the ADM 635 instance may already be known in the retrieving device profile step, and it there may be no need to perform the ADM discovery and selection again. Even if a need arises for the information, the A-IoT device permanent ID or domain information may be used in that case.
[0082] When the AIoTF 615 is to retrieve AF authorization data, after receiving an A-IoT service request, the AIoTF 615 may retrieve the AF authorization data to ensure the AF is authorized to perform the service operation on the target A-IoT devices within the target area. In this case, the AF ID may be used for ADM 635 discovery and selection.
[0083] When the NEF 625 is to obtain the last known AIoTF for the A-IoT device 605, after receiving an A-IoT service request, in case when targeting individual A-IoT device ( s ), the NEF 625 may fetch the last known AIoTF to send the request to this AIoTF as an optimization. In this case, the A-IoT device permanent ID or domain information may be used for ADM 635 discovery and selection.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0084] The AIoTF 615 supports ADM 635 discovery and selection to select an ADM 635 instance to retrieve the device profile data or update the last known AIoTF for the A-IoT device. The AIoTF 615 may also discover and select an ADM 635 to retrieve AF authorization data. When the ADM discovery is performed, the AIoTF 615 or the NEF 625 utilizes the network repository function (NRF) 640 to discover the ADM 635 instance ( s ) unless the ADM information is available by other means, e. g., locally configured and may use the following information: a] The A-IoT device permanent ID or domain information, b] the AF ID.
[0085] The A-IoT devices ( e. g., A-IoT device 605 ) may include a non-volatile memory that may be used to store application specific data that may be accessed using A-IoT NAS commands. The A-IoT device 605 memory may accessed by the following A-IoT NAS commands: a] Read: Used to read the contents of the Application Memory; and b] Write: Used to write into the Application Memory. The A-IoT NAS commands to access the memory may be used when an authorized AF uses the Read or Write command service operations. The A-IoT device 605 may store, for example, the A-IoT permanent device ID, device credentials, user, A-IoT temporary ID, device status, etc. From the A-IoT NAS perspective, the A-IoT device may expose the user memory for read / write operations. An example command operation is described in greater detail below.
[0086] Fig. 9 shows an example signaling diagram for an A-IoT inventory procedure 900 according to various example embodiments. The signaling diagram shows signaling between an A-loT device 901, a reader 902, an AMF 903, an AIoTF 904, a Unified Data Management (UDM) / Authentication Server Function (AUSF) / ADM 905, an NRF 906, an NEF 907 and an AF 908. TheAttorney Docket No. 30164 / 105502Ref. No. P72271WO1inventory procedure 900 i s described for the second example deployment scenario 200, e. g., where a base station i s a reader. However, the inventory procedure 900 may be modi fied to be used with the first example deployment scenario 100.
[0087] At 910, the A- IoT device 901 has been pre-conf igured with information such that it can be regi stered with the network and inventoried. Thi s information may include the A- IoT device permanent ID 800 ( e. g., one or more o f the PLMN ID, network ID 830, third party ID 840, group ID 850, etc. ), credential s to acces s the network, etc.
[0088] At 915, the reader 902 regi sters as a reader with the AIoTF 904. Thi s regi stration may include the reader ID o f the reader 902. As described above, in some example embodiments, the AIoTF 904 may be integrated with the AMF 903. In 920, the AIoTF 904 may regi ster with the NRF 906. This registration may include the AIoTF ID o f the AIoTF 904.
[0089] At 925, the AF 908 invokes an AIoT_Inventory_Request to the NEF 907 that may include, for example, the AF ID, external target area information, information about the target A- IoT device ( s ), approximate number o f A- IoT devices, location information requested, a service operation request, etc. The information about the target A- IoT device ( s ) may include f i ltering information that may include a bit string that can be used to match any component o f the A- IoT permanent device identi f ier 800 ( e. g., PLMN ID, group ID, etc. ). The approximate number o f A- IoT devices may be used to determine the number of A- IoT devices expected to respond to thi s inventory service operation. The location information requested parameter mayAttorney Docket No. 30164 / 105502Ref. No. P72271WO1indicate whether the AF 908 expects the network to provide the device location information.
[0090] At 930, the NEF 907 and the NRF 906 perform an AIoTF discovery and selection procedure. As described above, this AIoTF discovery and selection procedure may be based on information stored at the network, e. g., the last AIoTF used by the A-IoT device 901, the A-IoT permanent identifier of the A-loT device, etc.
[0091] At 935, the NEF 907 forwards the AIoT_Inventory_Request to the selected AIoTF 904. At 940, the AIoTF 904 performs a check to determine that the AF 908 is authorized to perform the inventory request. At 945, the AIoTF 904 provides an Inventory_Response to the NEF 907 indicating whether the check was successful. In this example, it may be considered that the check was successful and the inventory procedure 900 continues. At 950, the NEF 907 provides the Inventory Response to the AF 908.
[0092] At 960, the AIoTF 904 selects the reader ( s ) to perform the inventory procedure 900 with the A-IoT devices. As described above, the AIoTF 904 may store and manage the A-IoT device related information (also known as device context information) locally (e. g., separate from the data profile stored at the ADM 905 ) that includes, e. g. the A-IoT device permanent ID, the last known reader information of the A-IoT device, etc. The last known reader information may be used to support the AIoTF 904 to select the serving reader to forward messages towards the specific A-IoT device ( s ). If there is no available A-IoT device context for the A-IoT device 901, the AIoTF 904 may retrieve theAttorney Docket No. 30164 / 105502Ref. No. P72271WO1A-IoT device profile data from the ADM 905 and check the A-IoT device permanent ID against the A-IoT device profile. If validated, the AIoTF 904 may generate the A-IoT device context to locally store the A-IoT device permanent ID and the last known A-IoT RAN reader information. Otherwise, the AIoTF 904 checks the A-IoT device permanent ID against the local A-IoT device context. The AIoTF 904 may update the last known A-IoT RAN reader information in the A-IoT device context. In this example, the reader 902 is selected.
[0093] At 965, the AIoTF 904 sends the Inventory Request message including a Correlation ID, the A-IoT Identification Information to be included in the paging message, and assistance information to the reader 902. At 970, the reader 902 sends an Inventory Response to the AIoTF 904 indicating that the Inventory Request has been successfully received and the reader 902 will perform the service operation.
[0094] At 975, the reader 902 and the A-IoT device 901 perform the inventory procedure. As described above, upon receipt of the Inventory Request message from the AIoTF 904, the reader 902 may execute the inventory operation. The reader 902 may broadcast a paging message that includes the A-IoT identification information, e. g., PLMN ID, group ID, etc. The A-loT device 901 determines whether it matches the A-IoT identification information, e. g., the information in the A-IOT device 901 A-IoT permanent identifier 800 matches any information in the paging message.
[0095] At 980, if the A-IoT device 901 matches the A-IoT identification information in the paging message, the A-IoTAttorney Docket No. 30164 / 105502Ref. No. P72271WO1device 901 responds to the paging mes sage and sends an A- IoT NAS mes sage ( e. g., Inventory Report ) that includes the A- IoT device permanent ID to the AIoTF 904. As described above, in some example embodiments, the Inventory Report may include the A- IoT temporary identi f ier so that the A- IoT device permanent ID is not exposed during the inventory procedure.
[0096] At 983, the AIoTF 904 val idates the results, e. g., us ing local stored device information or device pro f i le data retrieved from the ADM 905 to match the A- IoT device permanent ID or the A- IoT temporary identi fier included in the Inventory_Report. At 987, the AIoTF 904 may send a NAS mes sage ( Inventory Complete ) to the A- IoT device 901. ThisInventory Complete mes sage may include the A- IoT device 901 temporary ID to indicate to the A- IoT device that the Inventory Report was success ful ly received by the AIoTF 904.
[0097] I f the inventory procedure 900 is a group inventory procedure, at 990, the AIoTF 904 may aggregate the results, e. g., the Inventory Reports from multiple A- IoT devices. In some example embodiments, i f the reader 902 detects that no additional A- IoT devices wil l respond to the inventory procedure, the reader 902 may inform the AIoTF 904 that the procedure i s complete.
[0098] At 993, the AIoTF 904 may report the progres s o f the A- IoT inventory request by sending an AIoT_Noti fy mes sage including a l i st o f A- IoT device permanent Identi fier ( s ) to the NEF 907. The AIoTF 904 may send multiple reports at 993. I f location information i s requested by the AF 908, and i f the location of the reader 902 i s conf igured, based on the mappingAttorney Docket No. 30164 / 105502Ref. No. P72271WO1between the reader ID and the A-IoT device ID (s), the AIoTF 904 may provide the location information in the reports. At 997, the NEF 907 forward the inventory reports to the AF 908 and the inventory procedure 900 is complete.
[0099] Fig. 10 shows an example signaling diagram for an A-loT command procedure 1000 according to various example embodiments. The signaling diagram shows signaling between an A-loT device 1001, a reader 1002, an AMF 1003, an AIoTF 1004, a UDM) / AUSF / ADM 1005, an NRF 1006, an NEF 1007 and an AF 1008. The command procedure 1000 is described for the second example deployment scenario 200, e. g., where a base station is a reader. However, the command procedure 1000 may be modified to be used with the first example deployment scenario 100. In addition, some of the operations performed in the command procedure 1000 are similar to the operations performed in the inventory procedure 900. These operations are not described in detail below because they have already been described above.
[0100] At 1010, the A-IoT device 1001 has been pre-configured with information similar to 910 of the inventory procedure 900. At 1015, the reader 1002 registers as a reader with the AIoTF 1004 similar to 915 of the inventory procedure 900. At 1020, the AIoTF 1004 may register with the NRF 1006 similar to 920 of the inventory procedure 900.
[0101] At 1025, the AF 1008 invokes an Al oT_Command_Re quest that may include, for example, the AF ID, external target area information, information about the target A-IoT device (s), an approximate number of A-IoT devices, location information requested, a service operation request, a command type, etc.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1Some of this information included in the AIoT Command Request was described above as also being included in the AIoT_Inventory_Request. The command type may be Read, Write, Permanent Disable, etc. Some example operations of A-IoT devices in response to these example commands were described above. The example embodiments are not limited to these commands as other command types may also be performed.
[0102] At 1030, the NEF 1007 and the NRF 1006 perform an AIoTF discovery and selection procedure similar to 930 of the inventory procedure 900. At 1035, the NEF 1007 forwards the AIoT_Command_Request to the selected AIoTF 1004. At 1040, the AIoTF 1004 performs a check to determine that the AF 1008 is authorized to perform the command request. At 1045, the AIoTF 1004 provides a Command_Response to the NEF 1007 indicating whether the check was successful. In this example, it may be considered that the check was successful and the command procedure 1000 continues. At 1050, the NEF 1007 provides the Command Response to the AF 1008.
[0103] At 1060, the AIoTF 1004 selects the reader ( s ) to perform the command procedure 900 with the A-IoT device ( s ) similar to 960 of the inventory procedure 900.
[0104] At 1065-1087 the operations described above for 965-987 of the inventory procedure 900 may be performed with some clarifications. For example, in 1083, the AIoTF 1004 may validate the results of the inventory procedure to determine whether the command should be sent to an A-IoT Device, e. g., by checking the target A-IoT device information. I f there is not a successful inventory response from the A-IoT device 901, theAttorney Docket No. 30164 / 105502Ref. No. P72271WO1operations between the AIoTF 1004, the reader 1002 and the A- IoT device 901 as sociated with the command procedure 1000, e. g., 1090- 1096, are not performed. In such a case, the AIoTF 1004 may send a failure report to the NEF 1007 in 1097 that i s then forwarded to the AF 1008 in 1099.
[0105] However, for each succes s ful inventory response received, the AIoTF 1004 may, at 1090, send a Command Request mes sage that includes, for example, a correlation ID, reader ID, NAS Command Request, approximate D2R message si ze, etc. to the reader 1002 directly or as an A- IoT Trans fer Container via the AMF 1003. The NAS Command Request mes sage may include the A-loT data.
[0106] At 1092, the reader 1002 sends the Command Request mes sage to the A- IoT device 1001. The A- IoT device 1001 performs the speci fied command, e. g., read, write, disable, and, at 1094, provides a Command_Response to the reader 1002 indicating whether the command has been succes s ful ly executed.
[0107] At 1096, the reader 1002 responds with a Command Response mes sage that may include, for example, the correlation ID, reader ID, NAS Command Response to the AIoTF 1004 directly or as an A- IoT Trans fer Container via the AMF 1003. At 1097, the AIoTF 1004 reports the result o f the A- IoT Command request to the NEF 1007 by sending the AIoT_Command Noti fy mes sage (A- IoT Device ID ( s ), AF ID, A- IoT data, etc. ). I f location information i s requested by the AF 1008, and i f the location of the reader 1002 i s conf igured based on the mapping between the reader ID and the A- IoT device ID ( s ), the AIoTF 1004 may provide theAttorney Docket No. 30164 / 105502Ref. No. P72271WO1location information in the reports. At 1099, the NEF 1007 may then forward the AIoT Command Notify message to the AF 1008.
[0108] As described above, the command may include a permanent disable command that may permanently disable an A-IoT device. A permanently disabled A-IoT device does not respond to the inventory procedure. An A-IoT device is permanently disabled by a Disable NAS Command. The Disable NAS Command may be sent to the A-IoT device when an authorized AF uses the disable command service operations. The disable NAS Command and its response may use the command procedure, e. g., procedure 1000. When the A-IoT device has received and verified a disable NAS Command, it may no longer respond to the inventory procedure. The A-IoT device may respond to indicate whether the disable command was successful.Examples
[0109] In a first example, a method, comprising storing, in the memory, an ambient- Internet of Things (A-IoT ) device permanent identifier of an A-IoT device comprising one or more of (a) a public land mobile network (PLMN) identifier corresponding to a mobile country code (MCC) or a mobile network code (MNC) of a mobile operator on which the A-IoT device has been configured to operate, (b) a network identifier corresponding to a Stand-Alone Non-Public Network ( SNPN) on which the A-IoT device been configured to operate, ( c) a third party identifier corresponding to a third party that operates the A-IoT device or (d) a group identifier corresponding to a group to which the A-IoT device been configured to belong and determining an A-IoT temporary identifier of the A-IoT device based at least in part on the stored A-IoT permanent identifier.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0110] In a second example, the method of the first example, wherein the A-IoT temporary identifier is further determined on signaling from a network.
[0111] In a third example, the method of the second example, wherein the signaling from the network comprises an encrypted A-loT non-access stratum (NAS) message.
[0112] In a fourth example, the method of the second example, wherein the signaling from the network comprises a command procedure comprising a write command to write the A-IoT temporary identifier to the memory.
[0113] In a fifth example, the method of the fourth example, wherein, when the A-IoT device has a previously stored A-IoT temporary identifier, the write command indicates that the A-IoT temporary identifier is to be used over the previously stored A-loT temporary identifier.
[0114] In a sixth example, the method of the fourth example, further comprising generating, for transmission to the network, an acknowledgment indicating the write command was successfully performed.
[0115] In a seventh example, the method of the first example, further comprising generating the A-IoT temporary identifier based at least in part on the determined A-IoT temporary identifier.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0116] In an eighth example, the method of the seventh example, wherein A-IoT temporary identifier is generated based on a pre-configured key and the A-IoT device permanent identifier.
[0117] In a ninth example, the method of the first example, further comprising storing, in the memory, one or more of device credentials of the A-IoT device, a user of the A-IoT device, or a device status of the A-IoT device.
[0118] In a tenth example, a processor configured to perform any of the methods of the first through ninth examples.
[0119] In an eleventh example, an ambient-IoT device configured to perform any of the methods of the first through ninth examples.
[0120] In a twelfth example, a method, comprising processing, based on signaling from a first network function, a service request comprising a first temporary identifier of an ambientinternet of Things (A-IoT) device, a first random number generated by the first network function and a second random number generated by a second network function, deriving a temporary key based on a preconfigured key and the second random number generated by the second network function, and generating, for transmission to the first network function, a Medium Access Control (MAC) element comprising the first temporary identifier and the first random number generated by the first network function.
[0121] In a thirteenth example, the method of the twelfth example, further comprising generating a second temporaryAttorney Docket No. 30164 / 105502Ref. No. P72271WO1identifier for the A-IoT device based on the temporary key, the first random number generated by the first network function and the first temporary identifier for the A-IoT device.
[0122] In a fourteenth example, a processor configured to perform any of the methods of the twelfth through thirteenth examples.
[0123] In a fifteenth example, an ambient-IoT device configured to perform any of the methods of the twelfth through thirteenth examples.
[0124] In a sixteenth example, a method, comprising generating a temporary key based on a preconfigured key that is stored in the memory and a random number, wherein at least a portion of the memory is memory allocated for an application function (AF), generating a first temporary identifier for an ambient-internet of Things (A-IoT) device based on the temporary key and a permanent identifier of the A-IoT device, and generating, for transmission to a network function, a service request comprising the first temporary identifier, the temporary key and the random number.
[0125] In a seventeenth example, the method of the sixteenth example, further comprising processing, based on signaling from the network function, a service response comprising the first temporary identifier of the A-IoT device and a second random number generated by the network function and generating a second temporary identifier for the A-IoT device based on the temporary key, the second random number and the first temporary identifier for the A-IoT device.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0126] In an eighteenth example, one or more processors configured to perform any of the methods of the sixteenth through seventeenth examples.
[0127] In a nineteenth example, a network function configured to perform any of the methods of the sixteenth through seventeenth examples.
[0128] In a twentieth example, a method, comprising processing, based on signaling from a network function, a first service request comprising a first temporary identifier of an ambient- Internet of Things (A-IoT) device, a temporary key and a first random number, generating, for transmission to the A-IoT device, a second service request comprising the first temporary identifier of the A-IoT device, the first random number and a second random number, processing, based on signaling from the A-loT device, a Medium Access Control (MAC) element comprising the temporary key, the first temporary identifier and the second random number, deriving, based on the MAC element, the temporary key, authenticating the MAC element based on the temporary key derived from the MAC element and the temporary key received in the first service request and generating, for transmission to the network function, a service response comprising the first temporary identifier of the A-IoT device and the second random number.
[0129] In a twenty first example, one or more processors configured to perform the method of the twentieth example.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0130] In a twenty second example, a network function configured to perform the method of the twentieth example.
[0131] In a twenty third example, a method, comprising processing, based on signaling from a reader, a paging message comprising ambient-internet of Things (A-IoT) identification information, determining the A-IoT identification information matches at least a portion of information stored in an ambientinternet of Things (A-IoT ) device permanent identifier of an A-loT device, generating, for transmission to the reader, a response to the paging message and generating, for transmission to a network, an inventory report comprising the A-IoT device permanent identifier of the A-IoT device or an A-IoT temporary identifier of the A-IoT device.
[0132] In a twenty fourth example, the method of the twenty third example, wherein the inventory report comprises an A-IoT non-access stratum (NAS ) message.
[0133] In a twenty fifth example, the method of the twenty third example, further comprising processing, based on signaling from the network, an inventory complete message comprising the A-IoT temporary identifier of the A-IoT device.
[0134] In a twenty sixth example, the method of the twenty third example, further comprising processing, based on signaling from the reader, a command request comprising a command Type, performing a command corresponding to the command type and generating, for transmission to the reader, a command response indicating whether the command was successfully performed.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0135] In a twenty seventh example, the method of the twenty sixth example, wherein the command type comprises one of read, write or disable.
[0136] In a twenty eighth example, the method of the twenty seventh example, wherein, when the command type is disable, the method skips responding to any further paging messages from the reader.
[0137] In a twenty ninth example, a processor configured to perform any of the methods of the twenty third through twenty eighth examples.
[0138] In a thirtieth example, an ambient-IoT device configured to perform any of the methods of the twenty third through twenty eighth examples.
[0139] In a thirty first example, a method, comprising processing, based on signaling from a network function, an inventory request for one or more ambient- Internet of Things (A-loT ) devices, the inventory request comprising one or more of an identification of an application function (AF) that generated the inventory request, external target area information, information about the one or more A-IoT devices, a number of the one or more A-IoT devices, whether location information is requested as part of the inventory request or a service operation request, determining the AF that generated the inventory request is authorized to receive results of the inventory request and generating, for transmission to the network function, an indication that the AF that generated theAttorney Docket No. 30164 / 105502Ref. No. P72271WO1inventory request is authorized to receive the results of the inventory request.
[0140] In a thirty second example, the method of the thirty first example, further comprising determining a reader to which the inventory request is to be sent and forwarding the inventory request to the determined reader.
[0141] In a thirty third example, the method of the thirty second example, wherein the method determines the reader based on locally stored A-IoT device related information for the one or more A-IoT devices, wherein the locally stored A-IoT device related information comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
[0142] In a thirty fourth example, the method of the thirty second example, wherein, to determine the reader, the method, further comprises retrieving A-IoT device profile data for the one or more A-IoT devices from an A-IoT Data Management (ADM) network function, wherein the A-IoT device profile data comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
[0143] In a thirty fifth example, the method of the thirty second example, further comprising processing, based on signaling from the one or more A-IoT devices, an inventory report comprising an A-IoT device permanent identifier or an A-loT temporary identifier of the one or more A-IoT devices, validating the inventory report based on the A-IoT deviceAttorney Docket No. 30164 / 105502Ref. No. P72271WO1permanent identifier and locally stored A-IoT device related information for the one or more A-IoT devices or A-IoT device profile data for the one or more A-IoT devices retrieved from an A-IoT Data Management (ADM) and generating, for transmission to the one or more A-IoT devices, an inventory complete message comprising an A-IoT temporary identifier for each of the one more A-IoT devices that sent a validated inventory report.
[0144] In a thirty sixth example, the method of the thirty fifth example, further comprising generating, for transmission to the network function, an inventory notify message comprising an indication of the A-IoT device permanent identifier of each of the one more A-IoT devices that sent a validated inventory report.
[0145] In a thirty seventh example, the method of the thirty sixth example, wherein the inventory notify message further comprises location information when location information is reguested in the inventory reguest and a location of the reader is configured.
[0146] In a thirty eighth example, the method of the thirty first example, wherein the inventory request comprises a group inventory request or a single device inventory request, wherein the method further comprises generating filtering information to identify a subset of the one or more A-IoT devices to be inventoried, wherein the filtering information comprises a mask or a group identifier, wherein the mask comprises A-IoT device information for the subset, or wherein the group identifier corresponds to a group identifier information included in A-IoT device permanent identifiers of the subset.Attorney Docket No. 30164 / 105502Ref. No. P72271WO1
[0147] In a thirty ninth example, one or more processors configured to perform any of the methods of the thirty first through thirty eighth examples.
[0148] In a fortieth example, a network function configured to perform any of the methods of the thirty first through thirty eighth examples.
[0149] In a forty first example, a method comprising processing, based on signaling from a network function, a command request for one or more ambient-Internet of Things (A-IoT) devices, the command request comprising a command type to be performed by the one or more A-IoT devices and an application function (AF) that generated the command request, wherein the command type comprises one of read, write or disable, determining the AF that generated the command request is authorized to invoke the command request for the one or more A-loT devices and generating, for transmission to the network function, an indication that the AF that generated the command request is authorized to invoke the command request for the one or more A-IoT devices.
[0150] In a forty second example, the method of the forty first example, further comprising determining a reader to which the command request is to be sent.
[0151] In a forty third example, the method of the forty second example, the reader is determined based on locally stored A-IoT device related information for the one or more A-IoT devices, wherein the locally stored A-IoT device relatedAttorney Docket No. 30164 / 105502Ref. No. P72271WO1information comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
[0152] In a forty fourth example, the method of the forty second example, wherein, to determine the reader, the method further comprises retrieving A-IoT device profile data for the one or more A-IoT devices from an A-IoT Data Management (ADM) network function, wherein the A-IoT device profile data comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
[0153] In a forty fifth example, the method of the forty second example, further comprising determining, for each of the one or more A-IoT devices, whether a successful inventory response has been received, for each of the one or more A-IoT devices from which the successful inventory response has been received, sending a command request message to the determined reader and processing, based on signaling from the reader, a command response indicating whether the command has been successfully performed by the one or more A-IoT devices.
[0154] In a forty sixth example, the method of the forty fifth example, wherein the command request message is one of sent directly to the selected reader or as an A-IoT transfer container via an access and mobility function (AMF).
[0155] In a forty seventh example, the method of the forty fifth example, further comprising generating, for transmission to the network function, a command notify message comprising anAttorney Docket No. 30164 / 105502Ref. No. P72271WO1indication of the A-IoT device permanent identifier of each of the one or more A-IoT devices that successfully performed the command.
[0156] In a forty eighth example, one or more processors configured to perform any of the methods of the forty first through forty seventh examples.
[0157] In a forty ninth example, a network function configured to perform any of the methods of the forty first through forty seventh examples.
[0158] Those skilled in the art will understand that the above-described example embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An example hardware platform for implementing the example embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc. The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.
[0159] Although this application described various embodiments each having different features in various combinations, those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not specifically disclaimed or which is not functionally or logicallyAttorney Docket No. 30164 / 105502Ref. No. P72271WO1inconsistent with the operation of the device or the stated functions of the disclosed embodiments.
[0160] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
[0161] It will be apparent to those skilled in the art that various modifications may be made in the present disclosure, without departing from the spirit or the scope of the disclosure. Thus, it is intended that the present disclosure cover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent.
Claims
Attorney Docket No. 30164 / 105502Ref. No. P72271WO1What is claimed:
1. An apparatus comprising processing circuitry coupled to memory, the processing circuitry configured to:process, based on signaling from a reader, a paging message comprising ambient- Internet of Things (A-IoT) identification information;determine the A-IoT identification information matches at least a portion of information stored in an ambient-internet of Things (A-IoT ) device permanent identifier of an A-IoT device; generate, for transmission to the reader, a response to the paging message; andgenerate, for transmission to a network, an inventory report comprising the A-IoT device permanent identifier of the A-IoT device or an A-IoT temporary identifier of the A-IoT device.
2. The apparatus of claim 1, wherein the inventory report comprises an A-IoT non-access stratum (NAS ) message.
3. The apparatus of claim 1, wherein the processing circuitry is further configured to:process, based on signaling from the network, an inventory complete message comprising the A-IoT temporary identifier of the A-IoT device.
4. The apparatus of claim 1, wherein the processing circuitry is further configured to:process, based on signaling from the reader, a command request comprising a command Type;perform a command corresponding to the command type; andAttorney Docket No. 30164 / 105502Ref. No. P72271WO1generate, for transmission to the reader, a command response indicating whether the command was successfully performed.
5. The apparatus of claim 4, wherein the command type comprises one of read, write or disable.
6. The apparatus of claim 5, wherein, when the command type is disable, the processing circuitry skips responding to any further paging messages from the reader.
7. An apparatus comprising processing circuitry coupled to memory, the processing circuitry configured to:process, based on signaling from a network function, an inventory request for one or more ambient-Internet of Things (A-IoT) devices, the inventory request comprising one or more of an identification of an application function (AF) that generated the inventory request, external target area information, information about the one or more A-IoT devices, a number of the one or more A-IoT devices, whether location information is requested as part of the inventory request or a service operation request;determine the AF that generated the inventory request is authorized to receive results of the inventory request; and generate, for transmission to the network function, an indication that the AF that generated the inventory request is authorized to receive the results of the inventory request.
8. The apparatus of claim 7, wherein the processing circuitry is further configured to:Attorney Docket No. 30164 / 105502Ref. No. P72271WO1determine a reader to which the inventory request is to be sent; andforward the inventory request to the determined reader.
9. The apparatus of claim 8, wherein the processing circuitry determines the reader based on locally stored A-IoT device related information for the one or more A-IoT devices, wherein the locally stored A-IoT device related information comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
10. The apparatus of claim 8, wherein, to determine the reader, the processing circuitry is configured to:retrieve A-IoT device profile data for the one or more A-IoT devices from an A-IoT Data Management (ADM) network function, wherein the A-IoT device profile data comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
11. The apparatus of claim 8, wherein the processing circuitry is further configured to:process, based on signaling from the one or more A-IoT devices, an inventory report comprising an A-IoT device permanent identifier or an A-IoT temporary identifier of the one or more A-IoT devices;validate the inventory report based on the A-IoT device permanent identifier and locally stored A-IoT device related information for the one or more A-IoT devices or A-IoT deviceAttorney Docket No. 30164 / 105502Ref. No. P72271WO1profile data for the one or more A-IoT devices retrieved from an A-IoT Data Management (ADM); andgenerate, for transmission to the one or more A-IoT devices, an inventory complete message comprising an A-IoT temporary identifier for each of the one more A-IoT devices that sent a validated inventory report.
12. The apparatus of claim 11, wherein the processing circuitry is further configured to:generate, for transmission to the network function, an inventory notify message comprising an indication of the A-IoT device permanent identifier of each of the one more A-IoT devices that sent a validated inventory report.
13. The apparatus of claim 12, wherein the inventory notify message further comprises location information when location information is reguested in the inventory request and a location of the reader is configured.
14. The apparatus of claim 7, wherein the inventory request comprises a group inventory request or a single device inventory request, wherein the processing circuitry is further configured to:generate filtering information to identify a subset of the one or more A-IoT devices to be inventoried, wherein the filtering information comprises a mask or a group identifier, wherein the mask comprises A-IoT device information for the subset, orwherein the group identifier corresponds to a group identifier information included in A-IoT device permanent identifiers of the subset.Attorney Docket No. 30164 / 105502Ref. No. P72271WO115. An apparatus comprising processing circuitry coupled to memory, the processing circuitry configured to:process, based on signaling from a network function, a command request for one or more ambient-Internet of Things (A-IoT) devices, the command request comprising a command type to be performed by the one or more A-IoT devices and an application function (AF) that generated the command request, wherein the command type comprises one of read, write or disable;determine the AF that generated the command request is authorized to invoke the command request for the one or more A-IoT devices; andgenerate, for transmission to the network function, an indication that the AF that generated the command request is authorized to invoke the command request for the one or more A-IoT devices.
16. The apparatus of claim 15, wherein the processing circuitry is further configured to:determine a reader to which the command request is to be sent.
17. The apparatus of claim 16, wherein the processing circuitry determines the reader based on locally stored A-IoT device related information for the one or more A-IoT devices, wherein the locally stored A-IoT device related information comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.Attorney Docket No. 30164 / 105502Ref. No. P72271WO118. The apparatus of claim 16, wherein, to determine the reader, the processing circuitry is configured to:retrieve A-IoT device profile data for the one or more A-IoT devices from an A-IoT Data Management (ADM) network function, wherein the A-IoT device profile data comprises an A-IoT device permanent identifier of the one or more A-IoT devices and a last known reader information of the one or more A-IoT devices.
19. The apparatus of claim 16, wherein the processing circuitry is further configured to:determine, for each of the one or more A-IoT devices, whether a successful inventory response has been received;for each of the one or more A-IoT devices from which the successful inventory response has been received, send a command request message to the determined reader; andprocess, based on signaling from the reader, a command response indicating whether the command has been successfully performed by the one or more A-IoT devices.
20. The apparatus of claim 19, wherein the processing circuitry is further configured to:generate, for transmission to the network function, a command notify message comprising an indication of the A-IoT device permanent identifier of each of the one or more A-IoT devices that successfully performed the command.
