Remote interference management (RIM)

Abstract

The invention relates to a network node and a method for RIM. A method for RIM at a first network node includes detecting whether there is an RI from one or more second network nodes during at least one first time period during which one or more ongoing processes for RIM mitigation at the first network node and the one or more second network nodes are suspended. A method for RIM at a second network node includes suspending one or more ongoing processes for RIM mitigation at the second network node during at least one first time period such that a first network node can detect whether there is an RI from the second network node during the at least one first time period.

Description

Technical Field

[0001] This disclosure relates to the telecommunications field, and more specifically, to network nodes and methods for remote interference management (RIM). Background Technology

[0002] With the development of electronic and telecommunications technologies, mobile devices (such as mobile phones, smartphones, laptops, tablets, and in-vehicle devices) have become an important part of our daily lives. To support a large number of mobile devices, an efficient radio access network (RAN) is needed, such as the 3rd Generation Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) RAN.

[0003] However, radio access networks (RANs) can sometimes experience performance degradation due to unintended interference. For example, atmospheric ducting, caused by lower density at higher altitudes in the Earth's atmosphere, leads to a decrease in refractive index, causing signals to bend back to Earth. Signals trapped in atmospheric ducts can travel much farther than normal. In time-division duplex (TDD) networks with identical uplink (UL) / downlink (DL) time slot configurations, and in the absence of atmospheric ducting, guard periods (GP) are used to avoid interference between UL and DL transmissions in different cells. However, when atmospheric ducting occurs, radio signals can propagate relatively long distances, and the propagation delay exceeds the guard period. Therefore, the DL signal of an attacking cell can interfere with the UL signal of a victim cell located far from the attacker. This interference is called remote interference (RI). The farther the attacker is from the victim, the more UL symbols of the victim will be affected. Summary of the Invention

[0004] The framework and reference signals for RIM defined in 3GPP will result in significant costs. It requires signaling and complex configuration, as well as extensive coordination with operators and other vendors who may supply network equipment to them. Many parameters need to be adjusted according to 3GPP Technical Specification (TS) 28.541, V18.4.1. Coordinating the logic for RIM detection, localization, and mitigation will also be highly complex.

[0005] Because the framework defined by 3GPP is costly and complex, many base station vendors attempt to find shortcuts, but this can cause problems. For example, with some shortcut solutions, the victim base station cannot know whether the remote interference has truly disappeared or has disappeared due to mitigation by the attacker base station. As another example, because in some cases the attacker base station does not send a RIM reference signal (RIM-RS), the victim base station does not know when to stop sending its RIM-RS. Furthermore, because these shortcut solutions are not specified in 3GPP, they cannot be used between different vendors.

[0006] Therefore, some embodiments of this disclosure are provided in order to solve or at least partially alleviate one or more of the above-mentioned problems.

[0007] According to a first aspect of this disclosure, a method for RIM at a first network node is provided. The method includes: detecting the presence of RI from the one or more second network nodes during at least a first time period during which one or more ongoing processes for RIM mitigation at the first network node and one or more second network nodes are paused.

[0008] In some embodiments, the method further includes: determining whether to continue or stop the one or more ongoing processes for RIM mitigation based at least on the detection of the presence or absence of an RI from the one or more second network nodes. In some embodiments, the method further includes at least one of the following operations: continuing and / or triggering the continuation of the one or more ongoing processes for RIM mitigation in response to the detection of an RI from the one or more second network nodes during the at least one first time period; and stopping and / or triggering the cessation of the one or more ongoing processes for RIM mitigation in response to the absence of an RI from the one or more second network nodes during the at least one first time period.

[0009] In some embodiments, determining whether to continue or stop the one or more ongoing processes for RIM mitigation is based at least on whether an RI (Information Receipt) is detected from the one or more second network nodes during a second time period of performing at least one of the one or more ongoing processes for RIM mitigation. In some embodiments, the method further includes at least one of the following operations: in response to detecting an RI from the one or more second network nodes during the at least one first time period and in response to detecting an RI from the one or more second network nodes during a second time period, continuing and / or triggering the continuation of the one or more ongoing processes for RIM mitigation; in response to detecting an RI from the one or more second network nodes during the at least one first time period and in response to not detecting an RI from the one or more second network nodes during the second time period, continuing and / or triggering the continuation of the one or more ongoing processes for RIM mitigation; and in response to not detecting an RI from the one or more second network nodes during the at least one first time period and in response to not detecting an RI from the one or more second network nodes during the second time period, stopping and / or triggering the cessation of the one or more ongoing processes for RIM mitigation.

[0010] In some embodiments, when the at least one first time period includes more than one first time period within a RIM detection period, detecting whether an RI from the one or more second network nodes exists during the at least one first time period includes: detecting the RI level during all first time periods within the RIM detection period; calculating a filtered RI value at least based on the detected RI levels at the end of the RIM detection period; and detecting whether an RI from the one or more second network nodes exists at least based on the filtered RI value. In some embodiments, detecting whether an RI from the one or more second network nodes exists at least based on the filtered RI value includes at least one of the following operations: detecting the existence of an RI from the one or more second network nodes in response to determining that the filtered RI value is higher than a first threshold; and detecting the absence of an RI from the one or more second network nodes in response to determining that the filtered RI value is lower than a second threshold. In some embodiments, the filtered RI value is at least one of the following: the average of the detected RI levels; and the maximum value of the detected RI levels.

[0011] In some embodiments, when the at least one first time period includes only a single first time period within the RIM detection period, detecting whether an RI from the one or more second network nodes exists during the at least one first time period includes: detecting the RI level during the single first time period; and detecting whether an RI from the one or more second network nodes exists, at least based on the RI level. In some embodiments, detecting whether an RI from the one or more second network nodes exists, at least based on the RI level, includes at least one of the following operations: detecting the existence of an RI from the one or more second network nodes in response to determining that the RI level is higher than a first threshold; and detecting the absence of an RI from the one or more second network nodes in response to determining that the RI level is lower than a second threshold. In some embodiments, the first threshold is higher than or equal to the second threshold.

[0012] In some embodiments, the at least one first time period is at least one frame. In some embodiments, the first network node and at least one of the one or more second network nodes are base stations. In some embodiments, the first network node is configured to perform any of the methods of the second aspect.

[0013] According to a second aspect of this disclosure, a method for RIM at a second network node is provided. The method includes pausing one or more ongoing processes for RIM mitigation at the second network node during at least one first time period, enabling a first network node to detect the presence of an RI from the second network node during the at least one first time period.

[0014] In some embodiments, the method further includes: determining whether a first network node detects an RI from a second network node during the at least one first time period; and determining whether to continue or stop the one or more ongoing processes for RIM mitigation, based at least on the determination of whether the first network node detects an RI from the second network node. In some embodiments, the method further includes at least one of the following operations: continuing the one or more ongoing processes for RIM mitigation in response to determining that the first network node detects an RI from the second network node during the at least one first time period; and stopping the one or more ongoing processes for RIM mitigation in response to determining that the first network node does not detect an RI from the second network node during the at least one first time period.

[0015] In some embodiments, the method further includes: determining whether a first network node detects an RI from a second network node during a second time period of performing at least one of the one or more ongoing processes for RIM mitigation, wherein determining whether to continue or stop the one or more ongoing processes for RIM mitigation is based at least on: determining whether the first network node detects an RI from the second network node during the second time period. In some embodiments, the method further includes at least one of the following operations: continuing the one or more ongoing processes for RIM mitigation in response to determining that the first network node detects an RI from the second network node during the at least one first time period and in response to determining that the first network node detects an RI from the second network node during the second time period; continuing the one or more ongoing processes for RIM mitigation in response to determining that the first network node detects an RI from the second network node during the at least one first time period and in response to determining that the first network node does not detect an RI from the second network node during the second time period; and stopping the one or more ongoing processes for RIM mitigation in response to determining that the first network node does not detect an RI from the second network node during the at least one first time period and in response to determining that the first network node does not detect an RI from the second network node during the second time period.

[0016] In some embodiments, the method further includes: generating a pseudo downlink service when no downlink service is to be transmitted during the at least one first time period; and transmitting the pseudo downlink service during the at least one first time period. In some embodiments, the pseudo downlink service is generated by padding. In some embodiments, the pseudo downlink service is scrambled using a Radio Network Temporary Identifier (RNTI) that cannot be descrambled by any terminal device.

[0017] In some embodiments, the at least one first time period is at least one frame. In some embodiments, at least one of the first network node and the second network node is a base station. In some embodiments, the first network node is configured to perform any of the methods of the first aspect.

[0018] According to a third aspect of this disclosure, a first network node is provided. The first network node includes: a processor; and a memory storing instructions that, when executed by the processor, cause the first network node to: detect the presence of an RI from the one or more second network nodes during at least a first time period during which one or more ongoing processes for RIM mitigation at the first network node and one or more second network nodes are paused. In some embodiments, the instructions, when executed by the processor, also cause the first network node to perform any of the methods of the first aspect.

[0019] According to a fourth aspect of this disclosure, a second network node is provided. The second network node includes: a processor; and a memory storing instructions that, when executed by the processor, cause the second network node to: suspend one or more ongoing processes for RIM mitigation during at least one first time period, enabling a first network node to detect the presence of an RI from the second network node during the at least one first time period. In some embodiments, the instructions, when executed by the processor, also cause the second network node to perform any of the methods of the second aspect.

[0020] According to a fifth aspect of this disclosure, a first network node is provided. The first network node includes a detection module configured to detect the presence of an RI (Reactivity Indicator) from the one or more second network nodes during at least a first time period during which one or more ongoing processes for RIM mitigation are paused at the first network node and one or more second network nodes. In some embodiments, the first network node includes one or more additional modules, each additional module performing any step of any method of the first aspect.

[0021] According to a sixth aspect of this disclosure, a second network node is provided. The second network node includes a pause module configured to pause one or more ongoing processes for RIM mitigation during at least one first time period, enabling a first network node to detect the presence of an RIM from the second network node during the at least one first time period. In some embodiments, the second network node includes one or more additional modules, each additional module performing any step of any method of the second aspect.

[0022] According to a seventh aspect of this disclosure, a computer program including instructions is provided. When executed by at least one processor, the instructions cause the at least one processor to perform any of the methods of the first and / or second aspects.

[0023] According to an eighth aspect of this disclosure, a carrier comprising the computer program of the seventh aspect is provided. In some embodiments, the carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0024] According to a ninth aspect of this disclosure, a telecommunications system is provided. The telecommunications system includes one or more first network nodes, each first network node including: a processor; and a memory storing instructions that, when executed by the processor, cause the corresponding first network node to: detect the presence of an RI (Reference Indicator) from the one or more second network nodes during at least a first time period during which one or more ongoing processes for RIM (Reference Indicator Mitigation) at the one or more first network nodes and one or more second network nodes are suspended. The telecommunications system also includes one or more second network nodes, each second network node including: a processor; and a memory storing instructions that, when executed by the processor, cause the corresponding second network node to: suspend one or more ongoing processes for RIM mitigation at the corresponding second network node during the at least one first time period, such that the one or more first network nodes are capable of detecting the presence of an RI from the one or more second network nodes during the at least one first time period.

[0025] In some embodiments, when the instructions stored in the memory of the corresponding first network node are executed by the processor of the corresponding first network node, the corresponding first network node also performs any method of the first aspect. In some embodiments, when the instructions stored in the memory of the corresponding second network node are executed by the processor of the corresponding second network node, the corresponding second network node also performs any method of the second aspect.

[0026] Through some embodiments of this disclosure, an alternative solution is provided for improving the performance of network nodes (e.g., base stations) by properly initiating / continuing or stopping RIM mitigation without using the 3GPP-defined RIM framework (without RIM reference signals). Using RIM RS signaling could result in transmitting numerous signals (one for each base station affected by remote interference), potentially exceeding the RIM RS detection capabilities of the base station. This solution is simpler than standardized solutions and has reduced development costs. Furthermore, the use of RIM RS signaling on the air interface can be avoided, which, for example, reduces the cost and effort required to adjust parameters defined for RIM RS signaling. Attached Figure Description

[0027] Figure 1 This is a diagram illustrating an exemplary network capable of applying RIM according to embodiments of the present disclosure.

[0028] Figure 2 This is a diagram illustrating an exemplary process for RIM.

[0029] Figure 3A This is a diagram illustrating another exemplary process used for RIM.

[0030] Figure 3B This is a diagram illustrating another exemplary process used for RIM.

[0031] Figure 4 This is a diagram illustrating an exemplary process for RIM according to an embodiment of the present disclosure.

[0032] Figure 5 This is a diagram illustrating an exemplary configuration of a detection system frame number (SFN) according to an embodiment of the present disclosure.

[0033] Figure 6 This is a diagram illustrating an exemplary RI detection according to an embodiment of the present disclosure.

[0034] Figure 7 This is a flowchart illustrating an exemplary method for RIM according to embodiments of the present disclosure.

[0035] Figure 8 This is a flowchart illustrating an example method for RIM at a first network node according to an embodiment of the present disclosure.

[0036] Figure 9 This is a flowchart illustrating an example method for RIM at a second network node according to an embodiment of the present disclosure.

[0037] Figure 10 An embodiment of an arrangement that can be used in a network node according to an embodiment of the present disclosure is illustrated schematically.

[0038] Figure 11 This is a block diagram of an exemplary first network node according to an embodiment of the present disclosure.

[0039] Figure 12 This is a block diagram of an exemplary second network node according to an embodiment of the present disclosure.

[0040] Figure 13 Examples of communication systems according to some embodiments of this disclosure are shown.

[0041] Figure 14 Exemplary user equipment (UE) according to some embodiments of this disclosure is shown.

[0042] Figure 15 Exemplary network nodes according to some embodiments of this disclosure are shown.

[0043] Figure 16 This is a block diagram of an exemplary host based on the aspects described herein, which may be... Figure 13 An example of a host computer.

[0044] Figure 17 This is a block diagram illustrating an exemplary virtualization environment capable of virtualizing functionality implemented by some embodiments.

[0045] Figure 18 A communication diagram is shown illustrating an exemplary host communicating with an exemplary UE via an exemplary network node through a partial wireless connection, according to some embodiments of the present disclosure. Detailed Implementation

[0046] The present disclosure is described below with reference to embodiments illustrated in the accompanying drawings. However, it should be understood that these descriptions are provided for illustrative purposes only and are not intended to limit the scope of the disclosure. Furthermore, descriptions of known structures and techniques are omitted below to avoid unnecessarily obscuring the concept of the present disclosure.

[0047] Those skilled in the art will understand that the term "exemplary" is used herein to mean "illustrative" or "serves as an example" and is not intended to imply that a particular embodiment is superior to another or that a particular feature is essential. Similarly, unless the context clearly indicates otherwise, the terms "first," "second," "third," and "fourth," and similar terms, are used only to distinguish one particular instance of an item or feature from another particular instance, and do not indicate a particular order or arrangement. Furthermore, as used herein, the term "step" is intended to be synonymous with "operation" or "action." Unless the context or details of the described operations clearly indicate otherwise, any description of a sequence of steps herein does not imply that these operations must be performed in a particular order, or even in any order.

[0048] Unless explicitly defined herein or understood from the context, the conditional language used herein (e.g., “can,” “may,” “can,” “for example,” etc.) is generally intended to convey that some embodiments include certain features, elements, and / or steps while other embodiments do not include said features, elements, and / or states. Therefore, such conditional language is not generally intended to imply that a feature, element, and / or step is necessary for one or more embodiments in any case, or to imply that one or more embodiments must include logic circuitry to determine, with or without the author’s input or permission, whether to include those features, elements, and / or states in any particular embodiment, or to perform said features, elements, and / or states in any particular embodiment. Furthermore, the term “or” is used in an inclusive sense (and not an exclusionary sense) such that when used, for example, to connect a list of elements, the term “or” indicates one, some, or all of the elements in the list. In addition to having its ordinary meaning, the term “each” as used herein may also mean any subset of the set of elements to which the term “each” is applied.

[0049] The term “based on” should be interpreted as “at least partially based on”. The terms “one embodiment” and “embodiment” should be interpreted as “at least one embodiment”. The term “another embodiment” should be interpreted as “at least one other embodiment”. Other explicit and implicit definitions may be included below. Additionally, unless expressly defined otherwise in the text, phrases such as “at least one of X, Y, and Z” should be understood in context as generally used to express that items, terms, etc., may be X, Y, or Z or combinations thereof.

[0050] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context explicitly indicates otherwise. It will also be understood that, when used herein, the words “comprising,” “having,” “including,” etc., indicate the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. It will also be understood that, unless explicitly stated to the contrary, when used herein, the terms “connected,” “connected to,” “connected to,” etc., mean only that there is an electrical or communication connection between two elements and that they may be directly or indirectly connected.

[0051] Of course, this disclosure may be implemented in other specific ways than those set forth herein without departing from the scope and essence of this disclosure. One or more specific processes discussed below can be performed in any electronic device including one or more appropriately configured processing circuits, which in some embodiments may be embodied in one or more application-specific integrated circuits (ASICs). In some embodiments, these processing circuits may include one or more microprocessors, microcontrollers, and / or digital signal processors programmed with appropriate software and / or firmware to implement one or more of the above operations and variations thereof. In some embodiments, these processing circuits may include custom hardware performing one or more of the above functions. The presented embodiments should therefore be considered illustrative rather than restrictive in all respects.

[0052] Although various embodiments of this disclosure will be shown in the accompanying drawings and described in the following detailed description, it should be understood that this disclosure is not limited to the disclosed embodiments, but is capable of various rearrangements, modifications and substitutions without departing from the disclosure as set forth and defined in the appended claims.

[0053] Furthermore, please note that although the following description of some embodiments of this disclosure is given in the context of 5G NR, this disclosure is not limited thereto. In fact, the inventive concepts of this disclosure can be applied to any suitable communication architecture as long as remote interference management (RIM) is involved, such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS), GSM Evolution Enhanced Data Rate (EDGE), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Time Division Synchronous CDMA (TD-SCDMA), CDMA2000, Global Microwave Access Interoperability (WiMAX), Wireless Fidelity (Wi-Fi), 4th Generation Long Term Evolution (LTE), LTE-Advanced (LTE-A), or 5G NR, 6th Generation (6G) mobile system standards, etc. Therefore, those skilled in the art will readily understand that the terms used herein can also refer to their equivalents in any other infrastructure. For example, the term "terminal device" as used herein can refer to UE, mobile device, mobile terminal, mobile station, user equipment, user terminal, wireless device, wireless terminal, or any other equivalent. For example, the term “network node” as used in this article may refer to a Transmitter / Receive Point (TRP), a base station, a base transceiver station, an access point, a hotspot, a NodeB, an evolved NodeB (eNB), a gNB, a network element, a satellite, an aircraft, or any other equivalent.

[0054] Furthermore, the terms "attacker," "attacker cell," "attacker base station," and "attacker BS" are sometimes used interchangeably and can refer to a network node that interferes with other nodes. Additionally, the terms "victim," "victim cell," "victim base station," and "victim BS" are sometimes used interchangeably and can refer to a network node that is interfered with by other nodes.

[0055] As mentioned above, atmospheric waveguided signals are a seasonal natural phenomenon that is largely dependent on atmospheric conditions. It primarily occurs in mid- or low-latitude regions, such as warm and humid coastal areas. Horizontal layers in the lower atmosphere guide radio signals to propagate along the Earth's curvature with minimal signal attenuation.

[0056] In TDD networks, the Guard Period (GP) combats cross-link interference between uplink and downlink through good radio frame time alignment between base stations. During the downlink-to-uplink handover, the UE receives DL transmissions during the GP, and these DL transmissions therefore cannot interfere with subsequent uplink transmissions after the GP. This means that the duration of the GP limits the distance between base station radio transmitters. The GP is part of a special subframe. Several configurations are defined in 3GPP. For example, if a GP with 4 symbols is configured, the maximum distance between transmitters for the mid-band is 4 * 10.7 = 42.8 km. Atmospheric waveguide effects can allow radio transmissions to reach hundreds of kilometers. Therefore, a downlink transmission from one base station (i.e., the attacker) will be received in the uplink time slot of another base station (i.e., the victim).

[0057] Figure 1 This is a diagram illustrating an exemplary network 10 capable of applying RIM according to embodiments of the present disclosure. Figure 1 As shown, network 10 may include multiple base stations providing services to multiple cells 110, 120, and 130. As mentioned above, atmospheric guide waves can be formed between cell 1 (and its corresponding base station) 110 and cell 2 (and its corresponding base station) 120, therefore their DL signals may interfere with the UL signal of another cell, as indicated by double arrow 115. Furthermore, although... Figure 1 Only two cells / base stations interfering with each other are shown in this disclosure, but the present disclosure is not limited thereto. In some other embodiments, more than two cells / base stations may be subject to remote interference, and some of them may be attackers, some of them may be victims, and some of them may be both attackers and victims.

[0058] To address this remote interference, 3GPP has proposed several frameworks for RIM. The 3GPP RIM framework can include three steps:

[0059] -RIM detection is used to determine whether a victim cell (e.g., cell 120) is affected by RI (remote interference).

[0060] -RIM location is used to pinpoint the origin of the RI wave and determine if the guided wave is persistent.

[0061] -RIM mitigation is used to take action at the attacker's cell (e.g., cell 110) and / or the victim's cell (e.g., cell 120) to reduce the impact of remote interference.

[0062] 3GPP has specified several RIM frameworks. Figure 2 This demonstrates how the distributed RIM framework 1 works. This framework provides autonomous RIM without the need for external nodes (e.g., operation and maintenance (O&M) systems) for control.

[0063] To coordinate the above three steps, 3GPP defines reference signals for transmission between the victim base station (e.g., cell 120) and the attacker base station (e.g., cell 110):

[0064] RS-1 is sent by victim cell 120 to inform attacker 110 of the existence of an affected victim cell and to help attacker 110 identify how many UL Orthogonal Frequency Division Multiplexing (OFDM) symbols are affected at victim cell 120. Attacker cell 110 monitors this to determine when to take mitigation measures and trigger RS-2 transmission.

[0065] Applying mitigation in the attacking cell 110 will typically result in RI mitigation in the victim cell 120. Therefore, the attacking cell 110 sends RS-2 to allow the victim cell 120 to determine whether the RI persists. The absence of RS-2 indicates that the atmospheric duct has disappeared, and RI mitigation can then be stopped.

[0066] refer to Figure 2 At step S205, victim 120 can detect remote interference. Furthermore, as indicated by the dashed arrow at step S205a, victim 120 can also cause RI to attacker 110, for example, due to the reciprocity of atmospheric guided waves. In other words, the victim's BS / cell can also be the attacker's BS / cell, and vice versa.

[0067] At step S210a, when remote interference is detected, victim 120 may start monitoring RIM-RS from other base stations / cells, and victim 120 may also send its own RIM-RS (i.e., RS-1), for example to notify other base stations / cells (e.g., attacker 110) of the presence of RI at victim 120.

[0068] Simultaneously or at different times (earlier than or later than steps S210a and / or S210b), for example, when an RI caused by victim 120 is detected at step S205a, or when another triggering event occurs, attacker 110 may begin monitoring RIM-RS from other base stations / cells at step S210c.

[0069] Regardless of how attacker 110 initiates its RS monitoring, it can detect RS-1 transmitted from victim 120, or otherwise detect its remote interference to victim 120. Upon detection, attacker 110 can apply one or more RI mitigation schemes at step S215a and transmit its own RIM-RS (i.e., RS-2) at step S215b. In this case, victim 120 can determine whether atmospheric guided waves still exist by determining whether RS-2 can be detected at victim 120.

[0070] After a period of time, the atmospheric guided wave disappears, so RS-2 is not detected at the victim 120 at step S220. In this case, at step S225, the victim 120 can stop transmitting RS-1, so at step S230, the attacker 110 cannot detect RS-1. Then, at step S235, the attacker 110 can stop monitoring RIM-RS and restore its original configuration, for example, stop the RIM mitigation scheme and stop RS-2 transmission.

[0071] However, as mentioned above, this framework and reference signals defined in 3GPP will result in significant costs. For example, it requires signaling and complex configuration, as well as extensive coordination with operators and other vendors who may supply network equipment to them. Furthermore, many parameters need to be adjusted according to 3GPP TS 28.541. In addition, the logic for coordinating RIM detection, location, and mitigation will also be highly complex.

[0072] Therefore, due to the high cost and complexity of the framework defined by 3GPP, many base station vendors attempt to find shortcuts, but this can cause problems, as follows. Figure 3A and Figure 3B As illustrated in the example shown.

[0073] Figure 3A This is a diagram illustrating an exemplary shortcut solution for RIM. (See diagram for example.) Figure 3A As shown, the base station only supports RIM detection + RIM mitigation, i.e., it does not use RIM RS. In this shortcut solution, when RI is detected at step S310, the base station (e.g., cell A 110 and cell B 120) will perform blind DL and / or UL mitigation. Since there is no coordination between the attacker base station and the victim base station using RIM RS1 and RIM RS2, the victim base station (e.g., cell B 120) does not know whether the remote interference has truly disappeared or disappeared due to mitigation by the attacker base station (e.g., cell A 110).

[0074] Figure 3B This is a diagram of another exemplary shortcut solution for RIM. (See diagram below.) Figure 3BAs shown, the base station supports RIM detection + RIM location (RS1 only) + RIM mitigation. In this shortcut solution, when remote interference is detected in step S350, the victim base station (e.g., cell B 120) will send RS1 to the attacker base station (e.g., cell A 110) in step S360. Figure 3B As shown, the attacking base station will mitigate the damage based on the received RS1. Furthermore, since RS2 is not transmitted from the attacking base station, the victim base station does not know when to stop transmitting RS1. Additionally, when cell A 110 is also a victim, it can also transmit RS1 to cell B 120, as indicated by the arrow pointing from cell A 110 to cell B 120 at step S360.

[0075] Furthermore, as mentioned above, since these shortcut solutions are not specified in 3GPP, these solutions cannot be used between base stations from different vendors.

[0076] As can be seen from the above, the entire RIM framework, including RIM RS transmission and reception, is costly, and shortcuts used to reduce costs cannot detect whether remote interference has truly disappeared. To address or at least partially mitigate these problems, some embodiments of this disclosure propose using simple and efficient detection methods to check whether remote interference still exists, and thus can automatically initiate / stop mitigation based on the detection results.

[0077] In some embodiments, all base stations can pause or stop RIM mitigation within the same specific probe SFN, or more generally, pause or stop RIM mitigation within a specific frame used for probe. In some embodiments, all base stations can detect and count the remote interference level on that specific probe SFN. In some embodiments, base stations can determine whether the remote interference has disappeared based on the probe RIM detection results. In some embodiments, base stations can stop or restart RIM mitigation based on the remote interference detection results.

[0078] In some embodiments, a detection method is proposed that can determine the presence of remote interference by time-coordinated measurements in the base station network, without using the RIM framework defined in 3GPP.

[0079] In some embodiments, the RIM RS defined by 3GPP for determining the presence of remote interference is not required. In some embodiments, the method may utilize new network-coordinated measurements that allow base stations to make decisions for RIM using traditional measurements within the base station.

[0080] This disclosure provides an alternative solution for a portion of the RIM framework defined by 3GPP through some embodiments. This solution is simpler and has reduced development costs than the standardized solution. With this solution, base stations can be commercially deployed in real-world networks and are suitable for different vendors. Furthermore, the use of RIM RS signaling on the air interface can be avoided, which, for example, reduces the cost and effort required to adjust parameters defined for RIM RS signaling. Receiving these signals requires a minimum SINR, which is not typically met in all scenarios. Using RIM RS signaling could result in transmitting numerous signals (one signal per base station affected by remote interference), potentially exceeding the RIM RS detection capabilities of the base station. Moreover, this solution is a simple solution that reduces many complexities on the base station side.

[0081] Next, the following will refer to Figure 4 Provide a detailed description of the procedures used for RIM.

[0082] Figure 4 This is a diagram illustrating an exemplary process for RIM according to an embodiment of the present disclosure. Figure 4 As shown, the process can be broadly divided into two parts: the "traditional" part and the "RIM detection" part. In some embodiments, one part can be performed independently of the other. In other words, in some embodiments, the traditional part can be omitted. In some other embodiments, they can be performed together in a coordinated manner, thereby reducing the amount of work required to upgrade existing base station hardware / software.

[0083] like Figure 4 As shown, the RIM detection section (e.g., steps S430a to S440a and steps S430b to S440b) can be performed by the attacker 110 and the victim 120, respectively, to manage remote interference. In some embodiments, in addition to the RIM detection section, the conventional section (e.g., Figure 3A The solution shown can also be executed by both attacker 110 and victim 120. In other words, attacker 110 and victim 120 can execute both parts together, or execute only the RIM detection part.

[0084] and Figure 3A The steps are similar, and at step S405, for example due to atmospheric waveguide effects, remote interference may occur at the attacker 110 and / or the victim 120. In this case, at step S410a, the attacker 110 can detect the remote interference (if any). Furthermore, at step S410b, the victim 120 can also detect the remote interference (if any). In some embodiments, methods such as... can be used at the attacker 110 and / or the victim 120. Figure 3AThe shortcut shown is a conventional solution. For example, at step S415a, attacker 110 may perform one or more RIM mitigation procedures / measures to reduce or eliminate potential remote interference detected at victim 120 and / or attacker 110 itself. For example, at step S415b, victim 120 may perform one or more RIM mitigation procedures / measures to reduce or eliminate potential remote interference detected at attacker 110 and / or victim 120 itself.

[0085] As referenced above Figure 3A Without the RIM RS transmitted between attacker 110 and victim 120, attacker 110 and / or victim 120 cannot determine whether and when the remote interference has disappeared. For example, as shown in step S420, even if the remote interference disappears, attacker 110 and victim 120 will not stop the RIM mitigation process because they are unaware that the remote interference has disappeared.

[0086] This is where RIM detection comes in. (Reference) Figure 4 In the "RIM Detection" section, attacker 110 and / or victim 120 can obtain this information through the following process. At step S430a, attacker 110 can pause or stop its RIM mitigation on one or more detection SFNs. Similarly, at step S430b, victim 120 can also pause or stop its RIM mitigation on the same one or more detection SFNs. In some embodiments, any BS involved in RIM (including but not limited to attacker 110 and victim 120) can stop its RIM mitigation on the same one or more detection SFNs. By detecting the SFNs, attacker 110 and / or victim 120 can detect whether the atmospheric guided wave still exists or has disappeared.

[0087] although Figure 4 This disclosure uses only SFNs or frames as the time period for detection, but it is not limited thereto. In some other embodiments, the detection time period during which RIM mitigation is paused or stopped may differ from the SFN or frame. For example, the detection time period may be a half-frame, a subframe, a time slot, or a time period of different lengths in the time domain. In other words, the detection time period can have any length in the time domain, as long as it is long enough for the relevant base station to detect remote interference.

[0088] In some embodiments, one or more fixed SFNs for each system frame period can be selected to detect the presence of atmospheric ducts. In some embodiments, RIM mitigation can be performed in a variety of ways. For example, the base station can pause or stop all RIM mitigation in order to be able to check for the presence of atmospheric ducts at the detection SFN (i.e., the SFN in the network used to detect atmospheric ducts).

[0089] At step S435a, attacker 110 can detect remote interference on each probe SFN and can calculate the remote interference level at the end of RIM detection, which will refer to Figure 6 A detailed explanation follows. Similarly, at step S435b, the victim 120 can also detect remote interference on each probe SFN and can calculate the remote interference level at the end of RIM detection. In some embodiments, the remote interference detected on the probe SFN can be recorded. In some embodiments, the interference level can be used to determine the RIM detection result.

[0090] At step S440a, attacker 110 may use probe-based RIM detection results, or both probe-based RIM detection results and conventional RIM detection results, to determine whether to stop or continue RIM mitigation. Similarly, at step S440b, victim 120 may also use probe-based RIM detection results, or both probe-based RIM detection results and conventional RIM detection results, to determine whether to stop or continue RIM mitigation. In some embodiments, conventional RIM detection results may be determined based on the fact that one or more RI levels are detected on one or more non-probe SFNs. If atmospheric ducts are detected, RIM mitigation may continue at attacker 110 and / or victim 120. If atmospheric ducts are not detected, RIM mitigation may be stopped at attacker 110 and / or victim 120.

[0091] Figure 5 This diagram illustrates an exemplary configuration for detecting SFNs according to embodiments of the present disclosure. In some embodiments, to simplify base station implementation, one or more fixed SFN numbers may be defined as detection SFN numbers. For example, such as Figure 5 As shown, the probe SFN is selected as SFN 1023. In other words, RIM mitigation can be paused or stopped on SFN 1023. Furthermore, SFN0 through SFN 1022 can be non-probe SFNs, and RIM mitigation will be active during these SNFs.

[0092] However, this disclosure is not limited thereto. In some other embodiments, more than one SFN can be selected as the probe SFN within each system frame period. For example, both SFN 511 and SFN 1023 can be selected as probe SFNs. For example, SFN 123, SFN 511, SFN 789, and SFN 1023 can be selected as probe SFNs. For yet another example, any appropriate number of SFNs can be selected as probe SFNs as long as the selection does not cause a significant performance degradation.

[0093] also, Figure 5The diagram shows all SFN 1023 selected as probe SFNs during different system frame periods. However, this disclosure is not limited thereto. In some embodiments, probe SFNs may be selected non-periodically. For example, SFN 1023 may be selected during one system frame period, while SFN 511 may be selected as a substitute or supplement to SFN 1023 during another system frame period. As another example, some probe SFNs may be selected periodically, while others may not be selected (e.g., they may be selected only once or twice).

[0094] In some embodiments, the selection of a probe SFN can be determined by the base station itself in a hard-coded manner. In some other embodiments, the selection of a probe SFN can be specified by another network node (e.g., OAM) and can be persistent or semi-persistent. In some other embodiments, the selection of a probe SFN can be dynamically configured by another network node (e.g., OAM) and can be changed intermittently as needed by the operator. In some embodiments, the selection of a probe SFN can be any suitable combination of the embodiments described above. For example, some probe SFNs can be determined in a hard-coded manner, while others can be determined through dynamic configuration from the OAM.

[0095] In some embodiments, remote interference measured during a single probe SFN may not accurately reflect the level of remote interference. Therefore, a RIM detection period can be defined that includes multiple probe SFNs (e.g., such as...). Figure 6 As shown in the figure, the base station can calculate the detection result of the RIM at the end of the RIM detection period.

[0096] Figure 6 This is a diagram illustrating an exemplary RI detection according to an embodiment of this disclosure. (As shown) Figure 6 As shown, on a probe SFN (e.g., SFN 1023), the base station can detect and store probed remote interference. In some embodiments where the RIM detection period is 10 minutes, at the end of the RIM detection period (i.e., SFN 607), the base station can calculate the remote interference level for that period. In some embodiments, this can be done, for example, by calculating the average of the interference plus noise (IpN) on all stored probe SFNs (which is one of the conditions used to check for the presence of RIM, and other conditions may also exist). However, this disclosure is not limited to this. In some other embodiments, another filtered value of the IpN detected on the probe SFN can be used. For example, the maximum value of the IpN can be determined as the RI value / level for determining the presence of remote interference.

[0097] In some embodiments, if the attacking base station has no downlink traffic on the probed SFN, the victim base station cannot detect the presence of an atmospheric duct. Therefore, the attacking base station can generate downlink traffic load on the probed SFN as follows:

[0098] - When probing the SNF, if there is no downlink traffic:

[0099] - Base stations can generate Physical Downlink Shared Channel (PDSCH) services by padding.

[0100] - PDSCH fill load can vary and does not need to occupy all available bandwidth.

[0101] - The RNTI of the PDSCH filling service can be selected as a value that cannot be decoded / descrambled by any UE.

[0102] In some embodiments, at the end of the RIM detection period:

[0103] -If the base station is operating normally (e.g., Figure 4 No long-range interference was detected in either the conventional part shown or the detection method:

[0104] - The base station can determine that the atmospheric waveguide no longer exists.

[0105] - The base station can determine whether RIM mitigation can be stopped.

[0106] -If the base station does not detect remote interference using conventional detection methods, but detects remote interference using detection methods:

[0107] - The base station can confirm that the atmospheric waveguide still exists.

[0108] - The base station can determine that it can continue to enable all RIM mitigation methods.

[0109] In some embodiments, to simplify the algorithm's complexity, two configurable thresholds can be used to determine whether remote interference is detected by the detection method. In some embodiments, remote interference is detected if the detected RIM value is greater than a detection mitigation threshold (e.g., -105 dBm). In some embodiments, remote interference disappears if the detected RIM value is less than a detection mitigation backoff threshold (e.g., -115 dBm).

[0110] Figure 7This is a flowchart illustrating an exemplary method for RIM according to an embodiment of the present disclosure. The method may begin at step S710, where a base station may detect the presence of RIM from other base stations. If not, the base station may continue to detect periodically and / or in response to events (e.g., explicit instructions from its operator). If yes, at step S720, the base station may initiate its RIM mitigation measures. At step S730, the base station may stop the RIM mitigation measures on each probe SFN, such that all base stations in the network or base stations involved in RIM (including the base station itself) may detect the presence of RI at step S740, for example, by measuring the RI level from other base stations and / or providing DL services (e.g., PDSCH transmission via padding as described above). At step S750, the base station may store its measurement results, and at step S760, at the end of the RIM detection period, process the latest and / or previous results. At step S770, the base station may determine whether the processing result indicates RI. If yes (meaning the remote interference still exists), the base station can continue its RIM mitigation measures and return to step S730 to repeat the steps for probe-based RI detection. If no (meaning the remote interference has disappeared), the base station can stop its RIM mitigation measures because the remote interference no longer exists.

[0111] The above embodiments provide an alternative solution for a portion of the RIM framework defined by 3GPP. This solution is simpler and has reduced development costs than the standardized solution. With this solution, base stations can be commercially deployed in real-world networks and are suitable for different vendors. Furthermore, the use of RIMRS signaling on the air interface can be avoided, which, for example, reduces the cost and effort required to adjust parameters defined for RIM RS signaling. Receiving these signals requires a minimum SINR, which is not always met in all scenarios. Using RIM RS signaling could result in transmitting numerous signals (one for each base station affected by remote interference), potentially exceeding the RIM RS detection capabilities of the base station. Moreover, this solution is a simple way to reduce many complexities on the base station side.

[0112] Figure 8This is a flowchart illustrating an example method 800 for RIM at a first network node according to an embodiment of the present disclosure. Method 800 may be performed at a base station (e.g., victim 120). Method 800 may include step S810. However, the present disclosure is not limited thereto. In some other embodiments, method 800 may include more steps, different steps, or any combination thereof. Furthermore, when multiple steps are involved, the steps of method 800 may be performed in an order different from that described herein. Additionally, in some embodiments, steps in method 800 may be broken down into multiple sub-steps and performed by different entities, and / or multiple steps in method 800 may be combined into a single step.

[0113] Method 800 may begin at step S810, wherein a first network node may detect whether an RI from the one or more second network nodes exists during at least a first time period of one or more ongoing processes for RIM mitigation at the first network node and one or more second network nodes.

[0114] In some embodiments, method 800 may further include: determining whether to continue or stop one or more ongoing processes for RIM mitigation based at least on the detection of the presence or absence of an RI from the one or more second network nodes. In some embodiments, method 800 may further include at least one of the following operations: continuing and / or triggering the continuation of one or more ongoing processes for RIM mitigation in response to the detection of an RI from the one or more second network nodes during the at least one first time period; and stopping and / or triggering the cessation of one or more ongoing processes for RIM mitigation in response to the absence of an RI from the one or more second network nodes during the at least one first time period.

[0115] In some embodiments, determining whether to continue or stop the one or more ongoing processes for RIM mitigation may also be based at least on whether an RI (Information Receipt) is detected from the one or more second network nodes during a second time period of performing at least one of the one or more ongoing processes for RIM mitigation. In some embodiments, method 800 may further include at least one of the following operations: in response to detecting an RI from the one or more second network nodes during the at least one first time period and in response to detecting an RI from the one or more second network nodes during a second time period, continuing and / or triggering the continuation of the one or more ongoing processes for RIM mitigation; in response to detecting an RI from the one or more second network nodes during the at least one first time period and in response to not detecting an RI from the one or more second network nodes during the second time period, continuing and / or triggering the continuation of the one or more ongoing processes for RIM mitigation; and in response to not detecting an RI from the one or more second network nodes during the at least one first time period and in response to not detecting an RI from the one or more second network nodes during the second time period, stopping and / or triggering the cessation of the one or more ongoing processes for RIM mitigation.

[0116] In some embodiments, when the at least one first time period includes more than one first time period within a RIM detection period, detecting whether an RI from the one or more second network nodes exists during the at least one first time period may include: detecting the RI level during all first time periods within the RIM detection period; calculating a filtered RI value at least based on the detected RI levels at the end of the RIM detection period; and detecting whether an RI from the one or more second network nodes exists at least based on the filtered RI value. In some embodiments, detecting whether an RI from the one or more second network nodes exists at least based on the filtered RI value may include at least one of the following operations: detecting the existence of an RI from the one or more second network nodes in response to determining that the filtered RI value is higher than a first threshold; and detecting the absence of an RI from the one or more second network nodes in response to determining that the filtered RI value is lower than a second threshold. In some embodiments, the filtered RI value may be at least one of the following: the average of the detected RI levels; and the maximum value of the detected RI levels.

[0117] In some embodiments, when the at least one first time period comprises only a single first time period within the RIM detection period, detecting whether an RI from the one or more second network nodes exists during the at least one first time period may include: detecting the RI level during the single first time period; and detecting whether an RI from the one or more second network nodes exists, at least based on the RI level. In some embodiments, detecting whether an RI from the one or more second network nodes exists, at least based on the RI level, may include at least one of the following operations: detecting the existence of an RI from the one or more second network nodes in response to determining that the RI level is higher than a first threshold; and detecting the absence of an RI from the one or more second network nodes in response to determining that the RI level is lower than a second threshold. In some embodiments, the first threshold may be higher than or equal to the second threshold.

[0118] In some embodiments, the at least one first time period may be at least one frame. In some embodiments, at least one of the first network node and the one or more second network nodes may be a base station. In some embodiments, the first network node may be configured to perform reference... Figure 9 Any method described.

[0119] Figure 9 This is a flowchart illustrating an example method 900 for RIM at a second network node according to an embodiment of the present disclosure. Method 900 can be performed at a base station (e.g., attacker 110). Method 900 may include step S910. However, the present disclosure is not limited thereto. In some other embodiments, method 900 may include more steps, different steps, or any combination thereof. Furthermore, when multiple steps are involved, the steps of method 900 may be performed in an order different from that described herein. In addition, in some embodiments, the steps in method 900 may be broken down into multiple sub-steps and performed by different entities, and / or multiple steps in method 900 may be combined into a single step.

[0120] Method 900 may begin at step S910, wherein the second network node may suspend one or more ongoing processes for RIM mitigation at the second network node during at least one first time period, such that the first network node is able to detect whether an RI from the second network node exists during the at least one first time period.

[0121] In some embodiments, method 900 may further include: determining whether a first network node detects an RI from a second network node during the at least one first time period; and determining whether to continue or stop the one or more ongoing processes for RIM mitigation, based at least on the determination of whether the first network node detects an RI from the second network node. In some embodiments, method 900 may further include at least one of the following operations: continuing the one or more ongoing processes for RIM mitigation in response to determining that the first network node detects an RI from the second network node during the at least one first time period; and stopping the one or more ongoing processes for RIM mitigation in response to determining that the first network node does not detect an RI from the second network node during the at least one first time period.

[0122] In some embodiments, method 900 may further include: determining whether a first network node detects an RI from a second network node during a second time period of performing at least one of the one or more ongoing processes for RIM mitigation, wherein determining whether to continue or stop the one or more ongoing processes for RIM mitigation is based at least on: determining whether the first network node detects an RI from the second network node during the second time period. In some embodiments, method 900 may further include at least one of the following operations: continuing the one or more ongoing processes for RIM mitigation in response to determining that the first network node detects an RI from the second network node during the at least one first time period and in response to determining that the first network node detects an RI from the second network node during the second time period; continuing the one or more ongoing processes for RIM mitigation in response to determining that the first network node detects an RI from the second network node during the at least one first time period and in response to determining that the first network node does not detect an RI from the second network node during the second time period; and stopping the one or more ongoing processes for RIM mitigation in response to determining that the first network node does not detect an RI from the second network node during the at least one first time period and in response to determining that the first network node does not detect an RI from the second network node during the second time period.

[0123] In some embodiments, method 900 may further include: generating a pseudo downlink service when no downlink service is to be transmitted during the at least one first time period; and transmitting the pseudo downlink service during the at least one first time period. In some embodiments, the pseudo downlink service may be generated by padding. In some embodiments, the pseudo downlink service may be scrambled using an RNTI that cannot be descrambled by any terminal device.

[0124] In some embodiments, the at least one first time period may be at least one frame. In some embodiments, at least one of the first network node and the second network node may be a base station. In some embodiments, the first network node may be configured to perform reference... Figure 8 Any method described.

[0125] Figure 10 An embodiment of arrangement 1000, according to embodiments of the present disclosure, is illustrated schematically and can be used in a network node (e.g., attacker BS110 and / or victim BS120). Arrangement 1000 includes a processing unit 1006, for example, having a digital signal processor (DSP) or a central processing unit (CPU). Processing unit 1006 may be a single unit or multiple units for performing different actions of the processes described herein. Arrangement 1000 may also include an input unit 1002 for receiving signals from other entities and an output unit 1004 for providing signals to other entities. Input unit 1002 and output unit 1004 may be arranged as integrated entities or separate entities.

[0126] Furthermore, arrangement 1000 may include at least one computer program product 1008 having a non-volatile or volatile memory form, such as electrically erasable programmable read-only memory (EEPROM), flash memory, and / or hard disk drive. Computer program product 1008 includes computer program 1010, which includes code / computer-readable instructions that, when executed by processing unit 1006 in arrangement 1000, cause arrangement 1000 or a terminal device / network node including arrangement 1000 to perform, for example, previously combined... Figures 4 to 9 Or the action of the process described by any other variant.

[0127] Computer program 1010 can be configured as computer program code built in computer program module 1010A. Therefore, in an exemplary embodiment where arrangement 1000 is used in a first network node for RIM, the code in the computer program of arrangement 1000 includes: module 1010A, configured to detect the presence of RI from the one or more second network nodes during at least a first time period during which one or more ongoing processes for RIM mitigation at the first network node and one or more second network nodes are paused.

[0128] Additionally, computer program 1010 can also be configured as structured computer program code in computer program module 1010B. Therefore, in an exemplary embodiment using arrangement 1000 in a second network node for RIM, the code in the computer program of arrangement 1000 includes: module 1010B, configured to pause one or more ongoing processes for RIM mitigation at the second network node during at least one first time period, enabling the first network node to detect the presence of an RIM from the second network node during that at least one first time period.

[0129] Computer program modules are basically executable. Figures 4 to 9 The illustrated process operates to simulate network nodes. In other words, when different computer program modules are executed in the processing unit 1006, they can correspond to different modules in the network node.

[0130] Despite the above combination Figure 10 In the disclosed embodiments, the code means are implemented as a computer program module (which, when executed in a processor, causes the arrangement to perform the actions described above in conjunction with the accompanying drawings), but in alternative embodiments, at least one code means may be implemented as hardware circuitry, at least in part.

[0131] The processor may be a single CPU (Central Processing Unit), but may also include two or more processing units. For example, the processor may include a general-purpose microprocessor, an instruction set processor, and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)). The processor may also include onboard memory for caching purposes. The computer program may be carried by a computer program product associated with the processor. The computer program product may include a computer-readable medium on which the computer program is stored. For example, the computer program product may be flash memory, random access memory (RAM), read-only memory (ROM), or EEPROM, and in alternative embodiments, the aforementioned computer program modules may be distributed across different computer program products in the form of memory within network nodes.

[0132] An exemplary first network node for RIM is provided in accordance with the method 800 described above. Figure 11 This is a block diagram of a first network node 1100 according to an embodiment of the present disclosure. For example, in some embodiments, the first network node 1100 may be a victim 120.

[0133] The first network node 1100 can be configured to perform the above combination Figure 8 The described method 800. (e.g.) Figure 11As shown, the first network node 1100 may include a detection module 1110, configured to detect the presence of an RI from the one or more second network nodes during at least a first time period during which one or more ongoing processes for RIM mitigation are paused at the first network node and one or more second network nodes.

[0134] The above module 1110 can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of the following: configured to perform the above description and, for example, in Figure 8 The processor or microprocessor and appropriate software shown herein, along with memory, programmable logic device (PLD), or other electronic components or processing circuitry for storing the software, are described. Furthermore, the first network node 1100 may include one or more additional modules, each capable of executing the reference... Figure 8 Any step of the described method 800.

[0135] An exemplary second network node for RIM is provided in correspondence with method 900 as described above. Figure 12 This is a block diagram of a second network node 1200 according to an embodiment of the present disclosure. In some embodiments, the second network node 1200 may be, for example, an attacker 110.

[0136] The second network node 1200 can be configured to perform the above combination Figure 9 The described method 900. (e.g.) Figure 12 As shown, the second network node 1200 may include a pause module 1210, configured to pause one or more ongoing processes for RIM mitigation during at least one first time period, enabling the first network node to detect whether an RI from the second network node exists during the at least one first time period.

[0137] The module 1210 described above can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of the following: configured to perform the above description and, for example, in Figure 9 The processor or microprocessor and appropriate software shown in the diagram, along with memory, PLD, or other electronic components or processing circuitry for storing the software, are described. Furthermore, the second network node 1200 may include one or more additional modules, each capable of executing the reference... Figure 9 Any step of the described method 900.

[0138] Figure 13 An example of a communication system QQ100 according to some embodiments is shown.

[0139] In this example, the communication system QQ100 includes a telecommunications network QQ102 and a core network QQ106. The telecommunications network QQ102 includes an access network QQ104, such as a radio access network (RAN), and the core network QQ106 includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be collectively referred to as network node QQ110), or any other similar 3GPP access node or non-3GPP access point. Network node QQ110 facilitates direct or indirect connections of user equipment (UEs), such as connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may generally be referred to as UE QQ112) to the core network QQ106 via one or more radio connections.

[0140] Examples of wireless communication via wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wiring, cables, or other conductors. Furthermore, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in communication of data and / or signals (whether via wired or wireless connections). The communication system QQ100 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system, and / or interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar system.

[0141] UE QQ112 can be any of a wide variety of communication devices, including wireless devices that are deployed, configured, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 is deployed, capable of, configured, and / or operable to communicate directly or indirectly with UE QQ112 and / or with other network nodes or devices in telecommunication network QQ102 to achieve and / or provide network access (e.g., wireless network access) and / or to perform other functions (e.g., management) in telecommunication network QQ102.

[0142] In the depicted example, core network QQ106 connects network node QQ110 to one or more hosts (e.g., host QQ116). These connections can be direct or indirect via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) that are formed together with hardware and software components. The characteristics of these components can be substantially similar to those described with respect to UE, network nodes, and / or hosts, such that the description is generally applicable to the corresponding components of core network node QQ108. Example core network nodes include one or more of the following functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Unhiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0143] The host QQ116 may be owned or controlled by a service provider other than the operator or provider of the access network QQ104 and / or the telecommunications network QQ102, and may be operated by or on behalf of that service provider. The host QQ116 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0144] As a whole, Figure 13The QQ100 communication system enables connections between the UE, network nodes, and the host. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0145] In some examples, the QQ102 telecommunications network is a cellular network implementing 3GPP standardized features. Therefore, the QQ102 network can support network slicing to provide different logical networks to different devices connected to it. For example, the QQ102 network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive IoT services to yet another set of UEs.

[0146] In some examples, UE QQ112 is configured to send and / or receive information without direct human interaction. For example, the UE can be designed to send information to access network QQ104 according to a predetermined schedule when triggered by internal or external events or in response to a request from access network QQ104. Additionally, the UE can be configured to operate in single-RAT mode, multi-RAT mode, or multi-standard mode. For example, the UE can operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0147] In this example, the central hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and a network node (e.g., network node QQ110b). In some examples, the central hub QQ114 may be a controller, router, content source and analyzer, or any other communication device described herein relating to the UE. For example, the central hub QQ114 may be a broadband router that enables the UE to access the core network QQ106. As another example, the central hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node QQ110, or via executable code, scripts, processes, or other instructions in the central hub QQ114. As another example, the central hub QQ114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, it may perform data analysis or other processing. As another example, the central hub QQ114 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, the central QQ114 can retrieve VR assets, videos, audio, or other media or data related to perception information via network nodes, and then provide them directly to the UE after performing local processing and / or adding additional local content. In yet another example, the central QQ114 acts as a proxy server or coordinator for the UE, particularly if one or more of these UEs are low-energy IoT devices.

[0148] The central hub QQ114 may have a continuous / persistent or intermittent connection with the network node QQ110b. The central hub QQ114 may also allow different communication schemes and / or scheduling between the central hub QQ114 and the UE (e.g., UE QQ112c and / or QQ112d) and between the central hub QQ114 and the core network QQ106. In other examples, the central hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Furthermore, the central hub QQ114 may be configured to connect to an M2M service provider via the access network QQ104, and / or to another UE via a direct connection. In some scenarios, the UE can establish a wireless connection with the network node QQ110 while still being connected via the central hub QQ114 via a wired or wireless connection. In some embodiments, the central hub QQ114 may be a dedicated hub, i.e., a hub whose primary function is to route communication from the network node QQ110b to the UE / to route communication from the UE to the network node QQ110b. In other embodiments, the central hub QQ114 may be a non-dedicated hub, i.e., a device capable of operating to route communication between the UE and network node QQ110b, but additionally capable of operating as a communication start point and / or endpoint for certain data channels.

[0149] Figure 14 A UE QQ200 according to some embodiments is illustrated. As used herein, a UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0150] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated device. Alternatively, the UE may represent a device intended to be sold to or operated by a human user but which may not or initially may not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended to be sold to or operated by an end user but which may be associated with or operated for the benefit of the user (e.g., a smart power meter).

[0151] UE QQ200 includes processing circuitry QQ202, which is operatively coupled via bus QQ204 to input / output interface QQ206, power supply QQ208, memory QQ210, communication interface QQ212, and / or any other component, or any combination thereof. Some UEs may utilize Figure 14 The components shown may be all or a subset. The level of integration between components can vary depending on the UE. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0152] The processing circuit QQ202 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in memory QQ210. The processing circuit QQ202 can be implemented as: one or more hardware-implemented state machines (e.g., implemented with discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the foregoing. For example, the processing circuit QQ202 may include multiple central processing units (CPUs).

[0153] In this example, the input / output interface QQ206 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, directional keys, touchpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0154] In some embodiments, the power supply QQ208 is configured as a battery or battery pack. Other types of power sources can be used, such as external power sources (e.g., power outlets), photovoltaic devices, or batteries. The power supply QQ208 may also include power circuitry for delivering power from the power supply QQ208 itself and / or an external power source to various parts of the UEQQ200 via input circuitry or an interface such as a power cable. Power delivery can be used, for example, for charging the power supply QQ208. The power circuitry can perform any formatting, conversion, or other modifications on the power from the power supply QQ208 to suit the power for the various components of the UE QQ200 to which it is supplied power.

[0155] The memory QQ210 can be or is configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, hard disk, removable magnetic tape, flash drive, etc. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, widget, utility engine, or other application, and corresponding data QQ216. The memory QQ210 can store any one or a combination of various operating systems used by the UE QQ200.

[0156] The QQ210 memory can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." The QQ210 memory can allow the UE QQ200 to access instructions, applications, etc., stored on transient or non-transient storage media to unload or upload data. Articles such as those utilizing communication systems may be tangibly embodied in or contained in memory QQ210, which may be or include a device-readable storage medium.

[0157] The processing circuitry QQ202 can be configured to communicate with an access network or other network using a communication interface QQ212. The communication interface QQ212 may include one or more communication subsystems and may include an antenna QQ222 or be communicatively coupled to the antenna QQ222. The communication interface QQ212 may include one or more transceivers for communication (e.g., via one or more remote transceivers capable of wireless communication with another device (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 suitable for providing network communication (e.g., optical, electrical, frequency assignment, etc.). Furthermore, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software, or firmware, or alternatively, be implemented separately.

[0158] In the illustrated embodiment, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (e.g., using a Global Positioning System (GPS) to determine location), another type of communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards (e.g., IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.).

[0159] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface QQ212 through a wireless connection with a network node. Data captured by the UE's sensors can be transmitted via another UE through the same wireless connection. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0160] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0161] When the UE is in the form of an Internet of Things (IoT) device, the UE can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door and window sensors, flood / humidity sensors, electronic door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device (such as heart rate monitors or remote-controlled surgical robots). In addition to the above... Figure 14 In addition to the other components described in the UE QQ200 shown, UEs in the form of IoT devices also include circuitry and / or software depending on the intended application of the IoT device.

[0162] As another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, this UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle (e.g., a car, bus, truck, ship, and aircraft) or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0163] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be a drone or integrated into a drone, and provides the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller for operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling the actuators) to increase or decrease the drone's speed. The first UE and / or the second UE can also include more than one of the functions described above. For example, the UE can include sensors and actuators, and handle data communication between both the speed sensor and the actuators.

[0164] Figure 15 A network node QQ300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs), and NR NodeBs (gNBs)).

[0165] Base stations can be classified based on the coverage they provide (or, in other words, their transmission power levels); therefore, depending on the coverage provided, a base station can be called a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor for control relays. Network nodes can also include one or more (or all) portions of a distributed radio base station, such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as remote radio headends (RRHs). These remote radio units can be integrated with antennas to form an antenna-integrated radio, or they can be independent of antenna integration. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0166] Other examples of network nodes include multi-transmitter point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices (e.g., MSR BS), network controllers (e.g., radio network controllers (RNC) or base station controllers (BSC)), base transceiver stations (BTS), transmitter points, transmitter nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved Serving Mobility Location Center (E-SMLC)) and / or minimized drive test (MDT).

[0167] Network node QQ300 includes processing circuitry QQ302, memory QQ304, communication interface QQ306, and power supply QQ308. Network node QQ300 can consist of multiple physically separate components (e.g., NodeB and RNC components, BTS and BSC components, etc.), each with its own corresponding components. In some scenarios where network node QQ300 includes multiple separate components (e.g., BTS and BSC components), one or more separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such scenarios, each unique "NodeB and RNC pair" can be considered a single network node in some cases. In some embodiments, network node QQ300 can be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components can be replicated (e.g., separate memory QQ304 exists for different RATs), and some components can be reused (e.g., the same antenna QQ310 can be shared by different RATs). The network node QQ300 may also include multiple sets of various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies). These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node QQ300.

[0168] The processing circuitry QQ302 may include one or more of the following: a microprocessor, a controller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or coding logic, operable to provide network node QQ300 functionality, either alone or in combination with other network node QQ300 components (e.g., memory QQ304).

[0169] In some embodiments, the processing circuit QQ302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on the same chip or chipset, board, or unit group.

[0170] The memory QQ304 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including computer programs, software, applications including logic, rules, codes, tables, and / or other instructions executable by the processing circuitry QQ302 and usable by the network node QQ300. The memory QQ304 may be used to store any calculations performed by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and the memory QQ304 are integrated together.

[0171] Communication interface QQ306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface QQ306 includes a port / terminal QQ316 for transmitting and receiving data to and from the network, for example, via a wired connection. Communication interface QQ306 also includes radio front-end circuitry QQ318, which may be coupled to antenna QQ310, or in some embodiments, to a portion of antenna QQ310. Radio front-end circuitry QQ318 includes a filter QQ320 and an amplifier QQ322. Radio front-end circuitry QQ318 may be connected to antenna QQ310 and processing circuitry QQ302. Radio front-end circuitry QQ318 can be configured to modulate the signal transmitted between antenna QQ310 and processing circuitry QQ302. Radio front-end circuitry QQ318 can receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry QQ318 can use a combination of filter QQ320 and / or amplifier QQ322 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna QQ310. Similarly, when data is received, the antenna QQ310 can collect radio signals, which are then converted into digital data by the radio front-end circuit QQ318. The digital data can then be passed to the processing circuit QQ302. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0172] In some alternative embodiments, network node QQ300 does not include a separate radio front-end circuit QQ318; instead, processing circuitry QQ302 includes radio front-end circuitry and is connected to antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of communication interface QQ306. In yet another embodiment, communication interface QQ306 includes one or more ports or terminals QQ316, radio front-end circuitry QQ318, and RF transceiver circuitry QQ312 as part of a radio unit (not shown), and communication interface QQ306 communicates with baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0173] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ310 may be coupled to radio front-end circuitry QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ310 is decoupled from network node QQ300 and may be connected to network node QQ300 via an interface or port.

[0174] Antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any receive operation and / or certain acquire operation described herein by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any transmit operation described herein by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0175] Power supply QQ308 provides power to the various components of network node QQ300 in a manner suitable for each component (e.g., at the voltage and current levels required by each respective component). Power supply QQ308 may also include or be coupled to power management circuitry to supply power to the components of network node QQ300 for performing the functions described herein. For example, network node QQ300 may be connected to an external power source (e.g., mains, power outlet) via input circuitry or an interface (e.g., cable), thereby supplying power to the power circuitry of power supply QQ308. As another example, power supply QQ308 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0176] Implementations of the network node QQ300 may include more than Figure 15 The components shown are additional components used to provide certain aspects of the functionality of the network node (including any functionality described herein and / or any functionality required to support the topics described herein). For example, the network node QQ300 may include a user interface device to allow information to be input into and output from the network node QQ300. This allows users to perform diagnostic, maintenance, repair, and other management functions on the network node QQ300.

[0177] Figure 16 This is a block diagram of the QQ400 host based on the various aspects described in this article. The QQ400 host can be... Figure 13 The embodiment of host QQ116. As used herein, host QQ400 can be or include various combinations of hardware and / or software (including processing resources in a standalone server, blade server, cloud-implemented server, distributed server, virtual machine, container, or server cluster). Host QQ400 can provide one or more services to one or more UEs.

[0178] The host QQ400 includes processing circuitry QQ402, which is operatively coupled via bus QQ404 to input / output interface QQ406, network interface QQ408, power supply QQ410, and memory QQ412. Other components may be included in other embodiments. The features of these components may be substantially similar to those with respect to the previous figures (e.g., Figure 14 and Figure 15 The characteristics described for the device make its description generally applicable to the corresponding components of the host QQ400.

[0179] The memory QQ412 may include one or more computer programs, including data QQ416 and one or more host applications QQ414. The data QQ416 may include user data, such as data generated by the UE for the host QQ400, or data generated by the host QQ400 for the UE. Embodiments of the host QQ400 may utilize only a subset or all of the illustrated components. The host application QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Universal Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for various categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application QQ414 may also provide user authentication and authorization checks and may periodically report health status, routing, and content availability to a central node (e.g., a device in the core network or a device at the edge of the core network). Therefore, the host QQ400 can select and / or indicate different hosts for the UE to use for overhead services. The host application QQ414 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0180] Figure 17 This is a block diagram illustrating a virtualization environment QQ500 that can virtualize functionality implemented by some embodiments. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualization hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein, and involves at least a portion of its functionality being implemented as an implementation of one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments QQ500 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized.

[0181] The application QQ502 (which may alternatively be referred to as a software instance, virtual application, network function, virtual node, virtual network function, etc.) is run in the virtualization environment Q500 to implement some of the features, functions and / or benefits of some of the embodiments disclosed herein.

[0182] The hardware QQ504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein (e.g., network interfaces, input / output interfaces, etc.). The software can be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may generally be referred to as VM QQ508), and / or perform any functions, features, and / or benefits described in relation to some embodiments described herein. The virtualization layer QQ506 can present a virtual operating platform to the VM QQ508, which appears as network hardware.

[0183] VM QQ508 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by the corresponding virtualization layer QQ506. Different embodiments of instances of virtual device QQ502 can be implemented on one or more VM QQ508, and these implementations can be made in different ways. In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0184] In the context of NFV, a VM QQ508 can be a software implementation of a physical machine, and its program runs as if it were running on a physical, non-virtualized machine. Each VM QQ508, along with the portion of the hardware QQ504 that executes for that VM (whether it is hardware dedicated to that VM and / or hardware shared by that VM with other VMs), forms a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling the specific network functions running on one or more VM QQ508s above the hardware QQ504 and corresponding to the application of QQ502.

[0185] The hardware QQ504 can be implemented in a standalone network node with general or specific components. Some functions of the hardware QQ504 can be implemented via virtualization. Alternatively, the hardware QQ504 can be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed by a management and orchestration QQ510, which in particular oversees the lifecycle management of the application QQ502. In some embodiments, the hardware QQ504 is coupled to one or more radio units, each radio unit including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be used in conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., radio access nodes or base stations). In some embodiments, some signaling can be provided by using a control system QQ512, which can alternatively be used for communication between the hardware nodes and the radio units.

[0186] Figure 18 A communication diagram is shown illustrating communication between host QQ602 and UE QQ606 via a partial wireless connection through network node QQ604, according to some embodiments. Reference will now be made to... Figure 18 To describe the UE discussed in the preceding paragraphs (e.g., Figure 13 UE QQ112a and / or Figure 14 UE QQ200), network nodes (e.g., Figure 13 Network node QQ110a and / or Figure 15 Network node QQ300) and host (e.g., Figure 13 The host QQ116 and / or Figure 16 Example implementations of the host QQ400 according to various embodiments.

[0187] Similar to host QQ400, embodiments of host QQ602 include hardware such as a communication interface, processing circuitry, and memory. Host QQ602 also includes software stored in or accessible by host QQ602 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UEQQ606 connected via an over-the-top (OTT) connection QQ650 extending between UE QQ606 and host QQ602. When providing services to remote users, the host application can provide user data sent using the OTT connection QQ650.

[0188] Network node QQ604 includes hardware that enables it to communicate with host QQ602 and UE QQ606. Connection to QQ604 can be a direct connection or via a core network (such as...). Figure 13 The connection is to the core network (QQ106) and / or one or more other intermediate networks (e.g., one or more public, private, or hosted networks). For example, an intermediate network could be a backbone network or the Internet.

[0189] UE QQ606 includes hardware and software stored within or accessible by UE QQ606 and executable by the UE's processing circuitry. The software includes client applications (e.g., web browsers or operator-specific "applications") operable to provide services to human or non-human users via UE QQ606, supported by host QQ602. In host QQ602, the executing host application can communicate with the executing client application via OTT connection QQ650, which terminates between UE QQ606 and host QQ602. When providing services to a user, the UE's client application can receive request data from the host application of the host and, in response to the request data, provide user data. OTT connection QQ650 can transmit both request data and user data. The UE's client application can interact with the user to generate user data provided to the host application via OTT connection QQ650.

[0190] The OTT connection QQ650 can be extended via connection QQ660 between host QQ602 and network node QQ604, and via wireless connection QQ670 between network node QQ604 and UE QQ606, to provide connectivity between host QQ602 and UE QQ606. Connection QQ660 and wireless connection QQ670, which provide OTT connection QQ650, have been abstractly drawn to illustrate communication between host QQ602 and UE QQ606 via network node QQ604, without explicitly involving any intermediate devices or the precise routing of messages via these devices.

[0191] As an example of sending data via an OTT connection QQ650, in step QQ608, host QQ602 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE QQ606. In other embodiments, the user data is associated with UE QQ606, which shares data with host QQ602 without explicit human interaction. In step QQ610, host QQ602 initiates a transmission to UE QQ606 carrying user data. Host QQ602 may initiate the transmission in response to a request sent by UE QQ606. This request may be caused by human interaction with UE QQ606 or by the operation of a client application executed on UE QQ606. Based on the teachings of the embodiments described throughout this disclosure, this transmission may be delivered via network node QQ604. Therefore, in step QQ612, based on the teachings of the embodiments described throughout this disclosure, network node QQ604 sends the user data carried in the transmission initiated by host QQ602 to UE QQ606. In step QQ614, UE QQ606 receives the user data carried in the transmission, which can be performed by a client application running on UE QQ606, which is associated with a host application running by host QQ602.

[0192] In some examples, UE QQ606 executes a client application that provides user data to host QQ602. User data can be provided as a response to data received from host QQ602. Therefore, in step QQ616, UE QQ606 can provide user data, which can be done by executing the client application. When providing user data, the client application may also consider user input received from the user via the input / output interface of UE QQ606. Regardless of the specific manner in which user data is provided, in step QQ618, UE QQ606 initiates the transmission of user data to host QQ602 via network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ604 receives user data from UE QQ606 and initiates the transmission of the received user data to host QQ602. In step QQ622, host QQ602 receives the user data carried in the transmission initiated by UE QQ606.

[0193] One or more embodiments in various examples improve the performance of the OTT service provided to the UE QQ606 using an OTT connection QQ650, in which a wireless connection QQ670 forms the final part. More precisely, the teachings of these embodiments can improve data rates, latency, and power consumption, thereby providing benefits such as reduced user wait times, relaxed file size limits, improved content resolution, better responsiveness, and extended battery life.

[0194] In the example scenario, host QQ602 can collect and analyze plant status information. As another example, host QQ602 can process audio and video data that may have been retrieved from the UE for creating mappings. As another example, host QQ602 can collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host QQ602 can store surveillance video uploaded by the UE. As another example, host QQ602 can store or control access to media content such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, host QQ602 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, presentation services (e.g., compiling charts based on data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0195] In some examples, a measurement process may be provided for the purpose of monitoring improved data rates, latency, and other factors of one or more embodiments. Optional network functions may also be present for reconfiguring the OTT connection QQ650 between host QQ602 and UE QQ606 in response to changes in measurement results. The measurement process and / or the network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection QQ650; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ650 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change in the operation of network node QQ604. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates host QQ602's measurement of throughput, propagation time, latency, etc. Measurement can be achieved by having the software use an OTT connection to QQ650 to send messages (especially empty or "virtual" messages) while monitoring propagation time, errors, etc.

[0196] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information in ways such as: converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making determinations based on the results of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0197] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuitry, for example, in a hard-wired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these particular embodiments, the processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the individual processing circuitry or other components of the computing device, but are enjoyed holistically by the computing device and / or generally by the end user and wireless network.

[0198] The present disclosure has been described above with reference to embodiments thereof. However, these embodiments are for illustrative purposes only and are not intended to limit the present disclosure. The scope of the present disclosure is defined by the appended claims and their equivalents. Various changes and modifications can be made by those skilled in the art without departing from the scope of the present disclosure, wherein such variations and modifications fall within the scope of the present disclosure.

[0199] Explanation of Abbreviations

[0200] 3GPP Third Generation Partnership Project

[0201] 5G fifth-generation wireless network

[0202] LTE Long Term Evolution

[0203] RI remote jamming

[0204] RIM Remote Interference Management

[0205] UE (User Equipment)

Claims

1. A method (800) for Remote Interference Management (RIM) at a first network node (120), the method (800) comprising: Detect (S440b, S810) whether there is remote interference (RI) from the one or more second network nodes (110) during at least a first time period during which one or more ongoing processes for RIM mitigation at the first network node (120) and one or more second network nodes (110) are suspended.

2. The method (800) according to claim 1, further comprising: Based at least on the detection of the presence of RI from the one or more second network nodes (110), determine (S445b) whether to continue or stop the one or more ongoing processes for RIM mitigation.

3. The method (800) according to claim 2, further comprising at least one of the following operations: In response to the detection of an RI from one or more second network nodes (110) during the at least one first time period, the ongoing process for RIM mitigation of one or more is continued and / or triggered; and In response to the absence of RI from the one or more second network nodes (110) during the at least one first time period, the one or more ongoing processes for RIM mitigation are stopped and / or triggered to be stopped.

4. The method (800) according to claim 2 or 3, wherein, The determination of whether to continue or stop the one or more ongoing processes for RIM mitigation is also based at least on whether an RI from the one or more second network nodes (110) is detected during a second time period of performing at least one of the ongoing processes for RIM mitigation.

5. The method (800) according to claim 4, further comprising at least one of the following operations: In response to the detection of an RI from the one or more second network nodes (110) during the at least one first time period and in response to the detection of an RI from the one or more second network nodes (110) during the second time period, the one or more ongoing processes for RIM mitigation are continued and / or triggered to continue; In response to the detection of an RI from the one or more second network nodes (110) during the at least one first time period and in response to the non-detection of an RI from the one or more second network nodes (110) during the second time period, the one or more ongoing processes for RIM mitigation are continued and / or triggered to continue; as well as In response to the absence of an RI from the one or more second network nodes (110) during the at least one first time period and in response to the absence of an RI from the one or more second network nodes (110) during the second time period, the one or more ongoing processes for RIM mitigation are stopped and / or triggered to be stopped.

6. The method (800) according to any one of claims 2 to 5, wherein, When the at least one first time period includes more than one first time period within the RIM detection period, detecting whether there is an RI from the one or more second network nodes (110) during the at least one first time period includes: Detect the RI level during all first time periods within the RIM detection period; At the end of the RIM detection period, the filtered RI value is calculated based at least on the detected RI levels; and Based at least on the filtered RI values, detect whether there is an RI from the one or more second network nodes (110).

7. The method (800) according to claim 6, wherein, Detecting the presence of an RI from one or more second network nodes (110) based at least on the filtered RI value includes at least one of the following operations: In response to determining that the filtered RI value is higher than a first threshold, an RI from the one or more second network nodes (110) is detected; as well as In response to determining that the filtered RI value is below a second threshold, it is detected that there is no RI from the one or more second network nodes (110).

8. The method (800) according to claim 6 or 7, wherein, The filtered RI value is at least one of the following: - The average of the detected RI levels; and - The maximum value of the detected RI level.

9. The method (800) according to any one of claims 2 to 5, wherein, When the at least one first time period includes only a single first time period within the RIM detection period, detecting whether there is an RI from the one or more second network nodes (110) during the at least one first time period includes: Detecting the RI level during the single first time period; and At least based on the RI level, detect whether there is an RI from the one or more second network nodes (110).

10. The method (800) according to claim 9, wherein, Detecting the presence of an RI from one or more second network nodes (110) based at least on the RI level includes at least one of the following operations: In response to determining that the RI level is higher than a first threshold, an RI from the one or more second network nodes (110) is detected; as well as In response to determining that the RI level is below a second threshold, an absence of RI from the one or more second network nodes (110) is detected.

11. The method (800) according to claim 7 or 10, wherein, The first threshold is higher than or equal to the second threshold.

12. The method (800) according to any one of claims 1 to 11, wherein, The at least one first time period is at least one frame.

13. The method (800) according to any one of claims 1 to 12, wherein, At least one of the first network node (120) and the one or more second network nodes (110) is a base station.

14. The method (900) according to any one of claims 1 to 13, wherein, The first network node (120) is configured to perform the method (900) according to any one of claims 15 to 25.

15. A method (900) for Remote Interference Management (RIM) at a second network node (110), the method (900) comprising: During at least one first time period, one or more ongoing processes for RIM mitigation at the second network node (110) are paused (S430a, S910) so that the first network node (120) is able to detect whether there is remote interference (RI) from the second network node (110) during the at least one first time period.

16. The method (900) according to claim 15, further comprising: Determine whether the first network node (120) detected an RI from the second network node (110) during the at least one first time period; as well as Based at least on the determination of whether the first network node (120) detects an RI from the second network node (110), it is determined whether to continue or stop the one or more ongoing processes for RIM mitigation.

17. The method (900) of claim 16, further comprising at least one of the following operations: In response to determining that the first network node (120) detected an RI from the second network node (110) during the at least one first time period, the one or more ongoing processes for RIM mitigation continue; and In response to determining that the first network node (120) did not detect an RI from the second network node (110) during the at least one first time period, the one or more ongoing processes for RIM mitigation are stopped.

18. The method (900) according to claim 16 or 17, further comprising: Determine whether the first network node (120) detects an RI from the second network node (110) during a second time period while performing at least one ongoing process in one or more ongoing processes for RIM mitigation. The determination of whether to continue or stop the one or more ongoing processes for RIM mitigation is also based at least on: determining whether the first network node (120) detected an RI from the second network node (110) during the second time period.

19. The method (900) according to claim 18, further comprising at least one of the following operations: In response to determining that the first network node (120) detected an RI from the second network node (110) during the at least one first time period and in response to determining that the first network node (120) detected an RI from the second network node (110) during the second time period, the one or more ongoing processes for RIM mitigation continue; In response to determining that the first network node (120) detected an RI from the second network node (110) during the at least one first time period and in response to determining that the first network node (120) did not detect an RI from the second network node (110) during the second time period, the one or more ongoing processes for RIM mitigation continue; as well as In response to determining that the first network node (120) did not detect an RI from the second network node (110) during the at least one first time period and in response to determining that the first network node (120) did not detect an RI from the second network node (110) during the second time period, the one or more ongoing processes for RIM mitigation are stopped.

20. The method (900) according to any one of claims 15 to 19, further comprising: When there is no downlink service to be transmitted during the at least one first time period, a pseudo downlink service is generated. as well as The pseudo downlink service is transmitted during at least one first time period.

21. The method (900) according to claim 20, wherein, The pseudo downlink service is generated by padding.

22. The method (900) according to claim 20 or 21, wherein, The pseudo downlink service is scrambled using the Radio Network Temporary Identifier (RNTI), which cannot be descrambled by any terminal device.

23. The method (900) according to any one of claims 15 to 22, wherein, The at least one first time period is at least one frame.

24. The method (900) according to any one of claims 15 to 23, wherein, At least one of the first network node (120) and the second network node (110) is a base station.

25. The method according to any one of claims 15 to 24, wherein, The first network node (120) is configured to perform the method (800) according to any one of claims 1 to 14.

26. A first network node (120, 1000, 1100), comprising: Processor (1006); Memory (1008) stores instructions that, when executed by the processor (1006), cause the first network nodes (120, 1000, 1100) to: Detect whether there is remote interference (RI) from the one or more second network nodes (110) during at least a first time period during which one or more ongoing processes for remote interference management (RIM) mitigation are suspended at the first network node (120) and one or more second network nodes (110).

27. The first network node (120, 1000, 1100) according to claim 26, wherein, When the instruction is executed by the processor (1006), it also causes the first network node (120, 1000, 1100) to perform the method (800) according to any one of claims 2 to 14.

28. A second network node (110, 1000, 1200), comprising: Processor (1006); Memory (1008) stores instructions that, when executed by the processor (1006), cause the second network nodes (110, 1000, 1200) to: One or more ongoing processes for remote interference management (RIM) mitigation are suspended during at least one first time period, enabling the first network node (120) to detect the presence of remote interference (RI) from the second network node (110) during the at least one first time period.

29. The second network node (110, 1000, 1200) according to claim 28, wherein, When the instruction is executed by the processor (1006), it also causes the second network node (110, 1000, 1200) to perform the method (900) according to any one of claims 16 to 25.

30. A computer program (1010) comprising instructions which, when executed by at least one processor (1006), cause the at least one processor (1006) to perform the method (800, 900) according to any one of claims 1 to 25.

31. A carrier (1008) comprising the computer program (1010) according to claim 30, wherein, The carrier (1008) is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium.

32. A telecommunications system (10), comprising: One or more first network nodes (120, 130), each first network node including: processor; The memory stores instructions that, when executed by the processor, cause the corresponding first network node (120, 130) to: Detect whether remote interference (RI) from the one or more second network nodes (110, 130) exists during at least a first time period when one or more ongoing processes for remote interference management (RIM) mitigation are suspended at the first network node (120, 130) and one or more second network nodes (110, 130). The one or more second network nodes (110, 130), each second network node includes: processor; The memory stores instructions that, when executed by the processor, cause the corresponding second network nodes (110, 130) to: During the at least one first time period, the one or more ongoing processes for RIM mitigation at the corresponding second network nodes (110, 130) are paused, enabling the one or more first network nodes (120, 130) to detect whether there is an RI from the one or more second network nodes (110, 130) during the at least one first time period.

33. The telecommunications system (10) according to claim 32, wherein, When the instructions stored in the memory of the corresponding first network node (120, 130) are executed by the processor of the corresponding first network node (120, 130), the corresponding first network node (120, 130) also causes the corresponding first network node (120, 130) to perform the method (800) according to any one of claims 2 to 14.

34. The telecommunications system (10) according to claim 32 or 33, wherein, When the instructions stored in the memory of the corresponding second network node (110, 130) are executed by the processor of the corresponding second network node (110, 130), the corresponding second network node (110, 130) also causes the corresponding second network node (110, 130) to perform the method (900) according to any one of claims 16 to 25.

Images