Methods and nodes for passive ambient IoT device authentication and registration

Abstract

Methods and apparatuses are disclosed for registering an Ambient-Internet-of- Things (A-IoT) device. In an example embodiment, a method in a radio node in communication with an A-IoT device is provided. The method comprises: transmitting a registration command, as part of a downlink (DL) transmission, to the A-IoT device, the registration command including registration information for the A-IoT device to perform a registration procedure with a core network node; and in response to sending the registration command, receiving a registration request from the A-IoT device to perform the registration procedure with the core network node.

Description

[0001] METHODS and NODES FOR PASSIVE AMBIENT loT DEVICE AUTHENTICATION AND

[0002] REGISTRATION

[0003] RELATED APPLICATIONS

[0004] This application claims the benefits of priority of PCT Patent Application No., PCT / CN2024 / 074161, entitled “PASSIVE AMBIENT loT DEVICE AUTHENTICATION AND REGISTRATION” and filed at the Chinese Patent Office on January 26, 2024, which is hereby incorporated by reference in its entirety.

[0005] FIELD

[0006] The present disclosure relates to wireless communications, and in particular, to passive Ambient Internet of Things (loT) device authentication and registration.

[0007] BACKGROUND

[0008] Zero-Energy Internet of Things (loT) & Ambient-IoT (A-IoT)

[0009] Wireless loT devices may be battery powered, and both the need to change battery and the battery lifetime may be concerns for many potential applications such as asset tracking or environmental / industrial sensors. For this reason, the wireless communications industry has been interested in so-called zero-energy (ZE) devices. ZE devices refer to wireless loT devices that do not require battery replacement because they are often arranged to harvest energy from the environment. In some use cases, such as monitoring the temperature of foodstuffs, the ZE devices may have small batteries that are disposable (e.g., organic, compostable batteries), rechargeable, or have very limited capacity.

[0010] These ZE-IoT devices can be of very small form factor and could even be printable, and they target ultra-low power consumption to enable operation based on either energy-harvesting from an ambient source or back-scattering communication (e.g., Radio Frequency Identification (RFID)). That is, instead of relying on energy for communication being provided by a battery, it is instead harvested from an ambient source, such as vibrations, solar power, radio frequency (RF), etc., (harvesting), or a charge carrier wave is provided to the device which is modulated and reflected back to a reader (in the back-scattering communication case). This enables energy autonomous operation during the lifetime of the devices without the need for either manual replacement or charging of the batteries. Compared to existing radio access technologies, this imposes additional requirements on the radio interface and the protocols.

[0011] Recently work on this has been performed in a Third Generation Partnership Project (3GPP) study, referred to as A-IoT. A-IoT devices are characterized in the study according to their energy storage capacity, and capability of generating RF signals for their transmissions. Relying on these storage capacities, the study considers the following set of A-IoT devices:

[0012] • Device A: No energy storage, no independent signal generation / amplification, i.e. backscattering transmission.

[0013] • Device B: Has energy storage, no independent signal generation, i.e. backscattering transmission. Use of stored energy can include amplification for reflected signals.

[0014] • Device C: Has energy storage, has independent signal generation, i.e., active RF components for transmission.

[0015] A limited energy storage can be different among implementations within Device B or implementations within Device C, and different between Device B and Device C. Such storage may be order(s) of magnitude smaller than a Narrowband (NB)-IoT device may typically include.

[0016] An A-IoT device may harvest energy from different energy sources, such as RF, solar / light, piezoelectric (kinetic / vibration), electromagnetic, electrostatic, heat / thermal, thermoelectric, magnetic, wind / water, acoustic, etc.

[0017] RFID backscatter

[0018] A-IoT devices A and B inherit principles of RFID backscatter, where an always on carrier wave generated by a RFID reader illuminates (i.e., powers) the transponder tag. The tag further transmits its stored information by modulating the same carrier wave signal that it receives from the reader. The modulation may be accomplished by adjusting the antenna impedances and radar cross section of the tag, and the whole process of modulating the carrier wave and reflecting the modulated carrier back to the reader is called “backscatter.”

[0019] The actual data transmission between the reader and the tag can involve multiple back and forth communication, with the reader sending packets on the carrier wave to the tag, and the tag responding back by backscattering the carrier wave from the reader. There are multiple protocols available in RFID literature to control this back and forth communication behavior between the tag and the reader, as specified by, e.g., the Electronic Product Code (EPC) C1G2 protocol (ISO 18000-6C) standard.

[0020] Below is an example 3GPP study:

[0021] Latest SID proposal from Dec 2023 RAN plenary discussion

[0022] 3GPP TSG RAN Meeting #102 RP-23xxxx

[0023] Edinburgh, UK, December 11-15, 2023

[0024] 4.1 Objective of SI or Core part W1 or Testing part W1

[0025] [...] A. The overall objective shall be to study a harmonized air interface design with minimized differences (where necessary) for Ambient loT to enable the following devices: UL transmission is backscattered on a carrier wave provided externally. ii. < a few hundred uW peak power consumption1, has energy storage, initial sampling frequency offset (SFO) up io 10xppm, both DL and / or UL amplification in the device. The device ’s UL transmission may be generated internally by the device, or be backscattered on a carrier wave provided externally.

[0026] [ •]

[0027] As indicated above, the devices based on 4.1 objective A - i and ii are limited, so the current New Radio (NR) access mechanism may not be applied directly, which includes registration and authentication. Various approaches have indicated utilization of RFID-based mechanism to cater for devices (4.1 objective A - i, ii). However, the RFID mechanism does not define proper authentication and registration algorithm, as there is no role of Core Network (CN) in RFID access mechanism, and it appears it’s generally left to infrastructure implementation.

[0028] SUMMARY

[0029] Some embodiments advantageously provide methods, systems, and apparatuses for A-IoT device authentication and registration.

[0030] It may be desirable that A-IoT devices are registered to the network to benefit from functionalities provided by the CN, such as security, charging, reachability, etc. However, A-IoT devices may not initiate the registration themselves, as they may not be capable of independent signal generation. Solutions to trigger and instruct such a type of A-IoT devices and other types of A-IoT devices to do registration, or such that registration is enabled, are disclosed herein.

[0031] These devices may have some energy storage, which may be provided with resources, especially processing resource that can enable such devices to do lightweight registration. This is utilized in various embodiments described herein. Further, a device’s uplink (UL) transmission may utilize backscatter communications, hence the role of a Carrier Wave (CW) may be relevant for registration of such devices.

[0032] Some embodiments relate to a Radio Access Technology (RAT) that allows both backscattering and non-backscattering to transmit UL data once devices have been registered. The RAT allows physical connection or communication in the Radio Access Network (RAN) composed of base stations / network nodes, Carrier Wave Emitters (CWEs), readers (which may receive A-IoT device transmissions, e.g., wireless device or network node) and A-IoT devices. The CW from a CWE node can be used to deliver information to the devices, enabling their registration. If a device can generate independent UL signals, then a similar downlink (DL) signal can be allocated for registration in the same RAT.

[0033] Some embodiments relate to a CN registration procedure in A-IoT RAT utilizing CW (can be complemented with DL) to enable registration for backscattering based devices (i.e., passive devices). The same registration procedure can be employed for devices that can generate independent UL (i.e., active devices) under the harmonized RAT where the probable registration related information or registration command (which would otherwise have been contained in the CW for the passive solution) can be sent using a regular DL transmission. for example, there is provided a method in a radio node, in communication with an A-IoT device. The method comprises: transmitting a registration command, as part of a DL transmission, to the A-IoT device the registration command including registration information for the A-IoT device to perform a registration procedure with a core network node; and in response to sending the registration command, receiving a registration request from the A-IoT device to perform the registration procedure with the core network node.

[0034] There is also provided a method performed by an A-IoT device in communication with at least a radio node. The method comprises: receiving a registration command as part of a DL transmission, the registration command including registration information, for the A-IoT device to perform a registration procedure with a core network node; and initiating the registration procedure based on the registration information.

[0035] There is furthermore provided a method performed by a core network node for registering an A-IoT device, in communication with at least a radio node. The method comprises: sending, to the radio node, a registration command destined to the A-IoT device, the registration command including registration information for the A-IoT device to perform a registration procedure with the core network node; and in response to sending the registration command, receiving, from the radio node, a registration request originated from the A-IoT device to perform the registration procedure with the core network node.

[0036] A radio node, an A-IoT device and a core network node are provided to perform respectively the above methods.

[0037] With registration and proper authentication, properly registered / authenticated devices that use backscattering or device in the RAT that is compatible with backscattering-based devices can communicate via the network.

[0038] BRIEF DESCRIPTION OF THE DRAWINGS

[0039] 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:

[0040] FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system according to an embodiment.

[0041] FIG. 2 is a block diagram of a wireless device, a network node and an A-IoT device according to some embodiments.

[0042] FIG. 3 is a flowchart of an example of registration process according to some embodiments.

[0043] FIG. 4 is a flowchart of an example method in a radio node according to an embodiment.

[0044] FIG. 5 is a flowchart of an example method in an A-IoT device according to some embodiments.

[0045] FIG. 6 is a flowchart of an example method in a core network node according to some embodiments of the present disclosure.

[0046] DETAILED DESCRIPTION

[0047] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to A-IoT device authentication and registration. 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. Like numbers refer to like elements throughout the description.

[0048] 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.

[0049] 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.

[0050] 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), radio network controller (RNC), g Node B (gNB), evolved NB (eNB ), NB, multi-standard radio (MSR) radio node such as MSR BS, multi- cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, 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, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) or a radio network node.

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

[0052] 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, eNB, NB, gNB, MCE, IAB node, relay node, AP, radio AP, RRU, RRH.

[0053] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or NR, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned 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.

[0054] Note further that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. 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 the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0055] FIG. 1 shows a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a CN 14. 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 APs, 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 WD 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as WDs 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. A first A-IoT device 100a located in coverage area 18b is configured to wirelessly connect to, or be paged by, the corresponding network node 16b and / or WD 22b. A second A-IoT device 100b in coverage area 18c is wirelessly connectable to the corresponding network node 16c. While a plurality of A-IoT devices 100a, 100b (collectively referred to as A-IoT device 100) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole A-IoT device is in the coverage area or where a sole A-IoT device is connecting to the corresponding network node 16 and / or WD 22. Note that although only two A-IoT devices 100, three network nodes 16, and two WD 22 are shown for convenience, the communication system may include many more WDs 22, network nodes 16, and A-IoT devices 100.

[0056] Also, it is contemplated that a WD 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 WD 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, e.g WD 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0057] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0058] A network node 16 is configured to include a network node (NN) registration unit 32 which is configured to perform one or more network node functions described herein, including functions related to a passive or active A-IoT device authentication and registration. A WD 22 is configured to include an WD registration unit 34 which is configured to perform one or more WD functions described herein, including functions related to passive / active A-IoT device authentication and registration. An A-IoT device 100 is configured to include an A-IoT registration unit 102 (see Fig. 2) which is configured to perform one or more A-IoT device functions described herein, including functions related to passive / active A-IoT device authentication and registration. As a note, the A- loT devices may not have the registration unit 102, but they can still perform the functions described herein.

[0059] Example implementations, in accordance with an embodiment, of the WD 22, network node 16, and A-IoT device 100 discussed in the preceding paragraphs will now be described with reference to FIG. 2.

[0060] The network node 16 has hardware 58 enabling it to communicate with WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 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.

[0061] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or Field Programmable Gate Arrays (FPGAs) and / or Application Specific Integrated Circuitry (ASIC) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or Random Access Memory (RAM) and / or Read-Only Memory (ROM) and / or optical memory and / or Erasable Programmable ROM (EPROM).

[0062] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 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 network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include NN registration unit 32 configured to perform one or more network node functions described herein, including functions related to passive / active A-IoT device authentication and registration. The network node can be a core network node, as such, the structure of the network node equally applies to the core network node.

[0063] The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 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.

[0064] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs and / or ASICs (adapted to execute instructions). The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM and / or ROM and / or optical memory and / or EPROM.

[0065] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.

[0066] The processing circuitry 84 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 WD 22. The processor 86 corresponds to one or more processors 86 for performing WD functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the WD 22 may include a WD registration unit 34 configured to perform one or more WD 22 functions described herein, including functions related to passive / active A-IoT device authentication and registration.

[0067] The A-IoT device 100 may have some hardware 104 that may include a radio interface 106 configured to set up and maintain a wireless connection 64 with a network node 16 and / or WD 22 serving a coverage area 18 in which the A-IoT device 100 is currently located. The radio interface 106 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.

[0068] The hardware 104 of the A-IoT device 100 further may include processing circuitry 108 or not. The processing circuitry 108 may include a processor 110 and memory 112. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 108 may comprise integrated circuitry for processing and / or control. The processor 110 may be configured to access (e.g., write to and / or read from) memory 112, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM and / or ROM and / or optical memory and / or EPROM, or just a simple storage place.

[0069] Thus, the A-IoT device 100 may further comprise software 114, which is stored in, for example, memory 112 at the A-IoT device 100, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the A-IoT device 100. The software 114 may be executable by the processing circuitry 108.

[0070] It should be noted that an A-IoT device has a complexity and power consumption order of magnitude lower than the existing 3GPP LPWA technologies (e.g. NB-IoT and eMTC) and UE.

[0071] Although FIG. 2 shows various “units” such as NN registration unit 32, A-IoT registration unit 102 and WD registration unit 34 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.

[0072] As mentioned above, A-IoT devices may not be capable of initiating a registration procedure since they are not capable of independent signal generation. Generally stated, embodiments in this disclosure allow a radio node (network node or WD 22) to send a registration command to the A-IoT devices to trigger the registration procedure . To do so, for example, a reader (CWE or radio node) can send a DL transmission to the A-IoT devices, using a CW, for example. Before describing the embodiments in more detail, the following is to be noted.

[0073] The embodiments are described for ultra-low power devices, ZE or A-IoT devices 100. However, the principles described herein are not limited to such devices, and can be extended other service / device classes or categories, e.g., related to Enhanced Mobile Broadband (eMBB), Extended Reality (XR), massive-Machine Type Communication (MTC), Ultra-Reliable Low Latency Communications (URLLC), and Time-Sensitive Networking (TSN).

[0074] The devices, e.g., A-IoT device 100, may be assumed to be capable of receiving DL data (a non-exclusive example may utilize on-off keying (OOK) waveforms for low-power DL reception). Furthermore, DL reception may be decoupled from CW events used for backscatter modulation. To enable this, the reader may be a combination of one or more spatially separated entities, which may transmit DL information in a separate frequency from the frequency on which the CW is emitted.

[0075] The CW is used to backscatter UL transmissions from the device (tag). The CWE transmits a CW. The CWE can be, e.g., a network node 16 and / or WD 22. The reader of the backscatter UL transmissions can be, e.g., the same or a different one of the network node 16 and / or WD 22.

[0076] In some examples, the scheduling slot may relate to UL transmissions over the backscattered link, but the scheduled slot can also be used for normal UL transmissions (without backscatter). Although some examples relate to backscattered UL transmissions, they are not to be limited to them, i.e., various examples below can also be applied in a similar fashion considering a normal UL transmission, where the device (e.g., A-IoT device 100) can generate the CW independently. Furthermore, the scheduling command can be termed as polling or query or query rep or query repetition, or paging command, etc. Also, the terms “A-IoT device”, “tag”, “device” are used interchangeably.

[0077] Embodiments

[0078] Generally stated, the embodiments provide a RAT that allows or enables the device 100 to send UL transmissions using the backscattering method, e.g. the device 100 is allowed to transmit user data in UL to any node among a set of inventory RAN nodes if the device is registered. The registration should allow the device to freely transmit to any RAN node that belongs to a network / PLMN (any or one or more specific nodes). The registration may consider non-limiting functions like authentication, conducting Non-Access Stratum (NAS), Access stratum security mode command (AS SMC) through the CWE nodes to authenticate / allocate context / registration of the A-IoT device. The CW from the CWE node (e.g., network node 16 and / or WD 22) is designed in such a manner that the registration information to be used by the device to select and conduct a particular procedure is included in the CW, e.g., in the beginning of the CW, etc. If the device 100 is capable of generating independent UL signals (i.e. for active A-IoT devices), then a similar DL signal can be allocated, replacing the CW in order to enable registration; it means that the DL transmission / signal may include similar information which could have been included in the CW. The CW can be sent to the device to trigger a request for registrations (or UL signaling that enables registration), and in one option, this CW type can be set apart from other CW types meant for data transmissions. Hence, in this CW, the control plane actions can be performed using a RAN resource in the form of CW (provided by a CWE, e.g., network node 16 or WD 22) or specific types of CW (which in some cases may only be allowed to perform control plane actions).

[0079] For example, registration control information could be added to the CW signal, e.g., a ‘registration request flag’ or a NAS container, which could contain the registration trigger and also other information.

[0080] In the case of a harmonized A-IoT solution, the same registration information transmitted in the CW to passive devices (e.g., A-IoT device 100), could be transmitted in paging to active devices (e.g., A-IoT device 100). For example, a ‘registration request flag’ included in the CW to passive devices could, in some examples, be communicated to active devices by common paging and having the same flag in the paging message or in a short message, i.e., in addition to system information update notification, Commercial Mobile Alert System (CMAS) / Earthquake and Tsunami Warning System (ETWS), etc. In either case, the device may, if it has not already registered, respond and register to the network.

[0081] In some examples, the registration of A-IoT devices to the network can be initiated by the network (e.g. a core network node), e.g., via network node 16 and / or WD 22. In case of passive devices (e.g., A-IoT device 100), an indication / trigger / command and relevant configuration information for the devices to perform registration can be incorporated into the CW from CWE nodes to the devices. In case the A-IoT devices are capable of independent signal generation (active devices), the indication / trigger / command to do registration can be sent in the DL transmission, e.g., included in paging or group paging with enhancements. Similarly, the deregistration of A-IoT devices can be initiated by the network via CW from CWE nodes (e.g., network node 16 and / or WD 22) or DL transmission to the devices in an individual or command control signaling manner.

[0082] In one example, it is left to network implementation e.g., via network node 16 and / or WD 22, how often to send out and poll for registration request from A-IoT devices (e.g., A-IoT device 100). For example, a periodicity (e.g. for sending the registration command) is specified and configured in the network.

[0083] As one example, the information in the registration command originated from CN 14 is not limited to just a trigger for a registration request but can be further differentiated with any of the following:

[0084] • Registration trigger for new devices (e.g., A-IoT device 100) that have not yet registered to CN 14 or in the current registration area).

[0085] • Registration trigger for all devices (e.g., A-IoT device 100), also previously registered (i.e., for the purpose of periodic Tracking / Registration area update, error correction for device-NW registration state mismatch, etc.)

[0086] • Any CN 14 / NAS signaling.

[0087] The above information can be provided in a multi-bit indication, which could be included in the CW (passive devices) or in the paging request (active devices), e.g., as follows in Table 1:

[0088] Furthermore, the registration command can be combined with an operator / Public Land Mobile Network (PLMN) / Non-Public Network (NPN) ID, and in some cases, only devices tags 100 with matching ID (either belonging or roaming) would respond to the registration command.

[0089] In one example, the registration command (e.g. indication / request / trigger) from the network, e.g., via the network node(s) 16, can be a common command targeting all the A-IoT devices 100 in the area of a CW or NG-RAN that have not yet registered / inventoried. This means any new devices when receiving such a command may trigger the registration procedure individually. The common command can be a broadcast system information containing information about the type of devices or group of devices with group ID that need to perform the registration procedure. In case of passive / semi -passive devices, the common command can be designed with some pre-defined common ID / indication (similar to a special use of paging message, e.g., short message). The registration command from the network (e.g., via network node 16 and / or WD 22) can also be a request to establish security, e.g., an authentication request / challenge.

[0090] Now turning to Fig. 3, an exemplary signaling flow illustrating communications between the different entities involved in the registration procedure for A-IoT devices 100, as mentioned above, will be described. This registration can be referred to as a lightweight registration. Fig. 3 shows a signaling flow example 140 between one or more tags, e.g., A-IoT device 100, a NN 16 / reader, and a CN 14 (which comprises e.g. a core network node). It should be noted that CN 14 and core network node 14 can be interchangeably in this disclosure. The tags are triggered to initiate a registration procedure by means of CW signaling, for example, with control information as mentioned above. In this case, the tags are passive tags. Since passive tags may be limited in capability, heavy security operations such as encryption (e.g., computing subscription concealed identifier (SUCI) from EPC / Subscription Permanent Identifier (SUPI)), deriving keys, etc., may take a long time. As such, the network can prepare / alert the tags to precompute or compute this before the actual registration procedure. In this example, only mutual authentication is shown, but other security procedures may be incorporated into the flow sequence as well. At the end of the registration procedure, the tag is identified, authenticated, and allocated with an ID in shorter form than EPC / SUPI, to be exchanged in the communications over the air interface. All this information (tag context) is maintained at the network side for subsequent authenticated / secured transmissions, as shown in Fig. 3.

[0091] More specifically, the signaling flow 140 starts, for example, with CN 14 (or a core network node) sending a registration command / inventory trigger to the NN 16 / reader (Block S146). The NN 16 sends the registration command to the tag 100 (Block S148), in a CW, for example. The registration command can comprise a PLMN and / or cell ID. The tag 100 may precompute or compute heavy cryptography processing, e.g., SUPI / EPC to SUCI (Block S150). Upon receipt of the registration command, the tag 100 is triggered to initiate the registration procedure with CN 14. To do so, the tag 100 replies with a registration request, which may comprise the tag ID and / or the computed SUCI (Block S152). The registration request is sent to the CN 16, through NN 16. For example, NN 16 / reader sends an initial UL message, which may comprise the registration request including the SUCI, to CN 14 (Block S154). Then, CN 14 sends an initial context setup request to NN 16 / reader (Block SI 56). The initial context setup request may comprise an authentication request, a registration accept (to indicate the acceptation to register the tag 100) including a Global Unique Temporary Identifier (GUTI). Then, NN 16 / reader sends / forwards the authentication request / command and registration accept to the tag 100 (Block S158). The registration accept may comprise an allocated short ID based on the GUTI. The tag 100 replies with an authentication response and registration complete (Block S160) to the NN 16. NN 16 / reader sends an Initial Context Setup Response comprising an authentication Response, and Registration Complete to CN 14 (Block SI 62). As such, the tag 100 is registered and authenticated by the network. Tag 100 can then send secured / authenticated transmissions to the network, e.g., NN 16, gNB, User Plane Function (UPF) or Access and Mobility Management Function (AMF) (Block SI 64).

[0092] Further details about the operations in Fig. 3 are provided below.

[0093] The communications between NN 16 and CN 14 can be performed using NGAP. The communications between NN 16 / reader and tag 10 can be performed using a CW in case tag 10 is a passive tag. If tag 10 is an active tag, then other signals can be used. The registration procedure of Fig. 3 can be applied to active tags as well, by replacing the CWs with signals generated by the active tags.

[0094] In one example, the registration procedure can involve:

[0095] • mutual authentication between the device (e.g., A-IoT device 100) and the network, which may comprise one or more nodes for different roles, e.g., to exercise control, to send CW, and to receive UL transmissions with or without backscatter depending on device capability. Examples of the one or more nodes are network node 16, WD 22, CWE.

[0096] • In another option, only one node authenticates the other, e.g., the network node authenticates the device or the device authenticates the network node.

[0097] The registration command could be an explicit registration request (or trigger). The registration request is not limited to the NAS registration. The device 100 may send an Access Stratum (AS) message to perform the registration, and NN 16 (e.g. NG-RAN) sends an NG-AP message to CN 14 on behalf of the device to make the device registered in the CN 14. The AS message may be sent by the device actively, or triggered by an AS message from NG-RAN which requests the device to perform the registration (e.g. like the inventory procedure in RFID solution).

[0098] The registration can be valid for a registration area, which is a set of RAN nodes, which could represent an Enterprise. In this case, the set of RAN nodes control the area. The CW may be controlled / transmitted by any of the RAN nodes or CWEs (e.g. network node 16 and / or WD 22) within the registration area. The CW may contain an ID which represents the registration area.

[0099] In one example, the UL signaling from the device 100 can be done in the form of:

[0100] - Backscatter manner, i.e., the information in UL (user data and / or control data, e.g., registration information and / or IDs) can be piggybacked or backscattered in UL using CW. The IDs can be device ID (ID defined in Subscriber Identity Module (SIM) configuration or hardcoded in device chip) or product / EPC ID (which can be configured) which can be used to identify the object to which the device (tag) is attached. The CW can be transmitted by a CWE (e.g., a separate node from network node 16) which can be either controlled by network node 16 or not controlled by network node 16. The CW can be transmitted by a gNB (acting as a CWE) or by a WD 22 (acting as a CWE).

[0101] - Non-backscater manner, i.e., device 100 can generate UL signal independently. The RAT may be designed to allow backscatter transmissions, and if a device can generate UL without backscattering, then the: o Device can ignore the CW; o Device can read the command from the CW but still can generate independent UL signals subject to commands received from the CW; o Network (gNB / CWE / WD) can disable the CW for the device with independent UL generation capability.

[0102] Alternatively, the RAT may be harmonized to support both device types (with or without backscatter) for their registration and / or data transmissions.

[0103] In one example, a device (subscribed to some network / operator / PLMN / NPN) can authenticate the network, e.g., if the

[0104] • CW includes network (home or visiting) or operator (home or visiting) or PLMN / NPN (home or visiting) ID; the ID can be modulated as payload over CW, or included in the form of sequence (inserted or appended, e.g., in the front of CW);

[0105] • DL / Device Terminated (DT) transmission network (home or visiting) or operator (home or visiting) or PLMN (home or visiting) ID which is sent prior to CW or UL slot (without the need of CW).

[0106] If the ID matches, then device 100 can transmit the registration request, perform data transmission in the UL (with or without CW) or send a message to initiate an authentication procedure.

[0107] In one example, the device 100 includes device ID / sequence (plain text (such as SUPI in LTE / NR) or encrypted based on algorithm included in device chip (like SUCI in NR)) for its authentication at reader or network node 16 or CN 14. furthermore, the device ID can be included as part of the registration request in CW or independent UL (replacing CW), but in the same RAT that supports CW reception, but no data payload is allowed to be included alongside (the purpose of transmission may be to perform the registration procedure first). In some examples, the device ID can be included with the data payload even if the device has not registered yet. In some examples, the device ID or a function of the device ID (e.g., short form or first or last X bits of the device ID) can be included with data provided the device is already successfully registered.

[0108] In one example, when the authentication is performed by the reader (e.g., via network node 16 or WD 22), the reader may request CN 14 to perform the authentication / authorization in a similar way as the current 3 GPP primary authentication, utilizing AMF, Unified Data Management (UDM), Authentication Server Function (AUSF). The reader may send the device ID or the function of the device ID to a credential server for authentication and authorization externally as secondary authentication, which may be performed after the primary authentication. It is also possible that the secondary authentication is executed without the primary authentication.

[0109] In one example, upon authentication by CN 14, CN 14 (e.g., via network node 16 and / or WD 22) can allocate a temporary ID like GUTI to the A-IoT device 100. This temporary ID can be smaller than legacy GUTI. This temporary ID can be built using components of GUTI (e.g., Mobile Network Code (MNC), AMF set, etc.) and new components related to CWE nodes, e.g., CWE ID, or the NF Set ID (e.g., AMF set ID). It means the CWE node can be part of CN 14 (or visible to CN 14). This temporary ID may be used as a pointer to where the context resides.

[0110] In one example, upon authentication by CN 14 or by RAN (e.g., successful collision resolution), a RAN node can allocate RAN scope ID / sequence or temporary RAN scope ID / sequence which may be associated with a current cell (network node 16), or a current CWE, or a group of cells (network nodes 16), or a group of CWEs or a given geographic area (e.g., an indoor defined area or part of an indoor area).

[0111] In some examples, a network node 16 can control or be associated with multiple CWEs (bistatic setup) or a network node 16 can itself act as a CWE (monostatic setup).

[0112] In one example, the CW may contain or be modulated with RAN scope ID / sequence and / or CN ID / sequence and / or Operator / network / PLMN ID / sequence so that only the targeted device can transmit UL in a backscatter manner.

[0113] In one example, if the reader is a WD 22, it can forward the received UL transmission from device 100 (e.g., authentication request or response or registration request or data) to network node 16, where the reader may or may not insert its signature of ID.

[0114] In one example, if the reader is a WD 22, then the reader authenticates the device, and if the device is successfully authenticated, it forwards the payload / data to network node 16, otherwise it does not. In one example option, the reader can authenticate the device if the device ID matches with allowable / rightful / subscribed device IDs. The device IDs can be communicated to the reader by network node 16 or CN 14.

[0115] In one example, if the device is authenticated, then it can be allocated NAS and / or AS keys if the device capability allows. Another option is to pass the security parameters to the device, so that the device can derive NAS and / or AS keys based on its confidential information, as well as the security parameters.

[0116] In one example, the device 100 may further authenticate the network based on the security parameters provided, besides the PLMN validation described above. This means that only authorized readers can read the device. In one example, the device includes an identifier or part of an identifier received in DL to the UL message (backscattered), and the receiving entity uses the identifier to route the UL message to the network node 16 identified by the identifier. The network node 16 is able to handle the UL message, e.g. decrypt it or forward it to the core network. In one example, if the device has been disabled from being allowed to communicate, the CW may contain or modulated with RAN scope ID / sequence and / or CN ID / sequence and / or Operator / network / PLMN ID / sequence so that all or a subset of the disabled devices are allowed to communicate with the network as to request to be reenabled.

[0117] In one example, the device 100 includes a short ID representing the registered PLMN / SNPN locally in one or more network node(s) 16 in its backscattered UL transmission (e.g. an index associated to a list of PLMNs / SNPNs can be made valid in more than one network node 16). The short ID may contain only a few bits as the backscattered UL transmission is restricted to a quite small area. The network node 16 discards the received UL message if it does not belong to the PLMN indicated in the UL message. It may inform the device that it does not belong to the indicated PLMN / SNPN. By this, the device can perform UL transmission without first correctly receiving the DL message containing the (full) PLMN / SNPN ID.

[0118] In one example, when receiving a registration request from a device 100, the CN 14 sends the corresponding registration response (e.g., whether accept or reject the registration) to multiple RAN nodes (e.g., network nodes 16) besides the RAN node from which it has received the registration request. In case the device does not receive the registration response while moving to a new RAN node, it sends a new registration request (which may be backscattered) including its device ID. In case the new RAN node has already received the registration response from CN 14, it directly sends the registration response to the device, otherwise it forwards the registration request to CN 14.

[0119] Now turning to Fig. 4, a flow chart of an example of a method 200 for registering an A- loT device 100 in a network, such as network 10, will be described, in accordance with the description above. The method 200 is performed by a radio node, which can be a network node 16 or a WD 22, for example. Method 200 comprises:

[0120] Step 210: transmitting a registration command, as part of a DL transmission, to the A-IoT device, the registration command including registration information for the A-IoT device to perform a registration procedure with a core network node; and

[0121] Step 220: in response to sending the registration command, receiving a registration request from the A-IoT device to perform the registration procedure with the core network node.

[0122] The core network node can be part of CN 14, for example. In some examples, the registration command is carried in a CW. In some examples, the registration information comprises configuration information for the A-IoT device to perform the registration procedure. In some examples, the registration information comprises at least one of: a registration trigger for at least one unregistered A-IoT device, a registration trigger for all A-IoT devices, and core network / non-access stratum, CN / NAS, signaling. In some examples, the registration information comprises a PLMN or NPN ID or cell ID. In some examples, the radio node can receive the registration command from a core network node. In some examples, the registration command comprises an indication for the A-IoT device to compute a security operation before performing the registration procedure. In some examples, the registration request comprises an ID of the A- loT device. In some examples, the radio node can send a registration request to the core network node. In some examples, in response to sending the registration request, the radio node receives an initial context setup request from the core network node, the initial setup request comprising an authentication request, and / or a registration accept. In some examples, the radio node sends the authentication request to the A-IoT device. In some examples, the radio node receives an authentication response from the A-IoT device and forwards the authentication response to the core network node. In some examples, the radio node further receives UL data from the A-IoT device. In some examples, the received UL data are at least one of backscattered and non- backscattered.

[0123] Fig. 5 illustrates a flow chart of an example method 300 for registering an A-IoT device 100 in a network, such as network 10. Method 300 is performed by the A-IoT device 100. The A-IoT device 100 can be a passive one or an active one and is in communication with a radio node, for example. The radio node can be a network node 16 or WD 22. Method 300 comprises: Step 310: receiving a registration command as part of a DL transmission, the registration command including registration information, for the A-IoT device to perform a registration procedure with a core network node; and

[0124] Step 320: initiating the registration procedure based on the registration information. In some examples, the A-IoT device initiates the registration procedure by sending a registration request to the radio node. In some examples, the registration command is received in a CW.

[0125] In some examples, the registration information comprises configuration information for the A-IoT device to perform the registration procedure. In some examples, the registration information comprises at least one of: a registration trigger for at least one unregistered A-IoT device, a registration trigger for all A-IoT devices, and CN / NAS signaling. In some examples, the registration information comprises a PLMN or NPN ID or cell ID. In some examples, the registration command comprises an indication for the A-IoT device to compute a security operation before performing the registration procedure. In some examples, the A-IoT device computes the security operation. In some examples, in response to the registration command, the A-IoT device sends a registration request comprising an ID of the A-IoT device, to the radio node. In some examples, the A-IoT device receive an authentication request from the radio node, originated from the core network node. In some examples, the A-IoT device sends an authentication response to the radio node. In some examples, the A-IoT device sends UL data to the radio node. In some examples, the transmitted UL data are at least one of backscattered and non-backscattered.

[0126] Fig. 6 illustrates a flow chart of an example method 400 for registering an A-IoT device 100 in a network, such as network 10. The method 400 can be performed by a core network node, such a core network node in CN 14. Method 400 comprises:

[0127] Step 410: sending, to the radio node, as part of a DL transmission a registration command destined to the A-IoT, the registration command including registration information for the A-IoT device to perform a registration procedure with the core network node; and

[0128] Step 420: in response to sending the registration command, receiving, from the radio node, a registration request originated from the A-IoT device to perform the registration procedure with the core network node.

[0129] In some examples, the registration information comprises configuration information for the A-IoT device to perform the registration procedure. In some examples the registration information comprises at least one of: a registration trigger for at least one unregistered A-IoT device, a registration trigger for all A-IoT devices, and CN / NAS signaling. In some examples, the registration information comprises a PLMN or NPN ID or cell ID. In some examples, the registration command comprises an indication for the A-IoT device to compute a security operation before performing the registration procedure. In some examples, in response to sending the registration command, the core network node receives a registration request comprising an ID of the A-IoT device, from the radio node. In some examples, the core network node sends an authentication request destined to the A-IoT device, to the radio node. In some examples, the core network node receives an authentication response from the radio node, originated from the A-IoT device. In some examples, the core network node receives uplink UL data from the A-IoT device. In some examples, the transmitted UL data are at least one of backscattered and non-backscattered. In some examples, the radio node is a radio access network node or a wireless device.

[0130] 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.” 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. 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.

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

Claims

Claims:

1. A method (200) performed by a radio node in communication with an Ambient- Intemet-of-Things, A-IoT, device (100), the method (200) comprising: transmitting (210) a registration command, as part of a downlink, DL, transmission, to the A-IoT device (100), the registration command including registration information for the A-IoT device (100) to perform a registration procedure with a core network node (14); and in response to sending the registration command, receiving (220) a registration request from the A-IoT device (100) to perform the registration procedure with the core network node (14).

2. The method of claim 1, wherein the registration command is carried in a Carrier Wave (CW).

3. The method of claim 1 or 2, wherein the registration information comprises configuration information for the A-IoT device to perform the registration procedure.

4. The method of any one of claims 1 to 3, wherein the registration information comprises at least one of: a registration trigger for at least one unregistered A-IoT device, a registration trigger for all A-IoT devices, and core network / non-access stratum, CN / NAS, signaling.

5. The method of any one of claims 1 to 4, wherein the registration information comprises a public land mobile network (PLMN) or Non Public Network (NPN) Identifier (ID) or cell ID.

6. The method of any one of claims 1 to 5, further comprising receiving the registration command from the core network node.

7. The method of any one of claims 1 to 6, wherein the registration command comprises an indication for the A-IoT device to compute a security operation before performing the registration procedure.

8. The method of any one of claims 1 to 7, wherein the registration request comprises an ID of the A-IoT device.

9. The method of any one of claims 1 to 8, further comprising sending a registration request, originated from the A-IoT device, to the core network node.

10. The method of claim 9, in response to sending the registration request, receiving an initial context setup request from the core network node, the initial setup request comprising an authentication request, and / or a registration accept.

11. The method of claim 10, further comprising sending the authentication request to the A-IoT device.

12. The method of claim 11, further comprising receiving an authentication response from the A-IoT device and forwarding the authentication response to the core network node.

13. The method of any one of claims 1 to 12, further comprising receiving uplink (UL) data from the A-IoT device.

14. The method of claim 13, wherein the received UL data are at least one of backscattered and non-backscattered.

15. The method of any one of claims 1 to 14, wherein the radio node is a radio access network node or a wireless device.

16. A method (300) performed by an Ambient-Intemet-of-Things, A-IoT, device (100) in communication with at least a radio node, the method (300) comprising: receiving a registration command as part of a downlink transmission, the registration command including registration information, for the A-IoT device (100) to perform a registration procedure with a core network node (14); and initiating the registration procedure based on the registration information.

17. The method of claim 16, wherein the registration command is received in a Carrier Wave (CW).

18. The method of claim 16 or 17, wherein the registration information comprises configuration information for the A-IoT device to perform the registration procedure.

19. The method of any one of claims 16 to 18, wherein the registration information comprises at least one of: a registration trigger for at least one unregistered A-IoT device, a registration trigger for all A-IoT devices, and core network / non-access stratum, CN / NAS, signaling.

20. The method of any one of claims 16 to 19, wherein the registration information comprises a PLMN or NPN Identifier (ID) or cell ID.

21. The method of any one of claims 16 to 20, wherein the registration command comprises an indication for the A-IoT device to compute a security operation before performing the registration procedure.

22. The method of any one of claims 16 to 21, further comprising, in response to the registration command, sending a registration request comprising an ID of the A-IoT device, to the radio node.

23. The method of claim 22, further comprising receiving an authentication request from the radio node, originated from the core network node.

24. The method of claim 23, further comprising sending an authentication response to the radio node.

25. The method of any one of claims 1 to 24, further comprising sending uplink (UL) data to the radio node.

26. The method of claim 25, wherein the transmitted UL data are at least one of backscattered and non-backscattered.

27. A method (400) performed by a core network node (14) for registering an Ambient-Intemet-of-Things, A-IoT, device (100) in communication with at least a radio node, the method (400) comprising: sending (410), to the radio node, a registration command destined to the A-IoT device (100), the registration command including registration information for the A-IoT device (100) to perform a registration procedure with the core network node (14); and in response to sending the registration command, receiving (420), from the radio node, a registration request originated from the A-IoT device (100) to perform the registration procedure with the core network node (14).

28. The method of claim 27, wherein the registration information comprises configuration information for the A-IoT device to perform the registration procedure.

29. The method of claim 27 or 28, wherein the registration information comprises at least one of: a registration trigger for at least one unregistered A-IoT device, a registration trigger for all A-IoT devices, and core network / non-access stratum, CN / NAS, signaling.

30. The method of any one of claims 27 to 29, wherein the registration information comprises a PLMN or NPN Identifier (ID) or cell ID.

31. The method of any one of claims 27 to 30, further comprising, in response to sending the registration command, receiving a registration request comprising an ID of the A-IoT device, from the radio node.

32. The method of claim 31, further comprising sending an authentication request destined to the A-IoT device, to the radio node.

33. The method of claim 32, further comprising receiving an authentication response from the radio node, originated from the A-IoT device.

34. The method of any one of claims 27 to 33, further comprising receiving uplink (UL) data from the A-IoT device.

35. The method of claim 34, wherein the transmitted UL data are at least one of backscattered and non-backscattered.

36. The method of any one of claims 27 to 35, wherein the radio node is a radio access network node or a wireless device.

37. A radio node (16, 22) in communication with an Ambient-Intemet-of-Things, A- loT, device (100), the radio node (16, 22) comprising a network interface (62, 82) and processing circuitry (68, 84) connected thereto, the processing circuitry (68, 84) configured to perform any steps of the method of claims 1 to 15.

38. An Ambient-Intemet-of-Things, A-IoT, device (100), in communication with a radio node (16, 22), comprising a network interface (106) and processing circuitry (108) connected thereto, the processing circuitry (108) configured to perform any steps of the method of claims 16 to 26.

39. A core network node (14) for registering an Ambient-Intemet-of-Things, A-IoT, device (100) in communication with at least a radio node (16, 22), the core network node (14) comprising a network interface (62) and processing circuitry (68) connected thereto, the processing circuitry (68) configured to perform any steps of the method of claims 27 to

Images