Method performed by ambient-internet of things, method performed by intermediate node and method performed by radio access network

Abstract

A method performed by an Ambient-Internet of Things is described that consists of receiving, from an intermediate node, resource allocation information for the IoT device, wherein the resource allocation information is determined by a Radio Access Network, RAN, node and is transmitted from the RAN node to the intermediate node; and transmitting data using one or more resource(s) configured by the resource allocation information.

Description

METHOD PERFORMED BY AMBIENT-INTERNET OF THINGS, METHOD PERFORMED BY INTERMEDIATE NODE AND METHOD PERFORMED BY RADIO ACCESS NETWORK

[0001] The present disclosure relates to a communication system and to parts thereof.

[0002] The disclosure has particular but not exclusive relevance to wireless communication systems and devices thereof operating according to the 3rd Generation Partnership Project (3GPP) standards, equivalents, or derivatives thereof (including Long Term Evolution (LTE)-Advanced, Next Generation or 5G networks, future generations, and beyond). The present disclosure relates, in particular but not exclusively, to resource allocation procedures and power control procedures in an 'Ambient' Internet-of-Things (A-IoT) system, in the context of i) an A-IoT connectivity topology comprising a RAN node and one or more A-IoT devices (also known as A-IoT 'Topology 1' and ii) an A-IoT connectivity topology comprising at least one or more (potentially multiple) intermediate nodes (also known as A-IoT 'Topology 2').

[0003] Earlier developments of the 3GPP standards were referred to as the Long-Term Evolution (LTE) of Evolved Packet Core (EPC) network and Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), also commonly referred as '4G'. More recently, the term '5G' and 'new radio' (NR) is used to refer to an evolving communication technology that supports a variety of applications and services. Various details of 5G networks are described in, for example, the 'NGMN 5G White Paper' V1.0 by the Next Generation Mobile Networks (NGMN) Alliance, which document is available from https: / / www.ngmn.org / 5g-white-paper.html. 3GPP intends to support 5G by way of the so-called 3GPP Next Generation (NextGen) radio access network (RAN) and the 3GPP NextGen core network.

[0004] Under the 3GPP standards, a NodeB (or an eNB in LTE, and gNB in 5G) is the radio access network (RAN) node (or simply 'access node', 'access network node' or 'base station') via which communication devices (user equipments or 'UEs') connect to a core network and communicate with other communication devices or remote servers. For simplicity, the present application may use the term access network node, RAN node (or simply RAN) or base station to refer to any such access nodes.

[0005] For simplicity, the present application will use the term mobile device, user device, UE, or IoT device, to refer to any communication device that is able to connect to the core network via one or more base stations. Although the present application may refer to mobile devices in the description, it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communication network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. An IoT device may, for example, be any UE equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may, for example, be in the form of automated equipment that may operate without requiring human supervision or interaction.

[0006] In the current 5G architecture, the base station structure may be split into two or more parts. In some RAN implementations there are two parts, known as the Central Unit (CU or gNB-CU) - sometimes referred to as a 'control unit' - and the Distributed Unit (DU or gNB-DU), connected by an F1 interface. This enables the use of a 'split' architecture in which the typically 'higher' CU layers (for example, but not necessarily or exclusively, Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) layers) and the, 'lower' DU layers (for example, but not necessarily or exclusively, Radio Link Control (RLC), Media (sometimes referred to as 'Medium') Access Control (MAC), and Physical (PHY) layers) are separated between a particular CU, and one or more Dus that are connected to and controlled by that CU via the F1 interface. Thus, for example, the higher layer CU functionality for a number of base stations may be implemented centrally (for example, by a single processing unit, or in a cloud-based or virtualised system), whilst retaining the lower layer DU functionality locally separately for each base station.

[0007] In 5G, core network entities comprise logical nodes (or 'functions') including control plane functions (CPFs) and one or more user plane functions (UPFs). The CPFs include, amongst other things, one or more Access and Mobility Management Functions (AMFs), a session management function (SMF), and one or more location management functions (LMFs). The AMF generally corresponds to the MME in 4G and performs many of the functions performed by the MME. Each UPF combines functionality of both the S-GW and P-GW - specifically user plane functionality of the Serving Gateway (S-GW (SGW-U)) and user plane functionality of the Packet Data Network Gateway (P-GW (PGW-U)). The SMF provides session management functionality (that formed part of MME functionality in 4G). The SMF also combines the some of the functionality provided by the S-GW and P-GW - specifically control plane functionality of the S-GW (SGW-C) and control plane functionality of the P-GW (PGW-C). The SMF also allocates IP addresses to each UE.

[0008] When a UE wishes to access a cell (and / or a beam in the case of 5G) it may attempt to access that cell and / or beam using a random access (RACH) procedure that historically involved four distinct steps. More recently, a simplified access procedure has been developed by which a UE may attempt to access that cell and / or beam using a two-step RACH procedure. Both the four-step and two-step RACH procedures are well known to those skilled in the art.

[0009] In summary, the four-step procedure typically involves the UE selecting random access resources (including, for example, a preamble) that it uses to initiate the RACH procedure. The UE sends the selected preamble in a first message ('Msg1') to a base station over a physical random access channel (PRACH). In response, the base station responds with a random access response (RAR) (or 'Msg2'). The RAR indicates reception of the preamble and includes, amongst other things, an uplink grant field indicating resources to be used in the uplink for a physical uplink shared channel (PUSCH). The UE 3 then sends a third message ('Msg3') to the network over a physical uplink shared channel (PUSCH) based on the information in the RAR. The specific message sent by the UE in this step, and the content of the message, depends on the context in which the random access procedure is being used. For initial RRC connection setup, for example, Msg3 typically comprises an RRC Setup request or similar message carrying a temporary randomly generated UE identifier. The network responds with a fourth message ('Msg4') which carries the randomly generated UE identifier received in Msg3 for contention purposes to resolve any collisions between different UEs using the same preamble sequence. When successful, Msg4 also transfers the UE to a connected state.

[0010] As those skilled in the art will appreciate, while a contention based random access (CBRA) procedure is described, a non-contention based (or 'contention free') procedure may also be used, e.g., in which a dedicated preamble is assigned by the base station to the UE.

[0011] The two-step procedure is similar in terms of the information transferred but involves one UE to base station message ('MsgA') and one base station to UE message ('MsgB'). MsgA, in effect, combines Msg1 and Msg 3 of the four-step procedure, and MsgB, in effect, combines Msg2 and Msg4 of the four-step procedure.

[0012] It will be appreciated that random access procedures such as those mentioned above may also be used in other contexts including, for example, handover, connection reestablishment, requesting UL scheduling where no dedicated resource for a scheduling-request has been configured for the UE, etc.

[0013] Recently, IoT has attracted much attention in the wireless communication world, and as IoT develops and grows, more 'things' are expected to be interconnected to improve productivity efficiency and increase the comforts of life. In this vein efforts have been made to try to reduce the size, complexity, and power consumption of IoT devices to enable the deployment of tens or even hundreds of billions of IoT devices for various applications. Typically, such IoT devices are powered by batteries that need to be replaced or recharged manually. Thus, as the number of IoT devices deployed grows apace, there is an increasingly negative impact from such devices as the need to replace them leads to increasingly high maintenance costs, serious environmental issues, and even safety hazards for some use cases, for example, for the use of wireless sensors in electrical power, and petroleum industries.

[0014] 'Ambient' IoT (A-IoT) attempts to address some of the above issues and relies on ultra-low complexity devices with ultra-low power.

[0015] A-IoT devices (which may also be referred to simply as IoT devices for simplicity) make use of 'backscatter' or 'reflected' communication to communicate with an A-IoT device reader which may be a cellular RAN node (base station), or other device connected to a cellular communication network. Specifically, A-IoT devices transmit data by reflecting or backscattering radio frequency (RF) signals from the A-IoT device reader without necessarily having to actively generate their own RF signals. Instead A-IoT devices effectively modulate their impedance or reflectivity in response to an incoming RF signal (known as an 'unmodulated carrier' or 'unmodulated carrier signal'), which causes the signal to be reflected to a receiver. The backscattered signals (also referred to as 'reflected' signals) carry information, encoded by the modulation, of the impedance or reflectivity of the A-IoT device.

[0016] Such backscattered signals are typically transmitted on the same frequency as the unmodulated carrier signal from which it originated, but alternatively, the backscattered signals may undergo additional processing such that the backscattered signals have an offset from the frequency of the unmodulated carrier signal.

[0017] It can be seen that A-IoT devices and associated A-IoT device readers have much in common with radio frequency identification (RFID) tags and associated RFID readers. However, A-IoT devices need to be able to operate successfully in a conventional, orthogonal frequency-division multiplexing (OFDM) based, cellular communication system, and to co-exist with more complex conventional UEs (such as smart phones, conventional IoT devices, and the like). Accordingly, compared to conventional RFID devices, A-IoT devices and associated A-IoT device readers are typically subject to additional constraints and need to be able to support additional functionality.

[0018] A-IoT devices may be categorised as follows: - Type 1 devices: A-IoT devices that have means of energy storage but no independent signal generation or downlink (DL) / uplink (UL) amplification capabilities. Such devices rely solely on backscatter communication to communicate in the uplink with other devices. Type 1 devices typically have an initial sampling frequency offset (SFO) up to 10Xppm (where the value of X is still to be agreed but may, for example, be 4 or 5). - Type 2a devices: A-IoT devices that have means of energy storage, and no independent signal generation capabilities, but that do have both DL and UL amplification capabilities. Such devices similarly rely on backscatter communication in the uplink to communicate with other devices. For example, the device can use stored energy to amplify signals backscattered on a carrier wave provided externally. Type 2a devices similarly have a typical initial SFO up to 10Xppm (where the value of X is still to be agreed but may, for example, be 4 or 5). - Type 2b devices: A-IoT devices that have means of energy storage and independent signal generation, i.e., the device has active radio frequency (RF) components that can generate signals for transmission. Hence, UL transmissions may be generated internally by the device, or may be backscattered on a carrier wave provided externally. Type 2b devices also have both DL and UL amplification capabilities. For example, the device can use its stored energy to amplify signals backscattered on the carrier wave provided externally. Type 2b devices similarly have a typical initial SFO up to 10Xppm (where the value of X is still to be agreed but may, for example, be 4 or 5).

[0019] It will be appreciated that type 1, 2a, and 2b, are only examples of possible ambient IoT device categories and that other categories and / or types of ambient IoT devices are possible. For example, the term 'type A' device is also sometimes used to refer to an ambient IoT device that has no means of energy storage and no independent signal generation / amplification capabilities. Such devices also rely on backscatter communication to communicate with other devices.

[0020] Typically, type 1, 2a, and 2b devices each have their own set of power consumption targets, complexity targets, latency targets, data rate targets, and the like.

[0021] For example, the power consumption target for type 1 devices during transmitting / receiving is typically set to less than or equal to 1 microwatts (μW), while for both type 2a and 2b devices the power consumption target during transmitting / receiving is typically set to less than or equal to a few hundred microwatts (μW).

[0022] It will be appreciated that the requirement for the power consumption target to be less than or equal to a 'few hundred μW' mentioned here means that a specific value does not need to be set. It is, therefore, open to discussion to ascertain whether a given design has a corresponding power consumption that satisfies this requirement.

[0023] It is envisaged that a coverage design target for A-IoT devices will have a maximum distance of between 10m and 50m when the devices are indoors. It will be appreciated that the maximum distance for such A-IoT devices may be sub-selected within the range of 10m to 50m.

[0024] Typically, where such ambient IoT devices are implemented in a communication network / system (also referred to as an ambient IoT network) a maximum connection density target may also be set to ensure optimal performance of the network. Typically, such maximum connection density is set at 150 devices per 100 m2for indoor scenarios, and 20 devices per 100 m2for outdoor scenarios.

[0025] Ambient IoT networks may be configured to have any one of several possible connectivity topologies and may be deployed in several different ways. These topologies include: -　　Topology 1 in which an ambient IoT device reader (in this example a base station or RAN node) and ambient IoT device communicate with one another directly (including the possibility that the base station that transmits to the ambient IoT device is different to the base station that receives from the ambient IoT device). This topology may, therefore, need to support full duplex operation at the base station to enable backscatter communication. This can be a significant challenge if an incoming RF signal (known as an 'unmodulated carrier' or 'unmodulated carrier signal') and reflected (or backscattered) signal are within the same RF band. -　　Topology 2 in which a base station (or RAN node) and ambient IoT device communicate with one another via an ambient IoT device reader in the form of an intermediate / assisting node (which may be a relay, an integrated access and backhaul (IAB) node, another UE, a repeater and / or the like, which is capable of ambient IoT operation). The intermediate node transfers ambient IoT data and / or signalling between base station and the ambient IoT device. Like Topology 1, this topology may require support of full duplex operation at the intermediate node and hence faces similar associated challenges. -　　Topology 3 in which the ambient IoT device: receives data / signalling from the base station (or RAN node) directly but transmits data / signalling to the base station indirectly via an assisting node; or transmits data / signalling to the base station (or RAN node) directly but receives data / signalling from the base station indirectly via an assisting node. Accordingly, in this example some IoT device reader functionality is provided by the base station and some IoT device reader functionality is provided by the assisting node. The assisting node may be a relay, an IAB node, another UE, a repeater and / or the like, which is capable of ambient IoT operation. This topology has the benefit that it does not require the base station, or the assisting node, to have full duplex operation. However, the node receiving the reflected signal needs to be able to differentiate between an unmodulated carrier signal and a reflected signal from an ambient IoT device.

[0026] For Topologies 1 and 2, there may be: none of RRC states typical to conventional UEs (e.g., IDLE, CONNECTED, SUSPENDED and / or the like); none of the mobility procedures typical to conventional UEs (e.g., at least no cell selection / re-selection functionality); and / or none of the automatic repeat request (ARQ) and / or hybrid-ARQ (HARQ) typical to conventional UEs.

[0027] Typically in ambient IoT-based systems the user experienced data rate target is between 0.1 kbps and 5 kbps (with 1 kbps being a typical rate), and the design target of the maximum message size is approximately 1000 bits over both the 'device-to-reader' ('D2R') link, and the 'reader-to-device' ('R2D') link, which is in turn based on the maximum possible application layer packet size. Thus assuming a 1 kbps data rate, it takes 1s to transmit 1000 bits over the D2R and R2D links.

[0028] Currently it is envisaged that, for A-IoT, fewer physical channels will be supported, and UL and DL physical layer (layer-1 (L1)) communication will be simplified significantly. For example, there may be a single physical R2D channel (PRDCH) for R2D communication and a single physical D2R channel (PDRCH) for D2R communication. For R2D, the PRDCH will typically carry any higher-layer payload, and any L1 R2D control information (if defined). For D2R, the PDRCH will typically carry any higher-layer payload, and any L1 D2R control information (if defined). The PDRCH may also carry, for example, a response transmitted from the A-IoT device to a reader during a contention-based access procedure. The current view is that R2D transmission will typically comprise an R2D preamble to indicate a start time of the following PRDCH and possibly and chip length information. This R2D preamble is followed immediately by the PRDCH transmission (carrying any R2D traffic data and / or any control information). An R2D postamble is transmitted immediately after the PRDCH transmission to indicate an end of the PRDCH transmission. Similarly, for D2R transmissions, it is envisaged that a D2R preamble will be transmitted at the beginning of each D2R transmission, immediately before the PDRCH transmission, to indicate a start time of the PDRCH transmission. A D2R postamble may also be transmitted following the PDRCH transmission to indicate the end of the PDRCH transmission (and possibly provide a final timing correction to the A-IoT device reader). In the context of D2R communication, however, a D2R midamble may be inserted into (sent during) the PDRCH transmission, for facilitating chip-level timing tracking and channel / interference estimation (e.g., depending on the length of that PDRCH transmission).

[0029] Thus, as the R2D preamble is used to indicate the start of each R2D transmission, the R2D postamble implicitly indicates the TBS of the PDRCH transmission by indicating the end of each R2D transmission. Accordingly, there is no need to restrict the timing of the R2D transmission to align with a conventional OFDM slot (e.g., an NR slot in a 5G system). Moreover, given the potential for a large number of small packets to be transmitted via A-IoT communications, flexible and efficient scheduling can be facilitated by not imposing a constraint that the boundary of the R2D transmission should align with that of the OFDM (e.g. NR) slots. Nevertheless, since the R2D transmission waveform is an OFDM-based waveform, the start of a R2D transmission may be aligned with the boundary of an OFDM (e.g., NR) symbol (including any cyclic prefix) when the R2D transmission co-exists with such transmissions) for in-band and guard-band operations.

[0030] NPL 1: 'NGMN 5G White Paper' V1.0 by the Next Generation Mobile Networks (NGMN), available from https: / / www.ngmn.org / 5g-white-paper.html.

[0031] Generally, for A-IoT communication, it is envisaged that multiple A-IoT logical channels for communication of upper layer data need not be supported. It is yet to be determined whether the concept of A-IoT logical channels is used (e.g., depending on final modelling issues). It is also envisaged that access stratum (AS) layer (above the PHY layer) RLC-like retransmission / repetition will not be supported for A-IoT. Nevertheless, this does not preclude the reader and device resending the payload again as a new transmission from the perspective of the MAC layer. It is yet to be determined how segmentation is to be handled (if needed).

[0032] Due to the simplicity of A-IoT technology, new random access procedures are being developed for allowing communication between an A-IoT device and the A-IoT device reader. These A-IoT access procedures are typically based on a slotted Additive Links On-line Hawaii Area (slotted-ALOHA) based algorithm / protocol that is widely used for communication between radio frequency identification (RFID) tags and their associated RFID reader. Slotted-ALOHA is a variation of the ALOHA protocol, which will be familiar to those skilled in the art. In slotted-ALOHA, a communication channel is effectively divided into small, fixed-length, time slots. Devices are only able to transmit data at particular times (e.g., during specific transmission occasions).

[0033] For random access in the context of RFID technology, as RFID tags are passive devices, the RFID reader needs to initiate any communication access from the RFID tags to the RFID reader. Specifically, communication between the RFID reader and the RFID tags is performed as part of a procedure called an inventory round. Initially, before the inventory process commences, the RFID reader typically transmits a 'Select' command to all RFID tags in the coverage area of the RFID reader, to select a particular group of the RFID tags that are allowed to respond to the RFID reader in the subsequent procedure. The Select command includes information that allows the RFID tags to identify if they are allowed to respond - for example, a device identifier (optionally with a mask) such as an electronic product code (EPC) (or part of it), and / or part of the information in the RFID tag's memory. Any RFID tag that matches the information in the Select command may respond. The RFID reader then sends a 'Query' command to initiate a random access like identification process and sets the parameters to be used for subsequent RFID tag to RFID reader communication.

[0034] Selected RFID tags (i.e., those that match the parameters in the Select command) then randomly determine a 'random access' slot (or 'reply slot') to reply in based on information in the 'Query' command. This reply slot may be the first slot (slot #0) or a subsequent slot. Selected RFID tags that do not respond immediately to the Query command in the first slot (slot #0) move to an Arbitrate state and wait to receive either a QueryAdjust command (to adjust one or more parameters provided in the original Query command and trigger the affected RFID tags to determine a new slot to reply in) or a QueryRep command (to indicate a transition to the next slot and hence the affected RFID tags to modify (decrease) an associated slot counter indicating a number of slots until the determined reply slot).

[0035] When a given selected RFID tag responds in a corresponding reply slot, that RFID tag does so by sending a 16-bit random number (RN16) to the RFID reader (the sending of this RN16 parameter is analogous to the transmission of Msg1 in conventional cellular random access procedures). This 16-bit random number may be used, for example, for the purposes of contention resolution in the event that a plurality of selected RFID tags select the same slot for response, and hence respond to the Query command simultaneously.

[0036] Assuming that a single RFID tag has responded to the RFID reader in a given slot, the RFID reader confirms reception of the with an acknowledgement (ACK command) containing the same RN16 value (the sending of this acknowledgement is analogous to the transmission of the RAR / Msg2 in conventional cellular random access procedures). On receipt of the acknowledgement with the same RN16 value, the RFID tag that responded enters an acknowledged state and responds to the RFID reader with an EPC (a unique identifier of the RFID tag), a cyclic-redundancy check (CRC) and a protocol-control (PC) (the sending of this information is analogous to the transmission of Msg3 in conventional cellular random access procedures).

[0037] The RFID reader then sends a QueryAdjust or QueryRep command, triggering the RFID tag that has just communicated with it to return to a Ready state, and triggering the remaining selected RFID tags in the current identification process to decrease their slot counters. If no RFID tags respond in a given slot RFID reader may send another QueryRep command to trigger the remaining selected RFID tags in the current identification process to decrease their slot counters again.

[0038] For random access in the context of A-IoT devices and A-IoT device readers it is envisaged that when a response is expected from multiple devices (e.g., for the purposes of identifying multiple devices in the vicinity of the A-IoT device reader) a contention-based random access procedure may be used. This contention-based random access procedure may, for example, be similar to a conventional four-step RACH procedure or to a conventional two-step RACH procedure and may also have some similarities with the RFID random access procedure.

[0039] In an A-IoT 'four-step' random access procedure, like the RFID random access procedure, random access is triggered by the A-IoT device reader using an appropriate reader-to-device (R2D) trigger message ('A-IoT Msg0') in a manner that is analogous to the Query command of the RFID random access procedure. The A-IoT device reader includes, in this trigger message, the information (appropriate parameters) that the A-IoT device needs to respond to the random access trigger. It is possible that this trigger message may trigger initial access by a single device, a group of devices, or all devices in a cell / coverage area.

[0040] When triggered by the R2D trigger message (A-IoT Msg0), the A-IoT device may send an initial device-to-reader (D2R) message ('A-IoT Msg1') carrying a corresponding identifier (e.g., a random ID generated by A-IoT device), and possibly other information, to the A-IoT device reader. The A-IoT device reader echoes the identifier received in the initial D2R message (A-IoT Msg1) back to the A-IoT device in an R2D response message ('A-IoT Msg2') that may include additional useful information where appropriate. The A-IoT device may then send a further D2R message ('A-IoT Msg3') including the A-IoT device's device identifier and / or any other higher layer data (depending on a higher layer request). It will be appreciated that the A-IoT device may consider contention resolution to be successful, if the received response message (A-IoT Msg2) includes the same random identifier that was sent by that A-IoT device in the initial D2R message (A-IoT Msg1). Hence the size of the random identifier needs to be sufficient for effective contention resolution purposes. A further R2D transmission ('A-IoT Msg4') may then be sent by the A-IoT device reader to the A-IoT device after the further D2R message (A-IoT Msg3) but does not always need to be sent. The further R2D transmission (A-IoT Msg4) may, for example, be sent to handle a transmission failure (e.g., a failure of A-IoT Msg3 due to any of a number of different reasons). It will be appreciated that the 'A-IoT Msg' terms (e.g., 'A-IoT Msg4') may or may not be used in practice.

[0041] Similarly, in an A-IoT 'two-step' random access procedure, like the RFID random access procedure, random access is triggered by the A-IoT device reader using an appropriate reader-to-device (R2D) trigger message ('A-IoT Msg0') in a manner that is analogous to the Query command of the RFID random access procedure.

[0042] In the two-step scenario, however, when triggered by the R2D trigger message (A-IoT Msg0), the A-IoT device may send an initial device-to-reader (D2R) message ('A-IoT Msg1') carrying a corresponding device identifier (e.g., a random ID generated by A-IoT device or some other identifier), and / or any other higher layer data (depending on a higher layer request), to the A-IoT device reader. This initial D2R message may also include other appropriate information. The A-IoT device reader may echo some or all of the information received in the initial D2R message (A-IoT Msg1) back to the A-IoT device in a R2D response message ('A-IoT Msg2') that may include additional useful information where appropriate.

[0043] Whilst significant work has been done in the development of A-IoT techniques including, for example, towards the development of overall A-IoT two-step and four-step random access procedures, there is still a need for further enhancement, especially in the context of Topology 2. For example, there is still a need to further develop A-IoT procedures that take account of how to appropriately control and / or configure one or more intermediate nodes (e.g., an intermediate UE) to act as an A-IoT device reader.

[0044] In more detail, there is still a need to further develop A-IoT procedures for topology 2 to allow the support of appropriate resource allocations to one or more intermediate nodes (e.g., an intermediate UE) in topology 2 when the intermediate nodes are acting as A-IoT device readers.

[0045] Additionally, appropriate adaptations of A-IoT procedures for topology 2 are needed to take account of different situations and / or connectivity states that one or more intermediate nodes - also referred to as assisting nodes - (e.g., an intermediate UE) in topology 2 may find themselves when they are acting as A-IoT device readers. For example, when one or more intermediate nodes (e.g., an intermediate UE) in topology 2 are acting as A-IoT device readers appropriate mechanisms may be needed to wake up the intermediate nodes if they are in an RRC inactive state or an RRC idle state.

[0046] Additionally, when one or more intermediate nodes (e.g., an intermediate UE) in topology 2 are acting as A-IoT device readers, appropriate mechanisms may be needed to deal with scenarios where an intermediate node does not have an RRC connection temporarily with another device (e.g., an A-IoT device and / or a RAN node, or the like) due to, for example, the occurrence of a handover (HO) event, or a radio link failure (RLF) event.

[0047] Additionally, when one or more intermediate nodes (e.g., an intermediate UE) in topology 2 are acting as A-IoT device readers, appropriate mechanisms may be needed to deal with scenarios where an intermediate node is temporarily outside the coverage area of another device with which it intends to communicate (e.g., an A-IoT device and / or a RAN node, or the like).

[0048] Additionally, when two or more intermediate nodes (e.g., an intermediate UE) in topology 2 are acting as A-IoT device readers, appropriate mechanisms may be needed to deal with scenarios where a different intermediate node is acting as an A-IoT device reader for receiving communication via the D2R link (or 'Rx A-IoT device reader') than is acting as an A-IoT device reader for transmitting communication via the R2D link (or 'Tx A-IoT device reader').

[0049] Additionally, there is also a need to develop appropriate power control procedures / mechanisms for application in A-IoT systems to control power usage of A-IoT devices and, in the case of A-IoT topology 2, to control power control of intermediate nodes (e.g., an intermediate UE) in the topology. For example, power control procedures / mechanisms are needed to control the power usage of A-IoT devices in an A-IoT system with topology 1 and / or topology 2.

[0050] Additionally, power control procedures / mechanisms are needed to control the power usage of intermediate nodes (e.g., an intermediate UE) in topology 2 where the intermediate nodes (e.g., an intermediate UE) either have a single transceiver, or separate transmitters and receivers in different intermediate nodes (e.g., an intermediate UE).

[0051] The disclosure aims to describe one or more apparatus and / or one or more associated mechanisms / procedures that at least partially addresses or contributes to meeting one or more of the above needs and / or addressing one or more of the above issues.

[0052] The disclosure has a method performed by an Ambient-Internet of Things, A-IoT, device, the method comprising receiving, from an intermediate node, resource allocation information for the IoT device, wherein the resource allocation information is determined by a Radio Access Network, RAN, node and is transmitted from the RAN node to the intermediate node; and transmitting data using one or more resource(s) configured by the resource allocation information.

[0053] The disclosure has a method performed by an intermediate node, the method comprising receiving, from a Radio Access Network, RAN, node, resource allocation information for an Ambient-Internet of Things, A-IoT, device, wherein the resource allocation information is determined by the RAN node; and transmitting the resource allocation information to the A-IoT device.

[0054] The disclosure has a method performed by a Radio Access Network, RAN, node, the method comprising determining resource allocation information for an Ambient-Internet of Things, A-IoT, device and transmitting the resource allocation information to an intermediate node, wherein the resource allocation information is transmitted from the intermediate node to the A-IoT device.

[0055] The various functional means described below that are part of the UE may be provided by a memory and one or more processors that execute instructions stored in the memory. Similarly, the various functional means described below that are part of the access network node may be provided by a memory and one or more processors that execute instructions stored in the memory.

[0056] Various example described below may be implemented by means of a computer program product comprising computer implementable instructions for causing a programmable computer to carry out any of the methods described below. The computer implementable instructions may be provided as a signal or on a tangible computer readable medium.

[0057] Examples of apparatus and methods will now be described, by way of example, with reference to the accompanying drawings in which:

[0058] Fig. 1 illustrates schematically a mobile (cellular or wireless) communication system to which example embodiments of the disclosure may be applied;Fig. 2A illustrates schematically a first possible arrangement of a first connectivity topology (topology 1) that may be used in the communication system of Fig. 1;Fig. 2B illustrates schematically another possible arrangement of a first connectivity topology (topology 1) that may be used in the communication system of Fig. 1;Fig. 3A illustrates schematically a first possible arrangement second connectivity topology (topology 2) that may be used in the communication system of Fig. 1;Fig. 3B illustrates schematically another possible arrangement second connectivity topology (topology 2) that may be used in the communication system of Fig. 1;Fig. 4A illustrates schematically a first possible arrangement of a third connectivity topology (topology 3) that may be used in the communication system of Fig. 1;Fig. 4B illustrates schematically another possible arrangement of the third connectivity topology (topology 3) of Fig. 4A;Fig. 5 illustrates a simplified sequence diagram of a network-controlled resource allocation procedure for A-IoT devices that may be implemented in the communication system;Fig. 6 illustrates a simplified sequence diagram of a resource allocation procedure for A-IoT devices when an A-IoT device reader in communication with the A-IoT devices experiences a mobility procedure;Fig. 7 illustrates a simplified sequence diagram of a resource allocation procedure for A-IoT devices when an A-IoT device reader in communication with the A-IoT devices undergoes an RRC state transition;Fig. 8 illustrates a simplified sequence diagram of a power control procedure for A-IoT devices that may be implemented in the communication system of Fig. 1;Fig. 9 illustrates a simplified sequence diagram of another power control procedure for A-IoT devices that may be implemented in the communication system of Fig. 1;Fig. 10 illustrates a simplified sequence diagram of yet another power control procedure for A-IoT devices that may be implemented in the communication system of Fig. 1;Fig. 11 is a simplified block schematic illustrating the main components of a user equipment that may be used in the communication system of Fig. 1;Fig. 12 is a simplified block schematic illustrating the main components of an ambient IoT device that may be used in the communication system of Fig. 1;Fig. 13 is a simplified block schematic illustrating the main components of a RAN node that may be used in the communication system of Fig. 1; andFig. 14 is a simplified block schematic illustrating the main components of an intermediate or assisting node that may be used in the communication system of Fig. 1.

[0059] <Overview> 　　An exemplary telecommunication system will now be described in general terms, by way of example only, with reference to Figs. 1 to 4.

[0060] Fig. 1 schematically illustrates a mobile ('cellular' or 'wireless') communication system (e.g., communication system 1) to which examples of the present disclosure are applicable.

[0061] In the communication system 1 user equipment (UEs) 3 (3-1, 3-2, 3-3) (e.g., mobile telephones and / or other mobile devices including (ambient) IoT devices) can communicate with each other via a corresponding radio access network (RAN) node 5-1 that operates according to one or more compatible radio access technologies (RATs). In the illustrated example, the RAN node 5-1 comprises a base station operating one or more associated cells. Communication via the RAN node 5-1 is typically routed through a core network 7 (e.g., a 5G core network or evolved packet core network (EPC)). As those skilled in the art will appreciate however, a base station 5-1 or 'gNB' 5-1 is an example of a RAN node 5-1 only and that the RAN node 5-1 may be any appropriate RAN node 5-1 (e.g., where appropriate the RAN node 5-1 may be a RAN node that operates using a different RAT than NR / 5G).

[0062] As those skilled in the art will appreciate, whilst three UEs 3, and one RAN node 5-1 are shown in Fig. 1 for illustration purposes, the system, when implemented, will typically include other RAN nodes and UEs 3.

[0063] In the illustrated example, the UEs 3 include at least one 'ambient' IoT device 3-1 (A-IoT device 3-1) that is capable of performing backscatter communication and a number of other, non-ambient IoT, UEs 3-2, 3-3 (such as smartphones or the like) that communicate in a conventional manner.

[0064] The A-IoT device 3-1 may, for example, be a Type 1, Type 2a, or Type 2b device as described in the introduction. As described in more detail later, depending on the connectivity topology employed, the A-IoT device 3-1 may be configured for uplink (backscatter) communication and / or downlink communication directly with the RAN node 5-1 and / or may be configured for uplink (backscatter) communication and / or downlink communication indirectly via communication (e.g., 'sidelink' or similar communication) with intermediate, or assisting, node 5-2. It will be appreciated that the intermediate, or assisting, node 5-2 may, in effect, be another node of the RAN, a separate RAN or other type of communication node, or another UE that communicates with the A-IoT device 3-1 via an appropriate device-to-device interface (e.g., D2D, sidelink, PC5 or the like). The intermediate, or assisting, node 5-2 may, for example, be a relay node (e.g., a dedicated relay or UE-relay), an integrated access and backhaul (IAB) node, a repeater and / or the like, which is capable of ambient IoT operation including receiving backscatter / reflected signals from, and / or transmitting unmodulated carrier signals to, the A-IoT device 3-1.

[0065] The RAN node 5-1 controls one or more associated cells either directly, or indirectly via one or more other nodes (such as home base stations, relays, remote radio heads, distributed units, and / or the like). It will be appreciated that the RAN node 5-1 may be configured to support both 4G, 5G, 6G and / or later generation, and / or any other 3GPP or non-3GPP communication protocols.

[0066] The RAN node 5-1 may be a distributed base station comprising at least one distributed unit (DU) (e.g., a gNB-DU or the like), and a central unit (CU) (e.g., a gNB-CU or the like). In such a distributed base station the CU employs a separated control plane and user plane and so is, itself, split between a control plane function (CU-CP) and a user plane function (CU-UP) which respectively communicate, with the DU via an appropriate interface (e.g. F1-C logical interface) and an appropriate interface (e.g. F1-U logical interface) (together forming an F1 interface (or 'reference point')), and with one another via an appropriate interface (e.g. E1 logical interface). It will be appreciated that while the DU may include the physical and virtual elements required to provide the functionality of the lower parts of the PHY layer and hence communicate with the UEs 3 over the air interface, the base station may alternatively (or additionally) include one or more separate radio units (RUs) (e.g., providing this functionality of the lower parts of the PHY layer). It will, nevertheless, be appreciated that the RAN node 5-1 may be a base station may of a non-distributed form, for example as an integrated gNB or eNB.

[0067] The UEs 3 (and possibly the intermediate or assisting node 5-2 if present) are configured for communication with the RAN node 5-1 via an appropriate air interface (for example a so-called 'Uu' interface and / or the like). It will be appreciated that the A-IoT device 3-1 may, alternatively or additionally, be configured for indirect communication with the RAN node 5-1 via an (air) interface with the intermediate or assisting node 5-2 (if present) and an (air) interface between the intermediate or assisting node 5-2 and the RAN node 5-1. Neighbouring RAN nodes 5-1 may be connected to each other via an appropriate base station to base station interface (such as the so-called 'X2' interface, 'Xn' interface and / or the like - not shown in Fig. 1).

[0068] The core network 7 includes a number of logical nodes (or 'functions') for supporting communication in the communication system 1. In this example, the core network 7 comprises control plane functions (CPFs) 10 and one or more network node entities for the communication of user data (e.g. user plane functions (UPFs)) 11. The CPFs 10 include one or more network node entities for the communication of control signalling (e.g. Access and Mobility Management Functions (AMFs)) 10-1, one or more network node entities for session management (e.g. Session Management Functions (SMFs)) 10-2 and a number of other functions 10-n. Additional functions may include, for example: an Authentication Server Function (AUSF) which facilitates security processes; a Unified Data Management (UDM) entity for managing user specific data (e.g., for access authorisation, user registration, and data network profiles); a Policy Control Function (PCF); an Application Function (AF); a Security Anchor Function (SEAF) which is in a serving network and acts as a "middleman" during an authentication process between a UE and its home network; an Authentication credential Repository and Processing Function (ARPF) which maintains the authentication credentials; and / or the like. It will be appreciated that the nodes or functions may have different names in different systems.

[0069] The RAN node 5-1 is connected to the core network nodes via appropriate interfaces (or 'reference points') such as an N2 reference point between the RAN node 5-1 and the AMF 10-1 for the communication of control signalling, and an N3 reference point between the RAN node 5-1 and each UPF 11 for the communication of user data. At least the non-ambient IoT UEs 3 are each connected to the AMF 10-1 via a non-access stratum (NAS) connection over an appropriate reference point (e.g., N1 reference point (analogous to the S1 reference point in LTE)). It will be appreciated, that N1 communication is routed transparently via the RAN node 5-1.

[0070] One or more UPFs 11 are connected to an external data network 40 (e.g., an IP network such as the internet) via an appropriate reference point (e.g., N6 refence point) for communication of the user data.

[0071] The AMF 10-1 performs mobility management related functions, maintains the NAS connection with at least each non-ambient IoT UE 3-2, 3-3 and manages UE registration. The AMF 10-1 is also responsible for managing paging.

[0072] The SMF 10-2 is connected to the AMF 10-1 via an appropriate reference point (e.g., N11 reference point). The SMF 10-2 provides session management functionality (that formed part of MME functionality in LTE) and additionally combines some control plane functions (provided by the serving gateway and packet data network gateway in LTE). The SMF 10-2 also allocates IP addresses to at least each non-ambient IoT UE 3-2, 3-3. The SMF 10-2 uses user information provided via the AMF 10-1 to determine what session manager would be best assigned to the user. The SMF 10-2 may be considered effectively to be a gateway from the user plane to the control plane of the network. The SMF 10-2 also allocates IP addresses to at least each non-ambient IoT UE 3-2, 3-3.

[0073] Each RAN node 5-1 is also configured for transmission of, and at least the non-ambient IoT UEs 3-2, 3-3 are configured for the reception of, control information and user data via a number of downlink (DL) physical channels and for transmission of a number of physical signals. The DL physical channels correspond to resource elements (REs) carrying information originated from a higher layer, and the DL physical signals are used in the physical layer and correspond to Res which do not carry information originated from a higher layer.

[0074] The physical channels may include, for example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), and a physical downlink control channel (PDCCH). The PDSCH carries data sharing the PDSCH's capacity on a time and frequency basis. The PDSCH can carry a variety of items of data including, for example, user data, UE-specific higher layer control messages mapped down from higher channels, system information blocks (SIBs), and paging. The PDCCH carries downlink control information (DCI) for supporting a number of functions including, for example, scheduling the downlink transmissions on the PDSCH and also the uplink data transmissions on a physical uplink shared channel (PUSCH). The PBCH provides at least the non-ambient IoT UEs 3-2, 3-3 with the Master Information Block (MIB). It also, in conjunction with the PDCCH, supports the synchronisation of time and frequency, which aids cell acquisition, selection and re-selection.

[0075] The DL physical signals may include, for example, reference signals (RSs) and synchronisation signals (SSs). A reference signal (sometimes known as a pilot signal) is a signal with a predefined special waveform known to both the UE 3 and the RAN node 5-1. The reference signals may include, for example, cell specific reference signals, UE-specific reference signal (UE-RS), downlink demodulation signals (DMRS), and channel state information reference signal (CSI-RS).

[0076] Similarly, at least the non-ambient IoT UEs 3-2, 3-3 are configured for transmission of, and the RAN node 5-1 is configured for the reception of, control information and user data via a number of uplink (UL) physical channels corresponding to REs carrying information originated from a higher layer, and UL physical signals which are used in the physical layer and correspond to REs which do not carry information originated from a higher layer. The physical channels may include, for example, the PUSCH, a physical uplink control channel (PUCCH), and / or a physical random access channel (PRACH). The UL physical signals may include, for example, demodulation reference signals (DMRS) for a UL control / data signal, and / or sounding reference signals (SRS) used for UL channel measurement.

[0077] Moreover, at least the non-ambient UEs 3-2, 3-3 and the RAN node 5-1 are mutually configured for performing a random access channel (RACH) procedure for those UEs 3-2, 3-3 to access the network. Specifically, on detection and selection of a cell (and / or a beam in the case of 5G) a UE 3 is able to attempt access to that cell and / or beam using an initial radio resource control (RRC) connection setup procedure comprising a random access procedure with the RAN node 5-1.

[0078] Prior to attempting initial access, at least a non-ambient IoT UE 3-2, 3-3 will choose random access resources (including, for example, a preamble) to use to initiate the RACH procedure. The UE 3 sends the selected preamble (e.g., in 'Msg1') to the RAN node 5-1 over a physical random access channel (PRACH) for initiating the process to obtain synchronisation in the uplink (UL). In response, the RAN node 5-1 responds with a random access response (RAR) (or 'Msg2'). The RAR indicates reception of the preamble and includes: a timing-alignment (TA) command for adjusting the transmission timing of the UE 3 based on the timing of the received preamble; an uplink grant field indicating the resources to be used in the uplink for a physical uplink shared channel (PUSCH); a frequency hopping flag to indicate whether the UE is to transmit on the PUSCH with or without frequency hopping; a modulation and coding scheme (MCS) field from which the UE can determine the MCS for the PUSCH transmission; and a transmit power control (TPC) command value for setting the power of the PUSCH transmission. The UE 3 then sends a third message ('Msg3') to the base station 5A over a physical uplink shared channel (PUSCH) based on the information in the RAR. The specific message sent by the UE 3 in this step, and the content of the message, depends on the context in which the random access procedure is being used. In the example of initial RRC connection setup, however, Msg3 typically comprises an RRC Setup request or similar message carrying a temporary randomly generated UE identifier. The base station 5A responds with a fourth message ('Msg4') which carries the randomly generated UE identifier received in Msg3 for contention purposes to resolve any collisions between different UEs using the same preamble sequence. When successful, Msg4 also transfers the UE to a connected state.

[0079] At least the non-ambient UEs 3-2, 3-3 and the RAN node 5-1 are also mutually configured for performing a two-step RACH procedure that involves the UE 3-2, 3-3 sending one message ('MsgA') to the RAN node 5-1 and the RAN node 5-1 sending one message ('MsgB') to the UE 3-1, 3-3. MsgA, in effect, combines Msg1 and Msg 3 of the four-step procedure, and MsgB, in effect, combines Msg2 and Msg4 of the four-step procedure.

[0080] While contention-based RACH procedures are described it will be appreciated that a UE 3 and the RAN node 5-1 may also perform a non-contention based (or 'contention free') procedure in which a dedicated preamble is assigned by the RAN node 5-1 to the UE 3. Moreover, a UE 3 and the RAN node 5-1 may perform a two-step RACH procedure.

[0081] Each A-IoT device 3-1 may be completely passive or may be active and configured with at least a subset of the functionality of the non-ambient IoT UEs 3-2, 3-3. It will be appreciated that the specific functionality with which the A-IoT device 3-1 is configured is dependent on the type of A-IoT device as described above. It will, nevertheless, be appreciated that regardless of the non-ambient IoT UE functionality that an A-IoT device may be configured with, each A-IoT device 3-1 is respectively configured with A-IoT specific functionality and each RAN node 5-1 is configured with corresponding functionality for communication with A-IoT devices 3-1.

[0082] For example, each RAN node 5-1 is also configured for transmission of, and the A-IoT UEs 3-1 are configured for the reception of, control information and data via a physical R2D channel (PRDCH) for R2D communication that will typically carry any higher-layer payload, and any L1 R2D control information (if defined). Similarly, each RAN node 5-1 is also configured for reception of, and the A-IoT UEs 3-1 are configured for the transmission of, control information and data via a physical D2R channel (PDRCH) for D2R communication that will typically carry any higher-layer payload, and any L1 D2R control information (if defined).

[0083] <Connectivity Topologies> 　　The A-IoT device 3-1 may form part of an ambient IoT network having any one of the possible connectivity topologies referred to in the introduction and may be deployed in any of several different ways. Possible connectivity topologies and their deployment will now be described in more detail with reference to Figs. 2 to 4.

[0084] Fig. 2A illustrates schematically a first possible arrangement of a first connectivity topology (topology 1) that may be used in the communication system 1.

[0085] As shown in Fig. 2A, in the first possible arrangement of topology 1 the functionality of an A-IoT device reader is implemented as part of a RAN node 5-1. An A-IoT device 3-1 and the RAN node 5-1 engage in direct communication with one another (i.e., without the presence of an assisting or intermediate node 5-2). Specifically, as shown, the A-IoT device 3-1 directly and bidirectionally communicates with the RAN node 5-1. The communication between the RAN node 5-1 and the IoT device 3-1 may, for example, include ambient IoT data and / or other ambient IoT signalling (e.g., control signals or the like). The communication between the RAN node 5-1 and the A-IoT device 3-1 may occur over an appropriate air interface such as the NR Uu air interface, a dedicated interface for ambient IoT, or the like.

[0086] In this example, the RAN node 5-1 is responsible for transmission of an unmodulated carrier signal 20-1 to the A-IoT device 3-1; also known as the 'Carrier Wave' signal (CW). That unmodulated carrier signal 20-1 (or CW) may be transmitted by the RAN node 5-1 to the A-IoT device 3-1 to provide the A-IoT device 3-1 with a signal and / or energy upon which modulated and backscattered / reflected information can be sent. For example, upon receiving a reader-to-device (R2D) signal 20-2 from the RAN node 5-1, the A-IoT device 3-1 may modulate the unmodulated carrier signal 20-1 (or CW) it received based on the R2D signal 20-2 it received and backscatter / reflect that modulated signal as a backscattered device-to-reader (D2R) signal 20-3, to the RAN node 5-1.

[0087] Such transmission of an unmodulated carrier, and receipt of backscattering by the same RAN node (base station) may, for example, be supported by topology 1 where full duplex operation is supported at that RAN node.

[0088] Nevertheless, while Fig. 2A shows the unmodulated carrier signal 20-1 (or CW) and the R2D signal 20-2 as originating from the same RAN node; namely RAN node 5-1, it will be appreciated that topology 1 also allows for the possibility that the RAN node 5-1 (in this case the 'IoT device reader') that communicates with the A-IoT device 3-1 may be a different communication node than a communication node that provides the unmodulated carrier signal 20-1 (or CW).

[0089] For example, as shown in Fig. 2B, which illustrates schematically a second possible arrangement of the first connectivity topology (topology 1) that may be used in the communication system 1, a separate communication node 6 may transmit the unmodulated carrier signal 20-1 (or CW) to the A-IoT device 3-1 to provide the A-IoT device 3-1 with a signal and / or energy based upon which modulated and backscattered / reflected information can be sent. The RAN node 5-1 acting as the IoT device reader may then provide the R2D signals 20-2 to the A-IoT device 3-1. Upon receiving an R2D signal 20-2, the A-IoT device 3-1 modulates the unmodulated carrier signal 20-1 (or CW) it received (e.g., based on an R2D signal 20-2 it received) and backscatter / reflect that modulated signal as a backscattered D2R signal 20-3 to the RAN node 5-1.

[0090] Topology 1 may typically be deployed for indoor scenarios, with a type 1, 2a, and / or 2b A-IoT device and the RAN node 5-1 (IoT device reader) being located in an indoor environment. In this scenario the RAN node 5-1 typically supports one or more small cells (e.g., micro-, and pico- cells) used for voice, video, and data transmission, which are designed to provide network coverage to small areas and operate on either licensed frequency division duplex (FDD), licensed time division duplex (TDD), or unlicensed parts of the spectrum.

[0091] Alternatively, topology 1 may be deployed for scenarios where the A-IoT device 3-1 is in an indoor environment but the RAN node 5-1 is located in an outdoor environment. In this case, the RAN node 5-1 may be configured to support one or more small cells (e.g., micro-cells) used for voice, video, and data transmission, which are designed to provide network coverage to small areas and operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum. Alternatively, the RAN node 5-1 may support one or more larger cells (e.g., macro- cells) providing radio coverage to a large area, and that operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum.

[0092] Topology 1 may also be deployed for outdoor scenarios with one or more A-IoT devices 3-1 and the RAN node 5-1 are located in an outdoor environment. In such scenarios the RAN node 5-1 may support one or more small cells (e.g., micro-cells) used for voice, video, and data transmission, which are designed to provide network coverage to small areas and operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum. Alternatively (or additionally), the RAN node 5-1 may support larger cells (e.g., macro- cells) providing radio coverage to a large area, and that operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum.

[0093] This topology may, for example, be appropriate for a situation in which a RAN node 5-1 needs to fetch data (e.g., a meter record, a sensor reading, an error code and / or the like) from the A-IoT device 3-1. The RAN node 5-1 will send an unmodulated carrier signal as a 'stimulus' signal to the A-IoT device 3-1 which will automatically respond with the required data encoded in the resulting backscattered / reflected signal.

[0094] Fig. 3A illustrates schematically a first possible arrangement of a second connectivity topology (topology 2) that may be used in the communication system 1.

[0095] As shown in Fig. 3A, in the first possible arrangement of topology 2 the functionality of an IoT device reader is implemented as part of an intermediate node 5-2. Specifically, an A-IoT device 3-1 and a RAN node 5-1 engage in communication with one another via the intermediate node 5-2 (which may also be referred to as an assisting node / IoT device reader) to transfer ambient IoT data and / or signalling between the RAN node 5-1 and the A-IoT device 3-1. It will be appreciated that while the intermediate node 5-2 is depicted in Fig. 3A as being a type of base station, the intermediate node 5-2 may in fact be any one of an IAB node, a UE, a repeater, or the like, or any other appropriate device, as described above, that can act as an intermediary between a RAN node 5-1 and an A-IoT device 3-1 and that is capable of supporting ambient IoT signalling.

[0096] In this example, the A-IoT device 3-1 communicates bidirectionally with the intermediate node 5-2, which is located between the A-IoT device 3-1 and RAN node 5-1, and which is able to transfer ambient IoT data and / or signalling between the RAN node 5-1 and the A-IoT device 3-1.

[0097] Specifically, the communication between the intermediate node 5-2 and the A-IoT device 3-1 may occur over an appropriate air interface. For example, they may communicate over a Uu, a dedicated interface for A-IoT, or any other appropriate interface (e.g., a sidelink-like interface, ProSe interface, PC5 interface, or the like where the intermediate node 5-2 is a UE).

[0098] In a first (downlink) direction a downlink signal may be transmitted from the RAN node 5-1 to the intermediate node 5-2 as part of communication 20-4 between the RAN node 5-1 and the intermediate node 5-2. The downlink signal, once received by the intermediate node 5-2, may trigger transmission of an unmodulated carrier signal / CW 20-1 to the A-IoT device 3-1 (e.g., on a 'sidelink' or similar interface where the intermediate node 5-2 is a UE). The downlink signal may be (or may carry) the unmodulated carrier signal 20-1 that is to be transmitted (e.g. relayed) by the intermediate node 5-2 to the A-IoT device 3-1 or may be a trigger signal for triggering transmission of the unmodulated carrier signal 20-1 to provide the A-IoT device 3-1 with an unmodulated carrier signal 20-1 (or CW) based upon which modulated and backscattered / reflected information can be sent. For example, upon receiving an R2D signal 20-2 from the intermediate node 5-2, the A-IoT device 3-1 may modulate the unmodulated carrier signal 20-1 (or CW) it received (e.g., based on the R2D signal 20-2) and backscatter / reflect that modulated signal as a backscattered D2R signal 20-3, to the intermediate node 5-2.

[0099] That is to say, in a second (uplink) direction the intermediate node 5-2 is responsible for receiving a modulated backscattered (D2R) signal 20-3 from A-IoT device 3-1 (e.g., on a 'sidelink' or similar interface where the intermediate node 5-2 is a UE). Specifically, the uplink communication may comprise a modulated backscattered signal 20-3 from the A-IoT device 3-1 to the intermediate node 5-2 that is transmitted (e.g., on a 'sidelink' or similar interface where the intermediate node 5-2 is a UE) in using the unmodulated carrier signal 20-1 from the intermediate node 5-2. This modulated backscattered D2R signal 20-3 (or at least the information encoded in it), once received by the intermediate node 5-2, may be relayed / forwarded (transmitted) to the RAN node 5-1 in an uplink signal as part of the communication 20-4 between the intermediate node 5-2 and the RAN node 5-1. The modulated backscattered D2R signal 20-3 may be processed before being relayed by the intermediate node 5-2 to the RAN node 5-1. For example, the modulated D2R backscattered D2R signal 20-3 may be processed by the intermediate node 5-2 to extract information encoded in the modulated D2R backscattered signal, and to encapsulate the extracted information into an appropriate message format (e.g., in accordance with a corresponding application protocol) for communication with the RAN node 5-1. Alternatively, the modulated backscattered D2R signal may itself be processed by the intermediate node 5-2 (without extracting any data encoded in it) to encapsulate it into an appropriate message format (e.g., in accordance with a corresponding application protocol) for communication with the RAN node 5-1.

[0100] Such transmission of an unmodulated carrier, and receipt of backscattering by the same intermediate node 5-2 may, for example, be supported by topology 2 where full duplex operation is supported at that intermediate node 5-2.

[0101] Communication 20-4 between the RAN node 5-1 and the intermediate node 5-2 may occur over any appropriate interface. For example, the RAN node 5-1 and intermediate node 5-2 may communicate over an air interface (such as the Uu interface or the like), for example where the intermediate node 5-2 is a UE (or at least acts like a UE in its communication with the RAN node 5-1). The RAN node 5-1 and intermediate node 5-2 may communicate over a direct base station to base station interface (such as X2 or Xn), for example where the intermediate node 5-2 is a base station (or at least acts like a base station in its communication with the RAN node 5-1). The RAN node 5-1 and intermediate node 5-2 may communicate over an appropriate IAB interface (such as F1*), for example where the RAN node 5-1 acts as an IAB donor base station and the intermediate node 5-2 is an IAB node. Nevertheless, the RAN node 5-1 and the intermediate node 5-2 may communicate over a dedicated interface for the purpose of ambient IoT.

[0102] Nevertheless, while Fig. 3A shows the unmodulated carrier signal 20-1 (or CW) and the R2D signal 20-2 as originating from the same node; namely the intermediate node 5-2, it will be appreciated that topology 2 also allows for the possibility that the intermediate node 5-2 (in this case the 'IoT device reader') transmitting to and receiving from the A-IoT device 3-1 is a different communication node than a communication node that provides the unmodulated carrier signal 20-1 (or CW).

[0103] For example, as shown in Fig. 3B, which illustrates schematically a second possible arrangement of a second connectivity topology (topology 2) that may be used in the communication system 1, a separate communication node 6 may transmit an unmodulated carrier signal 20-1 (or CW) to the A-IoT device 3-1 to provide the A-IoT device 3-1 with a signal and / or energy based upon which modulated and backscattered / reflected information can be sent. Upon receiving an R2D signal 20-2 from the intermediate node 5-2 (which may be triggered in response to the intermediate node 5-2 receiving a DL transmission 20-4 from the RAN node 5-1) the A-IoT device 3-1 may modulate the unmodulated carrier signal 20-1 (or CW) that it received (e.g., based on the R2D signal 20-2 it received) and backscatter / reflect that modulated signal as a backscattered D2R signal 20-3, to the intermediate node 5-2.

[0104] Similarly to in Fig. 3A, the intermediate node 5-2 may then send / relay the modulated backscattered D2R signal 20-3 it receives from the A-IoT device 3-1 (or at least the information encoded in it), to the RAN node 5-1 in an uplink signal as part of the communication 20-4 between the intermediate node 5-2 and the RAN node 5-1. The modulated backscattered D2R signal 20-3 may be processed before being relayed by the intermediate node 5-2 to the RAN node 5-1. For example, the modulated backscattered D2R signal 20-3 may be processed by the intermediate node 5-2 to extract information encoded in the modulated backscattered D2R signal, and to encapsulate the extracted information into an appropriate message format (e.g., in accordance with a corresponding application protocol) for communication with the RAN node 5-1. Alternatively, the modulated backscattered D2R signal may itself be processed by the intermediate node 5-2 (without extracting any data encoded in it) to encapsulate it into an appropriate message format (e.g., in accordance with a corresponding application protocol) for communication with the RAN node 5-1.

[0105] It will be appreciated that in the arrangement of Fig. 3A and Fig. 3B, the intermediate node 5-2 may be of a type that attempts to demodulate the received backscattered signal for subsequent forwarding of the data to the RAN node 5-1 (e.g., a layer-2 (L2) relay device that attempts to demodulate any layer-1 (L1) signals that it receives). Such an intermediate node 5-2 may be referred to as be a layer 2 ('L2') type intermediate node 5-2. Nevertheless, the intermediate node 5-2 may be of a type that blindly forwards a received signal without attempting to demodulate it and hence, on receipt of the backscattered signal no attempt is made to demodulate it (e.g., an L1 repeater device or a network-controlled repeater (NCR) node). Such an intermediate node 5-2 may be referred to as be a layer 1 ('L1') type intermediate node 5-2.

[0106] Topology 2 may be deployed for scenarios with a type 1, 2a, and / or 2b A-IoT device 3-1, in which the A-IoT device 3-1 is in an indoor environment but the RAN node 5-1 is located in an outdoor environment. In this scenario the RAN node 5-1 may support one or more small cells (e.g., micro-cells) used for voice, video, and data transmission, which are designed to provide network coverage to small areas and operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum. Alternatively, the RAN node 5-1 may support one or more larger cells (e.g., macro- cells) providing radio coverage to a large area, and that operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum. In this scenario, the assisting node 5-2 may be located in an indoor or an outdoor environment.

[0107] Topology 2 may also be deployed for indoor scenarios with a type 1, 2a, and / or 2b A-IoT device 3-1, intermediate device 5-2, and RAN node 5-1 are located in an indoor environment. In this scenario the RAN node 5-1 typically supports one or more small cells (e.g., micro-, and pico- cells) used for voice, video, and data transmission, which are designed to provide network coverage to small areas and operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum.

[0108] Topology 2 may also be deployed for outdoor scenarios with a type 1, 2a or 2b IoT device A-3-1, RAN node 5-1 and intermediate (or assisting) node 5-2 being located in an outdoor environment. In this scenario the RAN node 5-1 may support one or more small cells (e.g., micro-cells) used for voice, video, and data transmission, which are designed to provide network coverage to small areas and operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum. Alternatively, the RAN node 5-1 may support one or more larger cells (e.g., macro- cells) providing radio coverage to a large area, and that operate on either licensed FDD, licensed TDD, or unlicensed parts of the spectrum.

[0109] This topology may, for example, be appropriate for a situation in which a RAN node 5-1 needs to fetch data (e.g., a meter record, a sensor reading, an error code and / or the like) from the IoT device 3-1. The RAN node 5-1 will trigger the intermediate node 5-2 to send an unmodulated carrier signal as a 'stimulus' signal to the A-IoT device 3-1 which will automatically respond with the required data encoded in the resulting backscattered / reflected signal. The resulting backscattered / reflected signal (or at least the data encoded in it) will then be forwarded / relayed to the RAN node 5-1.

[0110] Figs. 4A and 4B illustrate schematically a third connectivity topology (topology 3) of a mobile (cellular or wireless) communication system.

[0111] As shown in Figs. 4A and 4B, in topology 3 part of the functionality of an A-IoT device reader is implemented as part of an assisting node 5-2 and part of the functionality of the A-IoT device reader is implemented as part of a RAN node 5-1. Specifically, an A-IoT device 3-1 and the RAN node 5-1 engage in communication with one another via the assisting node 5-2 (which may also be referred to as an intermediate node). It will be appreciated that while the assisting node 5-2 is depicted in Fig. 4A and Fig. 4B as a type of base station, the assisting node 5-2 may in fact be any one of an IAB node, a UE, a repeater, or the like, or any other appropriate device that can act as an intermediary between a RAN node 5-1 and an A-IoT device 3-1.

[0112] It will be appreciated that the assisting node 5-2 may be of a type that attempts to demodulate the received backscattered signal for subsequent forwarding of the data to the RAN node 5-1 (e.g., a layer-2 (L2) relay device that attempts to demodulate any layer-1 (L1) signals that it receives). Such an assisting node may be referred to as be a layer 2 ('L2') type assisting node 5-2. Nevertheless, the assisting node 5-2 may be of a type that blindly forwards a received signal without attempting to demodulate it (e.g., an L1 repeater device or a network-controlled repeater (NCR) node) and hence, on receipt of the backscattered signal no attempt is made to demodulate it. Such an assisting node may be referred to as be a layer 1 ('L1') type assisting node 5-2.

[0113] As shown in Fig. 4A, the A-IoT device 3-1 may communicate with a RAN node 5-1 in a downlink direction and an assisting (intermediate) node 5-2 in an uplink direction (e.g., on a 'sidelink' or similar). The communication between the RAN node 5-1 and the A-IoT device 3-1, or the communication between the assisting node 5-2 and the A-IoT device 3-1 respectively may occur over an appropriate air interface. For example, they may communicate over a Uu or dedicated 'sidelink' interface.

[0114] In this example the RAN node 5-1 (base station / cell) is responsible for transmission of an unmodulated carrier signal 20-1 (or CW) to the A-IoT device 3-1 to provide the A-IoT device 3-1 with a signal and / or energy based upon which modulated and backscattered / reflected information can be sent. Upon receiving an R2D signal 20-2 from the RAN node 5-1, the unmodulated carrier signal 20-1 may be modulated (e.g., based on the received R2D signal 20-2) and backscattered, as a modulated backscattered D2R signal 20-3, from the A-IoT device 3-1 and received at the assisting node 5-2. That is, the assisting node 5-2 is responsible for receiving the backscattered D2R signal 20-3 from the A-IoT device 3-1. The modulated backscattered D2R signal 20-3 (or at least the information encoded in it), once received by the assisting node 5-2, may be relayed (forwarded / transmitted) to the RAN node 5-1 in another signal 20-3'. The modulated backscattered D2R signal 20-3 may be processed before being relayed / forwarded by the assisting node 5-2 to the RAN node 5-1. For example, the modulated backscattered 20-3 signal may be processed by the assisting node 5-2 to extract information encoded in the modulated backscattered signal, and to encapsulate the extracted information into an appropriate message format (e.g., in accordance with a corresponding application protocol) for communication with the RAN node 5-1 over an appropriate signal 20-3'. Alternatively, the modulated backscattered D2R signal 20-3 may itself be processed by the assisting node 5-2 (without extracting any data encoded in it) to encapsulate it into an appropriate message format (e.g., in accordance with a corresponding application protocol) for communication with the RAN node 5-1 over an appropriate signal 20-3'.

[0115] The communication 20-3' between the RAN node 5-1 and the assisting node 5-2 occurs over an appropriate interface. For example, the RAN node 5-1 and the assisting node 5-2 may communicate over an air interface (such as the Uu interface or the like), for example where the assisting node 5-2 is a UE (or at least acts like a UE in its communication with the RAN node 5-1). The RAN node 5-1 and assisting node 5-2 may communicate over an appropriate IAB interface (such as F1*), for example where the RAN node 5-1 acts as an IAB donor base station and the assisting node 5-2 is an IAB node. Nevertheless, the RAN node 5-1 and the assisting node 5-2 may communicate over a dedicated interface for the purpose of ambient IoT. The communication, comprising the modulated backscattered signal 20-2 received at the assisting node 5-2 from the A-IoT device 3-1, also occurs over an appropriate air interface. For example, they may communicate over a Uu or a dedicated interface.

[0116] This topology may, for example, be appropriate for a situation in which a RAN node 5-1 needs to fetch data (e.g., a meter record, a sensor reading, an error code and / or the like) from the A-IoT device 3-1. The RAN node 5-1 will send an unmodulated carrier signal as a 'stimulus' signal to the A-IoT device 3-1 which will automatically respond with the required data encoded in the resulting backscattered / reflected signal sent to the assisting node 5-2 for relaying / forwarding to the RAN node 5-1.

[0117] Alternatively, as shown in Fig. 4B, the A-IoT device 3-1 may communicate with a RAN node 5-1 in an uplink direction and an assisting (intermediate) node 5-2 in a downlink direction (e.g., on a 'sidelink' or similar). The communication between the RAN node 5-1 and A-IoT device 3-1, and the communication between the assisting node 5-2 and the A-IoT device 3-1, respectively occur over an appropriate air interface. For example, they may communicate over a Uu or dedicated 'sidelink' interface.

[0118] In this example the assisting node 5-2 is responsible for transmission of an unmodulated carrier signal 20-1 to the A-IoT device 3-1 to provide the A-IoT device 3-1 with a signal and / or energy based upon which modulated and backscattered / reflected information can be sent. Upon receiving an R2D signal 20-2 from the assisting node 5-2, the unmodulated carrier signal 20-1 may be modulated (e.g., based on the received R2D signal 20-2) and backscattered, as a modulated backscattered D2R signal 20-3, from the A-IoT device 3-1 and received at the RAN node 5-1. That is, the RAN node 5-1 (base station / cell) is responsible for receiving the backscattered D2R signal 20-3 from the A-IoT device 3-1. The transmission of the unmodulated carrier signal 20-1 may be triggered by a downlink signal 20-2' received by the assisting node 5-2 from the RAN node 5-1. For example, the downlink signal 20-2' may be (or may carry) the unmodulated carrier signal 20-1 that is to be transmitted (e.g. relayed) by the assisting node 5-2 to the A-IoT device 3-1 or may be a trigger signal for triggering transmission of the unmodulated carrier signal 20-1.

[0119] This topology may, for example, be appropriate for a situation in which a RAN node 5-1 needs to fetch data (e.g., a meter record, a sensor reading, an error code and / or the like) from the A-IoT device 3-1. The RAN node 5-1 will send an unmodulated carrier signal as a 'stimulus' signal to the IoT device 3-1 which will automatically respond with the required data encoded in the resulting backscattered / reflected signal sent to the assisting node 5-2. The resulting backscattered / reflected signal (or at least the data encoded in it) will then be forwarded / relayed to the RAN node 5-1 by the assisting node 5-2.

[0120] Similarly to Fig. 4A, in Fig. 4B the communication 20-2' between the RAN node 5-1 and the assisting node 5-2 occurs over an appropriate interface. For example, the RAN node 5-1 and the assisting node 5-2 may communicate over an air interface (such as the Uu interface or the like), for example where the assisting node 5-2 is a UE (or at least acts like a UE in its communication with the RAN node 5-1). The RAN node 5-1 and assisting node 5-2 may communicate over an appropriate IAB interface (such as F1*), for example where the RAN node 5-1 acts as an IAB donor base station and the assisting node 5-2 is an IAB node. Nevertheless, the RAN node 5-1 and the assisting node 5-2 may communicate over a dedicated interface for the purpose of ambient IoT. The downlink communication, comprising the unmodulated carrier signal 20-1 sent from the assisting node 5-2 to the A-IoT device 3-1, also occurs over an appropriate air interface. For example, they may communicate over a Uu or a dedicated interface.

[0121] This topology may, for example, be appropriate for a situation in which a RAN node 5-1 needs to fetch data (e.g., a meter record, a sensor reading, an error code and / or the like) from the A-IoT device 3-1. The RAN node 5-1 will trigger the assisting node 5-2 to send an unmodulated carrier signal as a 'stimulus' signal to the A-IoT device 3-1 which will automatically respond with the required data encoded in the resulting backscattered / reflected signal sent to the RAN node 5-1.

[0122] In either scenario (illustrated in Fig. 4A or 4B), backscattering may be supported even if the RAN node 5-1 and / or the assisting node 5-2 do not support full duplex operation.

[0123] <Configuring Resources for A-IoT Devices for A-IoT Topology 2> 　　Beneficially, the RAN node 5-1, intermediate node 5-2 (e.g., intermediate UE) acting as an A-IoT device reader, and the A-IoT devices 3-1 of the communication system 1 are mutually configured for implementing one or more mechanisms / techniques for supporting configuration of resources for an intermediate node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader, and A-IoT devices 3-1.

[0124] A number of these possible mechanisms / techniques that may be implemented in the communication system 1 will now be briefly introduced, by way of example only, before a more detailed description of the various mechanisms / techniques is provided.

[0125] For example, as described in more detail later, the communication system 1 may be configured to support one or more procedures that allow for efficient configuration / allocation of resources to A-IoT devices 3-1 via an intermediate node, or intermediate UE, that acts as an A-IoT device reader. The one or more procedures may, for example, comprise one or more procedures that allow for the intermediate node, or intermediate UE, that acts as an A-IoT device reader to determine the validity of a configuration / allocation of resources for the A-IoT devices 3-1 by a RAN node prior to the assignment / indication of those resources to the A-IoT devices 3-1.

[0126] Beneficially, as described in more detail later, the communication system 1 may be configured to additionally (or alternatively) support one or more procedures that allow for efficient configuration / allocation of resources to A-IoT devices 3-1 via an intermediate node, or intermediate UE, that acts as an A-IoT device reader during the performance of a mobility procedure in the communication system 1. The one or more procedures may, for example, comprise one or more procedures that allow for the configuration / allocation of resources to A-IoT devices 3-1 via an intermediate node, or intermediate UE, that acts as an A-IoT device reader following a handover procedure involving the A-IoT device reader. For example, in certain scenarios, the A-IoT device reader may be handed over from a source RAN node to a target RAN node, in this case, appropriate resource configuration / allocation procedures are necessary to allocate resources to A-IoT devices 3-1 that account for the handover of the A-IoT device reader from the source to the target RAN node.

[0127] Beneficially, as described in more detail later, the communication system 1 may be configured to additionally (or alternatively) support one or more procedures that allow for efficient configuration / allocation of resources to A-IoT devices 3-1 via an intermediate node, or intermediate UE, that acts as an A-IoT device reader during the performance of a state transition procedure in the communication system 1. The one or more procedures may, for example, comprise one or more procedures that allow for the configuration / allocation of resources to A-IoT devices 3-1 via an intermediate node, or intermediate UE, that acts as an A-IoT device reader following the transition of the A-IoT device reader between an RRC CONNECTED state and an RRC IDLE / INACTIVE state.

[0128] Several A-IoT resource allocation procedures between a RAN node, one or more A-IoT device readers, and one or more A-IoT devices in topology 2 are be described in further detail with respect to Figs. 5 to 7.

[0129] <Power Control Enhancements for A-IoT> 　　Beneficially, the RAN node 5-1, intermediate node 5-2 (e.g., intermediate UE) acting as an A-IoT device reader where applicable, and the A-IoT devices 3-1 of the communication system 1 are mutually configured for implementing one or more mechanisms / techniques for power control of the intermediate node 5-2 (e.g., intermediate UE) acting as an A-IoT device reader where applicable and / or the A-IoT devices 3-1 of the communication system 1.

[0130] A number of these possible mechanisms / techniques that may be implemented in the communication system 1 will now be briefly introduced, by way of example only, before a more detailed description of the various mechanisms / techniques is provided.

[0131] Several A-IoT power control procedures between a RAN node, one or more A-IoT device readers (where applicable) and one or more A-IoT devices are be described in further detail with respect to Figs. 8 to 10.

[0132] Beneficially, as described in more detail later, the communication system 1 may be configured to additionally (or alternatively) support one or more procedures that allow for the configuration and control of power usage by A-IoT devices 3-1 of the communication system 1. The one or more procedures may, for example, comprise one or more procedures that allow for the control of power usage by A-IoT devices 3-1 by controlling the A-IoT transmissions performed by the A-IoT devices 3-1. Additionally (or alternatively), the one or more procedures may, for example, comprise one or more procedures that allow for the of power usage by A-IoT devices 3-1 by configuring / controlling maximum and minimum transmission powers, or the like.

[0133] Beneficially, as described in more detail later, the communication system 1 may be configured to additionally (or alternatively) support one or more procedures that allow for the configuration and control of power usage by A-IoT devices 3-1 of the communication system 1 via an intermediate node 5-2 (e.g., intermediate UE) acting as an A-IoT device reader. The one or more procedures may, for example, comprise one or more procedures that allow for the control of power usage by A-IoT devices 3-1 by controlling, through appropriate signalling by the A-IoT device reader, the A-IoT transmissions performed by the A-IoT devices 3-1. Additionally (or alternatively), the one or more procedures may, for example, comprise one or more procedures that allow for the of power usage by A-IoT devices 3-1 by configuring / controlling through appropriate signalling by the A-IoT device reader, maximum and minimum transmission powers, or the like.

[0134] Beneficially, as described in more detail later, the communication system 1 may be configured to additionally (or alternatively) support one or more procedures that allow for the configuration and control of power usage by A-IoT devices 3-1 of the communication system 1 via an intermediate node, or intermediate UE, that acts as an A-IoT device reader in cases where two intermediate nodes (or intermediate UEs) provide A-IoT device reader functions for a given A-IoT device 3-1. For example, a scenario in which one intermediate node acts as a transmitter A-IoT reader device that transmits R2D signals to the A-IoT device 3-1, and one intermediate node acts as a receiver A-IoT reader device that receives D2R signals from the A-IoT device 3-1.

[0135] It will be appreciated that the communication system 1 need not support all the possible mechanisms / techniques detailed with respect to Figs. 5 to 10 to achieve a technical benefit. For example, the communication system 1 may only support a single one of the mechanisms / techniques described. Nevertheless, the various mechanisms / techniques described are not mutually exclusive and so the communication system 1 may support all, or a subset of the various mechanisms / techniques described to provide a commensurate benefit. For example, some of the mechanisms / techniques may supported as different options that may be used by the A-IoT device reader and the A-IoT device 3-1 at different times in the communication system 1 depending on the prevailing conditions.

[0136] <Resource Configuration for A-IoT> <Network-controlled Resource Allocation for A-IoT> 　　Fig. 5 illustrates a simplified sequence diagram of a network-controlled resource allocation procedure for A-IoT that may be implemented in the communication system 1.

[0137] As shown in Fig. 5, there is provided a RAN node 5-1 (e.g., a base station, or the like) in communication with an intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE, or the like). Additionally, as shown in Fig. 5, the intermediate / assisting node 5-2 that operates as an A-IoT device reader is in communication with one or more A-IoT devices 3-1. Whilst the following description refers to the A-IoT device reader specifically as an intermediate UE this does not preclude the A-IoT device reader being any other appropriate intermediate device capable to acting as an A-IoT device reader.

[0138] To enable one or more A-IoT devices 3-1 to communicate with the RAN node 5-1 (e.g., send data transmission requested by the RAN node 5-1), the RAN node 5-1 may employ a resource allocation procedure such as that shown in Fig. 5.

[0139] It will be appreciated that in the procedure of Fig. 5, the intermediate / assisting node 5-2 will typically form an appropriate connection with the RAN node 5 prior to being able to communicate with the RAN node 5-1 and act as an A-IoT device reader for the A-IoT device 3-1. For example, where the intermediate / assisting node 5-2 is an intermediate UE, that intermediate UE will typically enter an RRC connected state (like a typical UE) prior to being able to act as an A-IoT device reader for the A-IoT device 3-1.

[0140] At step S502, the RAN node 5-1 allocates a resource (or resources) for A-IoT communication between the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as an A-IoT device reader and which is in communication with the RAN node 5-1, and the one or more A-IoT devices 3-1.

[0141] For example, the RAN node 5-1 may generate / prepare a resource configuration, or the like. That resource configuration may, for example, be a dedicated resource configuration that configures / allocates both D2R resources for D2R link communications between the intermediate / assisting node 5-2 (e.g., intermediate UE) and the A-IoT devices 3-1, and R2D resources for R2D link communications between the intermediate / assisting node 5-2 (e.g., intermediate UE) and the A-IoT devices 3-1. Alternatively, the resource configuration may, for example, be a dedicated resource configuration that configures / allocates only D2R resources (or possible only R2D resources).

[0142] The resource configuration generated at step S502 may, for example, configure / assign resources that may correspond to one, or a set of, transmission occasions, and may, for example, include specific time and / or frequency resources, resources with a specific transport block size (TBS) modulation, resources with a specific coding scheme, or the like.

[0143] The resource configuration generated at step S502 may, for example, configure / assign resources on a static, or semi-static basis. For example, the resource configuration may configure / assign resources for use in communications between the A-IoT device reader and A-IoT devices 3-1 that persist until the A-IoT device reader is informed otherwise e.g., until a new resource configuration is generated and sent to the A-IoT device reader by the RAN node 5-1. The resource configuration generated at step S502 may thus be considered to configure / assign resources in a similar way to how resources are configured / assigned by a conventional configured grant (CG) or the like.

[0144] The resource configuration generated at step S502 may, for example, only be valid in certain circumstances. For example, by default, the resource configuration generated at step S502 may only be valid in a 'current' cell being used by the RAN node 5-1 for communicating with the intermediate / assisting node 5-2 (e.g., intermediate UE). Additionally (or alternatively), the resource configuration generated at step S502 may be treated as valid based on one or more other conditions or criteria as described in more detail below. It will be appreciated that the validity conditions or criteria may, themselves, be configurable by the RAN node 5 such that one resource configuration is considered valid when one or more configured conditions or criteria are met / fulfilled, and another resource configuration is considered valid when one or more different configured conditions or criteria are met / fulfilled.

[0145] At step S504, the RAN node 5-1 sends the A-IoT resource configuration it generated at step S502 to the intermediate / assisting node 5-2 (e.g., intermediate UE). That A-IoT resource configuration may be sent by the RAN node 5-1 to the intermediate / assisting node 5-2 (e.g., intermediate UE) via, by way of example only, an RRC message (or the like) in either a static, or semi-static manner.

[0146] The resources configured / allocated by the A-IoT resource configuration may be considered to be valid resources for use with one or more A-IoT devices 3-1 by the intermediate / assisting node 5-2 (e.g., intermediate UE) based on one or more (possibly configurable) conditions or criteria. For example, the resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader following expiration of a timer configured for (or associated with) the resources.

[0147] In another example, resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader based on the mode / state of the A-IoT device reader - e.g., only when the A-IoT device reader is in an RRC CONNECTED state (mode), an RRC INACTIVE state (mode), and / or an RRC IDLE state (mode).

[0148] In another example, resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader only up until a point where the RAN node 5-1 sends a second (follow-up) message (e.g., a new A-IoT resource configuration) to the A-IoT device reader to deconfigure / reconfigure the resources.

[0149] In yet another example, resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader based on a number (or quantity) of resources - or CG resources specifically - configured by the A-IoT resource configuration. For example, where the A-IoT resource configuration sent at step S504 allocates a given number (N) of allocated (CG) resources those N CG resources may be treated as valid following a designated (e.g., time-domain) pattern.

[0150] In yet another example, resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader for a specific area scope which may be defined, for example, by a list of cells, a tracking area, a radio network area, or some other specified area. For example, the resources configured by the A-IoT resource configuration sent at step S504 may be considered valid resources by the A-IoT device reader for a specific area covered by a specific list of cells.

[0151] In yet another example, resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader for one or more specific types of A-IoT device (e.g., a type 1, 2a, 2b A-IoT device). Alternatively (or additionally), the resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader for one or more specific groups of A-IoT devices, which may, for example, be identified by an A-IoT device group ID, or the like. Alternatively (or additionally), the resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader for one specific A-IoT device 3-1, which may, for example, be identified by its A-IoT device ID. Alternatively (or additionally), the resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader for any other specific sub-category of A-IoT devices 3-1.

[0152] In yet another example, resources configured by the A-IoT resource configuration sent at step S504 may be treated as valid resources by the A-IoT device reader for use in specific types of A-IoT communications. For example, the resources configured by the A-IoT resource configuration sent at step S504 may be considered valid resources by the A-IoT device reader for the purposes of performing one or more of A-IoT data transmissions, A-IoT paging, A-IoT command transmission, and / or the like.

[0153] It will be appreciated that validity may be based on anyone, or a combination of two or more, of the above conditions / criteria.

[0154] Upon receipt of the A-IoT resource configuration sent at step S504, the resources that are indicated in the A-IoT resource configuration (and which are considered valid by the A-IoT device reader) may be automatically activated i.e., the resources may be made used as soon as they are configured by the A-IoT resource configuration.

[0155] Alternatively (or additionally), at step S506, the RAN node 5-1 may optionally send an activation (or deactivation, or cancellation) indication to the A-IoT device reader to activate (or deactivate or cancel) all (or a selected subset of) the resources configured by the A-IoT resource configuration sent to the A-IoT device reader at step S504.

[0156] For example, the RAN node 5-1 may send an appropriate indication or message to the A-IoT device reader to activate (or deactivate or cancel) all (or a selected subset of) the resources configured by the A-IoT resource configuration sent to the A-IoT device reader at step S504. That appropriate indication may, by way of example only, be sent to the A-IoT device reader by the RAN node 5-1 via a Layer-2 (L2) MAC Control Element (CE) or a Layer-1 (L1) DCI that is sent by the RAN node 5-1 to the A-IoT device reader while the A-IoT device reader is in an RRC CONNECTED state (mode) and able to communicate with the RAN node 5-1.

[0157] At step S508 the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader announces the resources allocated to / configured for the A-IoT devices 3-1 by the RAN node 5-1 and indicated to the intermediate / assisting node 5-2 (e.g., intermediate UE) by the A-IoT resource configuration sent at step S504. By way of example only, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may announce the resources allocated to / configured for the A-IoT devices 3-1 via an A-IoT paging message, an A-IoT scheduling message, or the like, sent to the A-IoT devices over an appropriate A-IoT interface.

[0158] That A-IoT paging message, an A-IoT scheduling message, or the like, announces / indicates the resources configured for use by the A-IoT devices 3-1 in communication with the A-IoT device reader, which may include indication as to whether the resources are allocated / configured to be shared by multiple A-IoT devices 3-1 or, alternatively whether they are allocated / configured as dedicated resources for use by a single A-IoT device 3-1.

[0159] At step S510, the A-IoT devices 3-1 use the allocated resources that were announced to them at step S508 to send a D2R transmission (e.g., a specific D2R message or a data transmission, or the like) to the A-IoT device reader.

[0160] At step S512, the A-IoT device reader (e.g., intermediate UE) may forward the D2R transmission (e.g., a specific D2R message or a data transmission, or the like) that it received from an A-IoT device 3-1 to the RAN node 5-1.

[0161] At step S514, the RAN node 5-1 may decide to reconfigure the resources to be allocated to / configured for the A-IoT devices 3-1 for use in performing D2R transmissions and / or R2D transmissions. For example, the RAN node 5-1 may generate a new A-IoT resource configuration to cancel previously allocated resources for the A-IoT devices 3-1 and / or to add new allocated resources for the A-IoT devices 3-1, which it sends, at step S514, to the A-IoT device reader.

[0162] Having received the new A-IoT resource configuration at step S514, the steps S506 through to S510 may be repeated.

[0163] <Resource Allocation Procedure for A-IoT Devices during a Handover (HO) of an A-IoT Device Reader> 　　Fig. 6 illustrates a simplified sequence diagram of a resource allocation procedure for A-IoT devices that may be implemented in the communication system 1 when an A-IoT device reader in communication with the A-IoT devices experiences a HO, or other such mobility procedure.

[0164] As shown in Fig. 6, there is provided a source RAN node 5-11 (e.g., a base station, or the like) in communication with an intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE, or the like). Additionally, as shown in Fig. 6, the intermediate / assisting node 5-2 that operates as an A-IoT device reader is in communication with one or more A-IoT devices 3-1. There is also a target RAN node 5-12 (e.g., a base station, or the like) to which the intermediate / assisting node 5-2 may be handed over during a mobility procedure (e.g., a handover procedure, or the like).

[0165] Whilst the following description refers to the A-IoT device reader specifically as an intermediate UE this does not preclude the A-IoT device reader being any other appropriate intermediate device capable of acting as an A-IoT device reader and of being handed over between RAN nodes 5.

[0166] To enable one or more A-IoT devices 3-1 to communicate with the target RAN node 5-12 (e.g., send a data transmission to the target RAN node 5-12) after completion of a handover of the intermediate / assisting node 5-2 from the source RAN node 5-11 to the target RAN node 5-12, the source RAN node 5-1 may employ a resource allocation procedure such as that shown in Fig. 6.

[0167] It will be appreciated that in the procedure of Fig. 6, the intermediate / assisting node 5-2 will typically form an appropriate connection with the source RAN node 5-11 prior to being able to communicate with the source RAN node 5-11 (and target RAN node 5-12) and act as an A-IoT device reader for the A-IoT device 3-1. For example, where the intermediate / assisting node 5-2 is an intermediate UE, that intermediate UE will typically enter an RRC connected state (like a typical UE) prior to being able to act as an A-IoT device reader for the A-IoT device 3-1.

[0168] At step S602, after being triggered to hand over the intermediate / assisting node 5-2 to a target RAN node 5-12 (or having decided to hand over the intermediate / assisting node 5-2 to a target RAN node 5-12), the source RAN node 5-11 may send an appropriate handover (HO) request message, or the like, to the target RAN node 5-12 to initiate the HO procedure. That HO request message may, for example, be any appropriate HO request message, and may also include an appropriate information element (IE) to indicate to the target RAN node 5-12 a request for a new resource allocation for the A-IoT devices 3-1 in communication with the intermediate / assisting node 5-2.

[0169] At step S604, the target RAN node 5-12 sends to the source RAN node 5-11 a HO request acknowledgement (ACK) message, or the like, to acknowledge receipt of the HO request message sent at step S602. That HO request ACK message may, for example, include an appropriate IE associated with the request for the allocation of resources for the A-IoT devices 3-1 indicated in the HO request message sent at step S602. That IE may include one (or a set of) configured grant (CG)-type resources for use by the A-IoT devices 3-1 in communication with the intermediate / assisting node 5-2 acting as an A-IoT device reader. Additionally, that IE may include validity information associated with the one (or the set of) CG-type resources.

[0170] For example, that IE may include validity information associated with the one (or the set of) CG-type resources expressed as a number of the CG-type resources. In another example, that IE may include validity information associated with the one (or the set of) CG-type resources expressed as a duration of the CG-type resources.

[0171] Alternatively, that IE may include validity information associated with the one (or the set of) CG-type resources expressed in the form of some other appropriate validity condition or criteria that should be applied by the intermediate / assisting node 5-2 to determine whether or not the one (or a set of) CG-type resources indicated in the HO request ACK message are valid. For example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader following expiration of a timer configured for (or associated with) the resources.

[0172] In another example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader only when the A-IoT device reader is in an RRC CONNECTED state (mode), an RRC INACTIVE state (mode), and / or an RRC IDLE state (mode).

[0173] In another example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader only up until the point where the A-IoT device reader receives a second (follow-up) message (e.g., a new A-IoT resource configuration) to the A-IoT device reader to deconfigure / reconfigure / deactivate the resources.

[0174] In yet another example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader based on the number of resources allocated by the IE.

[0175] In yet another example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader for a specific area scope which may be defined, for example, by a list of cells, a tracking area, a radio network area, or some other specified area.

[0176] In yet another example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader for one or more specific types of A-IoT device (e.g., a type 1, 2a, 2b A-IoT device). Alternatively (or additionally), the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader for one or more specific groups of A-IoT devices, which may, for example, be identified by an A-IoT device group ID, or the like. Alternatively (or additionally), the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader one specific A-IoT device 3-1, which may, for example, be identified by its A-IoT device ID. Alternatively (or additionally), the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader for any other specific sub-category of A-IoT devices 3-1.

[0177] In yet another example, the IE in the HO request ACK message may include an indication, or the like, that the one (or a set of) CG-type resources indicated in the HO request ACK message should be considered valid by the A-IoT device reader for use in specific types of A-IoT communications.

[0178] At step S606, the source RAN node 5-11 sends an appropriate HO command within an appropriate message (e.g., an RRC Reconfiguration Message, or the like) to the intermediate / assisting node 5-2 acting as an A-IoT device reader (e.g., an intermediate UE) to trigger the intermediate / assisting node 5-2 to prepare for a handover. For example, at step S606, the source RAN node 5-11 may forward the HO ACK message it received from the target RAN node 5-12 to the intermediate / assisting node 5-2 using an appropriate transparent container to trigger the intermediate / assisting node 5-2 to prepare for a handover. It will be appreciated that in this scenario, the source RAN node 5-11 does not perform any processing of the information contained within the HO ACK message but merely forwards it onto the intermediate / assisting node 5-2.

[0179] At step S608, the intermediate / assisting node 5-2 acting as an A-IoT device reader may access a cell (e.g., a new cell) provided by the target RAN node 5-12 using any appropriate access procedure known to the skilled person to enable the intermediate / assisting node 5-2 to communicate with the target RAN node 5-12.

[0180] At step S610, the intermediate / assisting node 5-2 may respond to the HO command that it received at step S606. For example, at step S610, the intermediate / assisting node 5-2 may send an appropriate message (e.g., an RRC Reconfiguration Complete message, or the like) to the target RAN node 5-12 to confirm successful handover of the intermediate / assisting node 5-2 to the target RAN node 5-12.

[0181] It will be appreciated that in a variation of this method, if at step S602 the HO request sent by the source RAN node 5-11 to the target RAN node 5-12 does not include an appropriate IE to request the allocation of resources for the A-IoT devices 3-1 as described above, such a request for the allocation of resources for the A-IoT devices 3-1 may be included in the message sent at step S610 to request the allocation of resources for the A-IoT devices 3-1 by the target RAN node 5-12. In this scenario, it will be appreciated that the HO acknowledgement message may not include the configuration information and / or validity information described with reference to step S604. Instead, therefore, an appropriate message (not shown) may subsequently be sent by the target RAN node 5-12 to the intermediate / assisting node 5-2 to configure resources for A-IoT communications between the intermediate / assisting node 5-2 and the A-IoT devices 3-1. That appropriate message may, for example, be another configuration message (e.g., an RRC Reconfiguration message), or the like and may include the configuration information and / or validity information described with reference to step S604.

[0182] At step S612, the the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader announces the resources allocated to / configured for the A-IoT devices 3-1 by the target RAN node 5-12 and indicated to the intermediate / assisting node 5-2 (e.g., intermediate UE). By way of example only, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may announce the resources allocated to / configured for the A-IoT devices 3-1 via an A-IoT paging message, an A-IoT scheduling message, or the like, sent to the A-IoT devices over an appropriate A-IoT interface.

[0183] That A-IoT paging message, an A-IoT scheduling message, or the like, announces / indicates the resources configured for use by the A-IoT devices 3-1 in communication with the A-IoT device reader, which may include indication as to whether the resources are allocated / configured to be shared by multiple A-IoT devices 3-1 or, alternatively whether they are allocated / configured as dedicated resources for use by a single A-IoT device 3-1.

[0184] <Resource Allocation Procedure for A-IoT Devices during an RRC State Transition of an A-IoT device reader> 　　Fig. 7 illustrates a simplified sequence diagram of a resource allocation procedure for A-IoT devices that may be implemented in the communication system 1 when an A-IoT device reader in communication with the A-IoT devices undergoes an RRC state transition.

[0185] As shown in Fig. 7, there is provided a RAN node 5-1 (e.g., a base station, or the like) in communication with an intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE, or the like). Additionally, as shown in Fig. 7, the intermediate / assisting node 5-2 that operates as an A-IoT device reader is in communication with one or more A-IoT devices 3-1. Whilst the following description refers to the A-IoT device reader specifically as an intermediate UE this does not preclude the A-IoT device reader being any other appropriate intermediate device capable of acting as an A-IoT device reader.

[0186] To enable one or more A-IoT devices 3-1 to communicate with the RAN node 5-1 (e.g., send data transmission requested by the RAN node 5-1), the RAN node 5-1 employs a resource allocation procedure such as that shown in Fig. 7.

[0187] It will be appreciated that in the procedure of Fig. 7, the intermediate / assisting node 5-2 will typically form an appropriate connection with the RAN node 5-1 prior to being able to communicate with the RAN node 5-1 and act as an A-IoT device reader for the A-IoT device 3-1. For example, where the intermediate / assisting node 5-2 is an intermediate UE, that intermediate UE will typically enter an RRC connected state (like a typical UE) prior to being able to act as an A-IoT device reader for the A-IoT device 3-1.

[0188] At step S702, the RAN node 5-1 allocates a resource (or resources) for A-IoT communication between the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as an A-IoT device reader and which is in communication with the RAN node 5-1, and the one or more A-IoT devices 3-1.

[0189] For example, the RAN node 5-1 may generate / prepare a resource configuration, or the like. That resource configuration may, for example, be a dedicated resource configuration that configures / allocates both D2R resources for D2R link communications between the intermediate / assisting node 5-2 (e.g., intermediate UE) and the A-IoT devices 3-1, and R2D resources for R2D link communications between the intermediate / assisting node 5-2 (e.g., intermediate UE) and the A-IoT devices 3-1. Alternatively, the resource configuration may, for example, be a dedicated resource configuration that configures / allocates only D2R resources (or possible only R2D resources).

[0190] The resource configuration generated at step S702 may, for example, configure / assign resources that may correspond to one, or a set of, transmission occasions, and may, for example, include specific time and / or frequency resources, resources with a specific transport block size (TBS) modulation, resources with a specific coding scheme, or the like.

[0191] The resource configuration generated at step S702 may, for example, configure / assign resources on a static, or semi-static basis. For example, the resource configuration may configure / assign resources for use in communications between the A-IoT device reader and A-IoT devices 3-1 that persist until the A-IoT device reader is informed otherwise e.g., until a new resource configuration is generated and set to the A-IoT device reader by the RAN node 5-1. The resource configuration generated at step S702 may thus be considered to configure / assign resources in a similar way to how resources are configured / assigned by a conventional configured grant (CG) or the like.

[0192] The resource configuration generated at step S702 may, for example, only be valid in certain circumstances. For example, by default, the resource configuration generated at step S702 may only be valid in a 'current' cell being used by the RAN node 5-1 for communicating with the intermediate / assisting node 5-2 (e.g., intermediate UE). Additionally (or alternatively), the resource configuration generated at step S702 may be treated as valid based on one or more other conditions or criteria as described in more detail below. It will be appreciated that the validity conditions or criteria may, themselves, be configurable by the RAN node 5 such that one resource configuration is considered valid when one or more configured conditions or criteria are met / fulfilled, and another resource configuration is considered valid when one or more different configured conditions or criteria are met / fulfilled.

[0193] At step S704, the RAN node 5-1 sends the A-IoT resource configuration it generated at step S702 to the intermediate / assisting node 5-2 (e.g., intermediate UE). That A-IoT resource configuration may be sent by the RAN node 5-1 to the intermediate / assisting node 5-2 (e.g., intermediate UE) via, by way of example only, an RRC message (or the like) in either a static, or semi-static manner.

[0194] The resources configured / allocated by the A-IoT resource configuration may be considered to be valid resources for use with one or more A-IoT devices 3-1 by the intermediate / assisting node 5-2 (e.g., intermediate UE) based on one or more (possibly configurable) conditions or criteria. For example, the resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader following expiration of a timer configured for (or associated with) the resources.

[0195] In another example, resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader based on the mode / state of the A-IoT device reader - e.g., only when the A-IoT device reader is in an RRC CONNECTED state (mode), an RRC INACTIVE state (mode), and / or an RRC IDLE state (mode).

[0196] In another example, resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader only up until a point where the RAN node 5-1 sends a second (follow-up) message (e.g., a new A-IoT resource configuration) to the A-IoT device reader to deconfigure / reconfigure the resources.

[0197] In yet another example, resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader based on a number or quantity of resources - or CG resources specifically - configured by the A-IoT resource configuration. For example, where the A-IoT resource configuration sent at step S704 allocates a given number (N) of allocated (CG) resources those N CG resources may be treated as valid following a designated (e.g., time-domain) pattern.

[0198] In yet another example, resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader for a specific area scope which may be defined, for example, by a list of cells, a tracking area, a radio network area, or some other specified area. For example, the resources configured by the A-IoT resource configuration sent at step S704 may be considered valid resources by the A-IoT device reader for a specific area covered by a specific list of cells.

[0199] In yet another example, resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader for one or more specific types of A-IoT device (e.g., a type 1, 2a, 2b A-IoT device). Alternatively (or additionally), the resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader for one or more specific groups of A-IoT devices, which may, for example, be identified by an A-IoT device group ID, or the like. Alternatively (or additionally), the resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader for one specific A-IoT device 3-1, which may, for example, be identified by its A-IoT device ID. Alternatively (or additionally), the resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader for any other specific sub-category of A-IoT devices 3-1.

[0200] In yet another example, resources configured by the A-IoT resource configuration sent at step S704 may be treated as valid resources by the A-IoT device reader for use in specific types of A-IoT communications. For example, the resources configured by the A-IoT resource configuration sent at step S704 may be considered valid resources by the A-IoT device reader for the purposes of performing one or more of A-IoT data transmissions, and / or A-IoT paging, and / or A-IoT command transmission, and / or the like.

[0201] It will be appreciated that validity may be based on anyone, or a combination of two or more, of the above conditions / criteria.

[0202] At step S706, the intermediate / assisting node 5-2 (e.g., intermediate UE) switches from an RRC CONNECTED state (mode) to an RRC IDLE or an RRC INACTIVE state (mode). For example, the intermediate / assisting node 5-2 may switch to an RRC IDLE or an RRC INACTIVE state (mode) in cases of out of cellular coverage, coverage hole, a radio link failure (RLF), a connection loss, a handover failure, RRC reestablishment failure, or any other event or trigger that causes the intermediate / assisting node 5-2 to switch to an RRC IDLE or an RRC INACTIVE state (mode).

[0203] For example, the intermediate / assisting node 5-2 (e.g., intermediate UE) may switch from an RRC CONNECTED state (mode) to an RRC IDLE or an RRC INACTIVE state (mode) when the RAN node 5-1 decides to transition the intermediate / assisting node 5-2 to an RRC IDLE or an RRC INACTIVE state (mode).

[0204] It will be appreciated that when an the intermediate / assisting node 5-2 transitions from an RRC CONNECTED state to an RRC IDLE or an RRC INACTIVE state (mode), any session (e.g., data session, or the like) established between one or more of the A-IoT devices 3-1 and the core network 7 (or any other upper layer entity involved in A-IoT communication) may remain active, or may remain active within a time window controlled by a timer.

[0205] At step S707, the intermediate / assisting node 5-2 acting as an A-IoT device reader, upon switching from an RRC CONNECTED state (mode) to an RRC IDLE or an RRC INACTIVE state (mode), may store the resources allocated by the RAN node 5-1 for A-IoT communication indicated to the intermediate / assisting node 5-2 at step S704 in its memory.

[0206] For example, the intermediate / assisting node 5-2 (e.g., intermediate UE) stores the ambient resource configuration in a new specific UE Context (e.g., a UE Ambient IoT Context). If the intermediate / assisting node 5-2 (e.g., intermediate UE) switches to an RRC INACTIVE state (mode), it may store the ambient resource configuration as part of UE Inactive AS Context. If the intermediate / assisting node 5-2 (e.g., intermediate UE) switches to an RRC IDLE state (mode), it may store the ambient resource configuration in new variables specific to A-IoT devices.

[0207] Those stored resources may subsequently be used by the intermediate / assisting node 5-2 to schedule A-IoT communications with the A-IoT devices 3-1 over an appropriate interface (e.g., an A-IoT interface) if the allocated resources are considered valid by the intermediate / assisting node 5-2 and the intermediate / assisting node 5-2 is able to schedule A-IoT transmissions with the A-IoT devices 3-1 (e.g., if the intermediate / assisting node 5-2 is able to schedule A-IoT transmissions with the A-IoT devices 3-1 while in an RRC IDLE or INACTIVE state).

[0208] Additionally, the scheduling of such A-IoT communications with the A-IoT devices 3-1 using those stored allocated resources may, for example, be conditional upon one or more other conditions or criteria configured by the RAN node 5-1 and indicated to the intermediate / assisting node 5-2 in the A-IoT resource configuration sent at step S704. For example, intermediate / assisting node 5-2 may additionally only schedule such A-IoT communications with the A-IoT devices 3-1 using those stored allocated resource provided one or more conditions or criteria associated with an area scope defined by a list of cell, a track area, a radio network area, or any other specific area are met.

[0209] At step S708 the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader, while in RRC IDLE or RRC INACTIVE state (mode) for A-IoT interface-based communications, announces the resources allocated to / configured for the A-IoT devices 3-1 by the RAN node 5-1 and indicated to the intermediate / assisting node 5-2 (e.g., intermediate UE) by the A-IoT resource configuration sent at step S704. By way of example only, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may announce the resources allocated to / configured for the A-IoT devices 3-1 via an A-IoT paging message, an A-IoT scheduling message, or the like, sent to the A-IoT devices over an appropriate A-IoT interface.

[0210] That A-IoT paging message, an A-IoT scheduling message, or the like, announces / indicates the resources configured for use by the A-IoT devices 3-1 in communication with the A-IoT device reader, which may include indication as to whether the resources are allocated / configured to be shared by multiple A-IoT devices 3-1 or, alternatively whether they are allocated / configured as dedicated resources for use by a single A-IoT device 3-1.

[0211] At step S710, the A-IoT devices 3-1 use the allocated resources that were announced to them at step S708 to send a D2R transmission (e.g., a specific D2R message or a data transmission, or the like) to the A-IoT device reader, while the A-IoT device reader is in RRC IDLE or RRC INACTIVE state (mode) for A-IoT interface-based communications.

[0212] At step S712, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader, while in RRC IDLE or RRC INACTIVE state (mode), may successfully (re)access the network. For example, the intermediate / assisting node 5-2 (e.g., intermediate UE) may successfully complete an RRC re-establishment procedure, or the like, which may, for example, be triggered by the RAN node 5-1 after a RLF event, a connection loss event, a handover failure event, or the like.

[0213] Alternatively, at step S712, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may itself initiate an RRC connection (re)establishment procedure, or the like, to (re)access the network.

[0214] For example, having received and buffered messages and / or data from the A-IoT devices 3-1 at step S710, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may itself initiate an RRC connection (re)establishment procedure, or the like, to (re)access the network when the amount of stored information (e.g., corresponding to buffered messages and / or data received from the A-IoT devices 3-1) reaches a threshold value. Having received that threshold value, the intermediate / assisting node 5-2 (e.g., intermediate UE) may be triggered to initiate an RRC connection (re)establishment procedure, or the like, to (re)access the network to allow for the messages and / or data to be forwarded onto the RAN node 5-1. In another example, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may itself initiate an RRC connection (re)establishment procedure, or the like, to (re)access the network when / if the resources allocated by the RAN node 5-1 at step S704 expires.

[0215] At step S714, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader forwards the buffered messages and / or data that it received from an A-IoT device 3-1 to the RAN node 5-1 at step S710 having transitioned back to an RRC CONNECTED state (mode). The buffered messages and / or data may, for example, be forwarded to the RAN node 5-1 in an appropriate message of the RRC connection (re)establishment procedure (e.g., an RRC Reconfiguration Complete message, or the like - i.e., a first RRC message sent by the A-IoT device reader to the RAN node 5-1).

[0216] At step S716, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may (optionally) send a resource allocation request message (or indication) to the RAN node 5-1 to request the allocation of new resources for use in A-IoT communication between the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader and the A-IoT devices 3-1. For example, at step S716, the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may send a resource allocation request to the RAN node 5-1 when / if the resources allocated and configured at steps S702 and S704 are no longer valid or have expired.

[0217] Alternatively (or additionally), the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader may send a resource allocation request to the RAN node 5-1 when / if the amount of resources allocated and configured at steps S702 and S704 (or the amount of those resources that are still valid) are more or less than the amount of resources currently needed for communication between the intermediate / assisting node 5-2 (e.g., intermediate UE) acting as the A-IoT device reader and the A-IoT devices 3-1.

[0218] At step S718, the RAN node 5-1 may decide, either independently or in response to the request received at step S716, to reconfigure the resources to be allocated to / configured for the A-IoT devices 3-1 for use in performing D2R transmissions and / or R2D transmissions. For example, the RAN node 5-1 may generate a new A-IoT resource configuration to cancel previously allocated resources for the A-IoT devices 3-1 and / or to add new allocated resources for the A-IoT devices 3-1, which it sends, at step S718, to the A-IoT device reader (in a similar manner to that described with reference to steps S702 and S704).

[0219] Having received the new A-IoT resource configuration at step S718, the steps S706 through to S716 may be repeated.

[0220] <Enhanced Power Control Procedures for A-IoT Devices> <Power Control Procedures for A-IoT Devices in A-IoT Topology 1> 　　Fig. 8 illustrates a simplified sequence diagram of a power control procedure for A-IoT devices that may be implemented in the communication system 1. As shown in Fig. 8, there is provided a RAN node 5-1 (e.g., a base station, or the like) in communication with one or more A-IoT devices 3-1. While Fig. 8 shows that there may be one or more A-IoT devices 3-1, for simplicity the following description will refer to a single A-IoT device 3-1.

[0221] At step S802, the RAN node 5-1 sends an appropriate configuration message (e.g., a power control configuration, or the like) to the A-IoT device 3-1 to control its power usage. That configuration message may, for example, provide open-loop power control of the A-IoT device 3-1 (i.e., power control that does not make use of feedback information). That power control configuration may, for example, be sent by the RAN node 5-1 to the A-IoT device at step S802 via a MAC CE, physical layer control information, or any appropriate L1 control signaling.

[0222] The power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT device 3-1 to disable its A-IoT transmissions to the RAN node 5-1 if a Signal-to-Interference-plus-Noise Ratio (SINR) or Reference Signal Received Power (RSRP) measured for the D2R link between the RAN node 5-1 and the A-IoT device is larger than a threshold value.

[0223] Alternatively (or additionally), the power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 may, for example, include the RAN node 5-1 sends an appropriate information elements / indications for configuring the A-IoT device 3-1 to enable its A-IoT transmissions to the RAN node 5-1 if a Signal-to-Interference-plus-Noise Ratio (SINR) or Reference Signal Received Power (RSRP) measured for the D2R transmission link between the RAN node 5-1 and the A-IoT device is smaller than a threshold value.

[0224] Alternatively (or additionally), the power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 may, for example, include an indication of a minimum and / or maximum transmission power that the A-IoT device 3-1 may use. It will be appreciated that a minimum and / or maximum transmission power that the A-IoT device 3-1 may use, may also be configured via a MAC CE, physical layer control information, or any appropriate L1 control signaling.

[0225] Alternatively (or additionally), the power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT device 3-1 to use a minimum transmission power (which may be configured as described above) based on an RSRP threshold value (i.e., based on a measurement of an R2D signaling strength).

[0226] Alternatively (or additionally), the power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT device 3-1 to report its SINR or RSRP measurement over the R2D transmission link.

[0227] Alternatively (or additionally), the power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT device 3-1 to report its SINR or RSRP measurement over an R2D transmission link when the measured SINR or RSRP is larger (or smaller) than a threshold value.

[0228] At step S804, the A-IoT device 3-1 sends an appropriate measurement report to the RAN node 5-1 when appropriate. For example, where the the power control configuration sent by the RAN node 5-1 to the A-IoT device 3-1 at step S802 configures the A-IoT device 3-1 to report one or more measurement (e.g., an SINR and / or RSRP value) to the RAN node 5-1, then those measurements are reported to the RAN node 5-1 at step S804.

[0229] <Power Control Procedures for A-IoT Devices in A-IoT Topology 2> 　　Fig. 9 illustrates a simplified sequence diagram of another power control procedure for A-IoT devices that may be implemented in the communication system 1.

[0230] As shown in Fig. 9, there is provided a RAN node 5-1 (e.g., a base station, or the like) in communication with an intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE , or the like). Additionally, as shown in Fig. 9, the intermediate / assisting node 5-2 that operates as an A-IoT device reader is in communication with one or more A-IoT devices 3-1. Whilst the following description refers to the A-IoT device reader specifically as an intermediate UE this does not preclude the A-IoT device reader being any other appropriate intermediate device capable to acting as an A-IoT device reader.

[0231] At step S902, the RAN node 5-1 sends an appropriate configuration message (e.g., a power control configuration, or the like) to the intermediate / assisting node 5-2 to control its power usage. That configuration message may, for example, provide open-loop power control of the intermediate / assisting node 5-2 and / or the A-IoT devices 3-1 (i.e., power control that does not make use of feedback information). That power control configuration may, for example, be sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 via a MAC CE, physical layer control information, or any appropriate L1 control signaling (e.g., RRC signaling, or the like).

[0232] The power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE, or the like) to use specific power levels for different types of transmissions. For example, a power control configuration may configure a number of (e.g., four) different power levels and each different power level may be respectively used for one or more different types of transmissions e.g., common transmissions, RACH responses, data transmission, and the like.

[0233] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE, or the like) to use a specific power level for common transmissions that are sent by the intermediate / assisting node 5-2 toward all (or a plurality) of A-IoT devices 3-1 in communication with the intermediate / assisting node 5-2.

[0234] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 that operates as an A-IoT device reader (for example an intermediate / assisting UE, or the like) to use a specific power level for RACH response transmissions (e.g., 'Msg2' of a RACH procedure) over an A-IoT interface toward all (or a subset of one or more) of the A-IoT devices 3-1 in communication with the intermediate / assisting node 5-2.

[0235] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to use a specific power level for dedicated transmissions over an A-IoT interface toward a dedicated A-IoT device 3-1 or a group of A-IoT devices 3-1 in communication with the intermediate / assisting node 5-2.

[0236] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 with a minimum and / or a maximum power value for use by the intermediate / assisting node 5-2.

[0237] Alternatively, the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 with a minimum power value for use by the intermediate / assisting node 5-2.

[0238] Alternatively, the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 with a maximum power value for use by the intermediate / assisting node 5-2.

[0239] Additionally, the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to use the maximum power value based on a condition being met. For example, the intermediate / assisting node 5-2 may be configured to use the maximum power value when a measurement of a SINR value for the D2R transmission link meets a threshold value.

[0240] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to use the minimum power value based on a condition being met. For example, the intermediate / assisting node 5-2 may be configured to use the minimum power value when a measurement of a SINR value for the D2R transmission link meets a threshold value.

[0241] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to stop its transmissions over the R2D link (and stop acting as an A-IoT device reader) when an RSRP or SINR measurement for the D2R link is larger than a threshold value.

[0242] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to initiate its transmissions over the R2D link (and start acting as an A-IoT device reader) when an RSRP or SINR measurement for the D2R link is smaller than a threshold value.

[0243] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to measure RSRP and / or SINR values for the D2R transmission link within a (pre)configured measurement window.

[0244] Additionally, the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to report its measured RSRP and / or its measured SINR values for the D2R transmission link within a (pre)configured reporting interval to the RAN node 5-1.

[0245] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to report / forward measured RSRP and / or measured SINR values to the RAN node 5-1 for the R2D transmission link that the intermediate / assisting node 5-2 has received from the A-IoT devices 3-1.

[0246] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the intermediate / assisting node 5-2 at step S902 may, for example, include one or more appropriate information elements / indications for configuring the intermediate / assisting node 5-2 to report its measured RSRP and / or its measured SINR values for the D2R transmission link when the measured RSRP and / or its measured SINR values are larger (or smaller) than a threshold value.

[0247] At step S904, the intermediate / assisting node 5-2 may forward the power control configuration it received from the RAN node 5-1 at step S902 to the A-IoT device or devices 3-1. Alternatively, the intermediate / assisting node 5-2 may send a different power control configuration to the A-IoT device or devices 3-1 that comprises, for example, a subset of the information elements / indications provided to the intermediate / assisting node 5-2 in the power control configuration it received from the RAN node 5-1 at step S902. That power control configuration sent to the A-IoT device or devices 3-1 may, for example, be sent via a MAC CE, R2D control information, or the like.

[0248] The power control configuration sent by the intermediate / assisting node 5-2 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring a minimum and / or maximum transmission power that the A-IoT device 3-1 may use.

[0249] Additionally, the power control configuration sent by the intermediate / assisting node 5-2 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to use the maximum transmission power when a measured RSRP value over the R2D transmission link meets a threshold value.

[0250] Additionally (or alternatively), the power control configuration sent by the intermediate / assisting node 5-2 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to use the minimum transmission power when a measured RSRP value for the R2D transmission link meets a threshold value.

[0251] Additionally (or alternatively), the power control configuration sent by the intermediate / assisting node 5-2 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to report its measured RSRP values associated with the R2D transmission link to the intermediate / assisting node 5-2.

[0252] Additionally (or alternatively), the power control configuration sent by the intermediate / assisting node 5-2 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to report its measured RSRP values associated with the R2D transmission link to the intermediate / assisting node 5-2 within a specified reporting interval.

[0253] Additionally (or alternatively), the power control configuration sent by the intermediate / assisting node 5-2 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to report its measured RSRP values and / or SINR values associated with the R2D transmission link to the intermediate / assisting node 5-2 when the measured RSRP values and / or SINR values are larger (or smaller) than a threshold value.

[0254] At step S906, the A-IoT devices 3-1 may generate D2R transmissions according to an indicated power level indicated to the A-IoT devices 3-1 by the power control configuration sent to the A-IoT devices by the intermediate / assisting node 5-2 at step S906. Those D2R transmissions may, for example, each include one or more measurement reports that report measured RSRP and / or SINR values measured for the R2D transmission link.

[0255] The transmission power used by the intermediate / assisting node 5-2 to transmit, for example, the power control configuration to the A-IoT devices 3-1 over the R2D transmission link, may be determined autonomously by the intermediate / assisting node 5-2 based on the measurement reports indicated to the intermediate / assisting node 5-2 by the A-IoT devices 3-1 at, for example, step S906. In this scenario, only measurement reports received from A-IoT devices 3-1 with which the intermediate / assisting node 5-2 has (or intends to) communicate may be used to determine a transmission power to be used by the intermediate / assisting node 5-2. For example, the intermediate / assisting node 5-2 may determine a transmission power to be used with A-IoT devices 3-1 based on a smallest, or largest, or average of the measurement reports received from the A-IoT devices 3-1 with which the intermediate / assisting node 5-2 has (or intends to) communicate.

[0256] Alternatively, the transmission power used by the intermediate / assisting node 5-2 to transmit, for example, the power control configuration to the A-IoT devices 3-1 over the R2D transmission link, may be determined by the RAN node 5-1 and indicated to the intermediate / assisting node 5-2 in a power control configuration (e.g., the power control configuration sent at step S902). In this scenario, the intermediate / assisting node 5-2 may gather all measurement reports sent to the intermediate / assisting node 5-2 from the A-IoT devices 3-1 at step S906 and forward those measurement reports to the RAN node 5-1 to enable the RAN node 3-1 to determine the transmission power to be used by the intermediate / assisting node 5-2.

[0257] At step S908, the intermediate / assisting node 5-2 may report its RSRP and / or SINR measurement results associated with the D2R transmission link to the RAN node 5-1. As indicated above, at step S908, all measurement reports sent to the intermediate / assisting node 5-2 from the A-IoT devices 3-1 at step S906 may be forwarded to the RAN node 5-1.

[0258] After step S908, the procedure of Fig. 9 may be restarted at step S902.

[0259] Fig. 10 illustrates a simplified sequence diagram of yet another power control procedure for A-IoT devices that may be implemented in the communication system 1.

[0260] As shown in Fig. 10 there is provided a RAN node 5-1 (e.g., a base station, or the like) in communication with a plurality of intermediate / assisting nodes 5-21, 5-22 (for example intermediate / assisting UEs, or the like) that each operate as an A-IoT device reader. Those intermediate / assisting nodes 5-21, 5-22 include a receiver (Rx) intermediate / assisting node 5-21 that operates as an Rx A-IoT device reader, and a transmitter (Tx) intermediate / assisting node 5-22 that operates as a Tx A-IoT device reader. Additionally, as shown in Fig. 10, the intermediate / assisting nodes 5-21, 5-22 are in communication with one or more A-IoT devices 3-1.

[0261] Whilst the following description refers to the A-IoT device readers specifically as intermediate UEs this does not preclude the A-IoT device readers being any other appropriate intermediate devices capable of acting as an A-IoT device reader.

[0262] At step S1002, the RAN node 5-1 sends an appropriate configuration message (e.g., a power control configuration, or the like) to the Tx intermediate / assisting node 5-21 to control its power usage. That configuration message may, for example, provide open-loop power control of the Tx intermediate / assisting node 5-21 and / or Rx intermediate / assisting node 5-22 and / or A-IoT devices 3-1 (i.e., power control that does not make use of feedback information). That power control configuration may, for example, be sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 via a MAC CE, physical layer control information, DCI, or any appropriate L1 control signaling (e.g., RRC signaling, or the like).

[0263] The power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 that operates as a Tx A-IoT device reader (for example an intermediate / assisting UE, or the like) to use specific power levels for different types of transmissions. For example, power control configuration may configure a number of (e.g., four) different power levels and each different power level may be respectively used for one or more different types of transmissions e.g., common transmissions, RACH responses, data transmission, and the like.

[0264] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 that operates as a Tx A-IoT device reader (for example an intermediate / assisting UE, or the like) to use a specific power level for common transmissions that are sent by the Tx intermediate / assisting node 5-21 toward all (or a plurality) of A-IoT devices 3-1 in communication with the Tx intermediate / assisting node 5-21.

[0265] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 that operates as a Tx A-IoT device reader (for example an intermediate / assisting UE, or the like) to a specific power level for RACH response transmissions (e.g., 'Msg2' of a RACH procedure) over an A-IoT interface toward all (or a subset of one or more) of the A-IoT devices 3-1 in communication with the Tx intermediate / assisting node 5-21.

[0266] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 to use a specific power level for dedicated transmissions over an A-IoT interface toward a dedicated A-IoT device 3-1 or a group of A-IoT devices 3-1 in communication with the Tx intermediate / assisting node 5-21.

[0267] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 with a minimum and / or a maximum power value for use by the Tx intermediate / assisting node 5-21.

[0268] Alternatively, the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications (in e.g., L1 control information, or the like) for configuring the Tx intermediate / assisting node 5-21 with a minimum power value for use by the Tx intermediate / assisting node 5-21.

[0269] Alternatively, the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications (in e.g., L1 control information, or the like) for configuring the Tx intermediate / assisting node 5-21 with a maximum power value for use by the Tx intermediate / assisting node 5-21.

[0270] Additionally, the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 to use the maximum power value based on a condition being met. For example, the Tx intermediate / assisting node 5-21 may be configured to use the maximum power value when a measurement of a SINR value of the D2R transmission link meets a threshold value.

[0271] Additionally (or alternatively), the power control configuration sent by the RAN node 5-1 to the Tx intermediate / assisting node 5-21 at step S1002 may, for example, include one or more appropriate information elements / indications for configuring the Tx intermediate / assisting node 5-21 to use the minimum power value based on a condition being met. For example, the Tx intermediate / assisting node 5-21 may be configured to use the minimum power value when a measurement of a SINR value of the D2R transmission link meets a threshold value.

[0272] At step S1004, the Tx intermediate / assisting node 5-21 may forward the power control configuration it received from the RAN node 5-1 at step S1002 to the A-IoT device or devices 3-1. Alternatively the Tx intermediate / assisting node 5-21 may send a different power control configuration to the A-IoT device or devices 3-1 that comprises, for example, a subset of the information elements / indications provided to the Tx intermediate / assisting node 5-21 in the power control configuration it received from the RAN node 5-1 at step S1002. That power control configuration sent to the A-IoT device or devices 3-1 may, for example, be sent via a MAC CE, Physical Layer control information, or the like).

[0273] The power control configuration sent by the Tx intermediate / assisting node 5-21 to the A-IoT device 3-1 at step S1004 may, for example, include one or more appropriate information elements / indications for configuring a minimum and / or maximum transmission power that the A-IoT device 3-1 may use.

[0274] Additionally, the power control configuration sent by the Tx intermediate / assisting node 5-21 to the A-IoT device 3-1 at step S1004 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to use the maximum transmission power when a measured RSRP value over the R2D transmission link meets a threshold value.

[0275] Additionally (or alternatively), the power control configuration sent by the Tx intermediate / assisting node 5-21 to the A-IoT device 3-1 at step S1004 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to use the minimum transmission power when a measured RSRP value for the R2D transmission link meets a threshold value.

[0276] Additionally (or alternatively), the power control configuration sent by the Tx intermediate / assisting node 5-21 to the A-IoT device 3-1 at step S1004 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to report its measured RSRP values associated with the R2D transmission link to the Tx intermediate / assisting node 5-21.

[0277] Additionally (or alternatively), the power control configuration sent by the Tx intermediate / assisting node 5-21 to the A-IoT device 3-1 at step S1004 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to report its measured RSRP values associated with the R2D transmission link to the Tx intermediate / assisting node 5-21 within a specified reporting interval.

[0278] Additionally (or alternatively), the power control configuration sent by the Tx intermediate / assisting node 5-21 to the A-IoT device 3-1 at step S904 may, for example, include one or more appropriate information elements / indications for configuring the A-IoT devices 3-1 to report its measured RSRP values and / or SINR values associated with the R2D transmission link to the Tx intermediate / assisting node 5-21 when the measured RSRP values and / or SINR values are larger (or smaller) than a threshold value.

[0279] At step S1006, RAN node 5-1 sends an appropriate configuration message (e.g., a power control configuration, or the like) to the Rx intermediate / assisting node 5-22 to control its power usage. That configuration message may, for example, provide open-loop power control of the Rx intermediate / assisting node 5-21 (i.e., power control that does not make use of feedback information). That power control configuration may, for example, be sent by the RAN node 5-1 to the Rx intermediate / assisting node 5-21 at step S1006 via a MAC CE, physical layer control information, DCI, or any appropriate L1 control signaling (e.g., RRC signaling, or the like).

[0280] That power control configuration sent to the Rx intermediate / assisting node 5-22 may, for example, configure the Rx intermediate / assisting node 5-22 to measure the RSRP and / or SINR value for the D2R transmission link between the Rx intermediate / assisting node 5-22 and the A-IoT devices 3-1 in a specific measurement window. Additionally, the power control configuration sent to the Rx intermediate / assisting node 5-22 may configure the Rx intermediate / assisting node 5-22 to report those measured RSRP and / or SINR values to the RAN node 5-1 (within a reporting interval).

[0281] Additionally (or alternatively), the power control configuration sent to the Rx intermediate / assisting node 5-22 may configure the Rx intermediate / assisting node 5-22 to report, to the RAN node 5-1, measured RSRP and / or SINR values associated with the R2D transmission link between the Rx intermediate / assisting node 5-22 and the A-IoT devices 3-1 that it receives from the A-IoT devices 3-1.

[0282] Additionally (or alternatively), the power control configuration sent to the Rx intermediate / assisting node 5-22 may configure the Rx intermediate / assisting node 5-22 to report, to the RAN node 5-1, the measured RSRP and / or SINR values for the D2R transmission link between the Rx intermediate / assisting node 5-22 and the A-IoT devices 3-1 when the measured RSRP and / or SINR values are larger than a threshold value.

[0283] At step S1008, the A-IoT devices 3-1 generate appropriate D2R transmissions according to an indicated power level indicated to the A-IoT devices 3-1 by the power control configuration sent to the A-IoT devices by the Tx intermediate / assisting node 5-21 at step S1004. Those D2R transmissions may, for example, each include one or more measurement reports that report measured RSRP and / or SINR values measured for the R2D transmission link.

[0284] At step S1010, the Tx intermediate / assisting node 5-22, having received one or more measurement reports from the A-IoT devices 3-1 at step S1008, may report its RSRP and / or SINR measurement results associated with the D2R transmission link to the RAN node 5-1 to enable the RAN node 3-1 to determine the transmission power to be used by the Rx intermediate / assisting node 5-22.

[0285] After step S1010, the procedure of Fig. 10 may be restarted at step S1002.

[0286] <Devices in the Communication System> <User Equipment> 　　Fig. 11 is a simplified block schematic illustrating the main components of a UE 3-2; 3-3 for implementation in the communication system 1. It will be appreciated that the UE 3-2; 3-3 may be configured to operate as an intermediate / assisting node 5-2 (i.e., and A-IoT device reader) in the communication system 1.

[0287] As shown, the UE 3-2; 3-3 has a transceiver circuit 31 that is operable to transmit signals to and to receive signals from a base station 5-1 via one or more antenna 33 (e.g., comprising one or more antenna elements). The UE 3 has a controller 37 to control the operation of the UE 3. The controller 37 is associated with a memory 39 and is coupled to the transceiver circuit 31. Although not necessarily required for its operation, the UE 3-2; 3-3 might, of course, have all the usual functionality of a conventional UE 3-2; 3-3 (e.g., a user interface 35, such as a touch screen / keypad / microphone / speaker and / or the like for, allowing direct control by and interaction with a user) and this may be provided by any one or any combination of hardware, software, and firmware, as appropriate. Software may be pre-installed in the memory 39 and / or may be downloaded via the communication system or from a removable data storage device (RMD), for example.

[0288] The controller 37 is configured to control overall operation of the UE 3-2; 3-3 by, in this example, program instructions or software instructions stored within memory 39. As shown, these software instructions include, among other things, an operating system 41, and a communication control module 43.

[0289] The communication control module 43 is operable to control the communication between the UE 3-2; 3-3 and its serving RAN node or RAN nodes 5-1 (and other communication devices connected to the RAN node 5-1, such as further UEs and / or core network nodes). The communication control module 43 is configured for the overall handling of uplink communication via associated uplink channels (e.g., via a physical uplink control channel (PUCCH), random access channel (RACH), and / or a physical uplink shared channel (PUSCH)) including both dynamic and semi-static signalling (e.g., SRS). The communication control module 43 is also configured for the overall handling of receipt of downlink communication via associated downlink channels (e.g., of DCI via a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH)) including both dynamic and semi-persistent scheduling (e.g., SPS). The communication control module 43 is responsible, for example: for determining where to monitor for downlink control information; for determining the resources to be used by the UE 3 for transmission / reception of UL / DL communication (including interleaved resources and resources subject to frequency hopping); for managing frequency hopping at the UE side; for determining how slots / symbols are configured (e.g., for UL, DL or full duplex communication, or the like); for determining which bandwidth parts are configured for the UE 3-2; 3-3; for determining how uplink transmissions should be encoded and the like.

[0290] Where the UE 3-2, 3-3 is configured to operate as an intermediate / assisting node 5-2 (i.e., as an A-IoT device reader) the communication control module 43 may be operable to control the communication between the IoT device 3-1 and the UE 3-2, 3-3, for example, via the associated physical channels (e.g., via a physical D2R channel (PDRCH), random access channel (RACH), and / or a physical R2D channel (PRDCH)).

[0291] It will be appreciated that the communication control module 43 may include a number of sub-modules ('layers' or 'entities') to support specific functionalities. For example, the UE 3-2, 3-3 may include sub-modules corresponding to the layers of a conventional protocol stack (PHY, MAC, RRC, RLC, PDCP etc.). Moreover, where the UE 3-2, 3-3 is configured to operate as an intermediate / assisting node 5-2, communication control module 43 may include sub-modules corresponding to the layers of a dedicated ambient IoT device protocol stack for controlling functions associated with those layers.

[0292] The communication control module 43 is configured, in particular, to control the UE's communication, where applicable, in accordance with any of the methods described herein.

[0293] <Ambient IoT device> 　　Fig. 12 is a simplified block schematic illustrating the main components of an example of a UE comprising an ambient IoT device 3-1 for possible implementation in the communication system 1.

[0294] As shown, the ambient IoT device 3-1 (also referred to simply as an IoT device 3-1) has a transceiver circuit 331 that is operable to transmit signals to and to receive signals from a RAN node 5-1 (and / or an assisting node 5-2, and / or an intermediate node 5-2) via one or more antenna 333 (e.g., comprising one or more antenna elements).

[0295] The transceiver circuit 331 may comprise energy harvesting circuitry 331-1 that is configured to harvest and / or collect energy from an ambient energy source such as an incoming signal and / or other ambient sources of energy (e.g., of light, vibrations, or heat). That collected energy may then be provided to other modules of IoT device 3-1 to provide a stable power supply to those modules. The energy harvesting circuitry 331-1 may include, by way of example only, inductive and / or capacitive architectures to harvest energy from incoming signals.

[0296] It will however be appreciated that the energy harvesting circuitry 331-1 may alternatively not form part of the transceiver circuit 331, but instead is its own module. For example, this may be the case when the energy to be harvested does not originate from signals transmitted to the IoT device 3-1. By way of example only, the IoT device 3-1 may harvest energy from solar cells such as dye-sensitised solar cells (DSSCs).

[0297] The transceiver circuit 331 also has modulation circuitry 331-2 which modulates an incoming unmodulated carrier signal to the IoT device 3-1 to produce the modulated backscatter signal to be reflected from the IoT device 3-1 for receipt by another device. For example, the modulation circuitry 331-2 may be configured modulate an incoming RF signal to the IoT device 3-1 by altering the impedance or reflectivity of the IoT device 3-1 in response to receiving that incoming RF signal. The modulation circuitry 331-2 may be configured to modulate the incoming signal to encode data provided from one or more data sources 332. Typically, for example, the IoT device 3-1 may comprise a data source 332 in the form of a sensor (e.g., an optical, temperature, position sensor or the like) for providing measurement data or a sensor alert, may comprise a data source 332 in the form of a stored or hardwired parameter such as a device or device type identifier, and / or may comprise one or more other sources of data.

[0298] In this example, the transceiver circuit 331 may also have a signal amplifier 331-3 (which may utilise energy harvested by the energy harvesting circuitry 331-1) for amplifying any modulated backscattered signal to be reflected by the IoT device 3-1 for receipt at another device.

[0299] In this example, the IoT device 3-1 also has a controller 337 to control the overall operation of the IoT device 3-1. The controller 337 is associated with a memory 339 and is coupled to the transceiver circuit 331. Although not necessarily required for its operation, the IoT device 3-1 might, of course, have all the usual functionality of a more conventional UE (e.g., a user interface 335, such as a touch screen / keypad / microphone / speaker and / or the like for, allowing direct control by and interaction with a user) and this may be provided by any one or any combination of hardware, software, and firmware, as appropriate. Software may be pre-installed in the memory 339 and / or may be downloaded via the communication system or from a removable data storage device (RMD), for example.

[0300] The controller 337 is configured to control overall operation of the IoT device 3-1 by, in this example, program instructions or software instructions stored within memory 339. As shown, these software instructions include, among other things, an operating system 341, and a communication control module 343.

[0301] The communication control module 343 is operable to control the communication between the IoT device 3-1, a RAN node 5-1, and / or an assisting node 5-2. The communication control module 343 may, for example, be configured for the overall handling of communication via associated physical channels (e.g., via a physical D2R channel (PDRCH), random access channel (RACH), and / or a physical R2D channel (PRDCH)).

[0302] It will be appreciated that the communication control module 343 may include a number of sub-modules ('layers' or 'entities') to support specific functionalities. For example, the communication control module 343 may include sub-modules corresponding to the layers of a dedicated ambient IoT device protocol stack for controlling functions associated with those layers.

[0303] The communication control module 343 is configured, in particular, to control the IoT device's communication, where applicable, in accordance with any of the methods described herein.

[0304] <RAN node> 　　Fig. 13 is a simplified block schematic illustrating the main components of a RAN node 5-1 (e.g., a base station / IoT reader device) for implementation in the communication system 1. It will be appreciated that the RAN node 5-1 may be configured to operate as an A-IoT device reader in the communication system 1.

[0305] As shown, the RAN node 5-1 has a transceiver circuit 51 for transmitting signals to and for receiving signals from the communication devices (such as UEs 3-2; 3-3, IoT devices 3-1, and possibly assisting or intermediate devices 5-2) via one or more antenna 53 (e.g., a single or multi-panel antenna array / massive antenna), and a core network interface 55 for transmitting signals to and for receiving signals from network nodes in the core network 7. Although not shown, the base station 5-1 may also be coupled to other base stations via an appropriate interface (e.g., the so-called 'X2' interface in LTE or the 'Xn' interface in NR). The RAN node 5-1 has a controller 57 to control the operation of the base station 5-1. The controller 57 is associated with a memory 59. Software may be pre-installed in the memory 59 and / or may be downloaded via the communication system 1 or from a removable data storage device (RMD), for example. The controller 57 is configured to control the overall operation of the base station 5-1 by, in this example, program instructions or software instructions stored within memory 59.

[0306] As shown, these software instructions include, among other things, an operating system 61, and a communication control module 63.

[0307] The communication control module 63 is operable to control the communication between the RAN node 5-1 and UEs 3 and other network entities (e.g., core network nodes) that communicate with the base station 5. The communication control module 63 is configured for the overall control of the reception and decoding of uplink communication, via associated uplink channels (e.g., via a physical uplink control channel (PUCCH), a random-access channel (RACH), and / or a physical uplink shared channel (PUSCH)) including both dynamic and semi-static signalling (e.g., SRS), and modulated backscattered communication in accordance with ambient IoT (where applicable). The communication control module 63 is also configured for the overall control of the transmission of downlink communication including downlink communication via associated downlink channels (e.g., via a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH)) including both dynamic and semi-persistent scheduling (e.g., SPS), and downlink communication of an unmodulated carrier signal in accordance with ambient IoT (where applicable). The communication control module 63 is responsible, for example: for determining where to configure the UE 3 to monitor for downlink control information (e.g., the location of search spaces, CORESETs, and associated PDCCH candidates to monitor); for determining the resources to be scheduled for UE transmission / reception of UL / DL communication (including interleaved resources and resources subject to frequency hopping); for managing frequency hopping at the base station side; for configuring slots / symbols appropriately (e.g., for UL, DL or full duplex communication, or the like); for configuring bandwidth parts for the UE 3; for providing related configuration signalling to a UE 3; and the like.

[0308] Where the RAN node 5-1 is configured to operate as an A-IoT device reader the communication control module 63 is operable to control the communication between the IoT device 3-1 and the RAN node 5-1, for example, via the associated physical channels (e.g., via a physical D2R channel (PDRCH), random access channel (RACH), and / or a physical R2D channel (PRDCH)) including both dynamic and semi-static signalling.

[0309] It will be appreciated that the communication control module 63 may include a number of sub-modules ('layers' or 'entities') to support specific functionalities. By way of example only the communication control module 63 may include sub-modules corresponding to the layers of a conventional protocol stack (PHY, MAC, RRC, RLC, PDCP etc.). Moreover, where the RAN node 5-1 is configured to operate as an A-IoT device reader, the communication control module 63 may include, sub-modules corresponding to the layers of a dedicated ambient IoT device protocol stack for controlling functions associated with those layers.

[0310] The communication control module 63 is configured in particular, to control the base station's communication, in accordance with any of the methods described herein.

[0311] <Assisting (or intermediate) node> 　　Fig. 14 is a simplified block schematic illustrating the main components of an example of an assisting (or intermediate) node 5-2 for possible implementation in the communication system 1.

[0312] As shown, the assisting node 5-2 may comprise a UE (such as, or similar to, UE 3-2; 3-3), an IAB node, a repeater, or the like, which is capable of ambient IoT operation. In this scenario, the assisting node 5-2 has a transceiver circuit 151 that is operable to transmit signals to and to receive signals from a UE 3 (such as an ambient IoT device) via one or more antenna 153 (e.g., comprising one or more antenna elements), and a RAN interface 155 for transmitting signals to and for receiving signals from the RAN node 5-1 (which may also be over the air via the antenna 153, or via a different antenna).

[0313] The assisting node 5-2 has a controller 157 to control the operation of the assisting node 5-2. The controller 157 is associated with a memory 159 and is coupled to the transceiver circuit 151. Although not necessarily required for its operation, the assisting node 5-2 might, of course, have other functionality (e.g., a user interface, such as a touch screen / keypad / microphone / speaker and / or the like for, allowing direct control by and interaction with a user) and this may be provided by any one or any combination of hardware, software, and firmware, as appropriate. Software may be pre-installed in the memory 159 and / or may be downloaded via the communication system or from a removable data storage device (RMD), for example.

[0314] The controller 157 is configured to control overall operation of the UE 3 by, in this example, program instructions or software instructions stored within memory 159. As shown, these software instructions include, among other things, an operating system 161, and a communication control module 163.

[0315] The communication control module 163 is operable to control the communication between the assisting node 5-2, the RAN node 5-1, and any IoT devices (including the ambient IoT device 3-1). The communication control module 163 is configured, in particular, for the overall handling of communication with the RAN node 5-1. For example, where the intermediate / assisting node 5-2 is a UE (or at least operates like a UE in its communication with the RAN node 5-1) this uplink communication may be via associated uplink channels (e.g., via a physical uplink control channel (PUCCH), random access channel (RACH), and / or a physical uplink shared channel (PUSCH)) including both dynamic and semi-static signalling (e.g., SRS). The communication control module 163 is also configured for the overall handling of receipt of downlink communication from the RAN node 5-1. For example, where the intermediate / assisting node 5-2 is a UE (or at least operates like a UE in its communication with the RAN node 5-1) this downlink communication may be via associated downlink channels (e.g., of DCI via a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH)) including both dynamic and semi-persistent scheduling (e.g., SPS). It will, nevertheless, be appreciated that where the assisting node 5-2 is a device other than a UE (e.g., an IAB or dedicated relay) then the communication control module 163 will be configured to communicate with the RAN node 5-1 using an appropriate corresponding signalling protocol for doing so.

[0316] The communication control module 163 is also responsible for appropriate ambient IoT related communication including, for example, reception of modulated backscattered communication from an ambient IoT device (where applicable) and / or downlink communication of an unmodulated carrier signal in accordance with ambient IoT (where applicable).

[0317] It will be appreciated that the communication control module 163 may include a number of sub-modules ('layers' or 'entities') to support specific functionalities. By way of example only the communication control module 163 may include sub-modules corresponding to the layers of a conventional protocol stack (PHY, MAC, RRC, RLC, PDCP etc.). Moreover, the communication control module 63 may include, sub-modules corresponding to the layers of a dedicated ambient IoT device protocol stack for controlling functions associated with those layers.

[0318] The communication control module 163 is configured, in particular, to control the assisting node's communication, in accordance with any of the methods described herein.

[0319] <Modifications and Alternatives> 　　Detailed examples been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above examples whilst still benefiting from the enhancements embodied therein.

[0320] It will be appreciated that description of features of and actions performed by a RAN node (or a RAN operating as an A-IoT reader device), apply equally to distributed type RAN nodes as to non-distributed type RAN nodes.

[0321] It will also be appreciated that whilst information elements having specific names may have been described, differently named information elements but having a similar purpose may be used.

[0322] In the above description the UE, A-IoT device, intermediate / assisting node, and the RAN node are described for ease of understanding as having a number of discrete functional components or modules. Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosed enhancements, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities.

[0323] In the above examples, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE or base station as a signal over a computer network, or on a recording medium. Further, the functionality performed by part, or all, of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE or the base station in order to update their functionalities.

[0324] Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and / or timers; and / or the like. Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0325] The User Equipment (or "UE," "mobile station," "mobile device" or "wireless device") in the present disclosure is an entity connected to a network via a wireless interface.

[0326] It should be noted that the present disclosure is not limited to a dedicated communication device and can be applied to any device having a communication function as explained in the following paragraphs.

[0327] The terms "User Equipment" or "UE" (as the term is used by 3GPP), "mobile station", "mobile device", and "wireless device" are generally intended to be synonymous with one another, and include standalone mobile stations, such as terminals, cell phones, smart phones, tablets, cellular IoT devices, IoT devices, and machinery. It will be appreciated that the terms "mobile station" and "mobile device" also encompass devices that remain stationary for an extended period of time.

[0328] A UE may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; moulds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.).

[0329] A UE may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motorcycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).

[0330] A UE may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).

[0331] A UE may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).

[0332] A UE may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).

[0333] A UE may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyser, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like.

[0334] A UE may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).

[0335] A UE may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)," using a variety of wired and / or wireless communication technologies.

[0336] Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for an extended period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g., vehicles) or attached to animals or persons to be monitored / tracked.

[0337] It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communication system for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0338] It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices. It will be appreciated that a UE may support one or more IoT or MTC applications. Some examples of MTC applications are listed in the following table. This list is not exhaustive and is intended to be indicative of some examples of machine type communication applications.

[0339] Further, the above-described UE categories are merely examples of applications of the technical ideas and exemplary examples described in the present document. Needless to say, these technical ideas and examples are not limited to the above-described UE and various modifications can be made thereto.

[0340] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0341] For example, the whole or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes. 　　(Supplementary note 1) 　　A method performed by an Ambient-Internet of Things, A-IoT, device, the method comprising: 　　receiving, from an intermediate node, resource allocation information for the IoT device, wherein the resource allocation information is determined by a Radio Access Network, RAN, node and is transmitted from the RAN node to the intermediate node; and 　　transmitting data using one or more resource(s) configured by the resource allocation information. 　　(Supplementary note 2) 　　The method of supplementary note 1, wherein the intermediate node is a node acting as an A-IoT device reader. 　　(Supplementary note 3) 　　The method of supplementary note 1 or 2, wherein the resource allocation information is transmitted from the RAN node to the intermediate node via Uu RRC signaling. 　　(Supplementary note 4) 　　The method of any one of supplementary notes 1-3, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, following expiration of a timer. 　　(Supplementary note 5) 　　The method of any one of supplementary notes 1-4, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, based on a state of the intermediate node. 　　(Supplementary note 6) 　　The method of any one of supplementary notes 1-5, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, until a time point where the RAN node transmits a follow-up message. 　　(Supplementary note 7) 　　The method of any one of supplementary notes 1-6, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, based on a number of resources configured by the resource allocation information. 　　(Supplementary note 8) 　　The method of any one of supplementary notes 1-7, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, for a specific area scope. 　　(Supplementary note 9) 　　The method of any one of supplementary notes 1-8, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, for one or more specific types of the terminal device as an A-IoT device, or for one or more specific groups of terminal devices as A-IoT devices. 　　(Supplementary note 10) 　　The method of any one of supplementary notes 1-9, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, for use in one or more specific communication types. 　　(Supplementary note 11) 　　The method of any one of supplementary notes 1-10, wherein the one or more resource(s) configured by the resource allocation information is automatically activated upon reception of the resource allocation information by the intermediate node from the RAN node. 　　(Supplementary note 12) 　　The method of any one of supplementary notes 1-11, wherein an indication of any one of an activation, deactivation, or cancellation is transmitted from the RAN node to the intermediate node, in order to activate, deactivate, or cancel the one or more resource(s) configured by the resource allocation information. 　　(Supplementary note 13) 　　The method of supplementary note 12, wherein the indication is transmitted from the RAN node to the intermediate node via a Media Access Control, MAC, Control Element, CE, or Downlink Control Information, DCI. 　　(Supplementary note 14) 　　The method of any one of supplementary notes 1-13, wherein, the RAN node is a Target RAN node, and the resource allocation information is transmitted from the Target RAN node to the intermediate node via a Source RAN node. 　　(Supplementary note 15) 　　The method of any one of supplementary notes 1-14, wherein the intermediate node switches from an RRC CONNECTED state to an RRC IDLE state or an RRC INACTIVE state, after receiving the resource allocation information. 　　(Supplementary note 16) 　　The method of supplementary notes 15, wherein the intermediate node switches to an RRC CONNECTED state after receiving the data from the terminal device. 　　(Supplementary note 17) 　　The method of any one of supplementary notes 1-16, wherein the resource allocation information is a power control configuration. 　　(Supplementary note 18) 　　The method of supplementary note 17, wherein the intermediate node is a first intermediate node acting as a Tx intermediate node, and wherein the terminal device transmits a measurement report to a second intermediate node acting as a Rx intermediate node, after receiving the resource allocation information. 　　(Supplementary note 19) 　　A method performed by an intermediate node, the method comprising: 　　receiving, from a Radio Access Network, RAN, node, resource allocation information for an Ambient-Internet of Things, A-IoT, device, wherein the resource allocation information is determined by the RAN node; and 　　transmitting the resource allocation information to the A-IoT device. 　　(Supplementary note 20) 　　A method performed by a Radio Access Network, RAN, node, the method comprising: 　　determining resource allocation information for an Ambient-Internet of Things, A-IoT, device; and 　　transmitting the resource allocation information to an intermediate node, wherein the resource allocation information is transmitted from the intermediate node to the A-IoT device.

[0342] This application is based upon and claims the benefit of priority from Great Britain Patent Application No. 2416357.8, filed on November 6, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0343] 1 COMMUNICATION SYSTEM 3 USER EQUIPMENT 5 BASE STATION 7 CORE NETWORK 9 CELL 10 CONTROL PLANE FUNCTIONS 11 USER PLANE FUNCTIONS 40 EXTERNAL DATA NETWORK 31 TRANSCEIVER CIRCUIT 33 ANTENNA 35 USER INTERFACE 37 CONTROLLER 39 MEMORY 41 OPERATING SYSTEM 43 COMMUNICATIONS CONTROL MODULE 331 TRANSCEIVER CIRCUIT 331-1 ENERGY HARVESTING CIRCUITRY 331-2 MODULATION CIRCUITRY 331-3 SIGNAL AMPLIFIER 332 DATA SOURCE 333 ANTENNA 335 USER INTERFACE 337 CONTROLLER 338 PROCESSING CIRCUITRY 339 MEMORY 341 OPERATING SYSTEM 343 COMMUNICATIONS CONTROL MODULE 345 DATA BUFFER 51 TRANSCEIVER CIRCUIT 53 ANTENNA 55 CORE NETWORK INTERFACE 57 CONTROLLER 59 MEMORY 61 OPERATING SYSTEM 63 COMMUNICATIONS CONTROL MODULE 151 TRANSCEIVER CIRCUIT 153 ANTENNA 155 RAN INTERFACE 157 CONTROLLER 159 MEMORY 161 OPERATING SYSTEM 163 COMMUNICATIONS CONTROL MODULE

Claims

1. A method performed by an Ambient-Internet of Things, A-IoT, device, the method comprising: 　　receiving, from an intermediate node, resource allocation information for the IoT device, wherein the resource allocation information is determined by a Radio Access Network, RAN, node and is transmitted from the RAN node to the intermediate node; and 　　transmitting data using one or more resource(s) configured by the resource allocation information.

2. The method of claim 1, wherein the intermediate node is a node acting as an A-IoT device reader.

3. The method of claim 1 or 2, wherein the resource allocation information is transmitted from the RAN node to the intermediate node via Uu RRC signaling.

4. The method of any one of claims 1-3, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, following expiration of a timer.

5. The method of any one of claims 1-4, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, based on a state of the intermediate node.

6. The method of any one of claims 1-5, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, until a time point where the RAN node transmits a follow-up message.

7. The method of any one of claims 1-6, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, based on a number of resources configured by the resource allocation information.

8. The method of any one of claims 1-7, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, for a specific area scope.

9. The method of any one of claims 1-8, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, for one or more specific types of the terminal device as an A-IoT device, or for one or more specific groups of terminal devices as A-IoT devices.

10. The method of any one of claims 1-9, wherein the one or more resource(s) configured by the resource allocation information is treated as valid, by the intermediate node, for use in one or more specific communication types.

11. The method of any one of claims 1-10, wherein the one or more resource(s) configured by the resource allocation information is automatically activated upon reception of the resource allocation information by the intermediate node from the RAN node.

12. The method of any one of claims 1-11, wherein an indication of any one of an activation, deactivation, or cancellation is transmitted from the RAN node to the intermediate node, in order to activate, deactivate, or cancel the one or more resource(s) configured by the resource allocation information.

13. The method of claim 12, wherein the indication is transmitted from the RAN node to the intermediate node via a Media Access Control, MAC, Control Element, CE, or Downlink Control Information, DCI.

14. The method of any one of claims 1-13, wherein, the RAN node is a Target RAN node, and the resource allocation information is transmitted from the Target RAN node to the intermediate node via a Source RAN node.

15. The method of any one of claims 1-14, wherein the intermediate node switches from an RRC CONNECTED state to an RRC IDLE state or an RRC INACTIVE state, after receiving the resource allocation information.

16. The method of claims 15, wherein the intermediate node switches to an RRC CONNECTED state after receiving the data from the terminal device.

17. The method of any one of claims 1-16, wherein the resource allocation information is a power control configuration.

18. The method of claim 17, wherein the intermediate node is a first intermediate node acting as a Tx intermediate node, and wherein the terminal device transmits a measurement report to a second intermediate node acting as a Rx intermediate node, after receiving the resource allocation information.

19. A method performed by an intermediate node, the method comprising: 　　receiving, from a Radio Access Network, RAN, node, resource allocation information for an Ambient-Internet of Things, A-IoT, device, wherein the resource allocation information is determined by the RAN node; and 　　transmitting the resource allocation information to the A-IoT device.

20. A method performed by a Radio Access Network, RAN, node, the method comprising: 　　determining resource allocation information for an Ambient-Internet of Things, A-IoT, device; and 　　transmitting the resource allocation information to an intermediate node, wherein the resource allocation information is transmitted from the intermediate node to the A-IoT device.

Images