Carrier-wave provision

Abstract

Methods, apparatus and systems for provision of a carrier wave (eg., in a communication network) are disclosed.

Description

[0001] Carrier-wave provision

[0002] TECHNOLOGICAL FIELD

[0003] The present disclosure is related to but not limited to communication networks as defined by the 3GPP standard, such as the 6G standard. The disclosure particularly relates to a communication with so called tags, such as Ambient Internet of Things, AIoT, devices, and in particular configurations of such a communication.

[0004] BACKGROUND

[0005] The number of loT connections has been growing rapidly in recent years and is predicted to be hundreds of billions by 2030. With more and more devices expected to be interconnected for improving production efficiency and increasing comforts of life, it demands further reduction of size, cost, and power consumption for loT devices.

[0006] A critical issue with existing 3GPP technologies for the target use cases is the capability of energy harvesting considering limited device size. Cellular devices usually consume tens or even hundreds of milliwatts power for transceiver processing. Taking NB-IoT module for example, the typical current consumption for receive processing is about 60mA with supply voltage higher than 3.1V, while 70mA for transmitting processing at OdBm transmit power. Furthermore, the output power provided by typical RF energy harvester is mostly below 1 milliwatt, considering the small size of a few square centimeters for practical devices. Since the available RF power is far less than the consumed power, it is impractical to power cellular devices directly by energy harvesting in most cases.

[0007] In a new approach, so called tags in the form of Ambient loT devices are used. An AIoT device may harness energy from a wireless signal called carrier wave (CW) it receives. The AIoT device may be both charged by the carrier wave and may further be activated (e.g., in a charged state) in order to reflect a signal (e.g., the carrier wave) while encoding at least one piece of information into the carrier wave, for instance at least an ID of the AIoT device.

[0008] A typical system architecture around an AIoT device may consist of: 1) The tag device (e.g., the AIoT tag apparatus) which harnesses energy (e.g., over a range of frequencies, e.g., from a carrier wave) and listens for activation signals. Once activated, it may reflect and / or modulate the carrier wave in a predefined way. 2) An activator, i.e. a user equipment or network device, that provides the CW and sends an activation signal targeted at waking up the AIoT device. Once both the AIoT device is charged by the activator’s CW and an activation signal is received from the activator, the AIoT device reflects the CW in a predefined way. 3) A reader, i.e. a user equipment or network device that listens and detects the reflected and / or modulated CW and for instance extracts information from it The reader may or may not be collocated with the activator. SUMMARY OF SOME EXEMPLARY EMBODIMENTS

[0009] It has been recognized that a carrier wave needs to have a sufficient power at the location of an AIoT device in order to be able to charge the device and / or for the CW to be reflected far enough by the AIoT device to reach a reader. As a consequence, an activator supplying the carrier wave may need to be positioned in proximity of the AIoT device and / or emit a strong carrier wave in order to be able to interact with the AIoT device. This may limit AIoT use cases. It has further been recognized that an activation of an already charged AIoT device may be achieved with much lower signal strength compared to the carrier wave. It has finally been recognized that it may be advantageous to create a split in the AIoT architecture wherein a CW provider provides a carrier wave to the AIoT device and an activator provides activation signals to the AIoT device wherein activator and CW provider are different from one another.

[0010] It is thus, inter alia, an object of the disclosure to enable an activator of an AIoT system to interact with an AIoT device wherein the activator does not itself provide the AIoT device with a carrier wave.

[0011] According to a first example aspect, a method is disclosed (e.g., performed and / or controlled by a first apparatus, e.g. network node or UE) comprising: sending (e.g., providing, transmitting] a carrier wave, CW, support request to a second apparatus (e.g., CW coordinating node or CW provider, not an AIoT device) for requesting provision of at least one CW transmission to at least one tag apparatus (e.g., AIoT device) (e.g., at least one of the CW transmission may be devoid of an activation signal, the CW transmission may provide (e.g., only) energy, the CW transmission may carry no information content, the CW transmission may correspond to a (e.g., pure and / or unmodulated) sinusoid, the CW transmission may correspond to or may reach multiple tag apparatuses and / or the CW transmission may be recipient-unspecific).

[0012] This method may for instance be performed and / or controlled by an apparatus, for instance a server. Alternatively, this method may be performed and / or controlled by more than one apparatus, for instance a server cloud comprising at least two servers. Alternatively, the method may for instance be performed and / or controlled by an electronic device, e.g. a node in a communication system and / or by a terminal device, e.g., a user equipment (UE). For instance, the method may be performed and / or controlled by using at least one processor of the electronic device.

[0013] According to a further example aspect, a computer program is disclosed, the computer program when executed by a processor causing an apparatus, for instance a server, a network node or a terminal device, e.g., a UE, to perform and / or control the actions of the method according to the first example aspect.

[0014] The computer program may be stored on computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read- (e.g., Only] Memory [ROM] or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0015] According to a further example aspect, an apparatus is disclosed, configured to perform and / or control or comprising respective means for performing and / or controlling the method according to the first example aspect.

[0016] The means of the apparatus can be implemented in hardware and / or software. They may comprise for instance at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. Alternatively, they could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0017] The above-disclosed apparatus according to any aspect may be a module or a component for a device, for example a chip. Alternatively, the disclosed apparatus according to any aspect may be a device, for instance a server or server cloud. The disclosed apparatus according to any aspect may comprise (e.g., only) the disclosed components, for instance means, processor, memory, or may further comprise one or more additional components.

[0018] A terminal device, e.g, a user equipment (UE) may for instance correspond to a mobile device such as for example a mobile phone, tablet, smartwatch, a laptop, a Personal Digital Assistant (PDA) device, a wearable, an Internet-of-Things (I0T) device, an IIOT (Industrial I0T) device, a vehicle and / or combinations thereof. Such a user equipment may also be referred to as user device.

[0019] A network node may correspond to a component of a communication network such as for instance a Base Transceiver Station (BTS), a nodeB, an evolved node B (eNB), a Next Generation NodeB (gNB), a distributed unit (DU), a central unit (CU) and / or combinations thereof.

[0020] An apparatus performing and / or controlling the method according to the first example aspect may be an activator. The activator may be configured to activate at least one tag apparatus. For instance, the activator may be configured to determine whether and / or recognize that a tag apparatus to be activated by the apparatus is positioned in a way (e.g., further away than a pre-defined distance) that prevents the activator from providing a carrier wave to said tag apparatus. In this case, the activator may perform the method in order to activate the tag apparatus nonetheless.

[0021] A carrier wave support request, CW support request, may be configured to request provision of at least one CW transmission to at least one tag apparatus. The tag apparatus may in particular be an AIoT device. For instance, there may be different categories of AIoT devices.

[0022] For instance, an AIoT device and / or tag apparatus may be of a category 1. A category 1 tag apparatus may have a peak power consumption of about 1 pW (e.g., + / - 10%), may comprise an energy storage, may have an initial sampling frequency offset (SFO) of up to 10X ppm, may have neither DL nor UL amplification in the device. A category 1 tag apparatus’ uplink (UL) transmission may be backscattered on a carrier wave provided externally.

[0023] An AIoT device and / or tag apparatus may be category 2a. A category 2a tag apparatus may have less or equal to a few hundred pW peak power consumption, may have an energy storage, may have an initial sampling frequency offset (SFO) up to 10X ppm, may have both DL and / or UL amplification in the device. A category 2a tag apparatus’ UL transmission may be backscattered on a carrier wave provided externally.

[0024] A category 2b tag apparatus may have equal or less than a few hundred pW peak power consumption, may have an energy storage, may have an initial sampling frequency offset (SFO) up to 10X ppm, may have both DL and / or UL amplification in the device. A category 2b tag apparatus’ UL transmission may be generated internally by the tag apparatus.

[0025] A tag apparatus according to the present disclosure may in particular be either category 1 or category 2 a but not 2b. Alternatively, a tag apparatus according to the present disclosure may further also be of category 2b.

[0026] The CW support request may be sent, provided and / or transmitted, for instance by means of at least one (e.g., wireless) communication link.

[0027] The second apparatus may for instance be a terminal device or a network node. The second apparatus may for instance correspond to a CW coordinating node and / or to a CW provider. A CW coordinating node may not itself provide the requested CW transmission but may forward the CW support request or may send a further CW support request based on the CW support request to a CW provider. The CW provider may provide the CW transmission to the at least one tag apparatus.

[0028] A CW transmission may for instance be free and / or devoid of an activation signal. For instance, the tag apparatus is not activated by a CW transmission. Instead, the CW transmission may provide (e.g., only) energy to at least one tag apparatus. For instance, the CW transmission may provide no information content (unless perhaps a single bit depending on whether the CW transmission is active or not). In particular, the CW transmission may be unmodulated and / or a (e.g., pure) sinusoid signal of a single frequency. For instance, the CW transmission may reach multiple (e.g., at least 2, 3, 4, 5, 10, 20, 50, 100, 500 or 1000) tag apparatuses. For instance, the CW transmission may be specific to at least one tagapparatus (e.g., within a coverage area of the CW transmission), for instance by a spectrum of the CW transmission and / or by a spatial area targeted by the CW transmission. For instance, the CW transmission may be recipient-unspecific. The CW transmission may be sent in a uniform spatial signal strength distribution and / or in an anisotropic manner, for instance shaped by at least one antenna of the CW provider. The CW transmission may for instance be beam-formed.

[0029] According to an embodiment of the first example aspect, the CW support request is configured to indicate at least one CW property of a CW transmission to be provided by the CW provider.

[0030] By indicating at least one CW property, the CW support request may enable a recipient of the CW support request to derive the CW support property. For instance, the CW property may be comprised by (i.e., encoded into] the CW support request. Additionally or alternatively, the CW property may be indicated by an indication which may in itself not be fully informative of the CW property. For instance, the CW support request may comprise an information element which may [e.g., only] comprise a few [e.g., less than or equal to 1, 2, 3, 4, 5, 6, 7, or 8] bits. A receiver of the CW support request may be able to derive the indicated CW property, for instance by using at least one information source such as a table which may be internally stored in a receiver of the CW support request

[0031] The CW property may specify at least one property of the CW transmission requested by means of the CW support request.

[0032] By indicating at least one CW property in the CW support request, it is possible to match a need for CW transmission of a requesting entity, in particular a first apparatus performing the method according to the first example aspect, to a provided CW transmission by a CW provider.

[0033] According to an embodiment of the first example aspect, the CW property comprises at least one of: a starting time of the CW transmission, an ending time of the CW transmission, a duration of the CW transmission, a periodic pattern of the CW transmission [e.g., to account for the activator future AIoT sessions], a spectrum of the CW transmission [UL or DL], a CW transmission identifier, a CW provider identifier, a tag apparatus location, or a tag apparatus identifier.

[0034] The CW property specify or be at least related to a property of the CW transmission. For instance, such a property may relate to a timing of the CW transmission. For instance, the CW transmission may have a starting time from which on the CW transmission starts. The requesting entity may be able to specify from when on the CW transmission is required. The CW transmission may have an associated ending time. For instance, the requesting entity may be able to specify until when the CW transmission is required. For instance, the CW transmission may have a duration, for instance a minimum duration and / or a maximum duration, during which the CW transmission is kept active. The requesting entity may thus be able to specify for how long it requires the CW transmission. The CW property may also relate to a periodic pattern of the CW transmission. For instance, CW transmission maybe required at pre-defined CW transmission times wherein between CW transmission times, a CW transmission may be paused. A CW property may indicate a pattern in time in which the CW transmission is required. For instance, a periodic pattern of CW transmissions may configure CW transmissions for future AIoT sessions (e.g., already known to or planned by the requesting entity].

[0035] The CW property may relate to a spectrum of the CW transmission, for instance uplink, UL, and / or downlink, DL, spectrum and / or a frequency region and / or a specific [e.g., single] frequency.

[0036] The CW property may relate to a (e.g., required] receive or transmit signal strength or power of the CW transmission.

[0037] Multiple CW properties may be indicated by a CW support request, for instance, multiple (e.g., different] spectra for respective multiple (e.g., different] CW transmissions.

[0038] The CW property may further relate to a CW transmission identifier. For instance, the identifier may be defined by a requesting entity and may be useful for future interactions between the requesting entity (e.g., performing the method according to the first example aspect] and the second apparatus. For instance, the requesting entity may be able to make reference to a previously transmitted CW support request by means of the CW transmission identifier, e.g., to terminate a CW transmission and / or to request an identical CW transmission to the one with the indicated CW transmission identifier.

[0039] The CW property may be related to a CW provider identifier. For instance, the requesting entity (e.g., performing the method according to the first example aspect] may be informed about which CW provider may be (e.g., best] suitable for a CW transmission it requests. By transmitting the CW provider identifier, a quicker identification and / or a reproducible activation of the desired CW transmission may be achieved, in particular if the CW support request is not directed to a desired CW provider directly but by intermediary of a CW coordinating node, for instance.

[0040] The CW property may further be related to a tag apparatus location and / or tag apparatus identifier. In some cases, the requesting entity (e.g., performing the method according to the first example aspect] desires to provide a CW transmission to one or more particular tag apparatuses]. By providing an indication of which tag apparatus and / or in which area of tag apparatuses to target, the second apparatus may be enabled to provide (e.g., by itself or by means of another apparatus, for instance a CW provider] an applicable CW transmission to the tag apparatuses] and / or select an appropriate CW provider to this end. According to an embodiment of the first example aspect: the first apparatus is a terminal device, or the first apparatus is a network node.

[0041] The requesting entity (e.g., performing the method according to the first example aspect) may be referred to a first apparatus.

[0042] The first apparatus may be a terminal device, in particular a UE.

[0043] For instance, the first apparatus [a terminal device) may be positioned relatively to a given tag apparatus in a way that prevents CW transmission provision (e.g., due to obstacles, an excessive distance, a required spectrum by the tag apparatus and / or combinations thereof). In such cases, the terminal device may transmit a CW support request to another apparatus (e.g., another terminal device and / or a network node) in order to request provision of a CW transmission to the tag apparatus. The first apparatus may still be able to activate the tag apparatus itself by direct signaling, e.g., by a (e.g., wireless) communication link to the tag apparatus.

[0044] Additionally or alternatively, the first apparatus may be network node.

[0045] It has been recognized that even if the first apparatus is not able to provide a CW transmission (e.g., of sufficient signal strength, in the correct spectrum, at a location of a tag apparatus), it may still be able to transmit an activating signal to the tag apparatus. The first apparatus may thus successfully interact with the tag apparatus, as long as the tag apparatus receives a CW transmission, e.g., from somewhere, e.g., from an apparatus different from the first apparatus.

[0046] In particular network nodes may often not be able to provide strong enough CW transmissions to tag apparatuses, e.g., tag apparatuses located within buildings or at a distance from the network node. At the same time, at least one other apparatus, in particular a terminal device, may be located within proximity of a tag apparatus and may be able to provide CW transmission, or at least one other apparatus, in particular a network node, may have the necessary output power and / or hardware capabilities, in particular antenna beamforming capabilities, to provide CW transmission.

[0047] According to an embodiment of the first example aspect, the second apparatus is at least one of: a CW coordinating node (e.g., does not itself provide CW transmission), a CW coordinating node, wherein the CW coordinating node is a network node, a CW coordinating node, wherein the CW coordinating node is a user equipment, UE, the CW provider (e.g., provides CW transmission itself), the CW provider, wherein the CW provider is a network node, or the CW provider, wherein the CW provider is a terminal device. The second apparatus, to which the CW support request is transmitted, may correspond to a CW coordinating node, in particular for the CW support request and / or for multiple (e.g., all] CW support requests.

[0048] A CW coordinating node may for instance be configured to forward the CW support request, e.g., to a CW provider or to another CW coordinating node. The CW coordinating node may for instance alter the CW support request and transmit an altered CW support request to another entity. For instance, the CW coordinating node may not provide (e.g., any] CW transmission and / or may at least not provide the requested CW transmission requested by means of the CW support request. For instance, the CW coordinating node may select a CW provider (e.g., for a given CW support request], for instance based on at least one CW property of the CW support request.

[0049] The second apparatus may be a CW provider, in particular for the CW support request and / or for multiple (e.g., all] CW support requests. For instance, the CW provider may provide (e.g., any requested] CW transmission and / or may at least provide the requested CW transmission requested by means of the CW support request.

[0050] A CW provider for a first CW support request may act as a CW coordinating node for another, second CW support request. For instance, the second apparatus may decide (e.g., based on a received CW support request] that it will act as the CW provider and provide the CW transmission requested by means of the CW support request. Additionally or alternatively, second apparatus may decide (e.g., based on a received CW support request] that it will not act as the CW provider itself and instead may act as a CW coordinating node and provide the CW support request to another apparatus which may act as a CW provider.

[0051] The (first apparatus performing the] method according to the first example aspect may be agnostic as to whether the second apparatus is a CW provider or a CW coordinating node. Alternatively, the (first apparatus performing the] method according to the first example aspect may be aware of whether the second apparatus is a CW provider or a CW coordinating node.

[0052] For instance, the CW support request may at least in part dependent on (or, alternatively, independent from] whether the second apparatus is a CW coordinating node or a CW provider.

[0053] The CW coordinating node and / or the CW provider may respectively correspond to a terminal device or to a network node. For instance, a CW coordinating node may correspond to a network node while the CW provider may correspond to a terminal device.

[0054] According to an embodiment of the first example aspect, the tag apparatus is an ambient internet of things, AIoT, apparatus. The tag apparatus may for instance correspond to an ambient internet of things, AIoT, apparatus. For instance, the tag apparatus may be a category 1 or 2 a AIoT apparatus.

[0055] An operation of the tag apparatus may therefore be dependent on a CW transmission provided by another entity, in particular a CW provider. The tag apparatus may be configured to be activatable by an activation signal, for instance transmitted by the first apparatus performing and / or controlling the method according to the first example aspect. For instance, an energy storage inside the tag apparatus may be charged by means of the CW transmission. The tag apparatus may be inactive and / or in-activatable (i.e., not be activatable] before it is charged by means of a CW transmission. The tag apparatus may be configured to backscatter, reflect and / or modulate a CW transmission, possibly depending on whether an activation signal has been received or not.

[0056] According to an embodiment of the first example aspect, at least one of: the CW support request is provided as [e.g., activator [first apparatus performing and / or controlling the method according to the first example aspect] is a terminal device (e.g., UE], second apparatus is a network node (e.g., gNB]] an uplink, UL, signal, the CW support request is provided as an UL signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non-Access Stratum, NAS, signaling, the CW support request is provided as (e.g., activator (first apparatus performing and / or controlling the method according to the first example aspect] is a terminal device (e.g., UE], second apparatus is a terminal device (e.g., UE]] at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information], a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request is provided as (e.g., activator (first apparatus performing and / or controlling the method according to the first example aspect] is a network node (e.g., gNB], second apparatus is a network node (e.g., gNB]] at least one of an Xn signaling, an Fl signaling, or a signaling over a fronthaul link (e.g., if the CW signal provider is a specific TRP], the CW support request is provided as (e.g., activator (first apparatus performing and / or controlling the method according to the first example aspect] is a network node (e.g., gNB], second apparatus is a terminal device (e.g., UE]] a downlink, DL, signal, or the CW support request is provided as a DL signal, wherein the DL signal is provided via at least one of a (e.g., specific] DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0057] The CW support request may be sent (e.g., transmitted and / or provided] by means of (e.g., wireless and / or wired) communication links between apparatuses. The means may depend on types of apparatuses involved.

[0058] For instance, the first apparatus performing the method according to the first example aspect, may correspond to a terminal device, e.g., a UE, and / or the second apparatus corresponds to a network node, e.g., a gNB or a network node hosting a Core Network, CN, function. For instance, in this constellation of apparatus types, but not only then, the CW support request may be provided as an uplink, UL, signal, in particular an UL signal of one or combinations of the following types. The UL signal may for instance correspond to an uplink scheduling request, UL, SR. Additionally or alternatively, the UL signal may for instance correspond to a Medium Access Control Control Element, MAC CE. Additionally or alternatively, the UL signal may for instance correspond to a Radio Resource Control, RRC, signaling. Additionally or alternatively, the UL signal may for instance correspond to a Non Access Stratum, NAS, signaling.

[0059] For instance, both the first apparatus performing the method according to the first example aspect and the second apparatus may correspond to a respective (e.g., mutually different) terminal device, e.g., a UE. For instance in this constellation of apparatus types, but not only then, the CW support request may be provided as one or combinations of the following types. The CW support request may be provided by means of a dedicated physical layer sequence, PHY sequence. Additionally or alternatively, the CW support request may be provided by means of a side link control information, SCI, in particular a specific field in, e.g., a 1ststage and / or a 2ndstage SCI information. Additionally or alternatively, the CW support request may be provided by means of a Side Link Medium Access Control Control Element, SL MAC CE and / or to sidelink an RRC signaling and / or a PC5 signaling.

[0060] For instance, both the first apparatus performing the method according to the first example aspect and the second apparatus may correspond to a respective (e.g., mutually different) network node, e.g., a gNB or a network node hosting a CN function. For instance in this constellation of apparatus types, but not only then, the CW support request may be provided as one or combinations of the following types. The CW support request may be provided by means of an Xn signaling. Additionally or alternatively, the CW support request may be provided by means of an Fl signaling. Additionally or alternatively, the CW support request may be provided by means of a signaling over a fronthaul link (e.g., if the CW provider is a specific Transmission Reception Point, TRP).

[0061] For instance, the first apparatus performing the method according to the first example aspect, may correspond to a network node, e.g., a gNB or a network node hosting a CN function, and / or the second apparatus corresponds to a terminal device, e.g., a UE. For instance in this constellation of apparatus types, but not only then, the CW support request may be provided as an uplink, DL, signal, in particular an DL signal of one or combinations of the following types. The DL signal may for instance correspond to a Downlink Control Information, DCL Additionally or alternatively, the DL signal may for instance correspond to a MAC CE. Additionally or alternatively, the DL signal may for instance correspond to an RRC signaling. Additionally or alternatively, the DL signal may for instance correspond to a MAC CE. Additionally or alternatively, the DL signal may for instance correspond to a NAS signaling.

[0062] According to an embodiment of the first example aspect, the method further comprises: obtaining a CW support response to the CW support request [e.g., ACK / NACK] from the second apparatus.

[0063] A CW support response may enable the requesting entity [e.g., first apparatus, e.g., performing the method according to the first example aspect] to be informed whether the CW support request was successful, e.g., whether it caused a requested CW transmission, or whether the CW support request failed. Additionally or alternatively, the CW support response may inform the requesting entity of a property of the CW transmission, a property [e.g., identifier] of the CW provider and / or combinations thereof.

[0064] According to an embodiment of the first example aspect, the CW support response is configured to indicate at least one of: a successful CW transmission, a failed CW transmission, a CW transmission starting time, a CW transmission ending time, a CW transmission duration, a minimum waiting time [e.g., before sending [e.g., by the first apparatus] an activation signal], a CW transmission identifier, or a CW provider identifier.

[0065] The CW support response may indicate a property [e.g., CW property] of the CW transmission, the CW provider and / or further information which may for instance be relevant to the requesting entity sending the CW support request. For instance, a [e.g., CW] property of the CW transmission may be an indication of a successful or a failed CW transmission. Additionally or alternatively, the CW support response may indicate a failed [no CW transmission] and / or successful [CW transmission provided] CW support request.

[0066] The CW support response may additionally or alternatively indicate at least one temporal property of the CW transmission, for instance a CW transmission starting time, ending time and / or duration. For instance, the requesting entity may be informed of a time during which it may interact with the at least one tag apparatus. The CW support response may additionally or alternatively indicate a (e.g., minimum] waiting time, e.g., between the CW support request and a subsequent sending of an activation signal.

[0067] The CW support response may additionally or alternatively indicate a CW transmission identifier, by which the requested and / or provided CW transmission may be identified, for instance uniquely, for instance to refer to (e.g., to deactivate] the CW transmission at a later stage. The CW support response may additionally or alternatively comprise an indication of a CW provider identifier (e.g., CW provider, e.g., different or identical to the second apparatus].

[0068] According to an embodiment of the first example aspect, the method further comprises: providing (e.g., in response to and / or after (a pre-defined time after] providing the CW request to the second apparatus] an activation signal to at least one of the at least one tag apparatus (AIoT device].

[0069] An activation signal may for instance be sent (e.g., transmitted and / or provided] to at least one tag apparatus. For instance, the activation signal may be provided by means of a (e.g., wireless] communication link.

[0070] The activation signal may for instance be different from a carrier wave transmission. In particular, the activation signal may be unsuitable to fulfil a function of a carrier wave. For instance, the activation signal may be transmitted over time period too short for a CW transmission, the activation signal may be variable in time, the activation signal may be in a spectrum which is unsuitable for a carrier wave, the activation signal may be below a minimum signal strength, in particular at a location of a tag apparatus, the activation signal may have a broad spectrum, e.g., caused by a modulation of a carrier frequency, the activation signal may carry at least one information, for instance an identifier of a tag apparatus and / or a command directed to a tag apparatus and / or combinations thereof.

[0071] An activation signal may target (e.g., only] one or more than one (e.g., at least 2, 3, 4, 5, 10, 20, 50, 100] tag devices.

[0072] According to an embodiment of the first example aspect, at least one of: the activation signal is configured to cause a backscatter response from the tag apparatus (e.g., to the first apparatus, the second apparatus or a third apparatus (reader]], the activation signal is specific to the tag apparatus (e.g., contains ID, matching frequency], the activation signal is sent during an ongoing (e.g., the requested] CW transmission, the activation signal indicates a (e.g., pre-defined] delay (e.g., waiting time] between a reception of the activation signal and an activation, or the activation signal is provided at least one of: in response to providing the CW support request, in response to obtaining a CW support response to the CW support request, or after a pre-defined time after providing the CW support request. The activation signal may be configured to cause a backscatter response from the (e.g., at least one or more] tag apparatus. The backscatter response may be at least partially based on a provided CW transmission. The tag apparatus may for instance backscatter the CW transmission on the condition of obtaining an activation signal. For instance, the tag apparatus may receive the activation signal while a CW transmission (e.g., the CW transmission requested by the CW support request] is active and may backscatter the CW transmission after (e.g., in response to] obtaining the activation signal. The backscatter response may for instance be received by the first apparatus (e.g., requesting entity and / or performing the method according to the first example aspect], by the second apparatus (e.g., CW provider and / or CW coordinating node] and / or by a third apparatus (e.g., a reader apparatus] which may for instance be different from the first and / or from the second apparatus.

[0073] The activation signal may be specific to a (e.g., targeted] tag apparatus, in particular the tag apparatus to which the activation signal is sent. For instance, the activation signal may, to this end, be transmitted in a specific spectrum (e.g., UL or DL and / or a specific frequency range], in a specific area and / or may contain an indication or identity of the tag apparatus.

[0074] The activation signal may be sent during a (e.g., ongoing] CW transmission, for instance a (e.g., previously] requested CW transmission, e.g., by means of a (e.g., the sent] CW support request. As the tag apparatus may be passive, a currently active CW transmission is required for it to generate a backscatter response to at least one other (e.g., reader] apparatus.

[0075] The activation signal may for instance indicate a (e.g., pre-defined] delay (e.g., a waiting time, e.g., for the tag apparatus] between a reception of the activation signal and an activation, or a time at which CW transmission shall be activated.

[0076] The activation signal may for instance be sent in response to sending (e.g., transmitting and / or providing] the CW support request. For instance, the method may comprise sending the CW support request and subsequently, for instance after a predefined time and / or after waiting at least a minimum predefined time, transmit the activation signal. Sending an activation signal after sending a CW support request may ensure that an activation (e.g., backscatter response] of the tag apparatus is possible, as the tag apparatus may not be able to be activated before it is charged and / or unless a CW transmission is available.

[0077] The activation signal may for instance be sent in response to obtaining a CW support response to the CW support request. For instance, the activation signal may be sent conditionally upon obtaining a (e.g., positive] CW support response to the CW support request. For instance, the sending of the activation signal and / or the activation signal (e.g., a content, a frequency spectrum, a timing of the activation signal, an information indicated by the activation signal] may be conditional on a content of the CW support response. For instance, the CW support response may indicate a successful or failed CW support request. The activation signal may (e.g., only] be sent if a successful CW support request is indicated but (e.g.,] not if a failed CW support request is indicated. For instance, the CW support response may indicate at least one CW property (e.g., a duration, start time and / or end time) of a CW transmission. The activation signal may be sent and / or configured depending at least partially on the CW property indicated by the CW support response. For instance, the activation signal may be sent at a time, during which, e.g., according to the CW support response, the CW transmission is (e.g., still) ongoing. The CW response may indicate a (e.g., minimum) waiting time. The activation signal may be sent after the (e.g., minimum) waiting time has elapsed. A sending and / or a configuration of the activation signal may further be dependent on a CW transmission identifier and / or a CW provider identifier indicated by the CW support response.

[0078] The activation signal may for instance be sent, after a pre-defined time after providing the CW support request. The pre-defined time may for instance be dimensioned to ensure that the tag apparatus is charged at the time the activation signal is sent. The pre-defined time may for instance be identical for (e.g., all) tag apparatuses to which the method may send activation signals. Additionally or alternatively, the pre-defined waiting time may be specific for a (e.g., type of) tag apparatus, for instance based on a charging duration.

[0079] According to an embodiment of the first example aspect, the method of the first example aspect further comprises the following steps, additionally, according to a second example aspect, a method is disclosed (e.g., performed and / or controlled by a first apparatus e.g., network node or UE) comprising: providing (e.g., transmitting) a CW deactivation request, to a (e.g., to the) second apparatus (CW coordinating node or CW provider, not an AIoT device) for requesting a deactivation of provision of at least one (e.g., or multiple, or all) carrier wave to at least one (e.g., of the at least one) tag apparatus (AioT device).

[0080] This method may for instance be performed and / or controlled by an apparatus, for instance a server. Alternatively, this method may be performed and / or controlled by more than one apparatus, for instance a server cloud comprising at least two servers. Alternatively, the method may for instance be performed and / or controlled by an electronic device, e.g. a node in a communication system and / or by a terminal device, e.g., a user equipment (UE). For instance, the method may be performed and / or controlled by using at least one processor of the electronic device.

[0081] According to a further example aspect, a computer program is disclosed, the computer program when executed by a processor causing an apparatus, for instance a server, a network node or a terminal device, e.g., a UE, to perform and / or control the actions of the method according to the first example aspect.

[0082] The computer program may be stored on computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read-(e.g., only) Memory (ROM) or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0083] According to a further example aspect, an apparatus is disclosed, configured to perform and / or control or comprising respective means for performing and / or controlling the method according to the first example aspect.

[0084] The means of the apparatus can be implemented in hardware and / or software. They may comprise for instance at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. Alternatively, they could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0085] The above-disclosed apparatus according to any aspect may be a module or a component for a device, for example a chip. Alternatively, the disclosed apparatus according to any aspect may be a device, for instance a server or server cloud. The disclosed apparatus according to any aspect may comprise (e.g., only) the disclosed components, for instance means, processor, memory, or may further comprise one or more additional components.

[0086] A CW deactivation request may enable to implement a configuration in which one or more CW transmissions are requested and subsequently continuously provided, for instance until a CW deactivation request is sent and / or received. As a consequence, less signaling (e.g., less frequency CW support requests) is required while at the same time staying in control of the energy expenditure of the system as CW transmissions may be deactivated at any time.

[0087] The CW deactivation request may be configured to deactivate at least one (e.g., ongoing) CW transmission. For instance, a CW deactivation request may be specific to at least one of a CW transmission, a CW provider, a CW coordinating node, or one or more tag apparatuses.

[0088] The CW deactivation request may be configured to deactivate one or multiple (e.g., ongoing) CW transmissions, for instance (e.g., all) CW transmissions of a given CW provider and / or CW transmissions coordinated by a given CW coordinator.

[0089] The CW deactivation request may be configured to cause an (e.g., essentially) immediate deactivation of the CW transmission and / or a deactivation after a pre-defined time. For instance, the CW deactivation may indicate a delay between the sending and / or reception of the CW deactivation request and a deactivation of the CW transmission, or a time at which CW transmission shall be deactivated. The CW deactivation request may be sent (e.g., provided and / or transmitted] to a second apparatus, for instance an apparatus to which (e.g., previously] a CW support request has been sent, e.g., by the same entity (e.g., first apparatus] sending the CW activation request. The second apparatus may be a CW provider and / or CW coordinating node. The second apparatus may in particular be different from an AIoT device.

[0090] According to an embodiment of the first and / or the second example aspect: the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by the CW provider.

[0091] By indicating at least one CW property of the CW transmission, the CW deactivation request may be able to deactivate a specific CW transmission and / or a group of CW transmissions.

[0092] According to an embodiment of the first and / or second example aspect, the CW property comprises at least one of: a (e.g., remaining] duration of a CW transmission, a spectrum of the CW transmission (e.g., UL or DL], a (e.g., previously provided] CW transmission identifier, or a CW provider identifier.

[0093] The CW property indicated by the CW deactivation request may for instance correspond to a CW transmission duration. For instance, only CW transmissions with a duration of more than a pre-defined duration threshold may be deactivated.

[0094] The CW property indicated by the CW deactivation request may for instance correspond to a CW transmission spectrum. For instance, only CW transmissions within the spectrum may be deactivated.

[0095] The CW property indicated by the CW deactivation request may for instance correspond to a CW transmission identifier. The CW deactivation request may thus target one specific CW transmission.

[0096] The CW property indicated by the CW deactivation request may for instance correspond to a CW provider identifier. The CW deactivation request may thus target at least one, multiple or all of the CW transmissions provided by the specified CW provider identifier.

[0097] According to an embodiment of the first and / or second example aspect: the CW deactivation request is (e.g., deactivator (first apparatus performing and / or controlling the method according to the first example aspect] is a terminal device (e.g., UE], second apparatus is a network node (e.g., gNB]] an uplink, UL, signal, the CW deactivation request is an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is (e.g., deactivator (first apparatus performing and / or controlling the method according to the first example aspect] is a terminal device (e.g., UE], second apparatus is a terminal device (e.g., UE)] at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information), a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is (e.g., deactivator (first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), second apparatus is a network node (e.g., gNB)) at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, (e.g, if the CW signal provider is a specific TRP), the CW deactivation request is (e.g., deactivator (first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), second apparatus is a terminal device (e.g., UE)) a DL, downlink, signal, or the CW deactivation request is a DL signal, wherein the DL signal is at least one of: a (e.g., specific) DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0098] The CW deactivation request may be sent (e.g., transmitted and / or provided) by means of (e.g., wireless and / or wired) communication links between apparatuses. The means may depend on types of apparatuses involved.

[0099] For instance, the first apparatus performing the method according to the first example aspect, may correspond to a terminal device, e.g., a UE, and / or the second apparatus corresponds to a network node, e.g., a gNB or a network node hosting a Core Network, CN, function. For instance in this constellation of apparatus types, but not only then, the CW deactivation request may be provided as an uplink, UL, signal, in particular an UL signal of one or combinations of the following types. The UL signal may for instance correspond to an uplink scheduling request, UL, SR. Additionally or alternatively, the UL signal may for instance correspond to a Medium Access Control Control Element, MAC CE. Additionally or alternatively, the UL signal may for instance correspond to a Radio Resource Control, RRC, signaling. Additionally or alternatively, the UL signal may for instance correspond to a Non Access Stratum, NAS, signaling. For instance, both the first apparatus performing the method according to the first example aspect and the second apparatus may correspond to a respective (e.g., mutually different] terminal device, e.g., a UE. For instance in this constellation of apparatus types, but not only then, the CW deactivation request may be provided as one or combinations of the following types. The CW deactivation request may be provided by means of a dedicated physical layer sequence, PHY sequence. Additionally or alternatively, the CW deactivation request may be provided by means of a side link control information, SCI, in particular a specific field in, e.g., a 1ststage and / or a 2ndstage SCI information. Additionally or alternatively, the CW deactivation request may be provided by means of a Side Link Medium Access Control Control Element, SL MAC CE and / or to a sidelink RRC signaling and / or PC5-RRC signaling.

[0100] For instance, both the first apparatus performing the method according to the first example aspect and the second apparatus may correspond to a respective (e.g., mutually different] network node, e.g., a gNB or a network node hosting a CN function. For instance in this constellation of apparatus types, but not only then, the CW deactivation request may be provided as one or combinations of the following types. The CW deactivation request may be provided by means of an Xn signaling. Additionally or alternatively, the CW deactivation request may be provided by means of an Fl signaling. Additionally or alternatively, the CW deactivation request may be provided by means of a signaling over a fronthaul link (e.g., if the CW provider is a specific Transmission Reception Point, TRP],

[0101] For instance, the first apparatus performing the method according to the first example aspect, may correspond to a network node, e.g., a gNB or a network node hosting a CN function, and / or the second apparatus corresponds to a terminal device, e.g., a UE. For instance in this constellation of apparatus types, but not only then, the CW deactivation request may be provided as an uplink, DL, signal, in particular an DL signal of one or combinations of the following types. The DL signal may for instance correspond to a Downlink Control Information, DCL Additionally or alternatively, the DL signal may for instance correspond to a MAC CE. Additionally or alternatively, the DL signal may for instance correspond to an RRC signaling. Additionally or alternatively, the DL signal may for instance correspond to a MAC CE. Additionally or alternatively, the DL signal may for instance correspond to a NAS signaling.

[0102] According to an embodiment of the first and / or second example aspect, the method further comprises: obtaining a (e.g., CW] deactivation response to the CW deactivation request (e.g., ACK / NACK] from the second apparatus.

[0103] A (CW] deactivation response may enable a deactivating entity (e.g., first apparatus, e.g., performing the method according to the first and / or second example aspect] to be informed whether the CW deactivation request was successful, e.g., whether it caused a deactivation of at least one or more CW transmission, or whether the CW deactivation request failed. Additionally or alternatively, the CW deactivation response may inform the deactivating entity of a property of the CW transmission (e.g., a remaining duration], a property (e.g., identifier] of the CW provider and / or combinations thereof. According to a third example aspect, a method is proposed (e.g., performed and / or controlled by a second apparatus, e.g., a CW provider, e.g., a network node or a terminal device (e.g., U E]]], comprising: obtaining (e.g., receiving] a CW support request from a requestor (e.g., from a first apparatus or from a CW coordinating node], and providing, in response to obtaining the CW support request, at least one CW transmission to at least one tag apparatus (e.g., different form apparatus performing the method, devoid of an activation signal].

[0104] This method may for instance be performed and / or controlled by an apparatus, for instance a server. Alternatively, this method may be performed and / or controlled by more than one apparatus, for instance a server cloud comprising at least two servers. Alternatively, the method may for instance be performed and / or controlled by an electronic device, e.g. a node in a communication system and / or by a terminal device, e.g., a user equipment (UE], For instance, the method may be performed and / or controlled by using at least one processor of the electronic device.

[0105] According to a further example aspect, a computer program is disclosed, the computer program when executed by a processor causing an apparatus, for instance a server, a network node or a terminal device, e.g., a UE, to perform and / or control the actions of the method according to the first example aspect.

[0106] The computer program may be stored on computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read- (e.g., only] Memory (ROM] or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0107] According to a further example aspect, an apparatus is disclosed, configured to perform and / or control or comprising respective means for performing and / or controlling the method according to the first example aspect.

[0108] The means of the apparatus can be implemented in hardware and / or software. They may comprise for instance at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. Alternatively, they could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0109] The above-disclosed apparatus according to any aspect may be a module or a component for a device, for example a chip. Alternatively, the disclosed apparatus according to any aspect may be a device, for instance a server or server cloud. The disclosed apparatus according to any aspect may comprise (e.g., only) the disclosed components, for instance means, processor, memory, or may further comprise one or more additional components.

[0110] The requestor may for instance correspond to a first apparatus, e.g., performing a method according to the first example aspect. Additionally or alternatively, the requestor may for instance correspond to a CW coordinating node, wherein for instance the CW coordinating node has obtained a [e.g., the) CW support request, e.g., from a first apparatus, e.g., performing the method according to the first example aspect.

[0111] The CW provider may be located within proximity of the at least one tag apparatus.

[0112] The CW provider may additionally fulfil, e.g., for a different (future or past) CW support request, the role of a CW coordinating node.

[0113] According to an embodiment of the third example aspect: the CW provider is a terminal device, or the CW provider is a network node.

[0114] According to an embodiment of the third example aspect: the CW support request is configured to indicate at least one CW property of a CW transmission to be provided by the CW provider.

[0115] According to an embodiment of the third example aspect, the CW property comprises at least one of: a starting time of the CW transmission, an ending time of the CW transmission, a duration of the CW transmission, a periodic pattern of the CW transmission (e.g., to account for the activator future AIoT sessions), a spectrum of the CW transmission (UL or DL), a CW transmission identifier, a CW provider identifier, a tag apparatus location, or a tag apparatus identifier.

[0116] For instance, the CW support request may indicate (and / or specify) at least one CW property of a (e.g., desired) CW transmission.

[0117] The CW provider performing the method according to the third example aspect may provide a CW transmission at least partially based on the CW support request, in particular on at least one CW property indicated by the CW support request. The provided CW transmission may for instance at least in one of its CW properties correspond to an indicated CW property indicated by the CW support request.

[0118] According to an embodiment of the third example aspect, the method further comprises: providing a CW support response to the CW support request (e.g., ACK / NACK] to the requestor.

[0119] According to an embodiment of the third example aspect, the CW support response is configured to indicate at least one of: a successful CW transmission, a failed CW transmission, a CW transmission starting time, a CW transmission ending time, a CW transmission duration, a minimum waiting time (e.g., before sending (e.g., by the first apparatus] an activation signal], a CW transmission identifier, or a CW provider identifier.

[0120] According to an embodiment of the third example aspect: the CW support request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect] is a terminal device (e.g., UE], CW provider is a network node (e.g., gNB]] an uplink, UL, signal, the CW support request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW support request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect] is a terminal device (e.g., UE], CW provider is a terminal device (e.g., UE]] at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information], a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect] is a network node (e.g., gNB], CW provider is a network node (e.g., gNB]] at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, (e.g., if the CW signal provider is a specific TRP] the CW support request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), CW provider is a terminal device (e.g., UE)) a DL, downlink, signal, or the CW support request is obtained as a DL signal, wherein the DL signal is at least one of: a (e.g., specific) DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0121] According to an embodiment of the first example aspect, the method of the third example aspect further comprises the following steps, additionally, according to a fourth example aspect, a method is disclosed (e.g., performed and / or controlled by a second apparatus, e.g., a CW provider, e.g., a network node or a terminal device (e.g., UE)) comprising: means for obtaining a CW deactivation request (e.g., from a first apparatus or from a CW coordinating node).

[0122] This method may for instance be performed and / or controlled by an apparatus, for instance a server. Alternatively, this method may be performed and / or controlled by more than one apparatus, for instance a server cloud comprising at least two servers. Alternatively, the method may for instance be performed and / or controlled by an electronic device, e.g. a node in a communication system and / or by a terminal device, e.g., a user equipment (UE). For instance, the method may be performed and / or controlled by using at least one processor of the electronic device.

[0123] According to a further example aspect, a computer program is disclosed, the computer program when executed by a processor causing an apparatus, for instance a server, a network node or a terminal device, e.g., a UE, to perform and / or control the actions of the method according to the first example aspect.

[0124] The computer program may be stored on computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read-(e.g., only) Memory (ROM) or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0125] According to a further example aspect, an apparatus is disclosed, configured to perform and / or control or comprising respective means for performing and / or controlling the method according to the first example aspect. The means of the apparatus can be implemented in hardware and / or software. They may comprise for instance at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. Alternatively, they could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0126] The above-disclosed apparatus according to any aspect may be a module or a component for a device, for example a chip. Alternatively, the disclosed apparatus according to any aspect may be a device, for instance a server or server cloud. The disclosed apparatus according to any aspect may comprise (e.g., only) the disclosed components, for instance means, processor, memory, or may further comprise one or more additional components.

[0127] The CW deactivation request may cause the CW provider to deactivate at least one of its (e.g., ongoing) CW transmissions. The CW transmissions may previously have been requested (e.g., by a same requestor from which the deactivation request is obtained or by a different requestor) by means of a CW support request.

[0128] According to an embodiment of the third and / or fourth example aspect: the CW deactivation request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), CW provider is a network node (e.g., gNB)) an uplink, UL, signal, the CW deactivation request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), CW provider is a terminal device (e.g., UE)) at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information), a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), CW provider is a network node (e.g., gNB)) at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, (e.g., if the CW signal provider is a specific TRP) the CW deactivation request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), CW provider is a terminal device (e.g., UE)) a DL, downlink, signal, or the CW deactivation request is obtained as a DL signal, wherein the DL signal is at least one of: a (e.g., specific) DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0129] According to an embodiment of the third and / or fourth example aspect: the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivation by the CW provider.

[0130] The CW provider may for instance deactivate at least one (e.g., ongoing CW transmission) based on the indicated at least one CW property.

[0131] According to an embodiment of the third and / or fourth example aspect, the CW property comprises at least one of: a duration of the CW transmission, a spectrum of the CW transmission (e.g., UL or DL), a (e.g., previously provided) CW transmission identifier, or a CW provider identifier.

[0132] The CW provider may for instance deactivate an (e.g., ongoing) CW transmission having a spectrum inside the indicated spectrum of the CW transmission and / or with an identifier corresponding to the indicated CW transmission identifier. Additionally or alternatively, the CW provider may deactivate at least one, multiple or all of its provided (e.g., ongoing) CW transmissions in case it obtains a CW deactivation request, for instance if a CW provider identifier indicated by the CW deactivation request corresponds to a CW provider identifier of the CW provider.

[0133] According to an embodiment of the third and / or fourth example aspect, the method further comprises: deactivating a provided CW transmission in response to at least one of: a locally observed condition, (e.g., a pre-defined time elapsing) or the obtaining of the CW deactivation request (e.g., depending on property of the CW transmission indicated by CW deactivation request).

[0134] For instance, a (e.g., ongoing) provided CW transmission may be deactivated.

[0135] Such deactivating of a provided CW transmission may for instance be conditional and / or be done in response to a locally observed condition. Such a locally observed condition may for instance correspond to a pre-defined time, for instance a CW transmission duration, e.g., indicated by a CW support request obtained (e.g., received] previously, e.g., wherein the CW support request has been configured to cause provision of the now-to-be deactivated CW transmission.

[0136] For instance, a provided CW transmission may be deactivated based on (e.g., in response to] a CW deactivation request. For instance, the deactivating may be based on at least one property indicated by the CW deactivation request and / or on a property of the (e.g., deactivated] CW transmission.

[0137] According to a fifth example aspect, a method is proposed (e.g., performed and / or controlled by a second apparatus, e.g., a CW coordinating node, e.g., a terminal device (e.g., UE] and / or a network node], comprising: obtaining (e.g., receiving] a CW support request from a first apparatus, and providing, in response to obtaining the CW support request, the CW support request or a further CW support request derived from the CW support request (e.g., the obtained CW support request or a derived CW support request derived based on the obtained CW support request] to a selected CW provider.

[0138] This method may for instance be performed and / or controlled by an apparatus, for instance a server. Alternatively, this method may be performed and / or controlled by more than one apparatus, for instance a server cloud comprising at least two servers. Alternatively, the method may for instance be performed and / or controlled by an electronic device, e.g. a node in a communication system and / or by a terminal device, e.g., a user equipment (UE]. For instance, the method may be performed and / or controlled by using at least one processor of the electronic device.

[0139] According to a further example aspect, a computer program is disclosed, the computer program when executed by a processor causing an apparatus, for instance a server, a network node or a terminal device, e.g., a UE, to perform and / or control the actions of the method according to the first example aspect.

[0140] The computer program may be stored on computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read-(e.g., only] Memory (ROM] or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0141] According to a further example aspect, an apparatus is disclosed, configured to perform and / or control or comprising respective means for performing and / or controlling the method according to the first example aspect. The means of the apparatus can be implemented in hardware and / or software. They may comprise for instance at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. Alternatively, they could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0142] The above-disclosed apparatus according to any aspect may be a module or a component for a device, for example a chip. Alternatively, the disclosed apparatus according to any aspect may be a device, for instance a server or server cloud. The disclosed apparatus according to any aspect may comprise (e.g., only) the disclosed components, for instance means, processor, memory, or may further comprise one or more additional components.

[0143] The method of the firth example aspect may be performed and / or controlled by a CW coordinating node, e.g., a network node and / or a terminal device (e.g, a UE). The CW coordinating node may for instance be configured to coordinate between a requestor (e.g., another CW coordinating node and / or a first apparatus performing and / or coordinating a method according to the first or second example aspect) and a CW provider (e.g., performing and / or coordinating a method according to the third or fourth example aspect). The CW coordinating node may provide no CW transmission and / or the CW coordinating node may (e.g., at least) not provide the requested CW transmission according to the received CW support request. Instead, the CW coordinating node may transmit the obtained CW support request (or a further CW support request which is based on the obtained CW support request) to a selected CW provider which may in turn provide the requested CW transmission. The further support request may for instance comprise at least one indication not present in the obtained CW support request, for instance an identifier of the selected CW provider.

[0144] According to an embodiment, the CW coordinating node may provide the CW support request to another CW coordinating node instead of the CW provider. Additionally or alternatively, CW provider may for instance turn into a CW coordinating node, e.g., when it cannot provide the CW transmission requested by the (e.g., further) CW support request.

[0145] According to an embodiment of the fifth example aspect: the CW coordinating node is a terminal device, or the CW coordinating node is a network node.

[0146] According to an embodiment of the fifth example aspect: the CW support request is configured to indicate at least one CW property of a CW transmission to be provided by the CW provider.

[0147] According to an embodiment of the fifth example aspect, the CW property comprises at least one of: a starting time of the CW transmission, an ending time of the CW transmission, a duration of the CW transmission, a periodic pattern of the CW transmission [e.g., to account for the activator future AIoT sessions], a spectrum of the CW transmission [UL or DL], a CW transmission identifier, a CW provider identifier, a tag apparatus location, or a tag apparatus identifier.

[0148] At least one of the CW properties may be defined by the CW coordinating node.

[0149] Additionally or alternatively, the CW coordinating node may select a selected CW provider based at least partially on at least one of the CW properties indicated by the CW support request.

[0150] According to an embodiment of the fifth example aspect, the method further comprises: selecting the CW provider [e.g., based on [e.g., at least one CW property indicated by) the CW support request [e.g., a CW provider identifier, a tag location / identifier, and / or another property indicated in the CW support request)).

[0151] A CW provider may be selected based at least partially on the obtained CW support request. For instance, a CW provider may be based on at least one CW property indicated by the CW support request.

[0152] For instance, a CW provider may be selected based on a CW provider identifier. For instance, a CW provider with an identifier corresponding to the indicated CW provider identifier may be selected as the selected CW provider.

[0153] Additionally or alternatively, a selected CW provider may be selected at least partially based on a tag location and / or a tag identifier indicated by the CW support request. For instance, a location of a CW provider may be matched to a location of a tag apparatus [e.g., as indicated by the CW support request and / or derived based on a tag apparatus identifier, e.g., indicated by the CW support request) . It may for instance be determined, whether a maximum distance between tag apparatus and CW provider is not exceeded).

[0154] Selecting a selected CW provider may be based on at least one or more than one [e.g., other) properties indicated in the CW support request

[0155] According to an embodiment, the CW support request may be free of an indication of a CW provider. In this case, the CW coordinating node may be responsible for selecting a suitable CW provider, e.g., based on at least one or the at least one CW properties indicated in the CW support request.

[0156] According to an embodiment of the fifth example aspect, the method further comprises: means for providing a CW support response to the CW support request [e.g., ACK / NACK) to the first apparatus. For instance, the CW support response may be indicative of a successful or failed selection of a selected CW provider and / or a successful or failed initiation of a CW transmission (e.g., by a selected CW provider).

[0157] According to an embodiment of the fifth example aspect, the CW support response is configured to indicate at least one of: a successful CW transmission, a failed CW transmission, a CW transmission starting time, a CW transmission ending time, a CW transmission duration, a minimum waiting time (e.g., before sending (e.g., by the first apparatus) an activation signal), a CW transmission identifier, or a CW provider identifier.

[0158] According to an embodiment, the method comprises obtaining (e.g., receiving) a (e.g., the one provided to the first apparatus) CW support response, e.g., from the selected CW provider, e.g., comprising at least one of the above properties. For instance, the CW coordinating node may attempt at least one further CW provider in case it receives a negative CW response (e.g., failed CW transmission).

[0159] According to an embodiment of the fifth example aspect: the CW support request is obtained as [e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), CW coordinating node is a network node (e.g., gNB)) an uplink, UL, signal, the CW support request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW support request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), CW coordinating node is a terminal device (e.g., UE)) at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information), a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request may be obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), CW coordinating node is a network node (e.g., gNB)) at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, (e.g., if the CW signal provider is a specific TRP) the CW support request is obtained as (e.g., requestor (e.g., first apparatus performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), CW coordinating node is a terminal device (e.g., UE)) a DL, downlink, signal, or the CW support request is obtained as a DL signal, wherein the DL signal is at least one of: a (e.g., specific) DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0160] According to an embodiment of the fifth example aspect: the CW support request is provided as (e.g., CW coordinating node is a terminal device (e.g., UE), CW provider is a network node (e.g., gNB)) an uplink, UL, signal, the CW support request is provided as an uplink, UL, signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW support request is provided as (e.g., CW coordinating node is a terminal device (e.g., UE), CW provider is a terminal device (e.g., UE)) at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information), a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request is provided as (e.g., CW coordinating node is a network node (e.g., gNB), CW provider is a network node (e.g., gNB)) at least one of an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, (e.g., if the CW signal provider is a specific TRP) the CW support request is provided as (e.g., CW coordinating node is a network node (e.g., gNB), CW provider is a terminal device (e.g., UE)) a DL, downlink, signal, or the CW support request is provided as a DL signal, wherein the DL signal is at least one of a (e.g., specific) DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0161] According to an embodiment of the fifth example aspect, the method further comprises the following steps, additionally, according to a sixth example aspect, a method is disclosed (e.g., performed and / or controlled by a second apparatus, e.g., a CW coordinator, e.g., a network node or a terminal device (e.g., UE)) comprising: obtaining a CW deactivation request (e.g., from a first apparatus).

[0162] This method may for instance be performed and / or controlled by an apparatus, for instance a server. Alternatively, this method may be performed and / or controlled by more than one apparatus, for instance a server cloud comprising at least two servers. Alternatively, the method may for instance be performed and / or controlled by an electronic device, e.g. a node in a communication system and / or by a terminal device, e.g., a user equipment (UE). For instance, the method may be performed and / or controlled by using at least one processor of the electronic device.

[0163] According to a further example aspect, a computer program is disclosed, the computer program when executed by a processor causing an apparatus, for instance a server, a network node or a terminal device, e.g., a UE, to perform and / or control the actions of the method according to the first example aspect.

[0164] The computer program may be stored on computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read-(e.g., only) Memory (ROM) or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0165] According to a further example aspect, an apparatus is disclosed, configured to perform and / or control or comprising respective means for performing and / or controlling the method according to the first example aspect.

[0166] The means of the apparatus can be implemented in hardware and / or software. They may comprise for instance at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. Alternatively, they could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0167] The above-disclosed apparatus according to any aspect may be a module or a component for a device, for example a chip. Alternatively, the disclosed apparatus according to any aspect may be a device, for instance a server or server cloud. The disclosed apparatus according to any aspect may comprise (e.g., only) the disclosed components, for instance means, processor, memory, or may further comprise one or more additional components. For instance, the CW deactivation request may be obtained from a first apparatus performing the method according to the first and / or second example aspect. The CW deactivation request may be configured to deactivate at least one (e.g., ongoing transmission), e.g., provided by a CW provider, e.g., to which the CW coordinating node (e.g., previously) provided a (e.g., further) CW support request.

[0168] According to an embodiment of the fifth and / or sixth example aspect, the method further comprises further comprising: means for providing, in response to obtaining the CW deactivation request, the CW deactivation request or a further CW deactivation request derived from the CW deactivation request (e.g., the obtained CW deactivation request or a derived CW deactivation request derived based on the obtained CW deactivation request) to a (e.g., the) selected CW provider.

[0169] For instance, a selected CW provider to which the CW deactivation request is provided may be selected based on the obtained CW deactivation request, e.g., on at least one CW property indicated by the CW support request.

[0170] The CW deactivation request may be configured to deactivate at least one (e.g., ongoing) CW transmission (e.g., currently) provided the selected CW provider.

[0171] According to an embodiment of the fifth and / or sixth example aspect: the CW deactivation request is provided as (e.g., CW coordinating node is a UE, CW provider is a gNB) an uplink, UL, signal, the CW deactivation request is provided as an uplink, UL, signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is provided as (e.g., CW coordinating node is a UE, CW provider is a UE) at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI (e.g., specific field in 1ststage or 2ndstage SCI information), a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is provided as (e.g., CW coordinating node is a gNB, CW provider is a gNB) at least one of an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, (e.g., if the CW signal provider is a specific TRP) the CW deactivation request is provided as (e.g., CW coordinating node is a gNB, CW provider is a UE] a DL, downlink, signal, or the CW deactivation request is provided as a DL signal, wherein the DL signal is at least one of a [e.g., specific] DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0172] According to an embodiment of the fifth and / or sixth example aspect: the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivation by the CW provider.

[0173] According to an embodiment of the fifth and / or sixth example aspect, the CW property comprises at least one of: a duration of the CW transmission, a spectrum of the CW transmission [e.g., UL or DL], a [e.g., previously provided] CW transmission identifier, or a CW provider identifier.

[0174] According to a seventh example aspect, a system is disclosed, comprising: a first apparatus comprising [e.g., a terminal device [e.g., UE] and / or a network node]: means for sending [e.g., providing, transmitting] a carrier wave, CW, support request to a second apparatus [e.g., CW coordinating node or CW provider, not an AIoT device] for requesting provision of at least one CW transmission to at least one tag apparatus [AIoT device] [CW transmission devoid of an activation signal, provides [e.g., only] energy, no information content, [pure] sinusoid, may reach multiple tag apparatuses, is recipient- unspecific], a CW provider [e.g., a terminal device [e.g., UE] and / or a network node] comprising: means for obtaining [e.g., receiving] a CW support request from the first apparatus (e.g., directly from a first apparatus or from the first apparatus via a CW coordinating node], and means for providing, in response to obtaining the CW support request, at least one CW transmission to at least one tag apparatus (e.g., different form first apparatus, devoid of an activation signal], and a tag apparatusfe.g., an AIoT device] comprising: means for obtaining the at least one CW transmission from the CW provider.

[0175] BRIEF DESCRIPTION OF THE FIGURES

[0176] Fig. la,b show schematic diagrams illustrating example radio environments in which example embodiments of the present disclosure may be performed; Fig. 2a,b shows schematic diagram illustrating an example radio environment in which example embodiments of the present disclosure may be performed;

[0177] Fig. 3 shows an signaling diagram in which example aspects of the disclosure are illustrated;

[0178] Fig. 4 shows a flow chart illustrating an embodiment according to the first example aspect of the disclosure;

[0179] Fig. 5 shows a flow chart illustrating an embodiment according to the first and second example aspect of the disclosure;

[0180] Fig. 6 shows a flow chart illustrating an embodiment according to the third example aspect of the disclosure;

[0181] Fig. 7 shows a flow chart illustrating an embodiment according to the third and fourth example aspect of the disclosure;

[0182] Fig. 8 shows a flow chart illustrating an embodiment according to the fifth example aspect of the disclosure;

[0183] Fig. 9 shows a flow chart illustrating an embodiment according to the fifth and sixth example aspect of the disclosure;

[0184] Fig. 10 shows a block diagram illustrating an embodiment according to the first example aspect of the disclosure;

[0185] Fig. 11 shows a block diagram illustrating an embodiment according to the first and second example aspect of the disclosure;

[0186] Fig. 12 shows a block diagram illustrating an embodiment according to the third example aspect of the disclosure;

[0187] Fig. 13 shows a block diagram illustrating an embodiment according to the third and fourth example aspect of the disclosure;

[0188] Fig. 14 shows a block diagram illustrating an embodiment according to the fifth example aspect of the disclosure;

[0189] Fig. 15 shows a block diagram illustrating an embodiment according to the fifth and sixth example aspect of the disclosure;

[0190] Fig. 16 shows a schematic illustration of examples of tangible and non- transitory computer- readable storage media.

[0191] DETAILED DESCRIPTION OF THE FIGURES

[0192] The following description serves to deepen the understanding of the present disclosure and shall be understood to complement and be read together with the description of example embodiments of the present disclosure as provided in the above SUMMARY section of this specification.

[0193] Fig. la, b illustrate relevant topologies for an ambient loT (AIoT) structure, for instance according to 3GPP Rel. 19 AIoT approaches. In a topology (AIoT topology), an ambient loT device may be provided with a carrier wave (CW) from other node(s) either inside the topology (e.g., by an entity involved in the communication interaction between AIoT device, in particular activator and / or reader) or outside the topology (e.g., by an entity not involved in communication interaction with the AIoT device, neither activator nor reader). The links in a topology may be bidirectional or unidirectional. A network node and / or a UE, an assisting node, and / or an intermediate node could comprise multiple BSs or UEs, respectively. Indoor and outdoor placement of any node may be done.

[0194] Fig. la illustrates a first topology. In the first topology, an Ambient loT device directly and bidirectionally communicates with a network node, base station BS. A communication between the base station and the ambient loT device includes Ambient loT data and / or signaling. This topology includes the possibility that the BS transmitting to the Ambient loT device is a different from the BS receiving from the Ambient loT device.

[0195] Fig. lb illustrates a second topology. In the second topology, an Ambient loT device communicates bidirectionally with an intermediate node between the device and base station. In this topology, the intermediate node can be a relay, an Integrated Access / Backhaul, I AB, node, a UE, a repeater, etc. The intermediate node may be capable of Ambient loT. The intermediate node may transfer at least some information between the BS and the Ambient loT device.

[0196] Fig. 2a, b illustrates a further AIoT topology. A carrier wave (CW) may be wave / carrier used by the AIOT device 400 to modulate and backscatter the AIOT reply. The CW signal is different from the activation signal and has the main purpose of carrying the AIOT response signal for those AIOT devices 400 which cannot actively and independently generate a signal of their own i.e., device category 1 and 2 a. In other words, the CW is being transformed by the AIOT device 400 to contain at least the AIOT ID and reflected i.e., backscattered either immediately or with a delay pre-configured by the activator.

[0197] In Fig. 2a, the activator 100 provides the activation signal and also provides the CW signal (i.e., CW transmission).

[0198] It has been recognized, that an entity generating the CW transmission does not necessarily need to be the activator (or even reader), e.g., in a given AIoT session. Fig. 2b demonstrates a different topology. Here, a CW provider 200 may instead provide a CW transmission can as a third-party entity. The CW provider may for instance correspond to a network node and / or to a UE. The CW provider is different from the activator.

[0199] The configuration shown in Fig. 2b may be referred to as a CW provision from outside topology, whereas Fig. 2 a shows a CW provision from inside topology.

[0200] The following example embodiments detail variations of enabling a CW transmission provision by an (e.g., out-of-topology) CW provider. Signaling details are provided which for instance a terminal device and / or a network entity may act as a CW provider. In some embodiments, an activation and / or a deactivation of the transmission of the CW signal may be triggered. Fig. 3 shows a signaling diagram illustrating a possible interplay between multiple entities of a AIoT topology.

[0201] For instance, an activator 100 may send a CW support request to a CW coordinating node 300, which in turn forwards it to the CW provider 200. Additionally or alternatively, the activator 100 may send a CW support request (e.g., directly) to an entity 200 taking the role of CW provider. Additionally or alternatively, the activator 100 may send the CW signal deactivation request to the coordinating node 300, which in turn forwards it to the CW provider 200. Additionally or alternatively, the activator 100 sends the CW signal deactivation request directly to the entity 200 taking the role of CW provider. Additionally or alternatively, the CW provider 200 decides when to deactivate the CW signal transmission based on locally observed triggering conditions.

[0202] Now turning to Fig. 3 in more detail, an activator 100, [for instance a first apparatus performing and / or controlling a method according to the first and / or second example aspect), may send, in step S100, a CW support request to a coordinating node 300 (for instance performing and / or controlling a method according to the fifth and / or sixth example aspect) which may in turn send the (or a further) CW support request to a CW provider 200 (for instance performing and / or controlling a method according to the third and / or fourth example aspect) in step S101. The coordinating node 300 may for instance select a CW provider 200, for instance based on at least one CW property indicated by the CW support request obtained in step S100. The CW provider 200 may provide a CW transmission in step S102, for instance in response to obtaining the CW support request in step S101. Using a CW coordinating node 300 instead of directly signaling a CW support request to a CW provider 200 may for instance prove advantageous if the CW provider 200 is not directly reachable by the activator 100 and / or if the activator 100 has not determined a suitable CW provider 200 for a given AIoT interaction with a tag apparatus 400 itself.

[0203] Thus, according to embodiments, the activator 100 sends the CW support request to the coordinating node 300, which in turn forwards it to the CW provider 200. In case the coordinating node 300 is a gNB A, then the request to the coordinating node 300 may be an UL signal such as UL SR, MAC CE or even RRC Request. In case the CW provider 200 is a UE under the coverage of the gNB A, then the gNB A 300 triggers the CW provider 200 directly to start the transmission of the CW. This triggering can be via a DL transmission from the gNB 300 to the device 200 acting as CW provider. In case the CW provider 200 is a network entity under the coverage of the gNB A 300, then the gNB A 300 triggers the CW provider 200 to start the transmission of the CW. This triggering can be via the Fl or fronthaul link from the gNB 300 to the entity acting as CW provider 200. In case the CW provider 200 is a UE under the coverage of gNB B, then the gNB A 300 triggers the CW provider 200 serving gNB B via the Xn interface. The gNB B then triggers via a DL transmission the CW provider 200 acting as the CW transmitter to start its transmission. In case the CW coordinating node 300 is a third UE (where the first UE and second are respectively the activator and reader), then the request to the coordinating node 300 can be a SL signal (if the activator is a UE) or a DL signal (if the activator is a NW node). In case the activator 100 is a UE, the SL activation signal can be a dedicated PHY sequence, a specific field in 1st stage SCI, a specific field in the 2nd stage SCI, a SL MAC CE or a PC5 RRC message. A discovery of a UE acting as a CW provider 200 can be provided by a network system information or announced by the actual UE acting as CW provider 200 based on the Prose Discovery procedure, where the CW signal transmission is part of the announced Prose services. In case the activator 100 is a NW node, the DL activation signal can be a specific DCI, a MAC CE, RRC message or a NAS message. The CW support request can include the indication of the starting time of when the CW transmission is required as well as the ending time. In addition, a periodic pattern for the required activation of the CW transmission can be provided with the request, in order to account for the activator future AIoT sessions.

[0204] In a slightly different embodiment, the activator 100 may (e.g., directly] signal a CW support request in step S103 to the CW provider 200, e.g., without involving a CW coordinating node as an intermediary. This embodiment may for instance be advantageous if the activator 100 know already which CW provider 200 is suitable for providing a CW transmission to a tag apparatus 400.

[0205] Thus, according to embodiments, the activator 100 sends the CW support request directly to an entity taking the role of CW provider 200. In case the activator 100 is a UE, then, if the CW provider 200 is another UE, the CW request can be a dedicated PHY sequence, a specific field in 1st stage SCI, a specific field in the 2nd stage SCI, a SL MAC CE or a PC5 RRC message. If, on the other hand, the CW provider 200 is a NW entity, then request can be a UL signal such as UL SR, MAC CE or even RRC Request. In case the activator 100 is a NW entity, then, if the CW provider 200 is a UE, then the CW support request can be a DL signal can be a specific DCI, a MAC CE, RRC message or a NAS message. If the CW provider 200 is another NW entity, then the CW support request can be via the Xn interface (if to another gNB] or via the Fl or fronthaul link if the CW signal provider 200 is a specific TRP. In both cases the request can include an indication of the starting time of when the CW transmission is required as well as the ending time. In addition, a periodic pattern for the required activation of the CW transmission can be provided with the CW support request, in order to account for the activator future AIoT sessions.

[0206] The activator 100 may further be configured to transmit an activation signal to the tag apparatus 400 in step SI 05. For instance, the activation signal may be sent after a CW support request is sent in step S100 or S103. At this stage, the activator 100 may expect that the CW provider 200 provides a CW to the tag apparatus 400. Thus, the tag apparatus 400 may be responsive to the activation signal provided in step S105. The activation signal is configured to transmit cause a backscatter reply by the tag apparatus 400 (step S106], The backscatter reply may for instance be received by a reader 500. The reader 500 may for instance be different or identical to the activator 100.

[0207] In particular according to aspects 2, 4 and 6 but also in aspects 1, 3, 5, and 7, a deactivation of CW provision is defined.

[0208] An activator 100 may, in step S107, send a CW deactivation request to a coordinating node 300 and / or to a CW provider 200. The CW deactivation request is configured to deactivate at least one (e.g., ongoing) CW transmission and / or more than one CW transmission, for instance multiple [e.g., all) CW transmissions at a given CW provider. The CW provider may, in step SI 10, deactivate at least one or more than one CW transmissions according to the CW deactivation request.

[0209] According to embodiments, the activator 100 or a reader 500 send a CW deactivation request to the coordinating node 300. The coordinating node 300 may then forward the CW deactivation request to the CW provider 200. In case the coordinating node 300 is a gNB, then the CW deactivation request to the coordinating node 300 can be an UL signal such as UL SR, MAC CE or even RRC Request. In case the CW provider 200 is a UE under the coverage of the gNB, then the gNB triggers the CW provider 200 directly to end the transmission of the CW. This triggering can be via a DL transmission from the gNB to the entity acting as CW provider 200. In case the CW provider 200 is a network entity under the coverage of the gNB, then the gNB triggers the CW provider 200 to end the transmission of the CW. This triggering can be via the Fl or fronthaul link from the gNB to the entity acting as CW provider 200. In case the CW provider 200 is a UE under the coverage of gNB B, then the original gNB A triggers the CW provider 200 serving gNB B via the Xn interface. The gNB B then triggers via a DL transmission the entity acting as the CW provider 200 to end [e.g., its) CW transmission. In case the coordinating node 300 is a third UE, then the CW deactivation request to the coordinating node 300 can be a SL signal [if the activator is a UE) or a DL signal [if the activator 100 is a NW node). In case the activator 100 is a UE, the SL deactivation signal can be a dedicated PHY sequence, a specific field in 1st stage SCI, a specific field in the 2nd stage SCI, a SL MAC CE or a PC5 RRC message. A discovery of the UE acting as CW provider 200 can be provided by network system information or announced by the actual UE acting as CW provider 200 based on the Prose Discovery procedure, where the CW signal transmission is part of the announced Prose services. In case the activator 100 is a NW node, the DL deactivation signal can be a specific DCI, a MAC CE, RRC message or a NAS message. The CW deactivation request can be triggered if the activator 100 no longer sees the need for a CW signal to be present. If an initial CW support request included an indication of when the CW transmission should end, then the CW deactivation request may not be needed unless the CW deactivation request indicates that the CW transmission should end sooner.

[0210] According to embodiments, the activator 100 and / or the reader 500 sends the CW deactivation request directly to the entity taking the role of CW signal provider 200. In case the activator 100 is a UE, then, if the CW provider 200 is another UE, then the CW deactivation request can be a dedicated PHY sequence, a specific field in 1st stage SCI, a specific field in the 2nd stage SCI, a SL MAC CE or a PC5 RRC message. If the CW provider 200 is a NW entity, then the CW deactivation request can be a UL signal such as UL SR, MAC CE or even RRC Request. In case the activator 100 is a NW entity, then, if the CW provider 200 is a UE, the CW deactivation request can be a DL signal can be a specific DCI, a MAC CE, RRC message or a NAS message. If the CW provider 200 is another NW entity, the CW deactivation request can be via the Xn interface [if to another gNB) or via the Fl or fronthaul link, in particular if the CW provider 200 is a specific TRP. The CW deactivation request can be triggered, if the activator 100 no longer sees the need for a CW signal to be present. If the initial CW support request included the indication of when the CW transmission should end, then the CW deactivation request may not be needed unless CW deactivation request indicates that the CW signal transmission should end sooner.

[0211] According to embodiments, the CW provider 200 may decide when to deactivate a CW transmission based on at least one of the following. Based on a reception of an [e.g., explicit) CW deactivation request, in particular while there are no other CW support requests of which a CW transmission period [e.g., indicated by a respective CW support request) may still be valid [e.g. the associated counter has not elapsed). Based on an elapsing of [e.g., all) counters associated with respective CW support requests.

[0212] Based on a lack of observation of [e.g., at least one) CW support request during a predefined observation window.

[0213] Fig. 4 shows a flowchart of an example embodiment according to the first example aspect, for instance performed by a first apparatus [e.g., activator). The method comprises sending a CW support request, in step M100, to a CW provider or to a CW coordinating node. The CW support request is configured to request a CW transmission from a CW provider.

[0214] Fig. 5 shows a flowchart of an example embodiment according to the first and / or second example aspect, for instance performed by a first apparatus [e.g., activator). The method comprises providing [e.g., transmitting, sending) a CW deactivation request, in step M200, to a CW provider or to a CW coordinating node. The CW deactivation request is configured to deactivate a [e.g., previously, e.g., in method step M100, requested) CW transmission by a CW provider is deactivated.

[0215] Fig. 6 shows a flowchart of an example embodiment according to the third example aspect, for instance performed by a second apparatus [e.g., CW provider). The method comprises obtaining a CW support request, in step M300, for instance from a first apparatus, e.g., an activator, in particular performing and / or controlling a method according to the first and / or second example aspect. Additionally or alternatively, the CW support request may be obtained from a CW coordinating node, for instance performing and / or controlling the method according to the fifth or sixth aspect. The method further comprises, in step M302, providing at least one CW transmission, e.g., to at least one tag apparatus, for instance in accordance with the CW support request obtained in step M300.

[0216] Fig. 7 shows a flowchart of an example embodiment according to the third and / or fourth example aspect, for instance performed by a second apparatus [e.g., CW provider). The method comprises obtaining a CW deactivation request, in step M400, for instance from a first apparatus, e.g., an activator, in particular performing and / or controlling a method according to the first and / or second example aspect. The CW deactivation request may be configured to deactivate an [e.g., previously, e.g., in method step M302, provided) CW transmission by the CW provider.

[0217] Fig. 8 shows flowchart of an example embodiment according to the fifth example aspect, for instance performed by a second apparatus [e.g., CW coordination node). The method comprises obtaining a CW support request, in step M500, for instance from a first apparatus, e.g., an activator, in particular performing and / or controlling a method according to the first and / or second example aspect. Additionally or alternatively, the CW support request may be obtained from another CW coordinating node, for instance also performing and / or controlling a method according to the fifth or sixth aspect. The method further comprises, in step M502, providing the least one CW support request and / or a further CW support request, e.g., to at least one CW provider, for instance performing and / or controlling the method according to the third and / or fourth aspect. The CW support request is configured to cause the CW provider to provide a CW transmission to at least one tag apparatus.

[0218] Fig. 9 shows a flowchart of an example embodiment according to the fifth and / or sixth aspect, for instance performed by a second apparatus (e.g., CW coordination node]. The method comprises obtaining a CW deactivation request in step M600, for instance from a first apparatus, e.g., an activator, in particular performing and / or controlling a method according to the first and / or second example aspect. Additionally or alternatively, the CW deactivation request may be obtained from another CW coordinating node, for instance also performing and / or controlling a method according to the fifth or sixth aspect. The CW deactivation request may be configured to deactivate an (e.g., previously requested, e.g., in method step M502) CW transmission by a CW provider.

[0219] Fig. 10 shows an example block diagram of a activator 100. The activator 100 may perform a method according to the first example aspect. The UE comprises a user interface A160, a program memory A110, a main memory A120, and a data memory A140. Further, it comprises a processor A130. The apparatus 100 may further comprise functional unit CW support request sender Al 31 which correspond to the action as shown in the flowchart of figure 4. A functional unit may for instance correspond to a code block within a memory A110, A120, A140. The CW support request sender A131 may for instance be connected to and / or control the communication interface A150.

[0220] Fig. 11 shows a further example block diagram of a activator 100. The activator 100 may perform a method according to the first and / or second example aspect. The UE comprises a user interface A160, a program memory A110, amain memory A120, and a data memory A140. Further, it comprises a processor A130. The apparatus 100 may further comprise functional unit CW deactivation request sender A132 which correspond to the action as shown in the flowchart of figure 5. A functional unit may for instance correspond to a code block within a memory A110, A120, A140. The CW support request sender A131 may for instance be connected to and / or control the communication interface A150.

[0221] Fig. 12 shows an example block diagram of a CW provider 200. The CW provider 200 may perform a method according to the third example aspect. The CW provider 200 comprises a user interface A260, a program memory A210, a main memory A220, and a data memory A240. Further, it comprises a processor A230. The CW provider 200 may further comprise functional unit CW support request obtainer A231 and a functional unit CW transmission provider A232 which correspond, respectively, to the action as shown in the flowchart of figure 6. A functional unit may for instance correspond to a code block within a memory A210, A220, A240. The functional units A231 and / or A232 may for instance be connected to and / or control the communication interface A250.

[0222] Fig. 13 shows an example block diagram of a CW provider 200. The CW provider 200 may perform a method according to the third and / or fourth example aspect. The CW provider 200 comprises a user interface A260, a program memory A210, a main memory A220, and a data memory A240. Further, it comprises a processor A230. The CW provider 200 may further comprise functional unit CW deactivation request obtainer A233 which corresponds to the action as shown in the flowchart of figure 7. A functional unit may for instance correspond to a code block within a memory A210, A220, A240. The functional unit A233 may for instance be connected to and / or control the communication interface A250.

[0223] Fig. 14 shows an example block diagram of a CW coordinating node 300. The CW coordinating node 300 may perform a method according to the fifth example aspect. The CW coordinating node 300 comprises a user interface A360, a program memory A310, a main memory A320, and a data memory A340. Further, it comprises a processor A330. The CW coordinating node 300 may further comprise functional unit CW support request obtainer A331 and a functional unit CW support request provider A332 which correspond, respectively, to the action as shown in the flowchart of figure 8. A functional unit may for instance correspond to a code block within a memory A310, A320, A340. The functional units A331 and / or A332 may for instance be connected to and / or control the communication interface A350.

[0224] Fig. 15 shows an example block diagram of a CW coordinating node 300. The CW coordinating node 300 may perform a method according to the fifth and / or sixth example aspect. The CW coordinating node 300 comprises a user interface A360, a program memory A310, a main memory A320, and a data memory A340. Further, it comprises a processor A330. The CW coordinating node 300 may further comprise functional unit CW deactivation request obtainer A333 which corresponds to the action as shown in the flowchart of figure 9. A functional unit may for instance correspond to a code block within a memory A310, A320, A340. The functional unit A333 may for instance be connected to and / or control the communication interface A350.

[0225] Fig. 16 is a schematic illustration of examples of tangible and non-transitory computer-readable storage media according to the present invention that may for instance be used to implement program and / or main memory A110, A120, A140, A210, A220, A240, A310, A320, A340 of the apparatus 100, 200 and / or 300 of Fig. 9 to 15. Fig. 16 shows a flash memory 1600, which may for instance be soldered or bonded to a printed circuit board, a solid-state drive 1601 comprising a plurality of memory chips (e.g. Flash memory chips], a magnetic hard drive 1602, a Secure Digital (SD) card 1603, a Universal Serial Bus [USB] memory stick 1604, an optical storage medium 1605 (such as for instance a CD-ROM or DVD) and a magnetic storage medium 1606.

[0226] Some embodiments comprise: Embodiment 1:

[0227] A first method (e.g., according to the first example aspect] comprising: sending a carrier wave, CW, support request to a second apparatus for requesting provision of at least one CW transmission to at least one tag apparatus.

[0228] Embodiment 2:

[0229] The first method of embodiment 1, wherein the CW support request is configured to indicate at least one CW property of a CW transmission to be provided by the CW provider.

[0230] Embodiment 3:

[0231] The first method of embodiment 2, wherein the CW property comprises at least one of: a starting time of the CW transmission, an ending time of the CW transmission, a duration of the CW transmission, a periodic pattern of the CW transmission, a spectrum of the CW transmission, a CW transmission identifier, a CW provider identifier, a tag apparatus location, or a tag apparatus identifier.

[0232] Embodiment 4:

[0233] The first method of any of embodiments 1 to 3, wherein: the first apparatus is a terminal device, or the first apparatus is a network node.

[0234] Embodiment 5:

[0235] The first method of any of embodiments 1 to 4, wherein the second apparatus is at least one of: a CW coordinating node, a CW coordinating node, wherein the CW coordinating node is a network node, a CW coordinating node, wherein the CW coordinating node is a user equipment, UE, the CW provider, the CW provider, wherein the CW provider is a network node, or the CW provider, wherein the CW provider is a terminal device.

[0236] Embodiment 6:

[0237] The first method of any of embodiments 1 to 5, wherein the tag apparatus is an ambient internet of things, AIoT, apparatus.

[0238] Embodiment 7: The first method of any of embodiments 1 to 6, wherein at least one of: the CW support request is provided as an uplink, UL, signal, the CW support request is provided as an UL signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW support request is provided as at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request is provided as at least one of an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW support request is provided as a downlink, DL, signal, or the CW support request is provided as a DL signal, wherein the DL signal is provided via at least one of a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0239] Embodiment 8:

[0240] The first method of any of embodiments 1 to 7, further comprising: obtaining a CW support response to the CW support request from the second apparatus.

[0241] Embodiment 9:

[0242] The first method according to embodiments 8, wherein the CW support response is configured to indicate at least one of: a successful CW transmission, a failed CW transmission, a CW transmission starting time, a CW transmission ending time, a CW transmission duration, a minimum waiting time, a CW transmission identifier, or a CW provider identifier. Embodiment 10:

[0243] The first method of any of embodiments 1 to 9, further comprising: providing an activation signal to at least one of the at least one tag apparatus.

[0244] Embodiment 11:

[0245] The first method of any of embodiments 1 to 10, wherein at least one of: the activation signal is configured to cause a backscatter response from the tag apparatus, the activation signal is specific to the tag apparatus, the activation signal is sent during an ongoing CW transmission, the activation signal indicates a delay between a reception of the activation signal and an activation, or the activation signal is provided at least one of: in response to providing the CW support request, in response to obtaining a CW support response to the CW support request, or after a pre-defined time after providing the CW support request.

[0246] Embodiment 12:

[0247] A first method (e.g., the method according to any of embodiments 1 to 9 or a method according to the second example aspect], further comprising: providing a CW deactivation request, to a second apparatus for requesting a deactivation of provision of at least one carrier wave to at least one tag apparatus.

[0248] Embodiment 13:

[0249] The first method of any of embodiments 1 to 12, wherein the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by a CW provider.

[0250] Embodiment 14:

[0251] The first method of any of embodiments 1 to 13, wherein the CW property comprises at least one of: a spectrum of the CW transmission, a CW transmission identifier, or a CW provider identifier.

[0252] Embodiment 15:

[0253] The first method of any of any of embodiments 1 to 14, wherein: the CW deactivation request is an uplink, UL, signal, the CW deactivation request is an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW deactivation request is a DL, downlink, signal, or the CW deactivation request is a DL signal, wherein the DL signal is at least one of: a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0254] Embodiment 16:

[0255] The first method of any of embodiments 1 to 15 further comprising: obtaining a deactivation response to the CW deactivation request from the second apparatus.

[0256] Embodiment 17:

[0257] A (e.g., carrier wave, CW, providing) method (e.g., according to the third example aspect), comprising: obtaining a CW support request from a requestor, and providing, in response to obtaining the CW support request, at least one CW transmission to at least one tag apparatus.

[0258] Embodiment 18:

[0259] The method of embodiment 17, wherein: the CW provider is a terminal device, or the CW provider is a network node.

[0260] Embodiment 19:

[0261] The method of embodiment 17 or 18, wherein the CW support request is configured to indicate at least one CW property of a CW transmission to be provided by the CW provider.

[0262] Embodiment 20:

[0263] The method of embodiment 19, wherein the CW property comprises at least one of: a starting time of the CW transmission, an ending time of the CW transmission, a duration of the CW transmission, a periodic pattern of the CW transmission, a spectrum of the CW transmission, a CW transmission identifier, a CW provider identifier, a tag apparatus location, or a tag apparatus identifier.

[0264] Embodiment 21:

[0265] The method of any of embodiments 17 to 20, further comprising: providing a CW support response to the CW support request to the requestor.

[0266] Embodiment 22:

[0267] The method of any of embodiments 17 to 21, wherein the CW support response is configured to indicate at least one of: a successful CW transmission, a failed CW transmission, a CW transmission starting time, a CW transmission ending time, a CW transmission duration, a minimum waiting time, a CW transmission identifier, or a CW provider identifier.

[0268] Embodiment 23:

[0269] The method of any of embodiments 17 to 22, wherein: the CW support request is obtained as an uplink, UL, signal, the CW support request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling. the CW support request is obtained as at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request is obtained as at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW support request is obtained as a DL, downlink, signal, or the CW support request is obtained as a DL signal, wherein the DL signal is at least one of: a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0270] Embodiment 24:

[0271] A (e.g., CW providing] method (e.g., the method according to any of embodiments 17 to 23 or a method according to the fourth example aspect], further comprising: obtaining a CW deactivation request.

[0272] Embodiment 25:

[0273] The method of any of embodiments 17 to 24, wherein: the CW deactivation request is obtained as an uplink, UL, signal, the CW deactivation request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is obtained as at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is obtained as at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW deactivation request is obtained as a DL, downlink, signal, or the CW deactivation request is obtained as a DL signal, wherein the DL signal is at least one of: a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0274] Embodiment 26:

[0275] The method of any of embodiments 17 to 25, wherein: the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by the CW provider

[0276] Embodiment 27:

[0277] The method of embodiment 26, wherein the CW property comprises at least one of: a spectrum of the CW transmission, a CW transmission identifier, or a CW provider identifier.

[0278] Embodiment 28:

[0279] The method of any of embodiments 17 to 27, further comprising: deactivating a provided CW transmission in response to at least one of: a locally observed condition, or the obtaining of the CW deactivation request.

[0280] Embodiment 29:

[0281] A (e.g., CW coordinating] method [e.g., according to the fifth example aspect), comprising: obtaining a CW support request from a first apparatus, and providing, in response to obtaining the CW support request, the CW support request or a further CW support request derived from the CW support request to a selected CW provider.

[0282] Embodiment 30:

[0283] The method of embodiment 29, wherein: the CW coordinating node is a terminal device, or the CW coordinating node is a network node.

[0284] Embodiment 31:

[0285] The method of embodiment 29 or 30, wherein the CW support request is configured to indicate at least one CW property of a CW transmission to be provided by the CW provider.

[0286] Embodiment 32:

[0287] The method according to embodiment 31, wherein the CW property comprises at least one of: a starting time of the CW transmission, an ending time of the CW transmission, a duration of the CW transmission, a periodic pattern of the CW transmission, a spectrum of the CW transmission, a CW transmission identifier, a CW provider identifier, a tag apparatus location, or a tag ap aratus identifier.

[0288] Embodiment 33:

[0289] The method of any of embodiments 29 to 32, further comprising: selecting the CW provider.

[0290] Embodiment 34:

[0291] The method of any of embodiments 29 to 33, further comprising: providing a CW support response to the CW support request to the first apparatus.

[0292] Embodiment 35:

[0293] The method of any of embodiments 29 to 34, wherein: the CW support request is obtained as an uplink, UL, signal, the CW support request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or Non Access Stratum, NAS, signaling, the CW support request is obtained as at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request may be obtained as at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW support request is obtained as a DL, downlink, signal, or the CW support request is obtained as a DL signal, wherein the DL signal is at least one of: a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0294] Embodiment 36:

[0295] The method of any of embodiments 29 to 35, wherein the CW support request is provided as an uplink, UL, signal, the CW support request is provided as an uplink, UL, signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW support request is provided as at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW support request is provided as at least one of an Xn signaling, an Fl signaling, or a signaling over a fronthaul link the CW support request is provided as a DL, downlink, signal, or the CW support request is provided as a DL signal, wherein the DL signal is at least one of a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

[0296] Embodiment 37:

[0297] A (e.g., CW coordinating] method [e.g., the method according to any of embodiments 29 to 36 or a method according to the sixth example aspect], further comprising: obtaining a CW deactivation request.

[0298] Embodiment 38:

[0299] The method of any of embodiments 29 to 37, further comprising: providing, in response to obtaining the CW deactivation request, the CW deactivation request or a further CW deactivation request derived from the CW deactivation request to a selected CW provider.

[0300] Embodiment 39:

[0301] The method of any of embodiments 29 to 38, wherein the CW deactivation request is provided as an uplink, UL, signal, the CW deactivation request is provided as an uplink, UL, signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is provided as at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is provided as at least one of an Xn signaling, or an Fl signaling, or a signaling over a fronthaul link, the CW deactivation request is provided as a DL, downlink, signal, or the CW deactivation request is provided as a DL signal, wherein the DL signal is at least one of a DCI, a MAC CE, an RRC signaling or a NAS signaling.

[0302] Embodiment 40:

[0303] The method of any of embodiments 29 to 39, wherein the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by a CW provider.

[0304] Embodiment 41:

[0305] The method of embodiment 40, wherein the CW property comprises at least one of: a spectrum of the CW transmission, a CW transmission identifier, or a CW provider identifier.

[0306] Embodiment 42:

[0307] A first apparatus comprising respective means for performing the method of any of Embodiments 1 to 16.

[0308] Embodiment 43:

[0309] An first apparatus comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform and / or control the method according to any of embodiments 1 to 16.

[0310] Embodiment 44:

[0311] A second apparatus, for instance a CW provider, comprising respective means for performing the method of any of embodiments 17 to 28.

[0312] Embodiment 45:

[0313] A second apparatus, for instance a CW provider, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform and / or control the method according to any of embodiments 17 to 28. Embodiment 46:

[0314] A third apparatus, for instance a CW coordinating node, comprising respective means for performing the method of any of embodiments 29 to 41.

[0315] Embodiment 47:

[0316] A third apparatus, for instance a CW coordinating node, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform and / or control the method according to any of embodiments 29 to 41.

[0317] Embodiment 48:

[0318] A computer program, the computer program when executed by a processor causing an apparatus, e.g. the apparatus according to embodiment 42 or 43, to perform and / or control the actions and / or steps of the method of any of embodiments 1 to 16.

[0319] Embodiment 49:

[0320] A computer program product comprising a computer program according to embodiment 48.

[0321] Embodiment 50:

[0322] A computer program, the computer program when executed by a processor causing an apparatus, e.g. the apparatus according to embodiment 44 or 45, to perform and / or control the actions and / or steps of the method of any of embodiments 17 to 28.

[0323] Embodiment 51:

[0324] A computer program product comprising a computer program according to embodiment 50.

[0325] Embodiment 52:

[0326] A computer program, the computer program when executed by a processor causing an apparatus, e.g. the apparatus according to embodiment 46 or 47, to perform and / or control the actions and / or steps of the method of any of embodiments 29 to 41.

[0327] Embodiment 53:

[0328] A computer program product comprising a computer program according to embodiment 52.

[0329] Embodiment 54:

[0330] A system comprising: at least one first apparatus according to any of the embodiments 42 or 43, at least one second apparatus according to any of the embodiments 44 or 45, and at least one third apparatus according to any of the embodiments 46 or 47. Any presented connection in the described embodiments is to be understood in a way that the involved components are operationally coupled. Thus, the connections can be direct or indirect with any number or combination of intervening elements, and there may be merely a functional relationship between the components.

[0331] Further, as used in this text, the term ‘circuitry’ refers to any of the following:

[0332] [a] hardware-only circuit implementations [such as implementations in only analog and / or digital circuitry)

[0333] [b] combinations of circuits and software (and / or firmware), such as: (i) to a combination of processor (s) or (ii) to sections of processor (s) / software (including digital signal processor (s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone, to perform various functions) and

[0334] [c] to circuits, such as a microprocessor(s) or a section of a microprocessor(s), that re-quire software or firmware for operation, even if the software or firmware is not physically present.

[0335] This definition of ‘circuitry’ applies to all uses of this term in this text, including in any claims. As a further example, as used in this text, the term ‘circuitry’ also covers an implementation of merely a processor (or multiple processors) or section of a processor and its (or their) accompanying software and / or firmware. The term ‘circuitry’ also covers, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone.

[0336] Any of the processors mentioned in this text, in particular but not limited to processors 130, 230, 330 of Figs. 9 to 15, could be a processor of any suitable type. Any processor may comprise but is not limited to one or more microprocessors, one or more processor(s) with accompanying digital signal processor(s), one or more processor(s) without accompanying digital signal processor(s), one or more special-purpose computer chips, one or more field-programmable gate arrays (FPGAS), one or more controllers, one or more application-specific integrated circuits (ASICS), or one or more computer(s). The relevant structure / hardware has been programmed in such a way to carry out the described function.

[0337] Moreover, any of the actions or steps described or illustrated herein may be implemented using executable instructions in a general-purpose or special-purpose processor and stored on a computer- readable storage medium (e.g., disk, memory, or the like) to be executed by such a processor. References to ‘computer-readable storage medium’ should be understood to encompass specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices.

[0338] Moreover, any of the actions described or illustrated herein may be implemented using executable instructions in a general-purpose or special-purpose processor and stored on a computer-readable storage medium (e.g., disk, memory, or the like) to be executed by such a processor. References to 'computer-readable storage medium’ should be understood to encompass specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices. The wording "A, or B, or C, or a combination thereof’ or "at least one of A, B and C" may be understood to be not exhaustive and to include at least the following: p) A, or pi) B, or pii) C, or pv) A and B, or (v) A and

[0339] C, or [vi) B and C, or [vii) A and B and C.

[0340] It will be understood that the embodiments disclosed herein are only exemplary, and that any feature presented for a particular exemplary embodiment may be used with any aspect of the present disclosure on its own or in combination with any feature presented for the same or another particular exemplary embodiment and / or in combination with any other feature not mentioned. It will further be understood that any feature presented for an example embodiment in a particular category may also be used in a corresponding manner in an example embodiment of any other category.

[0341] LIST OF ABBREVIATIONS

[0342] AIoT ambient I0T

[0343] R2D reader to device [Activation signal)

[0344] D2R device to reader [Response signal)

[0345] BPSK binary phase shift keying

[0346] CW Carrier Wave

Claims

C l a i m s1. A first apparatus comprising: means for providing a CW deactivation request, to a second apparatus for requesting a deactivation of provision of at least one carrier wave to at least one tag apparatus.

2. The first apparatus of claim 1, wherein the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by a CW provider.

3. The first apparatus of claim 2, wherein the CW property comprises at least one of: a spectrum of the CW transmission, a CW transmission identifier, or a CW provider identifier.

4. The first apparatus of any of claims 1 to 3, wherein: the CW deactivation request is an uplink, UL, signal, the CW deactivation request is an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW deactivation request is a DL, downlink, signal, or the CW deactivation request is a DL signal, wherein the DL signal is at least one of: a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

5. The first apparatus of any of claims 1 to 4 further comprising: means for obtaining a deactivation response to the CW deactivation request from the second apparatus.

6. A CW provider comprising: means for obtaining a CW deactivation request.

7. The CW provider according to claim 6, wherein: the CW deactivation request is obtained as an uplink, UL, signal, the CW deactivation request is obtained as an uplink, UL, signal, wherein the UL signal is at least one of: an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is obtained as at least one of: a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is obtained as at least one of: an Xn signaling, an Fl signaling, or a signaling over a fronthaul link, the CW deactivation request is obtained as a DL, downlink, signal, or the CW deactivation request is obtained as a DL signal, wherein the DL signal is at least one of: a DCI, a MAC CE, an RRC signaling, or a NAS signaling.

8. The CW provider according to claim 6 or 7, wherein: the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by the CW provider9. The CW provider according to claim 8, wherein the CW property comprises at least one of: a spectrum of the CW transmission, a CW transmission identifier, or a CW provider identifier.

10. The CW provider according to any of claims 6 to 9, further comprising: means for deactivating a provided CW transmission in response to at least one of: a locally observed condition, orthe obtaining of the CW deactivation request.

11. A CW coordinating node comprising: means for obtaining a CW deactivation request.

12. The CW coordinating node according to claim 11, further comprising: means for providing, in response to obtaining the CW deactivation request, the CW deactivation request or a further CW deactivation request derived from the CW deactivation request to a selected CW provider.

13. The CW coordinating node of claim 11 or 12, wherein: the CW deactivation request is provided as an uplink, UL, signal, the CW deactivation request is provided as an uplink, UL, signal, wherein the UL signal is at least one of an uplink scheduling request, UL SR, a Medium Access Control Control Element, MAC CE, a Radio Resource Control, RRC, signaling, or a Non Access Stratum, NAS, signaling, the CW deactivation request is provided as at least one of a dedicated physical layer sequence, PHY sequence, a sidelink control information, SCI, a sidelink, SL, MAC CE, or a sidelink RRC signaling or PC5-RRC signaling, the CW deactivation request is provided as at least one of an Xn signaling, or an Fl signaling, or a signaling over a fronthaul link, the CW deactivation request is provided as a DL, downlink, signal, or the CW deactivation request is provided as a DL signal, wherein the DL signal is at least one of a DCI, a MAC CE, an RRC signaling or a NAS signaling.

14. The CW coordinating node of any of claims 11 to 13, wherein the CW deactivation request is configured to indicate at least one CW property of a CW transmission to be deactivated by a CW provider.

15. The CW coordinating node of claim 14, wherein the CW property comprises at least one of: a spectrum of the CW transmission,a CW transmission identifier, or a CW provider identifier.

16. A system comprising at least: - a first apparatus comprising: means for providing a CW deactivation request, to a second apparatus for requesting a deactivation of provision of at least one carrier wave to at least one tag apparatus a CW provider comprising: means for obtaining the CW deactivation request.

Images