Gradual frequency adjustment for double loop frequency control based on user equipment requirements in NTN
By employing a frequency pre-compensation method in the NTN system, the total FPC adjustment value is updated and calculated based on the UE's location and speed, thus resolving the frequency misalignment problem between the UE and the NTN node and improving communication quality and system performance.
Patent Information
- Application Number
- CN202380033018.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-09-30
- Filing Date
- 2023-03-10
- Publication Date
- 2024-11-15
AI Technical Summary
In non-terrestrial networks (NTN), frequency misalignment issues exist in the frequency compensation adjustment between user equipment (UE) and network nodes, leading to uplink transmission interference and degraded communication quality. Existing technologies struggle to effectively address this problem.
By implementing the Frequency Precompensation (FPC) method at the UE and NTN nodes, the total FPC adjustment value is calculated, including the current UE location and speed update, as well as the intermediate UE location and speed update, to meet the threshold requirements and achieve gradual frequency adjustment to reduce frequency error.
It effectively reduces frequency misalignment, improves the accuracy and communication quality of uplink transmission, reduces interference, and enhances the performance of the NTN system.
Smart Images

Figure CN118975159A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 363,138, filed on April 18, 2022, entitled “GRADUAL FREQUENCY ADJUSTMENT FOR DUAL-LOOP FREQUENCY CONTROL IN NTN BASED ON USER EQUIPMENT REQUIREMENTS,” and U.S. Non-Provisional Patent Application Serial No. 17 / 937,302, filed on September 30, 2022, entitled “GRADUALFREQUENCY ADJUSTMENT FOR DUAL-LOOP FREQUENCY CONTROL IN NTN BASED ON USER EQUIPMENT REQUIREMENTS,” the entire contents of which are expressly incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems having a non-terrestrial network (NTN). Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability, and other requirements (e.g., in the Internet of Things (IoT)). 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5GNR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention
[0006] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.
[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive one or more frequency precompensation (FPC) commands from a non-terrestrial network (NTN). The at least one processor may be further configured to send an uplink transmission with a frequency change in response to receiving the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on the following items: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment meets one or more threshold requirements, or (b) an intermediate UE location update between a current UE location update and a previous UE location update and an intermediate UE speed update between a current UE speed update and a previous UE speed update.
[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a non-terrestrial network (NTN) node are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to send one or more FPC commands to a UE. The memory and the at least one processor coupled to the memory may be configured to receive an uplink transmission with a frequency change in response to sending the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on the following items: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE position between a current UE location update and a previous UE location update and an intermediate UE speed between a current UE speed update and a previous UE speed update.
[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.
[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.
[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.
[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.
[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.
[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network according to various aspects of the present disclosure.
[0016] Figure 4A , Figure 4B and Figure 4C Example aspects of a network architecture supporting communications via NTN devices according to various aspects of the present disclosure are illustrated.
[0017] Figure 5Examples of NTN configurations according to various aspects of the present disclosure are illustrated.
[0018] Figure 6 Diagrams illustrating example aspects of FPC calculations in accordance with various aspects presented herein are illustrated.
[0019] Fig. 7A An idealized NTN network according to various aspects of the present disclosure is shown, wherein a UE is configured to perform a location update for each uplink transmission to a network entity via an NTN device.
[0020] Figure 7B A non-idealized NTN network 950 is shown in which a UE is configured to perform a location update for every N time slots in accordance with various aspects of the present disclosure.
[0021] Fig. 8A A static UE location network with UEs that do not move from their locations is shown in accordance with various aspects of the present disclosure.
[0022] Figure 8B FIG. 1 shows a method for estimating a service link between an NTN device and a UE according to various aspects of the present disclosure. Fig. 8A Static UE location network.
[0023] Fig. 9 A graph illustrating sudden adjustments of an FPC over time in accordance with various aspects of the present disclosure is shown.
[0024] Fig.10 A graph illustrating gradual adjustment of an FPC over time in accordance with various aspects of the present disclosure is shown.
[0025] Fig.11 Graphs illustrating different gradual adjustments of an FPC over time in accordance with various aspects of the present disclosure are shown.
[0026] Fig.12 A connection flow diagram of various aspects of the present disclosure is shown, wherein a UE is configured to send uplink transmissions to a network entity via an NTN device.
[0027] Fig.13 is a flow chart of a wireless communication method according to various aspects of the present disclosure.
[0028] Fig.14 is another flow chart of a wireless communication method according to various aspects of the present disclosure.
[0029] Fig.15 is a diagram illustrating an example of hardware implementation of an example apparatus and / or network entity according to various aspects of the present disclosure.
[0030] Fig.16 is a flow chart of a wireless communication method according to various aspects of the present disclosure.
[0031] Fig.17 is a diagram illustrating an example of a hardware implementation of an example network entity.
[0032] Fig.18 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION
[0033] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring these concepts.
[0034] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0035] For example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform the various functions described in this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.
[0036] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that may be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0037] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.
[0038] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.
[0039] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0040] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0041] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.
[0042] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals on a wired transmission medium or send signals to one or more of the other units. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals on a wireless transmission medium or send signals to one or more of the other units, or both.
[0043] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.
[0044] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.
[0045] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).
[0046] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .
[0047] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.
[0048] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0049] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).
[0050] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
[0051] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.
[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0053] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0054] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.
[0055] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and the best transmit direction of each of the base station 102 / UE 104. The transmit direction and the receive direction of the base station 102 may be the same or different. The transmit direction and the receive direction of the UE 104 may be the same or different.
[0056] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, an NTN node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).
[0057] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.
[0058] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, user stations, mobile units, user units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.
[0059] In some aspects, the base station 102 may communicate with the UE 104 via an NTN device (such as a satellite or an aircraft) having the RU 140. In some aspects, the NTN device may be a transparent satellite that performs one or more of amplification, filtering, and frequency conversion. In some aspects where the NTN device is a transparent satellite, the NTN device may receive a signal from the base station 102 and relay the signal to one or more UEs 104, such as by performing amplification and forwarding relaying. The NTN device may also receive a signal from one or more UEs 104 and relay the signal to the base station 102, such as by performing amplification and forwarding relaying. In some aspects, the NTN device may also convert the carrier frequency between the input / received signal and the output / sent signal. The communication link between the NTN device and the base station 102 may be referred to as a feeder link. In some aspects, the NTN device may be a non-transparent satellite that may be capable of performing one or more aspects performed by the base station 102. In some aspects, the NTN device may be a base station and may be connected to the core network 120.
[0060] Reference again Figure 1In some aspects, the UE 104 may have an FPC component 198 configured to send an uplink transmission with a gradual frequency adjustment in response to receiving one or more FPC commands from the NTN to minimize the effect of possible double loop correction. The FPC component 198 may be configured to receive one or more FPC commands from the NTN node. The FPC component 198 may be configured to send an uplink transmission with a frequency change in response to receiving the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on the following items: (a) a current UE location update and a current UE speed update, where the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE location between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update. In some aspects, the base station 102 may be an NTN node. The base station 102 may have an FPC command component 199 configured to send one or more FPC commands to the UE. The FPC command component 199 may be configured to receive an uplink transmission with a frequency change in response to sending the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on: (a) a current UE location update and a current UE velocity update, where the total FPC adjustment may satisfy one or more threshold requirements, or (b) an intermediate UE location between a current UE location update and a previous UE location update and an intermediate UE velocity between a current UE velocity update and a previous UE velocity update. Although the following description may focus on NTN systems, the concepts described herein may be applicable to other similar areas, such as systems where UEs and base station transceivers rapidly change their positions and velocities relative to each other. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
[0061] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2CIn the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.
[0062] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.
[0063]
[0064] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).
[0065] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0066] like Figure 2A As illustrated in FIG, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).
[0067] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol time and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.
[0068] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.
[0069] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0070] Figure 3 370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0071] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be divided into parallel streams. Subsequently, each stream may be mapped to an OFDM subcarrier, each stream may be multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and each stream may then be combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.
[0072] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.
[0073] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0074] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0075] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.
[0076] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.
[0077] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0078] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The FPC assembly 198 combines various aspects.
[0079] At least one of the Tx processor 316, the Rx processor 370, and the controller / processor 375 may be configured to perform Figure 1 The FPC assembly 199 combines various aspects.
[0080] Figure 4A A generalized illustration of each component is provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Figure 4A The example includes one UE 405, but many UEs (e.g., hundreds, thousands, millions, etc.) can utilize the network architecture 400. Similarly, the network architecture 400 may include a larger (or smaller) number of NTN devices, NTN gateways, base stations, RANs, core networks, and / or other components. The illustrated connections connecting the various components in the network architecture 400 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.
[0081] UE 405 may be configured to communicate with core network 410 via NTN equipment 402, NTN gateway 404, and base station 406. One or more RANs associated with core network 410 may include one or more base stations, as shown by RAN 412. Access to the network may be provided to UE 405 via wireless communications between UE 405 and base station 406 (e.g., a serving base station), via NTN equipment 402 and NTN gateway 404. Base station 406 may provide wireless communication access to core network 410 on behalf of UE 405, for example, using 5G NR.
[0082] The base station 406 may be referred to by other names, such as a network entity, a gNB, a base station, a network node, a "satellite node", a satellite node B (sNB), a "satellite access node", etc. The base station 406 may be different from a terrestrial network gNB, but may be based on a terrestrial network gNB with additional capabilities. For example, the base station 406 may terminate the radio interface and the associated radio interface protocol to the UE 405, and may send DL signals to the UE 405 and receive UL signals from the UE 405 via the NTN device 402 and the NTN gateway 404. The base station 406 may also support signaling connections to the UE 405 and voice and data bearers, and may support handover of the UE 405 between different radio cells of the NTN device 402, between different NTN devices, and / or between different base stations. The base station 406 may be configured to manage mobile radio beams (e.g., for airborne tools and / or non-geostationary (non-GEO) devices) and the associated mobility of the UE 405. The base station 406 can assist in the handover (or transfer) of the NTN device 402 between different NTN gateways or different base stations. In some examples, the base station 406 can be separated from the NTN gateway 404, for example, Figure 4A In other examples, the base station 406 may include one or more NTN gateways, or may be combined with one or more NTN gateways, for example, using a split architecture. For example, using a split architecture, the base station 406 may include a central unit (CU), such as Figure 1 CU110 of the example, and the NTN gateway 404 may include or act as a distributed unit (DU), such as Figure 1 Example DU 130 of. Base station 406 may be fixed on the ground with transparent payload operation. In one implementation, base station 406 may be physically combined or physically connected to NTN gateway 404 to reduce complexity and cost.
[0083] The NTN gateway 404 may be shared by more than one base station and may communicate with the UE 405 via the NTN device 402. The NTN gateway 404 may be dedicated to one associated constellation of the NTN device. The NTN gateway 404 may be included within the base station 406, for example, as a base station DU within the base station 406. The NTN gateway 404 may communicate with the NTN device 402 using a control plane protocol and a user plane protocol. The control plane protocol and the user plane protocol between the NTN gateway 404 and the NTN device 402 may: (i) establish and release the communication link from the NTN gateway 404 to the NTN device 402, including authentication and encryption; (ii) update the NTN device software and firmware; (iii) perform NTN device operation and maintenance (O&M); (iv) control radio beams (e.g., direction, power, on / off status) and mapping between radio beams and NTN gateway UL and DL payloads; and / or (v) assist in the handover of the NTN device 402 or radio cell to another NTN gateway.
[0084] For use Figure 4A The support of transparent payload of the network architecture 400 shown in the figure may affect the communication system as follows. The core network 410 may treat the satellite RAT as a new type of RAT with longer delay, reduced bandwidth and / or higher error rate. Therefore, some impact may be produced on the PDU session establishment and the mobility management (MM) and connection management (CM) processes. The NTN device 402 can be shared with other services (e.g., satellite TV, fixed Internet access) that utilize 5G NR mobile access of UEs added in a transparent manner. This enables the use of old NTN equipment and avoids the deployment of new types of NTN equipment. The base station 406 can assist the allocation and transfer of NTN equipment 402 and radio cells between the base station 406 and the NTN gateway 404, and support the handover of UE 405 between radio cells, NTN equipment and other base stations. Thus, the base station 406 may be different from the ground network gNB. Additionally, the coverage area of the base station 406 may be much larger than the coverage area of the ground network base station.
[0085] exist Figure 4A In the illustrated example, service link 420 may facilitate communication between UE 405 and NTN device 402, feeder link 422 may facilitate communication between NTN device 402 and NTN gateway 404, and interface 424 may facilitate communication between base station 406 and core network 410. Service link 420 and feeder link 422 may be implemented by the same radio interface (e.g., NR-Uu interface). Interface 424 may be implemented by an NG interface.
[0086] Figure 4B A diagram of a network architecture 425 capable of supporting NTN access, for example using 5G NR, as presented herein is shown. Figure 4B The network architecture 425 shown in FIG. Figure 4A The network architecture shown in FIG. 1 is similar or identical to the elements specified in FIG. 1 . However, the network architecture shown in FIG. 1 is similar or identical to the elements specified in FIG. Figure 4A In contrast to the transparent payload shown in Figure 4B A network architecture with a regenerative payload is illustrated. Unlike a transparent payload, a regenerative payload includes an onboard base station (e.g., includes the functional capabilities of a base station) and is referred to herein as an NTN device 402 / base station. The onboard base station may be a device corresponding to Figure 3 405. The RAN 412 is illustrated as including NTN equipment 402 / base station. Reference to NTN equipment 402 / base station may refer to functions related to communication between UE 405 and core network 410 and / or functions related to communication between NTN gateway 404 and UE 405 at the physical radio frequency level.
[0087] The onboard base station may perform many of the same functions as the base station 406 as previously described. For example, the NTN device 402 / base station may terminate the radio interface and associated radio interface protocol to the UE 405, and may send DL signals to the UE 405 and receive UL signals from the UE 405, which may include encoding and modulation of the transmitted signals and demodulation and decoding of the received signals. The NTN device 402 / base station may also support signaling connections to the UE 405 and voice and data bearers, and may support handover of the UE 405 between different radio cells of the NTN device 402 / base station and between different NTN devices / base stations. The NTN device 402 / base station may assist in the handover (or transfer) of the UE 405 between different NTN gateways and different control networks. The NTN device 402 / base station may, for example, hide or obscure certain aspects of the NTN device 402 / base station from the core network 410 by interacting with the core network 410 in the same or similar manner as a ground network base station. The NTN device 402 / base station may also assist in the sharing of the NTN device 402 / base station. The NTN device 402 / base station may communicate with one or more NTN gateways and, via the NTN gateway 404, with one or more core networks. In some aspects, the NTN device 402 / base station may communicate directly with other NTN devices / base stations using an inter-satellite link (ISL), which may support an Xn interface between any pair of NTN devices / base stations.
[0088] In the case of low earth orbit (LEO) equipment, the NTN equipment 402 / base station may manage mobile radio cells with coverage at different times. The NTN gateway 404 may be directly connected to the core network 410, as illustrated. For example, if the NTN gateway is limited, the NTN gateway 404 may be shared by multiple core networks. In some examples, the core network 410 may be configured to know the coverage area of the NTN equipment 402 / base station in order to page the UE 405 and manage the handover. Therefore, it can be seen that the core network 410 is not as good as the core network 410. Figure 4A The network architecture 425 with regenerated payload may have greater impact and complexity on both the NTN equipment 402 / base stations and the core network 410 than the network architecture 400 including transparent payload shown in FIG.
[0089] To use Figure 4B The support of the regenerative payload of the network architecture 425 shown in FIG. 4 may affect the network architecture 425 as follows. If fixed tracking areas and fixed cells are not supported, the core network 410 may be affected because the core components of the mobility management and regulatory services based on the fixed cells and fixed tracking areas of the terrestrial PLMN may be replaced by a new system (e.g., based on the location of the UE 405). If fixed tracking areas and fixed cells are supported, when paging is performed for the UE 405 located in the fixed tracking area, the core network 410 may map any fixed tracking area to one or more NTN devices / base stations with current radio coverage of the fixed tracking area. This may include configuring long-term orbit data for the NTN devices 402 / base stations in the core network 410 (e.g., obtained from the operator of the NTN devices 402 / base stations), and may add significant new impacts to the core network 410.
[0090] exist Figure 4B In the illustrated example, service link 420 may facilitate communication between UE 405 and NTN device 402 / base station, feeder link 422 may facilitate communication between NTN device 402 / base station and NTN gateway 404, and interface 424 may facilitate communication between NTN gateway 404 and core network 410. Service link 420 may be implemented by NR-Uu interface. Feeder link 422 may be implemented by NG interface on SRI. Interface 424 may be implemented by NG interface.
[0091] Figure 4C A diagram of a network architecture 450 capable of supporting NTN access, for example using 5G NR, as presented herein is shown. Figure 4C The network architecture shown in is similar to Figure 4A and Figure 4B The network architecture shown in FIG. 1 is similar or identical to the elements specified in FIG. 1 . However, the network architecture shown in FIG. 1 is similar or identical to the elements specified in FIG. Figure 4AIn contrast to the transparent payload shown in Figure 4C The network architecture with a regenerative payload is illustrated, and has a split architecture for base stations. For example, a base station may be in a central unit (CU) (such as Figure 1 CU 110) and distributed units (DU) (such as Figure 1 The DU 130 is split between Figure 4C In the illustrated example, the network architecture 450 includes an NTN-CU 416, which may be a ground-based base station or a ground base station. The regenerative payload includes an onboard base station DU and is referred to herein as an NTN-DU 414. The NTN-CU 416 and the NTN-DU 414 may collectively or individually correspond to Figure 3 A network node associated with the base station 310 in.
[0092] The NTN-DU 414 communicates with the NTN-CU 416 via the NTN gateway 404. The NTN-CU 416 performs functions together with the NTN-DU 414 and may use an internal communication protocol that is similar or identical to a gNB with a split architecture. In this example, the NTN-DU 414 may correspond to and perform functions similar or identical to a gNB distributed unit (gNB-DU), and the NTN-CU 416 may correspond to and perform functions similar or identical to a gNB central unit (gNB-DU). However, the NTN-CU 416 and the NTN-DU 414 may each include additional capabilities to support access by UE 405 using NTN equipment.
[0093] NTN-DU 414 and NTN-CU 416 may communicate with each other using F1 Application Protocol (F1AP) and may perform operations together and in conjunction with each other. Figure 4B and Figure 4C Some or all of the same functionality as described for base station 406 or NTN device 402 / base station.
[0094] The NTN-DU 414 may terminate the radio interface and associated low-level radio interface protocols to the UE 405, and may send DL signals to the UE 405 and receive UL signals from the UE 405, which may include encoding and modulation of the transmitted signals and demodulation and decoding of the received signals. The operation of the NTN-DU 414 may be controlled in part by the NTN-CU 416. The NTN-DU 414 may support one or more NR radio cells of the UE 405. The NTN-CU 416 may also be split into separate control plane (CP) (NTN-CU-CP) and user plane (UP) (NTN-CU-UP) portions. The NTN-DU 414 and the NTN-CU 416 may communicate via the F1 interface to: (a) support control plane signaling for the UE 405 using IP, Stream Control Transmission Protocol (SCTP), and F1 Application Protocol (F1AP) protocols, and (b) support user plane data transmission for the UE using IP, User Datagram Protocol (UDP), PDCP, SDAP, GTP-U, and NR User Plane Protocol (NRUPP) protocols.
[0095] The NTN-CU 416 may communicate with one or more other NTN-CUs and / or with one or more other ground base stations using ground links to support an Xn interface between any pair of NTN-CUs and / or between the NTN-CU 416 and any ground base station.
[0096] The NTN-DU 414 together with the NTN-CU 416 may: (i) support signaling connections and voice and data bearers to the UE 405; (ii) support handover of the UE 405 between different radio cells of the NTN-DU 414 and between different NTN-DUs; and (iii) assist in the handover (or transfer) of NTN equipment between different NTN gateways or different core networks. The NTN-CU 416 may hide or obscure certain aspects of the NTN equipment from the core network 410, for example, by interacting with the core network 410 in the same or similar manner as a terrestrial network base station.
[0097] exist Figure 4C In the network architecture 450 of FIG. 4, the NTN-DU 414 that communicates with and is accessible from the NTN-CU may change with LEO devices over time. With a split base station architecture, the core network 410 may be connected to a fixed NTN-CU that does not change over time, which may reduce the difficulty of paging the UE 405. For example, the core network 410 may be configured to know which NTN-DU is used to page the UE 405. With a split base station architecture, the network architecture with a regenerative payload may therefore reduce the impact of the core network 410 at the expense of an additional impact on the NTN-CU 416.
[0098] For the use of Figure 4C The support of the regenerative payload of the split base station architecture shown may affect the network architecture 450 as follows. The impact on the core network 410 may be limited as discussed above for the transparent payload (e.g., NTN device 402). For example, the core network 410 may treat the satellite RAT in the network architecture 450 as a new type of RAT with longer latency, reduced bandwidth, and / or higher error rate. As described above with reference to Figure 4B As discussed, the impact on the NTN-DU 414 may be less than the impact on the NTN device / base station (e.g., NTN device 402 / base station with a non-split architecture). The NTN-DU 414 may manage the changing associations with different (fixed) NTN-CUs. In addition, the NTN-DU 414 may manage radio beams and radio cells. The NTN-CU 416 impact may be similar to the impact of the base station 406 on the network architecture with transparent payload as discussed above, except for the additional impact on managing the changing associations with different NTN-DUs and the reduced impact on supporting radio cells and radio beams (which may be transmitted to the NTN-DU 414). In some aspects, the NTN device may correspond to a high altitude platform system (HAPS) serving one or more UEs on the ground.
[0099] One or more satellites may be integrated with the ground infrastructure of the wireless communication system. Satellites may refer to low earth orbit (LEO) devices, medium earth orbit (MEO) devices, geostationary orbit (GEO) devices, and / or highly elliptical orbit (HEO) devices. Non-terrestrial networks (NTNs) may refer to networks or network segments that use airborne or spaceborne tools for transmission. Airborne tools may refer to high altitude platforms (HAPs), including unmanned aerial systems (UASs).
[0100] NTN can be configured to help provide wireless communications in unserved or underserved areas to improve the performance of ground networks. For example, compared to TN base stations, communication satellites can provide coverage of larger geographic areas. NTN can also enhance service reliability by providing service continuity for UE or mobile platforms (e.g., passenger vehicles-aircraft, ships, high-speed trains, buses). NTN can also increase service availability, including critical communications. NTN can also achieve network scalability by providing efficient multicast / broadcast resources for data delivery to the network edge or even directly to user equipment.
[0101] Figure 5An example of NTN 500 configuration is illustrated. NTN may refer to a network or network segment using RF resources on an NTN platform. An NTN platform may refer to a satellite-based tool or an airborne tool. A satellite-based tool includes a communication satellite that can be classified according to its orbit. For example, a communication satellite may include a GEO device that appears stationary relative to the earth. Therefore, a single GEO device can provide coverage of a geographic coverage area. In other examples, a communication satellite may include a non-GEO device, such as a LEO device, a MEO device, or a HEO device. Non-GEO devices do not appear to be stationary relative to the earth. Therefore, a satellite constellation (e.g., one or more satellites) may be configured to provide coverage of a geographic coverage area. An airborne tool may refer to a system including a tethered UAS (TUA), a lighter-than-air UAS (LTA), a heavier-than-air UAS (HTA), for example, at an altitude typically between 8km and 50km, including a high altitude platform (HAP).
[0102] In some aspects, NTN 500 may include a NR-NTN. Figure 5 An example is provided in which NTN 500 may include NTN device 502, NTN device 504, third NTN device 506, NTN gateway 508, data network 510, and UE 530 within the cell coverage of NTN device 502. In some aspects, UE 530 may include an IoT device, and the UE may be connected to NTN 500 for wireless communication.
[0103] The NTN gateway 508 may be one of one or more NTN gateways that may connect the NTN 500 to a public data network. In some examples, the NTN gateway 508 may support the functionality of forwarding signals from the NTN device to a Uu interface (such as an NR-Uu interface). In other examples, the NTN gateway 508 may provide a transport network layer node and may support transport protocols, such as acting as an IP router. A satellite radio interface (SRI) may provide an IP trunk connection between the NTN gateway 508 and the NTN device to transmit an NG or F1 interface, respectively. One or more geosynchronous equatorial orbit (GEO) devices (e.g., may be referred to herein as NTN device 502, NTN device 504, or a third NTN device 506) may be fed by the NTN gateway 508, and the one or more NTN devices may be deployed within a satellite target coverage, which may correspond to a regional coverage or even a continental coverage. Non-GEO devices may be successively served by one or more NTN gateways at a time, and NTN 500 may be configured to provide service and feeder link continuity between these successively served NTN gateways with a time duration to perform mobility anchoring and handover.
[0104] The NTN device 502 (including a satellite-based tool or an airborne tool) can communicate with the data network 510 via a feeder link 512 established between the NTN device 502 and the NTN gateway 508 to provide services to the UE 530 within the cell coverage or field of view of the NTN cell 520 of the NTN device 502 via a service link 514. The feeder link 512 may include a wireless link between the NTN gateway and the NTN device. The service link 514 may refer to a radio link between the NTN device (e.g., the NTN device 502) and the UE 530. As shown in conjunction with Figure 1 As described, the NTN device 502 may use one or more directional beams (eg, beamforming) to exchange communications with the UE 530. A beam may refer to a wireless communication beam generated by an antenna on the NTN device.
[0105] In some examples, UE 530 may communicate with NTN device 502 via service link 514. NTN device 504 may relay communications for NTN device 502 via inter-satellite link (ISL) 516, and NTN device 504 may communicate with data network 510 via feeder link 512 established between NTN device 504 and NTN gateway 508. ISL links may be provided between satellite constellations and may involve the use of transparent payloads on NTN devices. ISLs may operate in RF frequencies or optical bands.
[0106] exist Figure 5 In the illustrated example, the NTN device 502 can provide a first physical cell ID (PCI) (“PCI1”) to the NTN cell 520. In some examples, a satellite constellation can provide coverage for the NTN cell 520. For example, the NTN device 502 can include a non-GEO device that does not appear to be stationary relative to the earth. Therefore, a satellite constellation (e.g., one or more satellites) can be configured to provide coverage for the NTN cell 520. For example, the NTN device 502 and the third NTN device 506 can be part of a satellite constellation that provides coverage for the NTN cell 520.
[0107] In some examples, NTN deployments can provide different services based on the type of payload on the NTN device. The type of payload can determine whether the NTN device acts as a relay node or a base station. For example, a transmission payload can implement frequency conversion and radio frequency (RF) amplifiers in both uplink (UL) and downlink (DL) directions, and can correspond to an analog RF repeater. For example, a transparent payload can receive UL signals from all served UEs and can redirect the combined signal DL to an earth station without demodulating or decoding the signals. Similarly, a transparent payload can receive UL signals from an earth station and redirect the signal DL to a served UE without demodulating or decoding the signal. However, the transparent payload can frequency convert the received signals and can amplify and / or filter the received signals before sending them.
[0108] When the UE sends a signal to the NTN node and / or when the NTN node sends a signal to the UE, the wireless communication between the UE and the NTN node may experience a frequency phase shift and / or a Doppler shift. Factors affecting the Doppler shift (for which the UE can calculate the FPC) may include changes in the position and speed of the UE, and may include changes in the position and speed of the NTN node. In some aspects, different UEs experience different frequency shifts, which may cause frequency misalignment of uplink transmissions from different UEs at the NTN node. If this misalignment is large enough, it may cause interference between uplink transmissions (e.g., OFDM-based transmissions). The UE can compensate for the frequency shift by increasing or decreasing the frequency used by the total FPC adjustment value (i.e., changing the frequency). The total FPC adjustment value can be calculated as the sum of an open-loop frequency compensation, a closed-loop frequency compensation, and an additional / optional constant. In other words, the total FPC adjustment (FPC) applied by the UE communicating with the NTN is FPC_TOTAL ) may be based on:
[0109] F FPC _ TOTAL =F FPC _ CLOSED +F FPC _ OPEN +F FPC _ OFFSET
[0110] F FPC_CLOSED May include a closed loop FPC value received from the NTN based on an accumulation of FPC data from the network (such as attributes of UL and DL transmissions with the UE). FPC_CLOSED The FPC command field in Msg2 / MsgB and the MAC control element (MAC-CE) FPC value can be updated based on the FPC command field in Msg2 / MsgB and the MAC control element (MAC-CE) FPC value. FPC_CLOSED For example, F FPC_CLOSEDcan be set to the MAC-CE FPC value. On the other hand, the FPC value in the FPC MAC CE can be added to the previous FPC value. FPC_CLOSED To update F FPC_CLOSED The UE may be configured to send FPC command field in Msg2 / MsgB to FPC_CLOSED Set to the MAC-CE FPC value or add the MAC-CE FPC value to the previous F FPC_CLOSED The network-provided FPC adjustment may be referred to as a closed-loop FPC value. The network entity may provide the FPC value to the UE via the NTN equipment. FPC_CLOSED Values such as Figure 1 The base station 102 provides the UE 104 via the RU 140, or the NTN gateway 508 provides the UE 530 via the NTN device 502.
[0111] F FPC_OPEN May include the open loop FPC value calculated by the UE. FPC_OPEN It can be a self-estimated FPC based on the UE's self-estimated position and velocity and the UE's estimated position and velocity of an NTN node (such as a transceiver of the NTN). FPC_OPEN The variables may include a UE position variable, a UE speed variable, an NTN node position variable, and an NTN node speed variable. The position may include x, y, and z axis positions, and the speed may include a vector having x, y, and z axis positions. The UE may estimate the position and speed of the NTN node using any suitable means, such as by using an ephemeris formula associated with the NTN node. The UE may calculate F based on an estimate of the service link distance and an estimate of the feeder link distance. FPC_OPEN . The UE may self-estimate its position and velocity using any suitable means, such as by performing a position and velocity (L / V) update. The L / V update may be performed, for example, by performing a GNSS positioning update to generate an updated position of the UE, and then by comparing the UE's current position with the UE's last known position to generate an updated velocity vector for the UE. The L / V update may include, for example, a GNSS positioning update that generates an updated position and velocity of the UE. The UE may estimate the velocity by comparing the UE's current position with the UE's last known position, or estimate the velocity based on an observed Doppler frequency. The UE may estimate the position and velocity of the NTN node more frequently (e.g., in real time using an ephemeris formula) than the UE self-estimates its own position and velocity (e.g., using an L / V update), and may therefore use NTN node position and velocity estimates that are more current than the UE position and velocity estimates to calculate F FPC_OPEN For example, the UE may calculate its F without first performing an L / V update. FPC_OPEN This may result in an F estimate based on the UE's last known location rather than the UE's current location.FPC_OPEN The value has a frequency change error. FPC_CLOSED The value allows network feedback and control F FPC_CLOSED However, when the UE position and velocity estimates are current, F FPC_OPEN The frequency error can now be compensated, but F FPC_CLOSED The frequency error may still be compensated, leading to a double correction problem where both the network and the UE compensate for the previously incorrect UE position and velocity.
[0112] F FPC_OFFSET Can include fixed frequency offset. FPC_OFFSET The value of may be provided by the network and may be set to zero in some cases. FPC_OFFSET May exist (i.e., F FPC_TOTAL =F FPC_CLOSED +F FPC_OPEN Without F FPC_OFFSET ), and may be determined by the frequency band of the transmission (e.g., via a lookup table associating offset values with frequency bands). The common offset may be based on, for example, the delay at the feeder link between the satellite and the base station. The network entity may provide the F to the UE via the NTN equipment. FPC_OFFSET Values such as Figure 1 The base station 102 in the embodiment provides to the UE 104, or Figure 5 The NTN gateway 508 in the example provides the F to the UE 530 via the NTN device 502. In some aspects, the UE may calculate F based on the model. FPC_OFFSET The model is constructed by the UE using one or more parameters (eg, coefficients in a Taylor series) signaled by the network. In some aspects, these parameters may be signaled via system information.
[0113] The UE may calculate the total frequency pre-compensation adjustment value in an idle RRC state (e.g., an "RRC_IDLE" state), an inactive RRC state (e.g., an "RRC_INACTIVE" state), or an RRC connected state (e.g., an "RRC_CONNECTED" state). When the UE has established an RRC connection with a base station, the UE may be in a connected state (e.g., an "RRC_CONNECTED" state) or an inactive state (e.g., an "RRC_INACTIVE" state). If an RRC connection has not yet been established, the UE may be considered to be in an idle state (e.g., an "RRC_IDLE" state). When in the idle state, the UE and the base station may establish an RRC connection, and the UE may transition to a connected state. When in the connected state, the UE and / or the base station may release the RRC connection, and the UE may transition to an idle state. In other examples, when in the connected state, the UE and / or the base station may release and suspend the RRC connection, and the UE may transition to an inactive state. When in the inactive state, the UE and / or the base station may resume the RRC connection, and the UE may transition to a connected state. In other examples, when in an inactive state, the UE and / or the base station may release the RRC connection and the UE may transition to an idle state.
[0114] The base station may provide an FPC command to the UE, the FPC command instructing the UE to adjust the frequency of uplink transmissions to compensate for the frequency phase shift. The network may be configured to send the FPC command in response to detecting a frequency synchronization error that meets or exceeds a threshold level. Thus, the network may use the FPC command to control the uplink signal transmission frequency and / or update the FPC command. FPC_TOTAL In some aspects, the FPC command from the network may become outdated. For example, the network may consider an FPC command outdated when the time period since the UE received the last FPC command has reached or exceeded a threshold time period. In some aspects, the FPC calculation may result in a dual adaptation, where the propagation delay is determined by the network-controlled FPC (e.g., F FPC_CLOSED ) solution, the network-controlled FPC attempts to mitigate the UE's use of previous L / V updates, when the UE performs a new L / V update and updates the self-estimated FPC value F FPC_OPEN When , the previous L / V update becomes repeated. Double adaptation can also be called double correction.
[0115] Figure 6 A diagram 600 is illustrated showing an example of dual adaptation for FPC adjustment. The UE may be configured to perform L / V update 602 and use the position and velocity readings obtained from the L / V update and the NTN node position to determine the F FPC_OPEN The UE may update the L / V 602 based at least in part on the F FPC_OPENUplink transmission 604 is sent at time t1, and uplink transmission 606 is sent at time t1'. Uplink transmissions 604 and 606 may also have FPC adjustment values based on the accumulated FPC commands (eg, F FPC_TOTAL ). The network can provide F FPC_CLOSED and F FPC_OFFSET The network may provide FPC commands 608 and 612 based on previous transmissions of the UE. For example, FPC commands 608 and / or 612 may be based on the frequency error observed for uplink transmissions 604, 606, or 610 based on L / V update 602. Thus, FPC commands 608 or 612 may account for the movement of the UE relative to the NTN node after L / V update 602. When sending uplink transmissions, the UE applies the accumulation of FPC commands 608, 612, etc. For example, uplink transmission 604 and uplink transmission 606 may have a first value F FPC_TOTAL1 , and the uplink transmission 610 may have a cumulative value F FPC_TOTAL2 (FPC command 608 applies the updated F FPC_CLOSED ). The uplink transmission 616 may have a cumulative value F FPC_TOTAL3 (For its F FPC_CLOSED Based on FPC command 608 + FPC command 612). Closed loop FPC based on accumulated FPC commands from the network (e.g., F FPC_CLOSED ) may provide an FPC that accounts for the movement of the UE relative to the NTN node between L / V updates. The UE may perform another L / V update 614 and update a self-estimated FPC (e.g., an open-loop FPC value) based on the UE's position relative to the NTN node based on the L / V update 614. FPC_OPEN Therefore, the self-estimate F FPC_OPEN The movement of UEs between L / V updates 602 and 614 can also be accounted for. FPC_CLOSED +F FPC_OPEN ) can provide a double adaptation (also referred to as double correction) based on the movement of the UE relative to the NTN node. At time t2, when the uplink transmission 616 is sent, it can be close to time t1' when the uplink transmission 610 is sent and can be close to the L / V update 614. In addition to the FPC commands 608, 612 from the network to account for changes in position and / or speed, the self-estimated FPC (FPC) based on the L / V update 614 FPC_OPEN ) can also capture changes in position and / or velocity between t1 and t1'. Fig. 7A , Figure 7B , Fig. 8A and Figure 8B An example of the time period between L / V update, FPC from the network, and uplink transmission is illustrated.
[0116] NTN deployments may be associated with large Doppler shifts relative to terrestrial networks, at least in part due to the high relative speed between the UE and the NTN nodes. Therefore, in the NTN, the UE may typically apply the FPC to uplink transmissions performed in an RRC idle or inactive state and / or uplink transmissions performed in an RRC connected state. For example, in addition to the target uplink frequency, the FPC applied by the UE may have a value corresponding to the negation of the Doppler shift between the UE and the NTN node (e.g., a satellite). For example, the FPC applied by the UE may correspond to a value based on the Doppler shift between the UE and the NTN node (e.g., a satellite) and the received downlink frequency. In this way, the FPC applied by the UE may be aligned with the uplink reception frequency implemented at the base station to enable communication with different UEs that may be located at different distances from the base station and at different speeds.
[0117] In some cases, the UE may self-estimate the open-loop F based at least in part on the UE's location and the NTN node locations (eg, the locations of the NTN equipment). FPC_OPEN The UE's position may be estimated based at least in part on the current or most recent L / V update, and the UE may update the L / V update every few seconds (e.g., at intervals of 10 seconds). FPC_CLOSED The value is calculated in reverse, the open loop F FPC_OPEN The value may be an FPC calculation that is not based on feedback. Therefore, during the interval between L / V updates, the UE position used by the UE to calculate the UE-specific FPC may be inaccurate (e.g., when the UE is in motion and has not yet performed an L / V update). In some aspects, the UE position used to calculate the F FPC_OPEN The inaccuracy of the UE position of the value can be corrected in the closed-loop frequency offset (for example, the base station can measure the uplink receive frequency error and send a signal containing F FPC_CLOSED The value of the FPC command, the F FPC_CLOSED The value indicates the closed-loop frequency offset to be used in calculating the total FPC to be applied by the UE for uplink transmission. Therefore, when the UE calculates the new open-loop F after the updated L / V is updated, FPC_OPEN When the new F FPC_TOTAL The value can be corrected twice for changes in UE location—once at F FPC_CLOSED value, and another time in F FPC_OPEN This may lead to a double correction problem whereby the UE may have an overall FPC adjustment (e.g., F FPC_TOTAL ) is based at least in part on a closed-loop value (e.g., F FPC_CLOSED ) to calculate, and the open-loop value (for example, F FPC_OPEN ) can perform double correction for errors in UE position or velocity.
[0118] Fig. 7A An idealized NTN network 700 is shown in which a UE is configured to perform a position and velocity (L / V) update for each uplink transmission via an NTN device to a network entity 732. n When the position 721 moves to T n+1 At the time of the position 722, then move to T n+2 At the time of the position 723, then move to T n+N-1 At the time of the position 724, then move to T n+N At the time of the position 725, then move to T n+N+1 Similarly, the NTN equipment is at position 726 from T n When the position 711 moves to T n+1 At the time of the position 712, then move to T n+2 At the time of the position 713, then move to T n+N-1 At the time of the position 714, then move to T n+N At the time of the position 715, then move to T n+N+1 In other words, at T n At T , the UE at location 721 sends an uplink transmission to the network entity 732 via the NTN device at location 711. n+1 At T , the UE at location 722 sends an uplink transmission to the network entity 732 via the NTN device at location 712. n+2 At T , the UE at location 723 sends an uplink transmission to the network entity 732 via the NTN device at location 713. n+N-1 At T , the UE at location 724 sends an uplink transmission to the network entity 732 via the NTN device at location 714. n+N At T , the UE at location 725 sends an uplink transmission to the network entity 732 via the NTN device at location 715. n+N+1 When , the UE at location 726 sends an uplink transmission to the network entity 732 via the NTN device at location 716.
[0119] In the idealized NTN network 700, the UE performs an L / V update for each uplink transmission, thereby allowing the UE to calculate the exact F for each uplink transmission. FPC_OPEN The UE can know its position relative to the NTN equipment at multiple points in time. However, completing the L / V update is a resource-intensive process that consumes time, power, and bandwidth that can be more efficiently used for other tasks.
[0120] Figure 7BA non-idealized NTN network 750 is shown in which a UE is configured to perform a location update (eg, L / V update) every N time slots. Fig. 7A The idealized NTN network 700 in the non-idealized NTN network 750 also receives the UE from T n When the position 721 moves to T n+1 At the time of the position 722, then move to T n+2 At the time of the position 723, then move to T n+N-1 At the time of the position 724, then move to T n+N At the time of the position 725, then move to T n+N+1 Similarly, the NTN equipment is at position 726 from T n When the position 711 moves to T n+1 At the time of the position 712, then move to T n+2 At the time of the position 713, then move to T n+N-1 At the time of the position 714, then move to T n+N At the time of the position 715, then move to T n+N+1 The position at T is 716. n At T , the UE at location 721 sends an uplink transmission to the network entity 732 via the NTN device at location 711. n+1 At T , the UE at location 722 sends an uplink transmission to the network entity 732 via the NTN device at location 712. n+2 At T , the UE at location 723 sends an uplink transmission to the network entity 732 via the NTN device at location 713. n+N-1 At T , the UE at location 724 sends an uplink transmission to the network entity 732 via the NTN device at location 714. n+N At T , the UE at location 725 sends an uplink transmission to the network entity 732 via the NTN device at location 715. n+N+1 When , the UE at location 726 sends an uplink transmission to the network entity 732 via the NTN device at location 716.
[0121] However, since the UEs in the non-idealized NTN network 750 are configured to perform L / V positioning updates for every N time slots, the UEs in the non-idealized NTN network 750 may only perform L / V positioning updates for every T time slots. n The uplink transmission and T n+N The L / V update is performed at the time of the uplink transmission (e.g., just before the transmission). n When the UE is configured to FPC_OFFSETand epoch time and the UE's location 721 to estimate the one-way propagation delay on the serving link and the feeder link.
[0122] Although UE can accurately estimate T n and T n+N However, the UE may not be able to accurately estimate T n+1 , T n+2 , T n+N-1 and T n+N+1 For example, at T n+1 , T n+2 , T n+N-1 and T n+N+1 When the service link distance is estimated, it may be longer than the actual service link distance.
[0123] The UE in the non-idealized NTN network 750 may be configured to use the last known L / V updated position and velocity when estimating the serving link between the UE and the NTN device. n+1 , the UE may estimate its position to be at position 721 even though it is at position 722. Although the UE may correctly estimate the feeder link distance, the UE may incorrectly estimate the serving link distance. This may affect the UE's determination of its F FPC_TOTAL value, more specifically used to determine its F FPC_TOTAL The value of its F FPC_OPEN The UE may be configured to determine its F based on an estimate of the serving link distance and an estimate of the feeder link distance. FPC_OPEN Value. n+2 , T n+N-1 and T n+N+1 , a UE in the non-idealized NTN network 750 may similarly use its last known location to estimate the serving link distance since it may not have an accurate current location. n+2 , T n+N-1 and / or T n+N+1 When F FPC_CLOSED value to compensate for the detected frequency synchronization error.
[0124] In T n+N When the UE performs a location update, it can then determine its F FPC_TOTAL A transmission frequency error occurs in the F signal, and the F signal may then be updated based on its updated position at position 725. FPC_OPEN However, by then, network entity 732 may have also detected a transmit frequency error and may have updated its F FPC_CLOSED The value is used to compensate for the frequency error. F is calculated based on the updated position of the UE at position 725. FPC_TOTALA double correction error may result, which if used may result in a transmission error.
[0125] As the UE may not have line of sight (LoS) to the NTN equipment and no compensation for reflectors is made, the transmitted uplink transmissions may also suffer from transmit frequency errors.
[0126] Fig. 8A A static UE location network 800 is shown in which the UE does not move from its location 821. n , T n+1 , T n+2 , T n+N-1 , T n+N and T n+N+1 The NTN device sends the uplink data to the network entity 832 via the NTN device. n When the position 811 moves to T n+1 At the time of the position 812, then move to T n+2 At the time of the position 813, then move to T n+N-1 At the time of the position 814, then move to T n+N At the time of the position 815, then move to T n+N+1 816. Although the UE is at T n , T n+1 and T n+2 There is a straight line LoS to the NTN equipment at T n+N-1 , T n+N and T n+N+1 There is no direct line LoS to the NTN equipment when T n+N-1 , T n+N and T n+N+1 There is a direct line LoS to the NTN equipment.
[0127] Reflector 844 can be used at T n+N-1 , T n+N and T n+N+1 It reflects the signal between NTN equipment and UE.
[0128] Figure 8B An example T is shown n+N-1 , T n+N and T n+N+1 The static UE location network 850 of the estimated service link between the NTN device and the UE. Tn+N-1 , the UE may estimate its position to be at position 821, where no reflector is used for transmission, which may cause the UE to estimate the length of the service link at the effective position 824. Tn+N, the UE may estimate its position to be at position 821, where no reflector is used for transmission, which may result in the UE estimating the length of the service link at effective position 825. Tn+N+1 , the UE may estimate its position to be at position 821, where no reflector is used for transmission, which may result in the UE estimating the length of the serving link at effective position 826. In other words, at T n+N-1 、T n+N and T n+N+1 When T, the LoS-based propagation delay estimation error can be equivalently modeled as the UE position estimation error. Here, n+N-1 、T n+N and T n+N+1 When the service link distance is estimated, it may be shorter than the actual service link distance.
[0129] Similar to the UE in the non-idealized NTN network 750, the UE in the static UE location network 850 may correctly estimate the feeder link distance, but the UE may incorrectly estimate the serving link distance. This may affect the UE's ability to determine its F FPC_TOTAL value, more specifically used to determine its F FPC_TOTAL The value of its F FPC_OPEN The UE may be configured to determine its F based on an estimate of the serving link distance and an estimate of the feeder link distance. FPC_OPEN value.
[0130] The UE may detect that a transmission may be received from the NTN device via reflector 844, for example by comparing the transmitted timestamp from network entity 832 with the received timestamp at the UE at location 821, to determine that the estimated serving link is inaccurate. In response, the UE may correct its F FPC_OPEN However, by then, network entity 832 may have also detected a transmit frequency error and may have updated its F FPC_CLOSED The value of F is used to compensate for the frequency error. FPC_CLOSED and F considering inaccurate estimation of service links FPC_OPEN Both are used to calculate F FPC_TOTAL Double correction errors may result, which may lead to transmission errors, especially when the UE regains LoS with the NTN equipment.
[0131] exist Fig. 9 Graph 900 illustrates a sudden adjustment of the offset based on the corrected transmit frequency error. Graph 900 shows a graph where the x-axis is a slot index that increases by one slot from N-2 to N+4, and the y-axis is the FPC calculated based on the derived value, for example, according to (F FPC_CLOSED +F FPC_OPEN+F FPC_OFFSET ) calculated by F FPC_TOTAL . At each time slot in time slots N-2 to N+4, the UE may send an UL transmission to the NTN node using a frequency change based on the calculated FPC. Line 912 represents the FPC calculated based on the previously known UE position and velocity, while line 914 represents the FPC calculated based on the updated UE position and velocity determined between time slots N-1 and time slots N. In other words, line 912 may be an FPC based on the UE position and velocity applied to the uplink transmission before time slot N using the updated NTN node position and velocity at each time slot in time slots N-2 to time slots N+4. Line 914 may be an FPC based on the UE position and velocity updated after the uplink transmission at time slot N using the updated NTN node position and velocity at each time slot in time slots N-2 to time slots N+4. The UE may be configured to abruptly adjust its FPC for an offset based on its updated UE position and velocity.
[0132] At N-1, the UE may calculate the FPC using line 912 at point 921, which provides an FPC of FPC_p at time slot N-1. FPC_p may represent an FPC calculation based on the previously known position and velocity of the UE. Between N-1 and N, the UE may perform an L / V update and may update its FPC based on newly derived values (e.g., a new position and velocity determined by GNSS positioning). At N, the UE may calculate the FPC using line 914 at point 922 (i.e., using the UE position update made after time slot N-1 and before time slot N), which provides an FPC of FPC_c at time slot N. FPC_c may represent an amount of FPC derived based on the most recently updated UE position and velocity and the updated NTN position and velocity.
[0133] The total difference between the FPC at time slot N-1 and the FPC at time slot N is FPC_c–FPC_p. However, the new L / V update performed by the UE may not take into account the total difference between the FPC at time slot N-1 and the FPC at time slot N. FPC_h shows the intersection of line 912 at time slot N, and FPC_h may represent the amount of FPC uplink transmission frequency derived based on the previously updated UE position and velocity and the updated NTN node position and velocity at N. The difference between FPC_h and FPC_p is SP_off, which takes into account the frequency change of the FPC due to the NTN node position and velocity update between time slot N-1 and time slot N. The difference between FPC_c and FPC_h is AE_off, which takes into account the offset caused by propagation path blockage or the accumulated error caused by the UE position being outdated. In other words, the new L / V update performed by the UE takes into account the AE_off portion of the total difference between the FPC at time slot N-1 and the FPC at time slot N. On the other hand, AE_off can be considered as F FPC_OPEN_new With F FPC_OPEN_prev The difference between FPC_OPEN_new is the F calculated using the projected NTN node position and velocity at N and the updated UE position and velocity at N FPC_OPEN , and F FPC_OPEN_prev is the F calculated using the projected NTN node position and velocity at N and the previous UE position and velocity at N-1 FPC_OPEN .
[0134] At N, the UE may update its FPC to FPC_c at point 922 using line 914. From time slot N onwards, the UE may provide FPC updates at point 923 at N+1, point 924 at N+2, point 925 at N+3, and point 926 at N+4 using line 914. However, by abruptly adjusting the FPC based on the updated UE position and velocity determined just before time slot N, the UE may double count AE_off (i.e., double correction problem) because AE_off may have been set by FPC_c. FPC_CLOSED consider.
[0135] exist Fig.10 , graph 1000 illustrates a gradual adjustment of the offset based on the updated L / V. Fig. 9Similar to the graph 900 in FIG. 1 , graph 1000 shows a graph where the x-axis is a time slot index that increases by one time slot each time from N-2 to N+4, and the y-axis is the FPC calculated based on the derived value. Line 1012 represents the FPC calculated based on the previously known UE position and velocity, while line 1014 represents the FPC calculated based on the updated UE position and velocity determined between time slots N-1 and time slots N. However, instead of abruptly adjusting the FPC to point 1022' at time slot N, the UE may be configured to gradually adjust the FPC to point 1022 at time slot N. In other words, the UE may be configured to use a ΔT# value that partially corrects the UE's offset over time rather than all at once.
[0136] Similar to Fig. 9 900 in the graph 1000, at N-1 in the graph 1000, the UE may calculate the FPC at point 1021 using line 1012, which provides an FPC that is FPC_p. FPC_p may represent an FPC calculation based on a previously known position and velocity of the UE. Similarly, between N-1 and N, the UE may perform an L / V update and may update its FPC based on newly derived values (e.g., a new position and velocity determined by GNSS positioning). At N, the UE may calculate the FPC at point 1022 in a gradual manner, which provides a ΔT1 change relative to the amount of FPC that would have been applied at time slot N if the L / V update between N-1 and N had not occurred. At each time slot, the UE may calculate the FPC in a gradual manner. For example, at N+1, the UE may calculate the FPC at point 1023 in a gradual manner, which provides an incremental ΔT2 change. At N+2, the UE may calculate the FPC at point 1024 in a gradual manner, which provides an incremental ΔT3 change. At N+3, the UE may calculate the FPC at point 1025 in a gradual manner, which provides an incremental ΔT4 change.
[0137] The FPC at point 1025 represents the FPC used by the UE using the currently updated position and velocity based on the most recent L / V update. At N+4, the UE may calculate the FPC at point 1026 as normal. In other words, the UE may gradually increment the FPC. By gradually adjusting the FPC after an L / V update, the UE may minimize the impact of the double correction problem because the UE gradually adjusts its FPC. FPC_OPEN The network can gradually adjust its F FPC_CLOSED The line between point 1021 and point 1025 represents the FPC to be used by the UE during a gradual frequency adjustment.
[0138] As described above, the UE may gradually update its F FPC_OPENvalues to minimize the impact of the double correction error. For example, in one aspect, the UE may be configured to perform slew rate control on its UE position and velocity. In other words, the UE may be configured to gradually update its position and velocity after it performs an L / V update. After the L / V update, when the UE updates its position and velocity, the UE may be configured to gradually change the F FPC_OPEN For example, the UE may linearly combine or may filter the available UE positions and velocities to use intermediate positions and velocities between the UE's current position and velocity and the UE's last known / previous position and velocity.
[0139] For example, the UE may be configured to perform an L / V update every T seconds, such that u(n*T) provides a value (e.g., an x, y, or z axis value) of the UE's current position at n*T seconds, and u((n-1)*T) provides a value of the UE's previous position at (n-1)*T seconds. In other words, u(t') may be a function that provides a value of the UE's position at time t'. At time t, where t is between the time n when the UE last performed an L / V update, the UE may multiply the previous position by a weighting factor w, and may multiply the current position by a corresponding weighting factor (1-w), where the weighting factor w≤1. The intermediate UE position value x(t) may be calculated as x(t)=w*u(n*T)+(1-w)*u((n-1)*T), where (n+1)≥t≥n*T and w=(tn*T) / T. In other words, the intermediate UE position may be weighted based on the current position, the previous position, and the time since the previous position update. As time t passes from time n to time n+1, the reported UE position value may change linearly from the previous position at time (n-1)*T to the current position at time n*T. This linear progression may be used for any value of the UE's position (e.g., x, y, or z axis value) to gradually change the UE's position between L / V updates.
[0140] Similarly, the UE may be configured to perform an L / V update every T seconds, such that v_g(n*T) provides a value (e.g., an x, y, or z axis value) of the UE's current speed at n*T seconds, and v_g((n-1)*T) provides a value of the UE's previous speed at (n-1)*T seconds. In other words, v_g(t') may be a function that provides a value of the UE's speed at time t'. At time t, where t is between the time n when the UE last performed an L / V update, the UE may multiply the previous speed by a weighting factor w, and may multiply the current position by a corresponding weighting factor (1-w), where the weighting factor w≤1. The intermediate UE speed value v(t) may be calculated as v(t)=w*v_g(n*T)+(1-w)*v_g((n-1)*T), where (n+1)≥t≥n*T and w=(tn*T) / T. In other words, the intermediate UE speed may be weighted based on the current speed, the previous speed, and the time since the previous speed update. As time t passes from time n to time n+1, the reported UE speed value may change linearly from the previous speed at time (n-1)*T to the current speed at time n*T. This linear progression may be used for any value of the UE's speed (e.g., x, y, or z axis value) to gradually change the UE's speed between L / V updates.
[0141] In other words, at time n*T, the UE may be configured to use the UE's previous position and velocity, at time (n+1)*T, the UE may be configured to use the UE's current position and velocity, and between time n*T and (n+1)*T, the UE may be configured to use one or more calculated intermediate positions and velocities to linearly convert the UE's position and velocity between its previous position and velocity and its current position and velocity. After time (n+1)*T, the UE may not convert the UE's position and velocity. Instead, the UE may have a subsequent position and velocity generated by a new L / V update.
[0142] In another aspect, the UE may be configured to perform slew rate control on its open-loop FPC value. In other words, the UE may be configured to adjust its FPC value such that the difference between the amount of FPC derived based on the most recent L / V update and the amount of FPC that would have been derived based on the previous L / V update is less than a threshold. For example, Fig. 9 If AE_off is greater than a threshold, the UE may be configured to gradually adjust the FPC.
[0143] The following example provides yet another way to illustrate how slew rate control of open loop FPC values can be performed. The position of the UE can be considered as (x_u). The speed of the UE can be considered as (v_u). The position of the NTN node can be considered as (x_s). The speed of the NTN node can be considered as (v_x). The function f(x_u, v_u, x_s, v_s) can be used to describe FFPC_OPEN The current position value of the UE can be considered as (x_u_c). The current speed value of the UE can be considered as (v_u_c). The current position value of the NTN node can be considered as (x_s_c). The current speed value of the NTN node can be considered as (v_s_c). The previous position value of the UE can be considered as (x_u_p). The previous speed value of the UE can be considered as (v_u_p).
[0144] Therefore, the function f(x_u_p, v_u_p, x_s_c, v_s_c) can be expressed using the previously known position and velocity of the UE and the current known position and velocity of the NTN node. FPC_OPEN The function f(x_u_c, v_u_c, x_s_c, v_s_c) can be expressed using the current known position and velocity of the UE and the current known position and velocity of the NTN node. FPC_OPEN In other words, f(x_u_p,v_u_p,x_s_c,v_s_c) may be updated based on a previous UE location and a previous UE velocity, and f(x_u_c,v_u_c,x_s_c,v_s_c) may be updated based on a current UE location and a current UE velocity. Threshold F1 may represent a frequency threshold that triggers slew rate control of an open-loop FPC value of the UE. In response to determining |f(x_u_c,v_u_c,x_s_c,v_s_c)-f(x_u_p,v_u_p,x_s_c,v_s_c)|>F1, the UE may be configured to adjust its F for uplink transmissions. FPC_OPEN (i.e., f_used), such that |f_used-f(x_u_p,v_u_p,x_s_c,v_s_c)|≤F1. In other words, in response to the FPC difference between f(x_u_c,v_u_c,x_s_c,v_s_c) and f(x_u_p,v_u_p,x_s_c,v_s_c) being greater than F1 (or otherwise equal to F1), the UE may be configured to adjust f_used so that the FPC difference between f_used and f(x_u_p,v_u_p,x_s_c,v_s_c) is less than or equal to the frequency threshold F1. Adjusting the value of f_used may reduce the FPC difference between f(x_u_c,v_u_p,x_s_c,v_s_c). FPC_OPEN The value is adjusted by the corresponding amount and is therefore also based on F FPC_OPEN Value Adjustment F FPC_TOTAL value.
[0145] The UE may be further configured to adjust f_used to meet one or more threshold requirements. For example, the UE may be configured to ensure that the maximum magnitude of the FPC difference between f_used and f(x_u_p, v_u_p, x_s_c, v_s_c) in one adjustment (i.e., a single adjustment to the UE's uplink transmission immediately after the L / V update) does not exceed a first threshold F1. The UE may be configured to ensure that the minimum aggregate adjustment rate of the FPC adjustment within a time period (e.g., 0.5s, 1s, 1.5s, 2s, etc.) meets or exceeds a second threshold F2. For example, the sum of f_used and the group of past FPC adjustments within the time period may be configured to meet or exceed the second threshold F2. The UE may be configured to ensure that the maximum aggregate adjustment rate of the FPC adjustment within a time period (e.g., 100ms, 200ms, 300ms, 400ms, etc.) does not meet or exceed a third threshold F3. For example, the sum of f_used and the group of past FPC adjustments within the time period may be configured to be less than or at most meet the third threshold F3. Once f_used = f(x_u_c, v_u_c, x_s_c, v_s_c), the UE may not convert F FPC_OPEN values until the UE's subsequent position and velocity are generated via a new L / V update.
[0146] In another aspect, the UE may be configured to perform slew rate control on its open loop FPC value while resolving overlapping frequency adjustment processes. In other words, the UE may be configured to adjust its f_used or total FPC adjustment value as described above so that the difference between the amount of FPC derived based on L / V Update 1 and the amount of FPC that would have been derived based on the previous L / V Update 0 is less than a threshold, and may also be configured to use an intermediate FPC value when a subsequent position and velocity is generated by a new L / V Update 2, but f_used is not yet equal to f(x_u_c, v_u_c, x_s_c, v_s_c), where L / V Update 0 occurs before L / V Update 1 and L / V Update 1 occurs before L / V Update 2. In this regard, after L / V Update 2 , new x_u_c and v_u_c values may be updated based on L / V Update 2 , but new x_u_p and v_u_p values based on L / V Update 1 may not be used because f_used does not reach f(x_u_c, v_u_c, x_s_c, v_s_c) based on L / V Update 1 .
[0147] When the UE receives an update to the UE's position and velocity (e.g., L / V Update 2) during an ongoing gradual frequency adjustment process due to a previous update (e.g., L / V Update 1), the UE may be configured to adjust its subsequent total FPC adjustment value so that the difference between a subsequent FPC amount derived based on the subsequent L / V Update 2 and the FPC amount that would have been derived based on the previous L / V Update 1 is less than another threshold Fe.
[0148] The following example provides another way to illustrate how slew rate control of open-loop FPC values can be performed while resolving overlapping frequency adjustment processes. The parameter f_used_without_update2 may represent the f_used value that the UE would have used after L / V Update 2 if L / V Update 2 had not occurred (i.e., the UE's position and velocity were not updated a second time before f_used = f(x_u_c, v_u_c, x_s_c, v_s_c)). In other words, f_used_without_update2 may represent the FPC adjustment for the time after L / V Update 2 based on the first UE position update and the first UE velocity update (L / V Update 1), and f(x_u_c, v_u_c, x_s_c, v_s_c) may represent the FPC adjustment for the same time based on the second UE position update and the second UE velocity update (L / V Update 2). In response to determining |f_used_without_update2-f(x_u_c,v_u_c,x_s_c,v_s_c)|>Fe, the UE may be configured to adjust its used F FPC_OPEN (i.e., f_used_with_update2) such that |f_used_with_update2-f(x_u_c, v_u_c, x_s_c, v_s_c)|≤Fe. In other words, in response to the subsequent FPC difference between f_used_without_update2 and f(x_u_p, v_u_p, x_s_c, v_s_c) being greater than Fe (or otherwise equal to Fe), the UE may be configured to adjust f_used_with_update2 such that the subsequent FPC difference between f_used_with_update2 and f(x_u_c, v_u_c, x_s_c, v_s_c) (i.e., the new subsequent FPC difference) is less than or equal to the frequency threshold Fe.
[0149] The UE may be further configured to adjust f_used_with_update2 to meet one or more threshold requirements. For example, the UE may be configured to ensure that the maximum magnitude of the subsequent FPC difference between f_used_with_update2 and f(x_u_c, v_u_c, x_s_c, v_s_c) in one adjustment (i.e., a single adjustment to the UE's uplink transmission immediately after L / V Update 2) does not exceed a first threshold Fe. The UE may be configured to ensure that the minimum aggregate adjustment rate of the sum of the subsequent FPC difference between f_used_with_update2 and f(x_u_c, v_u_c, x_s_c, v_s_c) and a group of FPC adjustments within a time period (e.g., 0.5s, 1s, 1.5s, 2s, etc.) meets or exceeds a second threshold F2. For example, the difference between f_used_with_update2 and f(x_u_p, v_u_p, x_s_c, v_s_c) added to the set of past FPC adjustments within the time period may be configured to meet or exceed the second threshold F2. The UE may be configured to ensure that the maximum aggregate adjustment rate of the sum of subsequent FPC differences between f_used_with_update2 and f(x_u_c, v_u_c, x_s_c, v_s_c) and a set of FPC adjustments within a time period (e.g., 100ms, 200ms, 300ms, 400ms, etc.) meets or exceeds a third threshold F3. For example, the difference between f_used_with_update2 and f(x_u_p, v_u_p, x_s_c, v_s_c) added to the set of past FPC adjustments within the time period may be configured to be less than or at most meet the third threshold F3. Once f_used_with_update2 = f(x_u_c, v_u_c, x_s_c, v_s_c), the UE may not convert F FPC_OPEN values until subsequent positions and velocities are generated via new L / V updates.
[0150] exist Fig.11 , graph 1100 illustrates a gradual adjustment of the offset based on the updated L / V while resolving overlapping frequency adjustment processes. Fig.10, graph 1100 shows a graph where the x-axis is a slot index that increases by one slot at a time from N-2 to N+4, and the y-axis is an FPC calculated based on a derived value. Line 1112 represents an FPC calculated based on a previously known UE position and velocity, line 1114 represents an FPC calculated based on a first updated UE position and velocity determined between slots N-1 and slot N, and line 1116 represents an FPC calculated based on a second updated UE position and velocity determined between slots N+1 and N+2. Similarly, instead of abruptly adjusting the FPC to point 1122' at slot N, the UE may be configured to gradually adjust the FPC to point 1122 at slot N. In other words, the UE may be configured to use a ΔT# value that partially corrects the UE's offset over time, rather than all at once.
[0151] At N-1, the UE may calculate the FPC at point 1121 using line 1112, which provides an FPC that is FPC_p. FPC_p may represent an FPC calculation based on a previously known position and velocity of the UE. Between N-1 and N, the UE may perform L / V Update 1 and may update its FPC based on newly derived values (e.g., a new position and velocity determined by GNSS positioning). At N, the UE does not abruptly adjust the FPC to point 1122', which represents the FPC calculated using the new position and velocity determined by L / V Update 1. Instead, at N, the UE may calculate the FPC at point 1122 in a gradual manner, which provides a ΔT1 change in the amount of FPC that would be applied at time slot N if the L / V Update between N-1 and N did not occur. At N+1, the UE may continue to calculate the FPC at point 1123 in a gradual manner to align with line 1114, which provides an incremental ΔT2 change.
[0152] However, between N+1 and N+2, the UE may perform another L / V Update 2 (e.g., in response) and may update its FPC based on subsequently derived values (e.g., subsequent position and velocity determined by GNSS positioning). At N+2, the UE does not gradually adjust the FPC to point 1124', which represents a gradual tilt to the arrival line 1112. At N+2, the UE also does not abruptly adjust the FPC to point 1124"", which represents an FPC calculated using the subsequent position and velocity determined by L / V Update 2. Instead, at N+2, the UE may calculate the FPC at point 1124 in a different gradual manner, which provides a ΔT3 change in the amount of FPC that would have been applied at time slot N+2 if L / V Update 2 between N+1 and N+2 had not occurred. At N+3, the UE may calculate the FPC at point 1125 in a second gradual manner, which provides a ΔT4 change in the amount of FPC that would have been applied at time slot N+3 if L / V Update 2 between N+1 and N+2 had not occurred. At N+4, the UE may calculate the FPC at point 1126 in a second gradual manner, which provides a ΔT5 change in the amount of FPC that would have been applied at time slot N+4 if L / V Update 2 between N+1 and N+2 had not occurred.
[0153] In another aspect, the UE may be configured to perform a gradual control of its uplink center frequency. In other words, in response to determining that the transmit frequency error between the UE and the reference frequency exceeds a threshold value ±Fe, the UE may be configured to adjust its frequency to within ±Fe. REF ) may be based on:
[0154] F REF =F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +f(F_d)
[0155] F FPC_CLOSED 、F FPC_OPEN and F FPC_OFFSET It can be as previously mentioned about F FPC_TOTAL F_d may be the center frequency of the DL transmission received from the NTN node. In other words, F REF May be determined as a function of the frequency based on the download frequency. An example f(F_d) may be f(F_d)=F_d*f_u / f_d, where f_u is the center frequency of an ideal uplink transmission and f_d is the center frequency of an ideal DL transmission (e.g., the frequency used by the UE in the absence of Doppler shift). The values of f_u and f_d may be provided in a lookup table associated with the frequency band. For example, a channel with a defined frequency band may have an f_u of 2 GHz and an f_d of 1.98 GHz defined in the lookup table.
[0156] The UE may be configured to adjust F REF , so that the adjusted F REF The future sending and using the previous F REF The frequency change (i.e., the transmission frequency error value) between the previous transmissions (except for the F between these two transmissions due to the NTN node position and speed update) FPC_OPEN (except for changes in N-1 and N-2) meet one or more threshold requirements. No update F is made between N-1 and N-2. FPC_CLOSED In the case of NTN, the F between two transmissions is caused by the position and speed update of the NTN node. FPC_OPEN The changes can be, for example, Fig. 9 SP_off in the graph 900 in FIG. 9. The UE may be configured to use the unadjusted F REF (applying the above formula to the current value) The future send is the same as using the previous F REF The frequency change between the previous transmissions (applying the above formula to the value of the last transmission) (except for the F between these two transmissions due to NTN node position and speed updates) FPC_OPEN If the change exceeds ±Fe, adjust F REF The UE may be configured to ensure that the adjusted F REF The future sending of F REF The frequency change in one adjustment between the previous transmissions (except for the F between these two transmissions due to NTN node position and speed updates) FPC_OPEN The UE may be configured to ensure that the maximum amplitude of the Fq used is not greater than the first threshold Fq. REF The future sending of F REF The frequency change between the previous transmissions (except for the F between these two transmissions due to NTN node position and speed updates) FPC_OPEN a set of FPC adjustments within a time period (e.g., 0.5s, 1s, 1.5s, 2s, etc.) (except for the FPCs between transmissions due to NTN node position and velocity updates) FPC_OPEN The minimum aggregate adjustment rate of the sum of the adjusted Fp (except for the change of REF The future sending of F REF The frequency change between the previous transmissions (except for the F between these two transmissions due to NTN node position and speed updates) FPC_OPEN a set of FPC adjustments within a time period (e.g., 100ms, 200ms, 300ms, 400ms, etc.) (except for the FPC between transmissions due to NTN node position and speed updates) FPC_OPENThe maximum aggregate adjustment rate of the sum of the adjusted Fr (excluding the change of the adjusted Fr) meets or does not exceed the third threshold Fr. In some aspects, Fr may be equal to Fq. Once the adjusted Fr is used REF The future sending of F REF The frequency change between the previous transmissions (except for the F between these two transmissions due to NTN node position and speed updates) FPC_OPEN If the UE's uplink center frequency is zero, the UE may not perform gradual control of its uplink center frequency.
[0157] exist Fig.12 , the connection flow diagram 1200 has a UE 1202 configured to send uplink transmissions to a network entity 1206 via an NTN device 1204.
[0158] The network entity 1206 may be configured to send a network FPC command 1222 to the UE 1202 to adjust the frequency of the uplink transmission to compensate for the propagation delay. In response, the UE 1202 may then be configured to use FPC to adjust the frequency of its uplink transmission signals (such as uplink transmission 1224 and uplink transmission 1230) to the network entity 1206 to compensate for the propagation delay. In some aspects, the network entity 1206 may be configured to send the network FPC command 1222 in response to detecting that the frequency error associated with the UE 1202 is greater than or equal to a threshold.
[0159] At 1212, UE 1202 may determine an FPC. Such an FPC may be based on, for example, FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET F FPC_TOTAL Value or based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +f(F_d)F REF The FPC may be calculated based on, for example, an estimated position and velocity of the NTN device 1204, an estimated position and velocity of the UE 1202, and / or an estimated environment of a beam with no propagation path obstruction between the UE 1202 and the NTN device 1204. The UE 1202 may be configured to send an uplink transmission 1224 to the network entity 1206 via the NTN device 1204 using the calculated reference FPC value for adjusting the frequency of the uplink transmission 1224.
[0160] At 1214, the network entity 1206 may be configured to calculate a network FPC value. Such a value may include, for example, F FPC_CLOSED and / or F FPC_OFFSET For example, the network entity 1206 may detect an error in the frequency used by the UE and may change the F FPC_CLOSEDThe network entity 1206 may then send at least some of the network FPC values 1226 to the UE 1202 for use by the UE in calculating the FPC, such as F FPC_CLOSED The network entity 1206 may also send another network FPC command 1228 to the UE 1202 via the NTN device 1204. In some aspects, the network entity 1206 may be configured to send the network FPC command 1228 in response to detecting that the frequency error associated with the UE 1202 is greater than or equal to a threshold.
[0161] At 1216, UE 1202 may determine a corrected FPC. For example, UE 1202 may perform a GNSS positioning update to determine an updated position and velocity if it has determined that UE 1202 may not have the same position and velocity as it had during a previous GNSS positioning, and may update the position and velocity of UE 1202. On the other hand, UE 1202 may determine that a previous transmission (such as uplink transmission 1224) was blocked and was sent via a reflector, and the updated service link length may be used to calculate F FPC_OPEN .
[0162] At 1218, the UE 1202 may gradually update the FPC over time. For example, the UE may be configured to perform slew rate control on its UE position and speed, perform slew rate control on its open loop FPC value while not resolving overlapping frequency adjustment procedures, perform slew rate control on its open loop FPC value while resolving overlapping frequency adjustment procedures, or perform gradual control of its uplink center frequency. The UE 1202 may be configured to send an uplink transmission 1230 to the network entity 1206 via the NTN device 1204 using the gradually updated FPC.
[0163] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 350, 405, 530, 1202; device 1504). At 1302, the UE may be configured to receive one or more FPC commands from the NTN. For example, 1302 may be performed by Fig.12 1302 may also be executed by UE 1202 in the embodiment, which may receive a network FPC command 1228 from a network entity 1206 via NTN device 1204. Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0164] At 1304, the UE may be configured to send an uplink transmission with a frequency change including an overall FPC adjustment in response to receiving the one or more FPC commands. The overall FPC adjustment may be calculated based on a current UE location update and a current UE speed update. The overall FPC adjustment may satisfy one or more threshold requirements. The overall FPC adjustment may be calculated based on intermediate UE location updates between the current UE location update and a previous UE location update and intermediate UE speed updates between the current UE speed update and a previous UE speed update. For example, 1304 may be calculated by Fig.12 1202 in the embodiment of the present invention may be executed by a UE 1202 in the embodiment of the present invention, which may send an uplink transmission 1230 to the network entity 1206 via the NTN device 1204 using the gradually updated FPC in response to receiving a network FPC command 1228 from the network entity 1206 via the NTN device 1204. The gradually updated FPC may be gradually updated over time at 1218 by performing slew rate control on its UE position and speed. The gradually updated FPC may be gradually updated over time at 1218 by performing slew rate control on its open loop FPC value while not resolving overlapping frequency adjustment processes. The gradually updated FPC may be gradually updated over time at 1218 by performing slew rate control on its open loop FPC value while resolving overlapping frequency adjustment processes. The gradually updated FPC may be gradually updated over time at 1218 by performing gradual control on its uplink center frequency. 1304 may also be performed by Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0165] Fig.14 1400 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 350, 405, 530, 1202; device 1504). At 1402, the UE may be configured to receive one or more FPC commands from the NTN. For example, 1402 may be performed by Fig.12 1402 may also be executed by UE 1202 in the embodiment, which may receive a network FPC command 1228 from a network entity 1206 via NTN device 1204. Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0166] At 1404, the UE may be configured to send an uplink transmission with a frequency change including an overall FPC adjustment in response to receiving the one or more FPC commands. The overall FPC adjustment may be calculated based on a current UE location update and a current UE speed update. The overall FPC adjustment may satisfy one or more threshold requirements. The overall FPC adjustment may be calculated based on intermediate UE location updates between the current UE location update and a previous UE location update and intermediate UE speed updates between the current UE speed update and a previous UE speed update. For example, 1404 may be calculated by Fig.12 1202 in the embodiment of the present invention may be executed by a UE 1202 in the embodiment of the present invention, which may send an uplink transmission 1230 to the network entity 1206 via the NTN device 1204 using the gradually updated FPC in response to receiving a network FPC command 1228 from the network entity 1206 via the NTN device 1204. The gradually updated FPC may be gradually updated over time at 1218 by performing slew rate control on its UE position and speed. The gradually updated FPC may be gradually updated over time at 1218 by performing slew rate control on its open loop FPC value while not resolving overlapping frequency adjustment processes. The gradually updated FPC may be gradually updated over time at 1218 by performing slew rate control on its open loop FPC value while resolving overlapping frequency adjustment processes. The gradually updated FPC may be gradually updated over time at 1218 by performing gradual control on its uplink center frequency. 1404 may also be performed by Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0167] At 1406, the UE may adjust the total FPC adjustment in response to the FPC difference between the total FPC adjustment and the FPC adjustment value meeting or exceeding the FPC difference threshold, such that the FPC difference meets one or more threshold requirements. The total FPC adjustment may be based on a current UE location update and a current UE speed update, and the FPC adjustment value may be based on a previous UE location update and a previous UE speed update. For example, 1406 may be performed by Fig.12 The UE 1202 in the embodiment may be executed by adjusting the total FPC adjustment at 1216 or 1218 in response to the FPC difference between the total FPC adjustment and the FPC adjustment value meeting or exceeding the FPC difference threshold so that the FPC difference meets one or more threshold requirements. The total FPC adjustment may be based on the current UE location update and the current UE speed update, and the FPC adjustment value may be based on the previous UE location update and the previous UE speed update. 1406 may also be performed by Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0168] At 1408, the UE may adjust the total FPC adjustment in response to the transmit frequency error value between the total FPC adjustment and the reference frequency (in addition to the FPC adjustment based on the NTN node location update and the NTN node speed update) exceeding the transmit frequency error threshold, so that the transmit frequency error value meets one or more threshold requirements. For example, 1408 may be performed by Fig.12 1408 may also be performed by UE 1202 in the embodiment, the UE may adjust the total FPC adjustment in response to the transmission frequency error value between the total FPC adjustment and the reference frequency (except the FPC adjustment based on the NTN node position update and the NTN node speed update) exceeding the transmission frequency error threshold, so that the transmission frequency error value meets one or more threshold requirements. Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0169] At 1410, the UE may send a subsequent uplink transmission with a subsequent frequency change having a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update in response to a subsequent FPC difference between the subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold. The subsequent total FPC adjustment may meet one or more threshold requirements. For example, 1410 may be performed by Fig.12 1402 in the embodiment of the present invention may be executed by UE 1202 in the embodiment of the present invention, the UE may send a subsequent uplink transmission with a subsequent frequency change in response to a subsequent FPC difference between the subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold, the subsequent frequency change having a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The subsequent total FPC adjustment may meet one or more threshold requirements. 1410 may also be performed by Fig.15 The FPC assembly 198 of the device 1504 is executed.
[0170] Fig.151500 is an example of a hardware implementation of an example device 1504. The device 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1404 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the device 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or communicate using antennas 1580. The cellular baseband processor 1524 communicates with the UE 104 and / or with the RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1524 / application processor 1506 to perform the various functions described above when executed by the cellular baseband processor 1524 / application processor 1506. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software.The cellular baseband processor 1524 / application processor 1506 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1504 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1524 and / or the application processor 1506, while in another configuration, the device 1504 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1504.
[0171] As discussed above, component 198 is configured to receive one or more FPC commands from the NTN and transmit an uplink transmission with a frequency change including an overall FPC adjustment in response to receiving the one or more FPC commands. Component 198 may be within the cellular baseband processor 1524, the application processor 1506, or within both the cellular baseband processor 1524 and the application processor 1506. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1504 may include a variety of components configured for various functions. In one configuration, the apparatus 1504 and specifically the cellular baseband processor 1524 and / or the application processor 1506 include: means for receiving one or more FPC commands from the NTN; means for sending an uplink transmission with a frequency change including an overall FPC adjustment in response to receiving the one or more FPC commands; means for weighting intermediate UE location updates based on a current UE location update, a previous UE location update, and a time since the previous UE location update; means for weighting intermediate UE speed updates based on a current UE speed update, a previous UE speed update, and a time since the previous UE location update; means for sending an uplink transmission with an overall FPC adjustment that meets one or more threshold requirements in response to an FPC difference between a current FPC adjustment and a previous FPC adjustment meeting or exceeding an FPC difference threshold; means for basing a current FPC adjustment on a current UE location update, a previous UE speed update, a current NTN node location update, and a current NTN node speed update means for basing a previous FPC adjustment on a previous UE location update, a previous UE speed update, a current NTN node location update, and a current NTN node speed update; means for sending a subsequent uplink transmission with a subsequent frequency change including a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update in response to a subsequent FPC difference between a subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold; means for basing a subsequent total FPC adjustment on a subsequent UE location update, a subsequent UE speed update, a subsequent NTN node location update, and a subsequent NTN node speed update; and means for sending an uplink transmission with a total FPC adjustment that meets one or more threshold requirements based on an FPC adjustment change other than an FPC adjustment based on an NTN node location update and an NTN node speed update and a network controlled common FPC value in response to a transmit frequency error value between a transmit frequency of the UE and a reference frequency exceeding a transmit frequency error threshold. Apparatus 1504 may include means for receiving one or more FPC commands from an NTN node.The device 1504 may include means for sending an uplink transmission with a frequency change including a total FPC adjustment calculated based on the following items in response to receiving the one or more FPC commands: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements; or (b) an intermediate UE location between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and the previous UE speed update. The device 1504 may include means for weighting the intermediate UE location based on the current UE location update, the previous UE location update, and the time since the previous UE location update. The device 1504 may include means for weighting the intermediate UE speed based on the current UE speed update, the previous UE speed update, and the time since the previous UE location update. The device 1504 may include means for adjusting the total FPC adjustment in response to an FPC difference between the total FPC adjustment and the FPC adjustment value meeting or exceeding the FPC difference threshold so that the FPC difference meets one or more threshold requirements. The device 1504 may include a component for sending a subsequent uplink transmission with a subsequent frequency change in response to a subsequent FPC difference between a subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold, the subsequent frequency change having a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The device 1504 may include a component for adjusting the total FPC adjustment in response to a transmission frequency error value between a total FPC adjustment other than an FPC adjustment based on an NTN node location update and an NTN node speed update and a reference frequency exceeding a transmission frequency error threshold so that the transmission frequency error value meets one or more threshold requirements. The component may be a component 198 of the device 1504 configured to perform the functions recorded by the component. As described above, the device 1504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recorded by the component.
[0172] Fig.161600 is a flow chart of a wireless communication method. The method may be performed by an NTN node (e.g., base station 102, base station 310; NTN device 402, NTN device 502, NTN device 504, NTN device 1204; NTN gateway 404; core network 410; RAN 412; NTN-DU 414; NTN-CU 416; network entity 1502, network entity 1702, network entity 1860). At 1602, the NTN node may send one or more FPC commands to the UE. For example, 1602 may be performed by NTN device 1204, which may send one or more FPC commands to UE 1202. In addition, operation 1602 may be performed by Fig.17 and Fig.18 Component 199 in is executed.
[0173] At 1604, the NTN node may receive an uplink transmission having a frequency change including a total FPC adjustment calculated based on: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may satisfy one or more threshold requirements, or (b) an intermediate UE location update between the current UE location update and a previous UE location update and an intermediate UE speed update between the current UE speed update and a previous UE speed update in response to sending the one or more FPC commands. For example, 1604 may be performed by the NTN device 1204, which may receive the uplink transmission 1224 or the uplink transmission 1230 in response to sending the network FPC command 1222 or the network FPC command 1228. The uplink transmission 1230 may have a frequency change including a total FPC adjustment calculated based on: (a) a current UE location update and a current UE speed update of the UE 1202, wherein the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE location update between a current UE location update and a previous UE location update of the UE 1202 and an intermediate UE speed update between a current UE speed update and a previous UE speed update. In addition, operation 1604 may be performed by Fig.17 and Fig.18 Component 199 in is executed.
[0174] At 1606, the NTN node may receive a subsequent uplink transmission with a subsequent frequency change including a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The subsequent total FPC adjustment may satisfy one or more threshold requirements. For example, 1606 may be performed by the NTN device 1204, which may receive a subsequent uplink transmission with a subsequent frequency change including a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The subsequent total FPC adjustment may satisfy one or more threshold requirements. In addition, operation 1606 may be performed by Fig.17and Fig.18 Component 199 in is executed.
[0175] Fig.17 1700 is a diagram illustrating an example of a hardware implementation of a network entity 1702. The network entity 1702 may be a BS, may be a component of a BS, or may implement BS functionality. The network entity 1702 may include at least one of a CU 1710, a DU 1730, or a RU 1740. For example, depending on the layer functionality handled by the component 199, the network entity 1702 may include a CU 1710; both a CU 1710 and a DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both a DU 1730 and a RU 1740; or a RU 1740. The CU 1710 may include a CU processor 1712. The CU processor 1712 may include an on-chip memory 1712'. In some aspects, the CU 1710 may also include an additional memory module 1714 and a communication interface 1718. CU 1710 communicates with DU 1730 via a midhaul link such as an F1 interface. DU 1730 may include a DU processor 1732. DU processor 1732 may include on-chip memory 1732'. In some aspects, DU 1730 may also include additional memory modules 1734 and communication interfaces 1738. DU 1730 communicates with RU 1740 via a fronthaul link. RU 1740 may include a RU processor 1742. RU processor 1742 may include on-chip memory 1742'. In some aspects, RU 1740 may also include additional memory modules 1744, one or more transceivers 1746, antenna 1780, and communication interface 1748. RU 1740 communicates with UE 104. On-chip memory 1712', 1732', 1742' and additional memory modules 1714, 1734, 1744 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory can also be used to store data manipulated by the processor when executing the software.
[0176] As described above, component 199 is configured to send one or more FPC commands to the UE. Component 199 may be configured to receive an uplink transmission with a frequency change in response to sending the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on the following items: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE location between the current UE location update and the previous UE location update and an intermediate UE speed between the current UE speed update and the previous UE speed update. Component 199 may be within one or more processors of one or more of CU 1710, DU1730, and RU 1740. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 1702 may include a variety of components configured for various functions. In one configuration, network entity 1702 may include a component for sending one or more FPC commands to the UE. The network entity 1702 may include a component for receiving an uplink transmission with a frequency change including a total FPC adjustment calculated based on the following items in response to sending the one or more FPC commands: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements; or (b) an intermediate UE location between the current UE location update and the previous UE location update and an intermediate UE speed between the current UE speed update and the previous UE speed update. The network entity 1702 may include a component for receiving a subsequent uplink transmission with a subsequent frequency change including a subsequent total FPC adjustment calculated based on the subsequent UE location update and the subsequent UE speed update. The component may be a component 199 of the network entity 1702 configured to perform the functions recorded by the component. As described above, the network entity 1702 may include a Tx processor 316, an Rx processor 370, and a controller / processor 375. Therefore, in one configuration, these components may be a Tx processor 316, an Rx processor 370, and a controller / processor 375 configured to perform the functions recorded by these components.
[0177] Fig.181800 is an example of a hardware implementation of an example of an example network entity 1860. In one example, the network entity 1860 may be within the core network 120. The network entity 1860 may include a network processor 1812. The network processor 1812 may include an on-chip memory 1812'. In some aspects, the network entity 1860 may also include an additional memory module 1814. The network entity 1860 communicates with the CU 1802 directly (e.g., backhaul link) or indirectly (e.g., through the RIC) via a network interface 1880. The on-chip memory 1812' and the additional memory module 1814 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1812 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.
[0178] As described above, component 199 is configured to send one or more FPC commands to the UE. Component 199 may be configured to receive an uplink transmission with a frequency change in response to sending the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE location between a current UE location update and a previous UE location update and an intermediate UE speed between a current UE speed update and a previous UE speed update. Component 199 may be within processor 1812. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1860 may include a variety of components configured for various functions. In one configuration, network entity 1860 may include a component for sending one or more FPC commands to the UE. The network entity 1860 may include means for receiving, in response to sending the one or more FPC commands, an uplink transmission having a frequency change including a total FPC adjustment calculated based on: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements; or (b) an intermediate UE location between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update. The network entity 1860 may include means for receiving a subsequent uplink transmission having a subsequent frequency change including a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The means may be a component 199 of the network entity 1860 configured to perform the functions recited by the means.
[0179] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.
[0180] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ......" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a functional component unless the element is explicitly described using the phrase "component for...".
[0181] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.
[0182] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.
[0183] Aspect 1 is a method for wireless communication at a UE, the method comprising receiving one or more FPC commands from an NTN node. The method may also include sending an uplink transmission with a frequency change in response to receiving the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment meets one or more threshold requirements, or (b) an intermediate UE location update between the current UE location update and a previous UE location update and an intermediate UE speed update between the current UE speed update and a previous UE speed update.
[0184] Aspect 2 is a method according to aspect 1, wherein the intermediate UE location updates can be weighted based on the current UE location update, the previous UE location update, and the time since the previous UE location update. The intermediate UE speed updates can also be weighted based on the current UE speed update, the previous UE speed update, and the time since the previous UE location update.
[0185] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising adjusting the total FPC adjustment in response to an FPC difference between the total FPC adjustment and the FPC adjustment value meeting or exceeding an FPC difference threshold, so that the FPC difference meets the one or more threshold requirements. The total FPC adjustment value may be updated based on the current UE location and the current UE speed, and the FPC adjustment value is updated based on the previous UE location and the previous UE speed.
[0186] Aspect 4 is a method according to aspect 3, wherein the total FPC adjustment may be based on the current UE location update, the current UE speed update, the current NTN node location update, and the current NTN node speed update. The FPC adjustment value may be based on the previous UE location update, the previous UE speed update, the current NTN node location update, and the current NTN node speed update.
[0187] Aspect 5 is a method according to any one of Aspects 3 to 4, wherein the one or more threshold requirements include at least one of the following: (a) a maximum amplitude of the FPC difference in a single adjustment sent for the uplink that does not exceed a first threshold; (b) a minimum aggregation adjustment rate of the sum of the FPC difference and a first group of FPC adjustments in a first time period that meets or exceeds a second threshold; or (c) a maximum aggregation adjustment rate of the sum of the FPC difference and a second group of FPC adjustments in a second time period that meets or does not exceed a third threshold.
[0188] Aspect 6 is a method according to aspect 5, wherein the first threshold comprises the FPC difference threshold, the second threshold comprises a first plurality of 0.5 seconds, and the third threshold comprises a second plurality of 100 ms.
[0189] Aspect 7 is a method according to any one of aspects 3 to 6, the method further comprising, in response to a subsequent FPC difference between a subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold, sending a subsequent uplink transmission with a subsequent frequency change, the subsequent frequency change having the subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The subsequent total FPC adjustment may meet the one or more threshold requirements.
[0190] Aspect 8 is a method according to aspect 7, wherein the subsequent total FPC adjustment is based on the subsequent UE location update, the subsequent UE speed update, the subsequent NTN node location update and the subsequent NTN node speed update.
[0191] Aspect 9 is a method according to any one of Aspects 7 to 8, wherein the one or more threshold requirements include at least one of the following: (a) a maximum amplitude of the subsequent FPC difference in a single adjustment sent for the subsequent uplink that does not exceed a first threshold; (b) a minimum aggregate adjustment rate of the sum of the subsequent FPC difference and a first group of FPC adjustments within a first time period that meets or exceeds a second threshold; or (c) a maximum aggregate adjustment rate of the sum of the subsequent FPC difference and a second group of FPC adjustments within a second time period that does not exceed a third threshold.
[0192] Aspect 10 is a method according to any one of Aspects 1 to 9, the method further comprising, in response to a transmission frequency error value between the total FPC adjustment other than the FPC adjustment based on the NTN node position update and the NTN node speed update and the reference frequency exceeding a transmission frequency error threshold, adjusting the total FPC adjustment so that the transmission frequency error value meets the one or more threshold requirements.
[0193] Aspect 11 is a method according to Aspect 10, wherein the one or more threshold requirements include at least one of the following: (a) a maximum amplitude of a sending frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which does not exceed a first threshold; (b) a minimum aggregate adjustment rate of the sum of the sending frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first group of FPC adjustments in a first time period other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which meets or exceeds a second threshold; or (c) a maximum aggregate adjustment rate of the sum of the sending frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a second group of FPC adjustments in a second time period other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which meets or does not exceed a third threshold.
[0194] Aspect 12 is a method according to any one of aspects 10 to 11, wherein the total FPC adjustment is based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +F DL *(f UL / f DL ), F FPC_CLOSED includes the closed-loop FPC value received from the NTN node, F FPC_OPEN including an open-loop FPC value based on the current UE location update, the current UE speed update, the NTN node location update, and the NTN node speed update, F FPC_OFFSET Including fixed offset, F DL comprising a first center frequency of a transmission received from said NTN node, f UL includes the second center frequency of the ideal uplink transmission, and f DL Includes a third center frequency for ideal downlink transmission.
[0195] Aspect 13 is the method of any one of aspects 1 to 12, wherein the total FPC adjustment is based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET , F FPC_CLOSED includes the closed-loop FPC value received from the NTN node, F FPC_OPEN including an open-loop FPC value based on the current UE location update, the current UE speed update, the NTN node location update, and the NTN node speed update, and F FPC_OFFSET Includes fixed offset.
[0196] Aspect 14 is a method for wireless communication at a UE, wherein the method may include receiving one or more FPC commands from an NTN node. The method may include sending an uplink transmission with a frequency change in response to receiving the one or more FPC commands, wherein the frequency change has a total FPC adjustment calculated based on the following items: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE position between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update.
[0197] Aspect 15 is a method according to aspect 14, wherein the method may include weighting the intermediate UE position based on the current UE location update, the previous UE location update, and the time since the previous UE location update. The method may include weighting the intermediate UE speed based on the current UE speed update, the previous UE speed update, and the time since the previous UE location update.
[0198] Aspect 16 is a method according to any one of aspects 14 or 15, wherein the method may include adjusting the total FPC adjustment in response to an FPC difference between the total FPC adjustment and the FPC adjustment value meeting or exceeding an FPC difference threshold, so that the FPC difference meets the one or more threshold requirements. The total FPC adjustment value may be updated based on the current UE location and the current UE speed. The FPC adjustment value may be updated based on the previous UE location and the previous UE speed.
[0199] Aspect 17 is a method according to aspect 16, wherein the total FPC adjustment may be based on the current UE location update, the current UE speed update, the current NTN node location update, and the current NTN node speed update. The FPC adjustment value may be based on the previous UE location update, the previous UE speed update, the current NTN node location update, and the current NTN node speed update.
[0200] Aspect 18 is a method according to any one of Aspects 16 or 17, wherein the one or more threshold requirements may include at least one of the following: (a) a maximum amplitude of the FPC difference in a single adjustment sent for the uplink that does not exceed a first threshold; (b) a minimum aggregate adjustment rate of the sum of the FPC difference and a first group of FPC adjustments in a first time period that meets or exceeds a second threshold; or (c) a maximum aggregate adjustment rate of the sum of the FPC difference and a second group of FPC adjustments in a second time period that does not exceed a third threshold.
[0201] Aspect 19 is a method according to any one of aspects 16 to 18, wherein the method may include sending a subsequent uplink transmission with a subsequent frequency change in response to a subsequent FPC difference between a subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold, the subsequent frequency change having the subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The subsequent total FPC adjustment may meet the one or more threshold requirements.
[0202] Aspect 20 is a method according to aspect 19, wherein the subsequent total FPC adjustment may be based on the subsequent UE location update, the subsequent UE speed update, the subsequent NTN node location update and the subsequent NTN node speed update.
[0203] Aspect 21 is a method according to Aspect 20, wherein the one or more threshold requirements may include at least one of the following: (a) a maximum amplitude of the subsequent FPC difference in a single adjustment sent for the subsequent uplink that does not exceed a first threshold; (b) a minimum aggregate adjustment rate of the sum of the subsequent FPC difference and a first group of FPC adjustments within a first time period that meets or exceeds a second threshold; or (c) a maximum aggregate adjustment rate of the sum of the subsequent FPC difference and a second group of FPC adjustments within a second time period that does not exceed a third threshold.
[0204] Aspect 22 is a method according to any one of Aspects 14 to 21, wherein the method may include adjusting the total FPC adjustment in response to a transmission frequency error value between the total FPC adjustment other than the FPC adjustment based on the NTN node position update and the NTN node speed update and the reference frequency exceeding a transmission frequency error threshold, so that the transmission frequency error value meets the one or more threshold requirements.
[0205] Aspect 23 is a method according to Aspect 22, wherein the one or more threshold requirements may include at least one of the following: (a) a maximum amplitude of the transmission frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which does not exceed a first threshold; (b) a minimum aggregate adjustment rate that meets or exceeds a second threshold for the sum of the transmission frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first group of FPC adjustments in a first time period other than the FPC adjustment based on the NTN node location update and the NTN node speed update; or (c) a maximum aggregate adjustment rate that does not exceed a third threshold for the sum of the transmission frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a second group of FPC adjustments in a second time period other than the FPC adjustment based on the NTN node location update and the NTN node speed update.
[0206] Aspect 24 is a method according to any one of aspects 22 or 23, wherein the overall FPC adjustment can be based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +F DL *(f UL / f DL ). FPC_CLOSED May include a closed loop FPC value received from the NTN node. FPC_OPEN The open-loop FPC value may include an update based on the current UE location, the current UE speed, the NTN node location, and the NTN node speed. FPC_OFFSET Can include fixed offset. F DL may include a first center frequency of a transmission received from the NTN node. UL May include a second center frequency for the desired uplink transmission. DL A third center frequency for the desired downlink transmission may be included.
[0207] Aspect 25 is a method according to any one of aspects 14 to 24, wherein the overall FPC adjustment can be based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET . F FPC_CLOSED May include a closed loop FPC value received from the NTN node. FPC_OPEN The open loop FPC value may include an update based on the current UE location, the current UE speed, the NTN node location, and the NTN node speed. FPC_OFFSET A fixed offset may be included.
[0208] Aspect 26 is a method for wireless communication at an NTN node, wherein the method may include sending one or more FPC commands to a UE. The method may include receiving an uplink transmission with a frequency change in response to sending the one or more FPC commands, wherein the frequency change has a total FPC adjustment calculated based on: (a) a current UE location update and a current UE speed update, wherein the total FPC adjustment may meet one or more threshold requirements, or (b) an intermediate UE location between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update.
[0209] Aspect 27 is a method according to aspect 26, wherein the intermediate UE position can be weighted based on the current UE location update, the previous UE location update and the time since the previous UE location update. The intermediate UE speed can be weighted based on the current UE speed update, the previous UE speed update and the time since the previous UE location update.
[0210] Aspect 28 is a method according to any one of aspects 26 or 27, wherein the total FPC adjustment can be adjusted so that the FPC difference between the total FPC adjustment and the FPC adjustment value meets the one or more threshold requirements. The total FPC adjustment can be based on a current UE location update and a current UE speed update, and the FPC adjustment value can be based on a previous UE location update and a previous UE speed update.
[0211] Aspect 29 is a method according to aspect 28, wherein the total FPC adjustment may be based on the current UE location update, the current UE speed update, the current NTN node location update, and the current NTN node speed update. The FPC adjustment value may be based on the previous UE location update, the previous UE speed update, the current NTN node location update, and the current NTN node speed update.
[0212] Aspect 30 is a method according to any one of Aspects 28 or 29, wherein the one or more threshold requirements may include at least one of the following: (a) a maximum amplitude of the FPC difference in a single adjustment sent for the uplink that does not exceed a first threshold; (b) a minimum aggregate adjustment rate of the FPC difference and a first sum of a first group of FPC adjustments in a first time period that meets or exceeds a second threshold; or (c) a maximum aggregate adjustment rate of the FPC difference and a second sum of a second group of FPC adjustments in a second time period that meets or does not exceed a third threshold.
[0213] Aspect 31 is a method according to any one of aspects 28 to 30, wherein the method may include receiving a subsequent uplink transmission with a subsequent frequency change, the subsequent frequency change having a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update. The subsequent total FPC adjustment may meet the one or more threshold requirements.
[0214] Aspect 32 is a method according to aspect 31, wherein the subsequent total FPC adjustment may be based on the subsequent UE location update, the subsequent UE speed update, the subsequent NTN node location update and the subsequent NTN node speed update.
[0215] Aspect 33 is a method according to any one of Aspects 31 or 32, wherein the one or more threshold requirements may include at least one of the following: (a) a maximum amplitude of subsequent FPC differences in a single adjustment sent for the uplink that does not exceed a first threshold; (b) a minimum aggregation adjustment rate of a first sum of the subsequent FPC differences and a first group of FPC adjustments within a first time period that meets or exceeds a second threshold; or (c) a maximum aggregation adjustment rate of a second sum of the subsequent FPC differences and a second group of FPC adjustments within a second time period that meets or does not exceed a third threshold.
[0216] Aspect 34 is a method according to any one of aspects 26 to 33, wherein the overall FPC adjustment can be adjusted so that the transmit frequency error value meets the one or more threshold requirements.
[0217] Aspect 35 is a method according to Aspect 34, wherein the one or more threshold requirements may include at least one of the following: (a) a maximum amplitude of the transmission frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which does not exceed a first threshold; (b) a minimum aggregate adjustment rate of a first sum of the transmission frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first group of FPC adjustments in a first time period other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which meets or exceeds a second threshold; (c) a maximum aggregate adjustment rate of a second sum of the transmission frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a second group of FPC adjustments in a second time period other than the FPC adjustment based on the NTN node location update and the NTN node speed update, which meets or does not exceed a third threshold.
[0218] Aspect 36 is a method according to any one of aspects 34 or 35, wherein the overall FPC adjustment can be based on FFPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +F DL *(f UL / f DL ). FPC_CLOSED May include a closed loop FPC value received from the NTN node. FPC_OPEN The open loop FPC value may include an update based on the current UE location, the current UE speed, the NTN node location, and the NTN node speed. FPC_OFFSET Can include fixed offset. F DL may include a first center frequency of a transmission received from the NTN node. UL May include a second center frequency for the desired uplink transmission. DL A third center frequency for the desired downlink transmission may be included.
[0219] Aspect 37 is a method according to any one of aspects 26 to 36, wherein the overall FPC adjustment can be based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET . F FPC_CLOSED May include a closed loop FPC value received from the NTN node. FPC_OPEN The open loop FPC value may include an update based on the current UE location, the current UE speed, the NTN node location, and the NTN node speed. FPC_OFFSET A fixed offset may be included.
[0220] Aspect 38 is an apparatus for performing wireless communications, the apparatus comprising: a memory; at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of Aspects 1 to 37 based at least in part on information stored in the memory.
[0221] Aspect 39 is the apparatus of aspect 38, the apparatus further comprising at least one of an antenna or a transceiver coupled to the at least one processor.
[0222] Aspect 40 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 37.
[0223] Aspect 41 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 37.
Claims
1. A device for wireless communication at a user equipment (UE), the device include: Memory; and at least one processor coupled to the memory and, based at least in part on the information stored in the memory, configured to: receiving one or more frequency precompensation (FPC) commands from a non-terrestrial network (NTN) node; as well as and sending an uplink transmission with a frequency change in response to receiving the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on: a current UE location update and a current UE velocity update, wherein the total FPC adjustment satisfies one or more threshold requirements, or An intermediate UE position between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update.
2. The apparatus of claim 1 , wherein the intermediate UE position is weighted based on the current UE position update, the previous UE position update, and the time since the previous UE position update, and wherein the intermediate UE speed is weighted based on the current UE speed update, the previous UE speed update, and the time since the previous UE position update.
3. The apparatus of claim 1 , wherein the at least one processor is further configured to: In response to an FPC difference between the total FPC adjustment and the FPC adjustment value meeting or exceeding an FPC difference threshold, the total FPC adjustment is adjusted so that the FPC difference meets the one or more threshold requirements, wherein the total FPC adjustment is based on the current UE position update and the current UE speed update, and the FPC adjustment value is based on the previous UE position update and the previous UE speed update.
4. The apparatus of claim 3, wherein the total FPC adjustment is based on the current UE location update, the current UE speed update, the current NTN node location update, and the current NTN node speed update, wherein the FPC adjustment value is based on the previous UE location update, the previous UE speed update, the current NTN node location update, and the current NTN node speed update.
5. The apparatus of claim 3, wherein the one or more threshold requirements include at least one of the following: a maximum amplitude of the FPC difference in a single adjustment sent on the uplink that does not exceed a first threshold; A minimum aggregate adjustment rate of the FPC difference and a first sum of the first set of FPC adjustments in the first time period that meets or exceeds a second threshold; or A maximum aggregate adjustment rate of the FPC difference and a second sum of a second set of FPC adjustments within a second time period meets or exceeds a third threshold.
6. The apparatus of claim 3, wherein the at least one processor is further configured to: In response to a subsequent FPC difference between a subsequent total FPC adjustment and the total FPC adjustment meeting or exceeding a subsequent FPC difference threshold, sending a subsequent uplink transmission with a subsequent frequency change, wherein the subsequent frequency change has the subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update, wherein the subsequent total FPC adjustment meets the one or more threshold requirements.
7. The apparatus of claim 6, wherein the subsequent total FPC adjustment is based on the subsequent UE location update, the subsequent UE speed update, a subsequent NTN node location update, and a subsequent NTN node speed update.
8. The apparatus of claim 6, wherein the one or more threshold requirements include at least one of the following: a maximum magnitude of the subsequent FPC difference in a single adjustment for the subsequent uplink transmission that does not exceed a first threshold; A minimum aggregate adjustment rate of the subsequent FPC difference and the first sum of the first set of FPC adjustments in the first time period that meets or exceeds a second threshold; or A maximum aggregate adjustment rate of the subsequent FPC difference and a second sum of a second set of FPC adjustments within a second time period meets or exceeds a third threshold.
9. The apparatus of claim 1 , wherein the at least one processor is further configured to: In response to a transmit frequency error value between the total FPC adjustment excluding the FPC adjustment based on the NTN node position update and the NTN node speed update and a reference frequency exceeding a transmit frequency error threshold, adjusting the total FPC adjustment so that the transmit frequency error value meets the one or more threshold requirements.
10. The apparatus of claim 9, wherein the one or more threshold requirements include at least one of the following: a maximum magnitude of the transmission frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node position update and the NTN node speed update that does not exceed a first threshold; a minimum aggregate adjustment rate of the transmitted frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first sum of a first set of FPC adjustments other than the FPC adjustment based on the NTN node location update and the NTN node speed update within a first time period that meets or exceeds a second threshold, or a maximum aggregate adjustment rate of the transmitted frequency error value excluding the FPC adjustment based on the NTN node location update and the NTN node speed update and a second sum of a second set of FPC adjustments within a second time period excluding the FPC adjustment based on the NTN node location update and the NTN node speed update that meets or exceeds a third threshold.
11. The apparatus of claim 9, wherein the overall FPC adjustment is based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +F DL *(f UL / f DL ), where F FPC_CLOSED includes the closed-loop FPC value received from the NTN node, F FPC_OPEN including an open-loop FPC value based on the current UE location update, the current UE speed update, the NTN node location update, and the NTN node speed update, F FPC_OFFSET Including fixed offset, F DL comprising a first center frequency of a transmission received from said NTN node, f UL includes the second center frequency of the ideal uplink transmission, and f DL Includes a third center frequency for ideal downlink transmission.
12. The apparatus of claim 1, wherein the overall FPC adjustment is based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET , where F FPC_CLOSED includes the closed-loop FPC value received from the NTN node, F FPC_OPEN including an open-loop FPC value based on the current UE location update, the current UE speed update, the NTN node location update, and the NTN node speed update, and F FPC_OFFSET Includes fixed offset.
13. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein to receive the one or more FPC commands from the NTN node, the at least one processor is further configured to: The one or more FPC commands are received from the NTN node via the transceiver.
14. An apparatus for wireless communication at a non-terrestrial network (NTN) node, the apparatus include: Memory; and at least one processor coupled to the memory and, based at least in part on the information stored in the memory, configured to: sending one or more frequency precompensation (FPC) commands to a user equipment (UE); and In response to sending the one or more FPC commands, an uplink transmission with a frequency change is received, the frequency change having a total FPC adjustment calculated based on: a current UE location update and a current UE velocity update, wherein the total FPC adjustment satisfies one or more threshold requirements, or An intermediate UE position between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update.
15. The apparatus of claim 14, wherein the intermediate UE position is weighted based on the current UE position update, the previous UE position update, and the time since the previous UE position update, wherein the intermediate UE speed is weighted based on the current UE speed update, the previous UE speed update, and the time since the previous UE position update.
16. An apparatus according to claim 14, wherein the total FPC adjustment is adjusted so that an FPC difference between the total FPC adjustment and an FPC adjustment value satisfies the one or more threshold requirements, wherein the total FPC adjustment is based on the current UE position update and the current UE speed update, and the FPC adjustment value is based on the previous UE position update and the previous UE speed update.
17. The apparatus of claim 16, wherein the total FPC adjustment is based on the current UE location update, the current UE speed update, the current NTN node location update, and the current NTN node speed update, wherein the FPC adjustment value is based on the previous UE location update, the previous UE speed update, the current NTN node location update, and the current NTN node speed update.
18. The apparatus of claim 16, wherein the one or more threshold requirements include at least one of the following: a maximum amplitude of the FPC difference in a single adjustment sent on the uplink that does not exceed a first threshold; A minimum aggregate adjustment rate of the FPC difference and a first sum of the first set of FPC adjustments in the first time period that meets or exceeds a second threshold; or A maximum aggregate adjustment rate of the FPC difference and a second sum of a second set of FPC adjustments within a second time period meets or exceeds a third threshold.
19. The apparatus of claim 16, wherein the at least one processor is further configured to: A subsequent uplink transmission is received with a subsequent frequency change with a subsequent total FPC adjustment calculated based on a subsequent UE location update and a subsequent UE speed update, wherein the subsequent total FPC adjustment satisfies the one or more threshold requirements.
20. The apparatus of claim 19, wherein the subsequent total FPC adjustment is based on the subsequent UE location update, the subsequent UE speed update, a subsequent NTN node location update, and a subsequent NTN node speed update.
21. The apparatus of claim 19, wherein the one or more threshold requirements include at least one of the following: a maximum magnitude of subsequent FPC differences in a single adjustment for the subsequent uplink transmission that does not exceed a first threshold; A minimum aggregate adjustment rate of the subsequent FPC difference and the first sum of the first set of FPC adjustments in the first time period that meets or exceeds a second threshold; or A maximum aggregate adjustment rate of the subsequent FPC difference and a second sum of a second set of FPC adjustments within a second time period meets or exceeds a third threshold.
22. The apparatus of claim 14, wherein the overall FPC adjustment is adjusted so that a transmit frequency error value satisfies the one or more threshold requirements.
23. The apparatus of claim 22, wherein the one or more threshold requirements include at least one of the following: a maximum magnitude of the transmission frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node position update and the NTN node speed update, which does not exceed a first threshold; a minimum aggregate adjustment rate of the transmitted frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first sum of a first set of FPC adjustments other than the FPC adjustment based on the NTN node location update and the NTN node speed update within a first time period that meets or exceeds a second threshold, or a maximum aggregate adjustment rate of the transmitted frequency error value excluding the FPC adjustment based on the NTN node location update and the NTN node speed update and a second sum of a second set of FPC adjustments within a second time period excluding the FPC adjustment based on the NTN node location update and the NTN node speed update that meets or exceeds a third threshold.
24. The apparatus of claim 22, wherein the overall FPC adjustment is based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET +F DL *(f UL / f DL ), where F FPC_CLOSED includes the closed-loop FPC value received from the NTN node, F FPC_OPEN including an open-loop FPC value based on the current UE location update, the current UE speed update, the NTN node location update, and the NTN node speed update, F FPCOFFSET Including fixed offset, F DL comprising a first center frequency of a transmission received from said NTN node, f UL includes the second center frequency of the ideal uplink transmission, and f DL Includes a third center frequency for ideal downlink transmission.
25. The apparatus of claim 14, wherein the overall FPC adjustment is based on F FPC_CLOSED +F FPC_OPEN +F FPC_OFFSET , where F FPC_CLOSED includes the closed-loop FPC value received from the NTN node, F FPC_OPEN including an open-loop FPC value based on the current UE location update, the current UE speed update, the NTN node location update, and the NTN node speed update, and F FPC_OFFSET Includes fixed offset.
26. The apparatus of claim 14, further comprising a transceiver coupled to the at least one processor, wherein to send the one or more FPC commands to the UE, the at least one processor is further configured to: The one or more FPC commands are sent to the UE via the transceiver.
27. A method for wireless communication at a user equipment (UE), the method include: receiving one or more frequency precompensation (FPC) commands from a non-terrestrial network (NTN) node; as well as and sending an uplink transmission with a frequency change in response to receiving the one or more FPC commands, the frequency change having a total FPC adjustment calculated based on: a current UE location update and a current UE velocity update, wherein the total FPC adjustment satisfies one or more threshold requirements, or An intermediate UE position between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update.
28. The method according to claim 27, further comprising: include: In response to a transmit frequency error value between the total FPC adjustment other than the FPC adjustment based on the NTN node position update and the NTN node speed update and a reference frequency exceeding a transmit frequency error threshold, adjusting the total FPC adjustment so that the transmit frequency error value meets the one or more threshold requirements, wherein the one or more threshold requirements include at least one of the following: a maximum magnitude of the transmission frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node position update and the NTN node speed update that does not exceed a first threshold, a minimum aggregate adjustment rate of the transmitted frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first sum of a first set of FPC adjustments other than the FPC adjustment based on the NTN node location update and the NTN node speed update within a first time period that meets or exceeds a second threshold, or a maximum aggregate adjustment rate of the transmitted frequency error value excluding the FPC adjustment based on the NTN node location update and the NTN node speed update and a second sum of a second set of FPC adjustments within a second time period excluding the FPC adjustment based on the NTN node location update and the NTN node speed update that meets or exceeds a third threshold.
29. A method for wireless communication at a non-terrestrial network (NTN) node, the method include: sending one or more frequency precompensation (FPC) commands to a user equipment (UE); as well as In response to sending the one or more FPC commands, an uplink transmission with a frequency change is received, the frequency change having a total FPC adjustment calculated based on: a current UE location update and a current UE velocity update, wherein the total FPC adjustment satisfies one or more threshold requirements, or An intermediate UE position between the current UE location update and a previous UE location update and an intermediate UE speed between the current UE speed update and a previous UE speed update.
30. The method of claim 29, wherein the total FPC adjustment is adjusted so that the transmit frequency error value meets the one or more threshold requirements, wherein the one or more threshold requirements include at least one of the following: a maximum magnitude of the transmission frequency error value in a single adjustment for the uplink transmission other than the FPC adjustment based on the NTN node position update and the NTN node speed update, which does not exceed a first threshold; a minimum aggregate adjustment rate of the transmitted frequency error value other than the FPC adjustment based on the NTN node location update and the NTN node speed update and a first sum of a first set of FPC adjustments other than the FPC adjustment based on the NTN node location update and the NTN node speed update within a first time period that meets or exceeds a second threshold, or a maximum aggregate adjustment rate of the transmitted frequency error value excluding the FPC adjustment based on the NTN node location update and the NTN node speed update and a second sum of a second set of FPC adjustments within a second time period excluding the FPC adjustment based on the NTN node location update and the NTN node speed update that meets or exceeds a third threshold.
Citation Information
Patent Citations
Gradual frequency adjustment for dual-loop frequency control in NTN based on user equipment requirements
US20230336212A1
