Method and system for utilizing carrier wave infrastructure depending on memory type used to store temporary device id for ambient internet of thing (IOT) devices

Abstract

A method, system and apparatus are disclosed. In one embodiment, a method implemented in a device that is configured to communicate with a reader device, is provided. The method includes receiving device credentials for the device, determining, based on network parameters, whether to save the device credentials in volatile memory (V) or in non-volatile memory (NVM), and indicating to the reader device whether the device credentials are saved in VM or in NVM.

Description

[0001] METHOD AND SYSTEM FOR UTILIZING CARRIER WAVE INFRASTRUCTURE DEPENDING ON MEMORY TYPE USED TO STORE TEMPORARY DEVICE ID FOR AMBIENT INTERNET OF THING (loT) DEVICES FIELD

[0002] The present disclosure relates to wireless communications, and in particular, to methods, systems, and apparatuses for efficiently utilizing network infrastructure depending on which memory type is used by one or more A-IoT devices.

[0003] BACKGROUND

[0004] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0005] In 3 GPP, a study on Zero-Energy Internet of Things (ZE-IoT) was started in Release 18, and is referred to as “Ambient loT” (RP-222685) in 3GPP. The resulting 3GPP study item technical report can be found in TR 38.848. In Release 19, the work continued with a study in Radio Access Network (RAN) working groups (RP-240826) for which the outcome can be found in technical report TR 38.769. 3GPP agreed to continue in the last part of Release 19 with normative work (RP -243326) to specify a limited solution:

[0006] • Indoor inventory, indoor command only

[0007] • Backscattering Device Type 1 only

[0008] • D1T1-B (micro base station (BS) indoor; device indoor) only

[0009] • Carrier Wave (CW) outside topology

[0010] • Reader to Device (R2D) in Downlink (DL) spectrum; Device to Reader (D2R) and CW in UL spectrum

[0011] That is, the only services supported in Release 19 are “inventory” (reporting of the device identified to the network) and “command” (transmitting a small payload to the device). Further, the deployment scenario supported are indoor devices which receive carrier wave (CW) transmissions for network nodes and the reflected signals are receivedby indoor micro base stations (in Frequency Division Duplexing (FDD) uplink spectrum). For downlink, direct transmission from the indoor micro base station to the device is supported (in FDD downlink spectrum).

[0012] FIG. 1 is a diagram of an example Ambient-IoT communication network.

[0013] As shown in FIG. 1, “A” indicates uplink signals and “B” indicates the downlink signal.

[0014] Functional and protocol simplifications for Ambient loT

[0015] For Ambient loT (A-IoT), 3GPP will target an loT segment below the existing cellular loT technologies (e.g., Narrow Band Internet of Things (NB-IoT)), with significantly lower energy consumption and device complexity / cost. This requires simplifications in physical layer design, and the higher layer (L2 / L3) design will also be much more lightweight with a minimal set of functionalities. For Random Access and multiple access devices, the Release 19 scope is limited to the following:

[0016] - A-IoT Random access, including re-access for failure handling. Contentionbased and contention-free cases are supported. For the contention-based random access, only Solution 1 (3-step only) is included (unless RAN2 decides to use Solution 3 (unified solution) by RAN2#129).

[0017] Contention-based Random Access Types:

[0018] A 2-step contention-based random access (CBRA) includes:

[0019] • 2 messages / steps sequence

[0020] • Message 2 can be optional (at least for study)

[0021] • Device transmit collision resolution (CR ID, e.g., RN16) along with data in 1st message

[0022] A 3-step CBRA includes:

[0023] • 4 messages / steps sequence

[0024] • Message 4 can be optional (at least for study)

[0025] • Device transmit collision resolution (CR ID, e.g., RN16) in 1st message and data in subsequent message only if the 1st message is acknowledged

[0026] A 4-step Contention Free Random Access (CFRA) (Built similar / over CBRA) includes:

[0027] • Methods

[0028] • Using 3-step CBRA for single device but without Msgl / 2

[0029] • The paging message triggers CBRA targets single device

[0030] • Other methods can be based on ID to address resource utilization locally, e.g.,• AS ID (for further study (FFS))

[0031] . Other ID (FFS)

[0032] FIG. 2 is a diagram illustrating a 2-step contention-based Random Access. In FIG.

[0033] 2, a device sends a Msgl (including a CR ID and data (device ID)) to the reader. The reader then sends Msg2 (including at least the CR ID) to the device.

[0034] FIG. 3 is a diagram illustrating a 3-step and 4-step contention-based Random Access. In FIG. 4, the device sends a Msgl (including CR ID) to the reader. The reader then sends Msg2 (including CR ID echo) to the device. The device sends Msg3 (including at least data (device ID)) to the reader. The reader sends Msg4 (including Feedback) to the device.

[0035] Memory discussions in AIOT Radio Layer 1 (RANI) Group (referred to as RANI), System Aspects 2 (SA2) Group (referred to as SA2), System Aspects 3 (SA3)

[0036] Memory discussion in SA2, LS to RANI and response

[0037] In S2-2407231, System Aspects 2 (SA2) asks Radio Layer 1 (RANI) about nonvolatile memory aspects of Ambient loT device:

[0038] SA2 has discussed different aspects with respect to non-volatile memory:

[0039] whether or not an Ambient loT device can incorporate a non-volatile memory in the device design, i.e., include anon-volatile memory in the Bill-of-Materials (BoM).

[0040] whether an Ambient loT device will be able to update its non-volatile memory based on its energy status and energy storage capabilities at some point after receiving a trigger from the Reader.

[0041] SA2 has not reached any common understanding. While there is no consensus in SA2 whether it is in RANI scope to determine the devices' level of capability to support non-volatile memory; SA2 would like to ask the following question to RANI :

[0042] Question 5: SA2 would like to ask RANI if RANI can provide feedback on the non-volatile memory aspects listed above.

[0043] In R1 -2407364, RANI provided the reply to SA2:

[0044] Whether or not an Ambient loT device can incorporate a non-volatile memory in the device design, i.e., include anon-volatile memory in the Bill-of-Materials (BoM).

[0045] RANI is studying several different A-IoT device architectures, which all are assumed to include a memory block described as follows:

[0046] • Memory can include two types of memory: 1) Non-Volatile Memory (NVM) such as EEPROM for permanently storing device ID, etc., and 2)registers for temporarily keeping any information required for its operation only while energy is available in energy storage.

[0047] Therefore, it can be assumed that an A-IoT device can incorporate an NVM in the device design, i.e., include an NVM in the BoM.

[0048] Whether an Ambient loT device will be able to update its non-volatile memory based on its energy status and energy storage capabilities at some point after receiving a trigger from the Reader

[0049] RANI would like to provide the following answer:

[0050] An Ambient loT device will be able to update its non-volatile memory at some point after receiving a trigger from the Reader. Writing may not always be possible at all times.

[0051] The power consumption during writing to the NVM is higher than during reading.

[0052] RANI thinks that frequent or recurring writing to the NVM should be avoided.

[0053] RANI has not discussed energy status and energy storage capabilities in relation to an Ambient loT device ability to update its non-volatile memory.

[0054] For privacy purposes at the A-IoT device side, a temporary ID is agreed (in 3 GPP) to be utilized. The temporary ID is assigned by the Core Network (CN) with an aim to bypass the use of the original ID over the air between the A-IoT device and the CN due to security concerns. 3GPP SA3 has not made agreements on whether a non-volatile memory (NVM) or a volatile memory (VM) should be used to store this temporary ID. Each approach has its advantages and disadvantages.

[0055] According to the reply Liaison Statement (LS) from RANI, both options are feasible.

[0056] If the temporary ID is stored or written in an NVM, the A-IoT device needs a large amount of energy for writing the temporary ID but, once written in NVM, the ID is safe even if the A-IoT device runs out of energy (e.g., storage capacitor ran out, CW illumination is no longer available, etc.)

[0057] If the temporary ID is stored or written in a VM and / or register, the A-IoT device needs comparatively less energy than a NVM to write. However, a disadvantage is that maintaining the ID or parameters in a VM requires constant energy to keep the VM powered up, and if the device runs out of energy or the RF power link charging the devicegets disconnected, the device will lose the temporary ID as VM content will be erased. As a result, the A-IoT device will lose its communication link and will need to wait for the next paging / access round from the reader.

[0058] However, given that an A-IoT device will potentially have two plausible methods of storing a temporary ID, there remain distinct problems associated with each method.

[0059] SUMMARY

[0060] Some embodiments advantageously provide methods, systems, and apparatuses for efficiently utilizing network infrastructure depending on which memory type is used to store device credentials for A-IoT devices.

[0061] Some embodiments relate to a controlling device, such as a User Equipment (UE) (as a reader), or a network node (i. e. , a gNB, as a reader) optimize network behavior subject to a device’s utilization of memory type - NVM or VM, for storing device credentials.

[0062] In some embodiments, subject to the memory type chosen, the network utilizes CW power and illumination accordingly as these memory types have different requirements pertinent to CW illumination and harvesting. For example, if a device intends to save credentials in VM, the network ensures constant CW on the device, otherwise, in case of NVM utilization, the network can switch off or reduce power of the CW.

[0063] In another embodiment, solutions are provided impacting specifications which can assist in network implementation of CW utilization subject to memory type, such as when the device saves a temporary ID in either memory type). For example, a device can provide feedback to the network or include capabilities regarding its intention on storing device credentials in which memory type, and accordingly implement CW illumination and configuration.

[0064] According to one aspect of the present disclosure, a method implemented in a device that is configured to communicate with a reader device is provided. The method includes receiving device credentials for the device, determining, based on network parameters, whether to save the device credentials in volatile memory (VM) or in nonvolatile memory (NVM), and indicating to the reader device whether the device credentials are saved in VM or in NVM.In some embodiments of this aspect, the method further includes splitting the device credentials into two partitions, wherein a first partition is stored in the NVM and a second partition is stored in the VM.

[0065] In some embodiments, if the device determines to save the device credentials in NVM, the method further includes reducing at least one of energy consumption and processing to divert energy resources towards saving the device credentials in NVM.

[0066] In some embodiments, the network parameters include a carrier wave (CW) illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, the method further includes continuing to save the device credentials in VM.

[0067] In some embodiments, if the CW illumination time period is one of reduced or powered off, the method further includes saving the device credentials in NVM.

[0068] In some embodiments, if the device determines to save the device credentials in VM, the method further includes selecting a smaller occasion number in an access / paging round containing a number of Contention-Based Random Access, CBRA, transmissions.

[0069] In some embodiments, if the device determines to save the device credentials in NVM, the method further includes selecting any occasion number in an access or paging round for its transmissions.

[0070] In some embodiments, if the device determines to save the device credentials in VM, the method further includes selecting a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access, FDMA, to maintain its energy for storing the device credentials in the VM.

[0071] In some embodiments, the device is an ambient internet of things (A-IoT) device. In some embodiments, the device credentials include a temporary identification (temp ID) of the device.

[0072] According to another aspect of the present disclosure, a method implemented in a reader device that is configured to communicate with a device, is provided. The method includes receiving from the device an indication of a type of memory the device uses for storing device credentials, and configuring network energy utilization based on the type of memory the device uses for storing device credentials.

[0073] According to an embodiment of this aspect, the method further includes determining whether the device stores its device credentials in non-volatile memory (NVM) or volatile memory (VM), and in response to determining that the device stores its device credentials in NVM, reducing carrier wave (CW) illumination time.In some embodiments, if the reader device determines that the device stores its device credentials in VM, the method further includes one of maintaining CW power at a minimum threshold level and continuing to power the device to enable the device to maintain storage of the device credentials in VM.

[0074] In some embodiments, the method further includes determining that the device stores its device credentials in VM, and based on the determination, providing resources to the device earlier than other devices that store their device credentials in NVM.

[0075] In some embodiments, the reader device is one of a network node, a user equipment, UE, and an intermediate UE.

[0076] In some embodiments, the device credentials include a temporary identification (temp ID) of the device.

[0077] According to another aspect of the present disclosure, a device configured to communicate with a reader device, is provided. The device is configured to receive device credentials for the device, determine, based on network parameters, whether to save the device credentials in volatile memory (VM) or in non-volatile memory (NVM), and indicate to the reader device whether the device credentials are saved in VM or in NVM.

[0078] In some embodiments, the device is further configured to split the device credentials into two partitions, wherein a first partition is stored in the NVM and a second partition is stored in the VM.

[0079] In some embodiments, if the device determines to save the device credentials in NVM, the device is further configured to reduce at least one of energy consumption and processing to divert energy resources towards saving the device credentials in NVM.

[0080] In some embodiments, the network parameters include a carrier wave (CW) illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, the device is further configured to continue to save the device credentials in VM.

[0081] In some embodiments, if the CW illumination time period is one of reduced or powered off, the device is further configured to save the device credentials in NVM.

[0082] In some embodiments, if the device determines to save the device credentials in VM, the device is further configured to select a smaller occasion number in an access / paging round containing a number of Contention-Based Random Access (CBRA) transmissions.In some embodiments, if the device determines to save the device credentials in NVM, the device is further configured to select any occasion number in an access or paging round for its transmissions.

[0083] In some embodiments, if the device determines to save the device credentials in VM, the device is further configured to select a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access (FDMA) to maintain its energy for storing the device credentials in the VM.

[0084] In some embodiments, the device is an ambient internet of things (A-IoT) device. In some embodiments, the device credentials include a temporary identification (temp ID) of the device.

[0085] According to another aspect of the present disclosure, a reader device configured to communicate with a device, is provided. The reader device is configured to receive from the device an indication of a type of memory the device uses for storing device credentials, and configuring network energy utilization based on the type of memory the device uses for storing device credentials.

[0086] According to an embodiment of this aspect, the reader device is further configured to determine whether the device stores its device credentials in non-volatile memory (NVM) or volatile memory (VM), and in response to determining that the device stores its device credentials in NVM, reduce carrier wave (CW) illumination time.

[0087] In some embodiments, if the reader device determines that the device stores its device credentials in VM, the reader device is further configured to one of maintain CW power at a minimum threshold level and continue powering the device to enable the device to maintain storage of the device credentials in VM.

[0088] In some embodiments, the reader device is further configured to determine that the device stores its device credentials in VM, and based on the determination, provide resources to the device earlier than other devices that store their device credentials in NVM.

[0089] In some embodiments, the reader device is one of a network node, a user equipment, UE, and an intermediate UE.

[0090] In some embodiments, the device credentials include a temporary identification (temp ID) of the device.BRIEF DESCRIPTION OF THE DRAWINGS

[0091] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0092] FIG. 1 is a diagram of an example Ambient-IoT communication network;

[0093] FIG. 2 is a diagram illustrating a 2-step contention-based Random Access;

[0094] FIG. 3 is a diagram illustrating a 3-step and 4-step contention-based Random Access;

[0095] FIG. 4 is a schematic diagram of an example architecture illustrating a communication system according to principles disclosed herein;

[0096] FIG. 5 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0097] FIG. 6 is a block diagram of a reader device and device according some embodiments of the present disclosure;

[0098] FIG. 7 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0099] FIG. 8 is a flowchart of an example process in a reader device according to some embodiments of the present disclosure;

[0100] FIG. 9 is a flowchart of another example process in a reader device according to some embodiments of the present disclosure;

[0101] FIG. 10 is a flowchart of an example process in a device according to some embodiments of the present disclosure;

[0102] FIG. 11 is a flowchart of another example process in a device according to some embodiments of the present disclosure;

[0103] FIG. 12 illustrates an example of a first topology for Ambient-IoT device communication according to some embodiments of the present disclosure;

[0104] FIG. 13 illustrates an example of a second topology for Ambient-IoT device communication according to some embodiments of the present disclosure;

[0105] FIG. 14 illustrates an example of a third topology for Ambient-IoT device communication according to some embodiments of the present disclosure;

[0106] FIG. 15 illustrates an example of a fourth topology for Ambient-IoT device communication according to some embodiments of the present disclosure; andFIG. 16 illustrates an example of devices indicating capability information for storing temp ID in a specific memory type.

[0107] DETAILED DESCRIPTION

[0108] In accordance with embodiments described herein, subject to the memory type used by a device for the storage of device credentials, such as, for example, a device’s temporary ID (temp ID), a network can utilize CW infrastructure accordingly.

[0109] Some embodiments achieve one or more of the following advantages:

[0110] If the reader knows where devices intend to store temporary IDs, the network can efficiently utilize CW infrastructure. For example, if devices save IDs in NVM, then during periods of no communication, the network can switch off CW and save energy:

[0111] • By not transmitting CW; and

[0112] • By not keeping CW nodes switched on.

[0113] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to efficiently utilizing network infrastructure depending on which memory type is used such as by, for example, the A-IoT device. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0114] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0115] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

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

[0117] The term RAN node is used which can be a network node or a UE. The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), integrated access backhaul (IAB) node, radio network controller (RNC), central unit (e.g., in a gNB), Distributed Unit (e.g., in a gNB), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, repeater, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, transmission reception point (TRP), Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, operating support system (OSS) node, Operations, Administration and Maintenance (O&M) node, Enhanced-Serving Mobile Location Center (E-SMLC) node, Minimization of Drive Test (MDT) node, etc.), an external node (e.g., 3rd party node, anode external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, location measurement unit (LMU), Baseband Unit, Centralized Baseband, Cloud-RAN (C-RAN), an element management system (EMS), etc. Thenetwork node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0118] In particular, in an A-IoT scenario, the RAN nodes comprise an intermediate node / UE (e.g., relay UE, IAB, repeater etc.) and assisting node / UE (e.g., relay UE, IAB, repeater etc.).

[0119] As used herein, the terms “polling,” “poll” and “paging,” “page,” “inventory,” “query” and “interrogate” are used to represent one or more than one signal transmitted by a network node broadcast wise or specially to a dedicated UE. The purpose of the signal is to facilitate / serve / manage / command one or more than one UE to synchronize to the network node (DL / UL synchronize to a reference time / frame / symbol, or synchronize to one or more than one signal which the UE receives from the network node, or synchronize based on a pre-defined rule), receive DL data, respond and transmit UL data correctly in intended resources. The content of such signal may be a particular reference signal or a signal carrying control information and / or data. Such signal may be transmitted periodically or a periodically configured by the network node.

[0120] As used herein, the terms “A-IoT UE,” “A-IoT device,” “device,” or “UE” are used interchangeably without losing the meaning of the term.

[0121] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0122] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).The inventory or inventory procedure described herein may correspond to a device that is engaged or executing:

[0123] • Inventory

[0124] • Command

[0125] • Inventory plus command.

[0126] As used herein, the plurality of classifications, “related procedure / transmissions / use case, may be referred to by the single term “inventory.” As used herein, the term temporary ID (or temp ID) may refer to a temporary identifier allocated by the Core Network (CN) towards the A-IoT device, after successful authentication of the device. It can be similar to 5G-GUTI for UEs in NR, or based on a new method, such as an encrypted form of root or permanent or original ID. The temporary ID or part of the temporary ID (similar as 5G-S-TMSI) is used in an A-IoT paging request to page the device.

[0127] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0128] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0129] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in thecontext of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0130] Some embodiments are directed to efficiently utilizing network infrastructure depending on which memory type is used to store device credentials for A-IoT devices.

[0131] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 4 a schematic diagram of a communication system 2, according to one or more embodiments. Communication system 2 includes at least one reader device 4 (also referred to as reader 4 or reader device 4) and a plurality of devices 6a-6n (referred to collectively as device 6). In one or more embodiments, device 6 is an A-IoT device. In one or more embodiments, reader device 4 and device 6 may communicate using network resources.

[0132] In one or more embodiments, reader device 4 may include utilization unit 8 that is configured to perform one or more reader device 4 functions described herein. In one or more embodiments, device 6 may include credential unit 9 that is configured to perform one or more device 6 functions described herein.

[0133] FIG. 5 is a schematic diagram of an example communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more network nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first UE 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as UEs 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0134] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP radio access technologies (RAT), such as LTEor NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g., 4G, 5G and 6G 3GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0135] Also, it is contemplated that UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN, a gNB for NR / NG-RAN (i. e. , being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.

[0136] The network node 16 may be composed of multiple distinct network entities (e.g., aNodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 16.In one or more examples, reader device 4 may be implemented by network node 16 (network node 16a) or a UE 22. In one or more embodiments, device 6 may be implemented by a UE 22 (e.g., UE 22a).

[0137] Example implementations, in accordance with an embodiment, of device 6 and reader device 4 discussed in the preceding paragraphs will now be described with reference to FIG. 6.

[0138] The communication system 2 includes a reader device 4 provided in a communication system 2 and including hardware 28 enabling it to communicate with the device 6. The hardware 28 may include a communication interface 29 comprising a radio interface 30 communicating with device 6. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0139] In the embodiment shown, the hardware 28 of reader device 4 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0140] Thus, the reader device 4 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the reader device 4 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by reader device 4. Processor 38 corresponds to one or more processors 38 for performing reader 4 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causesthe processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to reader device 4. For example, processing circuitry 36 of reader device 4 may include utilization unit 8, which is configured to perform one or more reader device 4 functions as described herein.

[0141] In certain alternative embodiments, reader device 4 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 36 includes radio front-end circuitry and is connected to the antenna 34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / or transceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).

[0142] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the reader device 4 and connectable to reader device 4 through one or more interfaces or ports.

[0143] The communication system 2 further includes device 6 already referred to. The device 6 may have hardware 44 that may include a radio interface 46 for communicating with reader device 4. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0144] Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA),GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0145] The hardware 44 of device 6 may optionally include processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0146] Thus, the device 6 may optionally comprise software 56, which is stored in, for example, memory 54 at device 6, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by device 6. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the device 6.

[0147] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by device 6. The processor 52 corresponds to one or more processors 52 for performing device 6 functions described herein. The device 6 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to device 6. For example, the processing circuitry 50 of device 6 may include credential unit 9 which is configured to perform one or more device 6 functions described herein.In some embodiments, the inner workings of the reader device 4 and device 6 may be as shown in FIG. 6 and independently, the surrounding network topology may be that of FIG. 4.

[0148] The wireless connection 32 between the device 6 and the reader device 4 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0149] Although FIGS. 4 and 6 show various “units” such as utilization unit 8 and credential unit 9 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0150] FIG. 7 is another example of a communication system 10 according to some embodiments. For example, reader device 4 may be implemented in AP 60 or STA 62 while device 6 may be implemented in STA 62. As used herein, the communication system 10 of FIG. 7 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG. 7 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 1 and 2. In other words, in some embodiment, STA 62 is a UE 22.

[0151] Further, stations 62 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0152] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0153] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 7 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.

[0154] FIG. 8 is a flowchart of an example process in a reader device 4 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of reader device 4 such as by one or more of processing circuitry 36 (including the utilization unit 8), processor 38, and / or radio interface 30. Reader device 4 is configured to receive (Block SI 00) from device 6 an indication of a type of memory the device 6 uses for storing device credentials. Reader device 4 is further configured to utilize (Block SI 02) network infrastructure based on the type of memory the device 6 uses for storing device credentials.

[0155] According to one or more embodiments, reader device 4 is further configured to determine whether the device 6 stores its device credentials in NVM or VM, and in response to determining that the device 6 stores its device credentials in NVM, reduce carrier wave (CW) illumination time.

[0156] According to one or more embodiments, if the reader device 4 determines that the device 6 stores its device credentials in VM, the reader device 4 is further configured toone of maintain CW power at a minimum threshold level and continue illuminating the device 6 so that the device 6 can maintain storage of the device credentials in VM.

[0157] According to one or more embodiments, reader device 4 is further configured to determine that the device 6 stores its device credentials in V, and based on the determination, provide resources to the device 6 earlier than other devices that store their device credentials in NVM.

[0158] According to one or more embodiments, reader device 4 is one of a network node 16, UE 22, and an intermediate UE 22.

[0159] According to one or more embodiments, the device credentials include a temporary identification (temp ID) of device 6.

[0160] According to one or more embodiments, reader device 4 is further configured to, determine whether the device 6 stores its device credentials in non-volatile memory (NVM) or volatile memory (VM), and in response to determining that the device 6 stores its device credentials in NVM, reduce carrier wave (CW) illumination time.

[0161] FIG. 9 is a flowchart of another example process in a reader device 4 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of reader device 4 such as by one or more of processing circuitry 36 (including the utilization unit 8), processor 38, and / or radio interface 30. Reader device 4 is configured to receive (Block SI 04) from the device 6 an indication of a type of memory the device 6 uses for storing device credentials. Reader device 4 is further configured to configure (Block SI 06) network energy utilization based on the type of memory the device 6 uses for storing device credentials.

[0162] According to one or more embodiments, reader device 4 is further configured to determine whether the device 6 stores its device credentials in non-volatile memory (NVM) or volatile memory (VM), and in response to determining that the device 6 stores its device credentials in NVM, reducing carrier wave (CW) illumination time.

[0163] According to one or more embodiments, if the reader device 4 determines that the device 6 stores its device credentials in VM, reader device 4 is further configured to one of maintain CW power at a minimum threshold level and continue powering the device 6 to enable the device 6 to maintain storage of the device credentials in VM.

[0164] According to one or more embodiments, reader device 4 is further configured to determine that the device 6 stores its device credentials in VM and based on the determination, provide resources to the device 6 earlier than other devices that store their device credentials in NVM.According to one or more embodiments, reader device 4 is one of a network node, a user equipment, UE, and an intermediate UE.

[0165] According to one or more embodiments, the device credentials include a temporary identification (temp ID) of the device 6.

[0166] FIG. 10 is a flowchart of an example process in device 6 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of device 6 such as by one or more of processing circuitry 50 (including the credential unit 9), processor 52, and / or radio interface 46. Device 6 is configured to receive (Block SI 08) device credentials for the device 6. Device 6 is further configured to determine (Block SI 10) whether to save the device credentials in volatile memory (VM). Device 6 is further configured to determine (Block SI 12), based on network parameters, whether to save the device credentials in non-volatile memory (NVM).

[0167] According to one or more embodiments, if device 6 determines to save the device credentials in NVM, the device 6 is further configured to reduce at least one of energy consumption and processing to divert energy resources towards saving the device credentials in NVM.

[0168] According to one or more embodiments, the network parameters include a carrier wave (CW) illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, the device 6 is further configured to continue to save the device credentials in VM.

[0169] According to one or more embodiments, the network parameters include a CW illumination time period, and if the CW illumination time period is one of reduced or powered off, the device 6 is further configured to save the device credentials in NVM.

[0170] According to one or more embodiments, if device 6 determines to save the device credentials in VM, the device 6 is further configured to select a smaller occasion number in an access or paging round for its transmissions.

[0171] According to one or more embodiments, if device 6 determines to save the device credentials in VM, the device 6 is further configured to select a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access (FDMA) to maintain its energy for storing the device credentials in the VM.

[0172] According to one or more embodiments, if device 6 determines to save the device credentials in NVM, the device 6 is further configured to select any occasion number in an access or paging round for its transmissions.According to one or more embodiments, device 6 is an A-IoT device.

[0173] According to one or more embodiments, the device credentials include a temporary identification (temp ID) of the device.

[0174] FIG. 11 is a flowchart of another example process in device 6 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of device 6 such as by one or more of processing circuitry 50 (including the credential unit 9), processor 52, and / or radio interface 46.

[0175] Device 6 is configured to receive (Block SI 14) device credentials for the device 6. Device 6 is further configured to determine (Block SI 16) based on network parameters, whether to save the device credentials in volatile memory (VM) or in non-volatile memory (NVM). Device 6 is further configured to indicate (Block SI 18) to the reader device 4 whether the device credentials are saved in VM or in NVM.

[0176] According to one or more embodiments, device 6 is further configured to split the device credentials into two partitions, wherein a first partition is stored in the NVM and a second partition is stored in the VM.

[0177] According to one or more embodiments, if device 6 determines to save the device credentials in NVM, the device 6 is further configured to reduce at least one of energy consumption and processing to divert energy resources towards saving the device credentials in NVM.

[0178] According to one or more embodiments, the network parameters include a carrier wave (CW) illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, the device 6 is further configured to continue to save the device credentials in VM.

[0179] According to one or more embodiments, if the CW illumination time period is one of reduced or powered off, the device 6 is further configured to save the device credentials in NVM.

[0180] According to one or more embodiments, if the device 6 determines to save the device credentials in VM, the device 6 is further configured to select a smaller occasion number in an access / paging round containing a number of Contention-Based Random Access (CBRA) transmissions.

[0181] According to one or more embodiments, if device 6 determines to save the device credentials in NVM, the device 6 is further configured to select any occasion number in an access or paging round for its transmissions.According to one or more embodiments, if device 6 determines to save the device credentials in VM, the device 6 is further configured to select a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access (FDMA) to maintain its energy for storing the device credentials in the VM.

[0182] According to one or more embodiments, the device 6 is an ambient internet of things (A-IoT) device.

[0183] According to one or more embodiments, the device credentials include a temporary identification (temp ID) of the device 6.

[0184] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for efficiently utilizing network infrastructure depending on which memory type is used by one or more A-IoT devices 6.

[0185] Some embodiments provide for efficiently utilizing network infrastructure depending on which memory type is used by one or more Ambient-Internet of Things (A-loT) devices. One or more reader device 4 functions described below may be performed by one or more of processing circuitry 36, processor 38, utilization unit 8, communication interface 29, etc. One or more device 6 functions described below may be performed by one or more of radio interface 46, antenna 48, processing circuitry 50, processor 52, credential unit 9, etc.

[0186] 3GPP has defined four deployment topologies for A-IoT in Rel-18. In Rel-19 SI, the scope was limited to Topology 1 and 2 and later in the Work Item (WI) phase further limited to Topology 1. However, Rel-20 is expected to include at least Topology 2 leaving the other topologies for future A-IoT studies. The four different topologies are summarized in FIGs. 12-15.

[0187] FIG. 12 is a diagram of an example Topology 1 (BS <-> Ambient loT device). In FIG. 12, an A-IoT device 6 communicates directly with a reader device 4, (e.g., network node or base station) in a bi-directional manner. The communication includes data A-IoT data and / or signaling.

[0188] FIG. 13 is a diagram of an example Topology 2 (BS <-> intermediate node <-> Ambient loT device). In FIG. 13, the A-IoT device 6 communicates bidirectionally with an intermediate node (IN) which can be a relay, IAB node, UE, repeater, etc. The IN transfers the A-IoT data and / or signaling between the reader 4 and the A-IoT device 6.FIG. 14 depicts Topology 3 (BS <-> assisting node <-> Ambient loT device <-> BS). In FIG. 14, the A-IoT device 6 transmits data / signaling to a reader 4 (e.g., network node or base station), and receives data / signaling from the assisting node or the other way around.

[0189] FIG. 15 depicts Topology 4 (UE «-> Ambient loT device). In FIG. 15, the A-IoT device 6 communicates bidirectionally with a UE 22. The communication includes A-IoT data and / or signaling.

[0190] The embodiments described below consider or assume use cases with ultra-low power devices, zero-energy devices or 3GPP A-IoT devices 6.

[0191] Some embodiments provide for efficiently utilizing network infrastructure depending on which memory type is used to store device credentials for A-IoT devices 6.

[0192] Implementation

[0193] A-IoT Device Implementation

[0194] In some embodiments, the device 6 always receives a temp ID in VM and if the device 6 intends to save this temp ID in NVM, there is a transition time, as it may take time to write the temp ID in NVM. This “transition time” can be left to device implementation. During this transition time, the device 6 may reduce energy consumption and processing for other purpose (e.g., encoding D2R messages, decoding and / or monitoring R2D transmissions), and divert the energy resources in writing the temp ID in NVM.

[0195] In some embodiments, if the network indicates CW illumination knowledge or changes the CW illumination parameters, the device 6 accordingly determines to keep the temp ID in

[0196] • VM

[0197] If the CW illumination time period is large, e.g., much larger than the estimated or expected duration of an A-IoT paging / access round, then the device 6 keeps the temp ID in VM;

[0198] • Or move it to NVM

[0199] If the CW illumination time period is reduced or the network has indicated that it will be powered off, then the device 6 moves the temp ID to NVM

[0200] During a contention-based access procedure / round, an access occasion for a device 6 starts from the time when the device 6 receives a first DL (or reader to device (R2D)) signaling indicating the start of the access occasion until the time when the device 6receives a second DL (or R2D) signaling indicating the end of the access occasion or the start of the next access occasion.

[0201] A device 6 performs re-access in case of contention resolution failure. A device 6 performs re-access or retransmission in case of data transmission failure. Re-access means that the device 6 accesses and transmits in a different access occasion from the access occasion where the device 6 has experienced failures. Retransmission means that device 6 uses the same or different resources to retransmit the data on the same access occasion in time domain.

[0202] In some embodiments, if a device 6 intends to store the temp ID in VM, then the device picks a smaller occasion number from an access / paging round (containing a number of Contention-Based Random Access (CBRA) occasions), and tries to finish with its transmissions as soon as possible. With this approach, given afterwards, the device 6 does not need to monitor subsequent R2D message, such as QueryRep (or Msgl resource indication) like signaling except for a paging message for new access or re-access. The intention is that if the device 6 waits longer for its turn to transmit, it may risk losing its ID from VM due to disruption in CW / RF power link.

[0203] In some embodiments, devices 6 storing the temp ID in the VM may also pick a frequency shift from a subset of the smallest available frequency shifts for Frequency Division Multiple Access (FDMA) to maintain its / their energy as long as possible for storing the temp ID in the VM (since smaller frequency shifts correspond to lower clock speed / frequency, and thus, lower energy consumption).

[0204] In some embodiments, if a device 6 intends to store the temp ID in NVM, then if the device 6 has enough energy and can store the temp ID in NVM, device 6 can monitor R2D messages aggressively and can persist for a longer duration in an access / paging round, such that device 6 can select any occasion number in a paging / access round for its transmission.

[0205] A-IoT RAN (Reader, network node, UE, CW node) Implementation

[0206] In one or more embodiments described herein, “network” may refer to reader device 4.

[0207] In some embodiments, if a device 6 stores temp ID in:

[0208] • NVM: Then the network (or reader 4) will reduce the CW node illumination time. The network ensures that once the ID is stored in NVM of the device 6, it can reduce power or switch off or change beamforming of a CW node as the device 6 may not need any more energy with respect to storing the ID. The network canilluminate the device 6, if the device 6 is holding other parameters in VM or monitoring transmission from the A-IoT network.

[0209] • VM / register: The network will keep CW on or keep CW power at a minimum threshold level or keep illuminating the device 6 so that the device can maintain the temp ID storage in VM.

[0210] The CW node can be hosted at or provided by the network node 16, or at / by the UE 22 or at / by a separate node controlled by the network node 16 or UE 22.

[0211] In some embodiments, if the reader 4 obtains information about a device’s temp ID storage capability, then reader 4 can allocate resources in such a manner that devices 6 storing the temp ID in VM receive resources earlier or faster for their R2D and D2R transmissions with respect to devices 6 which store the temp ID in NVM if it is suitable.

[0212] Example: a CBRA time-domain occasion has 3 FDMA occasions in the frequency domain. It is assumed that two out of three occasions have successful Msgl transmissions from device DI and device D2. Msgl contains RN16 along with each device’s indication of temp ID storage or capability information (capability Cl indicated by device DI and capability C2 indicated by device D2). Cl indicates temp ID storage in NVM and C2 indicates temp ID storage in VM. Then, in the subsequent Msg2, the reader 4 allocates resources for successive D2R and R2D transmissions for each device 6 in an order where the devices 6 with VM storage for the temp ID are prioritized over devices 6 with temp ID storage in NVM. In this example, device D2 with C2 capability is allocated resources first and the device DI with Cl capability is served later within a CBRA occasion.

[0213] As shown in FIG. 16, devices (DI and D2) indicate capability information for storing a temp ID in a specific memory type when they access CBRA occasions. In response, the devices which indicate VM for storing the temp ID are prioritized in time for the transmission in comparison to the devices which indicate NVM for storing the temp ID.

[0214] Specification Impact

[0215] A-IoT RAN specification Impact

[0216] In some embodiments, a device 6 sends to the reader 4 (or network) feedback or capability information about where it stores or intends to store the temp ID, e.g., in NVM or VM. Based on the capability or feedback indication, the network controls CW illumination (discussed in implementation embodiments above).The feedback signaling is sent after the device 6 has received the temp ID from the reader, and in response to that, the device 6 sends an ACK for reception and / or indicates where it intends to save the temp ID (as part of the feedback indication).

[0217] The capability signaling is sent after paging, or during Msgl or Msg3 transmission, indicating the device nature of the temp ID storage.

[0218] In some embodiments, the feedback information is sent as part of the energy status indication. In another embodiment, the reader / network 4 also considers the energy status information (if reported) along with the memory type related information while scheduling the device, or scheduling a charging gap.

[0219] In some embodiments, the “transition time” quantity discussed in the implementation aspect can be included in the specification (e.g., 3GPP specification), where this quantity can be sent to a reader 4 via feedback / capability signaling. This enables the readers 4 to, for example:

[0220] • Send a smaller number of R2D transmissions during the window when the device 6 is expected to receive a temp ID so that the device 6 uses less processing power to monitor and decode R2D transmission, and instead spends energy in writing the temp ID in NVM; and

[0221] • Increase power of R2D transmissions (carrying temp ID, or transmissions before or after R2D transmission carrying temp ID) or CW, so the device 6 can harvest energy for writing the temp ID in NVM.

[0222] In some embodiments, the network can indicate over a R2D message or broadcast message, regarding CW illumination related, for example:

[0223] • Reducing or increasing or changes power level; and

[0224] • Time period validity of CW illumination or related changes.

[0225] This will have an impact on device implementation regarding storing or writing of the temp ID based on CW illumination knowledge.

[0226] In some embodiments, the device 6 indicates capability related to power needed for writing IDs in the device NVM.

[0227] In some embodiments, the network configures whether the device 6 is expected to report capability information about memory storage type. In another embodiment, if no capability is reported, a default setting can be assumed in the specification for the temp ID storage (NVM or VM).

[0228] In some embodiments, the network / reader 4 configures charging gaps for the devices 6 participating in a paging / access (e.g., inventory / command) round.In one example, the reader 4 configures the charging gap for a device 6 based on the feedback received from the device 6 (i.e., it is tailored for the device).

[0229] In another example, the reader 4 configures the charging gap for a group of devices 6 based on the feedback received from the group of devices 6 (e.g., it is tailored for the devices 6 that reported using VM for temp ID storage and reported low energy in their energy status report).

[0230] In another example, the reader 4 configures the charging gap for all devices based on the feedback received from the device 6 (i.e., it is not tailored for a particular group of devices 6).

[0231] In some embodiments, the reader 4 can provide multiple configurations on utilizing frequency shifts or Frequency Division Multiplexing (FDM) resources. The reader 4 can tie the configuration utilization to device’s memory utilization for storing temp ID or device’s energy status. In one configuration indicating smaller frequency shifts, the device 6 can utilize this configuration for selecting FDM resource in CBRA occasion if it has low energy (in other words, the device 6 is using VM to store IDs). In other configurations, indicating larger frequency shifts, the device 6 can utilize this configuration for selecting FDM resources in a CBRA occasion if it does not have low energy (in other words, the device can use NVM to store IDs).

[0232] AIoT CN specification Impact

[0233] In some embodiments, if the temp ID is upcycled after some time (due to security concerns), then the validity period of each temp ID can be made subject to device capability or device decision regarding storage. The capability or decision from the device 6 needs to be communicated to the CN via the reader 4. For instance, if a device 6 saves the temp ID in NVM, which requires relatively large amounts of energy for writing, and if it is not possible for the device 6 to harvest such an amount of energy from R2D or CW illumination in a short time, then the CN considers maintaining a long validity timer for a temp ID. Alternately, devices 6 which keep the temp ID in VM, or which require relatively less amount of energy for writing the temp ID in NVM, can have a short validity timer for the temp ID and the temp ID is upcycled before or at end of validity timer. The capability of the device 6 can be configured in the CN (e.g., in device profile database, e.g., A-IoT Device Data Management, ADM or Unified Data Management, UDM). The capability of the device 6 can be communicated with the CN before the allocation of the temp ID via a Non-Access Stratum (NAS) message (e.g., Inventory Response) or via AS signaling towards A-IoT RAN and the A-IoT RAN informs the CN (e.g., over NextGeneration Application Protocol (NGAP) signaling). The capability of the device 6 or the decision of the device 6 can be communicated with the CN after the storage of the temp ID via a NAS message (e.g., Temp ID Allocate Response) or via AS signaling towards A-IoT RAN and the A-IoT RAN informs the CN.

[0234] In some embodiments, the temp ID can be split into two partitions, X+Y, where a minimum partition (for example, X) is required to be stored in the NVM and the rest (for example, Y) can be maintained in the VM. The splitting can be configured by the network via control information or a rule that is hard coded in the device as a function of its available energy. For devices 6 with no guarantee of energy availability (e.g., indicated low energy with no guarantees of continuous CW illumination), the Y part of the temp ID can be retrieved via the following options / agreements:

[0235] • The network maintains during the ongoing access round a stored mapping or hashing function to complete the Y part given X to minimize the overhead and avoid full reauthentication of the device 6; and

[0236] • Before the device loses energy and the Y partition of the temp ID, the device 6 agrees with the network on a common seed (stored in the NVM part of the device 6) to generate the Y portion of the temp ID upon waking up and resuming the session.

[0237] For example, if the temp ID is 4G or 5G GUTI, then some part of the GUTI can be stored in NVM and the remaining parts in VM. For instance, the first 48 bits which include MCC, MNC, AMF region identity, AMF set identity, AMF pointer can be written in NVM, and the remaining 32 bits containing the TMSI part can be stored in VM. For A-loT, the GUTI can be different (for example, structure, size, content and even entities, for example there can be A-IoTF instead of AMF). The ID part in VM can be upcycled or refreshed after some time, so the device 6 always has a new ID, which improves security (using the same ID over long term can pose a security risk). In other examples, the temp ID can be based on some encrypted ID (it may also contain non-encrypted part alongside). Then, the encrypted part is not suitable to write in NVM as the encrypted quantity usually changes whenever it’s transmitted in a message. Therefore, in such a situation, it is suitable to keep the encrypted part in VM and the non-encrypted or fixed part in NVM.

[0238] Some examples of the present disclosure include:

[0239] Example Al. A device 6 configured to communicate with a reader 4, the device 6 configured to, and / or comprising a radio interface 46 and / or processing circuitry 50 configured to:receive device credentials for the device 6;

[0240] determine whether to save the device credentials in volatile memory (VM); and

[0241] determine, based on network parameters, whether to save the device credentials in non-volatile memory (NVM).

[0242] Example A2. The device 6 of Example Al, wherein if the device 6 determines to save the device credentials in NVM, the device 6 is further configured to reduce at least one of energy consumption and processing and to divert energy resources towards saving the device credentials in NVM.

[0243] Example A3. The device 6 of any of Examples A1-A2, wherein the network parameters include a carrier wave, CW, illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, the device is further configured to continue to save the device credentials in VM.

[0244] Example A4. The device 6 of any of Examples Al -A3, wherein the network parameters include a CW illumination time period, and if the CW illumination time period is one of reduced or powered off, the device 6 is further configured to save the device credentials in NVM.

[0245] Example A5. The device 6 of any of Examples A1-A4, wherein if the device 6 determines to save the device credentials in VM, the device 6 is further configured to select a smaller occasion number in an access / paging round for its transmissions.

[0246] Example A6. The device 6 of any of Examples A1-A5, wherein if the device 6 determines to save the device credentials in VM, the device 6 is further configured to select a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access (FDMA) to maintain its energy for storing the device credentials in the VM.

[0247] Example A7. The device 6 of any of Examples A1-A6, wherein if the device 6 determines to save the device credentials in NVM, the device 6 is further configured to select any occasion number in an access or paging round for its transmissions.

[0248] Example A8. The device 6 of any one of Examples A1-A7, wherein the device 6 is an ambient internet of things (A-IoT) device.

[0249] Example A9. The device 6 of any of Examples A1-A8, wherein the device credentials include a temporary identification (temp ID) of the device 6.

[0250] Example Bl . A method implemented in a device 6 that is configured to communicate with a reader 4, the method comprising:receiving device credentials for the device 6;

[0251] determining whether to save the temp ID in volatile memory (VM); and determining, based on network parameters, whether to save the device credentials in non-volatile memory (NVM).

[0252] Example B2. The method of Example Bl, wherein if the device 6 determines to save the device credentials in NVM, further comprising reducing at least one of energy consumption and processing and to divert energy resources towards saving the device credentials in NVM.

[0253] Example B3. The method of Examples B 1 -B2, wherein the network parameters include a carrier wave, CW, illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, further comprising continuing to save the device credentials in VM.

[0254] Example B4. The method of Examples B 1 -B3, wherein the network parameters include a CW illumination time period, and if the CW illumination time period is one of reduced or powered off, further comprising saving the device credentials in NVM.

[0255] Example B5. The method of Examples B1-B4, wherein if the device 6 determines to save the device credentials in VM, further comprising selecting a smaller occasion number in an access / paging round for its transmissions.

[0256] Example B6. The method of Examples B1-B5, wherein if the device 6 determines to save the device credentials in VM, further comprising selecting a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access, FDMA, to maintain its energy for storing the device credentials in the VM.

[0257] Example B7. The method of Examples B1-B6, wherein if the device 6 determines to save the device credentials in NVM, further comprising selecting any occasion number in an access or paging round for its transmissions.

[0258] Example B8. The method Examples B1-B7, wherein the device 6 is an ambient internet of things (A-IoT) device.

[0259] Example B9. The method of any of Examples B1-B8, wherein the device credentials include a temporary identification (temp ID) of the device 6.

[0260] Example Cl . A reader device configured to communicate with a device 6, the reader device 4 configured to, and / or comprising a radio interface 30 and / or comprising processing circuitry 36 configured to:receive from the device 6 an indication of a type of memory the device 6 uses for storing device credentials; and

[0261] utilize network infrastructure based on the type of memory the device 6 uses for storing device credentials.

[0262] Example C2. The reader device 4 of Example Cl, wherein the reader device 4 is further configured to:

[0263] determine whether the device 6 stores its device credentials in non-volatile memory (NVM) or volatile memory (VM); and

[0264] in response to determining that the device 6 stores its device credentials in NVM, reduce carrier wave (CW) illumination time.

[0265] Example C3. The reader device 4 of any of Examples C1-C2, wherein if the reader device 4 determines that the device 6 stores its device credentials in VM, the reader device 4 is further configured to one of maintain CW power at a minimum threshold level and continue illuminating the device 6 so that the device 6 can maintain storage of the device credentials in VM.

[0266] Example C4. The reader device 4 of any of Examples C1-C3, wherein the reader device 4 is further configured to:

[0267] determine that the device 6 stores its device credentials in VM; and

[0268] based on the determination, provide resources to the device 6 earlier than other devices that store their device credentials in NVM.

[0269] Example C5. The reader device 4 of any of Examples C1-C4, wherein the reader device 4 is one of a network node, a user equipment (UE), and an intermediate UE.

[0270] Example C6. The reader device 4 of any of Examples C1-C5, wherein the device credentials include a temporary identification (temp ID) of the device 6.

[0271] Example DI. A method implemented in a reader device 4 that is configured to communicate with a device 6, the method comprising:

[0272] receiving from the device 6 an indication of a type of memory the device 6 uses for storing device credentials; and

[0273] utilizing network infrastructure based on the type of memory the A-IoT device 6 uses for storing device credentials.

[0274] Example D2. The method of Example DI , further comprising:

[0275] determining whether the device 6 stores its device credentials in non-volatile memory (NVM) or volatile memory (VM); andin response to determining that the device 6 stores its device credentials in NVM, reducing carrier wave (CW) illumination time.

[0276] Example D3. The method of any of Examples D1-D2, wherein if the reader device 4 determines that the device 6 stores its device credentials in VM, further comprising one of maintaining CW power at a minimum threshold level and continuing illumination of the device 6 so that the device 6 can maintain storage of the device credentials in VM.

[0277] Example D4. The method of any of Examples D1-D3, further comprising:

[0278] determining that the device 6 stores its device credentials in VM; and based on the determination, providing resources to the device 6 earlier than other devices that store their device credentials in NVM.

[0279] Example D5. The method of any of Examples D1-D4, wherein the reader device 4 is one of a network node, a user equipment (UE), and an intermediate UE.

[0280] Example D6. The method of any of Examples D1-D5, wherein the device credentials include a temporary identification (temp ID) of the device 6.

[0281] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0282] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a specialpurpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0283] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0284] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0285] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0286] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may bemade to an external computer (for example, through the Internet using an Internet Service Provider).

[0287] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0288] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

Claims:

1. A method implemented in a device (6) that is configured to communicate with a reader device (4), the method comprising:receiving device credentials for the device (6) (SI 10);determining, based on network parameters, whether to save the device credentials in volatile memory, VM or in non-volatile memory, NVM (SI 12); andindicating to the reader device (4) whether the device credentials are saved in VM or in NVM (Step 114).

2. The method of Claim 1, further comprising splitting the device credentials into two partitions, wherein a first partition is stored in the NVM and a second partition is stored in the VM.

3. The method of any one of Claims 1 and 2, wherein if the device (6) determines to save the device credentials in NVM, further comprising reducing at least one of energy consumption and processing to divert energy resources towards saving the device credentials in NVM.

4. The method of any one of Claims 1-3, wherein the network parameters include a carrier wave, CW, illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, further comprising continuing to save the device credentials in VM.

5. The method of Claim 4, wherein if the CW illumination time period is one of reduced or powered off, further comprising saving the device credentials in NVM.

6. The method of any one of Claims 1-5, wherein if the device (6) determines to save the device credentials in VM, further comprising selecting a smaller occasion number in an access / paging round containing a number of Contention-Based Random Access, CBRA, transmissions.

7. The method of any one of Claims 1-6, wherein if the device (6) determines to save the device credentials in NVM, further comprising selecting any occasion number in an access or paging round for its transmissions.

8. The method of any one of Claims 1-7, wherein if the device (6) determines to save the device credentials in VM, further comprising selecting a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access, FDMA, to maintain its energy for storing the device credentials in the VM.

9. The method of any one of Claims 1-8, wherein the device (6) is an ambient internet of things, A-IoT, device.

10. The method of any one of Claims 1-9, wherein the device credentials include a temporary identification, temp ID, of the device (6).

11. A method implemented in a reader device (4) that is configured to communicate with a device (6), the method comprising:receiving from the device (6) an indication of a type of memory the device (6) uses for storing device credentials (SI 00); andconfiguring network energy utilization based on the type of memory the device (6) uses for storing device credentials (SI 02).

12. The method of Claim 11, further comprising:determining whether the device (6) stores its device credentials in non-volatile memory, NVM, or volatile memory, VM; andin response to determining that the device (6) stores its device credentials in NVM, reducing carrier wave, CW, illumination time.

13. The method of Claim 12, wherein if the reader device (4) determines that the device (6) stores its device credentials in VM, further comprising one of maintaining CW power at a minimum threshold level and continuing to power the device (6) to enable the device (6) to maintain storage of the device credentials in VM.

14. The method of any one of Claims 11-13, further comprising:determining that the device (6) stores its device credentials in VM; andbased on the determination, providing resources to the device (6) earlier than other devices that store their device credentials in NVM.

15. The method of any one of Claims 11-14, wherein the reader device (4) is one of a network node, a user equipment, UE, and an intermediate UE.

16. The method of any one of Claims 11-15, wherein the device credentials include a temporary identification, temp ID, of the device (6).

17. A device (6) configured to communicate with a reader device (4), the device (6) configured to:receive device credentials for the device (6);determine, based on network parameters, whether to save the device credentials in volatile memory, VM or in non-volatile memory, NVM; andindicate to the reader device (4) whether the device credentials are saved in VM or in NVM.

18. The device (6) of Claim 17, wherein the device (6) is further configured to split the device credentials into two partitions, wherein a first partition is stored in the NVM and a second partition is stored in the VM.

19. The device (6) of any one of Claims 17 and 18, wherein if the device (6) determines to save the device credentials in NVM, the device (6) is further configured to reduce at least one of energy consumption and processing to divert energy resources towards saving the device credentials in NVM.

20. The device (6) of any one of Claims 17-19, wherein the network parameters include a carrier wave, CW, illumination time period, and if the CW illumination time period exceeds an expected duration of a device paging or access round, the device (6) is further configured to continue to save the device credentials in VM.

21. The device (6) of Claim 20, wherein if the CW illumination time period is one of reduced or powered off, the device (6) is further configured to save the device credentials in NVM.

22. The device (6) of any one of Claims 17-21, wherein if the device (6) determines to save the device credentials in VM, the device (6) is further configured to select a smaller occasion number in an access / paging round containing a number of Contention-Based Random Access, CBRA, transmissions.

23. The device (6) of any one of Claims 17-22, wherein if the device (6) determines to save the device credentials in NVM, the device (6) is further configured to select any occasion number in an access or paging round for its transmissions.

24. The device of any one of Claims 17-23, wherein if the device (6) determines to save the device credentials in VM, the device (6) is further configured to select a frequency shift from a subset of smallest available frequency shifts for frequency division multiple access, FDMA, to maintain its energy for storing the device credentials in the VM.

25. The device (6) of any one of Claims 17-24, wherein the device (6) is an ambient internet of things, A-IoT, device.

26. The device (6) of any one of Claims 17-25, wherein the device credentials include a temporary identification, temp ID, of the device (6).

27. A reader device (4) configured to communicate with a device (6), the reader device (4) configured to:receive from the device (6) an indication of a type of memory the device (6) uses for storing device credentials; andconfigure network energy utilization based on the type of memory the device (6) uses for storing device credentials.

28. The reader device (4) of Claim 27, wherein the reader device (4) is further configured to:determine whether the device (6) stores its device credentials in non-volatile memory, NVM, or volatile memory, VM; andin response to determining that the device (6) stores its device credentials in NVM, reduce carrier wave, CW, illumination time.

29. The reader device (4) of Claim 23, wherein if the reader device (4) determines that the device (6) stores its device credentials in VM, the reader device (4) is further configured to one of maintain CW power at a minimum threshold level and continue powering the device (6) to enable the device (6) to maintain storage of the device credentials in VM.

30. The reader device (4) of any one of Claims 27-29, wherein the reader device (4) is further configured to:determine that the device (4) stores its device credentials in VM; andbased on the determination, provide resources to the device (6) earlier than other devices that store their device credentials in NVM.

31. The reader device (4) of any one of Claims 27-30, wherein the reader device (4) is one of a network node, a user equipment, UE, and an intermediate UE.

32. The reader device (4) of any one of Claims 27-31, wherein the device credentials include a temporary identification, temp ID, of the device (6).

Images