CW power, frequency and beam control for environmental IoT

Abstract

The invention relates to CW power, frequency and beam control for ambient IoT. An apparatus and method are provided by a carrier provider associated with an environmental Internet of Things session, where the carrier provider is a network node configured to transmit a carrier, and the environmental Internet of Things session relates to an environmental Internet of Things device, the environmental Internet of Things device is a network node configured to receive a carrier and manipulate the carrier transmitted by the carrier provider, and notification information is provided to at least one network node involved in an environmental Internet of Things session, wherein the notification information indicates how to interact with the associated carrier provider to send the control information to the associated carrier provider.

Description

Technical Field

[0001] This invention relates to apparatus, methods, and computer program products for implementing carrier (CW) power, frequency, and beam control for environmental IoT. Background Technology

[0002] The following meanings apply to the abbreviations used in this instruction manual:

[0003] AIoT environment IoT

[0004] CE control elements

[0005] CW carrier

[0006] D2R device to reader

[0007] DL downlink

[0008] IE Information Elements

[0009] IoT

[0010] L1 / 2 Floor 1 / 2

[0011] MAC Media Access Control

[0012] NAS Non-Access Layer

[0013] NW Network

[0014] PUCCH (Physical Uplink Control Channel)

[0015] PUSCH Physical Uplink Shared Channel

[0016] R2D reader to device

[0017] RACH Random Access Channel

[0018] RRC Radio Resource Control

[0019] SR scheduling request

[0020] SCU Session Control Unit

[0021] UE - User Equipment

[0022] UL uplink

[0023] The example embodiments relate to, but are not limited to, Ambient Internet of Things (AIoT, sometimes abbreviated as AIoT or A-IoT). The corresponding systems include AIoT devices, activators, readers, and CW providers (also called CW nodes or CW signal providers), which are controlled, for example, by an SCU (Session Control Unit).

[0024] In this scenario, the carrier wave (CW) is used by the AIoT device to modulate and backscatter the AIoT response (D2R signal). The CW signal differs from the activation signal (R2D signal) and serves the primary purpose of carrying AIoT transmissions for those AIoT devices that cannot actively and independently generate their own signals (i.e., device types 1 and 2a). In other words, the CW is transformed by the AIoT device to contain the AIoT payload (e.g., ID, data, and other control information) and reflected—that is, backscattered immediately or with a delay pre-configured by the activator via the R2D signal.

[0025] In this scenario, improving the control of the network components or nodes involved would be beneficial. Summary of the Invention

[0026] The example implementation addresses this situation and is designed to provide improved control over network elements or network nodes involved in an AIoT session.

[0027] Various aspects of the various exemplary embodiments will be described with respect to some aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments, nor are they intended to be used to otherwise limit the scope of the subject matter disclosure. Other features, aspects, and elements of the various exemplary embodiments will be apparent to those skilled in the art in light of this disclosure.

[0028] According to a first aspect, an apparatus is provided, the apparatus comprising:

[0029] At least one processor, and

[0030] At least one memory storing instructions that, when executed by at least one processor, cause the device to at least:

[0031] Associate a carrier provider with an environmental IoT session, where the carrier provider is a network node configured to transmit carriers, and the environmental IoT session involves an environmental IoT device, which is a network node configured to receive carriers and manipulate the carriers transmitted by the carrier provider.

[0032] Provide notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with the associated carrier provider to send control information to the associated carrier provider.

[0033] According to the second aspect, a method is provided, the method comprising:

[0034] Associating a carrier provider with an environmental IoT session, where the carrier provider is a network node configured to transmit carriers, and the environmental IoT session involves an environmental IoT device, which is a network node configured to receive and manipulate carriers transmitted by the carrier provider.

[0035] Provide notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with the associated carrier provider to send control information to the associated carrier provider.

[0036] According to a third aspect, a computer program product is provided, the computer program product including a code component for performing the method according to the second aspect above.

[0037] According to a fourth aspect, an apparatus is provided, the apparatus comprising:

[0038] Components for associating a carrier provider with an environmental IoT session, wherein the carrier provider is a network node configured to transmit a carrier, and the environmental IoT session involves an environmental IoT device, which is a network node configured to receive and manipulate the carrier transmitted by the carrier provider.

[0039] Components for providing notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with an associated carrier provider to send control information to the associated carrier provider.

[0040] Advantageous developments are defined in the dependent claims. Attached Figure Description

[0041] These and other objects, features, details, and advantages will become more apparent from the following detailed description of exemplary embodiments taken in conjunction with the accompanying drawings, in which:

[0042] Figure 1A An SCU 1 according to an example embodiment is shown.

[0043] Figure 1B The process executed by SCU 1 according to an example embodiment is shown.

[0044] Figure 2A CW provider 2 according to an example embodiment is shown.

[0045] Figure 2B The process performed by CW provider 2 according to an example embodiment is shown.

[0046] Figure 3A A reader 3 according to an example embodiment is shown.

[0047] Figure 3B The process performed by reader 3 according to an example embodiment is shown.

[0048] Figure 4A Network entity 4 according to an example embodiment is shown.

[0049] Figure 4B The process performed by network entity 4 according to the example embodiment is shown.

[0050] Figure 5A UE 5 according to an example embodiment is shown.

[0051] Figure 5B The process executed by UE 5 according to an example embodiment is shown.

[0052] Figure 6 A signaling diagram according to embodiment Z is shown.

[0053] Figure 7 A signaling diagram according to embodiment A is shown.

[0054] Figure 8 A signaling diagram according to embodiment B is shown, and

[0055] Figure 9 A signaling diagram according to embodiment C is shown. Detailed Implementation

[0056] In the following description, exemplary embodiments will be presented. However, it should be understood that this description is given by way of example only, and the described exemplary embodiments should in no way be construed as limiting the invention thereto.

[0057] Before describing the example embodiments, the technical context of the example embodiments and the problems of the prior art will be discussed in more detail below.

[0058] Some example embodiments relate to AIoT (Ambient Internet of Things). The SCU (Session Control Unit) can control an AIoT session involving AIoT devices, activators, readers, and CW providers (also called CW nodes or CW signal providers). As described above, the carrier wave (CW) is the wave that AIoT devices use to modulate and backscatter the AIoT response (D2R signal). The CW signal differs from the activation signal (R2D signal) and has the primary purpose of carrying AIoT transmissions for those AIoT devices that cannot actively and independently generate their own signals (i.e., device types 1 and 2a). In other words, the CW is transformed by the AIoT device to contain the AIoT payload (e.g., ID, data, and other control information) and is reflected, i.e., backscattered immediately or with a delay pre-configured by the activator via the R2D signal configuration.

[0059] The CW provider (i.e., the entity that generates the CW) should: a) be near the AIoT device, and b) transmit the CW at sufficient power on the correct carrier frequency for a sufficient duration so that the AIoT device can modulate all of its payload onto the CW and its response can be successfully decoded by the reader.

[0060] Since the configuration of CW nodes is crucial to the success of AIoT sessions, RAN 1 discusses the introduction of a separate entity for this sole purpose, which can be part of or outside of Topology 1 or 2. Furthermore, because CW transmissions can potentially harm other ongoing transmissions—whether AIoT or Uu services—their configuration should be handled by the network or an entity participating in the AIoT session, as highlighted in Proposal 2.4-2a, which can be found in the FL summary (R1-2403767) of CW waveform characteristics for A-IoT in AI 9.4 on 3GPP TSG RAN WG1#116bits. This is reiterated below:

[0061] Proposal 2.4-2a: From the perspective of RAN 1, control of at least the following CW characteristics should be implemented:

[0062] - Timing (e.g., time resources when CW is sent or not sent)

[0063] -Transmission power

[0064] - Frequency resources (including bandwidth)

[0065] - Spectrum

[0066] -(Outside the topology) Which CW node will send?

[0067] - Frequency hopping mode

[0068] - Beam transmission or directional transmission, if it is supported by CW.

[0069] In some example embodiments, how to associate (multiple) CW signal providers with AIoT session devices and how to control the power, frequency hopping, and spatial transmission of the CW signal providers are addressed.

[0070] In the following text, by reference Figure 1A , Figure 1B , Figure 2A and Figure 2B This section provides a general overview of some example embodiments.

[0071] Figure 1AAn SCU 1 according to this example embodiment is shown. SCU 1 is an example of a device that may be, for example, a network node or network element performing the functions or roles of a session control unit, or part thereof. Figure 1B The process executed by SCU 1 is shown in the figure. Figure 1A The LMF 1 shown includes at least one processor 11 and at least one memory 12 storing instructions that, when executed by at least one processor 11, cause the device to: associate a carrier provider with an Ambient Internet of Things (AIoT) session, wherein the carrier provider is a network node configured to transmit a carrier, and the AIoT session involves an Ambient Internet of Things device, which is a network node configured to receive a carrier and manipulate the carrier transmitted by the carrier provider. Figure 1B S11); and providing notification information to at least one network node involved in the IoT session in this environment, wherein the notification information indicates how to interact with the carrier provider to send control information to the associated carrier provider (S11); Figure 1B (S12 in the middle).

[0072] Figure 2A A CW provider 2 according to this example embodiment is shown. CW provider 2 is an example of a device, such as a network node or network element that performs the function or role of a carrier provider, or part thereof. Figure 2B The process executed by CW provider 2 is shown in the figure. Figure 2A The CW provider 2 shown includes at least one processor 21 and at least one memory 22 storing instructions that, when executed by the at least one processor 21, cause the device to: transmit a carrier for an environmental IoT session involving an environmental IoT device, the environmental IoT device being a network node configured to receive and manipulate the carrier. Figure 2B (S21 in the text); Receive a request for controlling at least one carrier transmission characteristic ( Figure 2B S22); and based on the received request, control at least one carrier transmission characteristic, such that the at least one carrier transmission characteristic is changed.

[0073] Figure 3A A reader 3 according to this example embodiment is shown. Reader 3 is an example for a device that may be, for example, a network node or network element, or part thereof, performing the functions or roles of a reader in an AIoT session. Figure 3B The process executed by reader 3 is shown in the figure. Figure 3A The reader 3 shown includes at least one processor 31 and at least one memory 32 storing instructions that, when executed by at least one processor 31, cause the device to: receive carrier transmissions modulated by environmental IoT devices in an environmental IoT session. Figure 3B In step S31), it is determined whether the received power of the carrier transmission is lower than a predetermined threshold. Figure 3B S32); and in response to determining that the received power is below a predetermined threshold, preparing a notification, the notification requesting control of at least one carrier transmission characteristic to increase the received power, and sending the notification to the carrier provider transmitting the carrier transmission or the session control unit controlling the IoT session of the environment (S32); Figure 3B (S33 in the text).

[0074] Figure 4A NW entity 4 according to this example embodiment is shown. NW entity 4 is an example of a device that may be, for example, a network control element outside of an AIoT session or a part thereof. For example, NW entity 4 may be a gNB that controls connections to network nodes such as a UE. Figure 4B The process executed by NW entity 4 is shown in the figure. Figure 4A The NW entity 4 shown includes at least one processor 41 and at least one memory 42 storing instructions that, when executed by at least one processor 41, cause the device to: control the session control unit of the IoT session in the control environment (e.g., Figure 1A The SCU 1 shown acquires information that can notify the session control unit or the carrier provider involved in the IoT session in this environment (e.g., Figure 2A The CW provider 2 shown in the figure identifies the carrier transmission (S41 in Figure 4) and provides the acquired information to at least one network node, wherein at least one network node is under the control of the device (S42 in Figure 4).

[0075] Provide notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with the associated carrier provider to send control information to the associated carrier provider.

[0076] Therefore, according to several example embodiments, a mechanism is provided that allows a CW signal provider to be assigned to an AIoT session and the radiated power from the CW signal provider to be controlled.

[0077] Figure 1A , Figure 2A , Figure 3A , Figure 4A and Figure 5A The devices 1 to 5 shown may include more components than those described above, and may also include I / O units 13, 23, 33, 43, and 53 capable of sending to and receiving from other network elements.

[0078] As described above, an AIoT session that can be controlled or supervised by a session control unit (SCU) may involve an Ambient Internet of Things (AIoT) device, which is a network node configured to receive and manipulate a carrier transmitted from a CW provider, a reader (e.g., reader 3 shown in Figure 3), which is a network node configured to receive the manipulated carrier, and an activator, which is a network node configured to send an activation signal to the AIoT device to instruct the AIoT device to begin manipulating the carrier.

[0079] The transmission of a carrier can be controlled / adapted by controlling at least one characteristic of the carrier. At least one carrier transmission characteristic (CW transmission characteristic) may include transmission power, frequency hopping, and / or transmission beamforming. For example, the received power at reader 3 can be increased by increasing the transmission power and / or by changing / adapting the frequency hopping mode and / or transmission beamforming. For example, interference caused by CW transmission and encountered at UE 5 can be reduced by decreasing the transmission power and / or by correspondingly changing / adapting the frequency hopping and / or transmission beamforming at the CW provider.

[0080] In the following sections, some example embodiments will be described in more detail.

[0081] According to some example embodiments, solutions are provided for configuring a neighboring CW signal provider for an AIoT session (with support from a session control unit (SCU)) and for controlling the radiated power from the CW signal provider by controlling transmission, frequency hopping and spatial transmission.

[0082] In the following, as Example A, an AIoT session configuration with CW provider and session association is described.

[0083] In this embodiment, two scenarios of CW provider control are considered. The first is SCU-mediated CW provider control. In this control, the network node attempting to interact with the CW provider will perform the operation via the SCU. That is, in this case, there is an indirect connection between the network node and the CW provider. The second scenario is direct CW provider control. In this scenario, the network node attempting to interact with the CW provider is capable of and enabled to interact directly with the CW provider. That is, in this case, there is a direct connection between the network node and the CW provider.

[0084] According to Embodiment A, the identification of CW providers(s) associated with the AIoT session is performed. In the case of SCU-mediated CW provider control, the identification may include the exchange of a private CW identifier that has become known between the SCU and AIoT session members (activators, AIoT devices, and / or readers). In the case of direct CW provider control, the identification may include the exchange of a private CW identifier (e.g., a sidelink L1 / 2 identifier or a sidelink service identifier).

[0085] Furthermore, the proximity between the CW provider and AIoT session members (specifically, the proximity to AIoT devices) is determined by the SCU (e.g., based on location information, based on exchange measurements between the CW and AIoT session members, or based on sidelink-based discovery, where the discovery results have been shared with the SCU).

[0086] In addition, configurations are provided for activators and / or readers to request specific actions from CW providers (e.g., directly to CW providers or via SCU).

[0087] In the case of SCU-mediated power control, the configuration may include the exchange of a dedicated SR / PUCCH configuration, which can be used by AIoT session members to indicate a need for control over the transmission characteristics of the CW provider (e.g., transmission power, frequency hopping, and / or transmission beamforming). The actual control information may be provided via payloads from PUCCH, MACCE, RRC IE, and / or NAS IE. The content of the control information may be at least one of the following:

[0088] - Power control: Power increase / decrease step size and / or absolute power level configuration.

[0089] - Frequency hopping: Changes in the frequency hopping sequence, masking of certain hops (i.e., zero-power transmission on the identified hops);

[0090] -Tx beamforming: This should include identifiers (i.e., beam IDs) for spatial filters that increase / decrease power.

[0091] - Duty cycle: Increase / decrease the duty cycle of the transmitted CW;

[0092] In the case of direct CW provider control, the configuration for activators and / or readers to request specific actions from the CW provider may include a dedicated sidelink configuration, which includes the resource pool to be used, the DRX configuration associated with the CW provider, and the service ID or L1 / 2 ID for contacting the CW provider.

[0093] In the following description, Example B is shown, in which a notification requiring a reduction in CW signal transmission power to minimize interference is executed.

[0094] To this end, the notification from an affected UE (or affected NW entity) to the NW entity or SCU regarding interference experienced by a UE outside the AIoT session due to transmissions to the CW provider of the NW entity or SCU is first described. Note that in this example, an affected UE (or victim UE) is described. However, this is merely an example and could be any node affected by interference. In the following text, such a node will also be referred to as an interference-affected node.

[0095] If the CW signal signature has been pre-informed to the victim UE by the NW, the victim UE can detect the interference source. Knowing the CW signal, the victim UE can identify its contribution to the total received signal and implicitly identify the CW provider—assuming a unique mapping between the CW provider and the CW signal. The CW signal configuration can be distributed by the NW to all UEs in the cell via the SIB, or alternatively, to a set of intended victim UEs. Details will be described later in Embodiment Z.

[0096] The notification includes information about the following:

[0097] - The received interference power and the recommended power are reduced;

[0098] - Past time and frequency resources for this interference have been observed; - Future time and frequency resources for this level of interference should be avoided (e.g., when such resources are known due to upcoming UL / DL authorization and / or configuration with SPS or CG-SDT) when available to the UE.

[0099] - Service priority (e.g., associated QoS profiles, such as the 5G QoS identifier 5QI).

[0100] Furthermore, the affected UE (or the network node controlling the affected UE, such as a gNB) can issue a request to control the CW provider's transmission characteristics based on interference notification. This control command (i.e., the request) can be provided via the SCU responsible for CW provider orchestration (which provides interference notification to the SCU from the node presumably affected by interference). Note that the decision regarding whether to apply power reduction will be based on a comparison between the service priority of the AIoT session and the service priority of the affected UE. Power reduction can also be triggered depending on whether the power reduction still results in power exceeding the minimum operating power range required for charging / activating the AIoT device.

[0101] The aforementioned control request can be provided directly from the NW entity (e.g., the NW entity serving the affected UE) to the CW provider. This assumes that the NW entity can contact the CW provider via the Uu interface (when the CW provider is a UE) or the Xn interface (when the CW provider is a network element). Furthermore, where it is possible to establish a sidelink between these UEs, the control request can also be provided directly from the affected UE to the UE acting as the CW provider.

[0102] The following describes the control of CW transmission characteristics in order to minimize the impact of interference. In particular, the control applied to transmission characteristics may be the backoff of transmission power requested by a notification, the avoidance of time and frequency resources indicated in the interference notification (e.g., changes or silencing of associated hops in frequency hopping mode); and / or the deactivation or power backoff in the beamformer provided at the CW provider in association with the direction of the interference-affected node.

[0103] In the following description, Embodiment C is provided, according to which a notification (hereinafter also referred to as “weak signal notification”) is sent indicating the need for increased power in CW transmission due to the observation of a weak backscatter signal at the receiver.

[0104] This notification indicates that the reader failed to receive a sufficiently strong CW signal, and therefore any backscattered signal was too weak to be decoded. Note that this assumes both the CW and AIoT device transmissions are within the reader's line of sight, as AIoT sessions typically consist of devices close to each other. In this case, the reader can determine whether the CW power needs to be increased based on a comparison of the received backscattered signal strength and the original CW signal. The same approach can be applied under non-line-of-sight conditions; however, there will be less correlation between the received low-power CW transmissions, making any CW transmission characteristic adaptation based on a request from the reader less reliable.

[0105] Based on the aforementioned weak signal notification, a request is provided to control the transmission characteristics of the CW provider. This control command can be provided via the SCU responsible for CW provider orchestration, where the notification is provided to the SCU (following the configuration details in Embodiment A). Alternatively, when a side link can be established between the affected UE and the UE serving the CW provider (according to the configuration details in Embodiment A), the control request can be provided directly from the affected UE to the UE serving the CW provider.

[0106] Then, the CW transmission characteristics can be controlled to increase the received CW signal. The control applied to the transmission characteristics can be:

[0107] - Gradually increase transmission power based on weak signal notification;

[0108] - A gradual increase in power in the time and frequency resources indicated in the weak signal notification;

[0109] - A gradual increase in the transmission power in the beamformer, which is associated with the direction of the node affected by the interference.

[0110] In the following description, embodiment Z is provided, according to which a configuration is provided regarding how to access the SCU associated with the CW to notify of excessive interference.

[0111] Specifically, configuration details on how to contact the CW provider regarding interference issues are provided. For a given area (i.e., cell or gNB coverage area), information on which SCU to contact in the event of interference is part of the Uu (whether public or private) RRC configuration. For example, a private SR / PUCCH configuration can be used to provide this notification. In this case, it is assumed that the private scheduling request SR / PUCCH configuration is associated with either the CW provider or the mechanism that triggers the adaptation within the CW provider. In the latter case, this would mean that the reader simply sends the notification, and then the SCU determines which CW provider(s) needs to act on that notification.

[0112] Alternatively, the notification may be provided via a RACH procedure, wherein a dedicated PRACH preamble is assigned to the use case or the PUSCH content of the RACH transmission includes information about the notification, for example in the form of a MAC CE, RRC IE, and / or NAS IE.

[0113] In the following text, by reference Figures 6 to 9 The above embodiments will be described in more detail by describing the signaling flow.

[0114] In particular, Figures 6 to 9 The signaling flow between the SCU, reader, AIoT device, activator, CW provider, NW (network node, such as gNB), and the affected node (such as UE) is illustrated. The reader, AIoT device, activator, and CW provider can participate in an AIoT session controlled / supervised by the SCU. The NW and the affected node are examples of network nodes outside the AIoT session.

[0115] Figure 6The above embodiment Z is illustrated. In process 0), a configuration is provided regarding how to contact the CW provider regarding interference issues. As mentioned above, for a given area (i.e., cell or gNB coverage area), information on which SCU to contact in the event of interference is part of the Uu (whether public or private) RRC configuration. For example, this notification can be provided using a private SR / PUCCH configuration. Alternatively, the notification can be provided via a RACH procedure, wherein a private PRACH preamble is assigned to the use case or the PUSH content transmitted via RACH includes information about the notification, for example in the form of a MAC CE, RRC IE, and / or NASIE.

[0116] Figure 7 The above embodiment A is illustrated. According to embodiment A, SCU-assisted AIoT session configuration is performed, which includes determining which specific nodes will act as activators, readers, and CW providers (e.g., based on proximity to AIoT devices) and determining the resources to be used for the AIoT session, as shown in process 1.

[0117] AIoT session configuration aspects related to CW interactions during an AIoT session include the identifiers of the CW providers(s) associated with the AIoT session and the configurations for activators and / or readers to request specific actions from the CW providers.

[0118] First, the identifiers of the CW providers(s) associated with the AIoT session are described. These identifiers may include the exchange of private CW identifiers that become known between the SCU and AIoT session members (activators and / or readers) in the case of SCU-mediated CW provider control. Alternatively, in the case of direct CW provider control, private CW identifiers (e.g., sidelink L1 / 2 identifiers or sidelink service identifiers) may be exchanged.

[0119] The proximity between the CW provider and the AIoT session member is determined by the SCU (e.g., based on location information, based on exchange measurements between the CW and the AIoT session member, or based on sidelink-based discovery, where the discovery results have been shared with the SCU).

[0120] The following describes the configuration of the activator and / or reader to enable it to request a specific action from the CW provider (e.g., directly to the CW provider or via the SCU).

[0121] In the case of SCU-mediated CW provider control, the configuration may include the exchange of a dedicated SR / PUCCH configuration, which can be used by AIoT session members to indicate the control requirements for the CW provider's transmission characteristics (e.g., transmit power, frequency hopping, and / or transmit beamformer). The actual control information may be provided via the PUCCH payload, MACCE, RRC IE, and / or NAS IE. The content of the control information may be at least:

[0122] -Power control: Power increase / decrease step size;

[0123] - Frequency hopping: Changes in the frequency hopping sequence, masking of certain hops (i.e., zero-power transmission on the identified hops);

[0124] -Tx beamforming: This should include identifiers (i.e., beam IDs) for spatial filters that increase / decrease power.

[0125] - Duty cycle: Increase / decrease the duty cycle of the transmitted CW;

[0126] In the case of direct CW provider control, the above configuration may include the exchange of a dedicated sidelink configuration, which includes the resource pool to be used, the DRX configuration associated with the CW provider, and the service ID or L1 / 2 ID for contacting the CW provider.

[0127] In procedure 2), it is assumed that the activator / reader needs to contact the CW provider. That is, the request for CW support can be made directly between the activator / reader and the CW provider, as shown in procedure 2.a. Otherwise, this can be done via the SCU, as shown in procedure 2.b.

[0128] In process 3), CW transmission begins. Note that it is assumed that CW continues its transmission at least during the AIoT session.

[0129] In process 4), the activator sends its activation signal.

[0130] In process 5), when the AIoT device receives the activation signal from the activator, it begins the transmission of its backscattered signal over the CW signal.

[0131] Figure 8 and Figure 9 Embodiments B and C are shown, in which CW transmission characteristics are adapted.

[0132] Typically, this adaptation of CW transmission characteristics is referred to as process 6.

[0133] According to Embodiment B, the CW transmission characteristics are adapted based on interference notification, as described above and as follows: Figure 8 As shown.

[0134] In process 6.ai), the affected node (affected UE or NW entity) sends a notification to the NW entity or SCU regarding the interference experienced due to CW provider transmissions. This notification includes information about the following:

[0135] - The received interference power and the recommended power are reduced;

[0136] - Past time and frequency resources of this interference have been observed; and / or

[0137] - Future time and frequency resources for this level of interference should be avoided.

[0138] In procedure 6.a.ii.a) or procedure 6.a.ii.b), a request is provided to control the transmission characteristics of the CW provider based on interference notification.

[0139] The request can be provided via the SCU, which is responsible for orchestrating CW providers (and which assumes that the affected node provides interference notification to the SCU), as shown in procedure 6.a.ii.b). That is, the NW entity (e.g., the NW entity serving the affected UE) forwards the request to the SCU, which then forwards it to the CW provider identified by the request.

[0140] Alternatively, the request can be made directly from the NW entity (e.g., the NW entity serving the affected UE) to the CW provider, as shown in procedure 6.a.ii.a). This assumes that the NW entity can contact the CW provider via the Uu interface (when the CW provider is a UE) or the Xn interface (when the CW provider is a network element).

[0141] When it is possible to establish a side link between the affected UE and the UE serving the CW provider, the control request can be provided directly from the affected UE to the UE serving the CW provider.

[0142] As shown in process 6.a.iii), control over the CW transmission characteristics is performed to minimize the effects of interference. The control applied to the transmission characteristics can be:

[0143] - The transmission power was rolled back as requested in the notification;

[0144] - Avoidance of time and frequency resources indicated in the interference notification (e.g., changes to or silencing of related hops in frequency hopping patterns); and / or

[0145] - Deactivation or power back-off in the beamformer associated with the direction of the node affected by the interference.

[0146] Subsequently, the transmission of the CW signal with updated parameters is performed, as shown in procedure 6.a.iv).

[0147] The following describes Figure 9 The example shown is Embodiment C, in which the CW transmission characteristics are adapted due to an excessively weak CW signal.

[0148] As shown in process 6.bia) or 6.bib), the reader issues a notification that it has failed to receive a sufficiently strong CW signal, and therefore the backscattered signal is too weak to be decoded. This notification includes a request to control the CW provider's transmission characteristics based on the weak signal notification. Note that, alternatively, this notification and the request can be two separate messages.

[0149] As shown in process 6.bia), when it is possible to establish a side link between the affected UE and the UE serving the CW provider (according to the configuration details in embodiment A), the request (control sequence) can be provided directly from the affected UE to the UE serving the CW provider.

[0150] Alternatively, as shown in process 6.bib, the request (control sequence) can be provided via the SCU responsible for orchestrating the CW provider, wherein the notification is provided to the SCU (following the configuration details in embodiment A). The SCU forwards the notification to the CW provider.

[0151] In process 6.b.ii), the CW transmission characteristics are controlled to increase the received CW signal. The controls applied to the transmission characteristics can be:

[0152] - Gradually increase transmission power as requested by notification;

[0153] - Gradual increase in power within the time and frequency resources indicated in the weak signal notification; and / or

[0154] - Gradual increase in transmission power in the beamformer associated with the direction of the node affected by interference.

[0155] Subsequently, the transmission of the CW signal with updated parameters is performed, as shown in procedure 6.b.iii).

[0156] The above example embodiments are merely examples and can be modified.

[0157] For example, some of the example embodiments described above illustrate a UE as a network element affected by interference caused by CW transmissions from a CW provider. However, the network element is not limited to a UE and can be any type of network element affected by interference caused by CW transmissions. For example, such a network element could also be a base station, etc.

[0158] The names of network elements, protocols, and methods are based on the current standard. In other versions or other technologies, the names of these network elements and / or protocols and / or methods may differ, as long as they provide the corresponding functionality.

[0159] Typically, exemplary embodiments can be implemented by computer software stored in memories (memory resources, memory circuitry) 12, 22, 32, 42 and executable by processors (processing resources, processing circuitry) 11, 21, 31, 41, 51, or by hardware or by a combination of software and / or firmware and hardware.

[0160] The terms “connection,” “coupling,” or any variation thereof mean any direct or indirect connection or coupling between two or more components, and may cover one or more intermediate elements existing between two elements that are “connected” or “coupled” together. The coupling or connection between components can be physical, logical, or a combination thereof. As a non-limiting example, as adopted herein, two components can be considered “connected” or “coupled” together by using one or more wires, cables, and printed electrical connections, and by using electromagnetic energy (such as electromagnetic energy with wavelengths in the radio frequency region, microwave region, and optical (visible and invisible) region).

[0161] The memory (memory resources, memory circuitry) 12, 22, 32, 42, 52 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, and non-transitory computer-readable media. As a non-limiting example, the processor (processing resources, processing circuitry) 11, 21, 31, 41, 51 can be of any type suitable for the local technical environment and can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0162] Furthermore, as used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuits) and (b) a combination of hardware circuitry and software, such as (as applicable): (i) A combination of analog and / or digital hardware (multiple) circuits and software / firmware, and (ii) Any part of a hardware processor having software (including (a plurality of) digital signal processors) that works together to enable a device such as a mobile phone or a server to perform various functions, and (c) (a plurality of) hardware circuits and / or (a plurality of) processors, such as (a plurality of) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but the software may not be present when it is not required to operate.

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

[0164] As used herein, the term “non-transient” refers to the limitation of the medium itself (i.e., tangible, not signal), rather than the limitation of data storage persistence (e.g., RAM versus ROM).

[0165] Note that, as used herein, “at least one of the following: ” and “at least one of ” and similar wording, where a list of two or more elements is combined with “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0166] It should be understood that the various exemplary embodiments of this disclosure are illustrative and non-limiting, and are not intended to be construed as restrictive. Various modifications and applications will be apparent to those skilled in the art without departing from the spirit and scope of the various exemplary embodiments disclosed herein.

[0167] The aforementioned publicly disclosed information includes the following terms:

[0168] Clause 1. An apparatus comprising

[0169] At least one processor, and

[0170] At least one memory storing instructions that, when executed by at least one processor, cause the device to at least:

[0171] Associate a carrier provider with an environmental IoT session, where the carrier provider is a network node configured to transmit carriers, and the environmental IoT session involves an environmental IoT device, which is a network node configured to receive carriers and manipulate the carriers transmitted by the carrier provider.

[0172] Provide notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with an associated carrier provider to send control information to the associated carrier provider.

[0173] Clause 2. The apparatus according to Clause 1, wherein the instructions, when executed by at least one processor, cause the apparatus to at least: provide an identifier to at least one network node involved in the environmental IoT session, the identifier identifying a carrier provider associated with the environmental IoT session.

[0174] Clause 3. The apparatus according to Clause 1 or 2, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0175] Based on the proximity between the carrier provider and the environmental IoT device, determine the carrier provider to be associated with the environmental IoT session from multiple carrier providers.

[0176] Clause 4. The apparatus according to Clause 1 or 2, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0177] Configure the notification settings to be an indirect connection via the device to the carrier provider.

[0178] Clause 5. The apparatus according to Clause 1 or 2, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0179] Configure the notification settings to a direct connection to the carrier provider.

[0180] Clause 6. The apparatus according to Clause 5, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0181] Configure the dedicated side link as a direct connection to the carrier provider.

[0182] Clause 7. The apparatus according to any one of Clauses 1 to 6, wherein the control information includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

[0183] Clause 8. The apparatus according to any one of Clauses 1 to 7, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0184] The reader receives a notification from an environmental IoT device involved in an environmental IoT session that the received power is below a predetermined threshold. The reader is a network node configured to receive manipulated carriers and is involved in the environmental IoT session.

[0185] The request carrier provider is made to control the transmission characteristics of the carrier, thereby increasing the received power.

[0186] Clause 9. The apparatus according to any one of Clauses 1 or 3 to 8, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0187] Provide to at least one network node outside the environmental IoT session: information that enables the session control unit or carrier provider to be notified of information about carrier transmission, and carrier transmission information for identifying carrier transmission.

[0188] Clause 10. The apparatus according to Clause 9, wherein the carrier transmission information includes information indicating a carrier transmission signature or an identifier of a carrier provider associated with an environmental IoT session.

[0189] Clause 11. The apparatus according to Clause 9 or 10, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0190] Receive notifications about carrier transmissions from at least one network node outside the environmental IoT session, and

[0191] Based on notifications received from network nodes, a request is made to the carrier provider to control carrier transmission characteristics.

[0192] Clause 12. The apparatus of Clause 11, wherein the notification may include information for identifying the carrier provider.

[0193] Clause 13. The apparatus according to Clause 12, wherein the information for identifying the carrier provider includes information identifying the signature of the carrier signal transmitted by the carrier provider.

[0194] Clause 14. The apparatus pursuant to any one of Clauses 11 to 13, wherein the notification includes at least one of the following:

[0195] Information regarding recommended adaptations for carrier transmission characteristics.

[0196] Information about interference caused by carrier transmission

[0197] Information regarding timing that should avoid interference, or

[0198] Information regarding business priorities.

[0199] Clause 15. An apparatus comprising

[0200] At least one processor, and

[0201] At least one memory storing instructions that, when executed by at least one processor, cause the device to at least:

[0202] A carrier wave is transmitted for an environmental IoT session involving an environmental IoT device, which is a network node configured to receive and manipulate the carrier wave.

[0203] Receive a request to control at least one carrier transmission characteristic to change the at least one carrier transmission characteristic, and

[0204] The transmission characteristics of the at least one carrier are controlled based on the received request.

[0205] Clause 16. The apparatus according to Clause 15, wherein,

[0206] The request is for controlling at least one carrier transmission characteristic to reduce interference caused by the carrier transmission; and

[0207] When an instruction is executed by at least one processor, it causes the device to at least:

[0208] Receive the request from the following location Session control unit used to control surrounding IoT sessions, or Network nodes outside of the environmental IoT session.

[0209] Clause 17. The apparatus according to Clause 16, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0210] The request is received from a network node outside the environmental IoT session via a dedicated side link configured as a direct connection.

[0211] Clause 18. The apparatus according to Clause 15, wherein

[0212] The request is for increasing transmission power; and

[0213] When an instruction is executed by at least one processor, it causes the device to at least:

[0214] Receive the request from the following location Session control unit for controlling IoT sessions in the control environment, or Readers involved in environmental IoT sessions.

[0215] Clause 19. The apparatus according to Clause 18, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0216] The request is received from the reader involved in the environmental IoT session via a dedicated side link configuration.

[0217] Clause 20. The apparatus according to any one of Clauses 15 to 19, wherein the request for controlling at least one carrier transmission characteristic includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

[0218] Clause 21. An apparatus comprising

[0219] At least one processor, and

[0220] At least one memory storing instructions that, when executed by at least one processor, cause the device to at least:

[0221] In an environmental IoT session, receive carrier transmissions modulated by environmental IoT devices.

[0222] Determine whether the received power of the carrier transmission is lower than a predetermined threshold;

[0223] In response to the determination that the received power is below a predetermined threshold, a notification is prepared requesting control of at least one carrier transmission characteristic to increase the received power, and the notification is sent to the carrier provider transmitting the carrier transmission or the session control unit of the IoT session in the control environment.

[0224] Clause 22. The apparatus according to Clause 21, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0225] Based on the identifier of the carrier provider provided by the session control unit, a notification is sent to the carrier provider that is sending the carrier transmission.

[0226] Clause 23. The apparatus according to Clause 21 or 22, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0227] A notification is sent to the carrier provider that transmits the carrier via a dedicated side link configuration.

[0228] Clause 24. The apparatus according to any one of Clauses 21 to 23, wherein the notification requesting control of at least one carrier transmission characteristic to increase the received power includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

[0229] Clause 25. An apparatus comprising

[0230] At least one processor, and

[0231] At least one memory storing instructions that, when executed by at least one processor, cause the device to at least:

[0232] Information is obtained from the session control unit of the control environment IoT session. This information can notify the session control unit or the carrier provider participating in the control environment IoT session about carrier transmission, and identify the carrier transmission.

[0233] The acquired information is provided to at least one network node, wherein at least one network node is under the control of the device.

[0234] Clause 26. The apparatus of Clause 25, wherein the information for identifying the session control unit is provided in the radio resource control configuration.

[0235] Clause 27. The apparatus according to Clause 25 or 26, wherein the information capable of notifying the session control unit includes information about the dedicated scheduling request / physical uplink control channel configuration to be used for notification, and / or information that the notification can be provided via a random access channel procedure.

[0236] Clause 28. The apparatus according to any one of Clauses 25 to 27, wherein

[0237] Multiple network nodes are under the control of the device, and

[0238] When executed by at least one processor, the instruction causes the device to at least:

[0239] Send the information to all network nodes controlled by the device; or

[0240] Based on the location information of at least one potentially affected network node among the plurality of network nodes and the carrier provider, at least one potentially affected network node is identified that is potentially affected by interference caused by the carrier transmission of the carrier provider, and the information is sent to the identified at least one potentially affected network node.

[0241] Clause 29. The apparatus according to any one of Clauses 25 to 27, wherein the instructions, when executed by at least one processor, cause the apparatus to at least:

[0242] Receive information from at least one network node that causes interference due to carrier transmissions from the carrier provider, and

[0243] Send a notification to the carrier provider or session control unit.

[0244] Clause 30. The apparatus pursuant to Clause 29, wherein the notification includes at least one of the following:

[0245] Information regarding recommended control of at least one carrier transmission characteristic

[0246] Information about interference caused by carrier transmission

[0247] Information regarding timing that should avoid interference, or

[0248] Information regarding business priorities.

[0249] Clause 31. An apparatus comprising

[0250] At least one processor, and

[0251] At least one memory storing instructions that, when executed by at least one processor, cause the device to at least:

[0252] Information is obtained from the session control unit of the control environment IoT session. This information can notify the session control unit or the carrier provider participating in the control environment IoT session about carrier transmission and identify the carrier transmission.

[0253] Detecting interference affecting the device caused by carrier transmission, and

[0254] Based on the information obtained, a notification regarding the detected interference is sent to the carrier provider or session control unit.

[0255] Clause 32. The apparatus according to Clause 31, wherein the notification of detected interference includes at least one of the following:

[0256] Information regarding recommended control of at least one carrier transmission characteristic

[0257] Information about interference caused by carrier transmission

[0258] Information regarding timing that should avoid interference, or

[0259] Information regarding business priorities.

[0260] Clause 33. The apparatus according to Clause 31 or 32, wherein information for identifying the session control unit is provided in the radio resource control configuration.

[0261] Clause 34. The apparatus according to any one of Clauses 26 to 28, wherein the information capable of notifying the session control unit includes information about the configuration of the dedicated scheduling request / physical uplink control channel to be used for notification, and / or information that the notification may be provided via a random access channel procedure.

[0262] Clause 35. The apparatus according to any one of Clauses 1 to 34, wherein at least one carrier transmission characteristic includes transmission power, frequency hopping and / or transmission beamforming.

[0263] Clause 36. A method comprising:

[0264] Associating a carrier provider with an environmental IoT session, where the carrier provider is a network node configured to transmit carriers, and the environmental IoT session involves an environmental IoT device, which is a network node configured to receive and manipulate carriers transmitted by the carrier provider.

[0265] Provide notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with an associated carrier provider to send control information to the associated carrier provider.

[0266] Clause 37. The method described pursuant to Clause 36 further includes:

[0267] Provide an identifier to at least one network node involved in the environmental IoT session, the identifier identifying the carrier provider associated with the environmental IoT session.

[0268] Clause 38. The method described pursuant to Clause 36 or 37 further includes:

[0269] Based on the proximity between the carrier provider and the environmental IoT device, determine the carrier provider to be associated with the environmental IoT session from multiple carrier providers.

[0270] Clause 39. The method described pursuant to Clause 36 or 37 further includes:

[0271] The network element executing this method will configure the notification settings as an indirect connection to the carrier provider.

[0272] Clause 40. The method described pursuant to Clause 36 or 37 further includes:

[0273] Configure the notification settings to connect directly to the carrier provider.

[0274] Clause 41. The method described pursuant to Clause 40 further includes:

[0275] Configure the dedicated side link as a direct connection to the carrier provider.

[0276] Clause 42. The method according to any one of Clauses 36 to 41, wherein the control information includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

[0277] Clause 43. The method according to any one of Clauses 36 to 42 further includes:

[0278] The reader receives a notification from an environmental IoT device involved in an environmental IoT session that the received power is below a predetermined threshold. The reader is a network node configured to receive manipulated carriers and is involved in the environmental IoT session.

[0279] The request carrier provider is made to control the transmission characteristics of the carrier, thereby increasing the received power.

[0280] Clause 44. The method according to any one of Clauses 36 or 38 to 43 further includes:

[0281] Provide to at least one network node outside the environmental IoT session: information that enables the session control unit or carrier provider to be notified of information about carrier transmission, and carrier transmission information for identifying carrier transmission.

[0282] Clause 45. The method according to Clause 44, wherein the carrier transmission information includes information indicating a carrier transmission signature or an identifier of a carrier provider associated with an environmental IoT session.

[0283] Clause 46. The method described pursuant to Clause 44 or 45 further includes:

[0284] Receive notifications about carrier transmissions from at least one network node outside the environmental IoT session, and

[0285] Based on notifications received from network nodes, a request is made to the carrier provider to control carrier transmission characteristics.

[0286] Clause 47. The method described in Clause 46, wherein the notification may include information for identifying the carrier provider.

[0287] Clause 48. The method according to Clause 47, wherein the information for identifying the carrier provider includes information identifying the signature of the carrier signal transmitted by the carrier provider.

[0288] Clause 49. The method pursuant to any one of Clauses 46 to 48, wherein the notification includes at least one of the following:

[0289] Information regarding recommended adaptations for carrier transmission characteristics.

[0290] Information about interference caused by carrier transmission

[0291] Information regarding timing that should avoid interference, or

[0292] Information regarding business priorities.

[0293] Clause 50. A method comprising:

[0294] A carrier wave is transmitted for an environmental IoT session, the carrier wave of which relates to an environmental IoT device, which is a network node configured to receive and manipulate the carrier wave.

[0295] Receive a request to control at least one carrier transmission characteristic to cause a change in the at least one carrier transmission characteristic, and

[0296] The transmission characteristics of at least one carrier are controlled based on the received request.

[0297] Clause 51. The method described pursuant to Clause 50, wherein,

[0298] The request is for controlling at least one carrier transmission characteristic to reduce interference caused by the carrier transmission; and

[0299] The method also includes:

[0300] Requests are received from the following locations. Session control unit for controlling IoT sessions in the environment, or Network nodes outside of the environmental IoT session.

[0301] Clause 52. The method described pursuant to Clause 51 further includes:

[0302] The request is received from a network node outside the environmental IoT session via a dedicated side link configuration that acts as a direct connection.

[0303] Clause 53. The method described pursuant to Clause 50, wherein,

[0304] The request is for increasing transmission power; and

[0305] The method also includes:

[0306] Receive the request from the following location Session control unit for controlling IoT sessions in the control environment or Readers involved in environmental IoT sessions.

[0307] Clause 54. The method described pursuant to Clause 53 further includes:

[0308] The request is received from the reader involved in the environmental IoT session via a dedicated side link configuration.

[0309] Clause 55. The method according to any one of Clauses 50 to 54, wherein the request for controlling at least one carrier transmission characteristic includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

[0310] Clause 56. A method comprising:

[0311] In an environmental IoT session, receive carrier transmissions modulated by environmental IoT devices.

[0312] Determine whether the received power of the carrier transmission is lower than a predetermined threshold;

[0313] In response to the determination that the received power is below a predetermined threshold, a notification is prepared requesting control of at least one carrier transmission characteristic to increase the received power, and a notification is sent to the carrier provider transmitting the carrier transmission or the session control unit of the IoT session in the control environment.

[0314] Clause 57. The method described pursuant to Clause 56 further includes:

[0315] Based on the identifier of the carrier provider provided by the session control unit, a notification is sent to the carrier provider that is sending the carrier transmission.

[0316] Clause 58. The methods described pursuant to Clause 56 or 57 further include:

[0317] A notification is sent to the carrier provider that transmits the carrier via a dedicated side link configuration.

[0318] Clause 59. The method according to any one of Clauses 56 to 58, wherein the notification requesting control of at least one carrier transmission characteristic to increase the received power includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

[0319] Clause 60. A method comprising:

[0320] Information is obtained from the session control unit of the control environment IoT session. This information can notify the session control unit or the carrier provider participating in the control environment IoT session about carrier transmission, and identify the carrier transmission, and

[0321] The acquired information is provided to at least one network node, wherein at least one network node is under the control of a network control element performing the method.

[0322] Clause 61. The method according to Clause 60, wherein information for identifying the session control unit is provided in the radio resource control configuration.

[0323] Clause 62. The method according to Clause 60 or 61, wherein the information capable of notifying the session control unit includes information about the dedicated scheduling request / physical uplink control channel configuration to be used for notification, and / or information that the notification can be provided via a random access channel procedure.

[0324] Clause 63. The method according to any one of Clauses 60 to 62, wherein

[0325] Multiple network nodes, under the control of the network control element executing this method, and

[0326] The method also includes:

[0327] Send the information to the network node controlled by the network control unit; or,

[0328] Based on the location information of at least one potentially affected network node among the plurality of network nodes and the carrier provider, at least one potentially affected network node is identified that is potentially affected by interference caused by the carrier transmission of the carrier provider, and the information is sent to the identified at least one potentially affected network node.

[0329] Clause 64. The method according to any one of Clauses 61 to 63 further includes:

[0330] Receive information from at least one network node that causes interference due to carrier transmissions from the carrier provider, and

[0331] Send a notification to the carrier provider or session control unit.

[0332] Clause 65. The method described in Clause 64, wherein the notification includes at least one of the following:

[0333] Information regarding recommended control of at least one carrier transmission characteristic

[0334] Information about interference caused by carrier transmission

[0335] Information regarding timing that should avoid interference, or

[0336] Information regarding business priorities.

[0337] Clause 66. A method comprising:

[0338] Information is obtained from the session control unit of the control environment IoT session. This information can notify the session control unit or the carrier provider participating in the control environment IoT session about carrier transmission and identify the carrier transmission.

[0339] Detecting interference caused by carrier transmission that affects the network nodes performing this method, and

[0340] Based on the information obtained, a notification regarding the detected interference is sent to the carrier provider or session control unit.

[0341] Clause 67. The method described in Clause 66, wherein the notification of detected interference includes at least one of the following:

[0342] Information regarding recommended control of at least one carrier transmission characteristic

[0343] Information about interference caused by carrier transmission

[0344] Information regarding timing that should avoid interference, or

[0345] Information regarding business priorities.

[0346] Clause 68. The method according to Clause 66 or 67, wherein information for identifying the session control unit is provided in the radio resource control configuration.

[0347] Clause 69. The method according to any one of Clauses 66 to 68, wherein the information capable of notifying the session control unit includes information about the dedicated scheduling request / physical uplink control channel configuration to be used for notification, and / or information that the notification may be provided via a random access channel procedure.

[0348] Clause 70. The method according to any one of Clauses 36 to 69, wherein at least one carrier transmission characteristic includes transmission power, frequency hopping and / or transmission beamforming.

[0349] Clause 71. A computer program product comprising code components for performing the method according to any one of Clauses 35 to 70 when executed on a processing component or module.

[0350] Clause 72. A computer program product pursuant to Clause 72, wherein the computer program product is embodied on a computer-readable medium, and / or the computer program product is directly loadable into the internal memory of a computer and / or can be transmitted over a network by at least one of the processes of uploading, downloading and pushing.

[0351] Clause 73. An apparatus comprising

[0352] Components for associating a carrier provider with an environmental IoT session, wherein the carrier provider is a network node for transmitting a carrier, and the environmental IoT session involves environmental IoT devices, which are network nodes for receiving and manipulating the carrier transmitted by the carrier provider.

[0353] Components for providing notification information to at least one network node involved in an environmental IoT session, wherein the notification information indicates how to interact with an associated carrier provider to send control information to the associated carrier provider.

[0354] Clause 74. An apparatus comprising:

[0355] Components used to transmit carrier waves for environmental IoT sessions involving environmental Internet of Things (IoT) devices, which are network nodes configured to receive and manipulate carrier waves.

[0356] A component for receiving a request to control at least one carrier transmission characteristic so that the at least one carrier transmission characteristic is changed, and

[0357] A component for controlling at least one carrier transmission characteristic based on a received request.

[0358] Clause 75. An apparatus:

[0359] A component used to receive carrier transmissions modulated by environmental IoT devices in an environmental IoT session.

[0360] A component for determining whether the received power of carrier transmission is below a predetermined threshold; and

[0361] A component for preparing a notification in response to a determination that the received power is below a predetermined threshold, the notification requesting control of at least one carrier transmission characteristic to increase the received power, and sending the notification to a carrier provider transmitting the carrier transmission or to a session control unit of an IoT session in the control environment.

[0362] Clause 76. An apparatus comprising:

[0363] Components for obtaining information from a session control unit of a control environment IoT session, which can notify the session control unit or a carrier provider participating in the control environment IoT session about carrier transmission, and identify the carrier transmission, and

[0364] A component for providing the acquired information to at least one network node, wherein the at least one network node is under the control of the device.

[0365] Clause 77. An apparatus comprising:

[0366] A component for obtaining information from the session control unit of a control environment IoT session, which can notify the session control unit or the carrier provider participating in the control environment IoT session about carrier transmission and identify the carrier transmission.

[0367] A component for detecting interference affecting the device caused by carrier transmission, and

[0368] A component used to send a notification about detected interference to a carrier provider or session control unit based on the information obtained.

Claims

1. A device for communication, comprising: 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: Associating a carrier provider with an environmental IoT session, wherein the carrier provider is a network node configured to transmit a carrier, and the environmental IoT session involves an environmental IoT device, which is a network node configured to receive the carrier and manipulate the carrier transmitted by the carrier provider. Provide notification information to at least one network node involved in the IoT session of the environment, wherein the notification information indicates how to interact with the associated carrier provider to send control information to the associated carrier provider.

2. The apparatus of claim 1, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: An identifier is provided to the at least one network node involved in the environmental IoT session, the identifier identifying the carrier provider associated with the environmental IoT session.

3. The apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: Based on the proximity between the carrier provider and the environmental IoT device, the carrier provider to be associated with the environmental IoT session is determined from a plurality of carrier providers.

4. The apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: The notification is configured to be an indirect connection to the carrier provider via the device.

5. The apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: Configure the notification to a direct connection to the carrier provider.

6. The apparatus of claim 5, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: Configure the dedicated side link as a direct connection to the carrier provider.

7. The apparatus according to claim 1 or 2, wherein the control information includes at least one of power control information, frequency hopping control information, transmission beamforming information, and duty cycle information.

8. The apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: The reader receives a notification from the environmental IoT device involved in the environmental IoT session that the received power is below a predetermined threshold. The reader is a network node configured to receive the manipulated carrier and is involved in the environmental IoT session. The carrier provider is requested to control the transmission characteristics of the carrier to increase the received power.

9. The apparatus of claim 1, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: Provide to at least one network node outside the IoT session of the environment: information that enables the session control unit or the carrier provider to notify the carrier transmission information, and carrier transmission information for identifying the carrier transmission.

10. The apparatus of claim 9, wherein the carrier transmission information includes information indicating a carrier transmission signature or an identifier of the carrier provider associated with the IoT session of the environment.

Images