User equipment positioning based on non-terrestrial communication network
By using Doppler measurement and range measurement in non-terrestrial networks, combining multiple backhaul time measurement and positioning session scheduling, the problem of low UE positioning accuracy in non-terrestrial networks is solved, and more accurate position calculation is achieved.
Patent Information
- Application Number
- CN202380034341.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-22
- Filing Date
- 2023-03-07
- Publication Date
- 2024-11-26
AI Technical Summary
In satellite-based wireless communication systems, it is difficult for the prior art to accurately locate user equipment (UEs) in non-terrestrial network environments, especially within a single satellite line of sight, to have problems of positioning errors and cross-orbit errors.
By using Doppler measurement and range measurement in non-terrestrial networks (NTNs), combining Doppler measurement information element (IE) and multiple backhaul time measurement information element (NR-Multi-RTT-SignalMeasurementInformation IE), and scheduling multiple The session is positioned to ensure that the UE is away from the suborbital of the satellite to calculate the position of the UE.
The positioning accuracy of UEs in non-terrestrial network environments is improved, positioning errors caused by single satellite line of sight and sub-orbital positions are reduced, and the accuracy of position calculation is enhanced.
Smart Images

Figure CN119032291A_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of U.S. Application No. 17 / 726,919, filed on April 22, 2022, entitled “USER EQUIPMENT POSITIONING BASED ON A NON-TERRESTRIAL COMMUNICATION NETWORK,” which is assigned to the assignee of this application and is incorporated herein by reference in its entirety. Background Art Technical Field
[0003]
[0013] Various aspects described herein relate generally to wireless communication systems, and more particularly to positioning using at least one communication satellite.
[0004] Related technical description
[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include several base stations or network access nodes, each of which simultaneously supports communication of multiple communication devices (which may each be referred to as user equipment (UE) in other aspects).
[0006] Standardization is underway to combine satellite-based communication systems with terrestrial wireless communication systems, such as 5G New Radio (NR) networks. In such systems, a UE would access a satellite (also referred to as a space vehicle (SV)), which would connect to an earth station (also referred to as a ground station or non-terrestrial network (NTN) gateway), which in turn would connect to a 5G network (e.g., directly or via a base station). The 5G network may treat the satellite system as another type of radio access technology (RAT), which is different from but similar to terrestrial 5G NR. UE positioning may also be performed using a 5G (or other suitable wireless communication) network, for which a location server in the wireless network may determine the location of the UE in the wireless network based on properties of communications to and from the UE. Summary of the invention
[0007] Techniques for supporting non-terrestrial network (NTN) based positioning for user equipment (UE) are described. Specifically, implementations for range and range rate based UE positioning using NTN are described so that UE positioning can be performed based on visibility of at least one NTN satellite to the UE. Measurements of range (such as based on receive (rx)-transmit (tx) time differences of signals) and range rate (also referred to as Doppler measurements) can be based on two or more reference signals (RS) to or from the UE. Means for reporting such measurements are also described, which may include bundling Doppler measurements with UE time difference reports. Means for mitigating positioning errors that may occur based on UE positioning using a single NTN satellite are also described.
[0008] In some aspects, an example method performed by a device for performing NTN-based positioning is described. The method includes receiving a first reference signal (RS) from a first device. The first RS is one of a positioning reference signal (PRS) from a base station (BS) or a sounding reference signal (SRS) from a user equipment (UE). The method also includes receiving a second RS from the first device. The second RS is associated with the first RS. The method also includes calculating a Doppler measurement based on one or both of the first RS or the second RS. The method also includes reporting the Doppler measurement. The Doppler measurement is to be used to calculate the positioning of the UE.
[0009] In some implementations, when the second RS is not bound to the first RS, only the second RS is used to calculate the Doppler measurement. In some other implementations, the second RS is bound to the first RS. Binding the second RS to the first RS includes maintaining phase coherence between the first RS and the second RS, and calculating the Doppler measurement based on both the first RS and the second RS. In some implementations, the method also includes reporting whether the UE uses the same local oscillator (LO) for receiving and transmitting. Calculating the range change rate is based on whether the UE uses the same LO for both receiving and transmitting. In some implementations, reporting the Doppler measurement includes reporting the Doppler measurement in an NR-Doppler-SignalMeasurementInformation information element (IE) or reporting one of the Doppler measurements in an NR-Multi-RTT-SignalMeasurementInformation IE.
[0010] In some other aspects, a device for performing NTN-based positioning is described. The device includes: a wireless transceiver configured to wirelessly communicate with one or more network devices; at least one memory; and at least one processor coupled to the wireless transceiver and the at least one memory. The at least one processor is configured to receive a first RS from a first device via the wireless transceiver. The first RS is one of a PRS from a BS or an SRS from a UE. The at least one processor is also configured to receive a second RS from the first device via the wireless transceiver. The second RS is associated with the first RS. The at least one processor is further configured to calculate a Doppler measurement based on one or both of the first RS or the second RS. The at least one processor is also configured to report the Doppler measurement. The Doppler measurement is to be used to calculate the positioning of the UE.
[0011] In some embodiments, when the second RS is not bound to the first RS, only the second RS is used to calculate the Doppler measurement. In some other embodiments, the second RS is bound to the first RS. Binding the second RS to the first RS includes maintaining phase coherence between the first RS and the second RS, and calculating the Doppler measurement based on both the first RS and the second RS. In some embodiments, the at least one processor is also configured to report whether the UE uses the same local oscillator (LO) for receiving and transmitting. The range change rate is calculated based on whether the UE uses the same LO for both receiving and transmitting. In some embodiments, reporting the Doppler measurement includes reporting the Doppler measurement in an NR-Doppler-SignalMeasurementInformation information element (IE) or reporting one of the Doppler measurements in an NR-Multi-RTT-SignalMeasurementInformation IE.
[0012] In some additional aspects, another example method performed by a device for performing NTN-based positioning is described. The method includes performing multiple positioning sessions associated with a user equipment (UE) and a satellite of the NTN. The positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning session. The method also includes reporting results from the positioning sessions. The results are to be used to calculate the positioning of the UE. In some specific implementations, the method also includes obtaining an altitude of the UE and reporting the altitude of the UE. The altitude is to be used to calculate the positioning of the UE.
[0013] In some other aspects, another example device for performing NTN-based positioning is described. The device includes: a wireless transceiver configured to wirelessly communicate with one or more network devices; at least one memory; and at least one processor coupled to the wireless transceiver and the at least one memory. The at least one processor is configured to perform multiple positioning sessions associated with a UE and a satellite of the NTN. The positioning session is scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning session. The at least one processor is also configured to report results from the positioning session. The results are to be used to calculate the positioning of the UE. In some specific implementations, the at least one processor is also configured to obtain the altitude of the UE and report the altitude of the UE. The altitude is to be used to calculate the positioning of the UE. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 A diagram of a communication system using a network architecture with a transparent space vehicle (SV) that can support satellite access to a wireless network is shown.
[0015] Figure 2 A diagram of a communication system using a network architecture with regenerative SVs that can support satellite access to a wireless network is shown.
[0016] Figure 3 A diagram of a communication system using a network architecture with regenerative SVs and a split-Satellite Node B (gNB) architecture that is capable of supporting satellite access to a wireless network.
[0017] Figure 4 Example positioning measurements calculated in a non-terrestrial network (NTN) that may be used to calculate the position of a UE in communication with a SV are illustrated.
[0018] Figure 5 is a diagram illustrating an example of a hardware implementation of a UE configured to support NTN-based UE positioning.
[0019] Figure 6 is a diagram illustrating an example of a hardware implementation of a base station configured to support NTN-based UE positioning.
[0020] Figure 7 A flow chart of an example process for performing NTN-based UE positioning is shown.
[0021] Figure 8 is a frequency diagram of example frequency offsets of reference signals measured on the downlink (DL) and frequency offsets of reference signals measured on the uplink (UL).
[0022] Fig. 9A flow chart of an example process for a device to perform NTN-based UE positioning based on multiple positioning sessions is shown.
[0023] Similar reference numerals in the various figures indicate similar elements according to certain example implementations. In addition, multiple instances of an element may be indicated by adding a letter or hyphen and a second numeral after the first numeral of the element. For example, multiple instances of element 102 may be indicated as 102-1, 102-2, 102-3, etc. When only the first numeral is used to refer to such an element, it will be understood as any instance of the element (e.g., element 102 in the previous example will refer to elements 102-1, 102-2, 102-3). DETAILED DESCRIPTION
[0024] Satellites (also referred to as space vehicles (SVs) or communication satellites) can be used in communication systems, for example, using a gateway and one or more satellites to relay communication signals between the gateway and one or more user equipments (UEs). For example, a UE may access a non-terrestrial network (NTN) satellite (instead of a ground base station), which may be connected to an earth station (ES), which is also referred to as a ground station or NTN gateway. The earth station in turn will be connected to an element in the network, such as a modified base station or network node (without a ground antenna) in a core network (CN). This element in turn will provide access to other elements in the network and ultimately provide access to entities outside the network (such as Internet web servers and other user equipment).
[0025] The basic principle of satellite access of UE may include providing ubiquitous outdoor coverage for both users and mobile network operators (MNOs). For example, in many countries including the United States, unavailable or poor cellular network coverage is a common problem. In addition, even if there is generally good cellular coverage, cellular access is not always possible. For example, cellular access may be hindered by congestion, physical obstacles, local cellular outages caused by weather (e.g., hurricanes or tornadoes), or local power outages. Satellite access to cellular networks can provide a new independent access that is potentially available everywhere outdoors. Current satellite-enabled phones for low earth orbit (LEO) SVs may have similar sizes to cellular smartphones, and thus mobile new radio (NR) support using satellite-enabled phones does not require a significant increase in phone size. In addition, satellite-enabled smartphones may help drive mobile phone sales and may increase operator revenues. For example, potential users may include anyone with limited or no cellular access, anyone who wants a backup for lack of cellular access, and anyone involved in public safety or otherwise requiring (almost) 100% reliable mobile communications. Additionally, some users may desire improved or more reliable emergency (eg, E911) services, for example, for medical emergencies or traffic breakdowns in remote areas.
[0026] The use of satellite access can provide other benefits. For example, satellite access can reduce mobile network operator (MNO) infrastructure costs. For example, MNOs can use satellite access to reduce ground base stations (such as NR B nodes, also known as gNBs) and backhaul deployment in sparsely populated areas. In addition, satellite access can be used to overcome Internet congestion in certain countries, for example. Additionally, satellite access can provide diversification for spacecraft operators (SVOs). For example, 5G NR satellite access can provide another revenue stream for SVOs that would otherwise provide fixed Internet access.
[0027] With TN, the third generation partnership project (3GPP) has defined a positioning service for UE in order to determine the positioning information of UE within the coverage area of TN (such as through a location server). In the case where wireless communication may be moved to NTN, it is expected that NTN also supports UE positioning. UE positioning in TN can be based on the triangulation of UE using signals from multiple base stations within the range of UE to and / or from UE. In addition, the communication between UE and satellite requires that the satellite is within the line of sight (LOS) of UE. For the communication between UE and NTN, in order to perform triangulation, a sufficient number of communication satellites in low earth orbit (LEO) may not be within the LOS of UE. For example, only one satellite may be within the LOS of UE. Therefore, performing UE positioning in NTN can be configured to be performed based on one satellite being within the LOS of UE. Positioning using a reference point (such as a satellite) can be based on Doppler measurements (also referred to as range change rate) and range (such as determined based on rx-tx time difference) measured according to the signal between satellite and UE. As described herein, various aspects of performing Doppler measurements and reporting Doppler measurements can be configured for UE and one or more base stations (BS).
[0066] As also described herein, aspects for reducing positioning errors based on UE positioning using one satellite may be configured for a UE and one or more satellites.
[0028] It should be noted that, although various aspects of the present disclosure are described with reference to a UE within an NTN, some aspects of the present disclosure may be performed for a UE within a TN. For example, although an example NTN is described and Doppler measurements are described as being generated and reported with reference to a UE communicating within the NTN, Doppler measurements may be performed between a UE and a ground BS, and Doppler measurements may be reported by the UE or the ground BS to a location server in the wireless network. As used herein, a base station (BS) may refer to one or more components of a satellite for an NTN, a ground BS for a TN, or an earth station for an NTN. A BS may include components distributed in one device or across multiple devices. Therefore, the term base station should not be limited to a particular type of device unless explicitly stated otherwise.
[0029] Figure 1 An example network architecture 100 is illustrated that can support satellite access using 5G New Radio (NR). Figure 1A network architecture with satellites that may be referred to as transparent space vehicles (SVs) is illustrated. A transparent SV may implement frequency conversion and radio frequency (RF) amplifiers in both uplink (UL) and downlink (DL) directions, and may correspond to an analog RF repeater. For example, a transparent SV may receive uplink (UL) signals from all served UEs, and may DL redirect the combined signal to an earth station without demodulating or decoding the signals. Similarly, a transparent SV may receive UL signals from an earth station and DL redirect the signal to a served UE without demodulating or decoding the signal. However, the SV may frequency convert the received signals, and may amplify and / or filter the received signals before transmitting them.
[0030] The network architecture 100 includes a number of UEs 105, a number of SVs 102-1 to 102-3 (collectively referred to herein as SVs 102), a number of non-terrestrial network (NTN) gateways 104-1 to 104-3 (collectively referred to herein as NTN gateways 104) (sometimes referred to herein simply as gateways 104, earth stations 104, or ground stations 104), and a number of NR B nodes (gNBs) 106-1 to 106-3 (collectively referred to herein as gNBs 106) that are capable of communicating with the UEs via the SVs 102 and are part of a next generation (NG) radio access network (RAN) (NG-RAN) 112. Note that the term gNB generally refers to an enhanced gNB with support for SVs and may be referred to as a gNB (e.g., in 3GPP) or may sometimes be referred to as a satellite B node (sNB). The network architecture 100 is illustrated as also including components of several fifth generation (5G) networks, including 5G core networks (5GCNs) 110 - 1 and 110 - 2 (collectively referred to herein as 5GCNs 110 ). Figure 1 The various components within 5GCN1 110-1 that may operate with NG-RAN 112 are illustrated. It should be understood that 5GCN2 110-2 and other 5GCNs may include the same, similar or different components and associated NG-RANs, and in order to avoid unnecessary confusion, the following descriptions are provided. Figure 1 5G networks may also be referred to as New Radio (NR) networks; NG-RAN 112 may be referred to as 5G RAN or NR RAN; and 5GCN 110 may be referred to as NG Core Network (NGC).
[0031] A base station may refer to one or more of an SV 102, an earth station 104, or a gNB 106. For example, a gNB 106 may be configured to provide a reference signal for transmission from the SV 102 to the UE 105 to measure Doppler and receive (rx)-transmit (tx) time difference (which is used to determine the range between the UE and the SV as the time difference multiplied by the speed of light). Additionally or alternatively, the UE 105 may be configured to provide a reference signal to the SV 102, from which the gNB 106 may measure the Doppler and rx-tx time difference. In this way, the SV 102 may be used for both communication operations and UE positioning operations. Additional components of the network architecture 100 are described below. Although in Figure 1 Some example components are depicted in FIG. 1 , but network architecture 100 may include additional or alternative components.
[0032] exist Figure 1 The connections permitted in the network architecture 100 illustrated in FIG. 1 having a network architecture with transparent SVs allow a gNB 106 to access multiple earth stations 104 and / or multiple SVs 102. A gNB 106 (e.g., as illustrated by gNB 106-3) may also be shared by multiple 5GCNs 110, and an earth station 104 (e.g., as illustrated by earth station 104-2) may be shared by more than one gNB 106.
[0033] It should be noted that Figure 1 Only generalized illustrations of the various components are provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only three UEs 105 are illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the network architecture 100. Similarly, the network architecture 100 may include a larger (or smaller) number of SVs 102, earth stations 104, gNBs 106, NG-RAN 112, 5GCN 110, external clients 140, and / or other components. The illustrated connections connecting the various components in the network architecture 100 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 according to the desired functionality.
[0034] Although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations may be used to support satellite wireless access (e.g., using SV 102) for other communication technologies such as 3G, 4G, Long Term Evolution (LTE), etc.
[0035] UE 105 may include and / or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a terminal (SET) with secure user plane location (SUPL) enabled, or some other name. In addition, UE 105 may correspond to a cellular phone, a smart phone, a laptop computer, a tablet, a PDA, a tracking device, a navigation device, an Internet of Things (IoT) device, or some other portable or portable device. Typically, but not necessarily, UE 105 may support wireless communications using one or more radio access technologies (RATs), such as using Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 112 and 5GCN 140), etc. UE 105 may also support wireless communications using a wireless local area network (WLAN), which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or packet cable. UE 105 further supports wireless communications using spacecraft such as SV 102. Using one or more of these RATs may allow UE 105 to communicate with external clients 140 (via non-resident clients of 5GCN 110). Figure 1 , or via a Gateway Mobile Location Center (GMLC) 126).
[0036] UE 105 may comprise a single entity or may comprise multiple entities, such as in a personal area network where a user may employ audio, video, and / or data I / O devices, and / or body sensors and separate wired or wireless modems.
[0037] The UE 105 may support positioning in the NTN using terrestrial positioning methods such as Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (ECID), Round Trip Signal Propagation Time (RTT), Multi-cell RTT, Angle of Arrival (AOA), Angle of Departure (AOD), Time of Arrival (TOA), Receive-Send Time Difference (Rx-Tx), Doppler measurements, and / or other positioning methods. Although not depicted, the UE 105 may also support position determination using signals and information from SVs in a Standard Positioning Service (SPS) such as GPS, GLONASS, Galileo, or BeiDou or some other local or regional SPS such as IRNSS, EGNOS, or WAAS, all of which may be generally referred to herein as GNSS.
[0038] The estimate of the position of the UE 105 may be referred to as a geodetic position, position, position estimate, position fix, fix, position fix, position estimate, or position fix, and may be geographic, thereby providing position coordinates (e.g., latitude and longitude) about the UE 105, which may or may not include an altitude component (e.g., altitude; height above or depth below ground level, floor level, or basement level). The altitude component may be referred to as height. The position of the UE 105 may also be expressed as an area or volume in which the UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The position of the UE 105 may also be a relative position, including, for example, a distance and direction defined relative to a certain origin at a known position or relative X, Y (and Z) coordinates, which may be defined geographically or by reference to a point, area, or volume indicated on a map, floor plan, or building plan. Unless otherwise noted, the use of the term position or position fix in the description contained herein may include any of these variants. In calculating the position of the UE, local x, y, and possibly z coordinates are typically solved for, and then converted to absolute coordinates (eg, for latitude, longitude, and altitude above or below mean sea level) if necessary.
[0039] UE 105 is configured to communicate with 5GCN 110 via SV 102, earth station 104 and gNB 106. As illustrated by NG-RAN 112, the NG-RAN associated with 5GCN 110 may include one or more gNBs 106. NG-RAN 112 may also include several ground base stations, such as gNBs (not shown), that cannot communicate with UE via SV 102 (not shown). Paired ground and / or satellite base stations (e.g., gNBs and gNB 106-1 in NG-RAN 112) may be connected to each other using ground links (e.g., directly or indirectly via other gNBs or gNB 106) and communicate using an Xn interface. Access to the 5G network is provided to UE 105 via wireless communications between each UE 105 and the serving gNB 106, via SV 102 and earth station 104. The gNB 106 may use 5G NR to provide wireless communication access to the 5GCN 110 on behalf of each UE 105. 5G NR radio access may also be referred to as NR radio access or 5G radio access and may be defined by the Third Generation Partnership Project (3GPP).
[0040] Figure 1The base stations (BSs) in the NG-RAN 112 shown in FIG. 1 may also additionally or alternatively include next generation evolved Node Bs (also referred to as ng-eNBs). The ng-eNBs may be connected to one or more gNBs 106 and / or gNBs in the NG-RAN 112 (e.g., directly or indirectly via other gNBs 106, gNBs, and / or other ng-eNBs). The ng-eNBs may provide LTE wireless access and / or evolved LTE (eLTE) wireless access to the UE 105.
[0041] The gNB 106 may be referred to by other names, such as gNB or "satellite node" or "satellite access node". The gNB 106 is distinct from a terrestrial gNB, but may be based on a terrestrial gNB with additional capabilities. For example, the gNB 106 may terminate at a radio interface and associated radio interface protocol to the UE 105, and may send DL signals to the UE 105 and receive UL signals from the UE 105 via the SV 102 and the earth station (ES) 104. The gNB 106 may also support signaling connections and voice and data bearers to the UE 105, and may support handover of the UE 105 between different radio cells of the same SV 102, between different SVs 102, and / or between different gNBs 106. In some systems, the gNB 106 may be referred to as a gNB or an enhanced gNB. The gNBs 106 may be configured to manage mobile radio beams (for LEO SVs) and the associated mobility of the UE 105. The gNB 106 may assist in the handover (or transfer) of the SV 102 between different earth stations 104, between different gNBs 106, and between different countries. The gNB 106 may hide or shield certain aspects of the connected SV 102 from the 5GCN 110, for example, by interfacing with the 5GCN 110 in the same or similar manner as a terrestrial gNB, and may avoid the 5GCN 110 having to maintain configuration information about the SV 102 or perform mobility management related to the SV 102. The gNB 106 may further assist in sharing the SV 102 over multiple countries. The gNB 106 may communicate with one or more earth stations 104, for example, as illustrated by the gNB 106-3 communicating with earth stations 104-2 and 104-3. The gNB 106 may be separate from the earth station 104. Alternatively, the gNB 106 may include one or more earth stations 104 or may be combined with the one or more earth stations, for example using a split architecture. For example, where a split architecture is used, the gNB 106 may include a central unit and the earth station may act as a distributed unit (DU). The gNB 106 may typically be fixed on the ground using transparent SV operation. In one implementation, one gNB 106 may be physically combined with one earth station 104 or may be physically connected to the one earth station to reduce complexity and cost.
[0042] The earth station 104 may be shared by more than one gNB 106 and may communicate with the UE 105 via the SV 102. The earth station 104 may be included within the gNB 106, for example, as a gNB-DU within the gNB 106. The earth station 104 may communicate with the SV 102 using control plane and user plane protocols. The control and user plane protocols between the earth station 104 and the SV 102 may: (i) establish and release the communication link from the earth station 104 to the SV 102, including authentication and encryption; (ii) update the SV software and firmware; (iii) perform SV operations and maintenance (O and M); (iv) control radio beams (e.g., direction, power, on / off state) and mapping between radio beams and earth station uplink (UL) and downlink (DL) payloads; and (v) assist in handover of an SV 102 or radio cell to another earth station 104.
[0043] As mentioned, although Figure 1 Nodes configured to communicate according to a 5G NR communication protocol for NG-RAN 112 are depicted, but nodes configured to communicate according to other communication protocols such as, for example, an LTE protocol for an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Narrowband Internet of Things (NB-IoT) protocol for E-UTRAN supporting low bandwidth access using an LTE variant, or an IEEE 802.11x protocol for WLAN may also be used. For example, in a 4G Evolved Packet System (EPS) providing LTE wireless access to UE 105, the RAN may include an E-UTRAN, which may include base stations having evolved Node Bs (eNBs) supporting LTE wireless access. The core network for the EPS may include an Evolved Packet Core (EPC). The EPS may then include the E-UTRAN plus the EPC, where the UE 105 is a 4G Evolved Packet System (EPS). Figure 1 In the embodiment, E-UTRAN corresponds to NG-RAN 112 and EPC corresponds to 5GCN 110. The methods and techniques described herein for supporting fixed TA may be applicable to such other networks.
[0044] The gNB 106 in the NG-RAN 112 may communicate with a 5G core access and mobility management function (AMF) 122 in the 5GCN 110, which may communicate with a location management function (LMF) 124 for positioning functionality. It should be noted that the LMF 124 may be implemented as at least one location server that performs operations to identify the location of the UE within the coverage area of the wireless network or otherwise support UE positioning. In some specific implementations, the gNB 106 may provide an N2 interface to the AMF 122. The N2 interface between the gNB 106 and the 5GCN 110 may be the same or similar to the N2 interface supported between the terrestrial gNB and the 5GCN 110 for terrestrial NR access by the UE 105, and the Next Generation Application Protocol (NGAP) defined in 3GPP Technical Specification (TS) 38.413 may be used between the gNB 106 and the AMF 122. The AMF 122 may support mobility of the UE 105, including radio cell changes and handovers, and may participate in supporting signaling connections to the UE 105 and possibly data and voice bearers for the UE 105. The LMF 124 may support positioning of the UE 105 when the UE accesses the NG-RAN 112, and may support positioning procedures / methods such as A-GNSS, OTDOA, RTK, PPP, DGNSS, ECID, AOA, AOD, multi-cell RTT, Doppler measurements, and / or other positioning procedures including positioning procedures based on communication signals from one or more SVs 102. The LMF 124 may also process location service requests for the UE 105 received, for example, from the AMF 122 or from a Gateway Mobile Location Center (GMLC) 126. The LMF 124 may be connected to the AMF 122 and / or the GMLC 126. In some embodiments, a node / system implementing LMF 124 may additionally or alternatively implement other types of location support modules, such as an enhanced serving mobile location center (E-SMLC). Note that in some embodiments, at least a portion of the positioning functionality (including the derivation of the location of UE 105) may be performed at UE 105 (e.g., using signal measurements obtained by UE 105 for signals sent by SV 102 or gNB, and assistance data provided to UE 105, for example, by LMF 124). Additionally or alternatively, at least a portion of the positioning functionality may be performed at a base station (such as a gNB using, for example, signal measurements calculated based on RS sent by UE 105 to SV 102, where RS is defined by, for example, LMF 124).
[0045] GMLC 126 may support location requests for UE 105 received from external client 140, and may forward such location requests to AMF 122 for forwarding by AMF 122 to LMF 124. A location response from LMF 124 (e.g., including a location estimate for UE 105) may similarly be returned to GMLC 126 via AMF 122, and GMLC 126 may then return the location response (e.g., including the location estimate) to external client 140. GMLC 126 may forward such location requests to AMF 122 for forwarding by AMF 122 to LMF 124. Figure 1 124, although in some implementations, may be connected to both AMF 122 and LMF 124, and may support direct communication between GMLC 126 and LMF 124 or indirect communication, for example via AMF 122.
[0046] A network opening function (NEF) 128 may be included in the 5GCN 110, for example connected to the GMLC 126 and the AMF 122. In some implementations, the NEF 128 may be connected to communicate directly with the external client 140. The NEF 128 may support secure opening of capabilities and events about the 5GCN 110 and the UE 105 to the external client 140 and may enable secure provisioning of information from the external client 140 to the 5GCN 110.
[0047] The user plane function (UPF) 130 may support voice and data bearers for the UE 105 and may enable the UE 105 to have voice and data access to other networks, such as the Internet. The UPF 130 may be connected to the gNB 106 and the gNB. The UPF 130 functions may include: external protocol data unit (PDU) session interconnection points to the data network, packet (e.g., Internet Protocol (IP)) routing and forwarding, user plane portion of packet inspection and policy rule enforcement, quality of service (QoS) handling of the user plane, downlink packet buffering, and downlink data notification triggering. The UPF 130 may be connected to a secure user plane location (SUPL) location platform (SLP) 132 to implement support for locating the UE 105 using SUPL. The SLP 132 may also be connected to or accessible from an external client 140.
[0048] As illustrated, a session management function (SMF) 134 is connected to the AMF 122 and the UPF 130. The SMF 134 may have the ability to control local and central UPFs within a PDU session. The SMF 134 may manage the establishment, modification, and release of PDU sessions for the UE 105, perform IP address allocation and management for the UE 105, act as a Dynamic Host Configuration Protocol (DHCP) server for the UE 105, and select and control the UPF 130 on behalf of the UE 105.
[0049] The external client 140 may connect to the core network 110 via the GMLC 126 and / or the SLP 132, and in some implementations via the NEF 128. The external client 140 may optionally connect to the core network 110 and / or to a location server via the Internet, which may be, for example, an SLP external to the 5GCN 110. The external client 140 may directly ( Figure 1 The external client 140 may be a server, a web server, or a user device such as a personal computer, a UE, etc.
[0050] A location retrieval function (LRF) 125 may be connected to the GMLC 126, as illustrated, and in some implementations, may be connected to the SLP 132, as defined in 3GPP Technical Specification (TS) 23.167. With respect to receiving and responding to location requests from external clients 140, the LRF 125 may perform the same or similar functions as the GMLC 126, which corresponds to a public safety answering point (PSAP) supporting emergency calls from the UE 105. One or more of the GMLC 126, the LRF 125, and the SLP 132 may be connected to the external client 140, for example, via another network, such as the Internet.
[0051] The AMF 122 may generally support network access and registration by the UE 105, mobility of the UE 105 (including radio cell changes and handovers), and may participate in supporting signaling connections to the UE 105 and possibly data and voice bearers for the UE 105. The role of the AMF 122 may be to register the UE during a registration procedure. The AMF 122 may page the UE 105, for example, by transmitting a paging message via one or more radio cells in a tracking area in which the UE 105 is located.
[0052] As mentioned, although the network architecture 100 is described with respect to 5G technology, the network architecture 100 may be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) for supporting and interacting with mobile devices such as UE 105 (e.g., to implement voice, data, positioning, and other functionality). In some such embodiments, the 5GCN 110 may be configured to control different air interfaces. For example, in some embodiments, the non-3GPP interworking function (N3IWF, Figure 1 105) connects 5GCN 110 to WLAN. For example, WLAN may support IEEE 802.11 WiFi access for UE 105 and may include one or more WiFi APs. Here, N3IWF may connect to WLAN and other elements in 5GCN 110, such as AMF 122.
[0053] In the case where the network 100 supports positioning services for the UE 105, in some implementations, the RS may be sent from the UE 105 to the SV 102 on the uplink (UL). For example, the UE 105 may send one or more sounding reference signals (SRS) and / or one or more other RFs, and the gNB 106 may use the RS to measure range and Doppler (or other positioning measurements). The gNB 106 may report the positioning measurements to the LMF 124, and the LMF 124 may use the positioning measurements to calculate the positioning of the UE 105. Additionally or alternatively, the RS may be defined by the LMF 124, configured by the gNB 106, and sent from the SV 102 to the UE 105 on the downlink (DL). The UE 105 may use the RS to measure range and Doppler (or other positioning measurements). UE 105 may report positioning measurements (such as via SV 102, earth station 104, and gNB 106) to LMF 124, and LMF 124 may use the positioning measurements to calculate the positioning of UE 105.
[0054] Figure 2 A diagram of a network architecture 200 capable of supporting satellite access using 5G New Radio (NR) is shown. Figure 2 The network architecture shown in is similar to Figure 1 , where similarly designated elements are similar or identical. Figure 1 In contrast to the transparent SV 102 shown in FIG. Figure 2A network architecture with regeneration SVs 202-1, 202-2, and 202-3 (collectively referred to as SVs 202) is illustrated. Unlike transparent SVs 102, regeneration SVs 202 include an onboard gNB 202 (e.g., include functional capabilities of a gNB) and are sometimes referred to herein as SVs / gNBs 202. NG-RAN 112 is illustrated as including SVs / gNBs 202. Reference to gNBs 202 is used herein when referencing SV / gNB 202 functionality related to communications with UEs 105 and 5GCN 110, and reference to SVs 202 is used when referencing SV / gNB 202 functionality related to communications with earth stations 104 and UEs 105 at a physical radio frequency level. However, there may not be a precise boundary between SVs 202 and gNBs 202. In some implementations, regeneration SVs 202 or gNBs 202 may be referred to as base stations.
[0055] The onboard gNB 202 may perform many of the same functions as the gNB 106 as previously described. For example, the gNB 202 may terminate at a radio interface and associated radio interface protocol to the UE 105, and may send DL signals to the UE 105 and receive UL signals from the UE 105, which may include encoding and modulation of the transmitted signals and demodulation and decoding of the received signals. The gNB 202 may also support signaling connections to the UE 105 and voice and data bearers, and may support handover of the UE 105 between different radio cells of the same gNB 202, and between different gNBs 202. The gNB 202 may assist in the handover (or transfer) of the SV 202 between different earth stations 104 or between different 5GCNs 110. The gNB 202 may hide or obscure certain aspects of the SV 202 from the 5GCN 110, for example, by interfacing with the 5GCN 110 in the same or similar manner as a terrestrial gNB. The gNB 202 may communicate with one or more earth stations 104 and, via the earth stations 104, with one or more 5GCNs 110. In some implementations, the gNB 202 may use an inter-satellite link (ISL) ( Figure 2 (not shown) communicates directly with other gNB 202, and ISL can support the Xn interface between any pair of gNB 202.
[0056] In the case where the network 200 supports positioning services for the UE 105, in some implementations, the RS may be sent from the UE 105 to the SV 202 on the uplink (UL). For example, the UE 105 may send one or more sounding reference signals (SRS) and / or one or more other RFs, and the SV 202 may use the RS to measure range and Doppler (or other positioning measurements). The SV 202 may report the positioning measurements to the LMF 124 via the earth station 104, and the LMF 124 may use the positioning measurements to calculate the positioning of the UE 105. Additionally or alternatively, the RS may be defined by the LMF 124 and sent from the SV 202 to the UE 105 on the downlink (DL). The UE 105 may use the RS to measure range and Doppler (or other positioning measurements). The UE 105 may report the positioning measurements to the LMF 124 (such as via the SV 202 and the earth station 104), and the LMF 124 may use the positioning measurements to calculate the positioning of the UE 105.
[0057] Figure 3 A diagram of a network architecture 300 capable of supporting satellite access using 5G New Radio (NR) is shown. Figure 3 The network architecture shown in is similar to Figure 1 and Figure 2 , where similarly designated elements are similar or identical. Figure 1 In contrast to the transparent SV 102 of the split architecture shown in and using gNB, Figure 3 A network architecture with regenerative SVs 302-1, 302-2, and 302-3 (collectively referred to as SVs 302) is illustrated. The gNB 307 includes a central unit (CU) and may sometimes be referred to as a gNB-CU 307, and unlike the transparent SV 102, the regenerative SV 302 includes an onboard gNB distributed unit (gNB-DU) 302 and is sometimes referred to herein as a SV / gNB-DU 302. References to the gNB-DU 302 are used herein when referencing SV / gNB 302 functionality related to communication with the UE 105 and the gNB-CU 307, and references to the SV 302 are used when referencing SV / gNB-DU 302 functionality related to communication with the earth station 104 and the UE 105 at the physical radio frequency level. However, there may not be a precise boundary for the SV 302 relative to the gNB-DU 302.
[0058] Each gNB-DU 302 communicates with a ground-based gNB-CU 307 via one or more earth stations 104. A gNB-CU 307, together with one or more gNB-DUs 302 in communication with the gNB-CU 307, performs functions and may use internal communication protocols similar to or the same as the terrestrial gNB using a split architecture described in 3GPP TS 38.401. Here, the gNB distributed unit (gNB-DU) 302 corresponds to and performs similar or the same functions as the terrestrial gNB-DU defined in TS 38.401, and the gNB central unit (gNB-CU) 307 corresponds to and performs similar or the same functions as the terrestrial gNB-CU defined in TS 38.401. For example, the gNB-DU 302 and the gNB-CU 307 may communicate with each other using the F1 Application Protocol (F1AP) defined in 3GPP TS 38.473, and may together perform some or all of the same functions as the gNB 106 or gNB 202 as previously described. To simplify references to different types of gNBs in the following description, the gNB-DU 302 may sometimes be referred to as gNB 302 (without the "DU" tag), and the gNB-CU 307 may sometimes be referred to as gNB 307 (without the "CU" tag).
[0059] The gNB-DU 302 may terminate at the radio interface to the UE 105 and the associated lower level radio interface protocols, and may send DL signals to the UE 105 and receive UL signals from the UE 105, which may include encoding and modulation of the transmitted signals and demodulation and decoding of the received signals. The gNB-DU 302 may support and terminate at the radio link control (RLC), medium access control (MAC), and physical (PHY) protocol layers of the NR radio frequency (RF) interface to the UE 105, as defined in 3GPP TS 38.201, 38.202, 38.211, 38.212, 38.213, 38.214, 38.215, 38.321, and 38.322. The operation of the gNB-DU 302 is controlled in part by the associated gNB-CU 307. One gNB-DU 307 may support one or more NR radio cells for the UE 105. The gNB-CU 307 may support and terminate the Radio Resource Control (RRC) protocol, Packet Data Convergence Protocol (PDCP), and Service Data Protocol (SDAP) of the NR RF interface to the UE 105, as defined in 3GPP TS 38.331, 38.323, and 37.324, respectively. The gNB-CU 307 may also be split into separate control plane (gNB-CU-CP) and user plane (gNB-CU-UP) portions, wherein the gNB-CU-CP uses the NGAP protocol to communicate with one or more AMFs 122 in one or more 5GCNs 110, and wherein the gNB-CU-UP uses the General Packet Radio System (GPRS) Tunneling Protocol (GTP) User Plane Protocol (GTP-U) to communicate with one or more UPFs 130 in one or more 5GCNs 110, as defined in 3GPP TS 29.281. The gNB-DU 302 and the gNB-CU 307 may communicate over the F1 interface to: (a) support control plane signaling for the UE 105 using Internet Protocol (IP), Stream Control Transmission Protocol (SCTP), and F1 Application Protocol (F1AP) protocols, and (b) support user plane data delivery for the UE using IP, User Datagram Protocol (UDP), PDCP, SDAP, GTP-U, and NR User Plane Protocol (NRUPP) protocols.
[0060] The gNB-CU 307 may use terrestrial links to communicate with one or more other gNB-CUs 307 and / or with one or more other terrestrial gNBs to support an Xn interface between any paired gNB-CUs 302 and / or between any gNB-CU 307 and any terrestrial gNB.
[0061] The gNB-DU 302 together with the gNB-CU 307 may: (i) support signaling connections and voice and data bearers to the UE 105; (ii) support handover of the UE 105 between different radio cells of the same gNB-DU 302 and between different gNB-DUs 302; and (iii) assist in the handover (or transfer) of the SV 302 between different earth stations 104 or between different 5GCNs 110. The gNB-CU 307 may hide or mask certain aspects of the SV 302 from the 5GCN 110, for example, by interfacing with the 5GCN 110 in the same or similar manner as a gNB.
[0062] In the network architecture 300, the gNB-DU 302 that communicates with and is accessible from any gNB-CU 307 will change over time along with the LEO SV 302. In the case of a split gNB architecture, the 5GCN 110 may be connected to a fixed gNB-CU 307 that does not change over time and may reduce the difficulty of paging the UE 105. For example, the 5GCN 110 may not need to know which SV / gNB-DU 302 is needed to page the UE 105. The network architecture with regenerated SV 302 with a split gNB architecture may therefore reduce the 5GCN 110 impact at the expense of additional impact on the gNB-CU 307.
[0063] refer to Figure 3 , the base station (BS) may refer to SV / gNB-DU 302, gNB-CU 307, or a combination of both. For example, either or both of SV 302 or gNB-CU 307 may be used to calculate one or more positioning measurements based on one or more UL RSs from UE 105 to SV 302. Additionally or alternatively, gNB-CU 307 and / or SV 302 may configure one or more DL RSs to be sent by SV 302 to UE 105 for UE 105 to calculate one or more positioning measurements.
[0064] When supporting satellite access to a wireless network, SV 102 / 202 / 302 may send radio beams (also referred to as "beams") to one or more UEs and may receive one or more radio signals from one or more UEs. Such wireless communications between SVs and UEs may be similar to wireless communications between ground base stations and UEs. In many of the examples described below regarding calculating Doppler measurements, ranges, or other types of positioning measurements for UE positioning, the wireless communications are described as being between the UE and a base station (BS), which may refer to, for example, a ground gNB or an SV for an NTN. It should be noted that for the examples provided herein, SVs, satellites, NTN satellites, and LEO satellites may be used interchangeably unless otherwise specifically stated.
[0065] If the UE is communicating with a base station (whether terrestrial or non-terrestrial), the UL RS (such as SRS or other defined RS) or DL RS (such as PRS or other defined RS) may be used to calculate Doppler measurements and ranges associated with the UE with reference to the base station.
[0066] As an example, Figure 4 Example positioning measurements calculated in an NTN that may be used to determine the position of a UE 404 in communication with an SV 402 are illustrated. SV 402 may be an example of any suitable satellite, such as one of SVs 102, 202, or 302. UE 404 may be an example of UE 105.
[0067] The range measurement may be used to indicate or determine the distance between the SV 402 and the UE 404. For example, the range may be the rx-tx transmission time difference (which may be used to calculate the RTT, which may be used to calculate the distance) or another suitable measurement associated with one or more RSs transmitted between the SV 402 and the UE 404. If the range is considered to be associated with the distance of the UE 404 from the SV 402, then the range sphere indicates the potential location of the UE 404 based exclusively on the calculated distance. Since the UE 404 is located approximately on the earth's surface 410, the UE 404 may be located anywhere along the intersection of the range sphere 406 and the earth's surface 410 (which approximates a circle on the earth's surface 410).
[0068] The Doppler measurements indicate motion between the UE 404 and the SV 402 based on frequency changes between the tx and rx of one or more RSs by the UE 404 and the SV 402. The Doppler cone 408 indicates the surface of potential locations of the UE 404 based solely on the Doppler measurements. Since the UE 404 is approximately located on the earth's surface 410, the UE 404 can be located anywhere along the intersection of the Doppler cone 408 and the earth's surface 410 (which is approximately an arc on the earth's surface 410).
[0069] When both range and Doppler measurements are used, UE 404 may be calculated to be located at the intersection of range sphere 406, Doppler cone 408, and earth surface 410 (which may be two points on earth surface 410). Previously calculated UE position or other information may thus be used to identify the location of UE 404, such as Figure 4 404 from the Earth's surface 410, whether the UE 404 is located on or near a sub-orbit of the SV 402, or other potential factors that may affect the positioning measurements and cause errors in the calculated position of the UE are not depicted in this example for clarity. Therefore, UE positioning performed by a location server in the NTN (such as LMF 124) may be based on range and Doppler measurements as measured by the UE and / or base stations (such as SVs and / or gNBs communicatively coupled to the SVs).
[0070] Figure 5 is an example of a UE 500 (such as Figure 1 , Figure 2 and Figure 3 105) is shown in FIG. 105. The UE 500 may include, for example, a wireless antenna ( Figure 5 5. Hardware components for wirelessly communicating with SV 102 / 202 / 302 (not shown), such as satellite transceiver 503, for example, Figure 1 , Figure 2 and Figure 3 UE 500 may also include a wireless antenna ( Figure 5 UE 500 may also include additional transceivers, such as a wireless local area network (WLAN) transceiver 506.
[0071] Although in Figure 5 503 is depicted as a separate component from the wireless transceiver 502, but the satellite transceiver 503 may also be referred to as a wireless transceiver that communicates with one or more network devices. Figure 5WLAN transceiver 506 is depicted as a separate component from wireless transceiver 502, but WLAN transceiver 506 may also be referred to as a wireless transceiver for communicating with one or more network devices. Network devices may include, for example, ground base stations, core network components, earth stations, SVs, WLAN access points, UEs, or other devices in a wireless network. Therefore, as used herein, the term wireless transceiver may refer to any suitable type of transceiver for terrestrial or non-terrestrial network communications, and a UE may have one or more wireless transceivers for one or more different communication types. In some specific implementations, UE 500 may also include a wireless antenna ( Figure 5 An SPS receiver 508 (not shown) receives and measures signals from the SPS SVs.
[0072] In some specific implementations, the UE 500 may receive data from a satellite, for example, via a satellite transceiver 503, and may respond to a ground base station, for example, via a wireless transceiver 502 or via a WLAN transceiver 506. For example, if the UE 500 is to measure Doppler and range (or other positioning measurements) based on a DL RS from a SV, the satellite transceiver 503 may receive a DL RS from the SV. The UE 500 may then report the positioning measurements on the ground via the wireless transceiver 502 or the WLAN transceiver 506. Alternatively, the UE 500 may report the positioning measurements to the SV via the satellite transceiver 503. The ultimate purpose of the positioning measurements may be for a location server to calculate the position of the UE (or perform other operations) based on the positioning measurements. Therefore, the UE 500 may include one or more transmitters, one or more receivers, or both, and they may be integrated, discrete, or a combination of both.
[0073] The UE 500 may also include one or more sensors 510, such as one or more cameras, accelerometers, gyroscopes, electronic compasses, magnetometers, barometers (which may be barometric altimeters), etc. The UE 500 may also include a user interface 512 through which a user can interface with the UE 500, which may include, for example, a display, a keypad, or other input device (such as a virtual keypad on a display). The UE 500 also includes one or more processors 504, a memory 516 (which may include one or more memories), and a non-transitory computer-readable medium 518 (also referred to as a medium), which may be coupled together using a bus 514. The one or more processors 504 and other components of the UE 500 may be similarly coupled together using a bus 514, a separate bus, or may be directly connected together, or coupled using a combination of the foregoing.
[0074] The one or more processors 504 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 504 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 520 on a non-transitory computer-readable medium, such as the medium 518 and / or the memory 516. In some implementations, the one or more processors 504 may represent one or more circuits that may be configured to perform at least a portion of a data signal computing process or method associated with the operation of the UE 500.
[0075] The medium 518 and / or the memory 516 may store instructions or program code 520 containing executable code or software instructions that, when executed by the one or more processors 504, cause the one or more processors 504 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. As illustrated in the UE 500, the medium 518 and / or the memory 516 may include one or more components or modules that may be implemented by the one or more processors 504 to perform the methodologies described herein. Although each component or module is illustrated as software in the medium 518 that may be executed by the one or more processors 504, it should be understood that each component or module may be stored in the memory 516 or may be dedicated hardware in or outside of the one or more processors 504.
[0076] Several software modules and data tables may reside in the medium 518 and / or the memory 516 and be utilized by one or more processors 504 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of the medium 518 and / or the memory 516 as shown in the UE 500 is only exemplary, and therefore, the functionality of each module and / or data structure may be combined, separated and / or constructed in different ways depending on the specific implementation of the UE 500. For the example operations described herein, the term memory may refer to any suitable medium or memory of the UE or other device. Therefore, unless otherwise explicitly stated, the medium and memory are used interchangeably herein. In addition, although each component or each module is illustrated as software in the medium 518 and / or the memory 516 that can be executed by one or more processors 504, it should be understood that each component or each module may be firmware or dedicated hardware in or outside the processor(s) 504.
[0077] As illustrated, the program code 520 stored on the medium 518 and / or the memory 516 may include a positioning module 521, which, when implemented by the one or more processors 504, may configure the one or more processors 504 to perform one or more positioning sessions. During the positioning session, the UE 500 may receive one or more RSs from a base station (such as from a ground base station or SV) via a wireless transceiver (such as a wireless transceiver 502 or a satellite transceiver 503). For example, for NTN, implementing the positioning module 521 may cause the UE 500 to receive a first RS (such as a PRS) and a second RS (such as a second PRS associated with the UE, a tracking reference signal (TRS), a synchronization signal block (SSB), or a demodulation reference signal (DMRS)) from the SV. In addition to or in lieu of receiving one or more RSs, the UE may send one or more RSs to a base station (such as to an SV or to a ground base station). For example, for NTN, implementing the positioning module 521 may cause the UE 500 to send a first RS (such as an SRS) and a second RS (such as a second SRS associated with the UE, a physical random access channel (PRACH) signal, or a DMRS) to the SV. Receiving or sending the RS may include configuring a wireless transceiver (such as a satellite transceiver 503) to receive or send such RS, and the RS may be defined by a location server in the wireless network and indicated to the UE before performing one or more positioning sessions.
[0078] If the UE 500 is to receive RS from a base station (such as from an SV or a terrestrial base station), the positioning session may also include the UE 500 (such as via one or more processors 504 or another component) measuring one or more positioning measurements (such as Doppler measurements and / or ranges) based on the received RS. It should be noted that positioning measurements may refer to any suitable measurements that can be used to calculate the position of the UE 500. For example, the range measurement may include the measured RTT, tx-rx time difference, or the actual distance between the UE 500 and other network devices.
[0079] The positioning session may also include reporting at least a portion of positioning measurements. The UE reporting positioning measurements may include sending an information element (IE) including positioning measurements to a base station (such as an SV or a terrestrial base station), and the positioning measurements may reach a final destination of a location server in the wireless network (where the location server uses the positioning measurements to calculate the location of the UE). IEs defined by 3GPP in one or more standards may be used to report one or more positioning measurements, and / or proprietary IEs may be used to report one or more positioning measurements.
[0080] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 504 may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.
[0081] For specific implementations of UE 500 involving firmware and / or software, these methodologies can be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software codes can be stored in medium 518 or memory 516 and executed by one or more processors 504, so that one or more processors 504 operate as a special-purpose computer programmed to perform the techniques disclosed herein. Memory can be implemented within one or more processors 504 or external to one or more processors 504. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which memory is stored.
[0082] If implemented in firmware and / or software, the functions performed by the UE 500 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as medium 518 or memory 516). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0083] In addition to being stored on a computer-readable storage medium, instructions and / or data for UE 500 may also be provided as a signal on a transmission medium included in a communication device. For example, a communication device including part or all of UE 500 may include a transceiver having a signal indicating instructions and data. The instructions and data are stored on a non-transitory computer-readable medium 518 or a memory 516, and are configured to cause one or more processors 504 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. That is, the communication device includes a transmission medium having a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.
[0084] Figure 6 6 is a diagram illustrating an example of a hardware implementation of a base station 600 configured to support NTN-based UE positioning. As described herein for NTN, the base station may include components of one or more of an SV, an earth station, or a gNB. Thus, although the base station 600 is depicted as a single device, the components of the base station 600 may be distributed across multiple devices. For TN, the base station 600 may be a ground base station. The base station 600 includes a wireless transceiver 602. For NTN, the wireless transceiver may include a satellite transceiver 503 of the SV to communicate with the UE via a wireless antenna ( Figure 6 ) to wirelessly communicate with UE 105, for example, Figure 1 , Figure 2 and Figure 3 For TN600, the wireless transceiver includes a wireless antenna ( Figure 6 105). The base station 600 may include a wireless transceiver 602 for transmitting or receiving terrestrial signals to wirelessly communicate with the UE 105. If the base station 600 includes an earth station or other terrestrial equipment, the base station 600 may also include a wired transceiver 602 for communicatively coupling with a core network or another suitable network device. For example, returning to reference Figure 1 , a base station may include components of an SV 102, an earth station 104, and a gNB 106. The SV 102 and the earth station 104 include wireless transceivers for communicating with the UE and with each other, and the gNB may include a wired transceiver for communicating with the core network.
[0085] The base station 600 also includes one or more processors 604, a memory 616 (which may include one or more memories), and a non-transitory computer-readable medium 618 (also referred to as a medium), which may be coupled together using a bus 614. The one or more processors 604 and other components of the base station 600 may similarly be coupled together using the bus 614, a separate bus, or may be directly connected together, or coupled using a combination of the foregoing.
[0086] The one or more processors 604 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 604 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 620 on a non-transitory computer-readable medium, such as the medium 618 and / or the memory 616. In some implementations, the one or more processors 604 may represent one or more circuits that may be configured to perform at least a portion of a data signal computing process or method associated with the operation of the base station 600.
[0087] The medium 618 and / or memory 616 may store instructions or program code 620 containing executable code or software instructions that, when executed by the one or more processors 604, cause the one or more processors 604 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. As illustrated in the base station 600, the medium 618 and / or memory 616 may include one or more components or modules that may be implemented by the one or more processors 604 to perform the methodologies described herein. Although each component or module is illustrated as software in the medium 618 that may be executed by the one or more processors 604, it should be understood that each component or module may be stored in the memory 616 or may be dedicated hardware in or outside of the one or more processors 604.
[0088] Several software modules and data tables may reside in the medium 618 and / or memory 616 and be utilized by one or more processors 604 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of the medium 618 and / or memory 616 as shown in the base station 600 is merely exemplary, and therefore, the functionality of the modules and / or data structures may be combined, separated and / or constructed in different ways depending on the specific implementation of the base station 600. For the example operations described herein, the term memory may refer to any suitable medium or memory of a base station (such as one or more of an SV, earth station, gNB, or other device). Therefore, unless otherwise explicitly stated, medium and memory are used interchangeably herein. In addition, although each component or module is illustrated as software in the medium 618 and / or memory 616 that can be executed by one or more processors 604, it should be understood that each component or module may be firmware or dedicated hardware in or outside of one or more processors 604.
[0089] As illustrated, the program code 620 stored on the medium 618 and / or the memory 616 may include a positioning module 621, which when implemented by the one or more processors 604 may configure the one or more processors 604 to perform one or more positioning sessions. During the positioning session, the base station 600 may receive one or more RSs from the UE via the wireless transceiver. For example, for NTN, implementing the positioning module 621 may cause the SV to receive a first RS (such as an SRS) and a second RS (such as a second SRS associated with the UE, a physical random access channel (PRACH) signal, or a DMRS) from the UE. In addition to or in lieu of receiving one or more RSs, the base station may send one or more RSs to the UE. For example, for NTN, implementing the positioning module 621 may cause the base station 600 to send a first RS (such as a PRS) and a second RS (such as a second PRS associated with the UE, a TRS, an SSB, or a DMRS) to the UE. Receiving or sending RSs may include configuring the wireless transceiver 602 to receive or send such RSs, and the RSs may be defined by a location server in the wireless network and indicated to the base station (such as to the gNB) before performing one or more positioning sessions.
[0090] If the base station 600 is to receive RS from the UE (such as regenerating SV to receive RS from the UE), the positioning session may also include the base station 600 (such as via one or more processors 604 or another component) measuring one or more positioning measurements (such as Doppler measurements and / or ranges) based on the received RS. As described above, positioning measurements may refer to any suitable measurements that can be used to calculate the position of the UE 500. For example, the range measurement may include the measured RTT, tx-rx, or actual distance between the UE and the base station.
[0091] The positioning session may also include reporting at least a portion of the positioning measurements. The base station reporting the positioning measurements may include sending an information element (IE) including the positioning measurements to a component of the core network, and the positioning measurements may reach a final destination of a location server in the wireless network (where the location server uses the positioning measurements to calculate the location of the UE). For example, if the SV includes a gNB, the SV may use a wireless transceiver to send the positioning measurements to an earth station, which may relay the positioning measurements to the core network components. In another example, if the gNB is separate from the SV, or the NTN includes a gNB-DU and a gNB-CU, the terrestrial gNB may use a wired transceiver to send the positioning measurements to the core network components.
[0092] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 604 may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.
[0093] For specific implementations of base station 600 involving firmware and / or software, these methodologies may be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions may be used to implement the methodologies described herein. For example, software codes may be stored in medium 618 or memory 616 and executed by one or more processors 604, thereby causing one or more processors 604 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. Memory may be implemented within one or more processors 504 or external to one or more processors 604. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which memory is stored.
[0094] If implemented in firmware and / or software, the functions performed by the base station 600 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as medium 618 or memory 616). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0095] In addition to being stored on a computer-readable storage medium, instructions and / or data for the base station 600 may also be provided as a signal on a transmission medium included in the communication device. For example, a communication device including part or all of the base station 600 may include a transceiver having a signal indicating instructions and data. The instructions and data are stored on a non-transitory computer-readable medium 618 or a memory 616, and are configured to cause one or more processors 604 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. That is, the communication device includes a transmission medium having a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.
[0096] As noted herein, one or more positioning sessions between a UE and a base station (such as an SV) may be performed to calculate positioning measurements associated with the location of the UE. When performing a positioning session, a device (such as a UE or a base station) may calculate Doppler measurements and / or range measurements (such as RTT or rx-tx time difference). When configured to calculate and use Doppler measurements and range measurements for positioning, the position of the UE may be calculated based on the UE being within the line of sight of only one satellite of the NTN. In order to calculate Doppler measurements, RS may need to be defined as being used for Doppler measurements. As described herein, two RSs may be defined as being received by a device. At least one of the two RSs may be used to calculate range measurements, and at least one of the two RSs may be used to calculate Doppler measurements (which may be the same or different RS as the RS used to calculate range measurements).
[0097] Figure 7 A flow chart of an example process 700 for performing NTN-based UE positioning is shown. Process 700 may be performed by a UE (such as UE 500) or a base station (such as base station 600) performing one or more UE positioning sessions. For NTN-based positioning, transmission of RSs for calculating one or more positioning measurements may be performed between the UE and the SV (such as Figure 1 , Figure 2 and Figure 3 ). Process 700 (and other processes described below) are described as being performed by a device. Unless otherwise explicitly stated in the example implementations described below, a device performing an operation may refer to a UE or a base station that performs such an operation. In addition, a base station that performs an operation may refer to a SV, an earth station, a gNB, or a combination of network devices that perform an operation.
[0098] At 702, a device receives a first RS from a first device, wherein the first RS is one of a PRS from a base station (BS) or an SRS from a UE. If the device receiving the first RS is a UE, the first device is a BS, and the first RS is a PRS received from the BS on the DL. For example, the UE may receive the PRS from a SV in the NTN via a wireless transceiver (such as a satellite transceiver). If the device receiving the second RS is a BS (such as a SV including the NTN), the first device is a UE, and the first RS is an SRS received from the UE on the UL. For example, the SV may receive the SRS from the UE via a wireless transceiver (i.e., a satellite transceiver).
[0099] At 704, the device receives a second RS from the first device, wherein the second RS is associated with the first RS. The second RS may be any suitable RS from the first device. For example, if the device receiving the first RS is a UE, the second RS may be one of a second PRS, a TRS, an SSB, or a DMRS associated with the UE. The first PRS and the second PRS may refer to different instances (such as consecutive instances) of the PRS. If the device receiving the second RS is a BS (such as an SV including an NTN), the second RS may be one of a second SRS, a PRACH signal, or a DMRS. The first SRS and the second SRS may refer to different instances (such as consecutive instances) of the SRS.
[0100] The first RS is associated with the second RS and may include the second RS within a defined time window of the first RS. In this way, the second RS may be received within a time amount less than the defined maximum time from receiving the first RS. The defined time window may be any suitable length, which may be defined by a standard or may be proprietary. The first RS and the second RS closely allocated in the time domain may allow the receiving device to receive the RS without noise introduced by a power amplifier (PA), a local oscillator (LO), or other components used by a wireless transceiver to receive the RS. For example, if the first RS and the second RS are separated by a certain amount of time so that the device sends a signal between receiving the two RSs, the PA switches between different states (such as increasing the power output for transmission). The switching between different states is associated with the amount of time for the PA to stabilize. During this time, any signal received may have noise included due to PA stability. If the first RS and the second RS are closely allocated so that the PA does not change state between receiving the first RS and the second RS, the received RS is not affected by the noise caused by the PA stabilizing from the switching state. Additionally or alternatively, if the same LO is used for transmission and reception, the LO will be used to tune to a first frequency for reception and a second frequency for transmission. Switching between the first frequency and the second frequency is also associated with the amount of time for the frequency to stabilize. During this time, any signal received may have noise included due to the frequency stabilization. If the first RS and the second RS are closely distributed so that no transmission occurs between receiving the first RS and the second RS, the received RS is not affected by the noise caused by stabilizing from the switching frequency.
[0101] The association of the second RS with the first RS may refer to the second RS being quasi co-located (QCL) with the first RS. In some specific implementations, the quasi co-location (QCL) of the RS may be based on one or more QCL types defined in the technical specification (TS) 38.214 from 3GPP. In TS 38.214, QCL types A to D are defined. QCL type A, QCL type B, and QCL type C allow a device to calculate Doppler measurements (also known as Doppler shift) based on the RS of the QCL. Therefore, the QCL between the first RS and the second RS may be one of QCL type A, QCL type B, or QCL type C, where the RS is configured according to such QCL. It should be noted that QCL type C may be the minimum QCL type that can be used to calculate Doppler measurements. For example, the location server may provide auxiliary data indicating information about the RS, such as defining the RS to be used (such as PRS and SSB for DL) and the QCL type. A base station (such as a gNB) may configure the RS to be sent to the UE based on the auxiliary data, where the SV sends the RS to the UE. Therefore, the UE can calculate the Doppler frequency shift according to the RS of the QCL.
[0102] At 706, the device calculates a Doppler measurement based on one or both of the first RS or the second RS. For example, the device may calculate the Doppler measurement based exclusively on the first RS (such as the first PRS or SRS), based exclusively on the second RS (such as the second PRS or SRS, TRS, SSB, PRACH signal, or DMRS), or based on a combination of the first RS and the second RS. Figure 7 Not shown, but the device may also calculate a range measurement (range) based on the first RS (such as calculating the rx-tx transmission time difference of the PRS or SRS).
[0103] Whether the Doppler measurement is calculated based on only one of the RSs or both RSs may be based on whether the second RS is bound to the first RS. Binding may refer to maintaining phase coherence between the first RS and the second RS, where the RSs are transmitted on the same carrier frequency. For example, a transmitting device using the same carrier frequency and the same PA level to transmit the first RS and the second RS within a short amount of time of each other (such as continuously or within a few symbols of each other) allows the receiving device to use the two RSs to measure the Doppler shift (which is based on the observed frequency change) because the carrier frequency and phase remain consistent between the two RSs. If the phase coherence between the RSs is not maintained, the receiving device may be limited to using only one of the RSs to measure the Doppler shift. For example, the receiving device may only use the second RS to calculate the Doppler measurement. If phase coherence is to be maintained, the transmitting device (such as a base station for DL RS or a UE for UL RS) may be responsible for maintaining phase coherence. It should be noted that the transmitting device may apply any existing RS bundling scheme (such as any bundling scheme defined in the standard set from 3GPP for NR) to maintain phase coherence.
[0104] In some implementations, bundling the first RS and the second RS may include allocating the first RS and the second RS within the same bandwidth (BW). As described above, bundling the RSs to maintain phase coherence may include using the same PA state and carrier frequency to transmit the two RSs. If the RSs are allocated the same BW, the transmitting device may use the same PA state and carrier frequency (without switching between RSs) to transmit the two RSs to prevent phase jumps between transmissions of the RSs. In this way, the first RS and the second RS may be received in the same BW.
[0105] However, the device may be scheduled to send a smaller BW signal on the UL, DL, or sidelink (SL) between the transmission of the first RS and the second RS. For example, the base station may be scheduled to send the SSB after the PRS and before the second RS (with a smaller BW than the PRS), or the UE may be scheduled to send the SSB after the SRS and before the second RS (with a smaller BW than the SRS). Therefore, the transmitting device may need to change the PA from the first state to the second state to send the signal between the RSs, and change the PA back to the first state to send the second RS (such as the second PRS or SRS). As described above, switching the PA state may require a stabilization time of several symbols to ensure that the most recently switched PA state does not introduce noise into the signal. In some specific implementations of maintaining phase coherence, the second RS may be sent with a minimum time gap of at least a symbol between the transmission of the signal between the RSs and the transmission of the second RS. Such a minimum time gap is used to ensure that the PA and any other components are stable after switching states before sending the second RS.
[0106] The number of symbols between the transmission of the signal and the transmission of the second RS may be defined in any suitable manner. In some implementations, if the UE transmits an RS to the SV on the UL, the minimum number of symbols between transmissions may be defined in a standard (such as defined by 3GPP), may be based on the UE's specification of a stabilization time for the PA, or may be based on a UE capability report provided by the UE to the network. For example, a location server may receive a UE capability report, identify the stabilization time required for the UE from the UE capability report, define a first RS and a second RS to ensure that there is a sufficient number of symbols between the intermediate signal that can be transmitted and the second RS, and indicate the RS to the base station in the auxiliary data (where the base station indicates the RS to the UE). In this way, the transmitting device configures the RS so as to allow the PA to stabilize after the switching state after transmitting the intermediate signal and before transmitting the second RS.
[0107] As described above, the bundled RSs may have a time gap between their transmissions. If the UE is to transmit a bundled RS, the UE may use the same PA and LO and other components to transmit the RS and other signals. Therefore, if the components are not allowed to stabilize before transmission, the need to change the PA state, carrier frequency, or any other configuration for transmission may cause noise. In the above example, the time gap between the transmission of the signal after the first RS and the transmission of the second RS may have a sufficient length to allow the components to stabilize.
[0108] The UE may be configured to prevent another signal (such as a PRACH signal or a physical uplink control channel (PUCCH) signal) from being transmitted between the first RS and the second RS, rather than the UE ensuring that a sufficient amount of time has elapsed between transmissions in order to maintain phase coherence. In some implementations, the time gap between the first RS and the second RS may be less than a defined number of time slots (such as 1-3 time slots or another suitable number). If the time gap is small enough, the UE is able to maintain phase coherence by not transmitting during the time gap (thereby allowing the PA and other components to remain in the same state) without significantly increasing the transmit latency. In some implementations, transmissions to the UE on the DL may be scheduled for the time gap so that the UE is configured to receive signals on the DL during such time gaps.
[0109] As described above, the location server may define the RS to be used. The location server may also determine whether the RS will be bound. In some embodiments, the location server (or another suitable network component) may provide an indication that the RS will be bound. For example, the location server may indicate in the auxiliary data that the RS will be bound, and the auxiliary data is received by the base station. The UE may also receive an indication, which may be forwarded by the base station or provided in other ways. In this way, the device receiving the RS can be configured based on which RS to calculate the Doppler measurement. If the indication is that the RS is bound, both RSs can be used to calculate the Doppler measurement. Conversely, if the RS is not bound, only the second RS can be used to calculate the Doppler measurement.
[0110] Doppler measurements may include any suitable measurement associated with the Doppler shift of signals between a UE and a base station. For example, a Doppler measurement may be a measured frequency offset between a carrier frequency used in transmission of an RS (or bundled RS) and a frequency observed in reception of an RS.
[0111] Return to reference Figure 7 At 708, the device may report Doppler measurements, where the Doppler measurements will be used to calculate the location of the UE. For example, if the base station calculates Doppler measurements (such as measuring frequency offset), the Doppler measurements may be reported to the core network component, which is then provided to the location server. If the UE calculates Doppler measurements (such as measuring frequency offset), the Doppler measurements may be sent to the base station (or another UE) in an information element (IE), where the Doppler measurements ultimately reach the location server. In addition, the base station or UE may also report range measurements (such as RTT or measured tx-rx time difference) to be received by the location server. The location server may then use the Doppler measurements (and range measurements) to calculate the location of the UE.
[0112] If the reporting device is a UE, any suitable IE may be used to send the Doppler measurement. In some specific implementations, the Doppler measurement may be reported in any suitable proprietary IE. In some other specific implementations, the Doppler measurement may be reported in an existing IE to be sent by the UE. For example, the IE may report the Doppler measurement in the NRNR-Doppler-SignalMeasurementInformation IE, which may be defined by 3GPP for NR. The NR-Doppler-SignalMeasurementInformation IE may also include one or more of a timestamp associated with calculating the Doppler measurement, a transmit-receive point (TRP) ID associated with the BS, a cell ID associated with the BS, an absolute radio frequency channel number (ARFCN) associated with the channel used to receive the first RS and the second RS, or a resource ID used to calculate the Doppler measurement. In addition to or in lieu of the UE reporting the resource ID, the base station may indicate the resource ID used for the Doppler measurement to the location server.
[0113] In another example, the UE may report Doppler measurements in an existing NR-Multi-RTT-SignalMeasurementInformation IE. The original NR-Multi-RTT-SignalMeasurementInformation IE is defined in 3GPP TS 37.355. The NR-Multi-RTT-SignalMeasurementInformation IE may include rx-tx time difference measurements as range measurements, and the NR-Multi-RTT-SignalMeasurementInformation IE may be modified to include Doppler measurements. In this way, range measurements and Doppler measurements may be included in the same IE.
[0114] An instance of the NR-Multi-RTT-SignalMeasurementInformation IE may be sent by the UE for each RS received by the UE. In this way, the UE sends a first instance of the NR-Multi-RTT-SignalMeasurementInformation IE for a first RS (i.e., a first PRS) and a second instance of the NR-Multi-RTT-SignalMeasurementInformation IE for a second RS (such as a second PRS or a different type of RS contiguous with the first RS). In some implementations, if the UE uses both the first RS and the second RS to calculate the Doppler measurement (using bundled RSs), the Doppler measurement may be included in both the first instance and the second instance of the NR-Multi-RTT-SignalMeasurementInformation IE.
[0115] In some other embodiments, the UE may include the Doppler measurement in only one of the first instance of the NR-Multi-RTT-SignalMeasurementInformation IE or the second instance of the NR-Multi-RTT-SignalMeasurementInformation IE. For example, the UE may use only the second RS to perform the Doppler measurement. Therefore, the Doppler measurement may be included in the second instance of the NR-Multi-RTT-SignalMeasurementInformation IE (where the Doppler measurement is excluded from the first instance of the NR-Multi-RTT-SignalMeasurementInformation IE). In some specific implementations, the UE may indicate which NR-Multi-RTT-SignalMeasurementInformation IEs will include the Doppler measurement during configuration. For example, the UE may indicate to the base station that each NR-Multi-RTT-SignalMeasurementInformation IE will include the Doppler measurement, or only a subset of the NR-Multi-RTT-SignalMeasurementInformation IE will include the Doppler measurement. It should be noted that in cases where limited wireless medium resources are allocated for certain IEs, excluding Doppler measurements from one or more IEs may save wireless medium resources, which may improve throughput.
[0116] Regarding whether the base station is to calculate and report Doppler measurements, the base station may indicate to the location server the resource ID used for Doppler measurements.It should be noted that the base station may report the Doppler measurements and the resource ID in any suitable manner so that they are received by the location server.
[0117] As described above, the location server may use Doppler measurements to determine the location of the UE. Figure 4 , Doppler cone 408 may be referred to as a range rate cone that indicates the range rate between UE 404 and SV 402. The range rate indicates the speed at which the UE moves toward or away from a base station (such as an SV). Points on the cone surface indicate potential locations of UE 404 associated with the same range rate calculated for UE 404. The range rate may be calculated using the following equation (1):
[0118]
[0119] R is the rate of change of range and C is the speed of light. meas,BS is the frequency offset at the base station (such as at the SV). meas,UE is the frequency offset at the UE. R is the carrier frequency on UL. F is the carrier frequency on the DL. It should be noted that even if the base station uses different LOs for transmission and reception, the offset between the frequencies generated by the LO at the base station (trying to generate the same frequency) can be ignored based on the quality of the components (no size and power limitations) to ensure that there are almost no unexpected differences in the output of the LO. If the range change rate is calculated based on only the UL RS or the DL RS with reference to the above equation (1), the range change rate can be calculated using the following equation (2) for the UL RS or the following equation (3) for the DL RS:
[0120]
[0121]
[0122] It should be noted that although the location server is described as calculating the range change rate, in some specific implementations, the device that calculates and reports the Doppler measurement can calculate the range change rate, where the range change rate is the Doppler measurement reported to the location server. The location server can use the range change rate and the range to calculate the position of the UE on the surface of the earth.
[0123] If the UE uses the same LO for reception and for transmission, there are no different LOs that cause unintended frequency offsets between transmission and reception, and the range rate can be calculated using equation (1) above without further calculation or modification. However, the UE may include different LOs for reception and transmission. Unlike a base station, the difference in the frequency of the LO output may be significant enough to affect Doppler measurements (such as when calculating the range rate). For example, smaller and lower power LOs and components may be used to conserve battery power for the UE (whereas such design considerations may not be required for a base station), and these LOs may have inherent frequency offsets from each other. Therefore, unintentional frequency offsets may affect the calculation of the range rate.
[0124] Figure 8 800 is a frequency diagram of an example frequency offset of a reference signal measured on the DL (as depicted by frequency diagram 802) and a frequency offset of a reference signal measured on the UL (as depicted by frequency diagram 804). In diagram 800, UT is an abbreviation for user terminal (which refers to UE) and GW is an abbreviation for gateway (which refers to base station). As described above for equation (1), R is the range change rate and C is the speed of light. f meas,GW is the measured frequency offset at a base station (such as at a SV). meas,UT is the measured frequency offset at the UE. R is the carrier frequency on UL. F is the carrier frequency on DL. off is the frequency offset between the LO used for reception and the LO used for transmission at the UE. f0 is the reference frequency of the LO (so that is the normalized frequency offset of the LO).
[0125] For DL as depicted in frequency diagram 802, the actual frequency offset is the carrier frequency f F to the frequency of the signal as received at the UE (f received@UT ). However, due to the frequency offset between different LOs used for the UE, the measured frequency offset f meas,UT Normalized frequency offset of LO smaller than the actual frequency offset Multiply by the carrier frequency f F .
[0126] For the UL as depicted in frequency diagram 804, the carrier frequency is affected by the frequency offset of the LO. Therefore, the actual carrier frequency (f UT,R ) and the expected frequency offset f R Normalized frequency offset from the phase LO Multiply by the carrier frequency f R Therefore, the base station can assume that the carrier frequency is f RSo that the measurement frequency of RS is offset (f meas,GW ) is derived from the assumed carrier frequency f R to the received RS frequency (f received@GW ). However, the actual frequency offset to be used to calculate the range change rate is the carrier frequency f used UT,R to the frequency of the signal received at the BS (f received@GW ), which is smaller than the measured frequency offset by the normalized frequency offset of the LO Multiply by the carrier frequency f R .
[0127] Therefore, it may be necessary to calculate the range change rate and thus the position of the UE based on the normalized frequency offsets of the different LOs. As described above, if the UE uses the same LO for both transmission and reception, there is no frequency offset for the different LOs to affect the range change rate. In some implementations, the UE may report whether the UE uses the same LO for both reception and transmission. For example, during configuration of the UE when connecting to a wireless network, the UE may send a flag or other indicator to indicate whether the UE uses different LOs.
[0128] If the UE indicates different LOs for reception and transmission, the UE may calculate and report a LO normalized frequency offset, where the location server ultimately receives an indication of the LO normalized frequency offset. For example, during calibration of the UE or within operation of the UE, the UE may be configured to calculate and store the LO normalized frequency offset. When the UE is connected to a base station of a wireless network or is configured for UE positioning in a wireless network, the UE may indicate the stored LO normalized frequency offset to the base station and continue to indicate to the location server. In this way, the location server may use the LO normalized frequency offset to correctly determine the range change rate based on the measured frequency offset at the base station or at the UE (thereby correcting the error in the measured frequency offset caused by the normalized LO frequency offset).
[0129] As an alternative to indicating whether the UE includes different LOs for reception and transmission, a UE that uses different LOs may be configured to always report a LO normalized frequency offset. If the location server does not receive an indication of the LO normalized frequency offset for the UE, the location server may assume that the same LO is used for both reception and transmission for the UE. Alternatively, the UE may be configured to send a LO normalized frequency offset of zero if the UE uses the same LO for both reception and transmission.
[0130] Various implementations are described above for devices to calculate and report Doppler measurements for use in UE positioning. For NTN (or even TN), Doppler measurements associated with the UE (together with range measurements) can be used by a location server to calculate the UE's position. Although LO frequency offset and PA state switching are described above as example factors that can affect Doppler measurements (such as range change rate) and range measurements (such as RTT), another factor that can affect UE positioning accuracy in NTN is the location of the sub-orbit of the UE reference SV. Specifically, as the UE approaches the sub-orbit of the SV, the cross-orbit positioning error increases exponentially. In some implementations, one or more positioning sessions may be scheduled for the UE and SV to ensure that the UE is not always near the sub-orbit of the SV. A positioning session may refer to an instance during which a first RS and a second RS are received (based on which Doppler and range measurements are calculated and the UE's position is determined).
[0131] Fig. 9 1 is a flow chart showing an example process 900 for a device to perform NTN-based UE positioning based on multiple positioning sessions. The process 900 may be performed by a UE such as Figure 1 , Figure 2 and Figure 3 UE 105 in) or a base station (such as Figure 1 , Figure 2 and Figure 3 At 902, the device performs a plurality of positioning sessions associated with a satellite of the NTN, wherein the positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning sessions. If the positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the SV (such as greater than a threshold distance associated with a maximum cross-orbit error) while the UE is still in a coverage area of the SV for at least a subset of the positioning sessions, then the subset of the positioning sessions can be used to calculate a more accurate Doppler measurement and therefore a more accurate UE positioning.
[0132] Because it is unlikely that the UE is exactly on a sub-orbit of the SV, and further because the UE is likely to be mobile and move within the coverage area associated with the SV, the UE may not remain on a sub-orbit of the SV as the SV traverses the surface of the Earth. Thus, while a first positioning session may be associated with a UE that is approximately on a sub-orbit of the SV, a subsequent or prior positioning session (in which the positioning of the SV and the UE are different) may be associated with a UE that is away from the sub-orbit of the SV.
[0133] Referring to block 902, a network component (such as a gNB or a core network component) may schedule multiple positioning sessions to be performed between a UE and the same SV for calculating Doppler measurements and range measurements for the UE (which may be used to calculate the positioning of the UE). For example, during a DL RS-based positioning measurement, a UE receiving the RS may calculate a frequency offset and an rx-tx transmit time difference. The frequency offset may be used to calculate a range change rate (such as described above), and the rx-tx transmit time difference may be used to calculate a distance between the UE and the SV, which is used to calculate the positioning of the UE.
[0134] Multiple positioning sessions may be distributed over a certain time duration (during which the UE remains within the coverage of the SV) to increase the likelihood that at least a subset of the positioning sessions are associated with UEs in a sub-orbit away from the SV. For example, 30 positioning sessions may be scheduled over a one-hour period so that a positioning session occurs every two minutes between the same UE and the same SV. However, the time duration over which multiple positioning sessions are to occur may be defined in any suitable manner. In addition, the time interval between positioning sessions may be defined in any suitable manner. For example, the time duration may be based on the speed of the SV relative to the earth's surface (which may affect the amount of time the UE may be within the coverage of the SV). In another example, the interval of positioning sessions may be based on the latency requirements of UE positioning (such as what application the UE is executing, including whether the UE is executing location-based services, such as navigation). In some specific implementations, the duration and interval of positioning sessions may be based on previous observations about the expected number and expected duration of positioning sessions to reduce cross-orbit errors in UE positioning.
[0135] At block 904, the device reports the results from the positioning session, where the results are used to calculate the position of the UE. Figure 7 As described in block 708 of , the UE may send Doppler and range measurements in any suitable IE, or the base station may send Doppler and range measurements to the core network (where the location server receives the measurements) in any suitable manner. In some implementations of reducing cross-track errors, the location server may attempt to calculate the UE position for each positioning session in sequence, and the location server may identify outliers in the sequence of UE positions as those affected by cross-track errors. The outlier UE positions may be ignored and the remaining UE positions can be used.
[0136] In addition to errors in UE positioning caused by UEs close to the sub-orbit of the SV, changes in the UE's altitude above the Earth's surface may also cause errors in UE positioning. Figure 4For clarity, the Earth's surface 410 is depicted as smooth and having a static elevation, but the Earth's actual surface varies in elevation. If the assumed smooth surface of the Earth were to be used to calculate UE positioning, the difference between the actual elevation and the assumed elevation would affect the range measurement, and changes in elevation could affect the Doppler measurement.
[0137] The location server may use a terrain map to identify the potential elevation of a UE when calculating UE error to reduce the error. However, man-made objects may also affect the height of a UE from the earth's surface. For example, a UE at the top of a skyscraper may have a large height difference compared to a UE at the bottom of the skyscraper.
[0138] In order to reduce the UE positioning error associated with the assumed height of the UE, in some specific implementations, the device may obtain the height of the UE and report the height of the UE. For example, during a positioning session, the device may obtain the current height of the UE and report the height together with other positioning measurements. In some specific implementations, if the device is a UE, the UE may use a UE elevation sensor to measure the height. For example, the UE may include a barometric altitude sensor to measure the height of the UE above sea level (where the height is based on changes in the earth's surface and man-made objects (such as different floors of a building)). Additionally or alternatively, obtaining the height of the UE may include obtaining the height according to user input. For example, the UE may include a user interface for the user to input the approximate height of the UE from the earth's surface (such as a user indicating that he or she is currently on the fifth floor of an office building). Further additionally or as an alternative, the device may obtain the height from a nearby UE. For example, a UE close to the UE may include a sensor or otherwise be able to indicate its height relative to the earth's surface, and the UE may indicate its height to the SV (which is provided to the location server). If the nearby UE is close enough to the UE in question, it can be assumed that the height of the nearby UE is the height of the UE in question. If the UE is to provide an indication of altitude, sensor measurements, user input, or other indication of altitude may be included in the IE that includes the Doppler measurement from the UE, or may be sent separately.
[0139] If the SV is to receive UL RS for UE positioning, a base station (such as a gNB) may obtain an indication of altitude from the UE or from a nearby UE in the coverage area of the SV (where the altitude is determined in any suitable manner, such as described above). The base station may send the indication of altitude to a location server (such as via the core network). In this way, the location server is able to further reduce cross-track errors by compensating for the UE's altitude above the Earth's surface.
[0140] As described above, UEs and base stations (such as satellites, earth stations, and / or gNBs) in an NTN may be configured for UE positioning even when only one satellite is within the LOS of the UE. For example, the UE and base station may be configured to calculate Doppler and range measurements and report such measurements for use by a location server to calculate the position of the UE. Example implementations for reducing cross-orbit errors that may occur due to using only one satellite for UE positioning (which may be caused by the position of the UE relative to the satellite's sub-orbit and / or the UE's altitude above the Earth's surface) are also described.
[0141] Although specific embodiments have been disclosed in detail herein, this is only for illustrative purposes and is given by way of example, and is not intended to limit the scope of the following claims. In particular, it is contemplated that various substitutions, changes and modifications may be made without departing from the spirit and scope of the present disclosure as defined by the claims.
[0142] Each configuration may be described as a process depicted as a flowchart or block diagram. Although each flowchart or block diagram may describe the operation as a sequential process, many operations may be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. The process may have additional steps that are not included in the accompanying drawings. In addition, examples of these methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments for performing the necessary tasks may be stored in a non-transient computer-readable medium (such as a storage medium). The processor may perform the described tasks.
[0143] Unless otherwise defined, all technical terms and scientific terms used herein have the same meaning as the meaning generally or conventionally understood.As used herein, the articles "one" and "certain" refer to one or more (that is, at least one) grammatical objects of the article.As an example, "element" means an element or more than one element.As used herein in quoting measurable values (such as amount, time duration, etc.), "about" and / or "approximately" encompass the deviation of ±20% or ±10%, ±5% or +0.1% from a specified value, because such deviations are appropriate in the context of the system, equipment, circuit, method and other implementations described herein.As used herein in quoting measurable values (such as amount, time duration, physical properties (such as frequency), etc.), "substantially" also encompasses the deviation of ±20% or ±10%, ±5% or +0.1% from a specified value, because such deviations are appropriate in the context of the system, equipment, circuit, method and other implementations described herein.
[0144] As used herein (including in the claims), "or" used in a list of items followed by "at least one of" or "one or more of" indicates a disjunctive list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C), and combinations of more than one feature (e.g., AA, AAB, ABBC, etc.). Also, as used herein, unless otherwise stated, a recitation of a function or operation "based on" an item or condition means that the function or operation is based on the recited item or condition, and may be based on one or more items and / or conditions other than the recited item or condition.
[0145] As used herein, a mobile device, user equipment (UE), user terminal (UT), or mobile station (MS) refers to a device such as a cellular or other wireless communication device, a smart phone, a tablet, a personal communication system (PCS) device, a personal navigation device (PND), a personal information manager (PIM), a personal digital assistant (PDA), a laptop or other suitable mobile device capable of receiving wireless communication and / or navigation signals (such as navigation positioning signals). A mobile device or user equipment (UE) may also be referred to as a mobile terminal, a terminal, a device, a terminal (SET) enabling secure user plane location, a target device, a target, or some other name. As used herein, a base station may refer to a ground base station, a SV, a satellite, an earth station, a gNB, a gNB-CU, a gNB-DU, or a combination thereof. A base station may also be referred to as a gateway or some other name. It should be noted that although some of the techniques, processes, and / or specific implementations given herein may follow all or part of one or more standards, in some embodiments, such techniques, processes, and / or specific implementations may not follow part or all of the one or more standards.
[0146] In view of this description, various embodiments may include different combinations of features. Specific implementation examples are described in the following numbered clauses:
[0147] 1. A method performed by a device for performing non-terrestrial network (NTN) based positioning, the method comprising:
[0148] receiving a first reference signal (RS) from a first device, wherein the first RS is one of a positioning reference signal (PRS) from a base station (BS) or a sounding reference signal (SRS) from a user equipment (UE);
[0149] receiving a second RS from the first device, wherein the second RS is associated with the first RS;
[0150] calculating a Doppler measurement based on one or both of the first RS or the second RS; and
[0151] The Doppler measurement is reported, wherein the Doppler measurement is to be used to calculate a position of the UE.
[0152] 2. The method of clause 1, wherein associating the second RS with the first RS comprises allocating the second RS within a defined time window of the first RS.
[0153] 3. The method of clause 1, wherein the second RS is associated with the first RS based on one of:
[0154] Quasi-co-located (QCL) Type A configuration;
[0155] QCL Type B configuration; or
[0156] QCL Type C configuration.
[0157] 4. The method of clause 1, wherein when the second RS is not bundled with the first RS, only the second RS is used to calculate the Doppler measurement.
[0158] 5. The method of clause 1, wherein the second RS is bound to the first RS, wherein:
[0159] Binding the second RS to the first RS includes maintaining phase coherence between the first RS and the second RS; and
[0160] Calculating the Doppler measurement is based on both the first RS and the second RS.
[0161] 6. The method of clause 5, wherein bundling the second RS with the first RS comprises receiving the first RS and the second RS in a same bandwidth.
[0162] 7. The method of clause 5, further comprising receiving an indication generated by a network component that the second RS is bundled with the first RS.
[0163] 8. The method according to clause 1, wherein:
[0164] The device is the UE;
[0165] The first device is the BS; and
[0166] The first RS is the PRS.
[0167] 9. The method of clause 8, wherein the second RS is one of:
[0168] Second PRS;
[0169] Tracking Reference Signal (TRS);
[0170] Synchronization Signal Block (SSB); or
[0171] A demodulation reference signal (DMRS) associated with the UE.
[0172] 10. The method according to clause 8, wherein:
[0173] A downlink (DL) signal is transmitted by the BS between the first RS and the second RS; and
[0174] There is at least a defined time gap between the DL signal and the second RS.
[0175] 11. The method of clause 8, wherein reporting the Doppler measurement comprises reporting the Doppler measurement in an NR-Doppler-SignalMeasurementInformation information element (IE).
[0176] 12. A method as described in clause 11, wherein the NR-Doppler-SignalMeasurementInformation IE comprises one or more of the following:
[0177] a timestamp associated with calculating the Doppler measurement;
[0178] a transmit-receive point (TRP) ID associated with the BS;
[0179] a cell ID associated with the BS;
[0180] an absolute radio frequency channel number (ARFCN) associated with a channel used to receive the first RS and the second RS; or
[0181] The resource ID used to calculate the Doppler measurement.
[0182] 13. The method of clause 8, wherein reporting the Doppler measurement comprises reporting the Doppler measurement in an NR-Multi-RTT-SignalMeasurementInformation information element (IE).
[0183] 14. A method as described in clause 13, wherein reporting the Doppler measurement in the NR-Multi-RTT-SignalMeasurementInformation IE comprises reporting the Doppler measurement in a first instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the PRS and in a second instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the second RS.
[0184] 15. A method as described in clause 13, wherein reporting the Doppler measurement in the NR-Multi-RTT-SignalMeasurementInformation IE comprises reporting the Doppler measurement only in a second instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the second RS, wherein the Doppler measurement is excluded from a first instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the PRS.
[0185] 16. A method as described in clause 13, further comprising indicating which instances of the NR-Multi-RTT-SignalMeasurementInformation IE are to include the Doppler measurement.
[0186] 17. The method according to clause 1, further comprising:
[0187] Reporting whether the UE uses a same local oscillator (LO) for both reception and transmission, wherein calculating a range change rate is based on whether the UE uses the same LO for both reception and transmission.
[0188] 18. The method according to clause 1, further comprising:
[0189] calculating a local oscillator (LO) normalized frequency offset (FO) between a first LO used for receiving at the UE and a second LO used for transmitting at the UE; and
[0190] The LO normalized FO is reported, where the LO normalized FO is used to calculate the range change rate.
[0191] 19. The method according to clause 1, wherein:
[0192] The device is the base station;
[0193] The first device is the UE; and
[0194] The first RS is the SRS.
[0195] 20. The method of clause 19, wherein the second RS is one of:
[0196] Second SRS;
[0197] a Physical Random Access Channel (PRACH) signal; or
[0198] Demodulation reference signal.
[0199] 21. A method according to clause 19, wherein:
[0200] The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE;
[0201] The transmission of a first signal from the UE is performed between the first RS and the second RS, wherein the first signal has a different bandwidth from the second RS; and
[0202] There is at least a defined time gap between the first signal and the second RS.
[0203] 22. A method as described in clause 21, wherein the defined time gap is based on a UE capability report from the UE.
[0204] 23. A method according to clause 19, wherein:
[0205] The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE;
[0206] There is a time gap between the first RS and the second RS that is less than a defined number of time slots; and
[0207] The UE is prevented from transmitting during the time gap.
[0208] 24. The method of clause 19, further comprising indicating the resource ID used to calculate the Doppler measurement.
[0209] 25. An apparatus for performing non-terrestrial network (NTN) based positioning, the apparatus comprising:
[0210] a wireless transceiver configured to communicate wirelessly with one or more network devices;
[0211] at least one memory; and
[0212] at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor configured to:
[0213] receiving, via the wireless transceiver, a first reference signal (RS) from a first device, wherein the first RS is one of a positioning reference signal (PRS) from a base station (BS) or a sounding reference signal (SRS) from a user equipment (UE);
[0214] receiving a second RS from the first device via the wireless transceiver, wherein the second RS is associated with the first RS;
[0215] calculating a Doppler measurement based on one or both of the first RS or the second RS; and
[0216] The Doppler measurements are reported, wherein the Doppler measurements are to be used to calculate a position of the UE.
[0217] 26. The apparatus of clause 25, wherein associating the second RS with the first RS comprises allocating the second RS within a defined time window of the first RS.
[0218] 27. The apparatus of clause 25, wherein the second RS is associated with the first RS based on one of:
[0219] Quasi-co-located (QCL) Type A configuration;
[0220] QCL Type B configuration; or
[0221] QCL Type C configuration.
[0222] 28. The apparatus of clause 25, wherein when the second RS is not bundled with the first RS, only the second RS is used to calculate the Doppler measurement.
[0223] 29. The apparatus of clause 25, wherein the second RS is bound to the first RS, wherein:
[0224] Binding the second RS to the first RS includes maintaining phase coherence between the first RS and the second RS; and
[0225] Calculating the Doppler measurement is based on both the first RS and the second RS.
[0226] 30. The apparatus of clause 29, wherein bundling the second RS with the first RS comprises receiving the first RS and the second RS in a same bandwidth.
[0227] 31. The apparatus of clause 29, wherein the at least one processor is further configured to receive, via the wireless transceiver, an indication generated by a network component that the second RS is bundled with the first RS.
[0228] 32. The apparatus of clause 25, wherein:
[0229] The device is the UE;
[0230] The first device is the BS; and
[0231] The first RS is the PRS.
[0232] 33. The apparatus of clause 32, wherein the second RS is one of:
[0233] Second PRS;
[0234] Tracking Reference Signal (TRS);
[0235] Synchronization Signal Block (SSB); or
[0236] A demodulation reference signal (DMRS) associated with the UE.
[0237] 34. Apparatus according to clause 32, wherein:
[0238] A downlink (DL) signal is transmitted by the BS between the first RS and the second RS; and
[0239] There is at least a defined time gap between the DL signal and the second RS.
[0240] 35. The apparatus of clause 32, wherein reporting the Doppler measurement comprises reporting the Doppler measurement in an NR-Doppler-SignalMeasurementInformation information element (IE).
[0241] 36. The apparatus of clause 35, wherein the NR-Doppler-SignalMeasurementInformation IE comprises one or more of:
[0242] a timestamp associated with calculating the Doppler measurement;
[0243] a transmit-receive point (TRP) ID associated with the BS;
[0244] a cell ID associated with the BS;
[0245] an absolute radio frequency channel number (ARFCN) associated with a channel used to receive the first RS and the second RS; or
[0246] The resource ID used to calculate the Doppler measurement.
[0247] 37. The apparatus of clause 32, wherein reporting the Doppler measurement comprises reporting the Doppler measurement in an NR-Multi-RTT-SignalMeasurementInformation information element (IE).
[0248] 38. An apparatus as described in clause 37, wherein reporting the Doppler measurement in the NR-Multi-RTT-SignalMeasurementInformation IE comprises reporting the Doppler measurement in a first instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the PRS and a second instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the second RS.
[0249] 39. An apparatus as described in clause 37, wherein reporting the Doppler measurement in the NR-Multi-RTT-SignalMeasurementInformation IE comprises reporting the Doppler measurement only in a second instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the second RS, wherein the Doppler measurement is excluded from a first instance of the NR-Multi-RTT-SignalMeasurementInformation IE associated with the PRS.
[0250] 40. The apparatus of clause 25, wherein the at least one processor is further configured to indicate, via the wireless transceiver, which instances of the NR-Multi-RTT-SignalMeasurementInformation IE are to include the Doppler measurement.
[0251] 41. The apparatus of clause 25, wherein the at least one processor is further configured to:
[0252] Reporting, via the wireless transceiver, whether the UE uses a same local oscillator (LO) for both receiving and transmitting, wherein calculating a range change rate is based on whether the UE uses the same LO for both receiving and transmitting.
[0253] 42. The apparatus of clause 25, wherein the at least one processor is further configured to:
[0254] calculating a local oscillator (LO) normalized frequency offset (FO) between a first LO used for receiving at the UE and a second LO used for transmitting at the UE; and
[0255] The LO normalized FO is reported via the wireless transceiver, wherein the LO normalized FO is used to calculate a range rate.
[0256] 43. The apparatus of clause 25, wherein:
[0257] The device is the base station;
[0258] The first device is the UE; and
[0259] The first RS is the SRS.
[0260] 44. The apparatus of clause 43, wherein the second RS is one of:
[0261] Second SRS;
[0262] a Physical Random Access Channel (PRACH) signal; or
[0263] Demodulation reference signal.
[0264] 45. Apparatus according to clause 43, wherein:
[0265] The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE;
[0266] The transmission of a first signal from the UE is performed between the first RS and the second RS, wherein the first signal has a different bandwidth from the second RS; and
[0267] There is at least a defined time gap between the first signal and the second RS.
[0268] 46. An apparatus as recited in clause 45, wherein the defined time gap is based on a UE capability report from the UE.
[0269] 47. Apparatus according to clause 43, wherein:
[0270] The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE;
[0271] There is a time gap between the first RS and the second RS that is less than a defined number of time slots; and
[0272] The UE is prevented from transmitting during the time gap.
[0273] 48. The apparatus of clause 43, wherein the at least one processor is further configured to indicate, via the wireless transceiver, the resource ID used to calculate the Doppler measurement.
[0274] 49. A method performed by an apparatus for performing non-terrestrial network (NTN) based positioning, the method comprising:
[0275] performing a plurality of positioning sessions associated with a user equipment (UE) and a satellite of the NTN, wherein the positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning sessions; and
[0276] Reporting results from the positioning session, wherein the results are used to calculate the position of the UE.
[0277] 50. The method according to clause 49, further comprising:
[0278] obtaining the height of the UE; and
[0279] The height of the UE is reported, wherein the height is used to calculate the positioning of the UE.
[0280] 51. The method of clause 50, wherein obtaining the altitude of the UE comprises one or more of:
[0281] Measuring said height using a UE altitude sensor;
[0282] Obtaining the height according to user input; or
[0283] The altitude is obtained from nearby UEs.
[0284] 52. An apparatus for performing non-terrestrial network (NTN) based positioning, the apparatus comprising:
[0285] a wireless transceiver configured to communicate wirelessly with one or more network devices;
[0286] at least one memory; and
[0287] at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor configured to:
[0288] performing a plurality of positioning sessions associated with a user equipment (UE) and a satellite of the NTN, wherein the positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning sessions; and
[0289] Results from the positioning session are reported via the wireless transceiver, wherein the results are used to calculate a position of the UE.
[0290] 53. The apparatus of clause 52, wherein the at least one processor is further configured to:
[0291] obtaining the height of the UE; and
[0292] The altitude of the UE is reported via the wireless transceiver, wherein the altitude is to be used to calculate a position of the UE.
[0293] 54. The apparatus of clause 53, wherein obtaining the altitude of the UE comprises one or more of:
[0294] Measuring said height using a UE altitude sensor;
[0295] Obtaining the height according to user input; or
[0296] The altitude is obtained from nearby UEs.
[0297] Other aspects, advantages, and modifications are considered to be within the scope of the appended claims. The claims presented are representative of the embodiments and features disclosed herein. Other embodiments and features not claimed are also contemplated. Therefore, other embodiments fall within the scope of the following claims.
Claims
1. A method performed by a device for performing non-terrestrial network (NTN) based positioning, the method comprising: receiving a first reference signal (RS) from a first device, wherein the first RS is one of a positioning reference signal (PRS) from a base station (BS) or a sounding reference signal (SRS) from a user equipment (UE); receiving a second RS from the first device, wherein the second RS is associated with the first RS; calculating a Doppler measurement based on one or both of the first RS or the second RS; and The Doppler measurements are reported, wherein the Doppler measurements are to be used to calculate a position of the UE. 2 . The method of claim 1 , wherein associating the second RS with the first RS comprises allocating the second RS within a defined time window of the first RS. 3 . The method of claim 1 , wherein when the second RS is not bound to the first RS, only the second RS is used to calculate the Doppler measurement.
4. The method according to claim 1, wherein the second RS is bound to the first RS, wherein: Binding the second RS to the first RS includes maintaining phase coherence between the first RS and the second RS; and Calculating the Doppler measurement is based on both the first RS and the second RS. The method of claim 4 , wherein bundling the second RS with the first RS comprises receiving the first RS and the second RS in the same bandwidth.
6. The method according to claim 1, wherein: The device is the UE; The first device is the BS; The first RS is the PRS; and The second RS is one of the following: Second PRS; Tracking Reference Signal (TRS); Synchronization Signal Block (SSB); or A demodulation reference signal (DMRS) associated with the UE.
7. The method according to claim 6, wherein: A downlink (DL) signal is transmitted by the BS between the first RS and the second RS; and There is at least a defined time gap between the DL signal and the second RS.
8. The method of claim 6, wherein reporting the Doppler measurement comprises reporting the Doppler measurement in one of: NR-Doppler-SignalMeasurementInformation information element (IE); or NR-Multi-RTT-SignalMeasurementInformation information element (IE).
9. The method according to claim 1, further comprising: Reporting whether the UE uses a same local oscillator (LO) for both reception and transmission, wherein calculating a range change rate is based on whether the UE uses the same LO for both reception and transmission.
10. The method according to claim 1, further comprising: calculating a local oscillator (LO) normalized frequency offset (FO) between a first LO used for receiving at the UE and a second LO used for transmitting at the UE; and The LO normalized FO is reported, where the LO normalized FO is used to calculate the range change rate.
11. The method according to claim 1, wherein: The device is the base station; The first device is the UE; The first RS is the SRS; and The second RS is one of the following: Second SRS; a Physical Random Access Channel (PRACH) signal; or Demodulation reference signal.
12. The method according to claim 11, wherein: The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE; The transmission of a first signal from the UE is performed between the first RS and the second RS, wherein the first signal has a different bandwidth from the second RS; and There is at least a defined time gap between the first signal and the second RS.
13. The method according to claim 11, wherein: The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE; There is a time gap between the first RS and the second RS that is less than a defined number of time slots; and The UE is prevented from transmitting during the time gap.
14. An apparatus for performing non-terrestrial network (NTN) based positioning, the apparatus comprising: a wireless transceiver configured to communicate wirelessly with one or more network devices; at least one memory; and at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor configured to: receiving, via the wireless transceiver, a first reference signal (RS) from a first device, wherein the first RS is one of a positioning reference signal (PRS) from a base station (BS) or a sounding reference signal (SRS) from a user equipment (UE); receiving a second RS from the first device via the wireless transceiver, wherein the second RS is associated with the first RS; calculating a Doppler measurement based on one or both of the first RS or the second RS; and The Doppler measurements are reported, wherein the Doppler measurements are to be used to calculate a position of the UE.
15. The apparatus of claim 14, wherein associating the second RS with the first RS comprises allocating the second RS within a defined time window of the first RS.
16. The apparatus of claim 14, wherein when the second RS is not bundled with the first RS, only the second RS is used to calculate the Doppler measurement.
17. The apparatus of claim 14, wherein the second RS is bound to the first RS, wherein: Binding the second RS to the first RS includes maintaining phase coherence between the first RS and the second RS; and Calculating the Doppler measurement is based on both the first RS and the second RS. 18 . The apparatus of claim 17 , wherein bundling the second RS with the first RS comprises receiving the first RS and the second RS in a same bandwidth.
19. The apparatus of claim 14, wherein: The device is the UE; The first device is the BS; The first RS is the PRS; and The second RS is one of the following: Second PRS; Tracking Reference Signal (TRS); Synchronization Signal Block (SSB); or A demodulation reference signal (DMRS) associated with the UE.
20. The apparatus of claim 19, wherein: A downlink (DL) signal is transmitted by the BS between the first RS and the second RS; and There is at least a defined time gap between the DL signal and the second RS.
21. The apparatus of claim 19, wherein reporting the Doppler measurement comprises reporting the Doppler measurement in one of: NR-Doppler-SignalMeasurementInformation information element (IE); or NR-Multi-RTT-SignalMeasurementInformation information element (IE).
22. The apparatus of claim 14, wherein the at least one processor is further configured to: Reporting, via the wireless transceiver, whether the UE uses a same local oscillator (LO) for both receiving and transmitting, wherein calculating a range change rate is based on whether the UE uses the same LO for both receiving and transmitting.
23. The apparatus of claim 14, wherein the at least one processor is further configured to: calculating a local oscillator (LO) normalized frequency offset (FO) between a first LO used for receiving at the UE and a second LO used for transmitting at the UE; and The LO normalized FO is reported via the wireless transceiver, wherein the LO normalized FO is used to calculate a range rate.
24. The apparatus of claim 14, wherein: The device is the base station; The first device is the UE; The first RS is the SRS; and The second RS is one of the following: Second SRS; a Physical Random Access Channel (PRACH) signal; or Demodulation reference signal.
25. The apparatus of claim 24, wherein: The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE; The transmission of a first signal from the UE is performed between the first RS and the second RS, wherein the first signal has a different bandwidth from the second RS; and There is at least a defined time gap between the first signal and the second RS.
26. The apparatus of claim 24, wherein: The second RS is bound to the first RS, wherein phase coherence between the first RS and the second RS is maintained by the UE; There is a time gap between the first RS and the second RS that is less than a defined number of time slots; and The UE is prevented from transmitting during the time gap.
27. A method performed by an apparatus for performing non-terrestrial network (NTN) based positioning, the method comprising: performing a plurality of positioning sessions associated with a user equipment (UE) and a satellite of the NTN, wherein the positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning sessions; as well as Reporting results from the positioning session, wherein the results are used to calculate the position of the UE.
28. The method according to claim 27, further comprising: Obtaining the height of the UE; as well as The height of the UE is reported, wherein the height is used to calculate the positioning of the UE.
29. A user equipment (UE) for performing non-terrestrial network (NTN) based positioning, the UE comprising: a wireless transceiver configured to communicate wirelessly with one or more network devices; at least one memory; and at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor configured to: performing a plurality of positioning sessions associated with a satellite of the NTN, wherein the positioning sessions are scheduled to ensure that the UE is away from a sub-orbit of the satellite for at least a portion of the positioning sessions; as well as Results from the positioning session are reported via the wireless transceiver, wherein the results are used to calculate a position of the UE.
30. The UE of claim 29, wherein the at least one processor is further configured to: obtaining the height of the UE; and The altitude of the UE is reported via the wireless transceiver, wherein the altitude is to be used to calculate a position of the UE.
Citation Information
Patent Citations
User equipment positioning based on a non-terrestrial communication network
US20230341562A1
