Method and apparatus for enabling ambient internet of things (AIOT) device
The use of NAS messages to securely manage AIoT devices in 5G networks addresses security concerns and inefficiencies in enabling/disabling RF signal transmission, ensuring reliable and secure network operations for AIoT devices.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-09-29
- Publication Date
- 2026-04-09
AI Technical Summary
Existing methods for managing Ambient Internet of Things (AIoT) devices in 5G networks face security concerns and inefficiencies in enabling and disabling RF signal transmission, particularly in the delivery of explicit indicators for temporarily disabled devices, which can compromise network security.
A method and apparatus that utilize Non-Access Stratum (NAS) messages to securely transfer explicit indicators for AIoT devices, ensuring that only enabled devices respond, thereby maintaining network security without impacting the Radio Access Network (RAN).
Enables secure and efficient management of AIoT devices by allowing temporarily disabled devices to respond to commands without compromising network security, thus enhancing the reliability and security of 5G network operations.
Smart Images

Figure CN2025125171_09042026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR ENABLING AMBIENT INTERNET OF THINGS (AIOT) DEVICE
[0001] The present patent application claims priority to:
[0002] - the PCT Application No. PCT / CN2024 / 123241 filed on 2024-10-04, the disclosure of which is incorporated herein in its entirety by reference; and
[0003] - the PCT Application No. PCT / CN2025 / 073728 filed on 2025-01-21, the disclosure of which is incorporated herein in its entirety by reference.Technical Field
[0004] The embodiments herein relate generally to the field of communication, and more particularly, the embodiments herein relate to method and apparatus for device response acquisition for an Ambient Internet of Things (AIoT) device.Background
[0005] Ambient Internet of Things (AIoT) , also referred as Zero-Energy IoT (ZE-IoT) , Ambient-IoT (A-IoT) , Passive-IoT, or Ambient power-enabled IoT, is recently increasingly researched. In 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 22.369 v19.3.0: “Service requirements for ambient power-enabled IoT; Stage 1 (Release 19) ” , the service requirements for enabling and disabling Ambient IoT devices are defined in section 5.2.3.
[0006] Management
[0007] The 5th Generation Mobile Communication Technology (5G) network shall support suitable management mechanisms for an Ambient IoT device or a group of Ambient IoT devices. The 5G system shall support a mechanism to:
[0008] - disable the capability to transmit RF signals for one or more Ambient IoT device that is / are currently able to transmit Radio Frequency (RF) signals;
[0009] - enable the capability to transmit RF signals for one or more Ambient IoT device that is / are currently disabled to transmit RF signals.
[0010] Based on operator policy, the 5G system shall provide a suitable mechanism to permanently disable the capability of an Ambient IoT device or a group of Ambient IoT devices to transmit RF signals.
[0011] Subject to operator policy and regulatory requirements, the 5G system shall support suitable mechanisms for the Ambient IoT device to move between one or more networks and countries. 3GPP Technical Report (TR) 23.700-13 v1.2.1: “Study on Architecture support of Ambient power-enabled Internet of Thing (Release-19) ” has interim conclusion on Key Issue #3.3GPP Change Request (CR) S2-2500425 solves editor note in Key Issue #3 conclusion about whether and how to support enabling temporarily disabled AIoT devices, by stating that implicit indicator or explicit indicator can enable temporarily disabled devices to respond the A-IoT paging.Summary
[0012] According to requirement in TS 22.369 v19.3.0, it is clear that “enable” , “ (temporary) disable” and “permanent disable” functions need to be provided.
[0013] In 3GPP TR 38.769 v19.0.0, according to the agreements from 3GPP Radio Access Network (RAN) 2 group, the command from upper layer can be delivered in “inventory and command” and “command-only” manners from A-IoT readers (e.g. User Equipment (UE) reader or RAN reader) , as “inventory-only” is expected to be used for inventory use case.
[0014] For “command-only” delivery manner, as the temporarily disabled devices are still receiving RF signals, they can determine whether they are the target devices. If they are, and if the command is an Enable command, the devices can enable themselves.
[0015] For “inventory and command” delivery manner, the temporarily disabled devices will receive an inventory request firstly (i.e., an A-IoT paging over the air) . In inventory procedure, the devices cannot differentiate whether the inventory is caused by a normal inventory or Enable command delivery. They can determine themselves as target devices in A-IoT paging. But they are not expected to respond to the inventory request, as their capabilities of transmitting RF signals are disabled. Without the device Identifier (ID) response, core network has no chance to deliver the Enable command towards those devices.
[0016] S2-2500425 mentions a solution with an explicit indicator in A-IoT paging to request temporarily disabled devices to respond. And thus, there is a dependency with 3GPP RAN2 group. Including such indicator in A-IoT paging may cause some security concerns as it is not protected. In addition, an A-IoT reader is involved to obtain the explicit indicator from one message and put it in another message. Therefore, the security issue is not solved by S2-2500425.
[0017] In view of the above security issue, the embodiments herein propose a method, apparatus and system for transferring the explicit indicator for an individual A-IoT device or a group of A-IoT devices in a Non-Access Stratum (NAS) message which is transparent to an A-IoT reader and the NAS message is securely protected by its nature. The A-IoT reader does not process the explicit indicator, which solves the security concern aforementioned.
[0018] According to a first aspect of the present disclosure, there proposes a method performed by an AIoT reader. The method comprises receiving, from a network node providing Ambient Internet of Things (A-IoT) service, a first message including a first indicator indicating that a response from an AIoT device in a disabled status is required. The first message is a Non-Access Stratum (NAS) message for an AIoT device. The method further comprises transmitting, to the AIoT device, the first message.
[0019] According to a second aspect of the present disclosure, there proposes a method performed by an AIoT device. The method comprises receiving, from an AIoT reader, a first message including a first indicator indicating that a response from an A-IoT device in a disabled status is required. The first message is a Non-Access Stratum (NAS) message for AIOT device. The method further comprises handling the first message.
[0020] According to a third aspect of the present disclosure, there proposes a method performed by a network node providing AIoT service. The method comprises transmitting, to an AIoT reader, a first message including a first indicator indicating that a response from an AIoT device in a disabled status is required. The first message is a Non-Access Stratum (NAS) message for an AIoT device.
[0021] According to a fourth aspect of the present disclosure, there proposes an AIoT reader. The AIoT reader comprises at least one processor and a non-transitory computer readable medium coupled to the at least one processor. The non-transitory computer readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to perform the above method according to the first aspect of the present disclosure.
[0022] According to a fifth aspect of the present disclosure, there proposes an AIoT device. The AIoT device comprises an energy harvester for harvesting energy, an energy storage for storing the harvested energy, and a digital logic for performing the above method according to the second aspect of the present disclosure. In some embodiments, the AIoT device may further include a memory. The digital logic may comprise a controller.
[0023] According to a sixth aspect of the present disclosure. There proposes a network node providing Ambient Internet of Things (AIoT) service. The network node comprises at least one processor and a non-transitory computer readable medium coupled to the at least one processor. The non-transitory computer readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to perform the method according to the third aspect of the present disclosure.
[0024] According to a seventh aspect of the present disclosure, there proposes a communication system. The communication system comprises one or more of the network node, the AIoT reader, and the AIoT device.
[0025] According to an eighth aspect of the present disclosure, there proposes a computer readable medium comprising computer readable code, which when run on an apparatus, causes the apparatus to perform any of the above method.
[0026] According to a ninth aspect of the present disclosure, there proposes a computer readable product comprising computer readable code, which when run on an apparatus, causes the apparatus to perform any of the above method.
[0027] The embodiments according to the above aspects of the present disclosure may allow an AIoT device in a disabled status to be enabled in a secured way without RAN impact, as RAN does not process the first indicator indicating that a response from the AIoT device in a disabled status is required.Brief Description of the Drawings
[0028] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments of the present disclosure and, together with the description, further serve to explain the principles of the disclosure and to enable a person skilled in the pertinent art to make and use the embodiments disclosed herein. In the drawings, like reference numbers indicate identical or functionally similar elements, and in which:
[0029] Figure 1 is a schematic diagram showing an 5G architecture to support Ambient IoT, in which the embodiments herein may be implemented;
[0030] Figure 2 is a schematic diagram showing another 5G architecture to support Ambient IoT, in which the embodiments herein may be implemented;
[0031] Figure 3 is a schematic signaling chart showing the messages for enabling AIoT device (s) , according to the embodiments herein;
[0032] Figure 4 is a schematic flow chart showing an example method in the network node providing AIoT service, according to the embodiments herein;
[0033] Figure 5 is a schematic flow chart showing an example method in the AIoT reader, according to the embodiments herein;
[0034] Figure 6 is a schematic flow chart showing an example method in the AIoT device, according to the embodiments herein;
[0035] Figure 7 is a schematic block diagram showing an example network node providing AIoT service, according to the embodiments herein;
[0036] Figure 8 is a schematic block diagram showing an example AIoT reader, according to the embodiments herein;
[0037] Figure 9 is a schematic block diagram showing an example AIoT device, according to the embodiments herein;
[0038] Figure 10 is a schematic block diagram showing an example communication system, according to the embodiments herein; and
[0039] Figure 11 is a schematic block diagram showing an example computer-implemented apparatus, according to the embodiments herein.Detailed Description of Embodiments
[0040] Embodiments herein will be described in detail hereinafter with reference to the accompanying drawings, in which embodiments are shown. These embodiments herein may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. The elements of the drawings are not necessarily to scale relative to each other.
[0041] Reference to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase “in an embodiment” appearing in various places throughout the specification are not necessarily all referring to the same embodiment.
[0042] As used in the description and the appended claims, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
[0043] As used throughout this description, and in the claims, a list of items joined by the term “at least one of” or “one or more of” can mean any combination of the listed terms. For example, the phrase “at least one of A, B or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.
[0044] Figure 1 is a schematic diagram showing an 5G architecture to support Ambient IoT, in which the embodiments herein may be implemented. Figure 2 is a schematic diagram showing another 5G architecture to support Ambient IoT, in which the embodiments herein may be implemented.
[0045] In the architectures shown in Figures 1 and 2, AIoT Function (AIOTF) 103 may enable / disable AIoT device 101 via AIoT reader 102 or 202, once a respective service operation request is received from Application Function (AF) 105 via Network Exposure Function (NEF) 102.
[0046] Note that, the AIOTF 103 shown in Figures 1 and 2 is an example of a network node providing AIoT service, such as executing an AIoT service request (e.g. inventory, read) in the network and handle any corresponding AIoT specific NAS messages, supporting inventory and message routing for AIoT devices 101, authorizing the AIoT service request, performing validation of AIoT device Identifier (ID) and securing AIoT device operations if needed, collecting AIoT data and aggregating reporting, and collecting charging information if required. The network node providing AIoT service may also be referred to, for example, as Ambient IoT Management Function (AIoTMF) , Ambient IoT Control Function (AIoTCF) , Ambient IoT Controller, AIoTF, etc.
[0047] Unified Data Management (UDM) 106 may manage subscription-like information for AIoT devices and service control information for third party application:
[0048] - An AIoT device ID is allocated to each AIoT device that has subscription-like information provisioned in the UDM. The AIoT device ID shall be unique within a mobile network, and it is used to locate the subscription-like information.
[0049] - The subscription-like information for an AIoT device is different from UE subscription data. The subscription-like information contains: AIoT device ID, security materials, and device status information e.g. last serving reader node, whether the AIoT device is disabled, etc.
[0050] - As part of a provisioning process for an AIoT device, the AIoT device is provided with its AIoT device ID, security materials and security settings which control what operations on which memory regions require what levels of security to be applied.
[0051] - The service control information is used to authorize the AF's device operation request. The service control information, based on service agreements between the network operator and the 3rd party AF, may contain: AF ID, allowed service area, allowed service operations, allowed AIoT device ID information etc.
[0052] The NEF 104 may expose 5GS AIoT capabilities so as to allow third party AF 105 to consume the AIoT services.
[0053] Note that, from AIoT device point of view, the interfaces with the network are the same for both Figure 1 and 2.
[0054] Note that, instead of UDM 106, Authentication Server Function (AUSF) 108 and / or AAA server 107 which is external to 5GC, may manage subscription-like information for AIoT devices including device credentials and service control information for the third party.
[0055] Figure 3 is a schematic signaling chart showing the messages for enabling AIoT device (s) , according to the embodiments herein. Figure 3 may be applicable to the architecture in both Figure 1 and Figure 2.
[0056] In an embodiment, the signaling chart in Figure 3 may include the following messages or steps:
[0057] Step 1. The AIoT device 101 is temporarily disabled by a Disable command.
[0058] Step 2. The AIOTF 103 within the core network receives an Enable request from the AF 105 (optionally via the NEF 104) and triggers Inventory Request towards reader 102 or 202.
[0059] The reader 102 or 202 can be a Base Station (BS) reader (areader within AIoT RAN) or a UE reader (aUE capable of handling Ambient IoT services) . The AIOTF 103 may send the inventory request to the reader 102 or 202 directly or via the Access and Mobility Management Function (AMF) .
[0060] Within the inventory request, a Device NAS message for the AIOT device 101 is included, containing device ID information identifying one or more devices, and a temporarily disabled device respond indicator. The temporarily disabled device respond indicator, indicating that a response from an AIoT device in a disabled status is required, is securely protected (encrypted) by the nature of NAS message.
[0061] The reader 102 or 202 sends Inventory Response towards the AIOTF 103.
[0062] Step 3. Reader 102 or 202 sends A-IoT Paging message with Device NAS message Inventory Request towards the AIoT device 101. The Inventory Request contains device ID information, and the temporarily disabled device respond indicator.
[0063] Step 4. The AIoT device 101 checks whether its permanent device ID stored in the device matches the received device ID information.
[0064] a. If yes and if the AIoT device is not disabled (permanent or temporarily disabled) , the AIoT device 101 generates a Device NAS message Inventory Response containing its device ID.
[0065] b. If yes but the AIoT device is temporarily disabled, the AIoT device 101 further checks if the temporarily disabled device respond indicator is received in the Inventory Request and / or its value. If the indicator is present and set to a specific value (e.g., 1 or true) , the AIoT device 101 generates a Device NAS message, i.e. Inventory Response containing its device ID. If the indicator is not present or set to another specific value (e.g., 0 or false) , the AIoT device 101 silently ignores or discards the Inventory Request.
[0066] c. otherwise, the AIoT device 101 silently ignores or discards the Inventory Request.
[0067] Step 5. The AIoT device 101 sends the Device NAS message, i.e. Inventory Response containing the device ID to the reader 102 or 202.
[0068] Step 6. The reader 102 or 202 sends an Inventory Report towards the AIOTF 103. The Device NAS message (Inventory Response) is included in the Inventory Report.
[0069] Step 7. The AIOTF 103 generates a Device NAS message, i.e. Enable Request which is to enable the responded AIoT device 101. The AIOTF 103 sends a Command Request towards the reader 102 or 202 containing the Device NAS message (Enable Request) . The Device ID is optionally included.
[0070] Step 8. The reader 102 or 202 delivers the Device NAS message, i.e. Enable Request towards the AIoT device 101. The device ID is optionally included.
[0071] Step 9. The AIoT device 101 executes the Enable Request. It enables itself and update its status stored in a NVM (non-volatile memory) within the device. It generates a Device NAS message, i.e. Enable Response based on the enable result.
[0072] Step 10. The AIoT device 101 sends the Device NAS message, i.e. Enable Response to the reader 102 or 202.
[0073] Step 11. The reader 102 or 202 sends a Command Response towards the AIOTF 103. The Device NAS message, i.e. Enable Response is included in the Command Response.
[0074] Figure 4 is a schematic flow chart showing an example method 400' in the network node providing AIoT service, according to the embodiments herein. In an embodiment, the flow chart in Figure 4 may be implemented in the AIOTF 103.
[0075] The method 400' begins with S401', in which the network node providing AIoT service transmits a first message to an AIoT reader, such as RAN reader 102 and UE reader 202, as shown in the step 2 of Figure 3. The first message may be an inventory request message. The first message includes a first indicator indicating that a response from an AIoT device in a disabled status is required.
[0076] In some embodiments, the first indicator may indicate that a response from an AIoT device in a disabled status is required when it is set to a first value (e.g. 1 or true) , while the first indicator may indicate that a response from an AIoT device in a disabled status is not required when it is set to a second value (e.g. 0 or false) other than the first value. In other embodiments, the first indicator may indicate that a response from an AIoT device in a disabled status is required when it is included in the first message while the first indicator may indicate that a response from an AIoT device in a disabled status is not required when it is not included in the first message.
[0077] The first message may be targeted to a specific AIoT device or one or more AIoT devices within a group of AIoT devices. When the first message is targeted to a specific AIoT device, the first message may include an AIoT device ID of the AIoT device. When the first message is targeted to one or more AIoT devices within a group of AIoT devices, the first message may include group information of the group of AIoT devices.
[0078] In some embodiments, the first message may be targeted to the AIoT device in a temporary disabled status or in a permanently disabled status. When the first message is targeted to the AIoT device in a permanently disabled status, the first message may further include a second indicator indicating that a response from the AIoT device in the permanently disabled status is required. In other embodiments, the first message may otherwise indicate that a response from the AIoT device in the permanently disabled status is required. For the architecture of Figure 1, in which the AIoT reader is a Radio Access Network (RAN) reader, the first message may be transmitted over Next Generation Application Protocol (NGAP) or another Application Protocol between Radio Access Network (RAN) and Core Network.
[0079] For the architecture of Figure 2, in which the AIoT reader is a User Equipment (UE) reader, the first inventory request message may be transmitted over UE Non-Access Stratum (NAS) message via Access and Mobility Management Function (AMF) and Next Generation Radio Access Network (NG-RAN) , or delivered over NGAP or another Application Protocol between RAN and Core Network from the network node providing AIoT service to the NG-RAN and then over Radio Resource Control (RRC) from NG-RAN to UE, or delivered over NGAP or another Application Protocol between RAN and Core Network from the network node providing AIoT service to the NG-RAN via AMF and then over RRC from NG-RAN to the UE reader.
[0080] Note that, the first message may be applicable to an AIoT device in any status, and is not limited to an AIoT device in temporary disabled status. For example, the AIoT device in status other than temporary disabled may not respond to this message. Otherwise, the AIoT device in status other than temporary disabled may also respond to this message, and the network node providing AIoT service (such as AIOTF 103) may perform a filter on the device (s) .
[0081] In some embodiments, the method 400 may proceed to S402', in which the network node providing AIoT service (such as AIOTF 103) may receive a second message indicating that the AIoT device is available or reachable (e.g. in a device state of temporarily disabled) , from the AIoT reader 102, 202, as shown in the step 6 of Figure 3. The second message may be an inventory response message.
[0082] In an embodiment, after receiving the second message, the network node providing AIoT service (such as AIOTF 103) may check a device status of the AIoT device, based on device information of the AIoT device as defined in a network node providing user data management (such as a Unified Data Management (UDM) 106) , and / or a network node providing Authentication and / or Authorization (such as an Authentication, Authorization, and Accounting (AAA) server 107, and / or an Authentication Server Function (AUSF) (108) ) . For example, if the device status is a temporary disabled status, the network node providing AIoT service may decide to transmit a third message for enabling the AIoT device. The third message may be a command message for enabling the AIoT device.
[0083] In some embodiments, the method 400' may proceed to S403', in which the network node providing AIoT service (such as AIOTF 103) may transmit a third message for enabling the AIoT device, to the AIoT reader, as shown in the step 7 of Figure 3. The third message may be transmitted responsive to receiving the second message. The third message may be a command message for enabling the AIoT device.
[0084] Note that, the third message is not limited to enabling the AIoT device, it may be a message aiming to permanently disable the AIoT device, temporarily disable the AIoT device, or enable the AIoT device.
[0085] In addition, the network node providing AIoT service (such as AIOTF 103) may update the device status of the AIoT device in a network node providing user data management (such as the UDM 106) , and / or a network node providing Authentication and / or Authorization (such as the AAA server 107 and / or the AUSF 108) . There are two options. That is, the network node providing AIoT service (such as AIOTF 103) may update the device status of the AIoT device, after sending the third message or after receiving a response to the third message. For example, the device status of the AIoT device may be updated as "enabled" , if the response to the third message shows that the AIoT device is enabled.
[0086] The above steps are only examples, and the network node providing AIoT service may perform any related actions described with respect to Figures 1 to 3.
[0087] Figure 5 is a schematic flow chart showing an example method 600' in the AIoT reader, according to some embodiments herein. In an embodiment, the flow chart in Figure 5 may be implemented in the AIoT RAN reader 102 or UE reader 202.
[0088] The method 600' begins with S601', in which the AIoT reader 102 or 202 receives, from a network node providing AIoT service, a first message, as shown in the step 2 of Figure 3. The first message includes the indicator indicating that a response from an AIoT device in a disabled status is required.
[0089] Then, the method 600' proceeds to S602', in which the AIoT reader 102 or 202 transmits, to the AIoT device, the first message including the indicator, in response to determining the first message includes the indicator indicating that a response from an AIoT device in a disabled status is required, as shown in the step 3 of Figure 3.
[0090] In some embodiments, the first message may be transmitted from the AIoT reader to the AIoT device in a RAN-to-UE Paging or Paging-like message (for RAN reader) or UE-to-UE Proximity Service message (for UE reader) .
[0091] In some embodiments, the method 600' may proceed to S603', in which the AIoT reader 102 or 202 may receive, from the network node providing AIoT service, a third message for enabling the AIoT device, as shown in the step 7 of Figure 3.
[0092] In some embodiments, the method 600' may proceed to S604', in which the AIoT reader 102 or 202 may transmit, to the AIoT device, the third message, as also shown in the step 8 of Figure 3.
[0093] In some embodiments, the method 600' may also comprise other steps not shown, such as the AIoT reader 102 or 202 may indicate, to the network node providing AIoT service, a completion of the inventory, as also shown in the step 6 of Figure 3.
[0094] The above steps are only examples, and the AIoT reader may perform any related actions described with respect to Figures 1 to 3.
[0095] Figure 6 is a schematic flow chart showing an example method 800' in the AIoT device, according to the embodiments herein. In an embodiment, the flow chart in Figure 8 may be implemented in the AIoT device 101.
[0096] The method 800' begins with step S801', in which the AIoT device 101 receives, from an AIoT reader 102 or 202, a first message including a first indicator indicating that a response from an AIoT device in a disabled status is required, as shown in the step 3 of Figure 3.
[0097] Then, the method 800' proceeds to step S802', in which the AIoT device 101 handles the first message accordingly. As an example, the AIoT device is in temporary disabled status, the AIoT device may perform a random access like procedure; and / or send out its device ID, as shown in the step 5 of Figure 3. As another example, the AIoT device may ignore or discard the first message. As another example, the AIoT device may ignore or discard the first message, if the AIoT device is permanently disabled regardless of the first indicator.
[0098] The above steps are only examples, and the AIoT device may perform any related actions described with respect to Figures 1 to 3.
[0099] For the sake of brevity, methods of interaction with other network functions and application functions which have been described in PCT / CN2024 / 123241 will not be detailed herein.
[0100] Figure 7 is a schematic block diagram showing an example network node 1300 providing AIoT service, according to the embodiments herein. In an embodiment, the network node 1300 providing AIoT service in Figure 7 may be implemented as the AIOTF 103.
[0101] In an embodiment, the network node 1300 providing AIoT service may comprise at least one processor 1301; and a non-transitory computer readable medium 1302 coupled to the at least one processor 1301. The non-transitory computer readable medium 1302 may contain instructions executable by the at least one processor 1301, whereby the at least one processor 1301 may be configured to perform the above method 400'.
[0102] Note that, the network node 1300 providing AIoT service may be implemented as hardware, software, firmware and any combination thereof. For example, the network node 1300 providing AIoT service may include a plurality of units, logics, circuities, modules or the like, each of which may be used to perform one or more steps of the example method 400' or one or more steps shown in Figure 3 related to the network node providing AIoT service.
[0103] Figure 8 is a schematic block diagram showing an example AIoT reader 1400, according to the embodiments herein. In an embodiment, the AIoT reader 1400 in Figure 8 may be implemented as the AIoT RAN reader 102 or UE reader 202.
[0104] In an embodiment, the AIoT reader 1400 may comprise at least one processor 1401; and a non-transitory computer readable medium 1402 coupled to the at least one processor 1401. The non-transitory computer readable medium 1402 may contain instructions executable by the at least one processor 1401, whereby the at least one processor 1401 may be configured to perform the above method 600'.
[0105] Note that, the AIoT reader 1400 may be implemented as hardware, software, firmware and any combination thereof. For example, the AIoT reader 1400 may include a plurality of units, logics, circuities, modules or the like, each of which may be used to perform one or more steps of the example method 600' or one or more steps shown in Figure 3 related to the AIoT reader.
[0106] Figure 9 is a schematic block diagram showing an example AIoT device 1500, according to the embodiments herein. In an embodiment, the AIoT device 1500 in Figure 9 may be implemented as the AIoT device 101.
[0107] In an embodiment, the AIoT device 1500 may comprise an energy harvester 1501 for harvesting energy; an energy storage 1502 for storing the harvested energy; and a digital logic 1503 for performing any of the above method related to the AIoT device.
[0108] In an embodiment, the digital logic 1503 may include functional blocks like encoder, decoder, controller, etc.
[0109] In an embodiment, the AIoT device 1500 may comprise a memory, for example the memory may include two types of memory: 1) Non-Volatile Memory (NVM) such as Electrically Erasable Programmable Read-Only Memory (EEPROM) for permanently storing device ID, etc., and 2) registers for temporarily keeping any information required for its operation while energy is available in energy storage.
[0110] In an embodiment, the AIoT device 1500 may comprise power management unit (PMU) , which manages storing energy to energy storage from energy harvester and supplying power to active component blocks which needs power supply.
[0111] In an embodiment, the AIoT device 1500 may comprise reception related blocks such as Band Pass Filter (BPF) for improving selectivity, envelope detector for converting radio frequency signal to baseband, and Low Pass Filter (LPF) for filtering out harmonics and high frequency components to improve input signal quality.
[0112] In an embodiment, the AIoT device 1500 may comprise transmission related blocks such as Backscatter modulator for switching impedance to modulate backscattered signal with transmitted signal from digital logic 1503.
[0113] Note that, the AIoT device 1500 may include a plurality of units, logics, circuities, modules or the like, each of which may be used to perform one or more steps of the example method 800' or one or more steps shown in Figure 3 related to the AIoT device; the details of the example AIoT device may be referred to 3GPP TR 38.769 v19.0.0, section 5, "Ambient IoT device architectures" .
[0114] Figure 10 is a schematic block diagram showing an example communication system 1800, according to the embodiments herein.
[0115] In an embodiment, the communication system 1800 may comprise the example network node 1300 providing AIoT service, the example AIoT reader 1400, the example AIoT device 1500. In an embodiment, the communication system 900 may further comprise the network node implementing network exposure function, and the network node implementing application function.
[0116] In an embodiment, the communication system 1800 may be configured in an Over-The-Top (OTT) scenario. The OTT connection may be transparent in the sense that the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
[0117] It should also be understood that, a network element (such as the example network node 1300 providing AIoT service, the network node implementing network exposure function, and the network node implementing application function, the RAN reader 102) can be implemented either as a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., on a cloud infrastructure.
[0118] Figure 11 is a schematic block diagram showing an example computer-implemented apparatus 1900, according to the embodiments herein. In an embodiment, the apparatus 1900 may be configured as the above mentioned apparatus, such as the AIoT device 101, the AIoT reader 102, 202, the AIOTF 103, the NEF 104, and / or the AF 105.
[0119] In an embodiment, the apparatus 1900 may include but not limited to at least one processor such as Central Processing Unit (CPU) 1901, a computer-readable medium 1902, and a memory 1903. The memory 1903 may comprise a volatile (e.g., Random Access Memory, RAM) and / or non-volatile memory (e.g., a hard disk or flash memory) . In an embodiment, the computer-readable medium 1902 may be configured to store a computer program and / or instructions, which, when executed by the processor 1901, causes the processor 1901 to carry out any of the above mentioned methods.
[0120] In an embodiment, the computer-readable medium 1902 (such as non-transitory computer readable medium) may be stored in the memory 1903. In another embodiment, the computer program may be stored in a remote location for example computer program product 1904 (also may be embodied as computer-readable medium) , and accessible by the processor 1901 via for example carrier 1905.
[0121] The computer-readable medium 1902 and / or the computer program product 1904 may be distributed and / or stored on a removable computer-readable medium, e.g. diskette, CD (Compact Disk) , DVD (Digital Video Disk) , flash or similar removable memory media (e.g. compact flash, SD (secure digital) , memory stick, mini SD card, MMC multimedia card, smart media) , HD-DVD (High Definition DVD) , or Blu-ray DVD, USB (Universal Serial Bus) based removable memory media, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or distributed as a propagated signal via a network (e.g. Ethernet, ATM, ISDN, PSTN, X. 25, Internet, Local Area Network (LAN) , or similar networks capable of transporting data packets to the infrastructure node) .
[0122] It will be recognized that principles of the disclosure are not limited to the embodiments so described, but instead can be practiced with modification and alteration without departing from the scope of the appended claims. The above embodiments may include the undertaking only a subset of such features, undertaking a different order of such features, undertaking a different combination of such features, and / or undertaking additional features than those features explicitly listed. The scope of the embodiments should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Claims
1.A method (600') performed by an Ambient Internet of Things (AIoT) reader (102, 202) , comprising:- receiving (S601') , from a network node (103) providing Ambient Internet of Things (AIoT) service, a first message including a first indicator indicating that a response from an AIoT device (101) in a disabled status is required, wherein the first message is a Non-Access Stratum (NAS) message for an AIoT device (101) ; and- transmitting (S602') , to the AIoT device (101) , the first message.2.The method (600') according to claim 1, wherein the AIoT reader (102, 202) is a Radio Access Network (RAN) reader (102) or a User Equipment (UE) reader (202) .3.The method (600') of claim 2, wherein the AIoT reader (102, 202) is a Radio Access Network (RAN) reader (102) , andwherein the first message is received from the network node (103) providing Ambient Internet of Things (AIoT) service over Next Generation Application Protocol (NGAP) or another Application Protocol between Radio Access Network (RAN) and Core Network.4.The method (600') of claim 2 or 3, wherein the AIoT reader (102, 202) is a User Equipment (UE) reader (202) , andwherein the first message is received via Access and Mobility Management Function (AMF) and Next Generation Radio Access Network (NG-RAN) , or delivered over NGAP or another Application Protocol between RAN and Core Network from the network node providing AIoT service to the NG-RAN and then over Radio Resource Control (RRC) from NG-RAN to UE, or delivered over NGAP or another Application Protocol between RAN and Core Network from the network node providing AIoT service to the NG-RAN via AMF and then over RRC from NG-RAN to the UE reader.5.The method (600') of any of claims 1 to 4, wherein the first message is transmitted from the AIoT reader (102, 202) to the AIoT device (101) in a paging message or a proximity service message.6.The method (600') according to claims 1 to 5, further comprising:- receiving (S603') , from the network node (103) providing Ambient Internet of Things (AIoT) service, a third message for enabling the AIoT device (101) ; and- transmitting (S604') , to the AIoT device (101) , the third message.7.The method (600') according to claim 6, wherein the third message is a NAS message for the AIoT device (101) .8.The method (600') of any of claims 1 to 7,wherein the first message is targeted to a specific AIoT device (101) , and the first message includes an AIoT device ID of the AIoT device (101) , orwherein the first message is targeted to one or more AIoT devices (101) within a group of AIoT devices (101) , and the first message includes group information of the group of AIoT devices (101) .9.The method (600') according to any of claims 1 to 8, wherein the first message is targeted to the AIoT device (101) in a temporarily disabled status or in a permanently disabled status.10.The method (600') of claim 9, wherein the first message is targeted to the AIoT device (101) in a permanently disabled status, andwherein the first message further includes a second indicator indicating that a response from the AIoT device (101) in the permanently disabled status is required.11.A method (800') performed by an Ambient Internet of Things (AIoT) device (101) , comprising:- receiving (S801') , from an AIoT reader (102, 202) , a first message including a first indicator indicating that a response from an AIoT device (101) in a disabled status is required, wherein the first message is a Non-Access Stratum (NAS) message; and- handling (S802') the first message.12.The method (800') of claim 11, wherein handling (S802') the first message comprises:- obtaining the first indicator from the first message.13.The method (800') of claim 11 or 12, wherein the first message further comprises: a device ID of the AIoT device (101) , and handling (S802') the first message comprises:- obtaining the device ID of the AIoT device (101) from the first message; and- in response to the obtained device ID being matched with the AIoT device (101) 's own device ID, transmitting to a network node (103) providing Ambient Internet of Things (AIoT) service via the AIoT reader (102, 202) the device ID of the AIoT device in a NAS message based on a status of the AIoT device (101) .14.The method (800') according to claim 13, wherein the status of the AIoT device (101) is not disabled, the device ID of the AIoT device is transmitted to the network node (103) providing Ambient Internet of Things (AIoT) service via the AIoT reader (102, 202) in a NAS message.15.The method (800’ ) according to claim 13, wherein the status of the AIoT device (101) is temporarily disabled, the device ID of the AIoT device is transmitted to the network node (103) providing Ambient Internet of Things (AIoT) service via the AIoT reader (102, 202) in a NAS message in response to the first indicator indicating that a response from an AIoT device (101) in a disabled status is required.16.The method (800') according to claim 13, wherein the status of the AIoT device (101) is temporarily disabled, handling (S802') the first message further comprises: discarding the first message in response to the first indicator indicating that a response from an AIoT device (101) in a disabled status is not required.17.The method (800') according to claim 13, wherein the status of the AIoT device (101) is permanently disabled, handling (S802') the first message further comprises: discarding the first message.18.The method (800') of any of claims 11 to 17, wherein the first message is received in a paging message or a proximity service message.19.The method (800') according to any of claims 11 to 18, further comprising:- receiving (S803') , from the AIoT reader (102, 202) , a third message for enabling the AIoT device (101) .20.The method (800') according to claim 18, wherein the third message is a NAS message.21.A method (400') performed by a network node (103) providing Ambient Internet of Things (AIoT) service, comprising:- transmitting (S401') , to an AIoT reader (102, 202) , a first message including a first indicator indicating that a response from an AIoT device (101) in a disabled status is required,wherein the first message is a Non-Access Stratum (NAS) message for an AIoT device (101) .22.The method (400') according to claim 21, wherein the AIoT reader (102, 202) is a Radio Access Network (RAN) reader (102) or a User Equipment (UE) reader (202) .23.The method (400') of claim 22, wherein the AIoT reader (102, 202) is a Radio Access Network (RAN) reader (102) , andwherein the first message is transmitted (S401') over Next Generation Application Protocol (NGAP) or another Application Protocol between Radio Access Network (RAN) and Core Network.24.The method (400') of claim 22, wherein the AIoT reader (102, 202) is a User Equipment (UE) reader (202) , andwherein the first message is transmitted (S401') via Access and Mobility Management Function (AMF) and Next Generation Radio Access Network (NG-RAN) , or delivered over NGAP or another Application Protocol between RAN and Core Network from the network node providing AIoT service to the NG-RAN and then over Radio Resource Control (RRC) from NG-RAN to UE, or delivered over NGAP or another Application Protocol between RAN and Core Network from the network node providing AIoT service to the NG-RAN via AMF and then over RRC from NG-RAN to the UE reader.25.The method (400') according to any of claims 21 to 24, further comprising:- transmitting (S403') , to the AIoT reader (102, 202) , a third message for enabling the AIoT device (101) .26.The method (400') according to claim 25, wherein the third message is a NAS message for the AIoT device (101) .27.The method (400') according to claim 25 or 26, further comprising:after transmitting (S401') the first message,- receiving (S402') , from the AIoT reader (102, 202) , a second message indicating that the AIoT device (101) is available;wherein transmitting (S403') the third message is responsive to receiving (S402') the second message.28.The method (400') according to any of claims 21 to 27,wherein the first message is targeted to a specific AIoT device (101) , and the first message includes an AIoT device ID of the AIoT device (101) , orwherein the first message is targeted to one or more AIoT devices (101) within a group of AIoT devices (101) , and the first message includes group information of the group of AIoT devices (101) .29.The method (400') according to any of claims 21 to 28, wherein the first message is targeted to the AIoT device (101) in a temporary disabled status or in a permanently disabled status.30.The method (400') of claim 29, wherein the first message is targeted to the AIoT device (101) in a permanently disabled status, andwherein the first message further includes a second indicator indicating that a response from the AIoT device (101) in the permanently disabled status is required.31.An Ambient Internet of Things (AIoT) reader (1400) , comprising:- at least one processor (1401) ; and- a non-transitory computer readable medium (1402) coupled to the at least one processor (1401) , the non-transitory computer readable medium (1402) contains instructions executable by the at least one processor (1402) , whereby the at least one processor (1401) is configured to perform the method (600') according to any of claims 1 to 10.32.An Ambient Internet of Things (AIoT) device (1500) , comprising:- an energy harvester (1501) , for harvesting energy;- an energy storage (1502) , for storing the harvested energy; and- a digital logic (1503) , for performing the method (800') according to any of claims 11 to 20.33.A network node (1300) providing Ambient Internet of Things (AIoT) service, comprising:- at least one processor (1301) ; and- a non-transitory computer readable medium (1302) coupled to the at least one processor (1301) , the non-transitory computer readable medium (1302) contains instructions executable by the at least one processor (1302) , whereby the at least one processor (1301) is configured to perform the method (400') according to any of claims 21 to 30.34.A communication system (1800) , comprising:- the AIoT reader (1400) according to claim 31;- the AIoT device (1500) according to claim 32; and- the network node (1300) providing Ambient Internet of Things (AIoT) service according to claim 33.35.A computer readable medium (1902) comprising computer readable code, which when run on an apparatus (1900) , causes the apparatus (1900) to perform the method (400', 600', 800') according to any of claims 1 to 30.36.A computer readable product (1904) comprising computer readable code, which when run on an apparatus (1900) , causes the apparatus (1900) to perform the method (400', 600', 800') according to any of claims 1 to 30.
Citation Information
Patent Citations
Handling HARQ feedback in internet of things (IOT)
EP4224761A2
Mobile device feature disablement
US20190149652A1
User authentication in wireless access network
US20200382959A1
Permanently disabling a terminal device
US20240260115A1