A-IoT device identity

Abstract

Example embodiments of the present disclosure relate to ambient Internet of Things (A-IoT) device identification. A method includes measuring, in an environment, a reflected signal of a radio frequency (RF) signal, the RF signal being transmitted from a first apparatus; determining, based on the measuring, that an entity is present in the environment, the entity performing a communication of an ambient Internet of Things (A-IoT) type; and determining a power-on characteristic of the entity, the power-on characteristic being configured to determine whether the entity is a valid A-IoT device.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure are generally related to the telecommunications field, and more particularly to methods, apparatuses, devices, and computer-readable storage media for identifying Ambient Internet of Things (A-IoT) devices. Background Technology

[0002] A communication network can be used as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network. Communication networks can operate according to standards provided by organizations such as the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of standards provided by 3GPP are the so-called 3GPP standards for cellular technology generations, such as those for 4G, 5G, and 6G technologies. Summary of the Invention

[0003] In a first aspect of this disclosure, a first device is provided. The first device includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first device to: measure a reflected signal of a radio frequency (RF) signal transmitted from the first device in an environment; determine, based on the measurement, that an entity exists in the environment, the entity performing environmental Internet of Things (A-IoT) type communication; and determine the electrical characteristics of the entity, the electrical characteristics being configured to determine whether the entity is a valid A-IoT device.

[0004] In a second aspect of this disclosure, a second device is provided. The second device includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second device to: receive, from a first device, the power-on characteristics of an entity, the entity performing ambient Internet of Things (A-IoT) type communication; and, based on the power-on characteristics, determine whether the entity is a valid A-IoT device.

[0005] In a third aspect of this disclosure, a method is provided. The method includes: measuring a reflected signal of a radio frequency (RF) signal transmitted from the first device in an environment; determining, based on the measurement, that an entity exists in the environment and that the entity performs environmental Internet of Things (A-IoT) type communication; and determining the electrical characteristics of the entity, the electrical characteristics being configured to determine whether the entity is a valid A-IoT device.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving, at a second device, the power-on characteristics of an entity from a first device, the entity performing ambient Internet of Things (A-IoT) type communication; and determining, based on the power-on characteristics, whether the entity is a valid A-IoT device.

[0007] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for measuring a reflected signal of a radio frequency (RF) signal transmitted from the first apparatus in an environment; components for determining, based on the measurement, that an entity exists in the environment, the entity performing environmental Internet of Things (A-IoT) type communication; and components for determining the electrical characteristics of the entity, the electrical characteristics being configured to determine whether the entity is a valid A-IoT device.

[0008] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving the energizing characteristics of an entity from a first apparatus, the entity performing environmental Internet of Things (A-IoT) type communication; and components for determining whether the entity is a valid A-IoT device based on the energizing characteristics.

[0009] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a third aspect.

[0010] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.

[0011] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0012] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 The signaling flow for an example procedure for A-IoT device identification according to some example embodiments of this disclosure is shown; Figure 3 Signaling flows for an example process for identifying benign A-IoT devices according to some example embodiments of this disclosure are shown; Figure 4 Signaling flows for an example process for spoofing A-IoT device identifiers according to some example embodiments of this disclosure are shown; Figure 5 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 6 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 7 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 8 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0013] Throughout all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0014] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0015] In the following description and claims, unless otherwise defined, all 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 pertains.

[0016] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, whether explicitly described or not, it is believed that incorporating other embodiments to affect such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0017] It should be understood that although the terms "first," "second," etc., preceding the noun(s) may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another, and they do not restrict the order of the noun(s). For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0018] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0019] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0020] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are also intended to include the plural forms. It will be further understood that the terms “comprising,” “including,” “having,” “containing,” “comprise,” and / or “containing” as used herein specify the presence of the stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0021] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors working together to enable a device (such as a mobile phone or server) to perform various functions), software, and (multiple) memory), and (c) The operation of the hardware circuitry and / or processors, such as microprocessors or a portion thereof, requires software (e.g., firmware) for operation, but the software may not be present when operation is not required.

[0022] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers implementations of hardware circuitry or processors (or processors) or a portion thereof and their accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits used in mobile devices or servers, cellular network devices or other computing or networking devices.

[0023] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. The scope of this disclosure should not be construed as limited to the aforementioned systems.

[0024] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header End (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femto, pico, or non-terrestrial network (NTN)) or non-terrestrial network equipment (such as satellite network equipment), low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites, spacecraft network equipment, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves as a UE facing the parent node, and the DU portion of the IAB node behaves as a base station facing the next-hop IAB node.

[0025] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal equipment may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.

[0026] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0027] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure can be implemented is shown. In communication environment 100, multiple communication devices (including terminal device 110 and network device 120) can communicate with each other. Figure 1 In the example, terminal device 110 can be a UE, and network device 120 can be a base station serving the UE.

[0028] In environment 100, one or more radio frequency (RF) sources may be present, such as RF source 111. Terminal device 110 and / or network device 120 may also be RF sources. RF sources may transmit one or more RF signals in environment 100. The transmitted RF signals may be reflected by one or more environmental objects in environment 100, such as environmental objects 130-1, 130-2, 130-3, and 130-4. For example, buildings, vehicles, and people may be environmental objects in environment 100. RF signals may be reflected back to their corresponding transmitters. Figure 1 As shown, the RF signal sent from the terminal device 110 can be reflected by environmental objects and returned to the terminal device 110.

[0029] Within environment 100, there may be one or more entities, such as entity 115, that perform environmental Internet of Things (A-IoT) type communication. A-IoT type communication may be associated with one or more characteristics of A-IoT devices, such as energy harvesting from environment 100, task-specific RF signal transmission, A-IoT device identifier transmission, etc.

[0030] A-IoT devices can be very low-power devices that do not have their own power supply but are powered by harvesting energy from environmental sources such as radio transmitters. Once an A-IoT device has received and stored enough energy to perform its designed (hereafter referred to as "energized") function, it can perform that function, and in doing so, it can consume the stored energy and return to a de-energized state. This may also be referred to below as an energization event or process. During an energization event or process, the A-IoT device can harvest energy from the environment and use the harvested energy to send task-specific signals. The A-IoT device can harvest energy from one or more RF signals transmitted in environment 100 (e.g., RF signals transmitted from terminal device 110 or RF source 111).

[0031] The entity performing A-IoT type communication can be a valid A-IoT device, a malicious A-IoT device, or a spoofed A-IoT device. Malicious A-IoT devices and / or spoofed A-IoT devices can be, for example, software-defined radio devices controlled by an attacker or any unauthorized A-IoT device. For example, in Figure 1 In this context, Entity 115 can be a valid A-IoT device that harvests energy from the environment. Alternatively, Entity 115 can be a malicious A-IoT device or a counterfeit A-IoT device that harvests energy from the environment. Alternatively, Entity 115 can be a counterfeit A-IoT device that does not harvest energy from the environment but instead sends counterfeit A-IoT device identifiers and / or counterfeit task-specific signals.

[0032] In some examples, entity 115 can be an effective A-IoT device that harvests energy from RF signals transmitted by terminal device 110. The RF signals transmitted from terminal device 110 can be partially harvested by entity 115 so that the RF signals reflected back to terminal device 110 can be attenuated.

[0033] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in communication environment 100. Note that although shown as a base station, network device 120 may be another device besides a base station. Although illustrated as a UE, terminal device 110 may be another device besides a UE.

[0034] In the following description, for illustrative purposes, some example embodiments are depicted in which terminal device 110 operates as a UE and network device 120 operates as a base station. However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other devices, and the operations described in connection with the network device can be implemented at the terminal device or other devices.

[0035] In some example embodiments, the transmission direction from network device 120 to terminal device 110 is referred to as the downlink (DL), and the transmission direction from terminal device 110 to network device 120 is referred to as the uplink (UL). In the DL, network device 120 is a transmitting (TX) device (or transmitter), and terminal device 110 is a receiving (RX) device (or receiver). In the UL, terminal device 110 is a TX device (or transmitter), and network device 120 is an RX device (or receiver).

[0036] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols, wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or to be developed in the future.

[0037] Currently, the identification of A-IoT devices can primarily rely on identifiers claimed by the A-IoT devices themselves. However, malicious and counterfeit A-IoT devices may provide spoofed identifiers to impersonate legitimate A-IoT devices, thereby reducing the reliability of these identifiers. Furthermore, A-IoT devices may have very low power consumption and may only be "on" infrequently for very short periods. Therefore, it may be difficult for A-IoT devices to provide a reliable identifier during operation, as secure identification methods, such as public-key cryptography, may not be available for short periods of activity.

[0038] According to some example embodiments of this disclosure, a solution for A-IoT device identification is provided. In one method, a first device measures a reflected signal of an RF signal transmitted from the first device in an environment, and based on the measurement, determines that an entity exists in the environment and that the entity performs A-IoT type communication. The first device also determines the entity's power-on characteristics, and the power-on characteristics are configured to determine whether the entity is a valid A-IoT device.

[0039] Using this solution, as an alternative or addition to the A-IoT device identifier, the power-on characteristic can be used for A-IoT device identification, thereby improving the reliability of A-IoT device identification.

[0040] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0041] Figure 2 The signaling flow for an example process 200 for A-IoT device identification, according to some example embodiments of this disclosure, is shown. For example... Figure 2 As shown, process 200 involves a first device 201 and a second device 202. For discussion purposes, reference is made to... Figure 1 To describe process 200. The first device 201 may be an example of terminal device 110 or be included in terminal device 110. The second device 202 may be an example of network device 120 or be included in network device 120.

[0042] In process 200, a first device 202 measures the reflected signal of an RF signal 210 emitted from an environment. The environment in which the first device 201 measures the reflected RF signal may include one or more RF sources, such as the first device 201. One or more entities performing A-IoT type communication (such as a legitimate A-IoT device, a malicious A-IoT device, or a counterfeit A-IoT device) may or may not be present in the environment. One or more entities may harvest energy from one or more RF signals emitted from one or more RF sources. A second device 202 may or may not be located in the same environment. (Reference) Figure 1 The environment in which the first device 201 and the entity performing A-IoT type communication are located can be Figure 1 An example or part of the communication environment 100 in the text.

[0043] In some cases, the first device 201 determines, based on measurements, that an entity performing A-IoT type communication exists in the environment. In some embodiments, if measurements indicate attenuation of an RF signal, the first device 201 may determine that an entity performing A-IoT type communication exists in the environment.

[0044] As described above, the energy harvested from RF signals in the environment can be an important characteristic of A-IoT type communication, allowing the attenuation of the RF signal level to indicate the presence of an entity performing A-IoT type communication. For example, if the attenuation of the RF signal meets a predefined signal level and / or a predefined attenuation level, the first device 201 can determine that an entity performing A-IoT type communication exists in the environment.

[0045] Alternatively or additionally, the first device 201 may determine that the entity performing A-IoT type communication exists in the environment based on the detection of task-specific RF signal transmissions and / or the A-IoT device identifier provided by the entity.

[0046] In some other cases ( Figure 2 (Not shown in the image) The first device 201 can determine that there is currently no A-IoT type communication in the environment. For example, if the reflected RF signal is at the expected signal strength level, indicating that there is no attenuation due to energy harvesting, the first device 201 can determine that there is currently no A-IoT type communication in the environment.

[0047] If it is determined that an entity performing A-IoT type communication is currently present in the environment, the first device 201 further determines 214 the entity's power-on characteristics, and the power-on characteristics are configured to determine whether the entity is a valid A-IoT device. Power-on characteristics can refer to one or more characteristics of a power-on event. Power-on characteristics may also be referred to as a power-on profile below.

[0048] A power-on event can refer to an event or operation in which an A-IoT device, initially unpowered (powered or unpowered), begins harvesting energy from the environment, continues harvesting energy until its internal energy storage is fully charged for device operation, and consumes that energy by performing its designated task and sending RF signals as task output. For example, a power-on event may include an energy harvesting phase and / or a task execution phase.

[0049] In some embodiments, the power-on characteristic may be associated with the duration of a power-on event. As an example, the power-on characteristic may include the duration during which an A-IoT device (active or inactive) switches from a non-power-on state to a power-on state. As another example, the power-on characteristic may include the complete duration from the start of energy harvesting to the end of the task.

[0050] Alternatively or additionally, energizing characteristics may be associated with patterns or distributions of energizing events. A pattern or distribution may indicate one or more characteristics of the energizing event process. For example, a pattern or distribution may be a power delivery distribution of energy harvesting, indicating changes in power delivery over time during the energizing process.

[0051] Alternatively or additionally, power-on characteristics may be correlated with the energy harvesting rate of a power-on event. For example, power-on characteristics may include the energy absorption rate of a (active or inactive) A-IoT device and the potential variation of that rate during the power-on period.

[0052] By utilizing power-on characteristics, it is possible to determine whether an entity performing A-IoT type communication is a valid A-IoT device. In some embodiments, if the power-on characteristics are determined to match predefined power-on characteristics, the entity can be determined to be a valid A-IoT device. For example, if the entity's power-on characteristics match a specific duration, mode, and / or energy harvesting rate, the entity can be determined to be a valid A-IoT device.

[0053] In some embodiments, predefined power-on characteristics can correspond to the type of A-IoT device. Specific durations, patterns, and / or energy harvesting rates can be specific to a type of A-IoT device, and a match with that type-specific power-on characteristic can indicate that an entity is a valid A-IoT device. For example, a UE can verify that an entity performing communication of an A-IoT device type via RF is indeed the correct type of A-IoT device. Additionally, depending on behavioral differences within a device type, an A-IoT device can be identified as a specific device of that type. In other words, if the measurable device characteristics are variable and sufficiently specific, devices of the same type can be distinguished, thus enabling the device power-on behavior to act as a physically unclonable function.

[0054] In some embodiments, if a power-on characteristic is determined to match identification information provided by an entity, the entity can be determined to be a valid A-IoT device. For example, the identification information provided by the entity may correspond to one or more specific power-on characteristics. If the determined power-on characteristic matches the power-on characteristics(s) of an entity-specific identifier, the entity can be determined to be a valid A-IoT device.

[0055] In some embodiments, the verification of an entity based on its electrical characteristics can be performed by the first device 201 ( Figure 2 (Not shown in the image) is executed. In some embodiments, the first device 201 may also receive identification information provided by an entity or network device (e.g., the second device 202).

[0056] In some embodiments, verification of an entity based on its electrical characteristics can be performed by the second device 202. For example... Figure 2 As shown, the first device 201 can send the power-on characteristics of an entity 216 to the second device 202. The second device 202 can receive the power-on characteristics of the entity 218 and use them to determine whether the entity 220 is a valid A-IoT device. In some embodiments, the first device 201 can receive a request for the power-on characteristics of an entity from the second device 202 and send the power-on characteristics as a response 216 to the second device 202. In some embodiments, the second device 202 can also receive identification information from the entity for verifying whether the entity is a valid A-IoT device.

[0057] Referring to process 200, a solution for A-IoT device identification according to embodiments of the present disclosure is described. The proposed solution can increase the reliability of the A-IoT device identity by combining A-IoT device power-on characteristics (such as process duration and / or power-on distribution during power-on) with potentially spoofable A-IoT identity claims. For example, power-on events of an entity performing A-IoT type communication can be distributed by power-on characteristics, such as their start and end times, and ideally, the power delivery measured in fine granularity between these times.

[0058] The proposed solution enhances the reliability of A-IoT device identifiers by providing a way to improve the credibility of spoofable A-IoT device identifiers through combining measurements of existing device power-on events with the stated A-IoT identifier. For example, with a pre-created database supporting A-IoT device power-on characteristics and / or patterns, the UE can verify that the entity performing communication of the A-IoT device type via RF is indeed the correct type of A-IoT device, and not, for example, a malicious actor using software-defined radio to spoof A-IoT identifiers.

[0059] Furthermore, the proposed solution enables A-IoT device identification in a more efficient and simpler manner. For example, some near-field power delivery techniques, such as inductive and capacitive coupling, can provide easier visibility into powered power delivery, while far-field power delivery techniques, such as 6G RF acquisition from the UE, may require additional contextual information (such as A-IoT / UE location and / or, for example, an A-IoT device energy harvesting estimate inferred from ambient radio reflections) to verify the A-IoT device. However, the solution utilizing the proposed A-IoT device identification may eliminate the need for additional contextual information such as A-IoT / UE location.

[0060] Figure 3 Signaling flow for example procedure 300 for benign A-IoT device identification according to some example embodiments of this disclosure is shown. Procedure 300 relates to A-IoT device 301, UE 302, and network entity 303. Procedure 300 may be an example of procedure 200. UE 302 may be... Figure 2 An example of the first device 201 in the example, and network entity 303 may be Figure 2 Example of the second device 202 in the example.

[0061] like Figure 3 As shown, at 311, UE 302 can move to the vicinity of A-IoT device 301. At 312, A-IoT device 301 can harvest energy from the RF signal transmitted from UE 302, and a measurable power-on event can begin. At 313, while power-on of A-IoT device 301 is in progress, UE 302 can measure energy harvesting. UE 302 can determine the power-on characteristics or distribution of the power-on event of A-IoT device 301.

[0062] At 314, A-IoT device 301 can send its identification information to network entity 303. For example, the A-IoT device identifier and / or task-specific data of A-IoT device 301 can be provided to network entity 303.

[0063] At 315, UE 302 can send the A-IoT device power distribution to network entity 303, and then at 316, network entity 303 can determine that the entity is a valid A-IoT device based on the determination that the A-IoT device identifier matches the power distribution.

[0064] Figure 4 Signaling flows for an example process 400 for spoofing A-IoT device identifiers according to some example embodiments of this disclosure are shown. Reference will be made to this example process 400 for spoofing A-IoT device identifiers for discussion purposes. Figure 3Describe process 400. Process 400 involves impersonating A-IoT device 401, UE 302, and network entity 303. Process 400 can be an example of process 200.

[0065] In process 400, at point 411, UE 302 may move to the vicinity of the spoofed A-IoT device 401. At a first time point, the spoofed A-IoT device 401 may not harvest energy from the RF signal transmitted by UE 302, resulting in no measurable power-on event initiating. However, at point 412, UE 302 may continue to measure / monitor energy harvesting. At a second time point, the spoofed A-IoT device 401 may begin harvesting energy from the RF signal transmitted by UE 302. UE 302 may determine the power-on characteristics or distribution of the power-on events of the spoofed A-IoT device 401. For example, the time points may be recorded as power-on characteristics of the spoofed A-IoT device 401.

[0066] At point 413, the spoofed A-IoT device 401 can send its identification information to network entity 303. For example, the spoofed A-IoT device identifier and / or data controlled by the attacker can be provided to network entity 303.

[0067] At 414, network entity 303 may send a power-on buffer data request to UE 302. At 415, UE 302 may send a buffered power-on distribution as a response to network entity 303. Then at 416, network entity 303 may determine that the entity is a counterfeit A-IoT device based on the determination that the provided device identifier does not match the buffered power-on distribution.

[0068] Referring to procedures 300 and 400, examples of identifying benign and counterfeit A-IoT devices according to embodiments of this disclosure are described. In these examples, the UE may move to the vicinity of energy harvesting from a valid A-IoT device or, in fact, a malicious counterfeit A-IoT device (e.g., a software-defined radio controlled by an attacker). Once near the device, the energy harvesting power-on process can be measured on the UE side.

[0069] When an A-IoT device is powered on and conducting its mission-specific communications with a UE or other network, the UE (or network) can use measured power-on process characteristics (such as power-on duration, energy delivered, and energy delivery differences over time during the power-on process) to determine whether the power-on characteristics match the identifiers stated by the A-IoT device. If a match is found, the device is likely benign and functioning as expected, while a mismatch may indicate a malfunction or a malicious spoofing device.

[0070] Counterfeit devices controlled by attackers may struggle to accurately model the power-on behavior of genuine devices, and in many attack scenarios, counterfeit devices (such as software-defined radios) may not even have the functionality for power-on. Therefore, power-on characteristics can be extremely useful for A-IoT device identification.

[0071] Figure 5 A flowchart of an example method 500 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 2 Method 500 is described by the angle of the first device 201 in the middle.

[0072] At frame 510, the first device 201 measures the reflected signal of a radio frequency (RF) signal transmitted from the first device in the environment.

[0073] At box 520, the first device 201 determines, based on the measurement, that an entity exists in the environment and that the entity performs Ambient Internet of Things (A-IoT) type communication.

[0074] At box 530, the first device 201 determines the electrical characteristics of an entity, which are configured to determine whether the entity is a valid A-IoT device.

[0075] In some example embodiments, A-IoT type communication is associated with harvesting energy from the environment. In some example embodiments, determining that an entity performing A-IoT type communication exists in the environment based on measurements includes determining that the entity performing A-IoT type communication exists in the environment if the measurements indicate attenuation of an RF signal.

[0076] In some example embodiments, the energizing characteristics are associated with at least one of the following: the duration of the energizing event, the pattern or distribution of the energizing event, or the energy harvesting rate of the energizing event.

[0077] In some example embodiments, method 500 further includes: determining whether an entity is a valid A-IoT device based on its power-on characteristics. In some example embodiments, determining whether an entity is a valid A-IoT device includes: determining that the entity is a valid A-IoT device based on a match between the determined power-on characteristics and identification information provided by the entity. In some example embodiments, method 500 further includes: receiving identification information provided by the entity from the entity or a network device.

[0078] In some example embodiments, determining whether an entity is a valid A-IoT device includes: if it is determined that the power-on characteristics match predefined power-on characteristics, then the entity is determined to be a valid A-IoT device. In some example embodiments, the predefined power-on characteristics correspond to the type of A-IoT device.

[0079] In some example embodiments, determining whether an entity is a valid A-IoT device includes: if it is determined that the power-on characteristics do not match the identification information or predefined power-on characteristics provided by the entity, then the entity is determined to be a malicious A-IoT device or a counterfeit A-IoT device.

[0080] In some example embodiments, method 500 further includes: sending the electrical characteristics of the entity to the second device. In some example embodiments, method 500 further includes: receiving a request for the electrical characteristics of the entity from the second device.

[0081] Figure 6 A flowchart of an example method 600 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 2 Method 600 is described by the angle of the second device 202 in the middle.

[0082] At box 610, the second device 202 receives the power-on characteristics of an entity from the first device, which performs Ambient Internet of Things (A-IoT) type communication.

[0083] At box 620, the second device 202 determines whether an entity is a valid A-IoT device based on its power-on characteristics.

[0084] In some example embodiments, method 600 further includes sending a request to the first device for the electrical characteristics of the entity.

[0085] In some example embodiments, the energizing characteristics are associated with at least one of the following: the duration of the energizing event, the pattern or distribution of the energizing event, or the energy harvesting rate of the energizing event.

[0086] In some example embodiments, determining whether an entity is a valid A-IoT device includes: if it is determined that the power-on characteristics match the identification information provided by the entity, then determining that the entity is a valid A-IoT device. In some example embodiments, method 600 further includes: receiving identification information from the entity.

[0087] In some example embodiments, determining whether an entity is a valid A-IoT device includes: if it is determined that the power-on characteristics match predefined power-on characteristics, then the entity is determined to be a valid A-IoT device. In some example embodiments, the predefined power-on characteristics correspond to the type of A-IoT device.

[0088] In some example embodiments, determining whether an entity is a valid A-IoT device includes: if it is determined that the power-on characteristics do not match the identification information or predefined power-on characteristics provided by the entity, then the entity is determined to be a malicious A-IoT device or a counterfeit A-IoT device.

[0089] In some example embodiments, a first device capable of performing any method 500 (e.g., Figure 2 The first device 201 may include a component for performing the corresponding operation of method 500. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 2 The first device 201 in the middle.

[0090] In some example embodiments, the first device includes: components for measuring reflected signals of radio frequency (RF) signals transmitted from the first device in the environment; components for determining, based on the measurement, that an entity is present in the environment, the entity performing environmental Internet of Things (A-IoT) type communication; and components for determining the electrical characteristics of the entity, the electrical characteristics being configured to determine whether the entity is a valid A-IoT device.

[0091] In some example implementations, A-IoT type communication is associated with harvesting energy from the environment.

[0092] In some example embodiments, the component for determining, based on measurement, that an entity performing A-IoT type communication exists in the environment includes a component for determining that an entity performing A-IoT type communication exists in the environment if the measurement indicates attenuation of an RF signal.

[0093] In some example embodiments, the energizing characteristics are associated with at least one of the following: the duration of the energizing event, the pattern or distribution of the energizing event, or the energy harvesting rate of the energizing event.

[0094] In some example embodiments, the first device further includes: a component for determining whether an entity is a valid A-IoT device based on its power-on characteristics. In some example embodiments, the component for determining whether an entity is a valid A-IoT device includes: a component for determining that the entity is a valid A-IoT device if the power-on characteristics match identification information provided by the entity. In some example embodiments, the first device further includes: a component for receiving identification information provided by the entity from the entity or a network device.

[0095] In some example embodiments, the component for determining whether an entity is a valid A-IoT device includes: a component for determining that the entity is a valid A-IoT device if its power-on characteristics match predefined power-on characteristics. In some example embodiments, the predefined power-on characteristics correspond to the type of A-IoT device.

[0096] In some example embodiments, the component for determining whether an entity is a valid A-IoT device includes: a component for determining that an entity is a malicious A-IoT device or a counterfeit A-IoT device if it is determined that the power-on characteristics do not match the identification information or predefined power-on characteristics provided by the entity.

[0097] In some example embodiments, the first device further includes a component for transmitting the electrical characteristics of the entity to the second device.

[0098] In some example embodiments, the first device further includes a component for receiving a request from the second device for the electrical characteristics of the entity.

[0099] In some example embodiments, a second device capable of performing any method 600 (e.g., Figure 2 The second device 202 may include a component for performing the corresponding operation of method 600. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 2 In the second device 202.

[0100] In some example embodiments, the second device includes: a component for receiving the energizing characteristics of an entity from the first device, the entity performing environmental Internet of Things (A-IoT) type communication; and a component for determining whether the entity is a valid A-IoT device based on the energizing characteristics.

[0101] In some example embodiments, the second device further includes a component for sending a request to the first device for the electrical characteristics of the entity.

[0102] In some example embodiments, the energizing characteristics are associated with at least one of the following: the duration of the energizing event, the pattern or distribution of the energizing event, or the energy harvesting rate of the energizing event.

[0103] In some example embodiments, the component for determining whether an entity is a valid A-IoT device includes a component for determining that the entity is a valid A-IoT device if it is determined that the power-on characteristics match the identification information provided by the entity. In some example embodiments, the second device further includes a component for receiving identification information from the entity.

[0104] In some example embodiments, the component for determining whether an entity is a valid A-IoT device includes: a component for determining that the entity is a valid A-IoT device if its power-on characteristics match predefined power-on characteristics. In some example embodiments, the predefined power-on characteristics correspond to the type of A-IoT device.

[0105] In some example embodiments, the component for determining whether an entity is a valid A-IoT device includes: a component for determining that the entity is a malicious A-IoT device or a counterfeit A-IoT device if it is determined that the power-on characteristics do not match the identification information or predefined power-on characteristics provided by the entity.

[0106] Figure 7 This is a simplified block diagram of a device 700 suitable for implementing an example embodiment of the present disclosure. The device 700 can be provided to implement a communication device, such as... Figure 1 The terminal device 110 or network device 120 shown. As shown, device 700 includes one or more processors 710, one or more memories 720 coupled to processor 710, and one or more communication modules 740 coupled to processor 710.

[0107] Communication module 740 is used for bidirectional communication. Communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 740 may include at least one antenna.

[0108] As a non-limiting example, processor 710 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.

[0109] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not persist for extended periods of power-off duration.

[0110] Computer program 730 includes computer-executable instructions that are executed by an associated processor 710. The instructions of program 730 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 730 may be stored in memory (e.g., ROM 724). Processor 710 can perform any suitable actions and processes by loading program 730 into RAM 722.

[0111] The exemplary embodiments of this disclosure can be implemented by program 730, enabling device 700 to perform as described in the reference. Figures 2 to 6 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0112] In some example embodiments, program 730 may be tangibly contained in a computer-readable medium, which may be included in device 700 (such as memory 720) or other storage devices accessible by device 700. Device 700 may load program 730 from the computer-readable medium into RAM 722 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0113] Figure 8 An example of a computer-readable medium 800 is shown, which may be in the form of a CD, DVD, or other optical storage disc. A program 730 is stored on the computer-readable medium 800.

[0114] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0115] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.

[0116] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0117] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0118] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0119] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0120] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the first device to: The reflected signal of a radio frequency (RF) signal transmitted from the first device is measured in the environment. Based on the measurements, it is determined that an entity exists in the environment, and the entity performs environmental Internet of Things (A-IoT) type communication; as well as The power-on characteristics of the entity are determined, and the power-on characteristics are configured to determine whether the entity is a valid A-IoT device.

2. The first device according to claim 1, wherein the A-IoT type communication is associated with energy harvesting from the environment.

3. The first apparatus according to claim 1 or 2, wherein determining, based on the measurement, that the entity performing A-IoT type communication exists in the environment comprises: If the measurement indicates attenuation of the RF signal, then the entity performing the A-IoT type of communication is determined to exist in the environment.

4. The first device according to claim 1 or 2, wherein the energizing characteristic is associated with at least one of the following: Duration of the power-on event, Patterns or distributions of energizing events, or Energy harvesting rate of an energized event.

5. The first device according to claim 1 or 2, wherein the first device is further configured to: Based on the power-on characteristics, it is determined whether the entity is a valid A-IoT device.

6. The first apparatus of claim 5, wherein determining whether the entity is the valid A-IoT device comprises: If the power-on characteristics are determined to match the identification information provided by the entity, then the entity is determined to be the valid A-IoT device.

7. The first device according to claim 6, wherein the first device is further configured to: Receive the identification information provided by the entity from the entity or network device.

8. The first apparatus of claim 5, wherein determining whether the entity is the valid A-IoT device comprises: If it is determined that the power-on characteristics match the predefined power-on characteristics, then the entity is determined to be the valid A-IoT device.

9. The first device according to claim 8, wherein the predefined power-on characteristics correspond to the type of A-IoT device.

10. The first apparatus of claim 5, wherein determining whether the entity is the valid A-IoT device comprises: If it is determined that the power-on characteristics do not match the identification information or predefined power-on characteristics provided by the entity, then the entity is determined to be a malicious A-IoT device or a counterfeit A-IoT device.

11. The first device according to claim 1 or 2, wherein the first device is further configured to: The electrical characteristics of the entity are sent to the second device.

12. The first device according to claim 11, wherein the first device is further configured to: Receive a request from the second device for the electrical characteristics of the entity.

13. A second means for communication, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the second device to: The entity receives the power-on characteristics of the entity from the first device, and the entity performs communication of the A-IoT type in the environment; as well as Based on the power-on characteristics, it is determined whether the entity is a valid A-IoT device.

14. The second device of claim 13, wherein the A-IoT type communication is associated with harvesting energy from the environment.

15. The second device according to claim 13 or 14, wherein the second device is further configured to: Send a request to the first device regarding the electrical characteristics of the entity.

16. The second device according to any one of claims 13 or 14, wherein the energizing characteristic is associated with at least one of the following: Duration of the power-on event, Patterns or distributions of energizing events, or Energy harvesting rate of an energized event.

17. The second apparatus according to any one of claims 13 or 14, wherein determining whether the entity is the valid A-IoT device comprises: If the power-on characteristics are determined to match the identification information provided by the entity, then the entity is determined to be the valid A-IoT device.

18. The second device according to claim 17, wherein the second device is further configured to: Receive the identification information from the entity.

19. The second apparatus according to any one of claims 13 or 14, wherein determining whether the entity is the valid A-IoT device comprises: If it is determined that the power-on characteristics match the predefined power-on characteristics, then the entity is determined to be the valid A-IoT device.

20. The second device according to claim 19, wherein the predefined power-on characteristics correspond to the type of A-IoT device.

21. The second apparatus according to any one of claims 13 or 14, wherein determining whether the entity is the valid A-IoT device comprises: If it is determined that the power-on characteristics do not match the identification information or predefined power-on characteristics provided by the entity, then the entity is determined to be a malicious A-IoT device or a counterfeit A-IoT device.

22. A method for communication, comprising: The reflected signal of a radio frequency (RF) signal transmitted from the first device is measured at the first device and in the environment. Based on the measurements, it is determined that an entity exists in the environment, and the entity performs environmental Internet of Things (A-IoT) type communication; as well as The power-on characteristics of the entity are determined, and the power-on characteristics are configured to determine whether the entity is a valid A-IoT device.

23. A method for communication, comprising: The second device receives the power-on characteristics of the entity from the first device, the entity performing environmental Internet of Things (A-IoT) type communication; as well as Based on the power-on characteristics, it is determined whether the entity is a valid A-IoT device.

24. A first means for communication, comprising: A component for measuring the reflected signal of a radio frequency (RF) signal in an environment, the RF signal being transmitted from the first device; Components used to determine the presence of an entity in the environment based on the measurements, the entity performing environmental Internet of Things (A-IoT) type communication; as well as Components for determining the electrical characteristics of the entity, the electrical characteristics being configured to determine whether the entity is a valid A-IoT device.

25. A second means for communication, comprising: A component for receiving the electrical characteristics of an entity from a first device, the entity performing environmental Internet of Things (A-IoT) type communication; as well as Components used to determine whether the entity is a valid A-IoT device based on the power-on characteristics.

26. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method of claim 22 or the method of claim 23.

Images