Apparatus for backscatter communication

Abstract

A method and apparatus for backscatter communication are provided herein. The method comprises: receiving, at an activator, a configuration of a physical random access channel (PRACH) resource; receiving, from a network node, a request to provide assistance for activating an environmental Internet of Things AIoT device; determining information for activating transmission of a signal to activate a physical uplink shared channel (PUSCH) resource required by the AIoT device, and selecting a PRACH resource associated with the information of the PUSCH resource from the provided PRACH resource; sending an indication to the network node via the selected PRACH resource, the indication indicating that the activator is to provide an activation signal on a PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform backscatter transmission; and on a PUSCH resource associated with the selected PRACH resource, sending an activation signal to the AIoT device to trigger backscatter transmission from the AIoT device.

Description

[0001] This application claims priority to GB application number 2308233.2, filed on June 2, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0002] Various example embodiments relate to apparatus for backscatter communication. Further embodiments relate to methods of operation associated with such apparatus. Background Technology

[0003] In the context of at least some traditional communication networks, an important aspect is sustainability, which includes, for example, zero-energy communication. This term refers to end devices, such as environmental IoT devices, that operate without batteries, but may have energy harvesting capabilities (e.g., energy stored in capacitors) or may not have batteries and no energy storage capabilities.

[0004] One candidate technology for ultra-low-energy or zero-energy devices is a tag for receiving / transmitting radio frequency signals, such as a backscatter tag, whereby an activator sends a radio frequency signal to activate the IoT device. In some systems, the tag modulates the input radio frequency signal, for example, using an information-carrying signal (e.g., by reflection), and the reflected signal can be received by a receiver. This modulated reflected signal is called backscatter transmission. Summary of the Invention

[0005] The scope of protection sought by the various embodiments of the present invention is set forth in the independent claims. Embodiments and features (if any) described in this specification that do not fall within the scope of the independent claims are to be interpreted as examples that aid in understanding the various embodiments of the invention.

[0006] According to a first aspect, an apparatus is described, comprising: means for receiving configuration of Physical Random Access Channel (PRACH) resources at an activator. The apparatus further comprises: means for receiving, at the activator, a request from a network node to assist the activator in activating an AIoT device in an environment. The apparatus further comprises: means for determining, at the activator, information about Physical Uplink Shared Channel (PUSCH) resources required for transmitting an activation signal to activate the AIoT device. The apparatus further comprises: means for selecting, at the activator, a PRACH resource associated with the PUSCH resource information from the provided PRACH resources. The apparatus further comprises: means for sending an instruction from the activator to the network node via the selected PRACH resource, the instruction indicating that the activator will provide an activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform a backscatter transmission. The apparatus further comprises: means for sending an activation signal from the activator to the AIoT device on the PUSCH resource associated with the selected PRACH resource to trigger a backscatter transmission from the AIoT device.

[0007] In some embodiments, the apparatus may further include a component for receiving an acknowledgment command from the network node by the activator to confirm that the backscatter transmission from the AIoT device has been received at the network node.

[0008] In some embodiments, the configuration may be received via RRC reconfiguration when the activator transitions to an RRC connected state, or via system information broadcast. In some embodiments, the configured PRACH resources may include: at least one PRACH preamble root sequence and AIoT-related configuration of cyclic shifts, and random access channel (RACH) timing in which the PRACH preamble can be applied at various times and frequencies.

[0009] In some embodiments, the configuration may include information about PUSCH resources and information about the association between PRACH resources.

[0010] In some embodiments, the apparatus may further include: a component for receiving a Msg2-RAR signal from a network node at the activator, the Msg2-RAR signal including: an indication of a PUSCH to be used to send an activation signal.

[0011] In some embodiments, the request to the activator to provide assistance for activating AIoT is based on a dedicated paging message or on RRC signaling.

[0012] In some embodiments, the device may be an AIoT or a user equipment (UE).

[0013] In some embodiments, the network node may be a radio access network (RAN) base station.

[0014] In some embodiments, the component may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to execute.

[0015] According to a second aspect, a method is described, comprising: receiving configuration of Physical Random Access Channel (PRACH) resources at an activator. The method further comprises: receiving from a network node at the activator a request to provide assistance to the activator for activating an AIoT device in an environment. The method further comprises: determining at the activator information on Physical Uplink Shared Channel (PUSCH) resources required for activating the AIoT device through the transmission of an activation signal. The method further comprises: selecting at the activator a PRACH resource associated with the PUSCH resource information from the provided PRACH resources. The method further comprises: sending an indication from the activator to the network node via the selected PRACH resource, the indication indicating that the activator will provide an activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform a backscatter transmission. The method further comprises: sending an activation signal from the activator to the AIoT device on the PUSCH resource associated with the selected PRACH resource to trigger a backscatter transmission from the AIoT device.

[0016] According to a third aspect, a computer program product is provided, the computer program product including an instruction set that, when executed on a device, is configured to cause the device to perform a method defined according to any of the foregoing methods.

[0017] According to a fourth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions stored thereon for performing a method, the method comprising: receiving configuration of Physical Random Access Channel (PRACH) resources at an activator. The method further comprises: receiving from a network node at the activator a request to provide assistance to the activator for activating an environment Internet of Things (AIoT) device. The method further comprises: determining at the activator information on Physical Uplink Shared Channel (PUSCH) resources required for the transmission of an activation signal to activate the AIoT device. The method further comprises: selecting at the activator a PRACH resource associated with the PUSCH resource information from the provided PRACH resources. The method further comprises: sending an indication from the activator to the network node via the selected PRACH resource, the indication indicating that the activator will provide an activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform a backscatter transmission. The method further comprises: sending an activation signal from the activator to the AIoT device on the PUSCH resource associated with the selected PRACH resource to trigger a backscatter transmission from the AIoT device. Attached Figure Description

[0018] Exemplary embodiments will now be described by way of non-limiting example with reference to the accompanying drawings, in which:

[0019] Figure 1 The network architecture of the communication system is illustrated through examples.

[0020] Figure 2 The topology of an environmental IoT device according to the first embodiment is illustrated by way of example.

[0021] Figure 3 The topology of an environmental IoT device according to the second embodiment is illustrated by way of example.

[0022] Figure 4 The topology of an environmental IoT device according to the third and fourth embodiments is illustrated by way of example.

[0023] Figure 5 The topology of an environmental IoT device according to the fifth embodiment is illustrated by way of example.

[0024] Figure 6 a topology of an environmental IoT device according to the present invention is illustrated by way of example.

[0025] Figure 6 b illustrates a signaling flow description according to the present invention by way of example;

[0026] Figure 7 The flowchart of the method is shown through examples;

[0027] Figure 8 The signaling flow description of AIoT device activation as part of the dedicated PRACH preamble RACH process for a 2-step RACH implementation is illustrated by way of example.

[0028] Figure 9 The signaling flow description for AIoT device activation, which is part of the dedicated PRACH preamble RACH process used for a 4-step RACH implementation, is illustrated by way of example.

[0029] Figure 10 The signaling flow description for AIoT device activation as part of a competition-based RACH process for a 2-step RACH implementation is illustrated by way of example.

[0030] Figure 11 The signaling flow description for AIoT device activation as part of a competition-based RACH process for a 4-step RACH implementation is illustrated by way of example.

[0031] Figure 12 A block diagram of the device is shown as an example. Detailed Implementation

[0032] Example embodiments may relate to apparatus, methods, and / or computer programs for managing TCI state activation.

[0033] Figure 1 The network architecture of a communication system, specifically a Radio Access Network (RAN), is illustrated by way of example. In the following description, different exemplary embodiments will be used as examples of access architectures to which embodiments can be applied, based on Long Term Evolution Advanced (LTE-A, LTE-A) or New Radio (NR) (also known as fifth generation (5G)). However, the embodiments are not intended to be limited to such architectures. Embodiments can also be applied to other types of communication networks with suitable components by appropriately adjusting parameters and processes. Some examples of other options suitable for the system are: Universal Mobile Telecommunications System, Radio Access Network, Long Term Evolution (LTE), Wireless Local Area Network (WLAN or WiFi), Global Microwave Access Interoperability (WiMAX), Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0034] Figure 1First and second user equipments 100 and 102 are shown, configured to wirelessly connect to network nodes (such as network node 104 providing the cell) on one or more communication channels in a cell. The physical link from a user equipment (e.g., first user equipment 100) to network node 104 is referred to as an uplink (UL) or reverse link, and the physical link from a network node to a user equipment is referred to as a downlink (DL) or forward link. It should be understood that network nodes and their functions can be implemented using any node, host, server, or access point entity suitable for such use. Communication systems typically include more than one network node, in which case the network nodes can also be configured to communicate with each other via wired or wireless links designed for this purpose. These links can be used for signaling purposes. A network node is a computing device configured to control the radio resources of the communication system to which it is coupled. A network node can also be referred to as a TRP, base station (BS), access point, or any other type of interface device including a relay station capable of operating in a wireless environment. A network node may include or be coupled to a transceiver. The connection from the transceiver of network node 104 can be provided to an antenna unit that establishes a bidirectional wireless link to user equipment (such as first and second user equipment 100, 102). The antenna unit may include multiple antennas or antenna elements, for example, arranged as an antenna array. Network node 104 may also be connected to core network 110.

[0035] User equipment (UE) generally refers to portable computing devices, including wireless mobile communication devices operating with or without a Subscriber Identity Module (SIM), including but not limited to: mobile stations (mobile phones), smartphones, personal digital assistants, cell phones, devices using wireless modems (such as alarm or measuring devices), laptops and / or touchscreen computers, tablets, game consoles, laptops, and multimedia devices. It should be understood that a UE can also be a virtually exclusively uplink-only device, an example of which is a camera or video camera that loads images or video clips onto a network. A UE can also be a device capable of operating in an Internet of Things (IoT) network, where objects are provided with the ability to transmit data over the network without requiring human-to-human or human-to-computer interaction.

[0036] 5G enables the use of multiple-input multiple-output (MIMO) technologies on both the UE and network node sides, with far more base stations or nodes than LTE. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different methods of data sharing, and applications across various machine types, including vehicle safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces: below 7 GHz, cmWave, and mmWave, and can also integrate with existing legacy radio access technologies such as LTE. Accordingly, the frequency range below 7 GHz can be referred to as FR1, and the frequency range above 24 GHz (or more precisely, 24–52.6 GHz) can be referred to as FR2. Integration with LTE can be implemented, at least initially, as a system where macro coverage is provided by LTE, and 5G radio interface access is provided through small cells aggregated to LTE.

[0037] The communication system can also communicate with other networks, such as the public switched telephone network or the Internet, or utilize services provided by them. The communication network can also support the use of cloud services; for example, at least a portion of core network operations can be performed as a cloud service (this is in...). Figure 1 (As shown in “Cloud” 114). The communication system may also include a central control entity, etc., to provide facilities for different operators’ networks to cooperate, for example, in spectrum sharing.

[0038] Edge cloud can be introduced into the radio access network (RAN). Using edge cloud means that access node operations are performed at least partially in servers, hosts, or nodes that are operatively coupled to remote radio heads or base stations, including the radio portion. Node operations can also be distributed across multiple servers, nodes, or hosts. The application of cloud RAN architecture enables real-time RAN functions to be performed on the RAN side (in the distributed unit, DU 104), while non-real-time functions are performed in a centralized manner (in the centralized unit, CU 108).

[0039] Beam management is applied during the Random Access Channel (RACH) procedure when the UE establishes an initial connection with the network and while the UE is in a connected state. In the connected state, the transmit and receive beams can be refined.

[0040] User equipment can also be a device capable of operating in an Internet of Things (IoT) network, where objects are provided with the ability to transmit data over the network without requiring human-to-human or human-to-computer interaction. Regarding IoT applications, 3GPP specified NB-IoT / eMTC and NR RedCap prior to Release 18 to meet the requirements for low-cost and low-power devices for wide-area IoT communication. These IoT devices typically consume tens or hundreds of milliwatts of power during transmission and reception, at a cost of a few dollars. However, to achieve the Internet of Everything, devices with ten or even a hundred times lower cost and power consumption are needed, especially for large-scale applications requiring battery-free devices.

[0041] The number of IoT connections has grown rapidly in recent years and is expected to reach billions by 2030. As the expectation grows for more interconnected "things" to improve productivity and enhance quality of life, there is a need for further reductions in the size, cost, and power consumption of IoT devices. In particular, regular battery replacements for all IoT devices are impractical due to the significant material and human resource costs. Using energy harvested from the environment to power IoT devices for self-sustaining communication has become a trend, especially in applications with a large number of devices such as ID tags and sensors.

[0042] The most critical issue with existing 3GPP technologies for the target use case is their ability to work in conjunction with energy harvesting, taking into account the limited device size. Cellular devices typically consume tens or even hundreds of milliwatts of power for transceiver processing. For example, in an NB-IoT module, the typical current consumption for receive processing is approximately 60 mA at a supply voltage above 3.1 V, while the current consumption for transmit processing is 70 mA at 0 dBm transmit power. Furthermore, considering the small size of a few square centimeters in actual devices, the output power provided by a typical energy harvester is mostly less than 1 milliwatt. Since the available power is far less than the power consumed, directly powering cellular devices via energy harvesting is impractical in most cases.

[0043] One possible solution is to integrate energy harvesting with rechargeable batteries or supercapacitors. However, several issues remain to be addressed. First, in practice, both rechargeable batteries and supercapacitors can suffer from shortened lifespans. Providing a constant charging current or voltage through energy harvesting is difficult, while requiring long periods of continuous charging due to the very small output power from the energy harvester. Both non-constant charging current and long periods of continuous charging are detrimental to battery life. For supercapacitors, their lifespan will be significantly reduced in high-temperature environments (e.g., less than 3 years at 50 degrees Celsius). Second, device size will increase significantly. Since small coin cells can only provide tens of milliamps of current, much larger batteries (e.g., AA batteries) are typically used to power cellular devices, and their size can even exceed that of the module itself. To store energy for a suitable operating duration (e.g., 1 second), supercapacitors require capacitance in the hundreds of millifarads range. Such supercapacitors can be larger than NB-IoT modules. Third, both rechargeable batteries and supercapacitors can be more expensive than the module itself. Even with bulk purchases, the cost of a suitable battery or supercapacitor can reach one or several dollars, which almost doubles the cost of the equipment.

[0044] RFID is the most well-known technology supporting battery-free tags (devices). Commercial passive RFID tags can consume as little as 1 microwatt. Key technologies enabling this low power consumption are envelope detection for downlink data reception and backscatter communication for uplink data transmission. RFID is designed for short-range communication, with a typical effective range of less than 10 meters. Because the RFID air interface has remained virtually unchanged since 2005, its overly simplistic transmission scheme has become an obstacle to improving its link budget and ability to support scalable networks.

[0045] Attracted by the extremely low power consumption of backscatter communication, many non-3GPP technologies, such as Wi-Fi, Bluetooth, UWB, and LoRa, have begun related research. Various studies show that power consumption of a few microwatts or tens of microwatts for passive tags can be supported based on or with minor modifications to these air interfaces. Most of the research targets long-range communication. For example, LoRa tags implemented using commercially available off-the-shelf components can transmit their sensing data to a receiver up to 381 meters away. Currently, most research focuses on individual, detailed techniques for various optimization objectives. Seeing a comprehensive system design that fully meets the requirements of the target use cases is difficult. However, standardization of those technologies is flexible and rapid because industry typically follows some practical standards. This means that many products on the market will even adhere to proprietary standards when they demonstrate competitiveness in certain applications.

[0046] Passive radio is a device that utilizes energy from a wireless signal transmitted on a specific carrier and / or bandwidth to charge a simple circuit system that, when activated, transmits / reflects a signal that at least encodes the ID of the passive radio. A typical system architecture surrounding passive radio consists of the following: 1. Activator: A device that sends an activation signal aimed at waking up a passive radio. 2. Passive Radio: Utilizes energy across a frequency range and listens for active signals. When such a signal is detected, the passive radio transmits / reflects a signal specific to that radio ID. 3. Reader: A device for listening to and detecting passive radio signals. The reader may or may not be placed alongside the activator.

[0047] The following two main types of energy storage are considered: 1. Passive: A completely battery-free device that has no energy storage capability and is entirely dependent on the availability of an external energy source. 2. Semi-passive: A device with limited energy storage capacity that does not require manual replacement or charging.

[0048] Environmental IoT devices can be passive or semi-passive in terms of their energy storage.

[0049] Several connectivity topologies for environmental IoT networks and devices are disclosed. In all these topologies, environmental IoT devices can be provided with carriers from (multiple) other nodes inside or outside the topology. Links in each topology can be bidirectional or unidirectional. BS, UE, auxiliary nodes, or intermediate nodes can be multiple BSs or UEs, respectively. Such a mix of indoor and outdoor node arrangements is considered a network implementation option.

[0050] An Ambient Internet of Things (AIoT) system, in its simplest form, consists of an AIoT activator, an AIoT reader, and an AIoT device. In a topology known as monopolar, the AIoT activator and reader are the same network element (or device). This means that responses to the AIoT device are backscattered transmissions, and the network element (or device) acting as both the AIoT activator and reader can operate in full-duplex mode, sending an activation signal while receiving a response from the AIoT device. Conversely, in a topology known as bipolar (or multipolar), the AIoT activator and reader are two distinct network elements (or devices), and therefore, full-duplex operation is no longer required in the AIoT activator and reader devices. Thus, from the perspective of NW and non-AIoT-enabled devices, bipolar topology is considered less technically challenging. The activator discussed in this paper is both for illustrative purposes and because the activator needs to be near both the AIoT device and, therefore, may also be a device / UE.

[0051] According to the first topology, such as Figure 2 As shown, the environmental IoT device 210 communicates with the base station 220 directly or bidirectionally. Communication between the base station 220 and the environmental IoT device 210 includes environmental IoT data and / or signaling. This topology allows for the possibility that the BS sent to the environmental IoT device differs from the BS received from the environmental IoT device.

[0052] According to the second topology, such as Figure 3 As shown, the environmental IoT device 310 communicates bidirectionally with the intermediate node 330 between the environmental IoT device 310 and the base station 320. In this topology, the intermediate node 330 can be a relay, IAB node, UE, repeater, etc., capable of environmental IoT. The intermediate node 330 transmits information between the BS and the environmental IoT device.

[0053] According to the third topology, such as Figure 4 As shown in a and 4b, the environmental IoT device 410 sends data / signaling to the base station 420 and receives data / signaling from the auxiliary node 430 (e.g., ...). Figure 4 (A is shown for downlink assistance). Alternatively, environmental IoT device 410 receives data / signaling from base station 420 and sends data / signaling to auxiliary node 430 (e.g., ...). Figure 4 (b is shown for uplink assistance). In the third topology, the auxiliary node 430 can be a relay, IAB, UE, repeater, etc., capable of enabling IoT environments.

[0054] According to the fourth topology, such as Figure 5 As shown, the environmental IoT device 510 communicates bidirectionally with the UE 540. The communication between the UE 540 and the environmental IoT device 510 includes environmental IoT data and / or signaling.

[0055] In this invention, we focus on such as Figure 6 The third topology shown in Figure a. When viewing as... Figure 6 During the Phase-1 signaling flow shown in b, the interaction between network node 620, activator (i.e., auxiliary node) 630, and AIoT device 610 can be observed to consist of the following steps. First, as shown in b... Figure 6 As shown in item 1 of b, network node 620 requests the auxiliary device (i.e., the activator) to activate the AIoT device. Secondly, as... Figure 6 As shown in item 2 of b, activator 630 sends an activation signal, which is a signal carrier suitable for backscattering (i.e., for AIoT to modulate its response signal). Subsequently, as... Figure 6 As shown in item 3 of b, the AIoT device 610 responds to the network node 620 using a backscatter signal.

[0056] The challenge of this interaction lies in the need to allocate resources for the activation and reception of the backscattered signal for any of these steps. One approach would be to have the gNB, along with its resource allocation request (i.e., in...). Figure 6 Step 1 of b provides resource allocation, which will allow activation and backscatter signals to be sent. However, since the activator may not be in an RRC connected state, it becomes necessary to decouple the auxiliary requests from the actual resource reservations used for activation / backscatter signal transmission. The subject matter disclosed herein addresses this problem.

[0057] Figure 7 A flowchart of a method according to an exemplary embodiment is shown by way of example. Each element of the flowchart may include one or more operations. Operations may be performed in hardware, software, firmware, or a combination thereof. For example, operations may be performed individually or jointly by components, wherein the components may include at least one processor; and at least one memory, wherein the instructions, when executed by the at least one processor, cause the execution of the operations.

[0058] Method 700 includes a first operation 710 of receiving configuration of physical random access channel (PRACH) resources at activator 630. The configuration may be received from network node 620.

[0059] In the case of dedicated RACH resources, this configuration can be provided during the RRC reconfiguration step when the UE has transitioned to and is included in the RRC connected state. For 4-step RACH, the RACH resource configuration may include the PRACH preamble root sequence and cyclic shift, as well as the RACH timing in which the PRACH preamble can be applied at time and frequency. Alternatively, for 2-step RACH, the configuration may include, in addition to the PRACH preamble and timing, information about the PUSCH resources associated with those PRACH preambles. In both 2-step and 4-step RACH, the allocated PRACH preambles are associated with different PUSCH resource profiles and types that allow for the fulfillment of AIoT communication requirements. For example, different PUSCH resource profiles and types may define different resource element organizations in time and frequency, and / or different numbers of PRBs, for different AIoT communication requirements. For example, a higher number of physical resource blocks (PRBs) associated with PUSCH resources in frequency is necessary for location-type applications, while a smaller number of PRBs are needed for communication. While a higher number of PRBs associated with PUSCH resources may be needed during a given time period to ensure AIoT devices have sufficient charge to initiate backscatter transmissions, Physical Resource Blocks (PRBs) are the smallest units of resources that can be allocated to users. The NR framework uses PRBs as a way to allocate time and frequency resources to users. Each PRB consists of a certain number of consecutive subcarriers for a specific time period. Depending on the specific implementation of the NR standard, the specific number and duration of the subcarriers can vary. The use of PRBs allows the network to efficiently allocate resources to users, ensuring that each user receives the bandwidth they need. This can be dynamically adjusted based on demand, allocating more PRBs during periods of high demand.

[0060] In the case of contention-based RACH resources, this configuration is provided as part of the system information, wherein the indication of the RACH resources associated with AIoT is explicitly specified. Note that in the case of contention-based RACH resources, the RACH resources may include all RACH preambles available in the RACH at the appropriate time and frequency, or only a portion of those available RACH preambles.

[0061] Method 700 includes a second operation 702 at the activator receiving a request from a network node to provide assistance to the activator for activating environmental Internet of Things (AIoT) devices.

[0062] If network node 620 does not have prior information about the relative positions of the (multiple) activators 630 or AIoT devices 610, the network node can request multiple activators 630 to activate the same AIoT device. This is beneficial in providing a greater opportunity to activate AIoT devices 610. In the case of dedicated PRACH resources, all these activators 630 will send the same PRACH preamble to the network node and thus perform the transmission of the activation signal in the same PUSCH resource, which allows the AIoT device to receive a stronger activation signal because the signal will be an overlap of multiple activation signals. Alternatively, in the case of contention-based PRACH resources, each activator 630 uniformly, randomly, and independently selects one of the available contention-based PRACH resources and thus performs the transmission of the activation signal in the corresponding PUSCH resource. If all activators 630 select the same PRACH resource, then it will also send the activation signal in the same PUSCH resource. However, it is more likely that each activator will select a different PRACH resource, and therefore the transmission of the activation signal will be performed in a separate PUSCH resource. In this case, network node 620 will receive different instances of the same backscattered signal, enabling diversity in the reception of backscattered transmissions. However, for cases where diversity is not required, a drawback of this method is the unnecessary power consumption on the tags.

[0063] The method for making the request can be based on a dedicated paging message (for activator devices in RRC idle / inactive state) or on RRC signaling for activators in RRC connected state. Although the request can be made when the activator UE is in RRC connected state, the activator can still switch to RRC idle / inactive state and can still perform the transmission of activation signals in that state.

[0064] The method includes a third operation 703 at the activator to determine information about the physical uplink shared channel (PUSCH) resources required for the transmission of an activation signal to activate the AIoT device 610. This information may be a profile or type of the PUSCH resources required for the transmission of the activation signal.

[0065] The method includes a fourth operation 704 at activator 630 selecting a PRACH resource associated with information about the PUSCH resource from the provided PRACH resource. This operation may include selecting an appropriate PRACH preamble and PRACH timing.

[0066] The method includes a fifth operation 705 in which the activator 630 sends an instruction to the network node 620 via a selected PRACH resource, the instruction indicating that the activator 630 will provide an activation signal on a PUSCH resource associated with the selected PRACH resource to activate the AIoT device 610 to perform a backscatter transfer. In response to this operation, the network node 620 can know that the activator 630 will trigger the AIoT device 610 to perform a backscatter transfer, and that the transfer will occur in the PUSCH resource associated with the activated PRACH resource (e.g., the selected PRACH preamble and PRACH timing).

[0067] The method includes a sixth operation 706: sending an activation signal from an activator to an AIoT device on a PUSCH resource associated with a selected PRACH resource to trigger a backscatter transmission from the AIoT device.

[0068] Optionally, the method may include: receiving an acknowledgment command from network node 620 by activator 630 to confirm that the backscatter transmission from AIoT device 610 has been received at network node 620.

[0069] Several technical advantages are associated with the proposed method. First, the proposed method provides the activator 630 with flexibility regarding the timing of its activation signal transmission, thus enabling the activator device to avoid in-device coexistence issues. Second, it establishes a mechanism that allows the activator 630 to notify the network node 610 when it will send an activation signal, thus allowing the network to be ready to receive backscatter signals. Additionally, the method allows activator UEs 630 in RRC idle / inactive states (and activator UEs in RRC connections without SR configuration) to access resources to send activation signals without needing to switch RRC connections and request dedicated resources from the NW. Due to the reduced number of signaling messages, the protocol provides a more energy-efficient method for activating backscatter transmissions from AIoT devices.

[0070] Figure 8 This is another flowchart 800 of the method according to an example embodiment. Each element of the flowchart may include one or more operations. Operations may be performed in hardware, software, firmware, or a combination thereof. For example, operations may be performed individually or jointly by components, wherein the components may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of the operation. Operations may be performed, for example, in a UE (such as...). Figure 1 The UE 100 shown or Figure 6 It is executed at activator 620 shown in a.

[0071] Figure 8 An exemplary embodiment of the signaling flow description for AIoT device activation, which is part of a dedicated PRACH preamble RACH process for a 2-step RACH implementation, is shown.

[0072] In some embodiments, the activator may perform an initial access procedure and transition to an RRC connected state (802). Network node 610 may initiate an RRC reconfiguration procedure, which may include the configuration of a dedicated 2-step RACH resource to be used for the AIoT use case and an indication of the associated PUSCH profile or type (804). Optionally, network node 610 may configure multiple dedicated PRACH preambles, where each PRACH preamble is associated with a different profile or type of PUSCH resource, such as, for example, a different number of PRBs for the time and / or frequency of the MsgA-PUSCH resource, to meet the requirements for AIoT communication. For example, for location-type applications, a higher number of PRBs in the frequency is necessary, while a smaller number of PRBs is required for communication. A higher number of PRBs in the time may be required to ensure that the AIoT has sufficient charge to initiate backscatter transmission.

[0073] In some embodiments, the activator confirms RRC reconfiguration (806). A network node may request the activator device to provide assistance for activating an AIoT device (808). For an activator (630) in an RRC idle / inactive state, the request may be made in the form of a paging message. This paging message may include an identifier of the activator device (630), a request for activation assistance, and an identifier of the AIoT device to be activated. Alternatively, for an activator (630) in an RRC connection, the request may be a MAC CE with information required for activation assistance, such as the identifier of the AIoT device to be activated.

[0074] In some embodiments, the activator 630 determines the type of PUSCH resource it needs to use to activate the AIoT device, and based on that determination, selects an appropriate 2-step RACH resource, such as a PRACH timing and a PRACH preamble (810). Different 2-step RACH resources may have different PUSCH resources associated with them. Additionally, the actual PRACH preamble selected may indicate the PUSCH resource to be used.

[0075] In some embodiments, activator 630 performs the transmission (812) of the PRACH preamble in the MsgA-PRACH resource provided in step 804 and selected in step 810. This may include an indication of the required PUSCH resource and an indication to the network node that an activation signal will be sent from activator 630 to AIoT device 620.

[0076] In some embodiments, activator 630 sends an activation signal to AIoT device 620, and a backscatter signal is triggered from AIoT device 620. Activator 630 sends the activation signal in a MsgA-PUSCH resource associated with the MsgA-RACH resource used in step 812 (814). In response, AIoT device can become active and use the received activation signal to perform backscatter transmission (i.e., AIoT device reflects the activation signal while modulating the reflection) (816). In some embodiments, the allocation of MsgA-PUSCH is included in the configuration in step 804.

[0077] In some embodiments, network node 610 confirms whether the AIoT backscatter signal has been correctly received (818). If the backscatter signal is not received, the network node can re-initiate the process, for example, by switching to repeat the process from step 808.

[0078] Figure 9 This is another flowchart 900 of the method according to the example embodiment. Each element of the flowchart may include one or more operations. Operations may be performed in hardware, software, firmware, or a combination thereof. For example, operations may be performed individually or jointly by components, wherein the components may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of the operation. For example, the operation may be performed in a UE (such as...) Figure 1 The UE 100 shown or Figure 6 It is executed at activator 620 shown in a.

[0079] Figure 9 An exemplary embodiment of the signaling flow description for AIoT device activation, which is part of a dedicated PRACH preamble RACH process for a 4-step RACH implementation, is shown.

[0080] Figure 9 Steps 902-912 correspond to Figure 8 Steps 802-812. Instead of a 2-step RACH implementation, the flowchart uses a 4-step RACH implementation, which includes the configuration of dedicated 4-step RACH resources to be used by the AIoT device 620 and an indication of the associated PUSCH profile or type.

[0081] In some embodiments, after the indication has been sent from activator 630 to network node 610 (912), network node 610 provides Msg2 RAR (914) with an indication of PUSCH resources to be used for AIoT activation / backscattering.

[0082] In some embodiments, activator 630 sends an activation signal to AIoT device 620, and a backscatter signal is triggered from AIoT device 620. Activator 630 sends the activation signal in a Msg3-PUSCH resource, which is indicated in step 914 (916). In response, the AIoT device can become active and use the received activation signal to perform backscatter transmission (i.e., the AIoT device reflects the activation signal while modulating the reflection) (918). This process remains consistent with... Figure 8 The flowcharts are the same.

[0083] Figure 10 This is another flowchart 1000 of the method according to an example embodiment. Each element of the flowchart may include one or more operations. Operations may be performed in hardware, software, firmware, or a combination thereof. For example, operations may be performed individually or jointly by components, wherein the components may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of an operation. For example, operations may be performed in a UE (such as...) Figure 1 The UE 100 shown or Figure 6 It is executed at activator 620 shown in a.

[0084] Figure 10 An exemplary embodiment of a signaling flow description of AIoT device activation as part of a competition-based RACH process for a 2-step RACH implementation is shown.

[0085] In some embodiments, network node 610 provides information on contention-based 2-step RACH resources to be used for AIoT use cases, such as PRACH preamble and PRACH timing (1002), via, for example, SIB1. Network node 610 can configure multiple contention-based PRACH resources, where each (or set of) PRACH resources is associated with PUSCH resources of different types or profiles, such as, for example, different numbers of PRBs for PUSCH resources in the time and / or frequency of MsgA-PUSCH resources, to meet the requirements for AIoT communication. For example, for location-type applications, a higher number of PRBs in the frequency is necessary, while a smaller number of PRBs are needed for communication. A higher number of PRBs in the time may be needed to ensure that AIoT has sufficient charge to initiate backscatter transmission. Network node 610 can also configure public 2-step PRACH resources to be used only for AIoT purposes, or public PRACH resources that can be shared with other services / features, but where AIoT indication is provided during or after the contention resolution phase. Figure 10 and 11 In the description, we consider, through examples, the scenario where the AIoT instruction is provided during the contention resolution phase.

[0086] In some embodiments, network node 610 requests activator 630 to provide assistance (840) for activating AIoT device 620. Similarly, as in combination Figure 8 As described in the example of the dedicated preamble, for an activator 620 in an RRC idle / inactive state, the request can be made in the form of a paging message. This paging message may include an identifier of the activator 630, a request for activation assistance, and an identifier of the AIoT device 620 to be activated. Alternatively, for an activator 620 in an RRC connection, the request may be a MAC CE with information required for activation assistance, such as the identifier of the AIoT device to be activated.

[0087] In some embodiments, activator 630 determines the type or profile of the PUSCH resource it needs to use to activate AIoT device 620, and based on this determination, selects a 2-step RACH resource, such as a PRACH timing and a PRACH preamble (1006). Different 2-step RACH resources may have different PUSCH resources associated with them. Additionally, the actual PRACH preamble selected may indicate the PUSCH resource to be used.

[0088] In some embodiments, the activator performs the transmission (1008) of the PRACH preamble in the MsgA-PRACH resource provided in step 1004 and selected in step 1006. This may include an indication of the required PUSCH resource and an indication to the network node that an activation signal will be sent from the activator 630 to the AIoT device 620.

[0089] In some embodiments, activator 630 sends an activation signal to AIoT device 620, and a backscatter signal is triggered from AIoT device 620. Activator 630 sends the activation signal in a MsgA-PUSCH resource associated with the MsgA-RACH resource used in step 1008 (1010). In response, the AIoT device can become active and use the received activation signal to perform backscatter transmission (i.e., the AIoT device reflects the activation signal while modulating the reflection) (1012). In some embodiments, the allocation of MsgA-PRACH is included in the configuration in step 1002.

[0090] In some embodiments, network node 610 confirms whether the AIoT backscatter signal has been correctly received (1014). Network node 610 confirms whether the AIoT backscatter signal has been correctly received in the MsgB payload and provides contention resolution information if necessary. If the backscatter signal has not been received, the network node may re-initiate the process, for example, by switching to repeat the process from step 808.

[0091] Figure 11 This is another flowchart 1100 of the method according to the example embodiment. Each element of the flowchart may include one or more operations. Operations may be performed in hardware, software, firmware, or a combination thereof. For example, operations may be performed individually or jointly by components, wherein the components may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of an operation. For example, operations may be performed in a UE (such as...) Figure 1 The UE 100 shown or Figure 6 It is executed at activator 620 shown in a.

[0092] Figure 11 An exemplary embodiment of the signaling flow description for AIoT device activation as part of a competition-based RACH process for a 4-step RACH implementation is shown.

[0093] Figure 10 Steps 1002-1008 correspond to Figure 1Steps 1102-1108. Instead of a 2-step RACH implementation, the flowchart uses a 4-step RACH implementation, which includes the configuration of contention-based 4-step RACH resources to be used in AIoT use cases and indications of associated PUSCH profiles or types.

[0094] In some embodiments, after the indication has been sent from activator 630 to network node 610 (1108), network node 610 provides Msg2 RAR (1110) with an indication of PUSCH resources to be used for AIoT activation / backscattering.

[0095] In some embodiments, activator 630 sends an activation signal to AIoT device 620, and a backscatter signal is triggered from AIoT device 620. Activator 630 sends the activation signal in a Msg3-PUSCH resource, which is indicated in step 1110 (1112). In response, AIoT device can become active and use the received activation signal to perform backscatter transmission (i.e., AIoT device reflects the activation signal while modulating the reflection) (1114). This process remains consistent with... Figure 10 The flowcharts are the same.

[0096] In both 2-step and 4-step RACH scenarios, the activator 630 determines the PUSCH profile or type (e.g., the required number of PUSCH PRBs and / or the associated required time and frequency organization) through interpretation. This determination then guides the selection of the PRACH preamble and PRACH timing.

[0097] However, in a 2-step RACH, the association between the PRACH preamble and a specific PUSCH resource is known (from RRC reconfiguration for a dedicated preamble or from RRC configuration in SIB1 for a contention-based preamble). In a 4-step RACH, however, initially, only one association exists between the PRACH preamble and the PUSCH resource type or profile (e.g., where the PUSCH resource type corresponds to the desired time and frequency organization). Then, only after receiving the Msg2-RAR is the association between the PRACH preamble and the specific PUSCH resource established (where the PUSCH resource allocation details are provided in conjunction with the selected PRACH preamble).

[0098] Figure 12 A block diagram of an apparatus capable of performing the methods(s) disclosed herein is shown by way of example. Apparatus 1200 is shown, which may include, for example, such as Figure 1The mobile communication device 1200 is a mobile communication device. Included in device 1200 is a processor 1210, which may include, for example, a single-core or multi-core processor, wherein a single-core processor includes one processing core, and a multi-core processor includes more than one processing core. Processor 1210 may typically include a control device. Processor 1210 may include more than one processor. Processor 1210 may be a control device. Processing cores may include, for example, a Cortex-A8 manufactured by ARM Holdings, or a Steamroller processing core designed by Advanced Micro Devices. Processor 1210 may include at least one Qualcomm Snapdragon and / or Intel Atom processor. Processor 1210 may include at least one application-specific integrated circuit (ASIC). Processor 1210 may include at least one field-programmable gate array (FPGA). Processor 1210 may be a component for performing method steps in device 1200. Processor 1210 may be configured at least partially by computer instructions to perform actions.

[0099] A processor may include, or be configured as, one or more circuit systems configured to perform stages of the methods according to the exemplary embodiments described herein. As used herein, the term “circuit system” may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry having software / firmware; and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories that work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0100] This definition of circuit system applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term circuit system also covers only hardware circuitry or a processor (or multiple processors) or portions of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices or other computing or network devices.

[0101] Device 1200 may include memory 1220. Memory 1220 may include random access memory and / or permanent memory. Memory 1220 may include at least one RAM chip. For example, memory 1220 may include solid-state, magnetic, optical, and / or holographic memory. Memory 1220 may be at least partially accessed by processor 1210. Memory 1220 may be at least partially included in processor 1210. Memory 1220 may be a component for storing information. Memory 1220 may include computer instructions configured to be executed by processor 1210. When computer instructions configured to cause processor 1210 to perform certain actions are stored in memory 1220, and device 1200 as a whole is configured to operate under the guidance of processor 1210 using computer instructions from memory 1220, processor 1210 and / or at least one of its processing cores may be considered as being configured to perform said certain actions. Memory 1220 may be at least partially external to device 1200, but may be accessed by device 1200.

[0102] Device 1200 may include a transmitter 1230. Device 1200 may include a receiver 1240. Transmitter 1230 and receiver 1240 may be configured to transmit and receive information according to at least one cellular or non-cellular standard. Transmitter 1230 may include more than one transmitter. Receiver 1240 may include more than one receiver. For example, transmitter 1230 and / or receiver 1240 may be configured to operate according to: Global System for Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), 5G, Long Term Evolution (LTE), IS-95, Wireless Local Area Network (WLAN), Ethernet, and / or Global Microwave Access Interoperability (WiMAX) standards.

[0103] Device 1200 may include a near-field communication (NFC) transceiver 1250. The NFC transceiver 1250 may support at least one NFC technology, such as NFC, Bluetooth, Wibree, or similar technologies.

[0104] Device 1200 may include a user interface (UI) 1260. UI 1260 may include at least one of the following: a display, a keyboard, a touchscreen, a vibrator arranged to signal to the user by causing device 1200 to vibrate, a speaker, and a microphone. The user can operate device 1200 via UI 1260, for example, to accept incoming phone calls, to initiate phone or video calls, to browse the Internet, to manage digital files stored in memory 1220, or accessible in the cloud via transmitter 1230 and receiver 1240, or via NFC transceiver 1250, and / or play games.

[0105] Device 1200 may include or be arranged to accept a subscriber identity module 1270. Subscriber identity module 1270 may include, for example, a subscriber identity module SIM card that can be installed in device 1200. Subscriber identity module 1270 may include subscription information identifying a user of device 1200. Subscriber identity module 1270 may include password information that can be used to verify the identity of a user of device 1200 and / or facilitate encrypted communication, as well as to account for the user of device 1200 for communications influenced by device 1200.

[0106] Processor 1210 may be equipped with a transmitter arranged to output information from processor 1210 to other devices included in device 1200 via electrical wires built into device 1200. Such transmitter may include a serial bus transmitter configured to output information for storage therein to memory 1220, for example, via at least one electrical wire. Alternatively, for a serial bus, the transmitter may include a parallel bus transmitter. Similarly, processor 1210 may include a receiver arranged to receive information within processor 1210 from other devices included in device 1200 via electrical wires built into device 1200. Such receiver may include a serial bus receiver configured to receive information for processing in processor 1210 from receiver 1240, for example, via at least one electrical wire. Alternatively, for a serial bus, the receiver may include a parallel bus receiver.

[0107] Processor 1210, memory 1220, transmitter 1230, receiver 1240, NFC transceiver 1250, UI 1260, and / or user identity module 1270 can be interconnected in various ways by electrical wires built into device 1200. For example, each of the devices mentioned above can be individually connected to the main bus built into device 1200 to allow the devices to exchange information. However, as those skilled in the art will understand, this is merely an example, and various ways of interconnecting at least two of the devices mentioned above can be selected depending on the embodiment.

[0108] Unless otherwise stated or explicitly indicated from the context, different statements about two entities indicate that they perform different functions. This does not necessarily mean that they are based on different hardware. That is, each entity described in this specification may be based on different hardware, or some or all entities may be based on the same hardware. This does not necessarily mean that they are based on different software. That is, each entity described in this specification may be based on different software, or some or all entities may be based on the same software. Each entity described in this specification may be represented in the cloud.

[0109] By way of non-limiting example, any implementation of the above boxes, apparatus, systems, techniques, or methods includes implementations as hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or combinations thereof. Some embodiments may be implemented in the cloud.

[0110] It should be understood that the above description represents what is currently considered a preferred embodiment. However, it should be noted that the description of the preferred embodiments is given by way of example only, and various modifications may be made without departing from the scope defined by the appended claims.

Claims

1. An apparatus comprising: A component used for configuring the reception of physical random access channel (PRACH) resources at the activator; A component for receiving, at the activator, a request from a network node to the activator to provide assistance for activating environmental Internet of Things (AIoT) devices; A component for determining, at the activator, the information required for transmitting an activation signal to activate the physical uplink shared channel (PUSCH) resources needed to activate the AIoT device; A component for selecting, at the activator, a PRACH resource associated with the information of the PUSCH resource from the provided PRACH resource; A component for sending an instruction from the activator to the network node via the selected PRACH resource, the instruction indicating that the activator will provide the activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform backscatter transmission; A component for sending the activation signal from the activator to the AIoT device on the PUSCH resource associated with the selected PRACH resource to trigger backscatter transmission from the AIoT device.

2. The apparatus according to claim 1, further comprising: A component for receiving an acknowledgment command from the network node by the activator to confirm that the backscatter transmission from the AIoT device has been received at the network node.

3. The apparatus according to claim 1 or 2, The configuration is received via RRC reconfiguration or via system information broadcast when the activator transitions to RRC connection state; and The configured PRACH resources include: AIoT-related configuration of at least one PRACH preamble root sequence and cyclic shift, and the random access channel (RACH) timing in which the PRACH preamble can be applied at both time and frequency.

4. The apparatus according to any one of claims 1 to 3, wherein the configuration includes: The information regarding the PUSCH resource and the information regarding the association between the PRACH resource.

5. The apparatus according to any one of claims 1 to 4, further comprising: A component for receiving a Msg2-RAR signal from the network node at the activator, the Msg2-RAR signal including an indication of the PUSCH to be used to send the activation signal.

6. The apparatus according to any of the preceding claims, wherein the request to the activator for assisting in activating the AIoT is based on a dedicated paging message or on RRC signaling.

7. The apparatus according to any of the preceding claims, wherein the apparatus is an AIoT or a user equipment (UE).

8. The apparatus according to any of the preceding claims, wherein the network node is a Radio Access Network (RAN) base station.

9. The apparatus according to any preceding claim, wherein the component comprises: At least one processor; And at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the execution of the device.

10. A method comprising: At the activator, the configuration of the physical random access channel (PRACH) resources is received; The activator receives a request from the network node to provide assistance for activating environmental Internet of Things (AIoT) devices. At the activator, information is determined for transmitting the activation signal to activate the Physical Uplink Shared Channel (PUSCH) resources required for the AIoT device; At the activator, a PRACH resource associated with the information of the PUSCH resource is selected from the provided PRACH resource; The activator sends an instruction to the network node via the selected PRACH resource, the instruction indicating that the activator will provide the activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform backscatter transmission; On the PUSCH resource associated with the selected PRACH resource, the activator sends the activation signal to the AIoT device to trigger backscatter transmission from the AIoT device.

11. An apparatus comprising: At least one processor; and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to: Configuration of Physical Random Access Channel (PRACH) resources; Receive a request from a network node to provide assistance to the device for activating environmental Internet of Things (AIoT) devices; Determine the information required for the transmission of the activation signal to activate the physical uplink shared channel (PUSCH) resources needed to activate the AIoT device; Select a PRACH resource associated with the information of the PUSCH resource from the provided PRACH resource; The device sends an instruction to the network node via the selected PRACH resource, the instruction indicating that the device will provide the activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform backscatter transmission; On the PUSCH resource associated with the selected PRACH resource, the activation signal is sent to the AIoT device to trigger a backscatter transmission from the AIoT device.

12. A computer-readable storage medium comprising instructions stored thereon, the instructions, when executed by at least one processor, causing the at least one processor to perform: At the activator, the configuration of the physical random access channel (PRACH) resources is received; At the activator, a request is received from the network node to provide assistance to the activator for activating environmental Internet of Things (AIoT) devices; At the activator, information is determined for transmitting the activation signal to activate the Physical Uplink Shared Channel (PUSCH) resources required for the AIoT device; At the activator, a PRACH resource associated with the information of the PUSCH resource is selected from the provided PRACH resource; The activator sends an instruction to the network node via the selected PRACH resource, the instruction indicating that the activator will provide the activation signal on the PUSCH resource associated with the selected PRACH resource to activate the AIoT device to perform backscatter transmission; On the PUSCH resource associated with the selected PRACH resource, the activator sends the activation signal to the AIoT device to trigger backscatter transmission from the AIoT device.

Images