Communications device and method

Abstract

Various aspects of the disclosure relate to devices and methods of communication. In one aspect, a first device receives, from a second device, a message to page a set of first devices, the set of first devices including the first device, and determines that the message indicates a first operation that requires a response from the first device. If the message satisfies a condition to skip a response, the first device does not respond to the message. In this way, unnecessary responses to pages for A-IoT devices can be avoided, and energy consumption at A-IoT devices can be conserved.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to devices and methods for communication for the Internet of Things in the Environment (A-IoT). Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] A-IoT is an Internet of Things (IoT) technology that supports battery-free devices without energy storage capabilities, or devices with energy storage that does not require manual replacement or charging. Recently, compact protocol stacks and corresponding processes designed for A-IoT have been proposed, such as paging, random access, and data transmission. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems for supporting communication with A-IoT devices. Communication with A-IoT devices can be enhanced by considering the success and / or failure of paging for one or more A-IoT devices.

[0005] In one aspect, some implementations of the methods and apparatus described herein may include: at a first device, receiving from a second device a message for paging a first set of devices, the first set of devices including the first device; determining that the message indicates a first operation that requires a response from the first device; and, based on determining that the message satisfies a condition for skipping a response, not responding to the message.

[0006] Some implementations of the methods and devices described herein may also include at least one of the following: initiating random access to a second device based on determining that the message does not meet the conditions; or performing a second operation based on determining that the message instructs a second operation, the second operation not requiring a response from the first device.

[0007] In some implementations of the methods and devices described herein, the condition may include at least one of the following: the message is identical to another message that has already been responded to; an indication to end the response is received; the status of the first device indicates that the first operation has been performed; the identification information of the second device is identical to the identification information of another second device that sent the other message; the second device is in the list of second devices that have been responded to; the message was not first received from the second device; the message was not the first message to be responded to; or the ongoing service or task has not been completed.

[0008] In some implementations of the methods and devices described herein, the indication to end the response may be associated with at least one of the following: identification information of a first device indicated in the message, the reason indicated in the message, identification information of a second device, or identification information of a service or task indicated in the message.

[0009] In some implementations of the methods and devices described herein, the identification information of the first device may include at least one of the following: the device identifier of the first device; the tag identifier of the first device; the electronic product code (EPC) identifier of the first device; the group identifier of the first device; the region identifier of the first device; or at least a portion of the data cached in the first device.

[0010] In some implementations of the methods and devices described herein, the validity of the indication to end the response may be associated with at least one of the following: duration, number of pagers to the first device, or the energy of the first device.

[0011] Some implementations of the methods and devices described herein may also include: receiving a command from a second device to change the state of a first device; or changing the state of the first device to indicate that the first operation was successfully executed, based on a determination that the first operation was successfully executed.

[0012] In some implementations of the methods and devices described in this paper, a list of the responding second devices may be included in the message.

[0013] On the other hand, some implementations of the methods and apparatus described herein may include: at a second device, sending a message for paging a first set of devices; receiving a response from a first device in the first set of devices; and sending information of the first device to at least one of a second device or a third device.

[0014] Some implementations of the methods and devices described herein may also include: receiving from a third device another message for paging another set of first devices, the other message including a list of responding second devices.

[0015] In some implementations of the methods and devices described herein, the information of the first device may include at least one of the following: identification information of the first device, the status of the first device, or identification information of a second device that receives a response from the first device.

[0016] On the other hand, some implementations of the methods and apparatus described herein may include: at a second device, sending a message for paging a first set of devices; determining that a paging failure has occurred; and performing an operation including at least one of: changing the transmission of an energy carrier set for the first set of devices, changing the retransmission of the message, sending failure information to a third device, or updating the message.

[0017] In some implementations of the methods and devices described herein, determining that a failure has occurred may include determining that a failure has occurred based on at least one of the following: no response was received from the first set of devices during a first time window; no response was received from the first set of devices at the resource; the number of first devices that responded during a second time window is less than or equal to a number threshold; the ratio of the first devices that responded during a third time window is less than or equal to a ratio threshold; or a response from a subset of the first devices in the first set of devices is missing.

[0018] In some implementations of the methods and apparatus described herein, altering the transmission of the energy carrier may include: transmitting the energy carrier at increased power or time; or causing the energy source to transmit the energy carrier at increased power or time.

[0019] In some implementations of the methods and devices described herein, modifying message retransmission may include retransmitting the message with an increased number of repetitions.

[0020] In some implementations of the methods and devices described herein, the failure information includes at least one of the following: the cause of the failure; identification information of the first device indicated in the message, where the failure occurred during paging for the first device; identification information of the second device in which the failure occurred; identification information of the service or task in which the failure occurred; or a preferred number of retransmissions of the message.

[0021] In some implementations of the methods and devices described herein, the identification information of the first device may include at least one of the following: the device identifier of the first device; the tag identifier of the first device; the EPC identifier of the first device; the group identifier of the first device; the area identifier of the first device; or at least a portion of the data buffered in the first device.

[0022] In some implementations of the methods and devices described herein, updating the message may include at least one of the following: updating a message with an increased paging area; or changing the identification information of the first set of devices in the message.

[0023] In some implementations of the methods and devices described herein, the first device may be an A-IoT device, the second device may be a base station or a communication node between the base station and the A-IoT device, and the third device may be a core network element. Attached Figure Description

[0024] Figure 1 An example of a wireless communication system supporting communication with A-IoT devices according to various aspects of this disclosure is shown.

[0025] Figure 2A A diagram illustrating an example scenario of paging transmission for a service or task according to various aspects of this disclosure is shown.

[0026] Figure 2B A diagram illustrating example scenarios of paging transmissions for different services or tasks according to various aspects of this disclosure is shown.

[0027] Figure 3 A signaling diagram illustrating an example process for supporting communication with A-IoT devices according to various aspects of this disclosure is shown.

[0028] Figure 4 Examples of devices supporting communication with A-IoT devices according to various aspects of this disclosure are shown.

[0029] Figure 5 An example of a processor that supports communication with A-IoT devices according to various aspects of this disclosure is shown.

[0030] Figure 6 A flowchart is shown illustrating a method for supporting communication with A-IoT devices according to various aspects of this disclosure.

[0031] Figure 7 A flowchart is shown illustrating another method for supporting communication with A-IoT devices according to various aspects of this disclosure.

[0032] Figure 8 A flowchart is shown illustrating another method for supporting communication with A-IoT devices according to various aspects of this disclosure. Detailed Implementation

[0033] The principles of this disclosure will now be described with reference to some 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 disclosure described herein can be implemented in various ways other than those described below.

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

[0035] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment(s). Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) such a feature, structure, or characteristic may affect such a feature, structure, or characteristic within the scope of their knowledge. The term "embodiment" may be used interchangeably with "implementation."

[0036] It should be understood that although the terms “first” and “second” 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. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also 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.

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

[0038] In the context of this disclosure, the term "first device" can refer to a battery-free device without energy storage capability, or a device with energy storage that does not require manual replacement or charging. The term "first device" may be used interchangeably with "A-IoT device" or "A-IoT UE".

[0039] In the context of this disclosure, the term "second device" can refer to a node that communicates with an A-IoT device. For example, the node can be a base station or a communication node between a base station and an A-IoT device. For example, the communication node can be a relay, integrated access and backhaul (IAB) node, UE, repeater, etc., capable of A-IoT association functions. In some embodiments, the second device can be a node that provides excitation signals or energy to the A-IoT device. In one embodiment, the second device can be a node that sends commands to the A-IoT device to perform selection, storage, or access (e.g., read and write) of the A-IoT device. For convenience, the term "second device" may be used interchangeably with "node".

[0040] In the context of this disclosure, the term "third device" can refer to a core network (CN) element. In some embodiments, a CN element can be an existing CN function, such as LMF, AMF, etc. In some embodiments, a CN element can be a newly defined CN function or server for A-IoT. The term "third device" can be used interchangeably with "CN element" or "CN device" or "server for A-IoT".

[0041] In the context of this disclosure, the term "paging message" can refer to a message used to page an A-IoT device. The term "A-IoT" can be used interchangeably with "passive IoT".

[0042] Typically, an A-IoT device can receive one or more paging messages from one or more nodes. In this case, it may be necessary to define the behavior of the A-IoT device for handling one or more paging messages. Furthermore, it may be unrealistic to expect paging to always succeed for a large number of A-IoT devices. If paging fails, it may be necessary to define the behavior of the node that sent the paging message.

[0043] In view of this, embodiments of the present disclosure provide a solution for communication with A-IoT devices. In one aspect, a first device receives from a second device a message for paging a first set of devices, the first set of devices including the first device, and determines that the message indicates a first operation that requires a response from the first device. If the message satisfies a condition for skipping a response, the first device does not respond to the message. In this way, unnecessary responses to paging for A-IoT devices can be avoided, and energy consumption at the A-IoT devices can be saved.

[0044] On the other hand, upon receiving a response from the first device, the second device sends the information from the first device to at least one of another second device or a third device. In this way, responses to paging for A-IoT devices can be managed in an efficient manner.

[0045] On the other hand, when a paging failure is determined to have occurred for the first set of devices, the second device performs an operation including at least one of the following: changing the transmission of the energy carrier set for the first set of devices; changing the message retransmission; sending a failure message to a third device, or updating the message. In this way, paging failures for A-IoT devices can be identified and handled.

[0046] The aspects of this disclosure are described in the context of wireless communication systems.

[0047] Figure 1 An example of a wireless communication system 100 supporting paging for A-IoT devices according to aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)). For convenience, network entities 102-1, 102-2, and 102-3 are shown and are collectively referred to below as one or more network entities 102. The wireless communication system 100 may also include one or more A-IoT devices 101, one or more UEs 104, a CN 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0048] One or more A-IoT devices 101 may be distributed within the geographical area of ​​the wireless communication system 100. A-IoT devices 101 may be battery-free devices without energy storage capabilities, or devices with energy storage that does not require manual replacement or charging. A-IoT devices 101 may include an energy harvesting module and a backscattering module. A-IoT devices 101 may receive energy supply signals or commands via the energy harvesting module and backscatter signals via the backscattering module.

[0049] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. The network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0050] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0051] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0052] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay devices, IAB nodes, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UEs 104, which can act as relays in the wireless communication system 100.

[0053] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0054] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0055] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an IAB network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0056] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0057] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0058] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, and RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0059] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1c, F1-u), while the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, which are supported by corresponding network entities 102 communicating via such communication links.

[0060] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core or a 5G core (5GC), and it can include one or more core network elements 103. Core network elements 103 can be control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)), and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0061] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be one example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0062] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0063] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0064] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0065] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technique. It should be understood that for the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0066] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0067] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0068] In some scenarios, A-IoT device 101 can communicate directly and bidirectionally with network entity 102. The communication between A-IoT device 101 and network entity 102 includes A-IoT data and / or signaling. These scenarios can be referred to as Topology 1.

[0069] In some scenarios, A-IoT device 101 can communicate bidirectionally with an intermediate node between A-IoT device 101 and network entity 102. This intermediate node can be a UE 104, a relay, an IAB node, a repeater, etc., possessing A-IoT capabilities. The intermediate node can transmit A-IoT data and / or signaling between A-IoT device 101 and network entity 102. These scenarios can be referred to as Topology 2.

[0070] In some scenarios, A-IoT device 101 can send data / signaling to network entity 102 and receive data / signaling from auxiliary nodes; or A-IoT device 101 can receive data / signaling from network entity 102 and send data / signaling to auxiliary nodes. Auxiliary nodes can be UE 104, relays, IAB nodes, repeaters, etc., and possess A-IoT capabilities. These scenarios can be referred to as Topology 3.

[0071] In some scenarios, A-IoT device 101 can communicate bidirectionally with UE 104. The communication between A-IoT device 101 and UE 104 includes A-IoT data and / or signaling. These scenarios can be referred to as Topology 4.

[0072] In some scenarios used for services or tasks, CN 106 can trigger one or more nodes (e.g., network entities 102-1, 102-2, UE 104, etc.) to send one or more paging messages to search for a set of A-IoT devices (i.e., one or more A-IoT devices). Figure 2A Figure 200A illustrates an example scenario of paging transmission for a service or task according to various aspects of this disclosure.

[0073] exist Figure 2A In scenario 210, a node (node ​​1) may send a paging message for a service or task. In some embodiments, a node may send the same paging message a number of times, i.e., paging message retransmission.

[0074] exist Figure 2A In scenario 211, a node (node ​​1) can send multiple paging messages (paging messages #1, #2, ..., #N) for services or tasks. Some or all of the paging messages can be the same (if all the content of the paging messages is the same, then the scenario is as follows). Figure 2A (Paging retransmission as described in scenario 210). For example, for the inventory use case, the paging reason can be the same. Since not all target A-IoT devices have completed the inventory process after an inventory cycle, a node can send multiple paging messages to complete the inventory process for all target A-IoT devices.

[0075] exist Figure 2A In scenario 212, multiple nodes (node ​​1, node 2, ..., node N) can send multiple paging messages (paging message #1, #2, ..., #N) for services or tasks. In this case, the transmission of paging messages from the nodes can be scheduled by CN according to the requirements of the service or task.

[0076] In some scenarios used for different services or tasks, CN 106 can trigger one or more nodes (e.g., network entities 102-1, 102-2, UE 104, etc.) to send multiple paging messages to search for one or more sets of A-IoT devices. Figure 2B Figure 200B illustrates example scenarios of paging transmissions for different services or tasks according to various aspects of this disclosure.

[0077] exist Figure 2B In scenario 220, after node 1 sends paging message #1 for service or task #1, the node can send another paging message #2 for service or task #2, and so on. That is, a node can send multiple paging messages for multiple services or tasks. In some cases, some content of the paging messages can be the same; for example, the paging reason in paging message #1 is for inventory of service / task #1, the paging reason in paging message #2 is for inventory of service / task #2, and so on.

[0078] exist Figure 2B In scenario 221, multiple nodes (node ​​1, node 2, ..., node N) can send multiple paging messages (paging message #1, #2, ..., #N) for different services or tasks.

[0079] As can be seen, A-IoT devices can receive one or more paging messages from one or more nodes for one or more services / tasks. In this case, it is necessary to define how to handle these paging scenarios. For example, after an A-IoT device receives a paging message, its behavior regarding whether the paging ID in the paging record matches the A-IoT device's identifier needs to be designed. Furthermore, for the inventory use case, one or more nodes can send multiple paging messages to an A-IoT device because not all target A-IoT devices complete the inventory upon receiving a single paging message (for non-periodic paging) or a period of paging messages (for periodic paging). In this case, those A-IoT devices that have already completed the inventory process may not need to respond to the paging message again to save power or due to capacity limitations. Therefore, A-IoT devices may need to determine under what circumstances they do not need to respond to the paging message. Another issue is that paging is not always successful. Therefore, it is also necessary to develop how to define failures in paging and the potential behavior of nodes for handling failures.

[0080] In view of the above, embodiments of this disclosure provide a solution for communication with A-IoT devices. The following will combine... Figure 3 Describe these solutions.

[0081] Figure 3 A signaling diagram of an example process 300 supporting communication with an A-IoT device according to various aspects of this disclosure is shown. For discussion purposes, it will be combined with... Figure 1 Process 300 is described. Process 300 may involve a first device, a second device, and a third device. The first device may be an A-IoT device, the second device may be a base station or a communication node between the base station and the A-IoT device, and the third device may be a core network element. For illustration, the following description will be given by assuming that the first device is A-IoT device 101, the second device is network entity 102-1, and the third device is core network element 103. It should be understood that... Figure 3 The steps and their order are for illustrative purposes only and are not intended to be limiting.

[0082] It is assumed that the A-IoT device 101 has been woken up (i.e. activated) before receiving a paging message via a separate power carrier or a power carrier along with a paging message.

[0083] like Figure 3As shown, network entity 102-1 can send 310 messages (i.e., paging messages) for paging a set of A-IoT devices (i.e., one or more A-IoT devices). For example, CN can instruct one or more base stations to send one or more paging messages to locate the set of A-IoT devices for one or more services / tasks. In some embodiments, the paging message may include a set of paging records for the set of A-IoT devices. The paging records in the set of paging records may have different paging identifiers (IDs).

[0084] After A-IoT device 101 is activated, it can receive paging messages. It should be understood that A-IoT device 101 can receive multiple paging messages from different network entities. For convenience, only one paging message from a single network entity is shown. In some embodiments, A-IoT device 101 can perform backscatter transmission upon receiving one or more paging messages. In some embodiments, A-IoT device 101 can decode all received paging messages. In some embodiments, A-IoT device 101 can randomly select paging messages and decode them.

[0085] Continue to refer to Figure 3 A-IoT device 101 can determine whether the ID information of the A-IoT device set 311 matches the ID information of A-IoT device 101. It should be understood that the ID information can take any suitable form.

[0086] In some embodiments, the A-IoT device set may include A-IoT device 101. In this case, the ID information of A-IoT device 101 may be matched with one of the ID information in the A-IoT device set. For example, the ID of A-IoT device 101 may be matched with the paging ID of a paging record in a paging message.

[0087] In some embodiments, the A-IoT device set may not include A-IoT device 101. In this case, the ID information of A-IoT device 101 may not match any ID information in the A-IoT device set. For example, the ID of A-IoT device 101 may not match any paging ID in any paging record in the paging message.

[0088] refer to Figure 3 If the ID information of the A-IoT device set does not match the ID information of A-IoT device 101, then A-IoT device 101 may not perform any operation or action. In this case, when the power carrier is insufficient, A-IoT device 101 may enter sleep mode.

[0089] refer to Figure 3If the ID information of the A-IoT device set matches the ID information of A-IoT device 101, then A-IoT device 101 can determine whether the paging message 313 indicates an operation that requires a response from A-IoT device 101 (referred to as the first operation in this document for convenience) or an operation that does not require a response from A-IoT device 101 (referred to as the second operation in this document for convenience).

[0090] In some embodiments, the first operation may be a count operation. In some embodiments, the first operation may be a downlink command that requires a response. It should be understood that any other suitable operation that requires a response is also possible.

[0091] In some embodiments, the second action may be a request to change the state of a specific service or task. In another example, the second action may be a downlink command without a response, including online modification of medical device status, device activation and deactivation, elderly healthcare, permanent device deactivation, electronic shelf labeling, etc. It should be understood that any other suitable action that does not require a response is also possible.

[0092] like Figure 3 As shown, if the paging message indicates a second operation without any response from A-IoT device 101, then A-IoT device 101 can perform the second operation 314. In other words, if the paging message does not require a response from A-IoT device 101, then A-IoT device 101 can perform the requested action.

[0093] Continue to refer to Figure 3 If a paging message indicates a first action requiring a response from A-IoT device 101, A-IoT device 101 can determine whether paging message 315 meets the conditions for skipping a response. For example, if an A-IoT device receives multiple paging messages from one or more nodes for the same service / task (e.g., inventory), an A-IoT device that has already responded to a node may not need to respond again to paging messages with the same service / task to save power. Therefore, the A-IoT device may need to determine under what circumstances it does not need to respond to matching paging messages.

[0094] refer to Figure 3 If the paging message meets the conditions for skipping the response, then the A-IoT device 101 may not respond to the paging message 316. For illustration, some example embodiments will be described below.

[0095] In some embodiments, the condition for skipping a response may include the paging message being identical to another paging message that has already been responded to. In some embodiments, if the paging record in the paging message is identical to the last responding paging message (i.e., a paging message retransmission), the A-IoT device 101 may not respond to the paging message. In other words, in the case of a paging message retransmission, the A-IoT device 101 may respond to only one paging message. When the same paging message is received again, the A-IoT device 101 may not take any action or respond, and the network entity 102-1 may not need to indicate the number of retransmissions to the A-IoT device 101.

[0096] In some embodiments, the conditions for skipping a response may include the receipt of an indication to end the response (also referred to herein as an “end” indication). In some embodiments, if an “end” indication is received or valid, the A-IoT device 101 may not respond to the paging message.

[0097] In some embodiments, the A-IoT device 101 may receive an "end" indication from a node that has already received a response directly from the A-IoT device or has received response information for a service / task from another node. In some embodiments, the "end" indication may be valid for newly received paging messages. In some embodiments, multiple "end" indications for different services or tasks may be received and maintained simultaneously for the A-IoT device.

[0098] In some embodiments, the "end" indication may be associated with the ID information (i.e., the paging ID) of the A-IoT device indicated in the paging message. In some embodiments, the A-IoT device ID information may include at least one of the following: device ID, tag ID, EPC ID, group ID, area ID, or at least a portion of data cached in the A-IoT device. For example, the "end" indication may be indicated by the paging ID. If the current paging message has the same paging ID as the last responded paging message, the A-IoT device 101 may no longer respond to the current paging message. For example, the "end" indication may be indicated by area ID / group ID / EPC / tag ID. If the current paging message has the same area ID / group ID / ECP / tag ID as the last responded paging message, the A-IoT device 101 may no longer respond to the current paging message.

[0099] In some embodiments, the "end" indication may be associated with a reason indicated in the paging message (also referred to herein as a paging reason). For example, the "end" indication may be indicated by a paging reason. If the current paging message has the same paging reason as the last paging message that was responded to (e.g., inventory, etc.), the A-IoT device 101 may no longer respond to the current paging message.

[0100] In some embodiments, the "end" indication may be associated with the identification information of network entity 102-1. For example, the "end" indication may be indicated by node ID (e.g., network entity ID or UE ID, etc.). If the current paging message has the same node ID as the last paging message that was responded to, the A-IoT device 101 may no longer respond to the current paging message.

[0101] In some embodiments, the "end" indication may be associated with the ID information of the service or task indicated in the paging message. For example, the "end" indication may be indicated by service ID or by task ID. If the current paging message has the same service / task ID as the last paging message that was responded to, the A-IoT device 101 may no longer respond to the current paging message.

[0102] In some embodiments, the validity of the “end” indication may be associated with at least one of the following: duration, number of paging attempts for A-IoT device 101, or energy of A-IoT device 101.

[0103] In some embodiments, the "end" indication may be valid for a duration. In some embodiments, a node may configure the "end" indication with a specified duration or window during which the A-IoT device may not need to respond to paging messages. The duration or window may be an integer multiple of the number of paging messages. In some embodiments, the "end" indication may become invalid when the duration or window expires.

[0104] In some embodiments, the "End" indication can be valid for a predefined number of paging messages. In some embodiments, a node can configure the "End" indication with a specified number of paging messages, for example, with the following pre-configured paging counts (e.g., 5 or 10 paging messages). That is, the A-IoT device may not need to respond to the following 5 or 10 paging messages. In some embodiments, the "End" indication may be invalid when the paging count expires.

[0105] In some embodiments, the "End" indication may be valid when the A-IoT device 101 is not empty. In some embodiments, the "End" indication may be invalid when the A-IoT device 101 is empty.

[0106] In some embodiments, the “end” indication may need to be updated when the A-IoT device 101 is reactivated by an energy carrier (from a node or energy source).

[0107] In some embodiments, the condition for skipping a response may include the status of the A-IoT device 101, which indicates that the first operation has been performed. In some embodiments, if the status of the A-IoT device 101 indicates that the first operation has been performed, the A-IoT device 101 may not respond to the paging message. For example, if the status of the A-IoT device 101 indicates or reflects "inventoried" when the same paging message for inventory is received, the A-IoT device 101 may not respond to the paging message.

[0108] In some embodiments, the state of A-IoT device 101 can be changed via network commands. In some embodiments, A-IoT device 101 can receive a command from network entity 102-1 to change the state of A-IoT device 101. In some embodiments, the command can be included in the next paging message. In some embodiments, the command can be included in a message separate from the next paging message.

[0109] In some embodiments, the state of A-IoT device 101 can change itself. In some embodiments, if the first operation is successfully performed, A-IoT device 101 can change its state to indicate or reflect that the first operation was successfully performed. For example, if the network allows, the state of A-IoT device 101 can be changed to indicate or reflect "counted" after a successful count.

[0110] In some embodiments, the condition for skipping a response may include the identification information of network entity 102-1 being the same as the identification information of a node that sent another message that has already been responded to. In other words, if A-IoT device 101 receives a paging message from a node with the same node ID as the last paging message responded to, A-IoT device 101 may not respond to the paging message, with or without further restrictions, for example, for inventory purposes or for the same service / task ID.

[0111] In some embodiments, the condition for skipping a response may include that network entity 102-1 is in the list of nodes to be responded to. In some embodiments, the list of nodes to be responded to may be included in the paging message. If the network entity 102-1 that sent the paging message is included in the list of nodes to be responded to as indicated in the paging message, then the A-IoT device 101 may not respond to the paging message.

[0112] In some embodiments, the condition for skipping a response may include that the paging message was not the first paging message received from the node. In other words, if the paging message is not the first paging message received, the A-IoT device 101 may not respond to the paging message.

[0113] In some embodiments, the condition for skipping a response may include that the paging message is not the first message to be responded to. In other words, if the paging message is not the first message to be responded to, the A-IoT device 101 may not respond to the paging message. In some embodiments, the A-IoT device 101 may randomly select a paging message to respond to and may not respond to other paging messages.

[0114] In some embodiments, the condition for skipping a response may include an ongoing service or task not being completed. In other words, if an ongoing service or task associated with the last paging message for the node to be responded to has not been completed, the A-IoT device 101 may not respond to the paging message.

[0115] Continue to refer to Figure 3 If the paging message does not meet the conditions for skipping the response, the A-IoT device 101 can initiate 317 random accesses to the network entity 102-1 and send a response to the network entity 102-1.

[0116] Accordingly, network entity 102-1 can receive a response from one or more A-IoT devices (e.g., A-IoT device 101) in the A-IoT device set. Figure 3 As shown, upon receiving a response, network entity 102-1 can send information about A-IoT device 101 to CN element 103. Alternatively or additionally, although not shown, network entity 102-1 can send information about A-IoT device 101 to other nodes, for example, concerning the same service or task. In other words, network entity 102-1 can exchange responses received from A-IoT devices with other nodes and / or CN elements.

[0117] In some embodiments, the information of A-IoT device 101 may include the ID information of A-IoT device 101. In some embodiments, the ID information of A-IoT device 101 may include at least one of the following: device ID, tag ID, EPC ID, group ID, region ID, or at least a portion of the data cached in A-IoT device 101.

[0118] In some embodiments, the information of the A-IoT device 101 may include the status of the A-IoT device 101, such as whether it has been counted or not.

[0119] In some embodiments, the information of A-IoT device 101 may include: the ID information of network entity 102-1 that receives the response from A-IoT device 101.

[0120] like Figure 3As shown, upon receiving information from A-IoT device 101, CN element 103 can generate a list of responding nodes as described above. CN element 103 can then indicate the list of responding nodes to the network entity (e.g., network entity 102-1) in the next paging message, 322.

[0121] Continue to refer to Figure 3 Based on the presence or absence of a response from an A-IoT device, network entity 102-1 can determine that a paging failure (also referred to herein as paging failure) has occurred in paging of the A-IoT device set 330.

[0122] In some embodiments, if no response is received from the A-IoT device set during a time window (also referred to herein as a first time window for convenience), network entity 102-1 may determine that a paging failure has occurred. For example, network entity 102-1 may send or retransmit a paging message with a predefined number of repetitions, but no response is received from the A-IoT device set during the time window. In this case, network entity 102-1 may determine that a paging failure has occurred.

[0123] In some embodiments, if no response is received from the A-IoT device set at a resource, network entity 102-1 may determine that paging failure has occurred. In some embodiments, network entity 102-1 may determine that paging failure has occurred if it does not receive any response at a predetermined time and / or frequency resource. For example, network entity 102-1 may send or retransmit a paging message with a predefined number of repetitions, but does not receive any response from the A-IoT device set at the predetermined time and / or frequency resource (e.g., time slot, frequency, etc.). In this case, network entity 102-1 may determine that paging failure has occurred.

[0124] In some embodiments, network entity 102-1 can determine whether a paging failure has occurred based on the number of A-IoT devices that responded during a time window. If the number of A-IoT devices that responded during the time window (also referred to herein as a second time window for convenience) is less than or equal to a number threshold, network entity 102-1 can determine that a paging failure has occurred. In some embodiments, the number threshold can vary based on different paging reasons. In some embodiments, the number threshold can vary based on different service / task IDs. It should be understood that the number threshold can be predefined or configured in any suitable manner.

[0125] In some embodiments, network entity 102-1 can determine whether a paging failure has occurred based on the ratio of responded A-IoT devices in the A-IoT device set during a time window. If the ratio of responded A-IoT devices in the A-IoT device set during the time window (also referred to herein as a third time window for convenience) is less than or equal to a ratio threshold, network entity 102-1 can determine that a paging failure has occurred. In some embodiments, the ratio threshold can vary based on different paging reasons. In some embodiments, the ratio threshold can vary based on different service / task IDs. It should be understood that the ratio threshold can be predefined or configured in any suitable manner.

[0126] In some embodiments, network entity 102-1 may determine that paging failure has occurred if a response is missing from a subset of A-IoT devices in the A-IoT device set. In some embodiments, the subset of A-IoT devices may include one or more specific or important A-IoT devices. For example, network entity 102-1 may want to page a specific A-IoT device. If a response from a specific A-IoT device is likely to be missing after a period of time, network entity 102-1 may determine that paging failure has occurred.

[0127] Continue to refer to Figure 3 When a paging failure is determined to have occurred, network entity 102-1 can execute operation 331 to handle the paging failure.

[0128] In some embodiments, upon determining that a paging failure has occurred, network entity 102-1 may alter the transmission of a set of power carriers for the A-IoT device set. In some embodiments, network entity 102-1 may transmit power carriers at increased power or for increased duration. In some embodiments, network entity 102-1 may cause a power source to transmit power carriers at increased power or for increased duration. For example, network entity 102-1 may send a command to a power source for a more powerful power carrier transmission, and the power source may, based on this command, transmit power carriers at increased power or for increased duration. In this way, more power carrier power can be provided to the A-IoT devices.

[0129] In some embodiments, when a paging failure is determined to have occurred, network entity 102-1 may change the retransmission of the paging message. In some embodiments, network entity 102-1 may retransmit the paging message with an increased number of repetitions (i.e., a greater number of repetitions).

[0130] In some embodiments, upon determining that a paging failure has occurred, network entity 102-1 may send paging failure information to CN element 103. In some embodiments, the paging failure information may include a reason for the paging failure. For example, the paging failure information may indicate that the paging failure was caused by the failure to receive a response from the set of A-IoT devices during a first time window or at a specified frequency resource. It should be understood that the reason may be any other suitable form.

[0131] In some embodiments, paging failure information may include the ID information of the A-IoT device (i.e., the paging ID) indicated in the paging message in which the failure occurred. For example, paging failure information may indicate a paging ID for which network entity 102-1 did not receive a response from the A-IoT device. In some embodiments, the A-IoT device ID information may include at least one of the following: device ID, tag ID, EPC ID, group ID, area ID, or at least a portion of data cached in the A-IoT device.

[0132] In some embodiments, paging failure information may include the ID information of the network entity 102-1 in which the failure occurred. For example, paging failure information may indicate the ID information of the node that did not receive a response from the A-IoT device.

[0133] In some embodiments, paging failure information may include the ID information of the service or task in which the failure occurred. For example, paging failure information may indicate the ID information of the service or task for which a response was not received from the A-IoT device. In some embodiments, paging failure information may include the preferred number of retransmissions of the paging message. For example, paging failure information may indicate the number of paging retransmissions required to change a paging failure into a paging success.

[0134] In some embodiments, network entity 102-1 may update the paging message upon determining that a paging failure has occurred. In some embodiments, network entity 102-1 may update the paging message with an increased paging area (i.e., a larger paging area). In some embodiments, network entity 102-1 may change the ID information of the A-IoT device set in the paging message. For example, network entity 102-1 may change at least one of the following: device ID, tag ID, EPC ID, group ID, area ID, or at least a portion of the data cached in the A-IoT devices.

[0135] So far, process 300 has described a solution for communicating with A-IoT devices. It should be understood that the operations in process 300 can be performed individually or in any combination.

[0136] Figure 4An example of a device 400 supporting communication with A-IoT devices according to various aspects of this disclosure is shown. Device 400 may be an example of a first, second, or third device as described herein. Device 400 may support wireless communication with one or more network entities 102, UE 104, core network element 103, or any combination thereof. Device 400 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 402, memory 404, transceiver 406, and optional I / O controller 408. These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0137] Processor 402, memory 404, transceiver 406, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 402, memory 404, transceiver 406, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0138] In some implementations, processor 402, memory 404, transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 402 and memory 404 coupled to processor 402 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 404 by processor 402).

[0139] For example, processor 402 may support wireless communication at example device 400 as disclosed herein. In some embodiments where device 400 is implemented as a first device, processor 402 may be configured to operate to support components for: receiving from a second device a message for paging a first set of devices, the first set of devices including the first device; determining that the message indicates a first operation that requires a response from the first device; and, based on determining that the message satisfies a condition for skipping a response, not responding to the message.

[0140] In some embodiments where device 400 is implemented as a second device, in one aspect, processor 402 may be configured to support components for: transmitting a message for paging a first set of devices; receiving a response from a first device in the first set of devices; and transmitting information about the first device to at least one of a second device or a third device. In another aspect, processor 402 may be configured to support components for: transmitting a message for paging a first set of devices; determining that a paging failure has occurred; and performing operations including at least one of: changing the transmission of an energy carrier set for the first set of devices, changing message retransmission, sending failure information to a third device, or updating the message.

[0141] Processor 402 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 402 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory (e.g., memory 404) to cause device 400 to perform various functions of this disclosure.

[0142] Memory 404 may include random access memory (RAM) and read-only memory (ROM). Memory 404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 402, cause device 400 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 402, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 404 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0143] I / O controller 408 can manage input and output signals for device 400. I / O controller 408 can also manage peripheral devices not integrated into device 400. In some implementations, I / O controller 408 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 408 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 408 can be implemented as part of a processor, such as processor 402. In some implementations, a user can interact with device 400 via I / O controller 408 or via hardware components controlled by I / O controller 408.

[0144] In some implementations, device 400 may include a single antenna 410. However, in other implementations, device 400 may have more than one antenna 410 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 406 may communicate bidirectionally via one or more antennas 410, wired or wireless links, as described herein. For example, transceiver 406 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 406 may also include a modem for modulating packets, providing modulated packets to one or more antennas 410 for transmission, and demodulating packets received from one or more antennas 410. Transceiver 406 may include one or more transmit chains, one or more receive chains, or a combination thereof.

[0145] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 410 for transmitting the amplified signal into the air or wireless medium.

[0146] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 410 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0147] Figure 5 An example of a processor 500 supporting communication with A-IoT devices according to various aspects of this disclosure is shown. Processor 500 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 500 may include a controller 502 configured to perform various operations according to the examples described herein. Processor 500 may optionally include at least one memory 504, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 500 may optionally include one or more arithmetic logic units (ALUs) 506. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0148] Processor 500 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 500)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0149] Controller 502 can be configured to manage and coordinate various operations of processor 500 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 500 to support various operations according to the examples described herein. For example, controller 502 can operate as a control unit of processor 500, generating control signals that manage the operation of various components of processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0150] Controller 502 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 504 and determine subsequent instructions(s) to be executed, enabling processor 500 to support various operations according to the examples described herein. Controller 502 can be configured to track the memory addresses of instructions associated with memory 504. Controller 502 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 502 can be configured to interpret instructions and determine control signals to be output to other components of processor 500, enabling processor 500 to support various operations according to the examples described herein. Additionally or alternatively, controller 502 can be configured to manage data flow within processor 500. Controller 502 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 500.

[0151] Memory 504 may include one or more caches (e.g., memory local to processor 500 or included in processor 500) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 504 may reside within or on the processor chipset (e.g., locally to processor 500). In some other implementations, memory 504 may reside outside the processor chipset (e.g., remotely from processor 500).

[0152] Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 500, cause processor 500 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 502 and / or processor 500 may be configured to execute computer-readable instructions stored in memory 504 to cause processor 500 to perform various functions. For example, processor 500 and / or controller 502 may be coupled to or coupled to memory 504, and processor 500, controller 502, and memory 504 may be configured to perform the various functions described herein. In some examples, processor 500 may include multiple processors, and memory 504 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0153] One or more ALU 506s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 506s may reside within or on the processor chipset (e.g., processor 500). In some other implementations, one or more ALU 506s may reside outside the processor chipset (e.g., processor 500). One or more ALU 506s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 506s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 506s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU506s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU506s to handle conditional operations, comparisons, and bitwise operations.

[0154] Processor 500 may support wireless communications as exemplified herein. In some embodiments where processor 500 is implemented at a first device, processor 500 may be configured or operable to support components for: receiving from a second device a message for paging a first set of devices, the first set of devices including the first device; determining that the message indicates a first operation requiring a response from the first device; and not responding to the message based on determining that the message satisfies a condition for skipping a response.

[0155] In some embodiments where the processor 500 is implemented at the second device, in one aspect, the processor 500 may be configured or operable to support components for: transmitting a message for paging a first set of devices; receiving a response from a first device in the first set of devices; and transmitting information about the first device to at least one of a second device or a third device. In another aspect, the processor 500 may be configured or operable to support components for: transmitting a message for paging a first set of devices; determining that a paging failure has occurred; and performing operations including at least one of: changing the transmission of an energy carrier set for the first set of devices, changing the message retransmission, sending failure information to a third device, or updating the message.

[0156] Figure 6 A flowchart of a method 600 supporting communication with an A-IoT device according to various aspects of this disclosure is shown. Operation of method 600 may be implemented by the device or components thereof described herein. For example, operation of method 600 may be performed by a first device described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the described functions.

[0157] At box 610, method 600 may include: at a first device, receiving from a second device a message for paging a first set of devices, the first set of devices including the first device. In this case, the identification information of the first device matches an identification information from the identification information of the first set of devices. The operation of 610 can be performed according to the examples described herein. In some implementations, aspects of the operation of 610 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0158] At box 620, method 600 may include: determining that the message indicates a first operation that requires a response from a first device. The operation at 620 can be performed according to the examples described herein. In some implementations, aspects of the operation at 620 may be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0159] At box 630, method 600 may include: if the message meets the conditions for skipping a response, then do not respond to the message. The operation at 630 can be performed according to the examples described herein. In some implementations, aspects of the operation at 630 may be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0160] In some embodiments, method 600 may further include: if the message does not meet the conditions, initiating random access to the second device. In some embodiments, method 600 may further include: if the message indicates a second operation, performing the second operation, which does not require a response from the first device. In some embodiments, method 600 may further include: if the identification information of the first device set does not match the identification information of the first device, then not performing any operation.

[0161] In some embodiments, the condition may include at least one of the following: the message is the same as another message that has already been responded to; an indication to end the response has been received; the status of the first device indicates that the first operation has been performed; the identification information of the second device is the same as that of another second device that sent another message; the second device is in the list of second devices that have been responded to; the message was not first received from the second device; the message was not the first message to be responded to; or the ongoing service or task has not been completed.

[0162] In some embodiments, the indication to end the response may be associated with at least one of the following: identification information of the first device indicated in the message, the reason indicated in the message, identification information of the second device, or identification information of the service or task indicated in the message. In some embodiments, the identification information of the first device may include at least one of the following: device identifier of the first device; tag identifier of the first device; EPC identifier of the first device; group identifier of the first device; region identifier of the first device; or at least a portion of data cached in the first device. In some embodiments, the validity of the indication to end the response may be associated with at least one of the following: duration, number of paged requests to the first device, or energy of the first device.

[0163] In some embodiments, method 600 may further include: receiving a command from a second device for changing the state of the first device. In some embodiments, method 600 may further include: if the first operation is successfully executed, changing the state of the first device to indicate that the first operation was successfully executed.

[0164] In some embodiments, a list of the second devices responding may be included in the message.

[0165] Figure 7 A flowchart of another method 700 supporting communication with an A-IoT device according to various aspects of this disclosure is shown. Operation of method 700 can be implemented by the device or components thereof described herein. For example, operation of method 700 can be performed by a second device described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0166] At box 710, method 700 may include sending a message for paging a first set of devices. The operation of 710 can be performed according to the examples described herein. In some implementations, aspects of the operation of 710 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0167] At box 720, method 700 may include: receiving a response from a first device in the first device set. The operation of 720 can be performed according to the examples described herein. In some implementations, aspects of the operation of 720 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0168] At box 730, method 700 may include: sending information of the first device to at least one of a second device or a third device. The operation of 730 can be performed according to the examples described herein. In some implementations, aspects of the operation of 730 may be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0169] In some embodiments, the information of the first device may include at least one of the following: identification information of the first device, the status of the first device, or identification information of a second device that receives a response from the first device. In some embodiments, the identification information of the first device may include at least one of the following: device identifier of the first device; tag identifier of the first device; EPC identifier of the first device; group identifier of the first device; region identifier of the first device; or at least a portion of the data cached in the first device.

[0170] In some embodiments, method 700 may further include: receiving from a third device another message for paging another set of first devices, the other message including a list of second devices that are responding.

[0171] In some embodiments, the first device may be an A-IoT device, the second device may be a base station or a communication node between the base station and the A-IoT device, and the third device may be a CN element.

[0172] Figure 8 A flowchart of another method 800 supporting communication with an A-IoT device according to various aspects of this disclosure is shown. Operation of method 800 may be implemented by the device or components thereof described herein. For example, operation of method 800 may be performed by a second device described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the described functions.

[0173] At box 810, method 800 may include sending a message for paging a first set of devices. The operation of 810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 810 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0174] At box 820, method 800 may include determining that a paging failure has occurred. The operation of 820 can be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0175] In some embodiments, determining that a failure has occurred may include determining that a failure has occurred based on at least one of the following: no response was received from the first set of devices during a first time window; no response was received from the first set of devices at the resource; the number of first devices that responded during a second time window is less than or equal to a number threshold; the ratio of the first devices that responded during a third time window is less than or equal to a ratio threshold; or a response from a subset of the first devices in the first set of devices is missing.

[0176] At block 830, method 800 may include performing an operation that includes at least one of the following: changing the transmission of an energy carrier set for a first set of devices, changing the retransmission of the message, sending a failure message to a third device, or updating the message. The operation of 830 may be performed according to the examples described herein. In some implementations, aspects of the operation of 830 may be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0177] In some embodiments, altering the transmission of the energy carrier may include: transmitting the energy carrier at increased power or time; or causing the energy source to transmit the energy carrier at increased power or time.

[0178] In some embodiments, changing message retransmission may include retransmitting the message an increased number of times.

[0179] In some embodiments, the failure information may include at least one of the following: the reason for the failure; identification information of the first device indicated in the message, where the failure occurred during paging for the first device; identification information of the second device in which the failure occurred; identification information of the service or task in which the failure occurred; or a preferred number of retransmissions of the message. In some embodiments, the identification information of the first device may include at least one of the following: the device identifier of the first device; the tag identifier of the first device; the EPC identifier of the first device; the group identifier of the first device; the area identifier of the first device; or at least a portion of the data cached in the first device.

[0180] In some embodiments, updating the message may include at least one of the following: updating the message with an increased paging area; or changing the identification information of the first set of devices in the message.

[0181] In some embodiments, the first device may be an A-IoT device, the second device may be a base station or a communication node between the base station and the A-IoT device, and the third device may be a CN element.

[0182] It should be understood that the operations of methods 600 to 800 correspond to the information regarding... Figure 3 The operations described herein will not be elaborated upon here for the sake of brevity.

[0183] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0184] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0185] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0186] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0187] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0188] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first device, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: The transceiver receives a message from the second device for paging a first set of devices, the first set of devices including the first device; The message indicates a first operation, which requires a response from the first device. as well as If the message is determined to meet the conditions for skipping the response, no response is given to the message.

2. The first device according to claim 1, wherein the processor is further configured to be at least one of the following: If the message does not meet the conditions, a random access to the second device is initiated via the transceiver; or The second operation is performed according to the message indicating the second operation, which does not require a response from the first device.

3. The first device according to claim 1, wherein the condition includes at least one of the following: The message is the same as another message that has already been responded to; An indication to end the response is received; The status of the first device indicates that the first operation has been performed; The identification information of the second device is the same as the identification information of the other second device that sent the other message; The second device is in the list of second devices that responded; The message was not first received from the second device; The message in question was not the first message to be responded to. or The ongoing service or task has not been completed.

4. The first device of claim 3, wherein the indication to end the response is associated with at least one of the following: The identification information of the first device indicated in the message, The reason indicated in the message, The identification information of the second device, or Identification information of the service or task indicated in the message.

5. The first device according to claim 4, wherein the identification information of the first device includes at least one of the following: The device identifier of the first device; The label of the first device; The Electronic Product Code (EPC) identifier of the first device; The group identifier of the first device; The area identifier of the first device; or At least a portion of the data cached in the first device.

6. The first device of claim 3, wherein the validity of the indication to terminate the response is associated with at least one of the following: Duration, The number of times the first device is paged, or The energy of the first device.

7. The first device according to claim 3, wherein the processor is further configured to: Receive a command from the second device to change the state of the first device; or Based on the determination that the first operation was successfully executed, the state of the first device is changed to indicate that the first operation was successfully executed.

8. The first device according to claim 3, wherein the list of the responding second devices is included in the message.

9. A second device, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: The transceiver sends a message for paging the first set of devices. Receive a response from a first device in the first set of devices via the transceiver; and The information of the first device is transmitted to at least one of a second or third device via the transceiver.

10. The second device according to claim 9, wherein the processor is further configured to: The transceiver receives from the third device another message for paging another set of first devices, the other message including a list of second devices that are responding.

11. The second device according to claim 9, wherein the information of the first device includes at least one of the following: The identification information of the first device, The status of the first device, or The identification information of the second device, and the second device receives the response from the first device.

12. A second device, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: The transceiver sends a message for paging the first set of devices. It has been determined that a paging failure occurred; as well as Perform an operation, the operation including at least one of the following: Change the transmission of the energy carrier set for the first set of devices. Modify the retransmission of the aforementioned message. Send the failure message to a third device, or Update the message.

13. The second device of claim 12, wherein the processor is configured to determine that the failure has occurred by: The failure is determined to have occurred based on at least one of the following: No response was received from the first set of devices during the first time window; No response was received from the first set of devices at the resource point; The number of first devices responding within the second time window is less than or equal to the number threshold. Within the third time window, the ratio of the first responding devices in the first device set is less than or equal to the ratio threshold; or The response from a subset of the first devices in the first set of devices is missing.

14. The second device of claim 12, wherein the processor is configured to modify the transmission of the energy carrier by: The energy carrier is transmitted with increased power or time; or This causes the energy source to transmit the energy carrier at increased power or time.

15. The second device of claim 12, wherein the processor is configured to modify the retransmission of the message by: The message is retransmitted an increased number of times.

16. The second device of claim 12, wherein the failure information includes at least one of the following: The reason for the failure; The identification information of the first device indicated in the message indicates that the failure occurred during paging of the first device; The identification information of the second device in which the failure occurred; The identification information of the service or task in which the failure occurred; or The preferred number of times the message is retransmitted.

17. The second device according to claim 11 or 16, wherein the identification information of the first device includes at least one of the following: The device identifier of the first device; The label of the first device; The Electronic Product Code (EPC) identifier of the first device; The group identifier of the first device; The area identifier of the first device; or At least a portion of the data cached in the first device.

18. The second device of claim 12, wherein the processor is configured to update the message by at least one of the following: Update the message with the added paging area; or Change the identification information of the first set of devices in the message.

19. The second device according to claim 9 or 12, wherein the first device is an environmental Internet of Things (A-IoT) device, the second device is a base station or a communication node between the base station and the A-IoT device, and the third device is a core network element.

20. A processor for wireless communication, comprising: At least one memory; as well as A controller, coupled to the at least one memory, and configured such that the processor: Receive a message from a second device for paging a first set of devices, the first set of devices including the first device; The message indicates a first operation, which requires a response from the first device. as well as If the message is determined to meet the conditions for skipping the response, no response is given to the message.

Images