Apparatus for backscattering communication

The described solution efficiently configures and manages PRACH and PUSCH resources to activate and manage backscattered transmissions from ambient IoT devices, addressing energy efficiency and cost challenges in ambient IoT communication systems.

GB2630638APending Publication Date: 2024-12-04NOKIA TECHNOLOGIES OY

Patent Information

Application Number
GB2023008233
Authority / Receiving Office
GB · GB
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-06-02
Publication Date
2024-12-04

AI Technical Summary

Technical Problem

Existing communication systems for ambient Internet of Things (IoT) devices face challenges in efficiently activating and managing backscattered transmissions from devices with limited or no energy storage, as current energy harvesting technologies struggle to provide consistent power, leading to shortened device lifetimes and increased costs.

Method used

An apparatus and method that configure and manage physical random-access channels (PRACH) and physical uplink shared channels (PUSCH) resources to enable efficient activation and backscattered transmission from ambient IoT devices, allowing for flexible resource allocation and reduced power consumption, even when the activator is in an RRC Idle/Inactive state.

Benefits of technology

This approach enhances energy efficiency, reduces device coexistence issues, and allows for more reliable and cost-effective activation of backscattered transmissions from ambient IoT devices, supporting the goal of self-sustainable communication networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

There is herein provided a method and apparatus for backscattering communication. Themethod comprises receiving, at an activator, a configuration of a physical random-access channel, PRACH, resource. The method further comprises receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device. The method further comprises determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device and selecting from the provided PRACH resource, at the activator, a PRACH resource associated with the information of the PUSCH resource. The method further comprises sending, from the activator to the network node, via the selected PRACH resource, an indication 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 a backscattered transmission. The method further comprises transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device.
Need to check novelty before this filing date? Find Prior Art

Description

Field Various example embodiments relate to an apparatus for backscattering communication. Further embodiments relate to a method of operating related to such apparatus. Background In the context of at least some conventional communication networks, one important aspect is sustainability, which e.g., includes zero-energy communications. This term refers to terminal devices, e.g., ambient Internet of Things loT devices, which operate without batteries, but which may e.g., have energy harvesting capabilities (e.g., energy stored in a capacitor) or devices without batteries and no capability of storing energy. One candidate technology for ultra-low energy or zero-energy devices are tags for receiving / transmitting radio frequency signals, e.g., backscatter tags, whereby an activator sends a radio frequency signal which activates an loT device. In some systems, a tag modulates an incoming radio frequency signal, e.g., with an information-bearing signal, e.g., by reflection, and the reflected signal may be received by a receiver. This modulated reflected signal is termed as a backscattered transmission, Summary The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention. According to a first aspect, there is described an apparatus comprising means for receiving, at an activator, a configuration of a physical random-access channel, PRACH, resource. The apparatus further comprises means for receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device. The apparatus further comprises means for determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device. The apparatus further comprises means for selecting from the provided PRACH resource, at the activator, a PRACH resource associated with the information of the PUSCH resource. The apparatus further comprises means for sending, from the activator to the network node, via the selected PRACH resource, an indication 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 a backscattered transmission. The apparatus further comprises means for transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device. In some embodiments, the apparatus may further comprise means for receiving, from the network node by the activator, a confirmation command to confirm that the backscattered transmission from the AIoT device has been received at the network node. In some embodiments the configuration may be received by an RRC reconfiguration upon transition of the activator to an RRC Connected state, or by a system information broadcast. In some embodiments the configured PRACH resource may include an AIoT related configuration of at least one PRACH preamble root sequence and cyclic shift and a random access channel, RACH, occasions in time and frequency where the PRACH preamble is applicable. In some embodiments the configuration may comprise information about the association between the information of PUSCH resource and the PRACH resource. In some embodiments, the apparatus may further comprise means for receiving, at the activator from the network node, an Msg2-RAR signal which comprises an indication of the PUSCH that is to be used for transmitting the activation signal. In some embodiments the request for the activator to provide assistance to activate the AIoT is based on a dedicated paging message or on RRC signaling. In some embodiments the apparatus may be an AIoT or user equipment, UE. In some embodiments the network nodes maybe radio access network, RAN, base stations. In some embodiments the means may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least processor, cause the performance of the apparatus. According to a second aspect, there is described a method comprising receiving, at an activator, a configuration of a physical random-access channel, PRACH, resource. The method further comprises receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device. The method further comprises determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device. The method further comprises selecting from the provided PRACH resource, at the activator, a PRACH resource associated with the information of the PUSCH resource. The method further comprises sending, from the activator to the network node, via the selected PRACH resource, an indication 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 a backscattered transmission. The method further comprises transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device. According to a third aspect, there is provided a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out the method of any preceding method definition. According to a fourth aspect, there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing a method, comprising receiving, at an activator, a configuration of a physical random-access channel, PRACH, resource. The method further comprises receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device. The method further comprises determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device. The method further comprises selecting from the provided PRACH resource, at the activator, a PRACH resource associated with the information of the PUSCH resource. The method further comprises sending, from the activator to the network node, via the selected PRACH resource, an indication 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 a backscattered transmission. The method further comprises transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device. Brief Description of the Drawings Example embodiments will now be described by way of non-limiting example, with reference to the accompanying drawings, in which: Fig. 1 shows, by way of example, a network architecture of a communication system; Fig. 2 shows, by way of example, a topology of an ambient loT device according to a first embodiment; Fig. 3 shows, by way of example, a topology of an ambient loT device according to a second embodiment; Fig. 4 shows, by way of example, a topology of an ambient loT device according to a third embodiment and fourth embodiment; Fig. 5 shows, by way of example, a topology of an ambient loT device according to a fifth embodiment; Fig. 6a shows, by way of example, a topology of an ambient loT device according to the invention. Fig, 6b shows, by way of example, a signalling flow description according to the invention; Fig. 7 shows, byway of example, a flowchart of a method; Fig. 8 shows, byway of example, a signalling flow description of AIoT device activation as part of dedicated PRACH preamble RACH procedure for a 2-step RACH implementation; Fig. 9 shows, byway of example, a signalling flow description of AIoT device activation as part of dedicated PRACH preamble RACH procedure for a 4-step RACH implementation; Fig. 10 shows, by way of example, a signalling flow description for an AIoT device activation as part of contention-based RACH procedure for a 2-step RACH implementation; Fig. 11 shows, byway of example, a signalling flow description for an AIoT device activation as part of contention-based RACH procedure for a 4-step RACH implementation; Fig. 12 shows, by way of example, a block diagram of an apparatus. Detailed Description Example embodiments may relate to an apparatus, method and / or computer program for managing TCI state activation. Figure 1 shows, by way of an example, a network architecture of a communication system which is a radio access network (RAN). In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which embodiments may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR), also known as fifth generation (5G), without restricting the embodiments to such an architecture, however. Embodiments may also be applied to other 4 kinds of communications networks having suitable means by adjusting parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system = radio access network, long term evolution (LTE), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof. Figure i shows first and second user devices too, 102 configured to be in a wireless connection on one or more communication channels in a cell with a network node, such as a network node 104 providing a cell. The physical link from a user device, e.g., the first user device too, to the network node 104 is called the uplink (UL) or reverse link and the physical link from the network node to the user device is called the downlink (DL) or forward link. It should be appreciated that network nodes and their functionalities may be implemented by using any node, host, server or access point entity suitable for such a usage. A communications system typically comprises more than one network node in which case the network nodes may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signaling purposes. A network node is a computing device configured to control the radio resources of the communication system it is coupled to. A network node may also be referred to as a TRP, base station (BS), an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment. A network node may include or is coupled to transceivers. From the transceivers of the network node 104, a connection may be provided to an antenna unit that establishes bidirectional radio links to user devices, such as the first and second user devices too, 102. The antenna unit may comprise a plurality of antennas or antenna elements, for example arranged as an antenna array. The network node 104 may further be connected to a core network 110. The user device, or user equipment UE, typically refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant, handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction. 5G enables using multiple input and multiple output technology at both the UE and network node side, many more base stations or nodes than the LTE. 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, namely below 7GHz, cmWave and mmWave, and also being integratable with existing legacy radio access technologies, such as the LTE. Below 7GHz frequency range may be called as FRi, and above 24GHz (or more exactly 24- 52.6 GHz) as FR2, respectively. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. The communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 112, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 114). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing. An edge cloud may be brought into radio access networks (RANs). Using an edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. Applications of cloud RAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU 104) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 108). Beam management is applied during a random access channel (RACH) procedure, when the UE forms the initial connection with the network, and while the UE is in a connected state. In a connected state, transmitting beams and receiving beams may be refined. A user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction. Regarding loT applications, 3GPP has specified NB-IoT / eMTC and NR RedCap before R18 to satisfy the requirements on low cost and low power devices for wide area loT communication. These loT devices usually consume tens or hundreds of milliwatts power during transceiving, while the cost is a few dollars. However, to achieve the internet of everything, loT devices with ten or even a hundred times lower cost and power consumption are needed, especially for a large number of applications requiring battery-less devices. The number of loT connections has been growing rapidly in recent years and is predicted to be hundreds of billions by 2030. With more ‘things’ expected to be interconnected for improving production efficiency and increasing comforts of life, it demands further reduction of size, cost, and power consumption for loT devices. In particular, regular replacement of battery for all the loT devices is impractical due to the tremendous consumption of materials and manpower. It has become a trend to use energy harvested from environments to power loT devices for self-sustainable communications, especially in applications with a vast number of devices (e.g., ID tags and sensors). The most critical issue with existing 3GPP technologies for the target use cases is the capability of cooperating with energy harvesting considering limited device size. Cellular devices usually consume tens or even hundreds of milliwatts power for transceiver processing. Taking NB-IoT module for example, the typical current consumption for receive processing is about 60mA with supply voltage higher than 3.1V, while 70mA for transmitting processing at odBm transmit power. Furthermore, the output power provided by typical energy harvester is mostly below 1 milliwatt, considering the small size of a few square centimeters for practical devices. Since the available power is far less than the consumed power, it is impractical to power cellular devices directly by energy harvesting in most cases. One possible solution is to integrate energy harvesting with rechargeable battery or supercapacitor. However, there are still a few problems to be solved. Firstly, both rechargeable battery and supercapacitor may suffer from shortened lifetime in practical cases. It is hard to provide constant charging current or voltage by energy harvesting, while longtime continuous charging is needed due to the veiy small output power from energy harvester. Inconstant charging current and longtime continuous charging are both harmful to battery life. For supercapacitor, its lifetime will be significantly reduced in high temperature environments (e.g., less than 3 years at 50 degrees centigrade). Secondly, device size will be significantly increased. As small size button battery can only provide current of a few tens of milliamps, battery with much larger size (e.g., AA battery) is usually used to power cellular devices, whose size can be even larger than the module itself. To store energy for a proper duration of working (e.g., one second), the required capacitance of a supercapacitor is at the level of a hundred mill-farads. The size of such supercapacitors may be larger than an NB-IoT module. Thirdly, both rechargeable batteries and supercapacitors can be more expensive than the module itself. Even purchased in large quantities, the cost of a suitable battery or supercapacitor may reach one or a few dollars, which nearly doubles the cost of the device. RFID is the most well-known technology supporting battery less tags (devices). The power consumption of commercial passive RFID tags can be as low as 1 microwatt. The key techniques enabling such low power consumption are envelope detection for downlink data reception, and backscatter communication for uplink data transmission. RFID is designed for short-range communications, whose typical effective range is less than 10 meters. As the air interface of RFID almost remains unchanged since 2005, the too-simple transmission scheme becomes the obstacle of improving its link budget and capability of supporting scalable network. Attracted by the extremely low power consumption of backscatter communication, many non-3GPP technologies begin to put efforts into related research, such as Wi-Fi, Bluetooth, UWB, and LORA. Various research show that a few or tens of microwatts power consumption can be supported for passive tags based on or with small modifications to the above air interfaces. A significant proportion of the studies are targeting at long range communication. Among them, a LoRa tag implemented with commercial off-the-shelf components can send its sensing data to the receiver of 381 meters away. Currently, most of the studies are focusing on independent detailed techniques for various optimization targets. It is hard to see a comprehensive system design fully meeting the requirements of the target use cases. However, the standardization of those technologies is agile and quick, as the industries usually follow some de facto standards. It means that many products in the market will follow even a private standard once it shows competitiveness in some applications. A passive radio is a device that harnesses energy from wireless signals sent on specific carriers and / or bandwidths and charges a simple circuitry that, once activated, it will emit / reflect a signal which encodes at least the ID of the passive radio. The typical system architecture around a passive radio consists of: i. An activator: a device that sends an activation signal targeted at waking up the passive radio. 2. The passive radio: harnesses energy over a range of frequencies and listens for activation signals. Once such a signal is detected, the passive radio emits / reflects a signal which is specific to that radio ID. 3. A reader: a device that listens and detects the passive radio signals. The reader may or may not be collocated with the activator. The following two main types of energy storage are considered: Passive: Pure battery-less devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy Semi-Passive: Devices with limited energy storage capability that do not need to be replaced or recharged manually. Ambient loT devices can be either passive or semi-passive in terms of their energy storage. Several connectivity topologies for Ambient loT networks and devices are disclosed. In all these topologies, the Ambient loT device may be provided with a carrier wave from other node(s) either inside or outside the topology. The links in each topology may be bidirectional or unidirectional. BS, UE, assisting node, or intermediate node could be multiple BSs or UEs, respectively. The mixture of indoor and outdoor placement of such nodes is regarded as a network implementation choice. An Ambient loT system (AIoT) is in its simplest form composed by an AIoT activator, an AIoT reader and an AIoT device. In topologies termed as monostatic, the AIoT activator and reader are the same network element (or device). This implies, that for where the AIoT device reply is a backscattered transmission, that the network element (or device) taking the role of AIoT activator and reader is able to operate in a full duplex fashion being able to transmit an activation signal while simultaneously receiving the reply from the AIoT device. In contrast, for topologies termed as bistatic (or multi-static), the AIoT activator and the AIoT reader are two different network elements (or devices) and therefore there is no longer the need for full duplex operation in the AIoT activation and reader devices. Therefore, bistatic topologies, from a NW and non-AIoT supporting device point of view, are seen as less technically challenging. The activator is herein referred to this is both for ease of exposition as well as due to the activator needing to be in the proximity of the AIoT device and as such is also likely to be a device / UE. According to a first topology, as shown in Figure 2, the Ambient loT device 210 directly and bidirectionally communicates with a base station 220. The communication between the base station 220 and the ambient loT device 210 includes Ambient loT data and / or signaling. This topology includes the possibility that the BS transmitting to the Ambient loT device is a different from the BS receiving from the Ambient loT device. According to a second topology, as shown in Figure 3, the Ambient loT device 310 communicates bidirectionally with an intermediate node 330 between the Ambient loT device 310 and base station 320. In this topology, the intermediate node 330 can be a relay, IAB node, UE, repeater, etc. which is capable of Ambient loT. The intermediate node 330 transfers the information between BS and the Ambient loT device. According to a third topology, as shown in Figures 4a and 4b, the Ambient loT device 410 transmits data / signaling to a base station 420 and receives data / signaling from the assisting node 430 (as shown in Figure 4a for downlink assistance). Alternatively, the Ambient loT device 410 receives data / signaling from a base station 420 and transmits data / signaling to the assisting node 430 (as shown in Figure 4b for uplink assistance). In the third topology, the assisting node 430 can be a relay, IAB, UE, repeater, etc. which is capable of ambient loT. According to a fourth topology, as shown in Figure 5, the Ambient loT device 510 communicates bidirectionally with a UE 540. The communication between UE 540 and the ambient loT device 510 includes Ambient loT data and / or signalling. In this invention we focus on the third topology as depicted in Figure 6a. When taking a look at the stage-i signalling flow, as depicted in Figure 6b, it can be observed that the interaction between the network node 620, activator (i.e., assisting node) 630 and AIoT device 610 is composed by the following steps. Firstly, the network node 620 requests for the assistance device (i.e., the activator) to activate the AIoT device, as depicted by item 1 in Figure 6b. Secondly, the activator 630 sends the activation signal, which is a signal carrier suitable for being backscattered (i.e., for the AIoT to modulate on top its reply signal), as depicted by item 2 in Figure 6b. Subsequently, the AIoT device 610 replies to the network node 620 using a backscattered signal, as depicted by item 3 in Figure 6b. The challenge with this interaction is that for any of these steps to occur there is the need to allocate resources for the activation and reception of the backscattered signal. One approach would be to have the gNB together with its request to allocate resources (i.e., resource allocation is provided in step i of Figure 6b that would allow the activation and backscattered signal to be transmitted). However, as the activator might not be in RRC Connected state it becomes necessary to decouple the request for assistance from the actual resource reservation for the activation / backscattered signal transmission. The subject matter disclosed herein addresses this issue. Figure 7 shows, by way of example, a flowchart of a method according to example embodiments. Each element of the flowchart may comprise one or more operations. The operations maybe performed in hardware, software, firmware or a combination thereof. For example, the operations may be performed, individually or collectively, by a means, wherein the means may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the operations. The method 700 comprises a first operation 701 of receiving, at an activator 630, a configuration of a physical random-access channel, PRACH, resource. The configuration may be received from the network node 620. In the case of dedicated RACH resources, this configuration may be provided during the RRC Reconfiguration step when the UE has transitioned to RRC Connected state and contains. The configuration of a RACH resource may comprise, for 4-step RACH, the PRACH preamble root sequence and cyclic shift as well as the RACH occasions in time and frequency where that PRACH preamble is applicable. Alternatively, the configuration may comprise, for 2-step RACH, in addition to the PRACH preamble and occasions it also includes information of 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 or types that allow to meet the requirements of the AIoT communication. For example, different PUSCH resource profiles or types may define for different requirements of the AIoT communication different organizations of resource elements in time and frequency, or / and different numbers of PRBs. For example, a higher number of physical resource blocks, PRBs, associated with the PUSCH resource in frequency is necessary for positioning kind of applications, while a smaller number of PRBs is needed for communications. While a higher number of PRBs associated with the PUSCH resource in time, might be required to ensure that a AIoT device has enough charge to initiate the backscattering transmission. A Physical Resource Block is the smallest unit of resources that can be allocated to a user. The NR framework uses PRBs as a way to allocate time and frequency resources to users. Each PRB consists of a certain number of contiguous subcarriers for a specific period of time. The exact number of subcarriers and the duration can vary depending on the specific implementation of the NR standard. The use of PRBs allows the network to efficiently allocate resources to users, ensuring that each user gets the necessary bandwidth for their needs. This can be dynamically adjusted based on demand, with more PRBs allocated during periods of high demand. In the case of contention-based RACH resources, this configuration is provided as part of the system information where indication of the RACH resources associated with AIoT is explicitly indicated. Note that the RACH resources in the case of contention-based RACH resources can include all RACH preambles available in a RACH occasion in time and frequency or just a fraction of those available. The method 700 comprises a second operation 702 of receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device. If the network node 620 has no prior information about the activator(s) 630 or the AIoT device 610 relative location, the network node can request multiple activators 630 to activate the same AIoT device. This is beneficial to provide a greater chance of activating the AIoT device 610. In case of dedicated PRACH resources, all these activators 630 will transmit the same PRACH preamble to the network node and therefore perform the transmission of the activation signal in the same PUSCH resources which allows the AIoT device to receive a stronger activation signal since this signal will be the overlapping of multiple activation signals. Alternatively, in case of contention based PRACH resources, each activator 630 selects uniformly, randomly and independently one of the available contention based PRACH resources and therefore will perform the transmission of the activation signal in the corresponding PUSCH resource. In case all activators 630 select the same PRACH resource then they will also transmit the activation signal in the same PUSCH resource. However, it is more likely that each activator will select different PRACH resource and therefore will perform the transmission of the activation signal in separate PUSCH resources. In this case, the network node 620 will receive different instances of the same backscattered signal, which enables diversity in the reception of the backscattered transmission. However, the drawback of this approach is unnecessary power drain on the tag for cases where diversity was not needed. The method used to make the request can be based on a dedicated paging message (for activator devices in RRC Idle / Inactive) or based on RRC signalling for activators in RRC Connected state. Although the request can be made while the activator UE is in RRC Connected, the activator can still transition to RRC Idle / Inactive and still be able to perform the transmission of the activation signal in that state. The method comprises a third operation 703 of determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device 610. The information may be the profile or the type of the PUSCH resource that is required for the transmission of the activation signal. The method comprises a fourth operation 704 of selecting from the provided PRACH resource, at the activator 630, a PRACH resource associated with the information of the PUSCH resource. This operation may comprise selecting an appropriate PRACH preamble and PRACH occasion. The method comprises a fifth operation 705 of sending, from the activator 630 to the network node 620, via the selected PRACH resource, an indication that the activator 630 will provide the activation signal, on the PUSCH resource associated with the selected PRACH resource, to activate the AIoT device 610 to perform a backscattered transmission. In response to this, the network node 620 may become aware that the activator 630 will trigger the AIoT device 610 to perform a backscattered transmission and that this transmission will occur in the PUSCH resources associated with an activated PRACH resource (for example, the selected PRACH preamble and PRACH occasion). The method comprises a sixth operation 706 of transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device. Optionally, the method may comprise a further operation of receiving, from the network node 620 by the activator 630, a confirmation command to confirm that the backscattered transmission from the AIoT device 610 has been received at the network node 620. Several technical effects are associated with the proposed approach. Firstly, the proposed approach provides the activator 630 with the flexibility for when in time it performs the transmission of the activation signal and therefore enables the activator device to avoid in device coexistence issues. Secondly, it establishes a mechanism that allows the activator 630 to notify the network node 610 when it will transmit the activation signal and therefore allow the network to become ready to receive the backscattered signal. Additionally, this approach allows for activator UEs 630 in RRC Idle / Inactive (and activator UEs in RRC Connected without a SR configuration) to be able to access resources to transmit the activation signal without having to transition to RRC Connected and request the NW for dedicated resources. This protocol due to the reduced number of signalling messages provides a more energy efficient approach for activating backscattered transmission from an AIoT device. Figure 8 is a further flowchart 800 of a method according to example embodiments. Each element of the flowchart may comprise one or more operations. The operations may be performed in hardware, software, firmware or a combination thereof. For example, the operations maybe performed, individually or collectively, by a means, wherein the means may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the operations. The operations may, for example, be performed at a UE such as UE too shown in Figure 1 or the activator 620 as shown in Figure 6a. Figure 8 depicts an exemplary embodiment of signalling flow description of AIoT device activation as part of dedicated PRACH preamble RACH procedure for a 2-step RACH implementation. In some embodiments the activator may perform the initial access procedure and transitions to an RRC connected state (802). The network node 610 may initiate the RRC Reconfiguration procedure, which may include indication of the configuration of dedicated 2-step RACH resources to be used for AIoT use cases and the associated PUSCH profiles or types (804). Optionally, the network node 610 can configure multiple dedicated PRACH preambles, where each PRACH preamble is associated with a different PUSCH resource profile or type, such as for example, a different number of PRBs for the PUSCH resources in time and / or frequency of MsgA-PUSCH resources with the goal to meet the requirements for the AIoT communication. For example, a higher number of PRBs in frequency is necessary for positioning kind of applications, while a smaller number of PRBs is needed for communications. While a higher number of PRBs in time, might be required to ensure that a AIoT device has enough charge to initiate the backscattering transmission. In some embodiments the activator confirms the RRC reconfiguration (806). The network node may request the activator device to provide assistance to activate the AIoT Device 620 (808). For an activator 630 in RRC idle / inactive the request may be made in the form of a paging message. This paging message may include the identification of the activator device 630, the request for activation assistance and identification of the AIoT device to be activated. Alternatively, for an activator 630 in RRC Connected, the request may be a MAC CE with the required information for the activation assistance such as the identification of the AIoT device to be activated. In some embodiments the activator 630 determines the type of PUSCH resources that it needs to use to activate the AIoT device and based on that selects the appropriate 2-step RACH resource, e.g., PRACH occasions and PRACH preamble (810). Different 2-step RACH resources can have different PUSCH resources associated with it. Additionally, the actual selected PRACH preamble may indicate the PUSCH resource to be used. In some embodiments, the activator 630 performs the transmission of the PRACH preamble in the MsgA-PRACH resource that was provided in step 804 and selected in step 810 (812). This may comprise an indication of the PUSCH resources needed and indicated to the network node that the activation signal will be sent from the activator 630 to the AIoT device 620. In some embodiments, the activator 630 transmits an activation signal to the AIoT device 620 and backscattering signal is triggered from the AIoT device 620. The activator 630 transmits the activation signal in the MsgA-PUSCH resources that are associated with the MsgA-RACH resource used in step 812 (814). In response, the AIoT device may become active and use the received activation signal to perform a backscatter transmission (i.e., the AIoT device reflects the activation signal while modulating this reflection) (816). In some embodiments, the allocation of the MsgA-PUSCH is included in the configuration of step 804. In some embodiments, the network node 610 confirms if the AIoT backscattered signal was received correctly (818). In case the backscattered signal was not received, the network node can re-initiate the procedure, e.g., transition to repeat the process from step 808. Figure 9 is a further flowchart 900 of a method according to example embodiments. Each element of the flowchart may comprise one or more operations. The operations may be performed in hardware, software, firmware or a combination thereof. For example, the operations maybe performed, individually or collectively, by a means, wherein the means may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the operations. The operations may, for example, be performed at a UE such as UE too shown in Figure 1 or the activator 620 as shown in Figure 6a. Figure 9 depicts an exemplary embodiment of signalling flow description of AIoT device activation as part of dedicated PRACH preamble RACH procedure for a 4-step RACH implementation. The steps 902-912 of Figure 9 correspond to the steps 802-812 of Figure 8. Instead of a 2-step RACH implementation, the flowchart uses 4-step RACH implementation which includes indication of the configuration of dedicated 4-step RACH resources to be used by the AIoT device 620 and the associated PUSCH profiles or types. In some embodiments after the indication has been sent from the activator 630 to the network node 610 (912), the network node 610 provides Msg2 RAR with indication of the PUSCH resources to be used for the AIoT activation / backscatter (914). In some embodiments, the activator 630 transmits an activation signal to the AIoT device 620 and backscattering signal is triggered from the AIoT device 620. The activator 630 transmits the activation signal in the Msg3-PUSCH resources that are indicated in step 914 (916). In response, the AIoT device may become active and use the received activation signal to perform a backscatter transmission (i.e., the AIoT device reflects the activation signal while modulating this reflection) (918). This process remains the same as the flowchart of Figure 8. Figure 10 is a further flowchart 1000 of a method according to example embodiments. Each element of the flowchart may comprise one or more operations. The operations may be performed in hardware, software, firmware or a combination thereof. For example, the operations maybe performed, individually or collectively, by a means, wherein the means may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the operations. The operations may, for example, be performed at a UE such as UE too shown in Figure 1 or the activator 620 as shown in Figure 6a. Figure 10 depicts an exemplary embodiment of signalling flow description of AIoT device activation as part of contention based RACH procedure for a 2-step RACH implementation. In some embodiments, the network node 610 provides information of the contention based 2-step RACH resources, e.g., PRACH preambles and PRACH occasions, which are to be used for AIoT use cases, via e.g., SIB1 (1002). The network node 610 may configure multiple contention based PRACH resources, where each (or a group of) PRACH resource are associated with a different type or profile of PUSCH resources, such as for example, a different number of PRBs for the PUSCH resources in time and / or frequency of MsgA-PUSCH resources with the goal to meet the requirements for the AIoT communication. For example, a higher number of PRBs in frequency is necessary for positioning kind of applications, while a smaller number of PRBs is needed for communications. While a higher number of PRBs in time, might be required to ensure that a AIoT device 620 has enough charge to initiate the backscattering transmission. The network node 610 can also configure common 2-step PRACH resources to be used solely for the purpose of AIoT or the common PRACH resources can be shared with other services / features, but where the indication for AIoT is provided during or after the contention resolution phase. In the procedure herein described in relation to Figures 10 and 11 we consider the case where the AIoT indication is provided during the contention resolution phase, by way of example. In some embodiments, the network node 610 requests the activator 630 to provide assistance to activate the AIoT Device 620 (840). Similarly, as described in relation to the example of dedicated preambles in Figure 8, for activators 620 in RRC idle / inactive the request can be made in the form of a paging message. This paging message can include the identification of the activator 630, the request for activation assistance and identification of the AIoT device 620 to be activated. Alternatively, for activator 620 in RRC Connected, the request can be a MAC CE with the required information for the activation assistance such as the identification of the AIoT device to be activated. In some embodiments, the activator 630 determines the type or profile of PUSCH resources that it needs to use to activate the AIoT device 620 and based on that selects one 2-step RACH resource, e.g., PRACH occasion and PRACH preamble (1006). Different 2-step RACH resources can have different PUSCH resources associated with it. Additionally, the actual selected PRACH preamble can indicate the PUSCH resource to be used. In some embodiments, the activator performs the transmission of the PRACH preamble in the MsgA-PRACH resource that was provided in step 1004 and selected in step 1006 (1008). This may comprise an indication of the PUSCH resources needed and indicated to the network node that the activation signal will be sent from the activator 630 to the AIoT device 620. In some embodiments, the activator 630 transmits an activation signal to the AIoT device 620 and backscattering signal is triggered from the AIoT device 620. The activator 630 transmits the activation signal in the MsgA-PUSCH resources that are associated with the MsgA-RACH resource used in step 1008 (1010). In response, the AIoT device may become active and use the received activation signal to perform a backscatter transmission (i.e., the AIoT device reflects the activation signal while modulating this reflection) (1012). In some embodiments, the allocation of the MsgA-PUSCH is included in the configuration of step 1002. In some embodiments, the network node 610 confirms if the AIoT backscattered signal was received correctly (1014). The network node 610 confirms if the AIoT backscattered signal was received correctly in the payload of the MsgB, as well as contention resolution information is provided if necessary. In case the backscattered signal was not received, the network node can re-initiate the procedure, e.g., transition to repeat the process from step 808. Figure 11 is a further flowchart 1100 of a method according to example embodiments. Each element of the flowchart may comprise one or more operations. The operations may be performed in hardware, software, firmware or a combination thereof. For example, the operations maybe performed, individually or collectively, by a means, wherein the means may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the operations. The operations may, for example, be performed at a UE such as UE too shown in Figure 1 or the activator 620 as shown in Figure 6a. Figure 11 depicts an exemplary embodiment of signalling flow description of AIoT device activation as part of a contention-based preambles RACH procedure for a 4-step RACH implementation. The steps 1002-1008 of Figure 10 correspond to the steps 1102-1108 of Figure 1. Instead of a 2-step RACH implementation, the flowchart uses 4-step RACH implementation which includes indication of the configuration of contention based 4-step RACH resources to be used for the AIoT use cases and the associated PUSCH profiles or types. In some embodiments after the indication has been sent from the activator 630 to the network node 610 (1108), the network node 610 provides Msg2 RAR with indication of the PUSCH resources to be used for the AIoT activation / backscatter (1110). In some embodiments, the activator 630 transmits an activation signal to the AIoT device 620 and backscattering signal is triggered from the AIoT device 620. The activator 630 transmits the activation signal in the Msg3-PUSCH resources that are indicated in step 1110 (1112). In response, the AIoT device may become active and use the received activation signal to perform a backscatter transmission (i.e., the AIoT device reflects the activation signal while modulating this reflection) (1114). This process remains the same as the flowchart of Figure 10. By way of explanation, in both 2-step and 4-step RACH scenario the activator 630 determines the profile or type of the PUSCH (e.g., number of PUSCH PRBs needed and / or the associated required organization in time and frequency). It is this determination that then guides the selection of the PRACH preamble and PRACH occasion. However, in 2-step RACH the association between a PRACH preamble and specific PUSCH resource is already know (either from RRC Reconfiguration for dedicated preambles or from RRC configuration in SIB 1 for contention based preambles). While in 4-step RACH, at the start there is only one association between a PRACH preamble and PUSCH resource type or profile (e.g., where a PUSCH resource type corresponds to the required organization in time and frequency). The association between a PRACH preamble and specific PUSCH resources is then only established after the reception of a Msg2-RAR (where the PUSCH resource allocation details are provided in connection with the selected PRACH preamble). Figure 12 shows, by way of example, a block diagram of an apparatus capable of performing the method(s) as disclosed herein. Illustrated is device 1200, which may comprise, for example, a mobile communication device such as mobile too of Figure 1. Comprised in device 1200 is processor 1210, which may comprise, for example, a single- or multi-core processor wherein a single-core processor comprises one processing core and a multi-core processor comprises more than one processing core. Processor 1210 may comprise, in general, a control device. Processor 1210 may comprise more than one processor. Processor 1210 may be a control device. A processing core may comprise, for example, a Cortex-A8 processing core manufactured by ARM Holdings, or a Steamroller processing core designed by Advanced Micro Devices Corporation. Processor 1210 may comprise at least one Qualcomm Snapdragon and / or Intel Atom processor. Processor 1210 may comprise at least one application-specific integrated circuit, ASIC. Processor 1210 may comprise at least one field-programmable gate array, FPGA. Processor 1210 may be means for performing method steps in device 1200. Processor 1210 may be configured, at least in part by computer instructions, to perform actions. A processor may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with example embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analogue and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analogue and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memoiy(ies) that work together to cause an apparatus, such as a mobile phone or a network node, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitiy applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitiy also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. Device 1200 may comprise memory 1220. Memory 1220 may comprise random-access memory and / or permanent memory. Memory 1220 may comprise at least one RAM chip. Memory 1220 may comprise solid-state, magnetic, optical and / or holographic memory, for example. Memory 1220 maybe at least in part accessible to processor 1210. Memory 1220 may be at least in part comprised in processor 1210. Memory 1220 may be means for storing information. Memory 1220 may comprise computer instructions that processor 1210 is configured to execute. When computer instructions configured to cause processor 1210 to perform certain actions are stored in memory 1220, and device 1200 overall is configured to run under the direction of processor 1210 using computer instructions from memory 1220, processor 1210 and / or its at least one processing core may be considered to be configured to perform said certain actions. Memory 1220 maybe at least in part external to device 1200 but accessible to device 1200. Device 1200 may comprise a transmitter 1230. Device 1200 may comprise a receiver 1240. Transmitter 1230 and receiver 1240 may be configured to transmit and receive, respectively, information in accordance with at least one cellular or non-cellular standard. Transmitter 1230 may comprise more than one transmitter. Receiver 1240 may comprise more than one receiver. Transmitter 1230 and / or receiver 1240 maybe configured to operate in accordance with global system for mobile communication, GSM, wideband code division multiple access, WCDMA, 5G, long term evolution, LTE, IS-95, wireless local area network, WLAN, Ethernet and / or worldwide interoperability for microwave access, WiMAX, standards, for example. Device 1200 may comprise a near-held communication, NFC, transceiver 1250. NFC transceiver 1250 may support at least one NFC technology, such as NFC, Bluetooth, Wibree or similar technologies. Device 1200 may comprise user interface, UI, 1260. UI 1260 may comprise at least one of a display, a keyboard, a touchscreen, a vibrator arranged to signal to a user by causing device 1200 to vibrate, a speaker and a microphone. A user maybe able to operate device 1200 via UI 1260, for example to accept incoming telephone calls, to originate telephone calls or video calls, to browse the Internet, to manage digital Ries stored in memory 1220 or on a cloud accessible via transmitter 1230 and receiver 1240, or via NFC transceiver 1250, and / or to play games. Device 1200 may comprise or be arranged to accept a user identity module 1270. User identity module 1270 may comprise, for example, a subscriber identity module, SIM, card installable in device 1200. A user identity module 1270 may comprise information identifying a subscription of a user of device 1200. A user identity module 1270 may comprise cryptographic information usable to verify the identity of a user of device 1200 and / or to facilitate encryption of communicated information and billing of the user of device 1200 for communication effected via device 1200. Processor 1210 may be furnished with a transmitter arranged to output information from processor 1210, via electrical leads internal to device 1200, to other devices comprised in device 1200. Such a transmitter may comprise a serial bus transmitter arranged to, for example, output information via at least one electrical lead to memory 1220 for storage therein. Alternatively, to a serial bus, the transmitter may comprise a parallel bus transmitter. Likewise, processor 1210 may comprise a receiver arranged to receive information in processor 1210, via electrical leads internal to device 1200, from other devices comprised in device 1200. Such a receiver may comprise a serial bus receiver arranged to, for example, receive information via at least one electrical lead from receiver 1240 for processing in processor 1210. Alternatively, to a serial bus, the receiver may comprise a parallel bus receiver. Processor 1210, memory 1220, transmitter 1230, receiver 1240, NFC transceiver 1250, UI 1260 and / or user identity module 1270 may be interconnected by electrical leads internal to device 1200 in a multitude of different ways. For example, each of the aforementioned devices may be separately connected to a master bus internal to device 1200, to allow for the devices to exchange information. However, as the skilled person will appreciate, this is only one example and depending on the embodiment various ways of interconnecting at least two of the aforementioned devices may be selected. If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software. Each of the entities described in the present description may be embodied in the cloud. Implementations of any of the above-described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Some embodiments maybe implemented in the cloud. It is to be understood that what is described above is what is presently considered the preferred embodiments. However, it should be noted that the description of the preferred embodiments is given byway of example only and that various modifications maybe made without departing from the scope as defined by the appended claims.

Claims

1. An apparatus, comprising:means for receiving, at an activator, a configuration of a physical random-access channel, PRACH, resource;means for receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device;means for determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device;means for selecting from the provided PRACH resource, at the activator, a PRACH resource associated with the information of the PUSCH resource;means for sending, from the activator to the network node, via the selected PRACH resource, an indication 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 a backscattered transmission;means for transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device.

2. The apparatus of claim 1, further comprising means for receiving, from the network node by the activator, a confirmation command to confirm that the backscattered transmission from the AIoT device has been received at the network node.

3. The apparatus of any preceding claim,wherein the configuration is received by an RRC reconfiguration upon transition of the activator to an RRC Connected state, or by a system information broadcast; andwherein the configured PRACH resource includes an AIoT related configuration of at least one PRACH preamble root sequence and cyclic shift and a random access channel, RACH, occasions in time and frequency where the PRACH preamble is applicable.

4. The apparatus of any preceding, wherein the configuration comprises information about the association between the information of PUSCH resource and the PRACH resource.

5. The apparatus of any of claims 1 to 3, further comprisingmeans for receiving, at the activator from the network node, an Msg2-RAR signal which comprises an indication of the PUSCH that is to be used for transmitting theactivation signal.

6. The apparatus of any preceding claim, wherein the request for the activator to provide assistance to activate the AIoT is based on a dedicated paging message or on RRC signaling.

7. The apparatus of any preceding claim, wherein the apparatus is an AIoT or user equipment, UE.

8. The apparatus of any preceding claim, wherein the network nodes are radio access network, RAN, base stations.

9. The apparatus of any preceding claim, wherein the means comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least processor, cause the performance of the apparatus.

10. A method comprising:receiving, at an activator, a configuration of a physical random-access channel, PRACH, resource;receiving, at the activator from a network node, a request for the activator to provide assistance to activate an ambient internet of things, AIoT, device;determining, at the activator, an information of a physical uplink shared channel, PUSCH, resource required for a transmission of an activation signal to activate the AIoT device;selecting from the provided PRACH resource, at the activator, a PRACH resource associated with the information of the PUSCH resource;sending, from the activator to the network node, via the selected PRACH resource, an indication 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 a backscattered transmission;transmitting, from the activator to the AIoT device, on the PUSCH resource associated with the selected PRACH resource, the activation signal to trigger backscattered transmission from the AIoT device.

Citation Information

Patent Citations

  • Gateway for allocating uplink frequency bands and backscattering IoT device and method

    US20220159671A1

Cited By

  • Apparatus for backscattering communication

    WO2024246675A1