The carrier provides

Abstract

Methods, apparatuses, and systems for providing a carrier (e.g., in a communication network) are disclosed.

Description

Technical Field

[0001] This disclosure relates to, but is not limited to, communication networks defined by 3GPP standards, such as the 6G standard. This disclosure particularly relates to communication with so-called tags (such as Ambient Internet of Things (AIoT) devices), and especially to the configuration of such communication. Background Technology

[0002] The number of IoT connections has grown rapidly in recent years and is projected to reach hundreds of billions by 2030. As more and more devices are expected to interconnect to improve productivity and enhance quality of life, there is a need to further reduce the size, cost, and power consumption of IoT devices.

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

[0004] In the new method, so-called tags in the form of environmental IoT devices are used. AIoT devices can utilize energy from wireless signals they receive, known as carrier waves (CW). AIoT devices can be charged by the carrier waves and can also be activated (e.g., in a charging state) to reflect signals (e.g., the carrier waves) while encoding at least one piece of information into the carrier waves, such as at least one ID of the AIoT device.

[0005] A typical system architecture surrounding an AIoT device may include: 1) a tag device (e.g., an AIoT tag apparatus) that utilizes energy (e.g., within a frequency range, such as from a carrier) and listens for an activation signal. Once activated, it can reflect and / or modulate the carrier in a predetermined manner. 2) an activator (i.e., a user equipment or network device) that provides a carrier wave (CW) and sends an activation signal aimed at waking up the AIoT device. Once the AIoT device is charged by the activator's CW and receives the activation signal from the activator, the AIoT device reflects the CW in a predefined manner. 3) a reader, i.e., a user equipment or network device that listens for and detects the reflected and / or modulated CW and, for example, extracts information from it. The reader may or may not be co-located with the activator. Summary of the Invention

[0006] It has been recognized that the carrier needs to have sufficient power at the location of the AIoT device to charge the device and / or allow the CW to be reflected far enough by the AIoT device to reach the reader. Therefore, the activator providing the carrier may need to be located near the AIoT device and / or transmit a strong carrier to be able to interact with the AIoT device. This can limit AIoT use cases. It has also been recognized that activation of an already charged AIoT device can be achieved with much lower signal strength compared to a carrier. Finally, it has been recognized that creating a split in the AIoT architecture can be advantageous, where the CW provider delivers the carrier to the AIoT device, and the activator provides the activation signal to the AIoT device, where the activator and CW provider are distinct from each other.

[0007] Therefore, the purpose of this disclosure is particularly to enable the activator of an AIoT system to interact with AIoT devices, wherein the activator itself does not provide a carrier wave to the AIoT device.

[0008] According to the first example aspect, a method is disclosed (e.g., executed and / or controlled by a first device (e.g., a network node or a UE)) comprising: - Send (e.g., provide) a carrier (CW) support request to a second device (e.g., a CW coordinating node or a CW provider, rather than an AIoT device) to request at least one CW transmission to be provided to at least one tag device (e.g., an AIoT device) (e.g., at least one of the following: the CW transmission may not have an activation signal, the CW transmission may (e.g., only) provide power, the CW transmission may not carry information content, the CW transmission may correspond to (e.g., a pure and / or unmodulated) sine wave, the CW transmission may correspond to or may reach multiple tag devices and / or the CW transmission may be non-receiver specific).

[0009] The method can be performed and / or controlled, for example, by a device (e.g., a server). Alternatively, the method can be performed and / or controlled by more than one device, such as a server cloud comprising at least two servers. Alternatively, the method can be performed and / or controlled, for example, by an electronic device (e.g., a node in a communication system) and / or a terminal device (e.g., a user equipment (UE)). For example, the method can be performed and / or controlled using at least one processor of an electronic device.

[0010] According to another example aspect, a computer program is disclosed that, when executed by a processor, causes a device (e.g., a server, network node, or terminal device, such as a UE) to perform and / or control actions according to the method of the first example aspect.

[0011] Computer programs can be stored on computer-readable storage media, particularly tangible and / or non-transitory media. Computer-readable storage media can be, for example, disks or memory. Computer programs can be stored in computer-readable storage media in the form of instructions encoding the computer-readable storage media. Computer-readable storage media can be intended to participate in the operation of a device, such as internal or external memory, such as a computer's read-only memory (ROM) or hard disk, or intended for program distribution, such as optical discs.

[0012] According to another example aspect, an apparatus is disclosed that is configured to perform and / or control or includes corresponding components for performing and / or controlling the method according to the first example aspect.

[0013] The components of the device can be implemented in hardware and / or software. They may include, for example, at least one processor for executing computer program code to achieve the desired function, at least one memory for storing the program code, or both. Alternatively, they may include, for example, circuitry designed to achieve the desired function, such as circuitry implemented in a chipset or chip (e.g., an integrated circuit). Typically, the component may include, for example, one or more processing components or processors.

[0014] The apparatus disclosed above according to any aspect may be a module or component for a device (e.g., a chip). Alternatively, the apparatus disclosed according to any aspect may be a device, such as a server or server cloud. The apparatus disclosed according to any aspect may include (e.g., only) the disclosed components, such as parts, processors, memory, or may also include one or more additional components.

[0015] Terminal equipment (e.g., user equipment (UE)) can correspond to mobile devices such as mobile phones, tablets, smartwatches, laptops, personal digital assistant (PDA) devices, wearable devices, Internet of Things (IoT) devices, IIoT (Industrial IoT) devices, vehicles, and / or combinations thereof. Such user equipment can also be referred to as user equipment.

[0016] Network nodes can correspond to components of a communication network, such as base transceiver stations (BTS), nodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), distributed units (DUs), centralized units (CUs), and / or combinations thereof.

[0017] The apparatus for performing and / or controlling the method according to the first example aspect can be an activator. The activator can be configured to activate at least one tag device. For example, the activator can be configured to determine and / or identify whether a tag device to be activated by the apparatus is positioned in a manner that prevents the activator from providing a carrier wave to the tag device (e.g., at a distance greater than a predefined distance). In this case, the activator can perform the method to activate the tag device.

[0018] A carrier support request (CW support request) can be configured to request at least one CW transmission to at least one tag device.

[0019] Tag devices can be, in particular, AIoT devices. For example, there may be different categories of AIoT devices.

[0020] For example, AIoT devices and / or tag devices can be Category 1. Category 1 tag devices may have a peak power consumption of about 1 μW (e.g., + / - 10%), may include energy storage, may have an initial sampling frequency offset (SFO) of up to 10X ppm, and may not have either DL amplification or UL amplification in the device. The uplink (UL) transmission of a Category 1 tag device may be backscattered on an externally provided carrier.

[0021] AIoT devices and / or tags can be Category 2a. Category 2a tags can have peak power consumption of less than or equal to several hundred μW, can have energy storage, can have an initial sampling frequency offset (SFO) of up to 10X ppm, and can have DL and / or UL amplification in the device. The UL transmission of Category 2a tags can be backscattered on an externally provided carrier.

[0022] Category 2b tag devices can have peak power consumption of less than or equal to several hundred μW, can have energy storage, can have an initial sampling frequency offset (SFO) of up to 10X ppm, and can have DL and / or UL amplification in the device. The UL transmission of a Category 2b tag device can be generated internally by the tag device.

[0023] The labeling device according to this disclosure may be specifically of category 1 or category 2a instead of category 2b. Alternatively, the labeling device according to this disclosure may also be of category 2b.

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

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

[0026] CW transmissions may, for example, contain no and / or lack an activation signal. For instance, a tag device may not be activated by the CW transmission. Instead, the CW transmission may (e.g., only) provide power to at least one tag device. For instance, the CW transmission may not provide information content (unless it is a single bit, depending on whether the CW transmission is active). In particular, the CW transmission may be an unmodulated and / or single-frequency (e.g., pure) sinusoidal signal. For instance, the CW transmission may reach multiple (e.g., at least 2, 3, 4, 5, 10, 20, 50, 100, 500, or 1000) tag devices. For instance, the CW transmission may be specific to at least one tag device (e.g., within the coverage area of ​​the CW transmission), for example, by the spectrum of the CW transmission and / or by the spatial region targeted by the CW transmission. For instance, the CW transmission may be non-receiver-specific. The CW transmission may be transmitted with a uniform spatial signal strength distribution and / or in an anisotropic manner, for example, shaped by at least one antenna of the CW provider. The CW transmission may, for example, be beamformed.

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

[0028] By indicating at least one CW attribute, a CW support request enables the recipient of the CW support request to derive the CW support attribute. For example, the CW attribute may be included (i.e., encoded into) by the CW support request. Additionally or alternatively, the CW attribute may be indicated by an indication that may not provide complete information about the CW attribute on its own. For example, the CW support request may include an information element that may (e.g., only) include a few (e.g., less than or equal to 1, 2, 3, 4, 5, 6, 7, or 8 bits). The recipient of the CW support request may be able to deduce the indicated CW attribute, for example, by using at least one information source (such as a table that may be internally stored in the recipient of the CW support request).

[0029] The CW attribute can specify at least one attribute of the CW transport requested by the CW support request.

[0030] By indicating at least one CW attribute in the CW support request, the CW transmission needs of the requesting entity (in particular the first device performing the method according to the first example aspect) can be matched with the CW transmission provided by the CW provider.

[0031] According to an embodiment of the first example aspect, the CW attribute includes at least one of the following: -CW transmission start time, -CW transmission end time, -CW transmission duration, - Periodic patterns of CW transmission (e.g., to account for future AIoT sessions of the activator). -CW transmission (UL or DL) spectrum, -CW transport identifier, -CW provider identifier, - Tag device location, or - Tag device identifier.

[0032] CW attributes can specify properties of CW transmissions or be at least related to properties of CW transmissions. For example, such attributes can relate to the timing of CW transmissions. For example, a CW transmission can have a start time from which it begins. The requesting entity can be able to specify when a CW transmission is needed. A CW transmission can have an associated end time. For example, the requesting entity may be able to specify when a CW transmission is needed. For example, a CW transmission can have a duration, such as a minimum duration and / or a maximum duration, during which the CW transmission remains active. Therefore, the requesting entity can specify how long it needs a CW transmission. CW attributes can also relate to the periodicity pattern of CW transmissions. For example, CW transmissions may be needed at predefined CW transmission times, where CW transmissions can be paused between CW transmission times. CW attributes can indicate the time pattern in which CW transmissions are needed. For example, the periodicity pattern of CW transmissions can configure CW transmissions for future AIoT sessions (e.g., those known or planned by the requesting entity).

[0033] CW attributes can relate to the spectrum of CW transmission, such as uplink UL and / or downlink DL spectrum and / or frequency region and / or specific (e.g., single) frequency.

[0034] CW attributes can relate to the (e.g., desired) received or transmitted signal strength or power of CW transmission.

[0035] Multiple CW attributes can be indicated by a CW support request, such as multiple (e.g., different) spectrums for corresponding multiple (e.g., different) CW transmissions.

[0036] CW attributes may also involve CW transfer identifiers. For example, the identifier may be defined by the requesting entity and may be used for future interactions between the requesting entity (e.g., to perform the method according to the first example aspect) and the second device. For example, the requesting entity may be able to reference a previously sent CW support request by means of the CW transfer identifier, such as to terminate a CW transfer and / or request the same CW transfer to a CW transfer having the indicated CW transfer identifier.

[0037] CW attributes can be associated with CW provider identifiers. For example, a requesting entity (e.g., performing a method according to the first example aspect) can be notified which CW provider is likely (e.g., best) suitable for its requested CW transport. By sending the CW provider identifier, faster identification and / or reproducible activation of the desired CW transport can be achieved, especially if the CW support request is not directly directed to the desired CW provider, but rather through an intermediary, such as a CW coordinating node.

[0038] CW attributes can also be associated with tag device location and / or tag device identifier. In some cases, the requesting entity (e.g., performing a method according to the first example aspect) expects to provide CW transmissions to one or more specific tag devices(s). By providing an indication of which tag device and / or which region of the tag device is being used, a second device can be enabled (e.g., by itself or by another device, such as a CW provider) to provide applicable CW transmissions to (multiple) tag devices(s) and / or to select an appropriate CW provider for this purpose.

[0039] According to the embodiment of the first example aspect: -The first device is a terminal device, or - The first device is a network node.

[0040] The requesting entity (e.g., executing a method according to the first example aspect) may be referred to as the first device.

[0041] The first device can be a terminal device, especially a UE.

[0042] For example, a first device (terminal device) can prevent CW transmission from being positioned relative to a given tag device in a manner that is problematic (e.g., due to obstacles, excessive distance, the spectrum required by the tag device, and / or a combination thereof). In this case, the terminal device can send a CW support request to another device (e.g., another terminal device and / or a network node) to request CW transmission to be provided to the tag device. The first device may still be able to activate the tag device itself via direct signaling (e.g., via a (e.g., wireless) communication link to the tag device).

[0043] Alternatively or concurrently, the first device may be a network node.

[0044] It has been recognized that even if the first device cannot provide CW transmission (e.g., there is sufficient signal strength in the correct spectrum at the location of the tag device), it can still transmit an activation signal to the tag device. Therefore, as long as the tag device receives CW transmission, for example, from somewhere (e.g., from a device different from the first device), the first device can successfully interact with the tag device.

[0045] In particular, network nodes may typically be unable to provide sufficiently strong CW transmission to tag devices (e.g., tag devices located inside buildings or at a distance from the network node). Meanwhile, at least one other device, particularly a terminal device, may be located near the tag device and may be able to provide CW transmission, or at least one other device, particularly a network node, may have the necessary output power and / or hardware capabilities, particularly antenna beamforming capabilities, to provide CW transmission.

[0046] According to the embodiment of the first example aspect, the second device is at least one of the following: -CW coordinating node (e.g., it does not provide CW transport itself). -CW coordinating node, where the CW coordinating node is a network node. -CW Coordination Node, where the CW Coordination Node is the User Equipment (UE). -CW provider (e.g., providing the CW transport itself). -CW provider, where the CW provider is a network node, or -CW provider, where the CW provider is the terminal device.

[0047] The second device that sends the CW support request to it may correspond to the CW coordinating node, particularly for the CW support request and / or for multiple (e.g., all) CW support requests.

[0048] A CW coordinating node may be configured, for example, to forward CW support requests to, for example, a CW provider or another CW coordinating node. A CW coordinating node may, for example, modify the CW support request and transmit the modified CW support request to another entity. For example, a CW coordinating node may not provide (e.g., any) CW transmissions and / or may at least not provide the requested CW transmissions requested by means of the CW support request. For example, a CW coordinating node may, for example, select a CW provider based on at least one CW attribute of the CW support request (e.g., for a given CW support request).

[0049] The second device can be a CW provider, particularly for CW support requests and / or for multiple (e.g., all) CW support requests. For example, the CW provider can provide (e.g., any requested) CW transmissions and / or can provide at least the requested CW transmissions requested by means of the CW support request.

[0050] A CW provider for a first CW support request can act as a CW coordinating node for a second CW support request. For example, a second device may decide (e.g., based on a received CW support request) that it will act as a CW provider and provide the CW transmission requested by way of the CW support request. Alternatively or additionally, a second device may decide (e.g., based on a received CW support request) that it will not act as a CW provider itself, but may act as a CW coordinating node and provide the CW support request to another device that may act as a CW provider.

[0051] According to the method of the first example aspect (the first device performing the method), it is unknown whether the second device is a CW provider or a CW coordinating node. Alternatively, according to the method of the first example aspect (the first device performing the method), it is known whether the second device is a CW provider or a CW coordinating node.

[0052] For example, a CW support request may depend at least in part on (or alternatively, independently of) whether the second device is a CW coordinating node or a CW provider.

[0053] CW coordinating nodes and / or CW providers can correspond to either end devices or network nodes, respectively. For example, a CW coordinating node can correspond to a network node, while a CW provider can correspond to an end device.

[0054] According to an embodiment of the first example aspect, the tag device is an environmental Internet of Things (AIoT) device.

[0055] The tag device may correspond to, for example, an environmental Internet of Things (AIoT) device. For instance, the tag device may be a category 1 or 2a AIoT device.

[0056] Therefore, the operation of the tag device can depend on CW transmission provided by another entity (specifically, a CW provider). The tag device can be configured to be activated by an activation signal, which is sent, for example, by a first means of performing and / or controlling the method according to the first example aspect. For example, the energy storage inside the tag device can be charged via CW transmission. Before the tag device is charged via CW transmission, it can be inactive and / or inactivated (i.e., not activated). The tag device can be configured to backscatter, reflect, and / or modulate the CW transmission, possibly depending on whether an activation signal has been received.

[0057] According to an embodiment of the first example aspect, at least one of the following: -CW support requests are provided as follows (e.g., the activator (a first device that performs and / or controls the method according to the first example aspect) is a terminal device (e.g., UE), and the second device is a network node (e.g., gNB)) uplink (UL) signal, - The CW support request is provided as a UL signal, wherein the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Unit (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - The CW support request is provided as follows (e.g., the activator (a first device that performs and / or controls the method according to the first example aspect) is a terminal device (e.g., a UE), and the second device is a terminal device (e.g., a UE)) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -CW support requests are provided as follows (e.g., the activator (a first device that performs and / or controls the method according to the first example aspect) is a network node (e.g., a gNB), and the second device is a network node (e.g., a gNB)) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP). -CW support requests are provided as follows (e.g., the activator (a first device that performs and / or controls the method according to the first example aspect) is a network node (e.g., gNB), and the second device is a terminal device (e.g., UE)) downlink (DL) signal, or -CW support requests are provided as DL signals, wherein the DL signals are provided via at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0058] CW support requests can be sent (e.g., transmitted and / or provided) via a communication link between devices (e.g., wireless and / or wired). The method used may vary depending on the type of device involved.

[0059] For example, the first apparatus performing the method according to the first example aspect may correspond to a terminal device, such as a UE, and / or the second apparatus may correspond to a network node, such as a gNB or a network node hosting core network (CN) functions. For example, in this combination of apparatus types, but not only there, a CW support request may be provided as an uplink (UL) signal, particularly a UL signal of one or a combination of the following types: A UL signal may, for example, correspond to an uplink scheduling request (UL SR). Additionally or alternatively, a UL signal may, for example, correspond to a Media Access Control (MAC) control element (MAC CE). Additionally or alternatively, a UL signal may, for example, correspond to Radio Resource Control (RRC) signaling. Additionally or alternatively, a UL signal may, for example, correspond to Non-Access Stratum (NAS) signaling.

[0060] For example, both the first and second devices performing the method according to the first example aspect can correspond to corresponding (e.g., different from each other) terminal devices, such as UEs. For example, in this combination of device types, but not only there, CW support requests can be provided as one or a combination of the following types: CW support requests can be provided by means of a dedicated physical layer sequence (PHY sequence). Additionally or alternatively, CW support requests can be provided by means of sidelink control information (SCI) (especially specific fields in, for example, first-phase and / or second-phase SCI information). Additionally or alternatively, CW support requests can be provided by means of sidelink media access control elements (SL MAC CE) and / or sidelink RRC signaling and / or PC5 signaling.

[0061] For example, the first and second devices performing the method according to the first example aspect can both correspond to corresponding (e.g., different from each other) network nodes, such as gNBs or network nodes hosting CN functions. For example, in this combination of device types, but not only there, CW support requests can be provided as one or a combination of the following types: CW support requests can be provided by means of Xn signaling. Additionally or alternatively, CW support requests can be provided by means of F1 signaling. Additionally or alternatively, CW support requests can be provided by means of signaling on the fronthaul link (e.g., if the CW provider is a specific Transmitter Receiving Point (TRP)).

[0062] For example, the first device performing the method according to the first exemplary aspect may correspond to a network node (e.g., a gNB or a network node hosting CN functionality), and / or the second device may correspond to a terminal device (e.g., a UE). For example, in this combination of device types, but not only there, a CW support request may be provided as an uplink DL signal, particularly a DL signal of one or a combination of the following types: A DL signal may, for example, correspond to downlink control information (DCI). Additionally or alternatively, a DL signal may, for example, correspond to MAC CE. Additionally or alternatively, a DL signal may, for example, correspond to RRC signaling. Additionally or alternatively, a DL signal may, for example, correspond to MAC CE. Additionally or alternatively, a DL signal may, for example, correspond to NAS signaling.

[0063] According to an embodiment of the first example aspect, the method further includes: - Obtain a CW support response (e.g., ACK / NACK) to the CW support request from the second device.

[0064] A CW support response may enable the requesting entity (e.g., a first device, such as performing a method according to a first example aspect) to be notified whether the CW support request was successful, for example, whether it resulted in the requested CW transfer, or whether the CW support request failed. Additionally or alternatively, the CW support response may notify the requesting entity of attributes of the CW transfer, attributes of the CW provider (e.g., identifier), and / or combinations thereof.

[0065] According to an embodiment of the first example aspect, the CW support response is configured to indicate at least one of the following: - Successful CW transfer, - Failed CW transfer, -CW transmission start time, -CW transmission end time, -CW transmission duration, - Minimum waiting time (e.g., before the activation signal is sent by the first device). -CW transport identifier, or -CW provider identifier.

[0066] A CW support response may indicate attributes of the CW transmission (e.g., CW attributes), the CW provider, and / or other information that may be related, for example, to the requesting entity that sent the CW support request. For example, the CW transmission (e.g., CW) attributes may be an indication of a successful or failed CW transmission. Additionally or alternatively, a CW support response may indicate a failed (no CW transmission) and / or successful (CW transmission provided) CW support request.

[0067] CW support responses may additionally or alternatively indicate at least one time attribute of the CW transmission, such as the CW transmission start time, end time, and / or duration. For example, the requesting entity may be notified of the time when it can interact with at least one tag device.

[0068] The CW support response may additionally or alternatively indicate, for example, a (minimum) waiting time between the subsequent transmission of the CW support request and the activation signal.

[0069] The CW support response may additionally or alternatively indicate a CW transport identifier, which may, for example, uniquely identify the requested and / or provided CW transport, such as to refer to (e.g., deactivate) a CW transport in a later stage. The CW support response may additionally or alternatively include an indication of a CW provider identifier (e.g., the CW provider, for example, different from or the same as the second device).

[0070] According to an embodiment of the first example aspect, the method further includes: - Provide an activation signal to at least one of at least one tag device (AIoT device), for example, in response to providing a CW request to a second device and / or after providing a CW request to the second device (after a predefined time)).

[0071] The activation signal can be sent (e.g., transmitted and / or provided) to at least one tag device. For example, the activation signal can be provided by means of (e.g., wireless) communication links.

[0072] The activation signal may differ from carrier transmission, for example. In particular, the activation signal may not be suitable for implementing the function of the carrier. For example, the activation signal may be transmitted for a period of time that is too short for CW transmission; the activation signal may be time-varying; the activation signal may be in a spectrum unsuitable for the carrier; the activation signal may be below the minimum signal strength, especially at the location of the tag device; the activation signal may have a wide spectrum, for example, due to modulation of the carrier frequency; and the activation signal may carry at least one piece of information, such as an identifier of the tag device and / or a command pointing to the tag device and / or a combination thereof.

[0073] The activation signal can (e.g., only) target one or more (e.g., at least 2, 3, 4, 5, 10, 20, 50, 100) tag devices.

[0074] According to an embodiment of the first example aspect, at least one of the following: - The activation signal is configured to elicit a backscatter response from the tag device (e.g., to a first device, a second device, or a third device (reader)). - The activation signal is specific to the tag device (e.g., it includes ID, matching frequency). - Send an activation signal during an ongoing (e.g., requested) CW transmission. - The activation signal indicates the (e.g., a predefined) delay (e.g., a wait time) between the reception of the activation signal and activation, or - An activation signal is provided with at least one of the following: -In response to a request to provide CW support - In response to receiving a CW support response to a CW support request, or - After a predefined time following the submission of a CW support request.

[0075] An activation signal can be configured to elicit a backscatter response from (e.g., at least one or more) tag devices. The backscatter response can be at least partially based on the provided CW transmission. The tag device can, for example, backscatter the CW transmission upon receiving the activation signal. For example, the tag device can receive the activation signal when a CW transmission (e.g., a CW transmission requested by a CW support request) is active, and can backscatter the CW transmission after receiving the activation signal (e.g., in response to receiving the activation signal). The backscatter response can be received, for example, by a first device (e.g., a requesting entity and / or performing a method according to a first example aspect), by a second device (e.g., a CW provider and / or a CW coordinating node), and / or by a third device (e.g., a reader device), which can be, for example, different from the first and / or second devices.

[0076] The activation signal can be specific to (e.g., target) the tag device, particularly the tag device to which the activation signal is sent. For example, for this purpose, the activation signal can be transmitted in a specific spectrum (e.g., UL or DL ​​and / or a specific frequency range) in a specific area, and / or can contain an indication or identifier of the tag device.

[0077] The activation signal can be sent during (e.g., an ongoing) CW transmission, such as a (e.g., a previously requested) CW transmission, for example, by means of (e.g., a sent) CW support request. Since the tag device may be passive, the current active CW transmission is required to generate a backscatter response to at least one other device (e.g., a reader).

[0078] The activation signal may, for example, indicate a (e.g., a predefined) delay (e.g., a waiting time, for example, for a tag device) between the reception and activation of the activation signal, or the time when the CW transmission should be activated.

[0079] The activation signal may be sent, for example, in response to a CW support request (e.g., transmission and / or provision). For instance, the method may include sending a CW support request and subsequently transmitting the activation signal, for example, after a predefined time and / or after waiting for at least a minimum predefined time. Sending the activation signal after sending the CW support request ensures that activation of the tag device (e.g., a backscatter response) is possible, since the tag device may not be activated before it is charged and / or unless CW transmission is available.

[0080] An activation signal may be sent, for example, in response to receiving a CW support response to a CW support request. For example, an activation signal may be conditionally sent upon receiving a (e.g., affirmative) CW support response to a CW support request. For example, sending an activation signal and / or an activation signal (e.g., content, spectrum, timing of the activation signal, information indicated by the activation signal) may be conditional on the content of the CW support response. For example, a CW support response may indicate a successful or failed CW support request. If a successful CW support request is indicated, an activation signal may be sent (e.g., only), but if a failed CW support request is indicated, no activation signal is sent. For example, a CW support response may indicate at least one CW attribute of a CW transmission (e.g., duration, start time, and / or end time). Activation signals may be sent and / or configured at least in part based on the CW attributes indicated by the CW support response. For example, an activation signal may be sent once during which time, for example, according to the CW support response, a CW transmission (e.g., still) is in progress. The CW response may indicate (e.g., a minimum) waiting time. An activation signal may be sent after (for example, a minimum) waiting time has elapsed. The sending and / or configuration of the activation signal may also depend on the CW transport identifier and / or CW provider identifier indicated by the CW support response.

[0081] For example, an activation signal can be sent after a predefined time following the provision of a CW support request. For example, the length of the predefined time can be set to ensure that the tag device is charged when the activation signal is sent. For example, the predefined time can be the same for all tag devices to which the method can send activation signals. Additionally or alternatively, the predefined waiting time can be specific to the tag device (e.g., the type of tag device), for example, based on charging duration.

[0082] According to an embodiment of the first example aspect, the method of the first example aspect further includes the following steps. Additionally, according to the second example aspect, a method (e.g., executed and / or controlled by a first device (e.g., a network node or a UE)) is disclosed, comprising: - To (e.g., to) a second device (CW coordinating node or CW provider, rather than an AIoT device) provide (e.g., transmit) a CW deactivation request, which requests deactivation to provide at least one (e.g., multiple or all) carriers to at least one (e.g., the at least one) tag device (AIoT device).

[0083] The method can be performed and / or controlled, for example, by a device (e.g., a server). Alternatively, the method can be performed and / or controlled by more than one device, such as a server cloud comprising at least two servers. Alternatively, the method can be performed and / or controlled, for example, by an electronic device (e.g., a node in a communication system) and / or a terminal device (e.g., a user equipment (UE)). For example, the method can be performed and / or controlled by using at least one processor of an electronic device.

[0084] According to another example aspect, a computer program is disclosed that, when executed by a processor, causes a device (e.g., a server, network node, or terminal device, such as a UE) to perform and / or control actions according to the method of the first example aspect.

[0085] Computer programs can be stored on computer-readable storage media, particularly tangible and / or non-transitory media. Computer-readable storage media can be, for example, disks or memory. Computer programs can be stored in computer-readable storage media in the form of instructions encoding the computer-readable storage media. Computer-readable storage media can be intended to participate in the operation of a device, such as internal or external memory, such as a computer's read-only memory (ROM) or hard disk, or intended for program distribution, such as optical discs.

[0086] According to another example aspect, an apparatus is disclosed that is configured to perform and / or control or includes corresponding components for performing and / or controlling the method according to the first example aspect.

[0087] The components of the device can be implemented in hardware and / or software. They may include, for example, at least one processor for executing computer program code to achieve the desired function, at least one memory for storing the program code, or both. Alternatively, they may include, for example, circuitry designed to achieve the desired function, such as circuitry implemented in a chipset or chip (e.g., an integrated circuit). Typically, the component may include, for example, one or more processing components or processors.

[0088] The apparatus disclosed above according to any aspect may be a module or component for a device (e.g., a chip). Alternatively, the apparatus disclosed according to any aspect may be a device, such as a server or server cloud. The apparatus disclosed according to any aspect may include (e.g., only) the disclosed components, such as parts, processors, memory, or may also include one or more additional components.

[0089] CW deactivation requests can be configured to request and subsequently provide one or more CW transmissions continuously, for example, until a CW deactivation request is sent and / or received. Therefore, less signaling (e.g., a lower frequency of CW support requests) is required while keeping the system's energy consumption low, since CW transmissions can be deactivated at any time.

[0090] A CW deactivation request can be configured to deactivate at least one (e.g., an ongoing) CW transmission. For example, a CW deactivation request can be specific to at least one of a CW transmission, a CW provider, a CW coordinating node, or one or more tag devices.

[0091] CW deactivation requests can be configured to deactivate one or more (e.g., ongoing) CW transports, such as (e.g., all) CW transports of a given CW provider and / or CW transports coordinated by a given CW coordinator.

[0092] CW deactivation requests can be configured to (e.g., substantially) deactivate CW transmissions immediately and / or after a predefined time. For example, CW deactivation can indicate a delay between the sending and / or receiving of a CW deactivation request and the deactivation of a CW transmission, or the time when a CW transmission should be deactivated.

[0093] A CW deactivation request may be sent (e.g., provided and / or transmitted) to a second device, such as (e.g., a device to which a CW support request has previously been sent, for example, by the same entity that sent the CW activation request (e.g., the first device). The second device may be a CW provider and / or a CW coordinating node. The second device may be specifically different from the AIoT device.

[0094] According to the embodiments of the first and / or second example aspects: - The CW deactivation request is configured to indicate at least one CW attribute of the CW transfer to be deactivated by the CW provider.

[0095] By indicating at least one CW attribute of the CW transport, a CW deactivation request can deactivate a specific CW transport and / or a group of CW transports.

[0096] According to the embodiments of the first and / or second example aspects, the CW attribute includes at least one of the following: - The duration of the CW transmission (e.g., remaining time). -CW transmission spectrum (e.g., UL or DL). - (e.g., the previously provided) CW transport identifier, or -CW provider identifier.

[0097] The CW attribute indicated by the CW deactivation request may, for example, correspond to the CW transmission duration. For instance, only CW transmissions with a duration greater than a predefined duration threshold can be deactivated.

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

[0099] The CW attribute indicated by the CW deactivation request may, for example, correspond to a CW transport identifier. Therefore, the CW deactivation request can be targeted at a specific CW transport.

[0100] The CW attributes indicated by the CW deactivation request may, for example, correspond to a CW provider identifier. Therefore, the CW deactivation request may be for at least one, more, or all CW transports provided by the specified CW provider identifier.

[0101] According to the embodiments of the first and / or second example aspects: -CW deactivation request is (e.g., the deactivator (a first means of performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), and the second means is a network node (e.g., gNB)) uplink (UL) signal, -CW deactivation request is an uplink (UL) signal, wherein the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - The CW deactivation request is (e.g., the deactivator (a first device that performs and / or controls the method according to the first example aspect) is a terminal device (e.g., UE), and the second device is a terminal device (e.g., UE)) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - The CW deactivation request is (e.g., the deactivator (a first device that performs and / or controls the method according to the first example aspect) is a network node (e.g., a gNB), and the second device is a network node (e.g., a gNB)) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP). -CW deactivation request is (e.g., the deactivator (a first means of performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), and the second means is a terminal device (e.g., UE)) downlink (DL) signal, or The CW deactivation request is a DL signal, where the DL signal is at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0102] CW deactivation requests can be sent (e.g., transmitted and / or provided) via a communication link between devices (e.g., wireless and / or wired). The method used can vary depending on the type of device involved.

[0103] For example, the first apparatus performing the method according to the first example aspect may correspond to a terminal device, such as a UE, and / or the second apparatus may correspond to a network node, such as a gNB or a network node hosting core network (CN) functions. For example, in this combination of apparatus types, but not only there, a CW deactivation request may be provided as an uplink (UL) signal, particularly a UL signal of one or a combination of the following types: A UL signal may, for example, correspond to an uplink scheduling request (UL SR). Additionally or alternatively, a UL signal may, for example, correspond to a Media Access Control (MAC) control element (MAC CE). Additionally or alternatively, a UL signal may, for example, correspond to Radio Resource Control (RRC) signaling. Additionally or alternatively, a UL signal may, for example, correspond to Non-Access Stratum (NAS) signaling.

[0104] For example, both the first and second devices performing the method according to the first example aspect can correspond to corresponding (e.g., different from each other) terminal devices, such as UEs. For example, in this combination of device types, but not only in this case, the CW deactivation request can be provided as one or a combination of the following types: The CW deactivation request can be provided by means of a dedicated physical layer sequence (PHY sequence). Additionally or alternatively, the CW deactivation request can be provided by means of sidelink control information (SCI) (especially specific fields in, for example, the first-phase and / or second-phase SCI information). Additionally or alternatively, the CW deactivation request can be provided by means of a sidelink media access control element (SL MAC CE) and / or sidelink RRC signaling and / or PC5-RRC signaling.

[0105] For example, both the first and second devices performing the method according to the first example aspect can correspond to corresponding (e.g., different from each other) network nodes, such as gNBs or network nodes hosting CN functions. For example, in this combination of device types, but not only there, the CW deactivation request can be provided as one or a combination of the following types: The CW deactivation request can be provided by means of Xn signaling. Additionally or alternatively, the CW deactivation request can be provided by means of F1 signaling. Additionally or alternatively, the CW deactivation request can be provided by means of signaling on the fronthaul link (e.g., if the CW provider is a specific transport receiving point (TRP)).

[0106] For example, the first device performing the method according to the first exemplary aspect may correspond to a network node (e.g., a gNB or a network node hosting CN functionality), and / or the second device may correspond to a terminal device (e.g., a UE). For example, in this combination of device types, but not only there, a CW deactivation request may be provided as an uplink DL signal, particularly a DL signal of one or a combination of the following types: The DL signal may, for example, correspond to downlink control information (DCI). Additionally or alternatively, the DL signal may, for example, correspond to MAC CE. Additionally or alternatively, the DL signal may, for example, correspond to RRC signaling. Additionally or alternatively, the DL signal may, for example, correspond to MAC CE. Additionally or alternatively, the DL signal may, for example, correspond to NAS signaling.

[0107] According to embodiments of the first and / or second example aspects, the method further includes: - Obtain a deactivation response (e.g., CW) to the CW deactivation request (e.g., ACK / NACK) from the second device.

[0108] A (CW) deactivation response can enable a deactivation entity (e.g., a first device, such as performing a method according to the first and / or second example aspects) to be notified whether a CW deactivation request was successful, such as whether it resulted in the deactivation of at least one or more CW transmissions, or whether the CW deactivation request failed. Additionally or alternatively, the CW deactivation response can notify the deactivation entity of attributes of the CW transmission (e.g., remaining duration), attributes of the CW provider (e.g., identifier), and / or combinations thereof.

[0109] According to the third example aspect, a method is proposed (e.g., executed and / or controlled by a second device (e.g., a CW provider, such as a network node or terminal device (e.g., a UE))) including: - Obtain (e.g., receive) a CW support request from the requesting party (e.g., from the first device or from the CW coordinating node), and - In response to a request for CW support, at least one CW transmission is provided to at least one tag device (e.g., unlike the device performing the method, it has no activation signal).

[0110] The method can be performed and / or controlled, for example, by a device (e.g., a server). Alternatively, the method can be performed and / or controlled by more than one device, such as a server cloud comprising at least two servers. Alternatively, the method can be performed and / or controlled, for example, by an electronic device (e.g., a node in a communication system) and / or a terminal device (e.g., a user equipment (UE)). For example, the method can be performed and / or controlled using at least one processor of an electronic device.

[0111] According to another example aspect, a computer program is disclosed that, when executed by a processor, causes a device (e.g., a server, network node, or terminal device, such as a UE) to perform and / or control actions according to the method of the first example aspect.

[0112] Computer programs can be stored on computer-readable storage media, particularly tangible and / or non-transitory media. Computer-readable storage media can be, for example, disks or memory. Computer programs can be stored in computer-readable storage media in the form of instructions encoding the computer-readable storage media. Computer-readable storage media can be intended to participate in the operation of a device, such as internal or external memory, such as a computer's read-only memory (ROM) or hard disk, or intended for program distribution, such as optical discs.

[0113] According to another example aspect, an apparatus is disclosed that is configured to perform and / or control or includes corresponding components for performing and / or controlling the method according to the first example aspect.

[0114] The components of the device can be implemented in hardware and / or software. They may include, for example, at least one processor for executing computer program code to achieve the desired function, at least one memory for storing the program code, or both. Alternatively, they may include, for example, circuitry designed to achieve the desired function, such as circuitry implemented in a chipset or chip (e.g., an integrated circuit). Typically, the component may include, for example, one or more processing components or processors.

[0115] The apparatus disclosed above according to any aspect may be a module or component for a device (e.g., a chip). Alternatively, the apparatus disclosed according to any aspect may be a device, such as a server or server cloud. The apparatus disclosed according to any aspect may include (e.g., only) the disclosed components, such as parts, processors, memory, or may also include one or more additional components.

[0116] The requesting party may correspond, for example, to the first device, and perform the method according to the first example aspect. Additionally or alternatively, the requesting party may correspond, for example, to a CW coordinating node, wherein the CW coordinating node has, for example, received (e.g., the) CW support request from the first device, and performs the method according to the first example aspect.

[0117] The CW provider may be located near at least one tagging device.

[0118] CW providers can additionally perform the role of CW coordinating nodes, for example, for different (future or past) CW support requests.

[0119] According to the embodiment of the third example aspect: -The CW provider is the terminal device, or -CW providers are network nodes.

[0120] According to the embodiment of the third example aspect: CW support requests are configured to indicate at least one CW attribute to be provided by the CW provider for CW transmission.

[0121] According to the embodiment of the third example aspect, the CW attribute includes at least one of the following: -CW transmission start time, -CW transmission end time, -CW transmission duration, - Periodic patterns of CW transmission (e.g., to account for future AIoT sessions of the activator). -CW transmission (UL or DL) spectrum, -CW transport identifier, -CW provider identifier, - Tag device location, or - Tag device identifier.

[0122] For example, a CW support request may indicate (and / or specify) (e.g., desired) at least one CW attribute of the CW transfer.

[0123] A CW provider implementing the method according to the third example aspect may provide CW transmission based at least in part on a CW support request, and in particular on at least one CW attribute indicated by the CW support request.

[0124] The provided CW transport may, for example, correspond at least in one of its CW attributes to the indicated CW attribute as indicated by the CW support request.

[0125] According to an embodiment of the third example aspect, the method further includes: - Provide the requesting party with a CW support response to the CW support request (e.g., ACK / NACK).

[0126] According to an embodiment of the third example aspect, the CW support response is configured to indicate at least one of the following: - Successful CW transfer, - Failed CW transfer, -CW transmission start time, -CW transmission end time, -CW transmission duration, - Minimum waiting time (e.g., before the activation signal is sent by the first device). -CW transport identifier, or -CW provider identifier.

[0127] According to the embodiment of the third example aspect: - The CW support request is obtained as follows (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), and the CW provider is a network node (e.g., gNB)) uplink (UL) signal. -CW support requests are obtained as uplink (UL) signals, where the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Unit (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - A CW support request is obtained if (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., a UE), and the CW provider is a terminal device (e.g., a UE)) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - A CW support request is obtained as follows (e.g., the requesting party (e.g., a first device that performs and / or controls the method according to the first example aspect) is a network node (e.g., a gNB), and the CW provider is a network node (e.g., a gNB)) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP) -CW support requests are obtained as follows (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), and the CW provider is a terminal device (e.g., UE)) downlink (DL) signal, or -CW support requests are obtained as DL signals, where a DL signal is at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0128] According to an embodiment of the first example aspect, the method of the third example aspect further includes the following steps; additionally, according to the fourth example aspect, a method is disclosed (e.g., executed and / or controlled by a second device (e.g., a CW provider, such as a network node or terminal device (e.g., a UE))) including: - A component used to obtain a CW deactivation request (e.g., from a first device or from a CW coordinating node).

[0129] The method can be performed and / or controlled, for example, by a device (e.g., a server). Alternatively, the method can be performed and / or controlled by more than one device, such as a server cloud comprising at least two servers. Alternatively, the method can be performed and / or controlled, for example, by an electronic device (e.g., a node in a communication system) and / or a terminal device (e.g., a user equipment (UE)). For example, the method can be performed and / or controlled by using at least one processor of an electronic device.

[0130] According to another example aspect, a computer program is disclosed that, when executed by a processor, causes a device (e.g., a server, network node, or terminal device, such as a UE) to perform and / or control actions according to the method of the first example aspect.

[0131] Computer programs can be stored on computer-readable storage media, particularly tangible and / or non-transitory media. Computer-readable storage media can be, for example, disks or memory. Computer programs can be stored in computer-readable storage media in the form of instructions encoding the computer-readable storage media. Computer-readable storage media can be intended to participate in the operation of a device, such as internal or external memory, such as a computer's read-only memory (ROM) or hard disk, or intended for program distribution, such as optical discs.

[0132] According to another example aspect, an apparatus is disclosed that is configured to perform and / or control or includes corresponding components for performing and / or controlling the method according to the first example aspect.

[0133] The components of the device can be implemented in hardware and / or software. They may include, for example, at least one processor for executing computer program code to achieve the desired function, at least one memory for storing the program code, or both. Alternatively, they may include, for example, circuitry designed to achieve the desired function, such as circuitry implemented in a chipset or chip (e.g., an integrated circuit). Typically, the component may include, for example, one or more processing components or processors.

[0134] The apparatus disclosed above according to any aspect may be a module or component for a device (e.g., a chip). Alternatively, the apparatus disclosed according to any aspect may be a device, such as a server or server cloud. The apparatus disclosed according to any aspect may include (e.g., only) the disclosed components, such as parts, processors, memory, or may also include one or more additional components.

[0135] A CW deactivation request can cause a CW provider to deactivate at least one of its (e.g., ongoing) CW transmissions. The CW transmission may have been previously requested via a CW support request (e.g., by the same requester from which the deactivation request was obtained or by a different requester).

[0136] According to the embodiments of the third and / or fourth example aspects: - The CW deactivation request is obtained as follows (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), and the CW provider is a network node (e.g., gNB)) uplink (UL) signal. - The CW deactivation request is obtained as an uplink (UL) signal, wherein the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - A CW deactivation request is obtained if (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., a UE), and the CW provider is a terminal device (e.g., a UE)) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - A CW deactivation request is obtained as follows (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a network node (e.g., a gNB), and the CW provider is a network node (e.g., a gNB)) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP) - The CW deactivation request is obtained as follows (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), and the CW provider is a terminal device (e.g., UE)) downlink (DL) signal, or - The CW deactivation request is obtained as a DL signal, where the DL signal is at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0137] According to the embodiments of the third and / or fourth example aspects: - The CW deactivation request is configured to indicate at least one CW attribute of the CW transfer to be deactivated by the CW provider.

[0138] A CW provider may, for example, deactivate at least one (e.g., an ongoing CW transfer) based on at least one indicated CW attribute.

[0139] According to the embodiments of the third and / or fourth example aspects, the CW attribute includes at least one of the following: -CW transmission duration, -CW transmission spectrum (e.g., UL or DL). - (e.g., the previously provided) CW transport identifier, or -CW provider identifier.

[0140] A CW provider may, for example, deactivate a (e.g., ongoing) CW transmission having a spectrum within the indicated spectrum of the CW transmission and / or having an identifier corresponding to the indicated CW transmission identifier. Additionally or alternatively, in the case where a CW provider receives a CW deactivation request, for example if the CW provider identifier indicated by the CW deactivation request corresponds to the CW provider's own CW provider identifier, the CW provider may deactivate at least one, several, or all of the (e.g., ongoing) CW transmissions it provides.

[0141] According to embodiments of the third and / or fourth example aspects, the method further includes: - Deactivate the provided CW transport in response to at least one of the following: - Locally observed conditions (e.g., predefined time elapsed) or - Obtain a CW deactivation request (e.g., depending on the attributes of the CW transfer indicated by the CW deactivation request).

[0142] For example, a provided CW transmission can be deactivated (e.g., in progress).

[0143] Such deactivation of the provided CW transmission can be, for example, conditional and / or in response to locally observed conditions. Such locally observed conditions may correspond, for example, to a predefined time, such as the duration of a CW transmission indicated by a previously obtained (e.g., received) CW support request, where the CW support request has been configured to provide a CW transmission to be deactivated.

[0144] For example, a provided CW transport can be deactivated based on (e.g., in response to) a CW deactivation request. For example, deactivation can be based on at least one attribute indicated by the CW deactivation request and / or on (e.g., attributes of the deactivated CW transport).

[0145] According to the fifth example aspect, a method is proposed (e.g., executed and / or controlled by a second device (e.g., a CW coordination node, such as a terminal device (e.g., a UE) and / or a network node)) comprising: - Obtain (e.g., receive) a CW support request from the first device, and - In response to a CW support request, provide the selected CW support provider with a CW support request or an additional CW support request derived from the CW support request (e.g., the obtained CW support request or a derived CW support request based on the obtained CW support request).

[0146] The method can be performed and / or controlled, for example, by a device (e.g., a server). Alternatively, the method can be performed and / or controlled by more than one device, such as a server cloud comprising at least two servers. Alternatively, the method can be performed and / or controlled, for example, by an electronic device (e.g., a node in a communication system) and / or a terminal device (e.g., a user equipment (UE)). For example, the method can be performed and / or controlled by using at least one processor of an electronic device.

[0147] According to another example aspect, a computer program is disclosed that, when executed by a processor, causes a device (e.g., a server, network node, or terminal device, such as a UE) to perform and / or control actions according to the method of the first example aspect.

[0148] Computer programs can be stored on computer-readable storage media, particularly tangible and / or non-transitory media. Computer-readable storage media can be, for example, disks or memory. Computer programs can be stored in computer-readable storage media in the form of instructions encoding the computer-readable storage media. Computer-readable storage media can be intended to participate in the operation of a device, such as internal or external memory, such as a computer's read-only memory (ROM) or hard disk, or intended for program distribution, such as optical discs.

[0149] According to another example aspect, an apparatus is disclosed that is configured to perform and / or control or includes corresponding components for performing and / or controlling the method according to the first example aspect.

[0150] The components of the device can be implemented in hardware and / or software. They may include, for example, at least one processor for executing computer program code to achieve the desired function, at least one memory for storing the program code, or both. Alternatively, they may include, for example, circuitry designed to achieve the desired function, such as circuitry implemented in a chipset or chip (e.g., an integrated circuit). Typically, the component may include, for example, one or more processing components or processors.

[0151] The apparatus disclosed above according to any aspect may be a module or component for a device (e.g., a chip). Alternatively, the apparatus disclosed according to any aspect may be a device, such as a server or server cloud. The apparatus disclosed according to any aspect may include (e.g., only) the disclosed components, such as parts, processors, memory, or may also include one or more additional components.

[0152] The method of the fifth example aspect can 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 can, for example, be configured to coordinate between a requesting party (e.g., another CW coordinating node and / or a first device performing and / or coordinating the method according to the first or second example aspect) and a CW provider (e.g., performing and / or coordinating the method according to the third or fourth example aspect). Based on a received CW support request, the CW coordinating node may not provide CW transmission and / or the CW coordinating node may (e.g., at least) not provide the requested CW transmission. Instead, the CW coordinating node may send the obtained CW support request (or another CW support request based on the obtained CW support request) to a selected CW provider, which in turn may provide the requested CW transmission. This additional support request may, for example, include at least one indication not present in the obtained CW support request, such as an identifier of the selected CW provider.

[0153] According to an embodiment, a CW coordinating node may provide a CW support request to another CW coordinating node instead of a CW provider. Additionally or alternatively, a CW provider may become a CW coordinating node, for example, if it is unable to provide (e.g., another) the CW transmission requested by the CW support request.

[0154] According to the fifth example aspect of the embodiment: -The CW coordinating node is an end device, or -CW coordinating nodes are network nodes.

[0155] According to the fifth example aspect of the embodiment: CW support requests are configured to indicate at least one CW attribute to be provided by the CW provider for CW transmission.

[0156] According to an embodiment of the fifth example aspect, the CW attribute includes at least one of the following: -CW transmission start time, -CW transmission end time, -CW transmission duration, - Periodic patterns of CW transmission (e.g., to account for future AIoT sessions of the activator). -CW transmission (UL or DL) spectrum, -CW transport identifier, -CW provider identifier, - Tag device location, or - Tag device identifier.

[0157] At least one CW attribute can be defined by the CW coordinating node.

[0158] Alternatively or concurrently, the CW coordinating node may select the chosen CW provider based at least in part on at least one of the CW attributes indicated by the CW support request.

[0159] According to an embodiment of the fifth example aspect, the method further includes: - Select a CW provider (e.g., based on a CW support request (e.g., CW provider identifier, tag location / identifier, and / or another attribute indicated in the CW support request) based on at least one CW attribute indicated by it).

[0160] The CW provider can be selected, at least in part, based on the obtained CW support request. For example, the CW provider can be selected based on at least one CW attribute indicated by the CW support request.

[0161] For example, a CW provider can be selected based on a CW provider identifier. For instance, a CW provider with an identifier corresponding to the indicated CW provider identifier can be selected as the chosen CW provider.

[0162] Alternatively or additionally, the selected CW provider may be selected based at least in part on the tag location and / or tag identifier indicated by the CW support request. For example, the location of the CW provider may be matched with the location of the tag device (e.g., as indicated by the CW support request and / or derived based on the tag device identifier (e.g., indicated by the CW support request)). For example, it may be determined whether the maximum distance between the tag device and the CW provider has not been exceeded.

[0163] The selection of the chosen CW provider can be based on at least one or more (e.g., other) attributes indicated in the CW support request.

[0164] According to an embodiment, a CW support request may not require an instruction from a CW provider. In this case, the CW coordinating node may be responsible for selecting a suitable CW provider, for example, based on at least one or more CW attributes indicated in the CW support request.

[0165] According to an embodiment of the fifth example aspect, the method further includes: - A component for providing a CW support response (e.g., ACK / NACK) to a first device for a CW support request.

[0166] For example, a CW support response may indicate the success or failure of a selection of a CW provider and / or the success or failure of a CW transmission (e.g., initiated by the selected CW provider).

[0167] According to an embodiment of the fifth example aspect, the CW support response is configured to indicate at least one of the following: - Successful CW transfer, - Failed CW transfer, -CW transmission start time, -CW transmission end time, -CW transmission duration, - Minimum waiting time (e.g., before the activation signal is sent by the first device). -CW transport identifier, or -CW provider identifier.

[0168] According to an embodiment, the method includes, for example, obtaining (e.g., receiving) (e.g., providing to a first device) a CW support response from a selected CW provider, which includes at least one of the attributes described above. For example, if the CW coordinating node receives a negative CW response (e.g., a failed CW transmission), the CW coordinating node may try at least one other CW provider.

[0169] According to the fifth example aspect of the embodiment: - The CW support request is obtained as follows [for example, the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., UE), and the CW coordinating node is a network node (e.g., gNB)] uplink (UL) signal, -CW support requests are obtained as uplink (UL) signals, where the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - A CW support request is obtained if (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a terminal device (e.g., a UE), and the CW coordination node is a terminal device (e.g., a UE)) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - A CW support request may be obtained as (e.g., the requesting party (e.g., a first device that performs and / or controls the method according to the first example aspect) is a network node (e.g., a gNB), and the CW coordination node is a network node (e.g., a gNB)) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP) -CW support requests are obtained as follows (e.g., the requesting party (e.g., a first device performing and / or controlling the method according to the first example aspect) is a network node (e.g., gNB), and the CW coordinating node is a terminal device (e.g., UE)) downlink (DL) signal or -CW support requests are obtained as DL signals, where a DL signal is at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0170] According to the fifth example aspect of the embodiment: -CW support requests are provided as (e.g., the CW coordinating node is the terminal device (e.g., UE), and the CW provider is the network node (e.g., gNB)) uplink (UL) signals. -CW support requests are provided as uplink (UL) signals, where the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - A CW support request is provided as (e.g., the CW coordinating node is a terminal device (e.g., UE), and the CW provider is a terminal device (e.g., UE)) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - A CW support request is provided as (e.g., the CW coordinating node is a network node (e.g., gNB), and the CW provider is a network node (e.g., gNB)) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP) -CW support requests are provided as (e.g., the CW coordinating node is a network node (e.g., gNB), and the CW provider is a terminal device (e.g., UE)) downlink (DL) signals, or -CW support requests are provided as DL signals, where a DL signal is at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0171] According to an embodiment of the fifth example aspect, the method further includes the following steps; additionally, according to the sixth example aspect, a method (e.g., executed and / or controlled by a second device (e.g., a CW coordinator, such as a network node or a terminal device (e.g., a UE))) is disclosed, comprising: - Receive a CW deactivation request (e.g., from the first device).

[0172] The method can be performed and / or controlled, for example, by a device (e.g., a server). Alternatively, the method can be performed and / or controlled by more than one device, such as a server cloud comprising at least two servers. Alternatively, the method can be performed and / or controlled, for example, by an electronic device (e.g., a node in a communication system) and / or a terminal device (e.g., a user equipment (UE)). For example, the method can be performed and / or controlled by using at least one processor of an electronic device.

[0173] According to another example aspect, a computer program is disclosed that, when executed by a processor, causes a device (e.g., a server, network node, or terminal device, such as a UE) to perform and / or control actions according to the method of the first example aspect.

[0174] Computer programs can be stored on computer-readable storage media, particularly tangible and / or non-transitory media. Computer-readable storage media can be, for example, disks or memory. Computer programs can be stored in computer-readable storage media in the form of instructions encoding the computer-readable storage media. Computer-readable storage media can be intended to participate in the operation of a device, such as internal or external memory, such as a computer's read-only memory (ROM) or hard disk, or intended for program distribution, such as optical discs.

[0175] According to another example aspect, an apparatus is disclosed that is configured to perform and / or control or includes corresponding components for performing and / or controlling the method according to the first example aspect.

[0176] The components of the device can be implemented in hardware and / or software. They may include, for example, at least one processor for executing computer program code to achieve the desired function, at least one memory for storing the program code, or both. Alternatively, they may include, for example, circuitry designed to achieve the desired function, such as circuitry implemented in a chipset or chip (e.g., an integrated circuit). Typically, the component may include, for example, one or more processing components or processors.

[0177] The apparatus disclosed above according to any aspect may be a module or component for a device (e.g., a chip). Alternatively, the apparatus disclosed according to any aspect may be a device, such as a server or server cloud. The apparatus disclosed according to any aspect may include (e.g., only) the disclosed components, such as parts, processors, memory, or may also include one or more additional components.

[0178] For example, a CW deactivation request can be obtained from a first device performing the method according to the first and / or second example aspects. The CW deactivation request can be configured to deactivate at least one (e.g., an ongoing transmission) provided, for example, by a CW provider (e.g., a CW support request previously provided to it by a CW coordinating node).

[0179] According to embodiments of the fifth and / or sixth example aspects, the method further includes: - A component for providing a CW deactivation request or an additional CW deactivation request derived from the CW deactivation request (e.g., the obtained CW deactivation request or a derived CW deactivation request based on the obtained CW deactivation request) to (e.g., a selected CW provider) in response to receiving a CW deactivation request.

[0180] For example, a selected CW provider that provides the CW deactivation request can be selected based on the obtained CW deactivation request (e.g., based on at least one CW attribute indicated by the CW support request).

[0181] CW deactivation requests can be configured to (e.g., currently) deactivate at least one (e.g., ongoing) CW transfer provided by a selected CW provider.

[0182] According to the embodiments of the fifth and / or sixth example aspects: - The CW deactivation request is provided as an uplink (UL) signal (e.g., the CW coordinating node is the UE and the CW provider is the gNB). - The CW deactivation request is provided as an uplink (UL) signal, wherein the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Unit (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - The CW deactivation request is provided as (e.g., the CW coordinating node is the UE, and the CW provider is the UE) at least one of the following: - Dedicated physical layer sequence (PHY sequence). - Side link control information (SCI) (e.g., specific fields in phase one or phase two SCI information). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - The CW deactivation request is provided as (e.g., the CW coordinating node is gNB, and the CW provider is gNB) at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link (e.g., if the CW provider is a specific TRP) - The CW deactivation request is provided as (e.g., the CW coordinating node is the gNB, and the CW provider is the UE) downlink (DL) signal or - The CW deactivation request is provided as a DL signal, where the DL signal is at least one of the following: - (e.g., a specific) DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0183] According to the embodiments of the fifth and / or sixth example aspects: - The CW deactivation request is configured to indicate at least one CW attribute of the CW transfer to be deactivated by the CW provider.

[0184] According to the embodiments of the fifth and / or sixth example aspects, the CW attribute includes at least one of the following: -CW transmission duration, -CW transmission spectrum (e.g., UL or DL). - (e.g., the previously provided) CW transport identifier, or -CW provider identifier.

[0185] According to the seventh example aspect, a system is disclosed, comprising: - A first apparatus, comprising (e.g., a terminal device (e.g., a UE) and / or a network node): - A component for sending (e.g., providing, transmitting) a carrier (CW) support request to a second device (e.g., a CW coordinating node or CW provider, but not an AIoT device), the CW support request being used to request at least one CW transmission (a CW transmission without an activation signal, (e.g., only) providing energy, without information content, (pure) sine wave, which can reach multiple tag devices and is receiver-unspecified) component.

[0186] - A CW provider (e.g., a terminal device (e.g., a UE) and / or a network node) includes: - Components for obtaining (e.g., receiving) a CW support request from a first device (e.g., directly from the first device or via a CW coordination node), and - A component for providing at least one CW transmission to at least one tag device (e.g., unlike the first device, without an activation signal) in response to a request for CW support, and - A tagging device (e.g., an AIoT device) comprising: - A component used to obtain at least one CW transmission from a CW provider. Attached Figure Description

[0187] Figure 1a , Figure 1b A schematic diagram of an example radio environment in which example embodiments of the present disclosure may be performed is shown; Figure 2a , Figure 2b A schematic diagram illustrating an example radio environment in which exemplary embodiments of the present disclosure may be performed; Figure 3 A signaling diagram illustrating example aspects of this disclosure is shown; Figure 4 A flowchart illustrating an embodiment according to a first exemplary aspect of this disclosure is shown; Figure 5 A flowchart illustrating embodiments according to the first and second exemplary aspects of this disclosure is shown; Figure 6 A flowchart illustrating an embodiment according to a third exemplary aspect of this disclosure is shown; Figure 7 Flowcharts illustrating embodiments according to the third and fourth exemplary aspects of this disclosure are shown; Figure 8 A flowchart illustrating an embodiment according to a fifth exemplary aspect of the present disclosure is shown; Figure 9 Flowcharts illustrating embodiments according to the fifth and sixth exemplary aspects of this disclosure are shown; Figure 10A block diagram illustrating an embodiment according to a first exemplary aspect of the present disclosure is shown; Figure 11 Block diagrams illustrating embodiments according to the first and second exemplary aspects of this disclosure are shown; Figure 12 A block diagram illustrating an embodiment according to a third exemplary aspect of the present disclosure is shown; Figure 13 Block diagrams illustrating embodiments according to the third and fourth exemplary aspects of this disclosure are shown; Figure 14 A block diagram illustrating an embodiment according to a fifth exemplary aspect of the present disclosure is shown; Figure 15 Block diagrams illustrating embodiments according to the fifth and sixth exemplary aspects of this disclosure are shown; Figure 16 A schematic diagram illustrating an example of a tangible and non-transitory computer-readable storage medium is shown. Detailed Implementation

[0188] The following description is intended to enhance understanding of this disclosure and should be understood to complement and be read together with the description of the exemplary embodiments of this disclosure provided in the foregoing overview section of this specification.

[0189] Figure 1a Figure b illustrates a relevant topology for an Ambient Internet of Things (AIoT) architecture, for example, according to the 3GPP Rel. 19 AIoT scheme. In this topology (AIoT topology), ambient IoT devices can receive carrier waves (CWs) from other (multiple) nodes either inside the topology (e.g., entities involved in communication interactions between AIoT devices, particularly activators and / or readers) or outside the topology (e.g., entities not involved in communication interactions with AIoT devices, whether activators or readers). Links in the topology can be bidirectional or unidirectional. Network nodes and / or UEs, auxiliary nodes and / or intermediate nodes can each comprise multiple BSs or UEs. Indoor and outdoor placement of any node is possible.

[0190] Figure 1a A first topology is illustrated. In this first topology, the environmental IoT device communicates directly and bidirectionally with network nodes (base stations, BBSs). Communication between the base station and the environmental IoT device includes environmental IoT data and / or signaling. This topology allows for the possibility that the BBS sending data to the environmental IoT device may differ from the BBS receiving data from the environmental IoT device.

[0191] Figure 1bA second topology is illustrated. In this second topology, the environmental IoT device communicates bidirectionally with an intermediate node between the device and the base station. In this topology, the intermediate node can be a relay, an integrated access / backhaul (IAB) node, a UE, a repeater, etc. The intermediate node can have environmental IoT capabilities. The intermediate node can transmit at least some information between the BS and the environmental IoT device.

[0192] Figure 2a Figure 2b illustrates another AIoT topology. The carrier wave (CW) can be a wave / carrier used by the AIoT device 400 to modulate and backscatter the AIOT response. The CW signal is distinct from the activation signal and serves the primary purpose of carrying the AIOT response signal for those AIoT devices 400 that cannot actively and independently generate their own signals, i.e., device categories 1 and 2a. In other words, the CW is transformed by the AIoT device 400 to at least contain the AIOT ID and is reflected immediately or with a delay pre-configured by the activator (i.e., backscattered).

[0193] exist Figure 2a In this process, activator 100 provides an activation signal and also provides a CW signal (i.e., CW transmission).

[0194] It has been recognized that, for example, in a given AIoT session, the entity that generates CW transmissions does not necessarily need to be an activator (or even a reader). Figure 2b Different topologies are shown. Here, CW provider 200 may alternatively provide a CW transport tank as a third-party entity. The CW provider may correspond, for example, to a network node and / or a UE. The CW provider is different from the activator.

[0195] Figure 2b The configuration shown can be referred to as CW provided from an external topology, while Figure 2a The CW provided from the internal topology is shown.

[0196] The following example embodiments detail variations provided by a (e.g., out-of-topology) CW provider that enables CW transmission. Signaling details are provided, such as how terminal devices and / or network entities may act as CW providers. In some embodiments, activation and / or deactivation of CW signal transmission may be triggered.

[0197] Figure 3 A signaling diagram illustrating the possible interactions between multiple entities in an AIoT topology is shown.

[0198] For example, activator 100 may send a CW support request to CW coordinating node 300, which then forwards it to CW provider 200. Alternatively or additionally, activator 100 may (e.g., directly) send the CW support request to entity 200 acting as a CW provider. Alternatively or additionally, activator 100 may send a CW signal deactivation request to coordinating node 300, which then forwards it to CW provider 200. Alternatively or additionally, activator 100 may send the CW signal deactivation request directly to entity 200 acting as a CW provider. Alternatively or additionally, CW provider 200 may determine when to deactivate CW signal transmission based on locally observed triggering conditions.

[0199] Now turning to more details Figure 3 In step S100, activator 100 (e.g., a first means of executing and / or controlling a method according to the first and / or second example aspects) may send a CW support request to coordinating node 300 (e.g., executing and / or controlling a method according to the fifth and / or sixth example aspects), and coordinating node 300 may in turn send (or another) CW support request to CW provider 200 in step S101 (e.g., executing and / or controlling a method according to the third and / or fourth example aspects). Coordinating node 300 may select CW provider 200, for example, based on at least one CW attribute indicated by the CW support request obtained in step S100. CW provider 200 may provide CW transmission in step S102, for example, in response to obtaining the CW support request in step S101. If the activator 100 cannot reach the CW provider 200 directly and / or if the activator 100 has not yet determined a suitable CW provider 200 for a given AIoT interaction with the tag device 400 itself, then using the CW coordinating node 300 instead of signaling the CW support request directly to the CW provider 200 may, for example, prove advantageous.

[0200] Therefore, according to the embodiment, activator 100 sends a CW support request to coordinating node 300, which then forwards it to CW provider 200. If coordinating node 300 is gNB A, the request to coordinating node 300 can be a UL signal, such as a UL SR, MAC CE, or even an RRC request. If CW provider 200 is a UE covered by gNB A, gNB A 300 directly triggers CW provider 200 to initiate CW transmission. This trigger can be via DL transmission from gNB 300 to device 200 acting as CW provider. If CW provider 200 is a network entity covered by gNB A 300, gNB A 300 triggers CW provider 200 to initiate CW transmission. This trigger can be via F1 or a fronthaul link from gNB 300 to the entity acting as CW provider 200. If CW provider 200 is a UE covered by gNB B, then gNB A 300 triggers CW provider 200 serving gNB B via the Xn interface. Then, gNB B triggers CW provider 200, acting as a CW transmitter, to begin its transmission via DL transmission. If CW coordinating node 300 is a third UE (where the first and second UEs are the activator and reader, respectively), the request to coordinating node 300 can be an SL signal (if the activator is a UE) or a DL signal (if the activator is an NW node). If activator 100 is a UE, the SL activation signal can be a dedicated PHY sequence, a specific field in the first-stage SCI, a specific field in the second-stage SCI, an SL MAC CE, or a PC5 RRC message. 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 a Proximity Service (ProSe) discovery process, where CW signal transmission is part of the announced Proximity Service. When Activator 100 is an NW node, the DL activation signal can be a specific DCI, MAC CE, RRC message, or NAS message. The CW support request can include an indication of the start and end times when CW transmission is required. Furthermore, the periodic pattern of the desired activation for CW transmission can be provided with the request to account for future AIoT sessions of the Activator.

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

[0202] Therefore, according to the embodiment, Activator 100 sends the CW support request directly to the entity acting as CW Provider 200. If Activator 100 is a UE, then if CW Provider 200 is another UE, the CW request can be a dedicated PHY sequence, a specific field in the first-stage SCI, a specific field in the second-stage SCI, an SL MAC CE, or a PC5 RRC message. On the other hand, if CW Provider 200 is an NW entity, the request can be a UL signal, such as a UL SR, MAC CE, or even an RRC request. If Activator 100 is an NW entity, then if CW Provider 200 is a UE, the CW support request can be a DL signal, which can be a specific DCI, MAC CE, RRC message, or NAS message. If CW Provider 200 is another NW entity, the CW support request can be via the Xn interface (if to another gNB), or if CW Provider 200 is a specific TRP, it can be via F1 or a fronthaul link. In both cases, the request may include an indication of when a CW transmission is needed, including both the start and end times. Furthermore, the required periodicity pattern for CW transmission activation can be provided along with the CW support request to account for future AIoT sessions with the activator.

[0203] In step S105, activator 100 may also be configured to send an activation signal to tag device 400. For example, the activation signal may be sent after sending a CW support request in step S100 or S103. At this stage, activator 100 may expect CW provider 200 to provide CW to tag device 400. Therefore, tag device 400 may respond to the activation signal provided in step S105. The activation signal is configured to send a backscatter response via tag device 400 (step S106). The backscatter response may be received, for example, by reader 500. Reader 500 may be different from or the same as activator 100.

[0204] Specifically, according to aspects 2, 4 and 6, and in aspects 1, 3, 5 and 7, the deactivation provided by CW is defined.

[0205] In step S107, activator 100 may send a CW deactivation request to coordinating node 300 and / or CW provider 200. The CW deactivation request is configured to deactivate at least one (e.g., an ongoing) CW transmission and / or more than one CW transmission, such as multiple (e.g., all) CW transmissions at a given CW provider. In step S110, the CW provider may deactivate at least one or more CW transmissions based on the CW deactivation request.

[0206] According to an embodiment, activator 100 or reader 500 sends a CW deactivation request to coordinating node 300. Coordinating node 300 can then forward the CW deactivation request to CW provider 200. If coordinating node 300 is a gNB, the CW deactivation request to coordinating node 300 can be a UL signal, such as a UL SR, MAC CE, or even an RRC request. If CW provider 200 is a UE covered by the gNB, the gNB directly triggers CW provider 200 to terminate CW transmission. This trigger can be via DL transmission from the gNB to the entity acting as CW provider 200. If CW provider 200 is a network entity covered by the gNB, the gNB triggers CW provider 200 to terminate CW transmission. This trigger can be via F1 or a fronthaul link from the gNB to the entity acting as CW provider 200. If CW provider 200 is a UE under the coverage of gNB B, then the original gNB A triggers CW provider 200 serving gNB B via the Xn interface. Then, gNB B triggers the entity acting as CW provider 200 to terminate (e.g., its) CW transmission via DL transmission. If coordinating node 300 is a third UE, then the CW deactivation request to coordinating node 300 can be an SL signal (if the activator is a UE) or a DL signal (if the activator 100 is an NW node). If the activator 100 is a UE, the SL deactivation signal can be a dedicated PHY sequence, a specific field in the first-stage SCI, a specific field in the second-stage SCI, an SL MAC CE, or a PC5 RRC message. 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 a proximity service discovery process, where CW signal transmission is part of the announced proximity service. When Activator 100 is an NW node, the DL deactivation signal can be a specific DCI, MAC CE, RRC, or NAS message. If Activator 100 no longer sees a CW signal requiring its presence, a CW deactivation request can be triggered. If the initial CW support request includes an indication of when the CW transmission should end, a CW deactivation request may not be necessary unless the CW deactivation request indicates that the CW transmission should end more quickly.

[0207] According to an embodiment, Activator 100 and / or Reader 500 send the CW deactivation request directly to the entity acting as CW Provider 200. If Activator 100 is a UE, and CW Provider 200 is another UE, the CW deactivation request can be a dedicated PHY sequence, a specific field in the first-stage SCI, a specific field in the second-stage SCI, an SL MACCE, or a PC5 RRC message. If CW Provider 200 is an NW entity, the CW deactivation request can be a UL signal, such as a UL SR, MAC CE, or even an RRC request. If Activator 100 is an NW entity, and CW Provider 200 is a UE, the CW deactivation request can be a DL signal, which can be a specific DCI, MAC CE, RRC message, or NAS message. If CW Provider 200 is another NW entity, the CW deactivation request can be via the Xn interface (if to another gNB), or via F1 or a fronthaul link if CW Provider 200 is a specific TRP. If Activator 100 no longer sees a required CW signal, a CW deactivation request can be triggered. If the initial CW support request includes an indication of when the CW transmission should end, a CW deactivation request may not be necessary, unless the CW deactivation request indicates that the CW signal transmission should end sooner.

[0208] According to various embodiments, CW provider 200 may determine when to deactivate CW transmission based on at least one of the following: Based on the receipt of an explicit CW deactivation request, particularly when no other CW support request may still be valid (e.g., indicated by the corresponding CW support request) for a CW transmission period (e.g., indicated by the corresponding CW support request) (e.g., the associated counter has not yet expired); Based on the elapsed counters (e.g., all) associated with the corresponding CW support request; Based on the absence of (e.g., at least one) CW support request observed during a predefined observation window.

[0209] Figure 4 A flowchart of an example embodiment according to a first example aspect is shown, performed, for example, by a first device (e.g., an activator). The method includes sending a CW support request to a CW provider or a CW coordinating node in step M100. The CW support request is configured to request CW transmissions from the CW provider.

[0210] Figure 5 A flowchart is shown of an example embodiment based on the first and / or second example aspects, performed, for example, by a first device (e.g., an activator). The method includes, in step M200, providing (e.g., transmitting, sending) a CW deactivation request to a CW provider or CW coordinating node. The CW deactivation request is configured to deactivate a CW transmission from the CW provider (e.g., previously, for example, requested in method step M100).

[0211] Figure 6 A flowchart illustrating an example embodiment according to a third example aspect is shown, performed, for example, by a second device (e.g., a CW provider). The method includes obtaining a CW support request, for example, from a first device (e.g., an activator) in step M300, and in particular, performing and / or controlling the method according to the first and / or second example aspects. Additionally or alternatively, the CW support request may be obtained from a CW coordination node, for example, performing and / or controlling the method according to the fifth or sixth aspect. The method further includes: in step M302, for example, providing at least one CW transmission to at least one tag device, for example, based on the CW support request obtained in step M300.

[0212] Figure 7 A flowchart illustrating an example embodiment according to the third and / or fourth example aspects is shown, performed, for example, by a second device (e.g., a CW provider). The method includes, in step M400, obtaining a CW deactivation request, for example, from a first device (e.g., an activator), and specifically performing and / or controlling the method according to the first and / or second example aspects. The CW deactivation request can be configured to deactivate a CW transfer performed by the CW provider (e.g., previously, for example, provided in method step M302).

[0213] Figure 8 A flowchart illustrating an example embodiment according to the fifth example aspect is shown, performed, for example, by a second device (e.g., a CW coordination node). The method includes obtaining a CW support request, for example, from a first device (e.g., an activator), in step M500, particularly performing and / or controlling the method according to the first and / or second example aspects. Additionally or alternatively, the CW support request may be obtained from another CW coordination node, for example, also performing and / or controlling the method according to the fifth or sixth aspect. The method further includes: in step M502, providing at least one CW support request and / or another CW support request, for example, to at least one CW provider, for example, performing and / or controlling the method according to the third and / or fourth aspects. The CW support request is configured to cause the CW provider to provide CW transmission to at least one tag device.

[0214] Figure 9 A flowchart illustrating an example embodiment according to the fifth and / or sixth aspects is shown, performed, for example, by a second device (e.g., a CW coordinating node). The method includes obtaining a CW deactivation request, for example, from a first device (e.g., an activator), in step M600, and in particular, performing and / or controlling the method according to the first and / or second example aspects. Additionally or alternatively, the CW deactivation request may be obtained from another CW coordinating node, which may also perform and / or control the method according to the fifth or sixth aspect. The CW deactivation request can be configured to deactivate a CW transmission from a CW provider (e.g., a previously requested one, for example, in method step M502).

[0215] Figure 10 An example block diagram of activator 100 is shown. Activator 100 can perform a method according to a first example aspect. The UE includes a user interface A160, a program memory A110, a main memory A120, and a data memory A140. Furthermore, it includes a processor A130. The device 100 may also include a functional unit CW support request transmitter A131, which corresponds to, for example... Figure 4 The actions are shown in the flowchart. The functional units may, for example, correspond to code blocks within memories A110, A120, and A140. The CW support request transmitter A131 may, for example, be connected to and / or control communication interface A150.

[0216] Figure 11 Another example block diagram of activator 100 is shown. Activator 100 can perform methods according to the first and / or second example aspects. The UE includes a user interface A160, a program memory A110, a main memory A120, and a data memory A140. Furthermore, it includes a processor A130. The device 100 may also include a functional unit CW deactivation request transmitter A132, which corresponds to, for example... Figure 5 The actions are shown in the flowchart. The functional units may, for example, correspond to code blocks within memories A110, A120, and A140. The CW support request transmitter A131 may, for example, be connected to and / or control communication interface A150.

[0217] Figure 12 An example block diagram of a CW provider 200 is shown. The CW provider 200 can execute a method according to a third example aspect. The CW provider 200 includes a user interface A260, a program memory A210, a main memory A220, and a data memory A240. Furthermore, it includes a processor A230. The CW provider 200 may also include a functional unit CW support request fetcher A231 and a functional unit CW transfer provider A232, which correspond respectively to... Figure 6 The flowchart illustrates the actions. Functional units may, for example, correspond to code blocks within memories A210, A220, and A240. Functional units A231 and / or A232 may, for example, be connected to and / or control communication interface A250.

[0218] Figure 13 An example block diagram of a CW provider 200 is shown. The CW provider 200 can execute methods according to the third and / or fourth example aspects. The CW provider 200 includes a user interface A260, program memory A210, main memory A220, and data memory A240. Furthermore, it includes a processor A230. The CW provider 200 may also include a functional unit, a CW deactivation request acquirer A233, which corresponds to... Figure 7 The actions are shown in the flowchart. Functional units may, for example, correspond to code blocks within memories A210, A220, and A240. Functional unit A233 may, for example, be connected to and / or control communication interface A250.

[0219] Figure 14 An example block diagram of a CW coordination node 300 is shown. The CW coordination node 300 can execute the method according to the fifth example aspect. The CW coordination node 300 includes a user interface A360, a program memory A310, a main memory A320, and a data memory A340. Furthermore, it includes a processor A330. The CW coordination node 300 may also include a functional unit CW support request fetcher A331 and a functional unit CW support request provider A332, which correspond to, respectively, as... Figure 8 The flowchart illustrates the actions. Functional units may, for example, correspond to code blocks within memories A310, A320, and A340. Functional units A331 and / or A332 may, for example, be connected to and / or control communication interface A350.

[0220] Figure 15 An example block diagram of a CW coordination node 300 is shown. The CW coordination node 300 can execute methods according to the fifth and / or sixth example aspects. The CW coordination node 300 includes a user interface A360, program memory A310, main memory A320, and data memory A340. Furthermore, it includes a processor A330. The CW coordination node 300 may also include a functional unit, a CW deactivation request acquirer A333, which corresponds to... Figure 9 The actions are shown in the flowchart. Functional units may, for example, correspond to code blocks within memories A310, A320, and A340. Functional unit A333 may, for example, be connected to and / or control communication interface A350.

[0221] Figure 16 This is a schematic diagram of an example of a tangible and non-transitory computer-readable storage medium according to the present invention, which can be used, for example, to implement... Figures 9 to 15 The program and / or main memory A110, A120, A140, A210, A220, A240, A310, A320, A340 of the devices 100, 200 and / or 300. Figure 16 The illustrations include, for example, a flash memory 1600 that can be soldered or bonded to a printed circuit board; a solid-state drive 1601 that includes multiple memory chips (e.g., flash memory chips); a magnetic hard disk drive 1602; a secure digital (SD) card 1603; a universal serial bus (USB) memory stick 1604; an optical storage medium 1605 (such as, for example, a CD-ROM or DVD); and a magnetic storage medium 1606.

[0222] Some embodiments include: Example 1: A first method (e.g., according to a first example aspect) includes: - Send a carrier (CW) support request to a second device, the CW support request being used to request at least one CW transmission to at least one tag device.

[0223] Example 2: According to the first method of Embodiment 1, the CW support request is configured to indicate at least one CW attribute to be provided by the CW provider for CW transmission.

[0224] Example 3: According to the first method of Embodiment 2, the CW property includes at least one of the following: -CW transmission start time, -CW transmission end time, -CW transmission duration, -CW transmission periodic pattern, -CW transmission spectrum -CW transport identifier, -CW provider identifier, - Tag device location, or - Tag device identifier.

[0225] Example 4: According to the first method of any one of Embodiments 1 to 3, wherein: -The first device is a terminal device, or - The first device is a network node.

[0226] Example 5: According to the first method of any one of Embodiments 1 to 4, the second device is at least one of the following: -CW coordinating node, -CW coordinating node, where the CW coordinating node is a network node. -CW Coordination Node, where the CW Coordination Node is the User Equipment (UE). -CW provider -CW provider, where the CW provider is a network node, or -CW provider, where the CW provider is the terminal device.

[0227] Example 6: According to the first method of any one of Embodiments 1 to 5, the tag device is an Environmental Internet of Things (AIoT) device.

[0228] Example 7: According to the first method of any one of Embodiments 1 to 6, at least one of the following is included: -CW support requests are provided as uplink (UL) signals. - The CW support request is provided as a UL signal, wherein the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, -CW support requests are provided as at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -CW support requests are provided as at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link -CW support requests are provided as downlink (DL) signals, or -CW support requests are provided as DL signals, wherein the DL signals are provided via at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0229] Example 8: The first method according to any one of embodiments 1 to 7 further includes: Receive the CW support response to the CW support request from the second device.

[0230] Example 9: According to the first method of Embodiment 8, the CW support response is configured to indicate at least one of the following: - Successful CW transfer, - Failed CW transfer, -CW transmission start time, -CW transmission end time, -CW transmission duration, -Minimum waiting time, -CW transport identifier, or -CW provider identifier.

[0231] Example 10: The first method according to any one of embodiments 1 to 9 further includes: - Provide an activation signal to at least one of the at least one tag device.

[0232] Example 11: According to the first method of any one of Embodiments 1 to 10, at least one of the following is included: - The activation signal is configured to elicit a backscatter response from the tag device. - The activation signal is specific to the tag device. - The activation signal is sent during the ongoing CW transmission. - The activation signal indicates the delay between the reception of the activation signal and activation, or - An activation signal is provided with at least one of the following: -In response to a request to provide CW support - In response to receiving a CW support response to a CW support request, or - After a predefined time following the submission of a CW support request.

[0233] Example 12: The first method (e.g., the method according to any one of embodiments 1 to 9 or the method according to the second exemplary aspect) further includes: - Provide a CW deactivation request to the second device, the CW deactivation request being used to request deactivation of at least one carrier provided to at least one tag device.

[0234] Example 13: According to a first method of any one of embodiments 1 to 12, the CW deactivation request is configured to indicate at least one CW attribute of the CW transmission to be deactivated by the CW provider.

[0235] Example 14: According to the first method of any one of Embodiments 1 to 13, the CW property includes at least one of the following: -CW transmission spectrum -CW transport identifier, or -CW provider identifier.

[0236] Example 15: According to the first method of any one of Examples 1 to 14, wherein: -CW deactivation request is an uplink (UL) signal. -CW deactivation request is an uplink (UL) signal, wherein the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, -CW deactivation request is at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -CW deactivation request is at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link -CW deactivation request is a downlink (DL) signal or -CW deactivation request is a DL signal, where the DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0237] Example 16: The first method according to any one of embodiments 1 to 15 further includes: - Obtain the deactivation response to the CW deactivation request from the second device.

[0238] Example 17: A method (e.g., provided by a carrier wave (CW)) comprising: - Obtain CW support requests from the requesting party, and - In response to a request for CW support, provide at least one CW transmission to at least one tag device.

[0239] Example 18: According to the method of Example 17, wherein: -The CW provider is the terminal device, or -CW providers are network nodes.

[0240] Example 19: According to the method of embodiment 17 or 18, the CW support request is configured to indicate at least one CW attribute to be provided by the CW provider for CW transmission.

[0241] Example 20: According to the method of Example 19, the CW property includes at least one of the following: -CW transmission start time, -CW transmission end time, -CW transmission duration, -CW transmission periodic pattern, -CW transmission spectrum -CW transport identifier, -CW provider identifier, - Tag device location, or - Tag device identifier.

[0242] Example 21: The method according to any one of embodiments 17 to 20 further includes: - Provide the requesting party with a CW support response to the CW support request.

[0243] Example 22: The method of any one of Examples 17 to 21, wherein the CW support response is configured to indicate at least one of the following: - Successful CW transfer, - Failed CW transfer, -CW transmission start time, -CW transmission end time, -CW transmission duration, -Minimum waiting time, -CW transport identifier, or -CW provider identifier.

[0244] Example 23: According to any one of Examples 17 to 22, wherein: -CW support requests are obtained as uplink (UL) signals. -CW support requests are obtained as uplink (UL) signals, where the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling.

[0245] - A CW support request is received as at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - A CW support request is received as at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link -CW supports requests being received as downlink (DL) signals, or -CW support requests are obtained as DL signals, where a DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0246] Example 24: A method (e.g., provided by CW) (e.g., the method according to any one of embodiments 17 to 23 or the method according to the fourth exemplary aspect) further includes: - Received a CW deactivation request.

[0247] Example 25: According to any one of Examples 17 to 24, wherein: -CW deactivation request is received 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 the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - A CW deactivation request is received as at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling - A CW deactivation request is received as at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link -CW deactivation request is received as a downlink (DL) signal, or - The CW deactivation request is obtained as a DL signal, wherein the DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0248] Example 26: According to the method of any one of Examples 17 to 25, wherein: The CW deactivation request is configured to indicate at least one CW attribute of the CW transfer to be deactivated by the CW provider. Example 27: According to the method of Example 26, the CW property includes at least one of the following: -CW transmission spectrum -CW transport identifier, or -CW provider identifier.

[0249] Example 28: The method according to any one of embodiments 17 to 27 further includes: - Deactivate the provided CW transport in response to at least one of the following: - The situation observed locally, or - Received a CW deactivation request.

[0250] Example 29: One approach (e.g., CW coordination) (e.g., according to the fifth example aspect) includes: - Obtain CW support request from the first device, and - In response to a CW support request, provide the CW support request or another CW support request derived from the CW support request to the selected CW provider.

[0251] Example 30: According to the method of Example 29, wherein: -The CW coordinating node is an end device, or -CW coordinating nodes are network nodes.

[0252] Example 31: According to the method of embodiment 29 or 30, the CW support request is configured to indicate at least one CW attribute to be provided by the CW provider for CW transmission.

[0253] Example 32: According to the method of embodiment 31, the CW property includes at least one of the following: -CW transmission start time, -CW transmission end time, -CW transmission duration, -CW transmission periodic pattern, -CW transmission spectrum -CW transport identifier, -CW provider identifier, - Tag device location, or - Tag device identifier.

[0254] Example 33: The method according to any one of embodiments 29 to 32 further includes: - Select a CW provider.

[0255] Example 34: The method according to any one of embodiments 29 to 33 further includes: - Provide the first device with a CW support response to the CW support request.

[0256] Example 35: According to the method of any one of Examples 29 to 34, wherein: -CW support requests are obtained as uplink (UL) signals. -CW support requests are obtained as uplink (UL) signals, where the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, - A CW support request is received as at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -CW support requests can be obtained as at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link -CW supports requests being received as downlink (DL) signals, or -CW support requests are obtained as DL signals, where a DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0257] Example 36: According to any one of Examples 29 to 35, wherein -CW support requests are provided as uplink (UL) signals. -CW support requests are provided as uplink (UL) signals, where the UL signal is at least one of the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, -CW support requests are provided as at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -CW support requests are provided as at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link -CW support requests are provided as downlink (DL) signals or -CW support requests are provided as DL signals, where a DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

[0258] Example 37: A method (e.g., CW coordination) (e.g., the method according to any one of embodiments 29 to 36 or the method according to the sixth exemplary aspect) further includes: - Received a CW deactivation request.

[0259] Example 38: The method according to any one of embodiments 29 to 37 further includes: - In response to receiving a CW deactivation request, provide a CW deactivation request to the selected CW provider or another CW deactivation request derived from the CW deactivation request.

[0260] Example 39: According to any one of Examples 29 to 38, wherein -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 the following: -Uplink Scheduling Request (UL SR). -Media Access Control Element (MAC CE). - Radio Resource Control (RRC) signaling, or - Non-access stratum (NAS) signaling, -The CW deactivation request is provided as at least one of the following: - Dedicated physical layer sequence (PHY sequence). Side link control information (SCI). - Side link (SL) MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -The CW deactivation request is provided as at least one of the following: -Xn signaling, or -F1 signaling, or - Signaling on the fronthaul link -CW deactivation request is provided as a downlink (DL) signal or - The CW deactivation request is provided as a DL signal, where the DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling or -NAS signaling.

[0261] Example 40: According to any one of embodiments 29 to 39, the CW deactivation request is configured to indicate at least one CW attribute of the CW transmission to be deactivated by the CW provider.

[0262] Example 41: The method of Example 40, wherein the CW property includes at least one of the following: -CW transmission spectrum -CW transport identifier, or -CW provider identifier.

[0263] Example 42: The first device includes corresponding components for performing the method according to any one of embodiments 1 to 16.

[0264] Example 43: A first device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least perform and / or control the method according to any one of embodiments 1 to 16.

[0265] Example 44: The second apparatus, such as that provided by the CW provider, includes corresponding components for performing the method of any one of embodiments 17 to 28.

[0266] Example 45: The second device, such as that of a CW provider, includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least perform and / or control the method according to any one of embodiments 17 to 28.

[0267] Example 46: The third device, such as a CW coordination node, includes corresponding components for performing the method according to any one of embodiments 29 to 41.

[0268] Example 47: A third device, such as a CW coordination node, includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least perform and / or control the method according to any one of embodiments 29 to 41.

[0269] Example 48: A computer program that, when executed by a processor, causes a device (e.g., a device according to embodiment 42 or 43) to perform and / or control the actions and / or steps of the method of any one of embodiments 1 to 16.

[0270] Example 49: A computer program product comprising a computer program according to embodiment 48.

[0271] Example 50: A computer program that, when executed by a processor, causes a device (e.g., a device according to embodiment 44 or 45) to perform and / or control the actions and / or steps of the method of any one of embodiments 17 to 28.

[0272] Example 51: A computer program product comprising the computer program according to embodiment 50.

[0273] Example 52: A computer program that, when executed by a processor, causes a device (e.g., a device according to embodiment 46 or 47) to perform and / or control the actions and / or steps of the method of any one of embodiments 29 to 41.

[0274] Example 53: A computer program product comprising a computer program according to embodiment 52.

[0275] Example 54: A system comprising: According to at least one first device of any one of embodiments 42 or 43, At least one second device according to any one of embodiments 44 or 45, and At least one third device according to any one of embodiments 46 or 47.

[0276] Any connections presented in the described embodiments are to be understood in a manner in which the components involved are operatively coupled. Therefore, connections can be direct or indirect, have any number or combination of intermediate elements, and may exist solely as functional relationships between components.

[0277] Furthermore, as used herein, the term "circuit" refers to any of the following: Hardware circuit implementation only (such as implementations in analog and / or digital circuits only) A combination of circuitry and software (and / or firmware), such as (i) a combination of (multiple) processors, or (ii) portions of (multiple) processors / software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device such as a mobile phone to perform various functions; and A circuit, such as (multiple) microprocessors or a portion thereof, requires software or firmware to operate, even if the software or firmware does not exist physically.

[0278] This definition of "circuit" applies to all uses of the term herein (including in any claim). As another example, as used herein, the term "circuit" also covers implementations of a processor (or processors) or a portion thereof and its accompanying software and / or firmware. The term "circuit" also covers, for example, baseband integrated circuits or application processor integrated circuits for mobile phones.

[0279] Any processor mentioned in this article, in particular but not limited to Figures 9 to 15The processors 130, 230, and 330 mentioned can be any suitable type of processor. Any processor can include, but is not limited to, one or more microprocessors, one or more processors with accompanying digital signal processors(s), one or more processors without accompanying digital signal processors(s), one or more application-specific 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 computers. The associated architecture / hardware has been programmed in a manner that performs the described functions.

[0280] Furthermore, any action or step 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., a disk, memory, etc.) for execution by such a processor. References to computer-readable storage media should be understood to encompass special-purpose circuitry such as FPGAs, ASICs, signal processing devices, and other devices.

[0281] Furthermore, any action 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., a disk, memory, etc.) for execution by such a processor. References to computer-readable storage media should be understood to encompass special-purpose circuitry, such as FPGAs, ASICs, signal processing devices, and other devices.

[0282] The phrase “A, or B, or C, or a combination thereof” or “at least one of A, B and C” can be understood as not exhaustive and includes at least the following: (i) A, or (ii) B, or (iii) C, or (iv) A and B, or (v) A and C, or (vi) B and C, or (vii) A and B and C.

[0283] It should be understood that the embodiments disclosed herein are merely exemplary, and any feature presented for a particular exemplary embodiment may be used alone in conjunction with any aspect of this disclosure, 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 should also be understood that any feature presented for example embodiments in a particular category may also be used in a corresponding manner in example embodiments of any other category.

[0284] List of abbreviations AIoT (Ambient Internet of Things) R2D reader to device (activation signal) D2R (Device to Reader) (Response Signal) BPSK (Binary Phase Shift Keying) CW carrier

Claims

1. A first device, comprising: - A component for providing a CW deactivation request to a second device, the CW deactivation request being used to request deactivation to provide at least one carrier to at least one tag device.

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

3. The first device according to claim 2, wherein the CW attribute includes at least one of the following: -The spectrum of the CW transmission, -CW transport identifier, or -CW provider identifier.

4. The first device according to any one 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 the following: -Uplink scheduling request UL SR, -Media Access Control (MAC) CE -Radio Resource Control (RRC) signaling, or -Non-Access Stratum (NAS) signaling -The CW deactivation request is at least one of the following: - Dedicated physical layer sequence PHY sequence Side Link Control Information (SCI) -Side link SL MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -The CW deactivation request is at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link - The CW deactivation request is a downlink DL signal or - The CW deactivation request is a DL signal, wherein the DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -NAS signaling.

5. The first device according to any one of claims 1 to 4, further comprising: - A component for obtaining a deactivation response to the CW deactivation request from the second device.

6. A CW provider, comprising: - A component used to obtain CW deactivation requests.

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 the following: -Uplink scheduling request UL SR, -Media Access Control (MAC) CE -Radio Resource Control (RRC) signaling, or -Non-Access Stratum (NAS) signaling -The CW deactivation request is obtained as at least one of the following: - Dedicated physical layer sequence PHY sequence Side Link Control Information (SCI) -Side link SL MAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -The CW deactivation request is obtained as at least one of the following: -Xn signaling, -F1 signaling, or - Signaling on the fronthaul link - The CW deactivation request is obtained as a downlink DL signal, or - The CW deactivation request is obtained as a DL signal, wherein the DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling, or -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 attribute of the CW transfer to be deactivated by the CW provider.

9. The CW provider of claim 8, wherein the CW attribute includes at least one of the following: -The spectrum of the CW transmission, -CW transport identifier, or -CW provider identifier.

10. The CW provider according to any one of claims 6 to 9, further comprising: - A component for deactivating the provided CW transmission in response to at least one of the following: - The situation observed locally, or - Obtain the CW deactivation request.

11. A CW coordination node, comprising: - A component used to obtain CW deactivation requests.

12. The CW coordination node according to claim 11, further comprising: - A component for providing the CW deactivation request or another CW deactivation request derived from the CW deactivation request to a selected CW provider in response to receiving the CW deactivation request.

13. The CW coordination node according to 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 the following: -Uplink scheduling request UL SR, -Media Access Control (MAC) CE -Radio Resource Control (RRC) signaling, or -Non-Access Stratum (NAS) signaling -The CW deactivation request is provided as at least one of the following: - Dedicated physical layer sequence PHY sequence Side Link Control Information (SCI) - Side-link SLMAC CE, or - Sidelink RRC signaling or PC5-RRC signaling -The CW deactivation request is provided as at least one of the following: -Xn signaling, or -F1 signaling, or - Signaling on the fronthaul link - The CW deactivation request is provided as a downlink DL signal or - The CW deactivation request is provided as a DL signal, wherein the DL signal is at least one of the following: -DCI, -MAC CE, -RRC signaling or -NAS signaling.

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

15. The CW coordination node of claim 14, wherein the CW attribute includes at least one of the following: -The spectrum of the CW transmission, -CW transport identifier, or -CW provider identifier.

16. A system comprising at least: - A first device, comprising: - A component for providing a CW deactivation request to a second device, the CW deactivation request being used to request deactivation of at least one carrier provided to at least one tag device. - A CW provider, comprising: - A component used to obtain the CW deactivation request.

Images