Preemptive measurement reporting with respect to Doppler shifts for active action
By detecting Doppler frequency shift and timing advance differences in the 5G NR system by user equipment, and sending alarm reports to service nodes, the interference management problems caused by UE in NTN are solved, and the interference prevention and mitigation is achieved, and the system is improved. spectrum usage efficiency.
Patent Information
- Application Number
- CN202280095384.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-25
- Publication Date
- 2024-12-10
AI Technical Summary
In non-terrestrial networks (NTNs), especially in new 5G radio (NR) systems, interference management problems caused by differences in Doppler frequency shift and timing advances, the prior art is difficult to effectively prevent and alleviate the interference management problems caused by mobile user equipment (UEs) induced interference, especially in the case of dynamic frequency and time slot offsets between LEO satellites and HAPS.
User equipment (UE) detects Doppler shift and timing advance differences, and sends alarm reports to service nodes (gNBs) to take interference mitigation measures such as power control and band resource allocation to avoid interference to other network nodes.
Effectively prevent and reduce UE interference to other NTN or TN nodes, improve the system's spectrum usage efficiency and overall throughput, and reduce the impact of dynamic factors in the interference management process.
Smart Images

Figure CN119111085A_ABST
Abstract
Description
Technical Field
[0001] Some example embodiments may generally relate to communications including mobile or wireless telecommunication systems, such as Long Term Evolution (LTE), or fifth generation (5G) radio access technology, or new radio (NR) access technology, or 5G and beyond (e.g., 6G) access technology, or other communication systems. For example, some example embodiments may generally relate to NR over non-terrestrial networks (NTNs). Background Art
[0002] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro and / or fifth generation (5G) radio access technology or new radio (NR) access technology, 5G and / or sixth generation (6G) radio access technology. 5G wireless systems refer to next generation (NG) radio systems and network architectures. 5G systems may be primarily built on 5G New Radio (NR), but 5G (or NG) networks may also be built on E-UTRA radio. It is estimated that NR provides bit rates of 10 to 20 Gbit / s or higher, and may support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more prevalent, there will be a growing demand for networks that meet the needs of lower power, low data rates, and long battery life. Next Generation Radio Access Network (NG-RAN) represents a RAN for 5G that can provide both NR and LTE (and LTE-Advanced) radio access. It should be noted that in 5G, a node that can provide radio access functionality to a user equipment (i.e., a Node B, NB in UTRAN or an evolved NB, eNB in LTE) can be named a Next Generation NB (gNB) when built on an NR radio, and can be named a Next Generation eNB (NG-eNB) when built on an E-UTRA radio. 5G or later or 6G is expected to support further use cases beyond current mobile usage scenarios, such as virtual and augmented reality, artificial intelligence, instant messaging, improved support for IoT, etc. Summary of the invention
[0003] Embodiments may be directed to an apparatus comprising at least one processor and at least one memory, the memory comprising computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: detect a possibility of interference with at least one network node; and based on the detection of the possibility of interference, send an alarm report to a serving node of the apparatus to indicate the possibility of interference with at least one network node.
[0004] Embodiments may be directed to an apparatus comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: receive an alert report from a user equipment indicating a possibility of generating interference to at least one network node; and initiate interference mitigation to prevent or reduce interference to at least one network node.
[0005] An embodiment may be directed to a method, the method comprising detecting, by a user equipment, a possibility of causing interference to at least one network node. The method may also include, based on the detection of the possibility of causing interference, sending an alarm report to a serving node of the user equipment to indicate the possibility of causing interference to at least one network node.
[0006] Embodiments may be directed to a method, the method comprising receiving, by a network node serving a user equipment, an alert report from a user equipment, wherein the alert report indicates a likelihood of causing interference to at least one network node. The method may also include initiating interference mitigation to prevent or reduce interference to at least one network node.
[0007] An embodiment may relate to an apparatus comprising: a component for detecting a possibility of causing interference to at least one network node; and a component for sending an alarm report to a service node of the apparatus based on the detection of the possibility of causing interference to indicate the possibility of causing interference to at least one network node.
[0008] Embodiments may be directed to an apparatus comprising means for receiving an alert report from a user equipment indicating a likelihood of causing interference to at least one network node; and means for initiating interference mitigation to prevent or reduce interference to the at least one network node.
[0009] An embodiment may relate to a computer-readable medium including program instructions stored thereon for performing at least the following operations: detecting a possibility of interference with at least one network node; and based on the detection of the possibility of interference, sending an alarm report to a service node to indicate the possibility of interference with at least one network node.
[0010] Embodiments may be directed to a computer-readable medium including program instructions stored thereon for performing at least the following operations: receiving an alert report from a user equipment indicating a likelihood of generating interference to at least one network node; and initiating interference mitigation to prevent or reduce interference to at least one network node. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:
[0012] Figure 1 According to an embodiment, an example of a system for depicting interference scenarios is shown;
[0013] Figure 2 An example flow chart of a method is shown according to an embodiment;
[0014] Figure 3 An example flow chart showing a method according to an embodiment; and
[0015] Figure 4 An example of a system including a plurality of devices is shown according to certain embodiments. DETAILED DESCRIPTION
[0016] It is readily understood that, as generally described and illustrated in the figures herein, the components of certain exemplary embodiments may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some exemplary embodiments of systems, methods, devices, and computer program products for preemptive measurement reporting is not intended to limit the scope of certain embodiments, but rather represents selected exemplary embodiments.
[0010] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the use of the phrases "certain embodiments," "some embodiments," or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment. Therefore, the appearance of the phrases "certain embodiments," "in some embodiments," "in other embodiments," or other similar language throughout this specification does not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. In addition, the terms "cell," "node," "gNB," "satellite," or other similar language may be used interchangeably throughout this specification.
[0017] In addition, if necessary, the different functions or processes discussed below can be performed in different orders and / or concurrently with each other. In addition, if necessary, one or more functions or processes in the described functions or processes can be optional or can be combined. Therefore, the following description should be considered as an explanation of the principles and teachings of some example embodiments, rather than a limitation thereof.
[0018] Certain example embodiments may relate to the field of NR over non-terrestrial networks (NTNs). 3GPP technology was originally designed for terrestrial applications with fixed base stations. Most procedures (including timing and frequency compensation) were developed for such scenarios.
[0019] The 3GPP system is based on synchronization between the UE and the gNB (NR base station) in both the time and frequency domains. In the downlink (DL), synchronization is achieved in timing when the UE reads the synchronization signals (primary synchronization signal (PSS) and secondary synchronization signal (SSS)) broadcast by the NR cell. Since the physical delay experienced by the signal is due to the propagation between the two nodes, the DL timing reference is different in the gNB (transmission time) and the UE (reception time). The system is designed to operate with such an offset, which is relatively small in the terrestrial network (TN). In the frequency domain, the UE searches for potential NR cells by looking at synchronization blocks (which carry synchronization signals) in predetermined frequencies, the so-called synchronization grid. In standalone operation, the frequency position of the synchronization signal (SS) block is defined by a number called the global synchronization channel number (GSCN). The UE searches for a frequency within the valid GSCN. By detecting the PSS / SSS, the UE can then detect and compensate for any frequency misalignment due to its hardware, such as the carrier frequency offset (CFO) of the local oscillator.
[0020] In the uplink (UL), at the initial transmission (random access), the UE is not assumed to be synchronized with the network. Upon reception of the random access special sequence (preamble), the gNB will inform the UE of the timing advance (TA) offset that the UE should apply for the next UL transmission in order to align with the UL timing at the gNB. This is necessary because the UE should have a similar UL timing reference at the receive timing through the gNB in order to avoid interference between UEs assigned in different time slots. In the frequency domain, the gNB signals the UE the GSCN to use for UL transmissions.
[0021] Because the UE is considered a mobile node in the 3GPP network, there may be a Doppler shift in the frequency domain caused by the UE's speed relative to the gNB. The UE is expected to capture the current Doppler shift compared to the reference value of the GSCN via DL measurements and use this shift to estimate the Doppler shift to be used in the UL in ppm (parts per million). For UL transmissions, the UE then adjusts its carrier frequency based on DL frequency synchronization to account for the hardware frequency error as well as the Doppler frequency shift experienced on the serving link.
[0022] Although some applications also consider high-speed UEs connected to 3GPP networks, such as UEs on trains or airplanes (300 to 1000 km / h); and some features are developed for enhanced coverage (e.g., tens of kilometers), NTN has provided more challenging scenarios for UE synchronization.
[0023] In 3GPP NTN, satellites used to transmit NR signals can travel at an orbit of 300 km (low earth orbit) to an orbit of more than 35,000 km (GEO and HEO, although HEO is not currently considered for NR on NTN). The following Table 1 (corresponding to Table 4.1-1 in 3GPP TR 38.821) presents reference values for these scenarios: Table 1: Types of NTN platforms
[0024] The speeds observed in NTN scenarios are much higher than those considered in NR for terrestrial applications. For example, a low earth orbit (LEO) satellite can travel at a relative speed of 7.5 km / s (about 27,000 km / h).
[0025] The high relative speeds observed in the NTN for LEO and medium earth orbit (MEO) deployments result in Doppler shifts that are significantly higher in the NTN. For example, for LEO satellites, the Doppler shift is expected to be on the order of more than 20 parts per million (ppm). This corresponds to a shift of 15 kHz already at 750 MHz (the lowest subcarrier spacing (SCS) allowed in NR). For frequencies above 9 GHz (e.g., frequency range 2 (FR2) frequencies), this will correspond to a Doppler shift equivalent to one or more physical resource blocks (PRBs).
[0026] Initially it was agreed that UL frequency pre-compensation was to be performed by the UE based on the UE position (obtained via the Global Navigation Satellite System (GNSS)) and satellite ephemeris. This meant that the UE was expected to perform Doppler pre-compensation of several kilohertz to ensure that UL signals from different UEs were received at the satellite antenna with zero Doppler shift (essentially eliminating the Doppler effect experienced in the UL direction of the serving link).
[0027] A similar situation is observed for timing advance pre-compensation by the UE. Current protocols specify that the timing advance on the UE side is expected to have a UE-specific component to be calculated by the UE based on satellite ephemeris and its own position (acquired via GNSS). The “autonomously acquired” component is a new feature in NTN compared to the traditional TN requirements and is introduced due to the large delays observed in NTN and the wide range between minimum and maximum delays experienced by users in the same cell, making it difficult for the gNB to decode the random access preamble transmission and subsequently estimate the full TA to be compensated by the UE.
[0028] Among the scenarios that can be addressed by the example embodiments described herein is a situation where more than one layer (high altitude platform station (HAPS), LEO, geosynchronous orbit (GEO), MEO) can be used for UEs in a dynamic and flexible manner so that the advantages of each of the deployments can be fully utilized by the network. In addition, the service links used by these layers can share the same frequency band or potentially use adjacent frequency bands. In addition, the example embodiments can avoid interference in scenarios where one layer is available to the UE and other layers are used by other UEs.
[0029] Figure 1 An example of an interference scenario is shown. Figure 1 In the example of FIG. 1 , two UEs (UE1 and UE2) are connected to an NR operator via a LEO satellite deployment 105. At some point, one of the UEs (UE1) notices the approach of a HAPS 110 from the same operator or from another operator. The HAPS 110 may have been deployed to cover a different area (e.g., a different country), or the UE may not be able to connect to the HAPS 110. In other words, the UE is not expected to perform a handover from the LEO satellite 105 to the HAPS 110. Because the NTN cell created by the LEO is expected to be much larger than the coverage area of the HAPS, there will often be a situation where UE2 cannot detect the same HAPS as UE1.
[0030] Typically, there may be interference management or interference mitigation techniques deployed between different cells in a network or multiple networks, including between HAPS and LEO of the same operator, for example, by allocating different 5G NR bandwidth parts (BWP) in HAPS and LEO to carry the majority of their respective traffic loads.
[0031] However, for the duration of the service provided by the LEO satellite to UE1, the Doppler shift on the service link between LEO and UE1 can vary from -20ppm to +20ppm relative to the carrier frequency, which corresponds to a multiple of the subcarrier spacing (SCS). This means that even if different network layers ( Figure 1 In the example of HAPS and LEO) are using different BWPs, the UE's UL transmissions can also potentially generate interference on different PRBs at NTN nodes other than the intended node (HAPS gNB). Therefore, even BWP separation may not be enough to fully protect the cell from interference for the entire duration of the flight. Introducing frequency guard bands is seen as suboptimal as it will result in unused resources and reduce the overall system throughput. Furthermore, due to the time-varying nature of the Doppler shift, there are dynamic factors such as the portion of the spectrum affected by the interference generated by UE1 is different over time. Most interference management techniques and algorithms do not consider interferers that "slide" in the frequency domain from large negative numbers to large positive numbers, and typically they assume that the interferers are aligned in frequency with the signal of interest.
[0032] Furthermore, on top of the Doppler variations, there are also timing difference variations. As an example, if the UL signal from UE1 is pre-compensated to provide time slot N at a specific time, when the satellite is located, for example, 800 km at the example location, the timing advance must correspond to a transmission at 5.33 milliseconds before time slot N. The same transmission by the UE will arrive at the HAPS at a distance of 40 km only 0.13 milliseconds after its transmission. Since the distance between the LEO and the UE also varies significantly, there will also be a dynamic misalignment in time for the interference caused by the UE in the HAPS PRB. The large time misalignment between the signals does not allow for the deployment of beam-based interference mitigation.
[0033] In the DL, a similar effect can be observed, but from the perspective of a UE on the ground. Since some pre-compensation may be applied by the LEO satellite and the HAPS system, the observed difference may be based on the "residual" difference in Doppler observed by the UE at its own location relative to the compensated versions by the LEO and HAPS.
[0034] This question is relevant because the possibility of sharing similar RAN resources (e.g., frequency bands) for TN and NTN has been considered. The same situation has been considered for different NTN layers, where LEO and MEO can share the same frequency band. Figure 1The example involves the HAPS <-> LEO case, but similar problems apply to several different scenarios such as: LEO <-> MEO, LEO <-> GEO, and LEO <-> LEO (two satellites in different orbits observe different Doppler shifts and timing advances from the same UE).
[0035] In TN, the differences in timing and Doppler shift are not relevant compared to the duration of the time slot in time and frequency, as this would affect the interference management process. However, similar issues can be observed if NTN and TN share frequency resources.
[0036] Certain embodiments provide a new procedure that may include measurements and signaling for the UE to provide so-called "alert reports" to the serving gNB / NR-RAN, which allows preventive measures at the gNB / NR-RAN for interference management procedures so that the UE avoids causing interference to other NTN objects or to the TN.
[0037] In an embodiment, the UE's decision to send an "Alert Report" may be triggered by detecting other NTN / TN using the same carrier frequency or an adjacent frequency band as configured for the UE by its serving gNB, plus the UE's Doppler shift and timing advance pre-compensation to be used in the UL, and whether these values are above certain limits and will cause interference to another system. This may be due to signal leakage due to a large frequency pre-compensation in the frequency band to the other system, for example.
[0038] In this way, the gNB can be aware of the situation and the associated risks and be able to direct its interference mitigation strategy for the UL. For example, interference mitigation may include UE power control, band usage, and / or resource allocation schemes to indicate that the UE will not interfere with other NTN objects / nodes in the UL that are different from the intended objects / nodes.
[0039] In accordance with some embodiments, additional timestamp assistance information may be provided by the UE to the serving gNB as part of the alert report. The assistance information may include, for example, timing advance and Doppler pre-compensation for the serving cell and multiple neighboring cells (which may or may not be at the same orbital altitude).
[0040] In certain embodiments, the reporting may be triggered by autonomous detection on the UE side or may be configured by the gNB as part of the measurement configuration and signaling framework.
[0041] In one embodiment, the UE may utilize autonomous detection of interference in the DL or possible cases of UL interference to provide early or preemptive reporting. The detection of such cases may be based on downlink measurements (e.g., Doppler and timing), based on information already provided by the gBN (TA commands, ephemeris information), and / or based on GNSS location information, etc.
[0042] According to this embodiment, a UE connected to a cell in one NTN platform (a satellite in a given orbit, referred to herein as a serving satellite) can identify the presence of other cells transmitted by different NTN platforms (different satellites or HAPS) or TN gNBs. This corresponds to a situation where other cells are active on the same frequency carrier as the serving cell, or in any frequency carrier configured in the UE, and / or on the same / adjacent frequency band / BWP / resource block as the UE. Optionally, in an embodiment, the detection may also be based on the ephemeris of a neighboring satellite (or neighboring HAPS) broadcast by the serving satellite. In an embodiment, the UE can use the neighboring satellite information to determine when the neighboring satellite is within the interference range (in both the Doppler domain and the time domain). Therefore, in the case where the ephemeris of the neighboring satellite is not provided by the serving satellite, the UE can receive and decode the system information block (SIB) or any other control information from the neighboring satellite, where the ephemeris is provided.
[0043] As an additional embodiment, the UE may consider its antenna or beamforming implementation and the ability to determine interference range in conjunction with the serving cell ephemeris.
[0044] When interference is detected or for the risk of causing interference, the UE can use its knowledge of the serving satellite ephemeris and / or its own time and frequency pre-compensation values to calculate the moment when the Doppler shift change exceeds the relevant threshold in the positive or negative direction. The relevant threshold can be used to indicate significant adjacent channel interference, which is generally not affected by common interference mitigation techniques available in cellular networks. Wherein adjacent channels can represent subcarriers or PRBs in the frequency domain that can be allocated to other users (or other logical channels). The threshold can be calculated based on a series of parameters and reported in different ways, such as the SCS used in the frequency band, the maximum Doppler shift in kilohertz, and / or the number of affected PRBs (in complete PRBs or partial PRBs). In an embodiment, the above process can also be used to provide (in the same or different report messages) a "co-channel" interference estimation time.
[0045] Note that in the case of two satellites, the UE can use the ephemeris of the neighboring satellite to calculate the relative offset of frequency and timing observed / caused by the UE relative to the two satellites. In this case, the relative offset and interference due to this value can be evaluated against the above thresholds.
[0046] According to an embodiment, the UE may be configured to send measurement report(s) to the gNB. This may be done using conventional signaling schemes, such as the UE requesting allocation of resources for submitting reports or predefined gNB resources.
[0047] In an embodiment, the UE may then send an alert report to the serving gNB indicating an event that may or may cause interference to another NTN or TN node. In addition, the report may include information of the node and its cell ID (PCI or other ID), and / or may optionally include (relative) timing advance and frequency Doppler measurements of the serving cell, beam index to be used, etc. The measurement may be provided with a timestamp (UTC time, system frame number (SFN), subframe number or slot number in a frame) that points to the moment when the UL transmission will potentially affect the neighboring node, as indicated by the reported parameters.
[0048] If the timestamp is provided based on the system timing (SFN, timeslot number, etc.), it can be understood by the serving gNB. In order for the gNB to be able to confirm the interference risk reported by the UE and furthermore take specific actions, the serving gNB needs to understand the timing of the other node. In cases where the gNB does not know this in advance, the UE can provide the serving gNB with relevant information as part of the alert report measurements, e.g. including the (relative) time offset and / or SFN offset between the other node (e.g. HAPS gNB) and the serving gNB.
[0049] An example of a Frequency Doppler report might be as follows: EarlyDopplerOffsetIndication: Unit: 2SCS. Current value: 2 Conversion: +1 in SFNX +1+Δ1 in SFNX +1+Δ1+Δ2 in SFNX -1+Δ1+Δ2+Δ3 in SFNX
[0050] In the above example, the UE is sending a Doppler shift indication where each unit corresponds to 2 SCS. The current value (i.e. the Doppler shift measured at the moment the trigger is initiated) is equal to 2 units (4 SCS). Then, at each transition time marked in the report by a given SFN, the UE expects the Doppler shift to increase / decrease by 1 unit (2 SCS for the above example) according to the indicated value.
[0051] In another embodiment, the gNB may set the measurement configuration for the UE, specifying the thresholds to be reported, the timestamp units, and the measurement objects. Optionally, the gNB may include the ephemeris of the neighboring satellites or HAPS to be reported. In this case, the UE may defer reporting if the UL transmission is expected to end before the interference window or if the UE is expected to be in discontinuous reception (DRX) sleep mode.
[0052] In yet another embodiment, the UE may identify additional interference in specific subcarriers sliding in the frequency domain over time (typically in the edges of the allocated PRBs), and this may become a trigger for the UE to search for the platform causing the interference and trigger a report.
[0053] Optionally, in an embodiment, the UE may use knowledge about its own directional antenna beam / panel to estimate at which points in time the UE will transmit with high directivity in the direction affecting the victim cell, and provide reports specifically for the time window in which this occurs. It should be noted that "high directivity" may result from the use of any kind of directional antenna, meaning that the UE will not interfere or receive interference from all directions, but only in selected directions with a specific antenna width. The reason for this implementation may be that if the beam directivity can protect the UE / victim cell from interference, then the relative Doppler shift and TA may not be relevant for interference management. Additionally, on this type of reporting, the UE may provide predicted antenna coupling gain from the UE side (or path loss) to cells belonging to neighboring platforms.
[0054] In some embodiments, to save some bits, the report may include two separate fields for positive and negative deltas (reducing the need to indicate +1 and -1 before the timestamp). Depending on the embodiment, the units reported may be implicit and preconfigured by the gNB (via RRC) or hard-coded in the specification.
[0055] According to certain embodiments, the trigger for reporting may also be a random access procedure, where the UE has identified the presence of more than one satellite or gNB platform in the area before initiating random access. In an embodiment, similar reporting may also be provided for relative timing advance indication (Relative Timing Advance Report), using the observed related units for relative timing difference (symbol duration, slot duration, subframe duration).
[0056] In some embodiments, the report may contain target objects that the UE has measured (HAPS indication, satellite ephemeris of the second satellite, etc.) In some cases, the report may contain a list of reports for different targets.
[0057] According to an embodiment, if the UE knows that a handover (HO) to another platform is bound to occur or the connection will be terminated soon, the UE may postpone the transmission of the report or provide early termination for the converted timestamp list.
[0058] Due to unpaired spectrum, the frequency Doppler shift observed in DL and UL in absolute terms may be different. This difference may be taken into account by the UE when calculating the UL reported value in the form of a scaling factor to be applied to the Doppler value obtained from the DL measurements.
[0059] Figure 2 An example flow chart of a method for preemptive measurement and / or alarm reporting according to an example embodiment is shown, for example, to avoid interference with other NTN or TN nodes. In some example embodiments, Figure 2 The flowchart may be executed by a network entity or a communication device in a communication system, such as but not limited to LTE, 5G NR or a system after 5G.
[0060] For example, in some example embodiments, executing Figure 2 The communication device of the method may include user equipment, UE, side link (SL) UE, wireless device, mobile station, IoT device, UE type roadside unit (RSU), wireless transmission / reception unit, customer premises equipment (CPE), other mobile or fixed devices, etc. For example, in some example embodiments, Figure 2 The method may include processes or operations that may be performed by UE1, as described or shown elsewhere in this document, such as in Figure 1 In an embodiment, Figure 2 One or more of the processes illustrated in the example of may be performed by the apparatus 20 discussed below.
[0061] like Figure 2 As shown in the example of , the method may include: at 205, the UE detects the possibility or risk of generating interference to one or more network nodes (such as NTN or TN nodes). For example, the one or more network nodes may include satellites, HAPS, gNBs, NR-RAN nodes, or other platforms or network nodes.
[0062] In one embodiment, detecting 205 may include autonomously detecting by the UE for the possibility of causing interference to (multiple) network nodes (i.e., (multiple) victim network nodes) based on one or more of the following: DL measurements, information provided by a serving node (e.g., gNB) serving the UE, ephemeris information and / or GNSS position information of the serving node. According to some embodiments, detecting 205 may include detecting that the (multiple) network nodes are using the same carrier frequency and / or adjacent frequency bands as configured by the serving node for the UE.
[0063] According to certain embodiments, detection 205 may include determining whether the value of the UE's Doppler shift and the value of the timing advance precompensation to be used in the UL is above a specific limit or threshold that will cause interference to the (multiple) network nodes, for example, due to signal leakage due to a large frequency precompensation in the frequency band of the (multiple) network nodes. For example, the UE can use its knowledge of the ephemeris of the serving node and / or its own time and frequency precompensation values to calculate the moment when the Doppler shift change exceeds those specific limits or thresholds in the positive or negative direction, where the adjacent channel represents the subcarriers or PRBs in the frequency domain that can be allocated to other users. In some embodiments, the limits or thresholds can be calculated based on a series of parameters and reported in different ways, such as the SCS used in the frequency band, the maximum Doppler shift in kilohertz, and / or the number of PRBs affected (in full PRBs or partial PRBs). In another embodiment, the UE may also be configured to provide (in the same or different reporting message) a "co-channel" interference estimation time. In the case where the network node includes two satellites, the UE can use the ephemeris of the neighboring satellites to calculate the relative offset of the frequency and timing observed / caused by the UE relative to the two satellites. In this case, the relative offset and interference due to this value can be evaluated against the above-mentioned limits or thresholds.
[0064] In some embodiments, the network node(s) may include a neighboring satellite or HAPS, and detecting 205 may include using neighboring satellite or HAPS information including at least ephemeris information to determine when the neighboring satellite or HAPS is within the interference range in the Doppler domain and / or the time domain. According to an embodiment, the interference range may be detected based on the antenna or beamforming capabilities of the UE in combination with the ephemeris information.
[0065] According to an embodiment, the method may include sending one or more measurement reports to a serving node (e.g., a gNB), at 210. This may be accomplished, for example, using conventional signaling solutions, such as a UE requesting allocation of resources for submitting reports or predefined gNB resources.
[0066] In an embodiment, based on the UE detecting the possibility of causing interference to (multiple) network nodes, the method may then include: sending an alarm report to the service node to indicate the possibility of causing interference to (multiple) network nodes at 215. In other words, the UE detecting the possibility or risk of causing interference to (multiple) network nodes may trigger the UE to send an alarm report to the service node so that it is aware of the possible interference and can take action to prevent or mitigate the interference.
[0067] According to some embodiments, the alarm report may include timestamp assistance information including one or more of: information of the network node(s) and its(multiple) cell identifiers, timing advance and frequency Doppler measurements for the serving node and the network node(s), and / or a beam index to be used. For example, in an embodiment, the assistance information may include a relative time offset or a system frame number (SFN) offset between the network node(s) and the serving node.
[0068] In some embodiments, to save some bits, the alert report may include two separate fields for positive and negative deltas (reducing the need to indicate +1 and -1 before the timestamp). According to certain embodiments, the trigger for the transmission 215 of the alert report may also be a random access procedure, where the UE has identified the presence of more than one satellite or gNB platform in the area before initiating random access. In an embodiment, similar reporting may also be provided for relative timing advance indication (Relative Timing Advance Report), using the observed related units for relative timing differences (symbol duration, slot duration, subframe duration).
[0069] According to some embodiments, the alert report may contain the target objects that the UE has measured (HAPS indication, satellite ephemeris of the second satellite, etc.) Additionally, in some cases, the alert report may contain a list of reports for different targets.
[0070] According to an embodiment, if the UE knows that a HO to another satellite or gNB platform will occur or the current connection will be terminated soon, the UE may postpone the sending of the warning report 215 or provide an early termination for the converted timestamp list.
[0071] According to another embodiment, detecting 205 may include the UE receiving configuration information from the serving node, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, or a measurement object, and optionally receiving ephemeris information of a neighboring satellite or HAPS. In this case, the UE may postpone sending the alert report if the UL transmission is expected to end before the window for interference, or when the UE is expected to be in a discontinuous reception mode.
[0072] In some embodiments, detecting 205 may include identifying additional interference in a particular subcarrier sliding in the frequency domain over time, wherein the identification of the additional interference triggers the UE to search for the platform causing the additional interference.
[0073] In accordance with certain embodiments, detection 205 may include using knowledge of the UE's own directional antenna beam or panel to estimate at which points in time the UE will transmit with high directionality in a direction affecting (multiple) network nodes, and the alert report may include information for the time windows in which the transmissions in the direction affecting (multiple) network nodes occur.
[0074] In some embodiments, the method may further include: in response to the alert report, the UE receiving instructions from the serving node to mitigate or prevent interference to (multiple) network nodes. For example, the instructions may include modifications to the UE's power control, frequency band usage, and / or resource allocation.
[0075] Figure 3 An example flow chart of a method for preemptive measurement and / or alarm reporting according to an example embodiment is shown, for example, to avoid interference to other NTN or TN nodes. In some example embodiments, Figure 3 The flowchart may be executed by a network entity or a communication device in a communication system, such as but not limited to LTE, 5G NR or a system after 5G.
[0076] For example, in some example embodiments, executing Figure 3 The device of the method may include a network node, a satellite, a base station, a node B, an evolved node B (eNB), a 5G node B or access point, a next generation node B (NG-NB or gNB), a TRP, a HAPS, a remote radio head (RRH), an integrated access and backhaul (IAB) node and / or a WLAN access point, other radio nodes, etc. For example, in one embodiment, Figure 3 The method may be performed by a serving node or a gNB serving the UE, such as the device 10 discussed below.
[0077] like Figure 3 As shown in the example of , the method may include: receiving one or more measurement reports from the UE at 305. In an embodiment, the method may then include: receiving an alert report from the UE at 310 to indicate the possibility or risk of generating interference to one or more network nodes (such as satellites, HAPS and / or gNBs).
[0078] According to some embodiments, the alarm report may include timestamp assistance information, which includes one or more of the following: information of (multiple) network nodes (i.e., victim nodes) and their (multiple) cell identifiers, timing advance and frequency Doppler measurements for the serving node and (multiple) network nodes, and / or beam indexes to be used. For example, in an embodiment, the assistance information may include a relative time offset or a system frame number (SFN) offset between the (multiple) network nodes and the serving node. In an embodiment, the alarm report may specifically include information about the time window for the UE to transmit in the direction affecting the (multiple) network nodes.
[0079] According to some embodiments, the method may include sending configuration information to the UE, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit or a measurement object, and optionally sending ephemeris information of the network node(s) to the UE.
[0080] In some embodiments, in response to receiving an alert report indicating a likelihood or risk of causing interference, the method may include, at 315, initiating interference mitigation to prevent or reduce interference to the network node(s). For example, interference mitigation may include one or more of: modifying UE power control, frequency band usage, and / or resource allocation.
[0081] Figure 4 Examples of apparatus 10 and apparatus 20 are shown according to certain example embodiments. In an embodiment, apparatus 10 may be a node, host or server in a communication network or serving such a network.
[0082] For example, the apparatus 10 may be a network node associated with a radio access network (such as an LTE network, 5G or NR), a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), a TRP, a HAPS, a remote radio head (RRH), an integrated access and backhaul (IAB) node, and / or a WLAN access point. In some example embodiments, the apparatus 10 may be, for example, a gNB or other similar radio node.
[0083] It should be understood that in some example embodiments, the device 10 may include an edge cloud server as a distributed computing system, wherein the server and the radio nodes may be independent devices that communicate with each other via a radio path or via a wired connection, or they may be located in substantially the same entity that communicates via a wired connection.
[0084] For example, in certain example embodiments, the apparatus 10 represents a gNB, which may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functionality, such as transmission of user data, mobility control, radio access network sharing, positioning, and / or session management. The CU may control the operation of (multiple) DUs via a fronthaul interface. The DU may be a logical node that includes a subset of the gNB functionality, depending on the functional split option. It should be noted that one of ordinary skill in the art will appreciate that the apparatus 10 may include Figure 4 Components or features not shown.
[0085] like Figure 4 As shown in the example of , the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general-purpose or special-purpose processor. In fact, as an example, the processor 12 may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture, or any other processing component. Although in Figure 4 A single processor 12 is shown in FIG. 1 , but multiple processors may be utilized according to other embodiments. For example, it should be understood that in some embodiments, the device 10 may include two or more processors forming a multiprocessor system that supports multiprocessing (e.g., in which case, the processor 12 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0086] Processor 12 may perform functions associated with the operation of device 10, which may include, for example, pre-decoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10, including processes associated with management of communications or communication resources.
[0087] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and may be of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static storage (such as a magnetic disk or optical disk), a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium, or other suitable storage components. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enables the device 10 to perform tasks as described herein.
[0088] In an example embodiment, the device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 12 and / or the device 10.
[0089] In some example embodiments, the apparatus 10 may also include or be coupled to one or more antennas 15 for sending signals and / or data to and receiving signals and / or data from the apparatus 10. The apparatus 10 may also include or be coupled to a transceiver 18 configured to send and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to (a plurality of) antennas 15, or may include any other suitable transceiver components. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: narrowband Internet of Things (NB-IoT), LTE, 5G, wireless local area network (WLAN), Bluetooth (BT), Bluetooth Low Energy (BT-LE), near field communication (NFC), radio frequency identifier (RFID), ultra-wideband (UWB), MulteFire, etc. The radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via uplinks).
[0090] As such, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15, and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other embodiments, the transceiver 18 may be capable of directly sending and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 10 may include input and / or output devices (I / O devices) or input / output components.
[0091] In an example embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for device 10. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software.
[0092] According to some example embodiments, the processor 12 and / or the memory 14 may be included in a processing circuit / component or a control circuit / component or may form part of a processing circuit system / component or a control circuit / component. In addition, in some embodiments, the transceiver 18 may be included in a transceiver circuit / component or may form part of a transceiver circuit / component.
[0093] As used herein, the term "circuit" may refer to a hardware circuit implementation only (e.g., analog and / or digital circuits), a combination of hardware circuits and software, a combination of analog and / or digital hardware circuits with software / firmware, any portion of a (multiple) hardware processor with software (including a digital signal processor) that work together to enable a device (e.g., device 10) to perform various functions, and / or a (multiple) hardware circuit and / or (multiple) processor or portion thereof that uses software for operation, but the software may not be present when not required for operation. As another example, as used herein, the term "circuit" may also cover an implementation of a hardware circuit or processor only (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term circuit may also cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.
[0094] As described above, in some example embodiments, the apparatus 10 may be or be part of a network element or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, RRH, HAPS, IAB node, relay node, WLAN access point, satellite, etc. According to some embodiments, the apparatus 10 may be controlled by a processor 12 and / or a memory 14, wherein the memory 14 stores instructions for performing functions associated with any of the embodiments described herein. For example, in some embodiments, the apparatus 10 may be configured to perform one or more processes depicted in any flowchart or signaling diagram described herein, such as Figure 3 or any other method described herein.
[0095] In some embodiments, as discussed herein, the apparatus 10 may be configured, for example, to perform processes related to preemptive measurements and / or alert reporting to avoid interference to other NTN or TN nodes. For example, in some embodiments, the apparatus 10 may be controlled by the processor 12 to receive an alert report from a UE to indicate a risk of interference to other NTN or TN nodes and initiate a process for mitigating or preventing interference, as described elsewhere herein.
[0096] Figure 4 An example of an apparatus 20 according to another embodiment is also shown. In an embodiment, the apparatus 20 may be a node or element in a communication network or associated with such a network, such as a user equipment, UE, communication node, mobile equipment (ME), mobile station, mobile device, fixed device, IoT device, CPE or other device.
[0097] As described herein, a UE may alternatively be referred to as, for example, a mobile station, a mobile equipment, a mobile unit, a mobile device, a user device, a subscriber station, a wireless terminal, a tablet computer, a smart phone, an IoT device, a sensor or NB-IoT device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, a medical device and its applications (e.g., remote surgery), an industrial device and its applications (e.g., a robot and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. As an example, the apparatus 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.
[0098] In some example embodiments, the apparatus 20 may include one or more processors and / or one or more computer-readable storage media (e.g., memory, storage device, etc.) and / or one or more radio access components (e.g., modem, transceiver, etc.) and / or a user interface. In some embodiments, the apparatus 20 may be configured to operate using one or more radio access technologies, such as LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that one of ordinary skill in the art will appreciate that the apparatus 20 may include Figure 4 Components or features not shown.
[0099] like Figure 4 As shown in the example of , the device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In fact, as an example, the processor 22 may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Figure 4 A single processor 22 is shown in FIG. 1 , but multiple processors may be utilized according to other embodiments. For example, it should be understood that in some embodiments, the device 20 may include two or more processors, which may form a multi-processor system that supports multi-processing (e.g., in this case, the processor 22 may represent a multi-processor). In some embodiments, the multi-processor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0100] Processor 22 may perform functions associated with the operation of device 20, including, as some examples, pre-decoding of antenna gain / phase parameters, encoding and decoding of individual bits that form communication messages, formatting of information, and overall control of device 20, including processes associated with management of communication resources.
[0101] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and may be of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage (such as a magnetic disk or optical disk), a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enables the device 20 to perform tasks as described herein.
[0102] In an embodiment, the device 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 22 and / or the device 20.
[0103] In some example embodiments, the apparatus 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals and for transmitting from the apparatus 20 via an uplink. The apparatus 20 may also include a transceiver 28 configured to send and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as orthogonal frequency division multiple access (OFDMA) or orthogonal frequency division multiplexing (OFDM) symbols.
[0104] For example, transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by antenna(s) 25 , and to demodulate information received via antenna(s) 25 for further processing by other elements of device 20 .
[0105] In other embodiments, the transceiver 28 is capable of directly sending and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 20 may include input and / or output devices (I / O devices). In some embodiments, the apparatus 20 may also include a user interface, such as a graphical user interface or a touch screen.
[0106] In an embodiment, the memory 24 stores software modules that provide functionality when executed by the processor 22. The modules may include, for example, an operating system that provides operating system functionality for the device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for the device 20. The components of the device 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, the device 20 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology (such as NR).
[0107] According to some embodiments, the processor 22 and the memory 24 may be included in a processing circuit or a control circuit or may form a part of a processing circuit or a control circuit. In addition, in some embodiments, the transceiver 28 may be included in a transceiver circuit or a part of a processing or control circuit or may form a part thereof.
[0108] As described above, according to some embodiments, the apparatus 20 may be, for example, a user equipment, a UE, a SL UE, a relay UE, a mobile device, a mobile station, a ME, an IoT device and / or a NB-IoT device, a CPE, etc. According to some embodiments, the apparatus 20 may be controlled by a processor 22 and / or a memory 24, and the processor 22 and / or the memory 24 may store instructions for executing functions associated with any of the embodiments described herein, such as in Figure 2 shown in or about Figure 2 One or more of the operations described herein, or any other method described herein. For example, in an embodiment, the device 20 may be controlled to perform processes related to preemptive measurement and / or alarm reporting, as described elsewhere herein. For example, in some embodiments, the device 20 may be controlled by the processor 22 to detect the possibility or existence of interference and trigger an alarm report, for example, to avoid causing interference to other NTN or TN nodes, as described elsewhere herein.
[0109] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing one or more methods, processes, and / or procedures, or any variants discussed herein. Examples of components may include one or more processors, memories, controllers, transmitters, receivers, sensors, circuits, and / or computer program codes for causing the execution of any of the operations discussed herein.
[0110] In view of the foregoing, certain example embodiments provide several technical improvements, enhancements and / or advantages over prior art procedures and constitute an improvement in at least the technical field of wireless network control and / or management.
[0111] For example, as discussed in detail above, certain example embodiments may provide systems and / or methods for proactive interference reporting, which may include measurements and signaling for a UE to provide so-called "alert reports" to a serving node (e.g., gNB / NR-RAN), thereby allowing preventive measures for interference management procedures at the gNB / NR-RAN so that the UE avoids causing interference to other NTN nodes or TNs.
[0112] In an embodiment, the UE is configured to notify the service node if the UE anticipates that future uplink transmissions may cause harmful interference to neighboring cells (e.g., other NTN or TN cells). For example, the UE may be configured to estimate whether the uplink transmission will cause interference in the same frequency band or an adjacent frequency band of the serving cell due to Doppler shift, and warn its service node of such interference risk. Therefore, certain embodiments may reduce or avoid the risk of causing interference to other NTN or TN nodes. Therefore, the use of certain example embodiments results in improved functionality of communication networks and their nodes (such as base stations, eNBs, gNBs and / or IoT devices, UEs or mobile stations, etc.).
[0113] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm, or flow chart described herein may be implemented by software and / or computer program code or portion of code stored in a memory or other computer-readable or tangible medium and executed by a processor.
[0114] In some example embodiments, the device may include or be associated with: at least one software application, module, unit or entity configured as (multiple) arithmetic operations, or configured as a program or part of a program (including added or updated software routines), which can be executed by at least one operating processor or controller. Programs, also known as program products or computer programs, include software routines, applets and macros, can be stored in any device-readable data storage medium, and may include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. One or more computer executable components may be at least one software code or part of a code. Modifications and configurations required to implement the functionality of the example embodiments may be performed as (multiple) routines, which may be implemented as (multiple) software routines added or updated. In one example, (multiple) software routines may be downloaded into the device.
[0115] As an example, software or computer program code or part of the code may be in source code form, object code form or some intermediate form, and may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. For example, such a carrier may include a recording medium, a computer memory, a read-only memory, an optoelectronic and / or electrical carrier signal, a telecommunications signal and / or a software distribution package. Depending on the processing power required, the computer program may be executed in a single electronic digital computer, or may be distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.
[0116] In other example embodiments, the functions of the example embodiments may be performed by hardware or circuitry included in a device, such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, some of the functions of the example embodiments may be implemented as signals carried by electromagnetic signals that may be downloaded from the Internet or other network.
[0117] According to example embodiments, an apparatus such as a node, a device or a corresponding component may be configured as a circuit, a computer or a microprocessor (such as a single-chip computer element), or as a chipset, which may include at least a memory for providing storage capacity for (multiple) arithmetic operations and / or an operation processor for performing (multiple) arithmetic operations.
[0118] Some embodiments described herein may use the conjunction "and / or". It should be noted that when used, the term "and / or" is intended to include any or both of the alternatives, depending on the example embodiment or implementation. In other words, "and / or" may refer to one, or the other, or both, or any one, or more, or all of the things or options that use the conjunction in combination.
[0119] The example embodiments described herein may apply to both singular and plural implementations, regardless of whether the singular or plural is used in conjunction with describing certain embodiments. For example, an embodiment describing the operation of a single network node may also apply to example embodiments including multiple instances of the network node, and vice versa.
[0120] Those of ordinary skill in the art will readily appreciate that the example embodiments described above may be practiced with processes in a different order and / or with hardware elements in a configuration different from that disclosed. Therefore, although some embodiments have been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent while remaining within the spirit and scope of the example embodiments.
Claims
1. A device comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: detecting a possibility of causing interference to at least one network node; Based on the detection of the possibility for generating the interference, an alert report is sent to a serving node of the apparatus to indicate the possibility for generating the interference to the at least one network node.
2. The apparatus of claim 1 , wherein the likelihood for causing the interference to the at least one network node is autonomously detected based on at least one of: downlink measurements, information provided by the serving node, ephemeris information for the serving node, or global navigation satellite system (GNSS) location information.
3. The apparatus according to claim 1 or 2, wherein in order to detect the possibility for generating the interference, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: The at least one network node is detected to be using at least one of a same carrier frequency and an adjacent frequency band as configured by the serving node for the apparatus.
4. The apparatus according to any one of claims 1 to 3, wherein in order to detect the possibility for generating the interference, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: It is determined whether a value of Doppler frequency shift and a value of timing advance precompensation of the device to be used in uplink is above a certain limit that would cause the interference to the at least one network node.
5. The apparatus of claim 4, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: A time point at which the Doppler frequency shift variation exceeds the specific limit in a positive direction or a negative direction is calculated, wherein the adjacent channel represents a subcarrier or a physical resource block that can be allocated to other users in the frequency domain.
6. The device according to any one of claims 1 to 5, wherein the at least one network node comprises a proximate satellite or a high altitude platform station (HAPS), and Wherein, in order to detect the possibility of generating the interference, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: use neighboring satellite or high altitude platform station (HAPS) information including ephemeris information to determine when the neighboring satellite or high altitude platform station (HAPS) is within an interference range in at least one of a Doppler domain or a time domain.
7. The apparatus of claim 6, wherein to detect the likelihood for generating the interference, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: The interference range is determined based on an antenna or beamforming capability of the device in combination with the ephemeris information.
8. The apparatus according to any one of claims 1 to 7, wherein in order to detect the possibility for generating the interference, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: receiving configuration information from the serving node, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, or a measurement object, and optionally receiving the ephemeris information of the neighboring satellite or high altitude platform station (HAPS); and The sending of the alert report is deferred when uplink transmission is expected to end before a window for the interference or when the apparatus is expected to be in a discontinuous reception mode.
9. The apparatus according to any one of claims 1 to 7, wherein in order to detect the possibility for generating the interference, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: Additional interference in a particular subcarrier sliding in the frequency domain over time is identified, wherein the identification of the additional interference triggers the apparatus to search for a platform causing the additional interference.
10. The apparatus according to any one of claims 1 to 9, wherein in order to detect the possibility for generating the interference, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: Using knowledge of the device's own directional antenna beam or panel, it is estimated at which points in time the device will transmit with high directionality in a direction affecting at least one network node, and wherein the alarm report includes information for the time window in which the transmission in the direction affecting at least one network node occurs.
11. The apparatus according to any one of claims 1 to 10, wherein the alarm report includes time stamp assistance information, the time stamp assistance information including at least one of the following: Information of the at least one network node and its cell identifier; Timing advance and frequency Doppler measurements for the serving node and the at least one network node; or The beam index to be used.
12. The apparatus of claim 11, wherein the assistance information comprises a relative time offset or a system frame number (SFN) offset between the at least one network node and the serving node.
13. The apparatus according to any one of claims 1 to 12, wherein the apparatus comprises a user equipment, and wherein the at least one network node comprises at least one of the following: a satellite, a high altitude platform station (HAPS), or a next generation Node B (gNB).
14. An apparatus comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving an alert report from a user equipment to indicate a likelihood of causing interference to at least one network node; as well as Interference mitigation is initiated to prevent or reduce the interference to the at least one network node.
15. The apparatus of claim 14, wherein the interference mitigation comprises modifying at least one of user equipment power control, frequency band usage, or resource allocation.
16. The apparatus of claim 14 or 15, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: Configuration information is sent to the user equipment, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, or a measurement object, and ephemeris information of the at least one network node is optionally sent to the user equipment.
17. The apparatus according to any one of claims 14 to 16, wherein the alert report comprises information on a time window in which transmissions by the user equipment in the direction affecting the at least one network node occur.
18. The apparatus according to any one of claims 14 to 17, wherein the alarm report includes time stamp assistance information, the time stamp assistance information including at least one of the following: Information of the at least one network node and its cell identifier; Timing advance and frequency Doppler measurements for said at least one network node and said apparatus; or The beam index to be used.
19. The apparatus of claim 18, wherein the assistance information comprises a relative time offset or a system frame number (SFN) offset between the at least one network node and the serving node.
20. The apparatus of any one of claims 14 to 19, wherein the apparatus comprises a network node serving the user equipment, and wherein the at least one network node comprises at least one of: a satellite, a high altitude platform station (HAPS), or a gNB.
21. A method comprising: detecting, by a user equipment, a possibility of causing interference to at least one network node; Based on the detection of the possibility for generating the interference, an alert report is sent to a serving node of the user equipment to indicate the possibility for generating the interference to the at least one network node.
22. The method of claim 21, wherein the detecting comprises: The potential for causing the interference to the at least one network node is autonomously detected based on at least one of: downlink measurements, information provided by the serving node, ephemeris information for the serving node, or Global Navigation Satellite System (GNSS) location information.
23. The method according to claim 21 or 22, wherein the detecting comprises: The at least one network node is detected to be using at least one of a same carrier frequency and an adjacent frequency band as configured by the serving node for the apparatus.
24. The method according to any one of claims 21 to 23, wherein the detecting comprises: It is determined whether a value of Doppler frequency shift and a value of timing advance precompensation of the user equipment to be used in uplink are above a certain limit that would cause the interference to the at least one network node.
25. The method according to claim 24, comprising: A time point at which the Doppler frequency shift variation exceeds the specific limit in a positive direction or a negative direction is calculated, wherein the adjacent channel represents a subcarrier or a physical resource block that can be allocated to other users in the frequency domain.
26. The method according to any one of claims 21 to 25, wherein the at least one network node comprises a proximate satellite or a high altitude platform station (HAPS), and The tests include: Neighboring satellite or high altitude platform station (HAPS) information including ephemeris information is used to determine when the neighboring satellite or high altitude platform station (HAPS) is within an interference range in at least one of a Doppler domain or a time domain.
27. The method of claim 26, wherein the detecting comprises: The interference range is determined based on an antenna or beamforming capability of the user equipment in combination with the ephemeris information.
28. The method according to any one of claims 21 to 27, wherein the detecting comprises: receiving configuration information from the serving node, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, or a measurement object, and optionally receiving the ephemeris information of the neighboring satellite or high altitude platform station (HAPS); as well as The sending of the alert report is postponed when uplink transmission is expected to end before a window for the interference or when the user equipment is expected to be in a discontinuous reception mode.
29. The method according to any one of claims 21 to 27, wherein the detecting comprises: Additional interference in a specific subcarrier sliding in the frequency domain over time is identified, wherein the identification of the additional interference triggers the user equipment to search for a platform causing the additional interference.
30. The method according to any one of claims 21 to 29, wherein the detecting comprises: Knowledge of the user equipment's own directional antenna beam or panel is used to estimate the points in time at which the user equipment will transmit with high directionality in a direction affecting the at least one network node, and wherein the alarm report includes information for the time window in which the transmission in the direction affecting the at least one network node occurs.
31. The method according to any one of claims 21 to 30, wherein the alarm report includes time stamp assistance information, the time stamp assistance information including at least one of the following: Information of the at least one network node and its cell identifier; Timing advance and frequency Doppler measurements for the serving node and the at least one network node; or The beam index to be used.
32. The method of claim 31, wherein the assistance information comprises a relative time offset or a system frame number (SFN) offset between the at least one network node and the serving node.
33. The method of any one of claims 21 to 32, wherein the at least one network node comprises at least one of: a satellite, a high altitude platform station (HAPS), or a next generation Node B (gNB).
34. A method comprising: receiving, by a network node serving a user equipment, an alert report from the user equipment, wherein the alert report indicates a likelihood of causing interference to at least one network node; as well as Interference mitigation is initiated to prevent or reduce the interference to the at least one network node.
35. The method of claim 34, wherein the interference mitigation comprises modifying at least one of user equipment power control, frequency band usage, and resource allocation.
36. A method according to claim 34 or 35, comprising: Configuration information is sent to the user equipment, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, or a measurement object, and ephemeris information of the at least one network node is optionally sent to the user equipment.
37. A method according to any one of claims 34 to 36, wherein the alert report comprises information on a time window in which transmissions by the user equipment in the direction affecting the at least one network node occur.
38. The method of any one of claims 34 to 37, wherein the alarm report includes time stamp assistance information, the time stamp assistance information including at least one of the following: Information of the at least one network node and its cell identifier; Timing advance and frequency Doppler measurements for said at least one network node and said apparatus; or The beam index to be used.
39. The method of claim 38, wherein the assistance information comprises a relative time offset or a system frame number (SFN) offset between the at least one network node and the serving node.
40. The method of any one of claims 34 to 39, wherein the at least one network node comprises at least one of: a satellite, a high altitude platform station (HAPS), or a gNB.
41. An apparatus comprising: means for detecting a possibility of causing interference to at least one network node; Means for sending an alert report to a serving node of the apparatus based on the detecting of the possibility for causing the interference to indicate the possibility for causing the interference to the at least one network node.
42. An apparatus according to claim 41, wherein the means for detecting includes means for autonomously detecting the possibility of causing the interference to the at least one network node based on at least one of the following: downlink measurements, information provided by the service node, ephemeris information for the service node, or global navigation satellite system (GNSS) location information.
43. The apparatus of claim 41 or 42, wherein the means for detecting comprises: Means for detecting that the at least one network node is using at least one of a same carrier frequency and an adjacent frequency band as configured by the serving node for the apparatus.
44. The apparatus of any one of claims 41 to 43, wherein the means for detecting comprises: Means for determining whether a value of Doppler shift and a value of timing advance precompensation of said device to be used in uplink is above a certain limit that would cause said interference to said at least one network node.
45. The apparatus of claim 44, comprising: means for calculating a time instant at which the Doppler shift variation exceeds the specific limit in a positive direction or a negative direction, wherein the adjacent channel represents a subcarrier or a physical resource block that can be allocated to other users in the frequency domain.
46. The device according to any one of claims 41 to 45, wherein the at least one network node comprises a proximate satellite or a high altitude platform station (HAPS), and The components used for detection include: Means for using neighboring satellite or high altitude platform station (HAPS) information including ephemeris information to determine when the neighboring satellite or high altitude platform station (HAPS) is within an interference range in at least one of a Doppler domain or a time domain.
47. The apparatus of claim 46, wherein the means for detecting comprises: Means for determining the interference range based on an antenna or beamforming capability of the device in combination with the ephemeris information.
48. The apparatus of any one of claims 41 to 47, wherein the means for detecting comprises: means for receiving configuration information from the serving node and optionally receiving the ephemeris information of the neighboring satellite or high altitude platform station (HAPS), the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, a measurement object; as well as Means for deferring said sending of said alert report when uplink transmission is expected to end before a window for said interference or when said apparatus is expected to be in a discontinuous reception mode.
49. The apparatus of any one of claims 41 to 47, wherein the means for detecting comprises: Means for identifying additional interference in a particular subcarrier sliding in the frequency domain over time, wherein said identification of said additional interference triggers said apparatus to search for a platform causing said additional interference.
50. The apparatus of any one of claims 41 to 49, wherein the means for detecting comprises: Means for using knowledge of the device's own directional antenna beam or panel to estimate at which points in time the device will transmit with high directivity in a direction affecting at least one network node, and wherein the alarm report includes information for the time window in which the transmission in the direction affecting at least one network node occurs.
51. The apparatus of any one of claims 41 to 50, wherein the alarm report includes timestamp assistance information, the timestamp assistance information including at least one of the following: Information of the at least one network node and its cell identifier; Timing advance and frequency Doppler measurements for the serving node and the at least one network node; or The beam index to be used.
52. The apparatus of claim 51, wherein the assistance information comprises a relative time offset or a system frame number (SFN) offset between the at least one network node and the serving node.
53. An apparatus according to any one of claims 41 to 52, wherein the apparatus comprises a user equipment, and wherein the at least one network node comprises at least one of the following: a satellite, a high altitude platform station (HAPS), or a next generation Node B (gNB).
54. An apparatus comprising: means for receiving an alert report from a user equipment to indicate a likelihood of causing interference to at least one network node; as well as Means for initiating interference mitigation to prevent or reduce the interference to the at least one network node.
55. The apparatus of claim 54, wherein the interference mitigation comprises modifying at least one of user equipment power control, frequency band usage, or resource allocation.
56. The apparatus of claim 54 or 55, comprising: Means for sending configuration information to the user equipment and optionally sending ephemeris information of the at least one network node to the user equipment, the configuration information specifying at least one of the following to be reported in the alert report: a threshold, a timestamp unit, or a measurement object.
57. An apparatus according to any one of claims 54 to 56, wherein the alert report comprises information for a time window in which transmissions by the user equipment in the direction affecting the at least one network node occur.
58. The apparatus of any one of claims 54 to 57, wherein the alarm report includes time stamp assistance information, the time stamp assistance information including at least one of the following: Information of the at least one network node and its cell identifier; Timing advance and frequency Doppler measurements for said at least one network node and said apparatus; or The beam index to be used.
59. The apparatus of claim 58, wherein the assistance information comprises a relative time offset or a system frame number (SFN) offset between the at least one network node and the serving node.
60. An apparatus according to any one of claims 54 to 59, wherein the apparatus comprises a network node serving the user equipment, and wherein the at least one network node comprises at least one of the following: a satellite, a high altitude platform station (HAPS), or a gNB.
61. A computer readable medium comprising program instructions stored thereon, the instructions being used to at least perform the method according to any one of claims 21 to 40.
