System and method for supporting uplink and downlink position determination procedures in a wireless network

By employing positioning methods based on downlink, uplink, or a combination of solutions in wireless communication systems, and leveraging the collaborative work of gNB and UE, the dependence on base station time synchronization is reduced, thus solving the problem of increased positioning costs and complexity for mobile devices and achieving efficient and accurate location determination.

CN112956254BActive Publication Date: 2024-11-15QUALCOMM INC
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN201980070602.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-10-30
Filing Date
2019-10-31
Publication Date
2024-11-15
Estimated Expiration
2039-10-31

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in increasing cost and complexity during mobile device positioning, making it difficult to achieve efficient and accurate location determination methods.

Method used

By using a solution based on downlink, uplink, or a combination of downlink and uplink, positioning support is provided by gNB and UE. The serving gNB requests neighboring gNBs to send and measure reference signals, and the UE combines its own reference signals to measure and determine the round-trip time, reducing the dependence on base station time synchronization.

Benefits of technology

It simplifies the positioning process, reduces system costs and complexity, and improves positioning accuracy and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112956254B_ABST
    Figure CN112956254B_ABST
Patent Text Reader

Abstract

The location of a user equipment (UE) may be determined using a downlink-based solution (e.g., OTDOA), an uplink-based solution (e.g., UTDOA), or a combined downlink- and uplink-based solution (e.g., RTT). The serving gNB may request a neighboring gNB to generate downlink reference signal transmissions to a target UE and / or measure uplink reference signal transmissions from a target UE. The serving gNB may receive uplink reference signal measurements from neighboring gNBs and obtain its own uplink reference signal measurements, and forward all uplink reference signal measurements to the UE or another network entity. The UE may determine the RTT using the uplink reference signal measurements together with the UE's own downlink reference signal measurements. The serving gNB or another entity may maintain the uplink reference signal measurements and may determine the RTT after receiving the downlink reference signal measurements from the UE.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 753,904, filed on October 31, 2018, entitled “SYSTEM AND METHODS FOR SUPPORTING NR POSITIONING PROCEDURES FOR DOWNLINK BASED, UPLINK BASED, AND DOWNLINK AND UPLINK BASED POSITIONING”; U.S. Provisional Application No. 62 / 754,572, filed on November 1, 2018, entitled “SYSTEM AND METHODS FOR SUPPORTING NR POSITIONING PROCEDURES FOR DOWNLINK BASED, UPLINK BASED, AND DOWNLINK AND UPLINK BASED POSITIONING”; and U.S. Provisional Application No. 62 / 754,572, filed on February 14, 2019, entitled “SYSTEM AND METHODS FOR SUPPORTING UPLINK AND DOWNLINK POSITIONING PROCEDURES IN AWIRELESS POSITIONING NETWORK”; U.S. Provisional Application No. 62 / 805,882, filed on February 14, 2019, entitled “ARCHITECTURE FOR SUPPORT OF HIGH-PERFORMANCE LOCATION SERVICES IN A NEXTGENERATION RADIO ACCESS NETWORK”; U.S. Provisional Application No. 62 / 825,779, filed on March 28, 2019, entitled “SYSTEM AND METHODS FOR SUPPORTING UPLINK AND DOWNLINK POSITIONING PROCEDURES IN A WIRELESS NETWORK”; U.S. Provisional Application No. 62 / 805,882, filed on February 14, 2019, entitled “ARCHITECTURE FOR SUPPORT OF HIGH-PERFORMANCE LOCATION SERVICES IN A NEXTGENERATION RADIO ACCESS NETWORK”; U.S. Provisional Application No. 62 / 825,779, filed on March 28, 2019, entitled “SYSTEM AND METHODS FOR SUPPORTING UPLINK AND DOWNLINK POSITIONING PROCEDURES IN A WIRELESS NETWORK”; U.S. Provisional Application No. 62 / 805,882, filed on February 14, 2019, entitled “ARCHITECTURE FOR SUPPORT OF HIGH-PERFORMANCE LOCATION SERVICES IN A NEXTGENERATION RADIO ACCESS NETWORK” NETWORK”;and U.S. Non-Provisional Application No. 16 / 669,504, filed on October 30, 2019, entitled “SYSTEM AND METHODS FOR SUPPORTING UPLINK AND DOWNLINK POSITIONING PROCEDURES IN A WIRELESS NETWORK,” which are assigned to the assignee of the present application and are expressly incorporated herein by reference in their entirety. ; Technical Field

[0003] Aspects of the present disclosure relate to a position estimation process. Background Art

[0004] Wireless communication systems have gone through generations of development, including first generation analog wireless phone service (1G), second generation (2G) digital wireless phone service (including temporary 2.5G and 2.75G networks), third generation (3G) high-speed data, Internet-enabled wireless services, and fourth generation (4G) services (e.g., LTE or WiMax). The fifth generation (5G) mobile standard calls for higher data transmission speeds, more connections, and better coverage, among other improvements. The 5G standard according to the Next Generation Mobile Networks Alliance is designed to provide data rates of tens of megabits per second to each of tens of thousands of users and 1 gigabit per second to dozens of employees in an office.

[0005] Obtaining the location of a mobile device that is accessing a wireless (e.g., 5G) network may be useful for many applications, including, for example, emergency calls, personal navigation, asset tracking, locating friends or family members, etc. However, the positioning of a mobile device may require the implementation of multiple positioning methods by different elements in the wireless network and by the mobile device. This may increase the cost and complexity of both the wireless network and the mobile device, and may not be conducive to supporting the most efficient and accurate location determination methods. Therefore, it may be necessary to improve support for different location determination methods to better achieve synergies and other means to reduce the cost and complexity of implementation. Summary of the invention

[0006] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, the following summary of the invention should not be considered as an extensive overview related to all expected aspects, nor should it be considered that the following summary of the invention identifies key or important elements related to all expected aspects or delimits the scope associated with any particular aspect. Therefore, the following summary of the invention has the following sole purpose: to present certain concepts related to one or more aspects related to the mechanism disclosed herein in a simplified form before the specific embodiments presented below.

[0007] The location (position) of a user equipment (UE) may be determined using a downlink-based solution (OTDOA), an uplink-based solution (UTDOA), or a combined downlink and uplink-based solution (RTT). The process offloads positioning support from the Positioning Management Function (LMF), thereby utilizing the gNB and / or UE for positioning support. The serving gNB may request a neighboring gNB to generate downlink reference signal transmissions to the target UE and / or measure uplink reference signal transmissions from the target UE. The serving gNB may receive uplink reference signal measurements from a neighboring gNB and forward them to the UE or another network entity along with the serving gNB's own uplink reference signal measurements. The UE may determine the RTT using the uplink reference signal measurements together with the UE's own downlink reference signal measurements. The serving gNB may maintain the uplink reference signal measurements and may determine the RTT after receiving the downlink reference signal measurements from the UE.

[0008] On the one hand, a method performed by a user equipment (UE) for determining a location of the UE includes: receiving auxiliary data of multiple gNBs from a serving gNB, the multiple gNBs including the serving gNB; sending an uplink reference signal to the multiple gNBs; receiving uplink reference signal measurements measured by each of the multiple gNBs from the serving gNB, wherein the serving gNB receives the uplink reference signal measurements from other gNBs in the multiple gNBs; and determining the location of the UE based on the uplink reference signal measurements measured by each of the multiple gNBs and the auxiliary data of the multiple gNBs.

[0009] In one aspect, a user equipment (UE) configured for determining a location of the UE includes: an external interface configured to communicate with a gNB; at least one memory; at least one processor coupled to the external interface and the at least one memory, the at least one processor configured to: receive auxiliary data of multiple gNBs from a serving gNB via the external interface, the multiple gNBs including the serving gNB; send an uplink reference signal to the multiple gNBs via the external interface; receive uplink reference signal measurements measured by each of the multiple gNBs from the serving gNB via the external interface, wherein the serving gNB receives the uplink reference signal measurements from other gNBs in the multiple gNBs; and determine the location of the UE based on the uplink reference signal measurements measured by each of the multiple gNBs and the auxiliary data of the multiple gNBs.

[0010] On the one hand, a method for determining a position of a user equipment (UE) performed by a serving gNB of the UE includes: receiving a positioning request for the UE from another entity; determining multiple neighboring gNBs; transmitting a request to each of the multiple neighboring gNBs to increase downlink reference signal transmissions and measure uplink reference signal transmissions from the UE; generating auxiliary data for the multiple neighboring gNBs; sending the auxiliary data for the multiple neighboring gNBs to the UE; receiving uplink reference signal transmissions from the UE; generating uplink reference signal measurements of the uplink reference signal transmissions; receiving one or more uplink reference signal measurements from each of the multiple neighboring gNBs, wherein the one or more uplink reference signal measurements are generated based on uplink reference signal transmissions from the UE to the neighboring gNB; generating positioning information based on the uplink reference signal measurements from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNBs; and sending the positioning information to another entity.

[0011] In one aspect, a gNB configured to determine a location of a user equipment (UE) includes: at least one external interface configured to communicate with the UE, with other gNBs, and with entities in a wireless network; at least one memory; and at least one processor coupled to the at least one external interface and the at least one memory, the at least one processor configured to: receive a positioning request for the UE from another entity; determine a plurality of neighboring gNBs; transmit a request to each of the plurality of neighboring gNBs to increase downlink reference signal transmissions and measure uplink reference signal transmissions from the UE; generate assistance data for the plurality of neighboring gNBs; transmit the plurality of neighboring gNBs via the at least one external interface to each of the plurality of neighboring gNBs; The invention further comprises: sending auxiliary data of a gNB to a UE; receiving an uplink reference signal transmission from the UE via at least one external interface; generating uplink reference signal measurements of the uplink reference signal transmission; receiving one or more uplink reference signal measurements from each of a plurality of neighboring gNBs via at least one external interface, wherein the one or more uplink reference signal measurements are generated based on an uplink reference signal transmission from the UE to the neighboring gNB; generating positioning information based on the uplink reference signal measurement from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB; and sending the positioning information to the another entity via at least one external interface.

[0012] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are presented to aid in describing various aspects of the disclosure and are provided for purposes of illustration of the various aspects only and not limitation thereof.

[0014] Figure 1A A high-level system architecture of a wireless communication system according to an aspect of the present disclosure is shown.

[0015] Figure 1B A wireless communication system including a next generation (NG) radio access network is shown.

[0016] Figure 2 A schematic diagram of a position determination architecture of a communication system is shown.

[0017] Figure 3 is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communications as taught herein.

[0018] Figure 4 is a diagram illustrating an exemplary technique for determining the location of a mobile station using information obtained from multiple base stations.

[0019] Figure 5A and 5B is a schematic diagram illustrating exemplary timing within the RTT that occurs during wireless probe requests and responses.

[0020] Fig. 6A An example of network-centric RTT estimation according to an aspect of the present disclosure is shown.

[0021] Figure 6B An example of UE-centric RTT estimation according to an aspect of the present disclosure is shown.

[0022] Figure 7 An exemplary system in accordance with an aspect of the present disclosure is shown in which the RTT estimation process disclosed herein is extended to massive multiple-input multiple-output (MIMO) and millimeter wave (mmW) systems.

[0023] Figure 8 An exemplary timing diagram with two gNBs is shown, showing the uplink-downlink timing relationship of the serving gNB and the downlink timing relationship of the neighboring gNB.

[0024] Fig. 9 An uplink / downlink measurement process controlled and initiated by the positioning management function is shown.

[0025] Fig.10 The call flow of Mobile Originated Location Request (MO-LR) for RTT measurement of a UE is shown, where the measured signal data from the gNB is aggregated using a positioning server.

[0026] Fig.11 The call flow for Mobile Originated Location Request (MO-LR) for RTT measurement of a UE is shown, where the measured signal data from the gNB is aggregated using the gNB.

[0027] Fig.12 The call flow of a Network Initiated Location Request (NI-LR) for RTT measurement of a UE is shown, where a positioning server is used to request RTT determination and aggregate measured signal data from gNBs.

[0028] Fig.13 The call flow for Network Initiated Location Request (NI-LR) for RTT measurement of a UE is shown, where RTT determination is requested using a serving gNB and the measured signal data from the gNB is aggregated using a positioning server.

[0029] Fig.14 The call flow for the network-centric UL / DL measurement procedure for a UE is shown.

[0030] Fig.15 The call flow for the UE-centric UL / DL measurement procedure of the UE is shown.

[0031] Fig.16 An exemplary method performed by a UE for determining a location of the UE according to an aspect of the present disclosure is shown.

[0032] Fig.17 An exemplary method performed by a gNB for determining a location of a UE according to an aspect of the present disclosure is shown.

[0033] Fig.18 and 19 is a simplified block diagram of several sample aspects of an apparatus configured to support position determination and communication as taught herein.

[0034] Elements, phases, steps, and / or actions with the same reference numerals in different figures may correspond to each other (e.g., may be similar or identical to each other). In addition, some elements in various figures are labeled using a numerical prefix followed by a letter or a numerical suffix. Elements with the same numerical prefix but different suffixes may be different instances of the same type of element. A numerical prefix without any suffix is ​​used herein to refer to any element with the numerical prefix. For example, Figure 1A Different instances of UE 102-1, 102-2, 102-3, 102-4, 102-5, and 102-N are shown. Reference to UE 102 then refers to any one of UE 102-1, 102-2, 102-3, 102-4, 102-5, and 102-N. DETAILED DESCRIPTION

[0035] Techniques for calculating the location of a UE, for example, using OTDOA, UTDOA, AOD, AOA, or RTT are disclosed. As discussed herein, radio access technology (RAT)-dependent location solutions are possible, including downlink (DL)-based solutions; downlink (DL) and uplink (UL)-based solutions; and uplink (UL)-based solutions. An example of a DL-based solution may be OTDOA location determination; an example of a UL-based solution may be UTDOA. Round Trip Time (RTT) location determination is an example of a combined DL- and UL-based solution.

[0036] The NG-RAN location determination procedures may be applicable to DL-based location determination methods, UL-based location determination methods, and DL and UL-based location determination methods, such as RTT-based solutions. The procedures may be considered as a general case, where downlink-based (e.g., OTDOA) and uplink-based (e.g., UTDOA) location determination may be supported as special cases (e.g., subsets) of the procedures.

[0037] OTDOA and UTDOA position determination methods are based on time of arrival (TOA) measurements performed on downlink or uplink signals, respectively. Although these methods have been shown to be effective, they still require precise base station time synchronization, which can be difficult to install and maintain.

[0038] Round Trip Time (RTT) positioning uses two-way time of arrival measurements and in principle does not require time synchronization between base stations. However, coarse base station time synchronization may be required in order to reduce interference from multiple transmission points and increase hearability. This time synchronization requirement may be similar to that of Time Division Duplex (TDD) (e.g., it may be synchronization at the microsecond level, rather than nanoseconds as in the case of OTDOA and UTDOA).

[0039] These techniques and other aspects are disclosed in the following description and related drawings directed to specific aspects of the present disclosure. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid blurring the relevant details of the present disclosure.

[0040] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects" of the present disclosure does not require that all aspects of the present disclosure include the discussed feature, advantage, or mode of operation.

[0041] In addition, many aspects are described in terms of sequences of actions performed, for example, by elements of a computing device. It will be appreciated that the various actions described herein may be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of the two. In addition, it may be considered that the sequence of (one or more) actions described herein are fully embodied in any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions, which, when executed, will cause or instruct the associated processor of the device to perform the functionality described herein. Thus, various aspects of the present disclosure may be embodied in many different forms, all of which are considered to be within the scope of the claimed subject matter. In addition, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, "logic" that is "configured to" perform the described actions.

[0042] A mobile device (also referred to herein as a UE) may be mobile, or may be stationary (e.g., at certain times), and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT," "client device," "wireless device," "subscriber equipment," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile station," "mobile device," or a variant thereof. Typically, a UE may communicate with a core network via the RAN, and the UE may be connected to an external network such as the Internet and to other UEs through the core network. Of course, other mechanisms such as connecting to the core network and / or the Internet through a wired access network, a WiFi network (e.g., based on IEEE802.11, etc.), etc., are also possible for the UE. A UE may be embodied by any of a variety of types of devices, including, but not limited to, a printed circuit (PC) card, a compact flash device, an external or internal modem, a wireless or wired phone, a smart phone, a tablet computer, a tracking device, an asset tag, etc. The communication link through which a UE may transmit a signal to the RAN is referred to as an uplink channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link through which the RAN can transmit signals to the UE is called a downlink or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to an uplink / reverse or downlink / forward traffic channel.

[0043] Figure 1AA high-level system architecture of a wireless communication system 10 according to one aspect of the present disclosure is shown. The wireless communication system 10 contains UEs 1 to N (referenced as 102-1 to 102-5). The UEs 102-1 to 102-N may include cellular phones, personal digital assistants (PDAs), pagers, laptop computers, tablet computers, desktop computers, etc. For example, in Figure 1A 1, UE 102-1 and UE 102-2 are shown as cellular feature phones, UE 102-3, 102-4, and 102-5 are shown as cellular touch screen phones or "smart phones", and UE 102-N is shown as a desktop computer or personal computer (often referred to as a "PC"). Figure 1A Only six UEs 102 are shown in FIG. 1 , but in the wireless communication system 10 , the number of UEs 102 may be in the hundreds, thousands, or millions (eg, N may be any value up to or exceeding one million).

[0044] refer to Figure 1A UEs 102-1 to 102-N are configured to Figure 1A 104, 106, and 108 and / or direct wired connections to communicate with one or more access networks (e.g., RAN 135A and 135B, access point 124, etc.). The air interfaces 104 and 106 may conform to a given cellular communication protocol (e.g., code division multiple access (CDMA), evolution data optimization (E-VDO), enhanced high rate packet data (eHRPD), global system for mobile communications (GSM), wideband CDMA (W-CDMA), long term evolution (LTE), LTE unlicensed (LTE-U), 5G new radio (NR), etc.), while the air interface 108 may conform to a wireless local area network (WLAN) protocol (e.g., IEEE 802.11). Both RAN 135A and 135B may include multiple access points that provide services to UEs over air interfaces such as air interfaces 104 and 106. The access points in RAN 135A and 135B may be referred to as access nodes (AN), access points (AP), base stations (BS), Node Bs, eNodeBs, gNBs, etc. For example, an eNodeB (also referred to as an evolved NodeB) is typically a base station that supports wireless access by UE 102 according to an LTE wireless interface defined by 3GPP. As another example, an NR NodeB (also referred to as a gNB or gNodeB) is typically a base station that supports wireless access by UE 102 according to a 5G NR wireless interface. These access points may be terrestrial access points (or ground stations), or satellite access points.

[0045] Both RANs 135A and 135B are configured to be connected to a core network 140, which may perform a variety of functions including routing and connecting circuit-switched (CS) calls between UEs 102 served by the RAN 135A / 135B and other UEs 102 served by the RAN 135A / 135B or UEs served by a different RAN entirely, and may also mediate the exchange of packet-switched (PS) data with external networks such as the Internet 175 and external clients and servers.

[0046] The Internet 175 includes many routing agents and processing agents (not shown for convenience). Figure 1A ). Figure 1A 1, UE 102-N is shown as being directly connected to the Internet 175 (i.e., separate from the core network 140, such as through an Ethernet connection based on WiFi or an 802.11 network). The Internet 175 can thus be used to route and connect packet-switched data communications between UE 102-N and UEs 102-1 to 102-5 via the core network 140.

[0047] Figure 1A Also shown is an access point 124 that is separate from the RAN 135A and 135B. The access point 124 can be connected to the Internet 175 independently of the core network 140 (e.g., via an optical communication system such as FiOS, a cable modem, etc.). The air interface 108 can provide services to the UE 102-4 or UE 102-5 through a local wireless connection (such as, in the example, IEEE 802.11). The UE 102-N is shown as a desktop computer that has a wired connection to the Internet 175, such as a direct connection to a modem or router, which in the example can correspond to the access point 124 itself (e.g., for a WiFi router with both wired and wireless connectivity).

[0048] refer to Figure 1A , the positioning server 120A is shown as being connected to the Internet 175 and the core network 140. The positioning server 120A may be implemented as a plurality of structurally separate servers, or alternatively may each correspond to a single server. As will be described in more detail below, the positioning server 120A is configured to support one or more positioning services for the UE 102, which may be connected to the positioning server 120A via the core network 140 and / or via the Internet 175.

[0049] The following is about Figure 1B and Figure 2An example of a protocol specific implementation of the RAN 135A and 135B and the core network 140 is provided to help illustrate the wireless communication system 10 in more detail. In particular, the components of the RAN 135A and 135B and the core network 140 correspond to components associated with supporting packet-switched (PS) communications, whereby legacy circuit-switched (CS) components may also be present in these networks, but Figure 1B and Figure 2 No legacy CS-specific components are explicitly shown.

[0050] Figure 1B A schematic diagram of a communication system 100 according to an embodiment is shown. The communication system may be Figure 1A 100 is a portion of the communication system 10 shown in . The communication system 100 can be configured to implement the location determination of the UE using a downlink-based solution (e.g., OTDOA), an uplink-based solution (e.g., UTDOA), or a combined downlink-based and uplink-based solution (e.g., RTT). Here, the communication system 100 includes a UE 102 and components of a fifth generation (5G) network including a next generation (NG) radio access network (RAN) (NG-RAN) 135 and a 5G core network (5GC) 140. The 5G network may also be referred to as a new radio (NR) network; the NG-RAN 135 may be referred to as a 5GRAN or as an NR RAN; and the 5GC 140 may be referred to as an NG core network (NGC). The communication system 100 may also use information from a satellite vehicle (SV) 190 for a global navigation satellite system (GNSS), such as GPS, GLONASS, Galileo, or BeiDou, or some other regional or regional satellite positioning system (SPS), such as IRNSS, EGNOS, or WAAS. Additional components of the communication system 100 are described below. The communication system 100 may include additional or alternative components.

[0051] It should be noted that Figure 1BOnly a generalized illustration of the various components is provided, any or all of which may be utilized as appropriate, and each of which may be repeated or omitted as desired. Specifically, although only one UE 102 is shown, it should be understood that many UEs (e.g., hundreds, thousands, millions of UEs, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include a greater or lesser number of SVs 190, gNBs 110, ng-eNBs 114, AMFs 115, external clients 130, and / or other components. The illustrated connections connecting the various components in the communication system 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, components may be rearranged, combined, separated, replaced, and / or omitted, depending on the desired functionality.

[0052] although Figure 1B A 5G-based network is shown, but similar network implementations and configurations may be used for other communication technologies, such as 3G, Long Term Evolution (LTE), etc. The implementations described herein (whether for 5G technology or for other communication technologies and protocols) may be used to configure and support RAT-dependent location solutions, including: downlink (DL)-based solutions; downlink (DL) and uplink (UL)-based solutions; and uplink (UL)-based solutions;

[0053] UE 102 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 secure user plane location (SUPL) enabled terminal (SET), or some other name. In addition, UE 102 may correspond to a cellular phone, a smart phone, a laptop computer, a tablet computer, a PDA, a tracking device, a navigation device, an Internet of Things (IoT) device, or some other portable or portable device. Generally, although not necessarily, UE 102 may use one or more radio access technologies (RATs) to support wireless communications, 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), LTE, 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 102 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. The use of one or more of these RATs may allow UE 102 to communicate with external clients 130 (via Figure 1B Elements of the 5GC 140 not shown in the figure may be used, or via a Gateway Mobile Positioning Center (GMLC) 125) and / or allow an external client 130 to receive positioning information about the UE 102 (e.g., via the GMLC 125).

[0054] UE 102 may include a single entity in a personal area network or may include multiple entities, such as a personal area network in which a user may employ audio, video and / or data I / O devices and / or body sensors and a separate wired or wireless modem. The estimate of the location of UE 102 may be referred to as location, location estimate, location fix, fix, position, location estimate or location fix, and may be geographic, thus providing UE 102 with location coordinates (e.g., latitude and longitude), which may or may not include a height component (e.g., altitude, height above ground or depth below ground, number of floors or number of underground floors). Alternatively, the location of UE 102 may be expressed as a civic location (e.g., as a postal address or a designation of a point or small area in a building (such as a specific room or floor)). The location of UE 102 may also be expressed as an area or volume (defined geographically or in a city) in which the UE 102 is expected to be located with a certain probability or confidence level (e.g., 67% or 95%, etc.). The positioning of UE102 may also be a relative positioning, which includes, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location, which may be defined geographically or in terms of a city or with reference to a point, area, or volume indicated on a map, floor plan, or building plan. In the description contained herein, unless otherwise indicated, the use of the term "positioning" may include any of these variations. When calculating the positioning of the UE, the local x, y, and possibly z coordinates are typically solved first, and then the local coordinates are converted to absolute coordinates (e.g., latitude, longitude, and height above or below mean sea level) as needed.

[0055] Figure 1BThe base stations (BSs) in the NG-RAN 135 shown in FIG. 1 include NR NodeBs also referred to as gNBs 110-1, 110-2, and 110-3 (collectively referred to herein as gNBs 110). Pairs of gNBs 110 in the NG-RAN 135 may be connected to each other, e.g., as Figure 1B As shown, the UE 102 may be directly connected or indirectly connected via other gNBs 110. Access to the 5G network is provided to the UE 102 via wireless communications between the UE 102 and one or more of the gNBs 110, which may use 5G NR to provide wireless communication access to the 5GC 140 on behalf of the UE 102. 5G NR radio access may also be referred to as NR radio access or as 5G radio access, and may be as defined by the Third Generation Partnership Project (3GPP). Figure 1B , it is assumed that the serving gNB for UE 102 is gNB 110-1, but if UE 102 moves to another location, other gNBs (e.g., gNB 110-2 and / or gNB 110-3) may serve as the serving gNB, or may serve as secondary gNBs to provide additional throughput and bandwidth to UE 102.

[0056] Figure 1B The base stations (BSs) in the NG-RAN 135 shown in FIG. 1 may also be or alternatively include next generation evolved Node Bs, also referred to as ng-eNBs 114. The ng-eNBs 114 may be connected to one or more gNBs 110 in the NG-RAN 135, for example, directly or indirectly via other gNBs 110 and / or other ng-eNBs. The ng-eNBs 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UEs 102. Figure 1B Some gNBs 110 (e.g., gNB 110-2) and / or ng-eNBs 114 in the UE 100 may be configured to function as positioning-only beacons that may transmit signals (e.g., PRS signals) and / or may broadcast assistance data to assist in positioning UE 102, but may not receive signals from UE 102 or from other UEs. Figure 1B Only one ng-eNB 114 is shown in FIG, but some embodiments may include multiple ng-eNBs 114.

[0057] As will be discussed in more detail below, in some embodiments, the gNB 110 and / or ng-eNB 114 (alone or in combination with other modules / units of the communication system 100) may be configured to send or broadcast positioning-related information (e.g., position determination reference signals (PRS) and / or positioning-related assistance data) with an increased amount of resources (e.g., in the case of PRS, a higher bandwidth, a longer duration, and / or a shorter periodicity) in response to receiving (e.g., from the UE 102 or LMF 120) a request to increase the amount of positioning-related information (e.g., position determination reference signals (PRS) and / or positioning-related assistance data). As noted, although Figure 1B Nodes configured to communicate according to 5G NR and LTE communication protocols for NG-RAN 135 are depicted, but nodes configured to communicate according to other communication protocols may be used, such as, for example, the LTE protocol for an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) or the IEEE 802.11x protocol for a WLAN. For example, in a 4G Evolved Packet System (EPS) that provides LTE wireless access to UE 102, the RAN may include an E-UTRAN that may include base stations including evolved Node Bs (eNBs) that support 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 LTE protocol is used in conjunction with the UE 102. Figure 1B In the present invention, E-UTRAN corresponds to NG-RAN 135 and EPC corresponds to 5GC 140. The methods and techniques described herein for supporting RAT-related location solutions (e.g., including downlink (DL)-based solutions; downlink (DL) and uplink (UL)-based solutions; and uplink (UL)-based solutions) may be applicable to such other networks.

[0058] The gNB 110 and ng-eNB 114 may communicate with an access and mobility management function (AMF) 115, which, for position determination functionality, communicates with a location management function (LMF) 120. The AMF 115 may support mobility of the UE 102, including cell changes and handovers, and may participate in supporting signaling connections with the UE 102 and may support data and voice bearers for the UE 102. The LMF 120 may support position determination for the UE 102 when the UE accesses the NG-RAN 135, and may support position determination procedures / methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), Angle of Arrival (AOA), Angle of Departure (AOD), and / or other position determination procedures. LMF 120 may also process positioning service requests for UE 102, for example, received from AMF 115 or from GMLC 125. LMF 120 may be connected to AMF 115 and / or GMLC 125. In some embodiments, a node / system implementing LMF 120 may additionally or alternatively implement other types of positioning support modules, such as an enhanced serving mobile positioning center (E-SMLC). It should be noted that in some embodiments, at least part of the position determination functionality (including the derivation of the positioning of UE 102) may be performed at UE 102 (e.g., using signal measurements obtained by UE 102 for signals transmitted by wireless nodes such as gNB 110 and ng-eNB 114, and assistance data provided to UE 102, for example, by LMF 120).

[0059] A gateway mobile location center (GMLC) 125 may support location requests for UE 102 received from an external client 130 and may forward such location requests to AMF 115 for forwarding to LMF 120 via AMF 115 or may forward such location requests directly to LMF 120. A location response (e.g., containing a location estimate for UE 102) from LMF 120 may similarly be returned to GMLC 125 directly or via AMF 115, and GMLC 125 may then return the location response (e.g., containing a location estimate) to the external client 130. GMLC 125 is shown connected to Figure 1B The 5GC 140 may support both the AMF 115 and the LMF 120, but in some embodiments the 5GC 140 may support only one of these connections.

[0060] A user plane function (UPF) 128 may support voice and data bearers for UE 102 and may enable voice and data access of UE 102 to other networks such as the Internet 175. UPF 128 functions may include: external protocol data unit (PDU) session points for interconnection with data networks, packet (e.g., Internet Protocol (IP)) routing and forwarding, packet inspection and user plane portion of policy rule enforcement, quality of service (QoS) handling for the user plane, downlink packet buffering, and downlink data notification triggering. UPF 128 may be connected to SLP 129 to enable support for positioning of UE 102 using SUPL. SLP 129 may be further connected to or accessible from external client 130.

[0061] As shown, a session management function (SMF) 126 connects AMF 115 and UPF 128. SMF 126 may have the ability to control both local UPFs and central UPFs within a PDU session. SMF 126 may manage the establishment, modification, and release of PDU sessions for UE 102, perform IP address configuration and management for UE 102, act as a Dynamic Host Configuration Protocol (DHCP) server for UE 102, and select and control UPF 128 on behalf of UE 102.

[0062] The external client 130 may be connected to the core network 140 via the GMLC 125 and / or the SLP 129. The external client 130 may alternatively be connected to the core network 140 and / or the positioning server 120A via the Internet 175, which may be, for example, an SLP located outside the 5GCN 140. The external client 130 may be a server, a web server, or a user device such as a personal computer, a UE, etc.

[0063] As in Figure 1B As further shown in FIG. 1 , LMF 120 may communicate with gNB 110 and / or with ng-eNB 114 using a new radio position determination protocol A (which may be referred to as NPPa or NRPPa), which may be defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages may be transmitted between gNB 110 and LMF 120 and / or between ng-eNB 114 and LMF 120 via AMF 115. As shown in FIG. Figure 1BAs further shown in , the LMF 120 and the UE 102 may communicate using the LTE Position Determination Protocol (LPP), which may be defined in 3GPP TS 36.355. The LMF 120 and the UE 102 may also or alternatively communicate using a New Radio Position Determination Protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of the LPP. Here, LPP and / or NPP messages may be transmitted between the UE 102 and the LMF 120 via the AMF 115 and the serving gNB 110-1 or the serving ng-eNB 114 for the UE 102. For example, the LPP and / or NPP messages may be transmitted between the LMF 120 and the AMF 115 using a service operation based on the Hypertext Transfer Protocol (HTTP), and the LPP messages may be transmitted between the AMF 115 and the UE 102 using a 5G Non-Access Stratum (NAS) protocol. The LPP and / or NPP protocols may be used to support position determination of UE 102 using UE-assisted and / or UE-based location methods, such as A-GNSS, RTK, OTDOA, angle of arrival (AOA), angle of departure (AOD), and / or ECID. The NRPPa protocol may be used to support position determination of UE 102 using network-based location methods (such as ECID) (e.g., when used with measurements obtained by gNB 110 or ng-eNB 114) and / or may be used by LMF 120 to obtain positioning-related information from gNB 110 and / or ng-eNB 114, such as parameters defining PRS transmissions from gNB 110 and / or ng-eNB 114.

[0064] Using UE-assisted location methods, UE 102 may obtain positioning measurements and transmit the measurements to a positioning server (e.g., LMF 120 or SLP 129) for use in computing a positioning estimate for UE 102. For example, the positioning measurements may include one or more of: received signal strength indication (RSSI), round-trip signal propagation time (RTT) (which may also be more simply referred to as round-trip time), reference signal time difference (RSTD), reference signal received power (RSRP), reference signal received quality (RSRQ), AOA, and / or AOD for gNB 110, ng-eNB 114, and / or WLAN access point (AP). The positioning measurements may also or alternatively include measurements of GNSS pseudoranges, code phase, and / or carrier phase for SV 190. With a UE-based location method, UE 102 may obtain positioning measurements (e.g., which may be the same or similar to positioning measurements for a UE-assisted location method) and may calculate the position of UE 102 (e.g., with assistance data received from a positioning server such as LMF 120 or broadcast by gNB 110, ng-eNB 114, or other base stations or APs). With a network-based location method, one or more base stations (e.g., gNB 110 and / or ng-eNB 114) or APs may obtain positioning measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AOA, or time of arrival (TOA) for signals sent by UE 102) and / or may receive measurements obtained by UE 102 and may transmit the measurements to a positioning server (e.g., LMF 120) to calculate a positioning estimate for UE 102.

[0065] The information provided to LMF 120 by gNB 110 and / or ng-eNB 114 using NRPPa may include timing and configuration information for PRS transmission and positioning coordinates. LMF 120 may then provide some or all of this information to UE 102 as assistance data in LPP and / or NPP messages via NG-RAN 135 and 5GC 140.

[0066] Depending on the desired functionality, the LPP or NPP message transmitted from the LMF 120 to the UE 102 may instruct the UE 102 to perform any of a variety of operations. For example, the LPP or NPP message may include instructions for causing the UE 102 to obtain measurements of GNSS (or A-GNSS), WLAN, and / or OTDOA (or some other location determination method). In the case of OTDOA, the LPP or NPP message may instruct the UE 102 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a particular cell supported by a particular gNB 110 and / or ng-eNB 114 (or supported by some other type of base station (such as an eNB or WiFi AP)). The RSTD measurement may include the difference in time between a signal (e.g., a PRS signal) transmitted or broadcast by one gNB 110 and a similar signal transmitted by another gNB 110 arriving at the UE 102. UE 102 may send the measurements back to LMF 120 in an LPP or NPP message (e.g., within a 5G NAS message) via serving gNB 110-1 (or serving ng-eNB 114) and AMF 115.

[0067] As mentioned, although the communication system 100 is described with respect to 5G technology, the communication system 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 102 (e.g., to implement voice, data, location determination, and other functionality). In some such embodiments, the 5GC 140 may be configured to control different air interfaces. For example, in some embodiments, the 5GC 140 may directly or using a non-3GPP interworking function (N3IWF, not implemented in the 5GC 140) in the 5GC 140 to control the different air interfaces. Figure 1B11) is connected to the WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for the UE 102 and may include one or more WiFi APs. Here, the N3IWF may be connected to the WLAN and other elements in the 5GC 140, such as the AMF 115. In some other embodiments, both the NG-RAN 135 and the 5GC 140 may be replaced by other RANs and other core networks. For example, in the EPS, the NG-RAN 135 may be replaced by an E-UTRAN containing an eNB, and the 5GC 140 may be replaced by an EPC containing a mobile management entity (MME) replacing the AMF 115, an E-SMLC replacing the LMF 120, and a GMLC similar to the GMLC 125. In this EPS, the E-SMLC may use LPPA (LPPa, as defined in 3GPP TS 36.455) instead of NRPPa to transmit positioning information to and receive positioning information from the eNB in ​​the E-UTRAN, and may use LPP to support the location determination of the UE 102. In these other embodiments, RAT-dependent location solutions for UE 102 (e.g., including downlink (DL)-based solutions, downlink (DL) and uplink (UL)-based solutions, and uplink (UL)-based solutions) may be supported in a manner similar to that described herein for 5G networks, with the difference that the functions and processes described herein for gNB 110, ng-eNB 114, AMF 115, and LMF 120 may in some cases be applied alternatively to other network elements such as eNB, WiFi AP, MME, and E-SMLC.

[0068] To support certain location methods such as OTDOA or UTDOA, and to transmit or PRS or other signals for location determination of UE 102, the base stations may be synchronized. In a synchronized NR network, the transmit timing of gNBs 110 may be synchronized such that each gNB 110 has the same transmit timing as every other gNB 110 to a high level of accuracy (e.g., 50 nanoseconds or less). Alternatively, the gNBs 110 may be synchronized at a radio frame or subframe level such that each gNB 110 transmits a radio frame or subframe during the same duration as every other gNB 110 (e.g., such that each gNB 110 starts and ends transmitting a radio frame or subframe at almost exactly the same time as every other gNB 110), but without necessarily maintaining the same count or numbering of the radio frames or subframes. For example, when one gNB 110 sends a subframe or radio frame with a count or number of zero (which may be the first radio frame or subframe in a partially periodically repeating sequence of radio frames or subframes), another gNB 110 may send a radio frame or subframe with a different number or count (such as one, ten, one hundred, etc.).

[0069] Synchronization of the transmit timing of the ng-eNB 114 in the NG-RAN 135 may be supported in a manner similar to the synchronization of the gNB 110, but because the ng-eNB 114 may typically use a different frequency than the gNB 110 (to avoid interference), the ng-eNB 114 may not always be synchronized with the gNB 110. Synchronization of the gNB 110 with the ng-eNB 114 may be achieved using a GPS receiver or a GNSS receiver in each of the gNB 110 and the ng-eNB 114, or by other means, such as using the IEEE 1588 Precision Time Protocol.

[0070] In the case of on-demand scheduling of PRS, base stations (BSs) such as gNB 110 and ng-eNB 114 in the communication system 100 or eNBs in the EPS may each transmit PRS using a low bandwidth and a low duration of PRS on a continuous background basis (e.g., 1 or 2 subframes per location determination occasion (occasion) and using a 1.4 MHz bandwidth in the case of an eNB), and temporarily switch to a high bandwidth (e.g., 20 MHz) and / or a high duration (e.g., 6 subframes per location determination occasion) upon request by the UE 102. To support fast switching between low PRS resource allocation and high PRS resource allocation, a UE 102 request for high PRS resource allocation may be transmitted to a serving BS for the UE 102 (e.g., a serving gNB 110 or ng-eNB 114 for the UE 102 to access the NG-RAN 135, or a serving eNB for the UE 102 to access the E-UTRAN) using a radio resource control (RRC) protocol. The serving BS may be configured to transmit or communicate the request to a neighboring BS. In the case where PRS is transmitted for some cells using a frequency and / or RAT different from the serving cell for UE 102, the request for high PRS resource allocation may be combined with the request for measurement gaps by UE 102. The positioning server (e.g., SLP 129, E-SMLC for EPS, or LMF 120 for 5GC 140) may then provide the UE 102 with the background low resource PRS configuration for reference cells and neighboring cells for OTDOA position determination, and may also indicate whether switching to high PRS resource allocation is supported. Alternatively, this information may be provided to UE 102 from gNB 110 via periodic broadcasts (e.g., broadcast in positioning-related SIBs). In the case where switching to high PRS resource allocation is supported, the positioning server (or gNB 110 in the case of information transmission via broadcast) may indicate to UE 102 the types of supported increased PRS resource allocation, such as increased PRS bandwidth, increased PRS subframes per position determination opportunity, and / or the availability of UL frequencies for DL ​​PRS transmission (e.g., in the case where the UL frequency is temporarily reassigned to DL PRS transmission). For each supported type of increased PRS resource allocation, the positioning server (or gNB 110) may also indicate the available amount of increased PRS resource allocation, such as the available (or maximum) PRS bandwidth value, the available (or maximum) number of PRS subframes per position determination opportunity, and / or one or more DL PRS configurations that can be used for the UL carrier frequency.

[0071] When supporting switching to high PRS resource allocation, UE 102 may transmit an RRC protocol request to a serving BS (e.g., a serving eNB for E-UTRAN access or a serving gNB 110 or ng-eNB 114 for NG-RAN 135 access), and include, for example, PRS frequencies that UE 102 can measure, a maximum PRS resource allocation that UE 102 can measure (e.g., a maximum PRS bandwidth and / or a maximum number of subframes per PRS position determination opportunity), whether UE 102 supports measurement of PRS on an uplink frequency (e.g., an uplink frequency for frequency division duplexing (FDD)), and / or whether a measurement gap is required. For example, if the positioning server has indicated to UE 102 an available amount of increased PRS resource allocation, UE 102 may indicate a maximum increased PRS resource allocation that UE 102 can measure within the available amount. UE 102 may also include identification of reference cells and neighboring cells for OTDOA, which may have been previously provided to UE 102 by a positioning server (e.g., LMF 120) when requesting OTDOA RSTD, RSRP, or receive time-transmit time (Rx-Tx) measurements from UE 102. The serving BS may then transmit a request for increased resource allocation (e.g., higher PRS bandwidth, more subframes per PRS position determination opportunity, and / or use of PRS broadcasts using uplink frequency) to the neighbor BSs indicated by UE 102 for the reference cell and neighboring cells (and / or to other neighbor BSs that are capable of supporting the increased PRS resource configuration). The serving BS may also alternatively transmit an RRC confirmation to the UE 102 to confirm that the UE 102 request for increased PRS resource allocation will be supported, and may provide configuration parameters for increased PRS transmission, such as increased PRS bandwidth, increased number of PRS subframes per position determination opportunity, use of specific subframes and bandwidth for UL frequency, and / or identification of cells in which increased PRS transmission will be supported. The UE 102 will then use the increased PRS resource allocation to obtain PRS measurements.

[0072] Figure 2 The invention is shown in accordance with the embodiment Figure 1A The communication system 10 and Figure 1B Schematic diagram of the location determination architecture of the communication system 100 in FIG. Figure 2 The location determination architecture shown in Figure 1B A subset of the architecture shown in FIG. 1 is applicable to NG-RAN 135 and is shown Figure 1B135 and may be used to support location methods that rely on NRRAT. As shown, LMF 120 may communicate with an enhanced serving mobile location center (E-SMLC) 127 (e.g., which may be part of a separate EPC) and a secure user plane location (SUPL) location platform (SLP) 129.

[0073] It should be noted that both gNB 110 and ng-eNB 114 may not always be present in NG-RAN 135. In addition, when both gNB 110 and ng-eNB 114 are present, the NG-C interface with AMF 115 may exist only for one of them.

[0074] As shown, the gNB 110 may be allowed to control one or more transmit points (TPs) 111, such as remote radio heads or broadcast-only TPs, to provide improved support for DL ​​location methods such as OTDOA, AOD, RTT, or ECID. Additionally, the gNB 110 may be allowed to control one or more receive points (RPs) 113, such as remote radio heads or internal location measurement units (LMUs), to perform UL measurements for location methods such as uplink time difference of arrival (UTDOA), AOA, RTT, or ECID. In some embodiments, the TPs 111 and RPs 113 may be combined into a transmit receive point (TRP) (not shown in FIG. 1 ). Figure 2 15 ), which performs the functions of both TP 111 and RP 113. TP 111, RP 113 and / or TRP may be part of a distributed unit (DU, also referred to as gNB-DU) in gNB 110, or may include the distributed unit, which manages UL and / or DL ​​transmission and reception of one or more cells according to 5G NR. In addition, gNB 110 may include a positioning management component (LMC) 117 (also referred to as a "local LMF"), which may be a positioning server (or positioning server function) enabled in a serving gNB 110 or a neighboring gNB 110 for UE 102 to support location determination of a target UE 102. The location determination of UE 102 by LMC 117 in serving gNB or neighboring gNB 110 may be used to provide positioning services to UE 102, serving AMF 115 or LMF 120, and improve NG-RAN operation, for example, by assisting UE in switching and distribution among available NG-RAN nodes.

[0075] LMC 117 may support location determination for UE 102 in a similar or identical manner as LMF 120, and may support the same or similar location methods (e.g., OTDOA, RTT, AOD, AOA, UTDOA, ECID, A-GNSS, RTK). LMC 117 may be part of a central unit (CU, also referred to as gNB-CU) in gNB 110, where the CU may also manage and control the overall operation of gNB 110 and act as an endpoint for RRC communications with UE 102, Xn communications with another gNB 110, NGAP communications with AMF 154, and / or NRPPa communications with LMF 120. Alternatively, LMC 117 may be a separate element in gNB 110 and connected to the CU in gNB 110 (e.g., using an F1 interface). For example, LMC 117 may request positioning measurements from UE 102, for example using RRC or LPP, may manage UL positioning measurements made by one or more gNBs 110 of UE 102, and may provide cell database assistance data and / or UL positioning measurements to UE 102 for location methods such as OTDOA, AOD, and RTT. LMC 117 may further manage static and dynamic scheduling of PRS broadcasts and broadcasts of assistance data by one or more gNBs 110, interact with neighboring gNBs 110 (e.g., using XnAP and NRPPa) to coordinate positioning support, for example, exchanging positioning measurements of UE 102 or coordinating changes in PRS transmission. LMC 117 may determine a positioning estimate for UE 102. LMC 117 may provide positioning service capabilities to a serving AMF (eg, using Next Generation Application Protocol (NGAP)), to LMF 120 (eg, using NRPPa), and to UE 102 (eg, using RRC or LPP).

[0076] Peer-level LMCs 117 may communicate using the Xn Application Protocol (XnAP) or positioning-specific protocols above the XnAP to coordinate support for these functions, for example, to enable continued positioning of UE 102 after UE 102 switches to a new serving gNB 110.

[0077] Thus, the LMC 117 may allow or support NG-RAN 135 determination of the positioning of the UE 102, which may be requested by the UE 102 (e.g., using RRC or LPP), by the serving AMF 154 (e.g., using NGAP), by another gNB 110 (e.g., using XnAP), or by the LMF 120 (e.g., using NRPPa). This capability may allow positioning support without the need for the LMF 120 (or LMF 120 in the 5GC 140). Figure 1B), and can also be used to reduce the latency of position determination (this is because the NG-RAN 135 is closer to the UE 102 than the LMF 120) and to offload positioning support from the LMF 120.

[0078] The time intervals of communication resources in 5G NR (or LTE) may be organized according to radio frames, each having a duration of 10 milliseconds (ms). Radio frames may be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame may contain 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 millisecond. The subframes may be further divided into time slots, where the time slot duration and the number of time slots per subframe may depend on a parameter set (including OFDM subcarrier spacing and symbol length). In 5G NR, for example, the time slot length varies depending on the parameter set; typically, the time slot length becomes shorter as the subcarrier spacing becomes wider. A time slot may consist of 14 OFDM symbols. Micro slots may also be supported, which may be as small as 2 OFDM symbols and have a variable length. In some cases, a time slot may be the smallest scheduling unit of the wireless communication system 100 and may be referred to as a transmission time interval (TTI).

[0079] Figure 3 Several sample components (represented by corresponding boxes) that may be incorporated into apparatus 302, apparatus 304, and apparatus 306 (e.g., corresponding to UE 102, base station (e.g., gNB 110), and network entity or positioning server, respectively) to support operations as disclosed herein are shown. As an example, apparatus 302 may correspond to UE 102, apparatus 304 may correspond to any of gNB 110, and apparatus 306 may correspond to LMF 120, LMC 117, E-SMLC 127, SLP 129, or GMLC 125. It should be understood that in different embodiments (e.g., in an ASIC, in an SoC, etc.), the components may be implemented in different types of apparatuses. The components shown may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in the system may include components similar to the components described to provide similar functionality. Moreover, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

[0080] Each of the apparatuses 302 and 304 includes at least one wireless communication device (represented by communication devices 308 and 314) for communicating with other nodes via at least one designated radio access technology (RAT) (e.g., LTE, 5G NR). Each communication device 308 includes at least one transmitter (represented by transmitter 310) for sending and encoding signals (e.g., messages, indications, information, etc.) and at least one receiver (represented by receiver 312) for receiving and decoding signals (e.g., messages, indications, information, pilots, etc.). Each communication device 314 includes at least one transmitter (represented by transmitter 316) for sending signals (e.g., messages, indications, information, pilots, etc.) and at least one receiver (represented by receiver 318) for receiving signals (e.g., messages, indications, information, etc.).

[0081] The transmitter and receiver may comprise an integrated device (e.g., a transmitter circuit and a receiver circuit embodied as a single communication device) in some embodiments, may comprise a separate transmitter device and a separate receiver device in some embodiments, or may be embodied in other ways in other embodiments. The wireless communication device (e.g., one of the plurality of wireless communication devices) of apparatus 304 may also include a network listening module (NLM) for performing various measurements, etc.

[0082] Devices 304 and 306 include at least one communication device (represented by communication device 320 and communication device 326) for communicating with other nodes. For example, communication device 326 may include a network interface (e.g., one or more network access ports) configured to communicate with one or more network entities via a wire-based backhaul connection or a wireless backhaul connection. In some aspects, communication device 326 may be implemented as a transceiver configured to support wire-based signal communication or wireless signal communication. Such communication may involve, for example, transmitting and receiving: messages, parameters, or other types of information. Therefore, in Figure 3 In the example of , the communication device 326 is shown to include a transmitter 328 and a receiver 330 (e.g., a network access port for transmitting and receiving). Similarly, the communication device 320 may include a network interface configured to communicate with one or more network entities via a wire-based backhaul or a wireless backhaul. Like the communication device 326, the communication device 320 is shown to include a transmitter 322 and a receiver 324.

[0083] Apparatus 302, 304, and 306 also include other components that may be used in conjunction with operations as disclosed herein. Apparatus 302 includes a processing system 332 for providing functionality, such as related to RTT measurements in licensed or unlicensed frequency bands as disclosed herein and for providing other processing functionality. Apparatus 304 includes a processing system 334 for providing functionality, such as related to RTT measurements in licensed or unlicensed frequency bands as disclosed herein and for providing other processing functionality. Apparatus 306 includes a processing system 336 for providing functionality, such as related to RTT measurements in licensed or unlicensed frequency bands as disclosed herein and for providing other processing functionality. In one aspect, processing systems 332, 334, and 336 may include, for example, one or more general purpose processors, multi-core processors, application specific integrated circuits (ASICs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), or other programmable logic devices or processing circuits.

[0084] The apparatuses 302, 304, and 306 include memory components 338, 340, and 342 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In addition, the apparatuses 302, 304, and 306 include user interface devices 344, 346, and 348, respectively, for providing indications (e.g., auditory and / or visual indications) to a user and / or for receiving user input (e.g., when a user actuates a sensing device such as a keypad, a touch screen, a microphone, etc.).

[0085] For convenience, devices 302, 304 and / or 306 are Figure 3 1 and 2. The blocks shown in FIG. 1 include various components that can be configured according to the various examples described herein. However, it should be understood that the blocks shown may have different functionality in different designs.

[0086] Can be implemented in various ways Figure 3 In some embodiments, Figure 3The components may be implemented in one or more circuits, such as one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component to store information or executable code used by the circuit to provide functionality. For example, some or all of the functionality represented by blocks 308, 332, 338, and 344 may be implemented by the processor and (one or more) memory components of device 302 (e.g., by the execution of appropriate code and / or by the appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 314, 320, 334, 340, and 346 may be implemented by the processor and (one or more) memory components of device 304 (e.g., by the execution of appropriate code and / or by the appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 326, 336, 342, and 348 may be implemented by the processor and (one or more) memory components of device 306 (e.g., by the execution of appropriate code and / or by the appropriate configuration of the processor component).

[0087] In one aspect, apparatus 304 may correspond to a “small cell” or home gNB, such as Figure 2 Device 302 may send and receive messages including information related to various types of communications (e.g., voice, data, multimedia services, associated control signaling, etc.) via wireless link 360 with device 304. Wireless link 360 may be used over a communication medium of interest (on Figure 3 The communication medium may be operated by a communication device (shown by way of example as medium 362) that may be shared with other communications and other RATs. This type of medium may be composed of one or more frequency, time, and / or spatial communication resources (e.g., covering one or more channels across one or more carriers) associated with communication between one or more transmitter / receiver pairs (such as device 304 and device 302 for medium 362).

[0088] As a specific example, medium 362 may correspond to at least a portion of an unlicensed band shared with other RANs and / or other APs and UEs. In general, devices 302 and 304 may operate via wireless link 360 according to one or more radio access types such as LTE, LTE-U, or 5G NR, depending on the network in which devices 302 and 304 are deployed. These networks may include, for example, different variants of CDMA networks (e.g., LTE networks, 5G NR networks, etc.), time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, and the like. Although various licensed frequency bands have been reserved for wireless communications (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), certain communications networks (particularly those that employ small cell base stations) have expanded operations into unlicensed frequency bands, such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies (most notably IEEE 802.11x WLAN technology, commonly referred to as “Wi-Fi,” and LTE technology in unlicensed spectrum, commonly referred to as “LTE-U” or “MuLTEFire”).

[0089] Apparatus 302 may also include an RTT measurement component 352 operable to obtain positioning-related measurements of signals (e.g., RTT or other signals) sent by a base station or AP (e.g., any of gNBs 110) in accordance with techniques described herein. Positioning-related measurements may include measurements of signal propagation time or RTT between UE 102 and a base station or AP (such as any of gNBs 110).

[0090] Devices 304 and 306 may each include an RTT measurement component 354 and 356, respectively, in accordance with the techniques described herein that may be used to determine a positioning estimate for UE 102 (e.g., device 302) based on positioning-related measurements provided by UE 102 and / or a base station or AP, such as any of gNBs 110. Positioning-related measurements obtained by UE 102 may include measurements of signal propagation time, or RTT, between UE 102 and a base station or AP, such as any of gNBs 110. Positioning-related measurements obtained by any of gNBs 110 (e.g., device 304) may include measurements of signal propagation time, or RTT, between UE 102 and a base station or AP, such as any of gNBs 110.

[0091] Figure 4A simplified environment for illustrating an exemplary technique for determining the location of a UE 102 is shown in FIG. UE 102 may wirelessly communicate with multiple gNBs 110 using radio frequency (RF) signals and standardized protocols for modulation of the RF signals and exchange of information packets. By extracting different types of information from the exchanged signals and utilizing the layout of the network (i.e., network geometry), UE 102 may determine its location in a predefined reference coordinate system. Figure 4 As shown in , UE 102 may specify its position (x, y) using a two-dimensional coordinate system; however, the aspects disclosed herein are not limited thereto and may also be adapted to use a three-dimensional coordinate system to determine position where additional dimensions are required. Figure 4 Three gNBs 110 are shown, but aspects may utilize additional gNBs.

[0092] To determine its location (x, y), UE 102 may first need to determine the network geometry. The network geometry may include the location of each of gNB 110 in a reference coordinate system ((x, y)). k ,y k ), where k=1, 2, 3). The network geometry may be provided to the UE 102 in any manner, such as, for example, providing such information in a beacon signal, providing the information using a dedicated server located outside the external network, providing the information using a uniform resource identifier, and the like.

[0093] UE 102 may then determine the distance (d k , where k = 1, 2, 3). As will be described in more detail below, there are methods for estimating these distances (d ) by exploiting different characteristics of the RF signals exchanged between UE 102 and gNB 110. k As will be discussed below, such characteristics may include the round trip time of the signal and / or the strength of the signal (RSSI).

[0094] In other aspects, other sources of information not associated with gNB 110 may be used to partially determine or refine the distance (d k ). For example, other positioning systems such as GPS may be used to provide k (It should be noted that in the expected operating environment (indoors, metropolitan areas, etc.), GPS may not have sufficient signal to provide a rough estimate of d k However, GPS signals may be combined with other information to assist in the position determination process). Other relative position determination devices may reside in the UE 102, which may be used as a basis for providing a rough estimate of relative position and / or direction (e.g., an onboard accelerometer).

[0095] Once each distance is determined, the UE 102 can then solve for its position (x, y) by using a variety of known geometric techniques such as, for example, trilateration. Figure 4 It can be seen from FIG. 1 that the location of UE 102 is ideally at the intersection of the circles drawn using dotted lines. Each circle passes through a radius d k and center (x k ,y k ) where k = 1, 2, 3. In practice, due to noise and other errors in the networking system, the intersection of these circles may not be at a single point.

[0096] Determining the distance between UE 102 and each gNB 110 may involve using timing information of RF signals. In one aspect, determining the RTT of signals exchanged between UE 102 and gNB 110 and converting it into a distance (d k ). RTT techniques measure the time between transmitting a data packet and receiving a response. These methods utilize calibration to remove any processing delays. In some environments, it may be assumed that the processing delays of UE 102 and gNB 110 are the same. However, this assumption may not actually be true.

[0097] The position estimate (e.g., for UE 102) may be referred to by other names, such as a position estimate, a position fix, a position determination, a position fix, a fix, etc. The position estimate may be geographic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be urban and include a street address, a postal address, or some other verbal description of a location. The position estimate may be further defined relative to some other known location, or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). The position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default confidence level).

[0098] Figure 5A and 5B Schematic diagrams illustrating exemplary timing within the RTT occurring during a radio probe request and response initiated by UE 102 and gNB 110, respectively. In one aspect, the response may take the form of an acknowledgment packet (ACK); however, any type of response packet will be consistent with various aspects of the present disclosure. For example, an RTS (Request to Send) Send packet and / or a CTS (Clear to Send) response packet may be appropriate.

[0099] like Figure 5AAs shown in FIG. 1 , to measure RTT with respect to a given gNB (e.g., any of gNBs 110), UE 102 may transmit a directional probe request (e.g., an uplink RTT reference signal) to the gNB and record the time (timestamp) at which the probe request packet was transmitted (t TX packet), as shown on the UE timeline. At propagation time t from UE 102 to gNB P Afterwards, the gNB will receive the packet. The gNB may then process the directional sounding request and may send an ACK (e.g., a downlink RTT reference signal) back to the UE 102 after some processing time Δ, which is sometimes referred to herein as a processing delay, such as Figure 5A As shown on the gNB timeline in Figure 2. At the second propagation time t p After that, UE 102 may record the time (timestamp) of receiving the ACK packet (t RX ACK), as shown on the UE timeline. UE 102 or another entity such as a positioning server may then determine the total RTT as the time difference t RX ACK-t TX The net RTT (ie, the two-way propagation time) may be determined based on the difference between the gross RTT and the processing delay Δ.

[0100] Figure 5B Similar to Figure 5A , but it shows that to measure RTT relative to the UE, the gNB (e.g., any of gNB 110) may transmit a directional sounding request (e.g., a downlink RTT reference signal) to the UE and record the time (timestamp) at which the sounding request packet was transmitted (t TX The propagation time t from the gNB to the UE 102 is P Afterwards, UE 102 will receive the packet. UE 102 may then process the directional sounding request and may send an ACK (e.g., uplink RTT reference signal) back to the gNB after some processing time Δ (e.g., processing delay), as in Figure 5B As shown on the UE timeline in the second propagation time t p After that, the gNB can record the time (timestamp) of receiving the ACK packet (t RX ACK), as shown on the gNB timeline. The gNB or another entity such as UE 102 or a positioning server may then determine the net RTT as the time difference t RX ACK-t TX The net RTT (ie, the two-way propagation time) may be determined based on the difference between the gross RTT and the processing delay Δ.

[0101] Current location positioning methods used in cellular networks, such as Observed Time Difference of Arrival (OTDOA) and Uplink Time Difference of Arrival (UTDOA), require fine (e.g., sub-microsecond) timing synchronization across base stations in the network. On the other hand, RTT-based methods require only coarse timing synchronization (within the cyclic prefix (CP) duration of an orthogonal frequency division multiple access (OFDM) symbol). The present disclosure describes a process that can be implemented in a 5G NR network with its independent subframe structure.

[0102] In 5G NR, precise timing synchronization across the network is not required. Instead, it is sufficient to have (coarse) CP-level time synchronization across gNBs. Coarse time synchronization enables low usage of RTT measurement signals, which mitigates inter-cell interference. Inter-cell interference mitigation ensures deep penetration of RTT signals, which enables multiple independent timing measurements across different gNBs and, therefore, more accurate position determination.

[0103] In network-centric RTT estimation, a serving gNB (one of gNBs 110) instructs a UE (e.g., UE 102) to look for RTT signals from one or more gNBs (one or more of gNBs 110). One of the more gNBs sends an RTT measurement signal on a low-utilization resource allocated by the network (e.g., positioning server 120). The UE records the arrival time Δt(i) of each RTT measurement signal relative to its current DL timing and sends (one or more) common or individual RTT response messages to one or more gNBs (when instructed by its serving gNB). The RTT response message directed to a specific gNB includes (one or more) timestamps (Δt(i)+TA) in its payload, where Δt(i) indicates the arrival time of the RTT measurement signal received from that gNB and TA indicates the uplink timing adjustment parameter of the UE. In the case of a common RTT response message, the set of timestamps (Δt(i)+TA) may be reorganized in other ways known to those of ordinary skill in the art. The network may allocate low usage resources for the UE to send (one or more) RTT response messages. In any case, each gNB that receives the RTT response message records its arrival time ΔT(i) relative to the DL time reference of the gNB. The gNB can calculate the RTT between the UE and itself by adding the timestamp value (Δt(i)+TA) to the arrival time ΔT(i). This calculation may be performed at the gNB that receives the RTT response signal from the UE or at a central location in the network.

[0104] Fig. 6A An example of network-centric RTT estimation according to an aspect of the present disclosure is shown. Fig. 6AAs shown in FIG. 6 , in a downlink-centric / downlink-only (at a low duty-cycle) subframe in a downlink (DL) subframe sequence 602, a serving gNB (e.g., gNB 110-1) transmits a control signal (e.g., on a physical downlink control channel (PDCCH)) to a UE 102, thereby indicating to the UE 102 that one or more gNBs (at a low duty-cycle) Fig. 6A In the example of , gNB 110 will send a downlink RTT measurement (RTTM) signal. During downlink subframe sequences 606 and 608, gNB 110 sends the downlink RTT measurement signal in a time division multiple access (TDM) or frequency division multiple access (FDM) manner at designated symbols of the subframe. The RTT measurement sent by gNB 110 should be a wideband signal that enables UE 102 to make precise timing measurements. Any other gNB in ​​the neighborhood should not send other signals in or around the symbols associated with the RTT measurement (resulting in low reuse, interference avoidance, and deep penetration of the RTT measurement).

[0105] During downlink subframe sequence 604, UE 102 measures the arrival time Δt(i) of each downlink RTT measurement sent during subframe sequence 606 and 608 relative to its own downlink subframe timing (derived from the downlink signal received on the PDCCH from the serving gNB). UE 102 is instructed to report its RTT measurement on the physical uplink shared channel (PUSCH) during a subsequent subframe, which it does during uplink subframe sequence 612. The report from UE 102 includes the arrival time Δt(i) of each downlink RTT measurement, as well as the UE 102's own uplink timing adjustment (TA) provided by the serving gNB. Similar to the downlink RTT measurements sent by gNB 110, the uplink RTT measurements sent by UE 102 should be wideband signals that enable the gNB to make precise timing measurements.

[0106] Each gNB in ​​the neighborhood of UE 102 (i.e., within the communication range of UE 102; within Fig. 6A The gNB 110 in the example above receives the report from the UE 102 during the uplink subframe sequence 614 and decodes the report and also records the arrival time ΔT(i) of the uplink (UL) signal from the UE 102 relative to its own system time. The RTT may then be calculated based on the arrival time of the report from the UE 102 in combination with the timing information in the payload (i.e., the RTT measurement report).

[0107] It should be noted that the timing advance (TA) for the wideband signal is a parameter that takes into account the distance of the UE 102 from the serving gNB. The TA enables all uplink signals from the UE 102 to arrive at the serving gNB at the same time. The uplink TA enables the RTT measurement to arrive accurately at the end of the gap.

[0108] UE-centric RTT estimation is similar to the network-based approach, except that a UE (e.g., UE 102) sends an RTT measurement signal (when instructed) that is received by multiple gNBs in the UE's neighborhood. Each gNB responds with an RTT response message, including the arrival time Δt(i) of the RTT measurement signal from the UE in the message payload. The UE determines the arrival time ΔT(i) of the RTT measurement message, decodes the RTT response message and estimate, extracts the timestamp Δt(i) embedded in the message, and calculates the RTT of the responding gNB by adding the measured arrival time ΔT(i), the extracted timestamp Δt(i), and its own uplink-downlink timing adjustment value TA.

[0109] Figure 6B An example of UE-centric RTT estimation according to an aspect of the present disclosure is shown. At an uplink-centric (at a low duty cycle) subframe during an uplink subframe sequence 702, the serving gNB transmits a control signal (e.g., on the PDCCH) to the UE 102, thereby instructing the UE 102 (and any number of other UEs) to send an uplink RTT measurement signal (UL-RTTM).

[0110] During the uplink subframe sequence 704, the UE 102 sends the RTT measurement signal at the designated resource block of the uplink data portion of the subframe in a TDM or FDM manner. The RTT measurement signal should be a broadband signal to achieve more accurate timing measurement. Any UE in the neighborhood should not send other signals on the codeword associated with the uplink RTT measurement signal (resulting in low reuse, interference avoidance, and deep penetration of RTTM).

[0111] During uplink subframe sequences 706 and 708, each gNB in ​​the neighborhood (i.e., within communication range of UE 102; within Figure 6BThe serving gNB 110 (in the example of gNB 110) measures the arrival time Δt(i) of each uplink RTT measurement signal relative to its own downlink subframe timing (assuming synchronous deployment of the gNBs). The serving gNB instructs UE 102 to look for an RTT response from gNB 110 on a subsequent subframe that occurs during downlink subframe sequence 714 and 716. The RTT response signal from each gNB 110 includes the arrival time Δt(i) of the uplink RTT measurement signal from UE 102. The RTT response signal should be a wideband signal that enables UE 102 to make precise timing measurements.

[0112] UE 102 and each UE in the neighborhood (e.g., all UEs within communication range of the serving gNB and gNB 110) decode the RTT response from gNB 110 during downlink subframe sequence 712 and also measure the arrival time ΔT(i) of the uplink signal from gNB 110 relative to its own (downlink) system time.

[0113] The RTT may be calculated based on the arrival time of the downlink RTT response at the UE 102, combined with the timing information in the gNB payload (downlink RTT response), along with its own TA (provided by the serving gNB). Any mismatch between inter-gNB timing may be absorbed into 0.5RTT(0); precise timing synchronization across gNBs 110 is not required.

[0114] The RTT estimation process disclosed herein can be extended to massive multiple-input multiple-output (MIMO) and extremely high frequency (EHF) spectrum regions, also known as millimeter wave (mmW) (typically, spectrum bands above 24 GHz) systems. In mmW band systems, as well as massive MIMO systems in any frequency band, the gNB uses transmit / receive beamforming to extend signal coverage to the cell edge.

[0115] "Beamforming" is a technique for focusing an RF signal in a particular direction. Traditionally, when a base station broadcasts an RF signal, it broadcasts the signal in all directions. Using beamforming, the base station determines where a given target device (e.g., UE 102) is located (relative to the base station) and projects a stronger downlink RF signal in that particular direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the base station can control the phase and relative amplitude of the RF signal at each transmitter. For example, a base station can use an antenna array (referred to as a "phased array" or "antenna array") that generates RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to the individual antennas in the correct phase relationship so that the radio waves from the individual antennas can be added together to increase the radiation in the desired direction, while canceling to suppress the radiation in the undesired direction.

[0116] The term "cell" refers to a logical communication entity used to communicate with a base station (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) used to distinguish adjacent cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types that may provide access to different types of devices (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types). In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) on which the logical entity operates.

[0117] Figure 7 An exemplary system according to one aspect of the present disclosure is shown in which the RTT estimation process disclosed herein is extended to massive MIMO and mmW systems. Figure 7In the example of , gNB110 is a massive MIMO gNB. In order to perform the RTT estimation process described herein in a massive beamforming system (e.g., MIMO, mmW), each physical gNB (e.g., gNB 110) acts as a set of multiple "logical gNBs" that send their RTT measurement or RTT response signals on multiple beams (e.g., beams 1 to 4) on different time-frequency resources in a TDM or FDM manner. The RTT measurement / response signal may carry (implicitly or explicitly) information about the identity of the gNB sending the signal and the beam index (e.g., 1 to 4) used to send the signal. The UE (e.g., UE 102) processes the RTT (measurement / response) signals received on the downlink as if they were sent by different gNBs. Specifically, in addition to the timestamp (e.g., arrival time) previously described, it also records or reports the beam index on which the RTT signal was received.

[0118] During reception, the gNB 110 records / reports the beam index from which the RTT signal was received from the UE 102 and includes this information in the RTT response payload along with the previously described timestamp (e.g., arrival time). In the event that the gNB 110 has fewer RF chains than the number of receiver beams it uses, the UE 102 may be commanded to repeat the RTT measurement / response message multiple times so that the gNB can sequentially cycle through the set of all receiver beams that can be used to receive the RTT signal from the UE 102 based on its limited baseband processing capabilities. An RF chain may be a receiver chain or a transmitter chain and is hardware used to receive or transmit RF signals at a given frequency or set of frequencies. A device (e.g., a base station 110 or a UE 102) may have multiple receiver / transmitter chains and may thereby be able to transmit and / or receive RF signals on multiple frequencies simultaneously.

[0119] In one aspect, in a (massive) MIMO system, either or both of the gNB 110 and UE 102 may repeat their RTT measurement / report signal multiple times. Different repetitions may use the same or different transmit beams. When the signal is repeated with the same transmit beam, it is intended to support receive beam scanning at the receiving endpoint (UE 102 or gNB 110) (in addition to coherent combining, if desired).

[0120] On the one hand, the UE's geographic location can be calculated using the angle of arrival / departure associated with the beam index information (at gNB 110) in combination with the RTT estimate (RTT plus AOA / AOD-based location determination).

[0121] Figure 8 An exemplary timing diagram with two gNBs 110 is shown (in Figure 8Referred to as gNB1 (or gNB1) and gNB2 (or gNB2). Figure 8 The upper part of shows the uplink-downlink timing relationship of serving gNB1 (e.g., gNB110-1). According to 3GPP TS 38.211, an uplink frame i for transmission from a UE starts T before the start of the corresponding downlink frame at the UE. TA =(N TA +N TAoffset )T c , where N TA corresponds to the timing advance between the downlink and uplink, and T c It is the basic time unit of NR. TAoffest is a constant as defined in 3GPP TS 38.133. N TA is usually determined so that the UL transmissions from UEs in a cell are aligned. Therefore, the UE Rx-Tx time difference (Rx1–Tx) ideally corresponds to twice the propagation delay 1, while the gNB Rx-Tx time difference is Figure 8 In this example, the TOA of UE uplink frame iRX2 may be zero. The same UE uplink frame i arrives at neighboring gNB2 after a propagation delay of 2. gNB2 may have a synchronization offset Δ relative to serving gNB1 and record the TOA of UE uplink frame iRX2. The RTT for gNB1 and gNB2 may then be determined in this example as:

[0122] RTT1=(UE Rx1–Tx)+(gNB Rx1–Tx1) Formula 1

[0123] RTT2=(UE Rx2–Tx)+(gNB Rx2–Tx2) Formula 2

[0124] Figure 8 The basic UE and gNB measurements shown are TOA measurements (e.g., UE RX1, RX2; and gNB RX1, RX2). Those measurements can be correlated with the appropriate TX time so that the Rx-Tx time difference can be reported to determine the RTT. Figure 8 It is also shown that any synchronization offset Δ between gNBs does not affect the RTT calculation. However, it may affect the TOA search window center at the neighboring gNB.

[0125] Fig. 9 Shown based on Figure 1A , 1B 2 and 3 , wherein the location determination process is controlled and initiated by LMF 120. It should be understood that Fig. 9The overall process shown in shows the main functionality, but does not necessarily show all signaling steps / possibilities. For example, a request for DL-PRS or UL-PRS measurement may have a specific response message indicating, for example, success or failure. Fig. 9 The process shown in presupposes that LMF 120 knows (at least) the approximate timing of each involved gNB (e.g., SFN initialization time).

[0126] As shown in the figure, Fig. 9 At stage 1 in the process, the AMF 115 requests positioning of the target UE 102 (e.g., after the AMF 115 receives a request for positioning from the GMLC 125, from the UE 102, or after an emergency call is initiated by the UE 102 to the AMF 115).

[0127] At stage 2, LMF 120 may request the location determination capability of target UE 102 using the LPP capability transfer procedure.

[0128] At stage 3, LMF 120 transmits an NRPPa UL PRS request message to serving gNB 110-1 to request UL PRS configuration information. The request may include any desired UL PRS configuration (i.e., SRS needs to meet QoS); for example, desired periodicity and time domain behavior (e.g., periodic, semi-persistent).

[0129] At stage 4, serving gNB 110-1 determines radio resources available for UL PRS of UE 102, and determines UL PRS configuration information to be used for UL PRS transmission by UE 102 at stage 9b. The UL PRS configuration information may indicate preferred or maximum UL signaling resources (e.g., preferred or maximum transmit power, preferred or maximum bandwidth, available frequency, preferred or minimum periodicity, and / or preferred or maximum transmit duration) available for UL PRS transmission by UE 102 at stage 9b.

[0130] At stage 5, serving gNB 110-1 provides the UL PRS configuration information in an NRPPa UL PRS response message to LMF 120. LMF 120 may adjust the UL PRS configuration received at stage 5 (e.g., by increasing or decreasing transmit power, UL PRS bandwidth, periodicity, and / or duration), but may not exceed them by going above any maximum values ​​or below any minimum values, respectively, indicated at stage 5.

[0131] At stage 6, gNB 110-1 may configure target UE 102 with the (e.g., preferred) UL PRS resources determined at stage 4. This stage may be included in stage 9 below, in which case stage 6 is not required. As discussed below, stage 6 may also be omitted for additional reasons.

[0132] At stage 7, LMF 120 may determine gNBs 110 that are near the approximate location of target UE 102 (e.g., as given by the serving cell of UE 102). If no DL PRS resources are configured on these gNBs 110 or the DL PRS resources are insufficient, LMF 120 may initiate the NRPPa process to configure (or reconfigure) DL-PRS transmission for gNB 110.

[0133] At stage 8, LMF 120 provides the UL PRS configuration as obtained or adjusted at stage 5 to the selected gNB 110 in an NRPPa UL PRS Measurement Request message. The message includes all information required to enable the gNB 110 to perform UL measurements of the UL PRS. The message may also include the start time (e.g., RTOA or Rx-Tx) when each gNB 110 should expect UL transmissions from the target UE 102 and / or a search window for UL measurements.

[0134] At stage 9a, LMF 120 transmits an LPP Provide Assistance Data message to target UE 102. The message includes any assistance data required by target UE 102 to perform the necessary DL PRS measurements (e.g., cell-ID, DL-PRS configuration, measurement search window, etc.) and any information necessary to send UL PRS when stage 6 is not performed (e.g., the UL PRS configuration obtained or adjusted at stage 5). Alternatively, and when stage 6 is not performed, the UL PRS configuration may be provided in an LPP Request Positioning Information message.

[0135] At stage 9b, LMF 120 transmits an LPP request positioning information message for requesting DL PRS measurement and a request for sending UL PRS according to the UL PRS configuration received in the auxiliary data at stage 9a (or included in the message at stage 9b, or provided at stage 6). For example, the DL PRS measurement may include measurement of Rx-Tx. The target UE 102 starts UL PRS transmission according to the time domain behavior (e.g., periodic, aperiodic, semi-persistent) of the UL-PRS resource configuration.

[0136] At stage 10a, the target UE 102 performs DL-PRS measurements from all gNBs 110 provided in the assistance data at stage 9a.

[0137] At stage 10b, each gNB 110 configured at stage 8 measures the UL PRS transmissions from the target UE 102 (e.g., obtains Rx-Tx measurements).

[0138] At stage 11, the target UE 102 reports the DLPRS measurements in an LPP Provide Positioning Information message to the LMF 120. The message may also include an indication of successful completion of the UL PRS transmission.

[0139] At stage 12, each gNB 110 reports the UL PRS measurements to the LMF 120 in the NRPPa UL PRS Measurement Response message.

[0140] At stage 13, LMF 120 determines the RTT of each gNB 110 that provided corresponding UL and DL measurements at stages 11 and 12, calculates the location of target UE 102 (e.g., as for Figures 4 to 5B ), and provides the positioning estimate to the AMF 115 in a positioning response message.

[0141] It can be seen that only DL (e.g., OTDOA, AOD) or only UL (e.g., UTDOA, AOA) position determination can be supported, as Fig. 9 For example, for DL-only position determination, stages 3, 4, 5, 6, 8, 10b, 12 will not be performed. For UL-only position determination, stages 7, 10a will not be performed, and optionally stages 9a and 11 will not be performed. Therefore, the above Fig. 9 The procedures described in support NR position determination methods based on DL, UL, and DL+UL. For the various methods, only the measurements made and / or reported will necessarily be different, for example: for OTDOA, DL reference signal time difference (RSTD) may be measured at stage 10a; for UTDOA, UL relative time of arrival (RTOA) may be measured at stage 10b; for UL-AoA, UL angle of arrival may be measured at stage 10b; for multi-cell RTT, UE Rx-Tx time difference may be measured at stage 10a, and gNB Rx-Tx time difference may be measured at stage 10b; for DL ​​AOD, RSRP may be measured at stage 10a. For downlink E-CID position determination, stages 3 to 8 and 10b, 12 may not be required.

[0142] Although the assistance data may also be different, it is possible to share the assistance data that is transmitted to the UE 102 for DL, UL, and DL+UL position determination methods (e.g., PRS configuration), or to the gNB 110 (e.g., for UL PRS configuration). Such sharing of assistance data may be more easily implemented using procedures and signaling messages that are common or overlapping for multiple position methods (e.g., for LPP and NRPPa).

[0143] The UL Sounding Reference Signal (SRS) for position determination (which may correspond to the UL-PRS referred to herein) may be configured for periodic, semi-persistent, or aperiodic transmission. For example, a periodic SRS may be transmitted with a certain configured period and a certain configured slot offset within the period. A semi-persistent SRS has a configured period and slot offset in the same manner as a periodic SRS. However, the actual SRS transmission according to the configured period and slot offset is activated and deactivated by means of MAC CE signaling. Aperiodic SRS may be transmitted by UE 102 only when explicitly triggered by the serving gNB 110 at Layer 1 level.

[0144] Fig. 9 UL-PRS (SRS) configurations are basically considered as "assistance data" for both UE 102 and measuring gNB 110; they determine time / frequency / spatial information for UE 102 to send UL-PRS and for gNB 110 to measure UL-PRS. Similarly, activation / deactivation / triggering may be equivalent to an "LPP positioning request".

[0145] This can support UE mobility. For example, UE 102 can switch to a new cell and / or new serving gNB 110 during or after switching to a new cell and / or new serving gNB 110. Fig. 9 The configured / activated UL-PRS configuration continues to be sent at stage 9b in , since this can be controlled by LMF120.

[0146] However, when LPP is used without including stage 6 as described above for Fig. 9 The described SRS configuration and activation may result in conflicting SRS configurations at UE 102; i.e., multiple SRS resources may appear in the same symbol. For example, "regular" SRS usage, such as beam management, may conflict with UL-PRS (e.g., conflicting path loss references or spatial relationships). For semi-persistent or aperiodic UL-PRS, conflicts should only occur when SRS is triggered to be transmitted, not when it is just configured. However, since the serving gNB 110 may Fig. 9The non-location determination specific SRS details are determined at stage 4 in , so the serving gNB will be aware of the UL-PRS resource set. This may require reserving UL-PRS resources that cannot be used for other applications. However, this may be of little concern, as the location determination SRS (UL-PRS) is not very suitable for other purposes (e.g., given path loss reference or spatial relationship), and the use of Fig. 9 It may still be possible to reuse the existing SRS configuration / usage for position determination as this can be done in Fig. 9 Otherwise (e.g., if a conflict would occur after handover), some priority / conflict handling rules may be specified.

[0147] It should be noted that the serving gNB 110-1 may know Fig. 9 9a or 9b in UE-associated mode (e.g., by transmitting a UL PRS measurement request message to the serving gNB at stage 8 in UE-associated mode and / or including some additional information in the message). Using the above method, the serving gNB 110-1 Fig. 9 4 in the HANDOVER REQUEST message, the SRS resources available for UL PRS are provided to LMF 120, and LMF 120 determines the remaining (e.g., location determination specific) configuration parameters. The serving gNB 110-1 may then transmit this information to any new serving gNB 110 after the handover in a HANDOVER REQUEST message to enable the new serving gNB 110 to similarly avoid potential conflicts with the UL PRS.

[0148] It should be noted that Fig. 9 In the embodiment, LMF 120 may control DL PRS transmission from gNB 110 and / or from TP 111 and / or TRP within gNB 110 at stage 7. Similarly, LMF 120 may request and receive UL PRS measurements from gNB 110 and / or from RP 113 and / or TRP within gNB 110 at stages 8 and 12. Thus, in an embodiment, Fig. 9 One or more of the neighboring gNBs 110 in (and the serving gNB 110-1 in stages 7, 8, and 12) may each be replaced with a TP 111, an RP 113, or a TRP. Additionally or alternatively, in some embodiments, Fig. 9 The LMF 120 in the can be replaced by LMC117, such as for Figure 2 The same embodiment can be applied to the following Figures 10 to 15The described signaling flow shows LMF 120 and gNB 110 in the figure, but it is also possible to replace it with LMC 117 (for LMF 120) or with TP 111, RP 113 or TRP (for gNB 110) in the figure.

[0149] Combined with the following Figures 10 to 15 Provide the above for Fig. 9 Alternative embodiments and additional examples, details and options of the described combined UL and DL position determination process.

[0150] Fig.10 A call flow for a mobile originated location request (MO-LR) for RTT measurement of UE 102 is shown, wherein the positioning server 120 is used to aggregate the measured signal data from the gNB 110 and transmit an aggregated report of the measured signal data to the UE 102. Fig.10 By way of example, the UE 102 is shown to initiate RTT reference signal transmission, wherein the UE 102 measures the overall RTT, and the gNB 110 measures its corresponding processing delay Δ and transmits it to the positioning server 120. However, it should be understood that if desired, the gNB may initiate RTT reference signal transmission, wherein the gNB 110 measures the overall RTT and transmits it to the positioning server 120, and the UE 102 measures its processing delay Δ.

[0151] As shown in the figure, Fig.10 At stage A in the process, UE 102 sends a request RTT message to positioning server 120 .

[0152] Phases B, C, and D are optional phases for on-demand downlink reference signal transmission. For example, as shown at optional phase B, positioning server 120 may transmit a request for a gNB RTT configuration message to gNB 110.

[0153] At optional stage C, gNB 110 may transmit a gNB RTT configuration ready response message to the positioning server 120.

[0154] At optional stage D, the positioning server 120 may transmit a clear gNB RTT DL (downlink) RS (reference signal) message to the gNB 110.

[0155] At stage E, positioning server 120 may transmit gNB RTT assistance data (AD) with participating UE messages to gNB 110. For example, there may be more than one UE for which RTT measurements are to be determined. The assistance data identifies the UEs that are engaged with gNB 110110.

[0156] At stage F, gNB 110 transmits a gNB RTT AD ready response message to the positioning server 120.

[0157] At stage G, positioning server 120 transmits UE RTT assistance data with a list of participating gNB messages to UE 102. For example, the assistance data identifies gNB 110 and any other gNBs with which UE 102 should engage in order to make RTT measurements. It should be appreciated that if there are multiple UEs, positioning server 120 may transmit appropriate assistance data to each UE participating in the RTT determination, if there are multiple UEs.

[0158] At optional stage H, positioning server 120 transmits a UE RTT clear to send UL (uplink) RS message to UE 102. Optional stage H may be performed, for example, at an on-demand UL reference signal transmission.

[0159] At stage I, UE 102 sends an uplink RTT reference signal which is received by gNB 110.

[0160] At stage J, gNBs 110 each send a downlink RTT reference signal in response to the uplink RTT reference signal received in stage I and after a processing delay Δ between, for example, the TOA of the uplink RTT reference signal and the TOT of the downlink RTT reference signal, which processing delay is measured by gNB 110.

[0161] At stage K, gNB 110-1 transmits a gNB RTT report of the difference between the detected DL TOT and UL TOA (i.e., the processing delay Δ measured by gNB 110-1 for all UEs (including UE 102) for which RTT is being measured) to positioning server 107.

[0162] At stage L, gNB 110-2 transmits a gNB RTT report of the difference between the detected DL TOT and UL TOA (i.e., the processing delay Δ measured by gNB 110-2 for all UEs (including UE 102) for which RTT is being measured) to positioning server 107.

[0163] At stage M, positioning server 120 aggregates gNB RTT reports of processing delay Δ measured by each gNB 110 for all UEs including UE 102.

[0164] At stage N, the positioning server 120 transmits to the UE 102 an aggregated report of the processing delay Δ measured by each gNB 110 for the UE 102 .

[0165] At stage O, UE 102 may determine the net RTT of each gNB 110, for example, using the overall RTT measured by UE 102 for each gNB 110 and the processing delay Δ measured by each gNB 110 received in the aggregated report received at stage N. UE 102 may determine the positioning of UE 102 using at least the net RTT of gNB 110 and the known location of gNB 110, for example, received in the assistance data from stage G. It should be understood that although for simplicity, Fig.10 Only two gNBs are shown, but for positioning determination using trilateration, RTT measurements from three or more gNBs may be used.

[0166] As discussed above, if necessary, the gNB may initiate RTT reference signal transmission (e.g., phase J may occur before phase I), where the gNB 110 measures the overall RTT at phases K and L and transmits it to the positioning server 120, and the UE 102 measures its processing delay Δ in phase O for determining the net RTT.

[0167] Fig.11 A call flow for a mobile originated positioning request (MO-LR) for RTT measurement of UE 102 is shown, where serving gNB 110-1 is used to aggregate measured signal data from gNB 110 and transmit an aggregated report of the measured signal data to UE 102. Fig.11 By way of example, UE 102 is shown initiating RTT reference signal transmission, wherein UE 102 measures the overall RTT, and gNB 110 measures its corresponding processing delay Δ, and gNB 110-2 transmits its processing delay Δ to serving gNB 110-1. However, it should be understood that if desired, the gNB may initiate RTT reference signal transmission, wherein gNB 110 measures its corresponding overall RTT, and gNB 110-2 transmits its overall RTT to serving gNB 110-1, and UE 102 measures its processing delay Δ.

[0168] As shown in the figure, Fig.11 At stage A in the process, UE 102 sends a request RTT message to gNB110-1.

[0169] Phases B, C, and D are optional phases for on-demand downlink reference signal transmission. For example, as shown at optional phase B, gNB 110-1 may transmit a request for a DL configuration message to gNB 110-2.

[0170] At optional stage C, gNB 110-2 may transmit a DL configuration ready response message to gNB110-1.

[0171] At optional stage D, gNB 110-1 may transmit a Clear to Send DL RS message to gNB 110-2.

[0172] At stage E, gNB 110-1 may transmit assistance data (AD) with participating UE messages to gNB 110-2. For example, there may be more than one UE for which RTT measurements are to be determined. The assistance data identifies the UE with which gNB 110 is to engage.

[0173] At stage F, gNB 110-1 transmits a gNB AD Ready Response message to gNB 110-1.

[0174] At stage G, gNB 110-1 transmits assistance data with a list of participating gNB messages to UE 102. For example, the assistance data identifies gNB 110 and any other gNBs with which UE 102 should engage for RTT measurements. It should be appreciated that if there are multiple UEs, gNB 110-1 may transmit appropriate assistance data to each UE participating in the RTT determination, if there are multiple UEs.

[0175] At optional stage H, gNB 110-1 transmits a clear to transmit UL RS message to UE 102. For example, optional stage H may be performed when an on-demand UL reference signal is transmitted.

[0176] At stage I, UE 102 sends an uplink RTT reference signal which is received by gNB 110.

[0177] At stage J, gNBs 110 each send a downlink RTT reference signal in response to the uplink RTT reference signal received in stage I and after a processing delay Δ between, for example, the TOA of the uplink RTT reference signal and the TOT of the downlink RTT reference signal, which processing delay is measured by gNB 110.

[0178] At stage K, gNB 110-2 transmits a gNB RTT report of the difference between the detected DL TOT and the UL TOA (i.e., the processing delay Δ measured by gNB 110-2 for all UEs (including UE 102) for which RTT is being measured) to gNB 110-1.

[0179] At stage L, gNB 110-1 aggregates the gNB RTT reports of the processing delay Δ measured by each gNB 110 for all UEs including UE 102.

[0180] At stage M, gNB 110-1 transmits to UE 102 an aggregated report of the processing delay Δ measured by each gNB 110 for UE 102.

[0181] At stage N, UE 102 may determine the net RTT of each gNB 110, for example, using the overall RTT measured by UE 102 for each gNB 110 and the processing delay Δ measured by each gNB 110 received in the aggregated report received at stage N. UE 102 may determine the positioning of UE 102 using at least the net RTT of gNB 110 and the known location of gNB 110, for example, received in the assistance data from stage G. It should be understood that although for simplicity, Fig.11 Only two gNBs are shown, but for positioning determination using trilateration, RTT measurements from three or more gNBs may be used.

[0182] As discussed above, if necessary, the gNB may initiate RTT reference signal transmission (e.g., stage J may occur before stage I), where the gNB 110 measures the overall RTT at stages K and L and transmits it to the positioning server 120, and the UE 102 measures its processing delay Δ at stage N for determining the net RTT.

[0183] Fig.12 A call flow for a network initiated positioning request (NI-LR) for RTT measurement of UE 102 is shown, where the positioning server 120 is used to request RTT determination and aggregate measured signal data from gNB 110. Fig.12 By way of example, a gNB is shown in which RTT reference signal transmission is initiated, wherein the gNB 110 measures the overall RTT and transmits it to the positioning server 120, and the UE 102 measures its processing delay Δ and transmits it to the positioning server 120. However, it should be understood that if desired, the UE 102 may initiate RTT reference signal transmission, wherein the UE 102 measures the overall RTT and transmits it to the positioning server 120, and the gNB 110 measures its corresponding processing delay Δ and transmits it to the positioning server 120.

[0184] As shown in the figure, Fig.12 At stage A in the process, the positioning server 120 transmits a request UE RTT configuration message to the UE 102 .

[0185] At stage B, UE 102 transmits a UE RTT configuration ready response message to positioning server 120 .

[0186] Phases C, D, and E are optional phases for on-demand downlink reference signal transmission. For example, as shown at optional phase C, positioning server 120 may transmit a request for a gNB RTT configuration message to gNB 110.

[0187] At optional stage D, gNB 110 may transmit a gNB RTT configuration ready response message to the positioning server 120.

[0188] At optional stage E, positioning server 120 may transmit a clear-to-transmit gNB RTT DL RS message to gNB 110.

[0189] At stage F, positioning server 120 may transmit gNB RTT assistance data (AD) with participating UE messages to gNB 110. For example, there may be more than one UE for which RTT measurements are to be determined. The assistance data identifies the UEs that are engaged with gNB 110.

[0190] At stage G, gNB 110 transmits a gNB RTT AD ready response message to positioning server 120.

[0191] At stage H, positioning server 120 transmits UE RTT assistance data with a list of participating gNB messages to UE 102. For example, the assistance data identifies gNB 110 and any other gNBs with which UE 102 should engage in order to make RTT measurements. It should be appreciated that if there are multiple UEs, positioning server 120 may transmit appropriate assistance data to each UE participating in the RTT determination, if there are multiple UEs.

[0192] At optional stage I, positioning server 120 transmits a UE RTT clear to send UL (uplink) RS message to UE 102. Optional stage I may be performed, for example, at an on-demand UL reference signal transmission.

[0193] At stage J, gNBs 110 each send a downlink RTT reference signal to UE 102.

[0194] At stage K, UE 102 sends an uplink RTT reference signal to gNB 110 in response to the downlink RTT reference signal received in stage J and after a processing delay Δ between (e.g.) the TOA of the downlink RTT reference signal and the TOT of the uplink RTT reference signal, which processing delay is measured by UE 102.

[0195] At stage L, UE 102 transmits an RTT report of the difference between the detected UL TOT and DL TOA (i.e., processing delay Δ) for each gNB 110 of the UE.

[0196] In stage M, gNB 110-1 transmits a gNB RTT report of the difference between the detected UL TOT and DL TOA (i.e., the overall RTT measured by gNB110-1 for all UEs (including UE 102) for which RTT is being measured) to positioning server 107.

[0197] In stage N, gNB 110-2 transmits a gNB RTT report of the difference between the detected UL TOT and DL TOA (i.e., the overall RTT measured by gNB 110-2 for all UEs (including UE 102) for which RTT is being measured) to positioning server 107.

[0198] At stage O, positioning server 120 aggregates the overall RTT measured by each gNB 110 and the gNB reports of the processing delay Δ for all UEs including UE 102.

[0199] At stage P, positioning server 120 may determine the net RTT of each gNB 110, for example, using the processing delay Δ measured by UE 102 for each gNB 110 and the aggregated reported overall RTT measured by each gNB 110 from stage O. Positioning server 120 may determine the location of UE 102 using at least the net RTT of gNB 110 and the known location of gNB 110. It should be understood that although for simplicity, Fig.12 Only two gNBs are shown, but for positioning determination using trilateration, RTT measurements from three or more gNBs may be used.

[0200] As discussed above, if necessary, UE 102 may initiate RTT reference signal transmission (e.g., stage K may occur before stage J), ​​where gNB 110 measures its processing delay Δ at stages M and N and transmits it to positioning server 120, and UE 102 measures the overall RTT, which is used to determine the net RTT in stage P.

[0201] Fig.13 1 shows a call flow for a network initiated positioning request (NI-LR) for RTT measurement of UE 102, wherein serving gNB 110-1 is used to request RTT determination and positioning server 120 is used to aggregate measured signal data from gNB 110. Advantageously, by using serving gNB 110-1, as Fig.13 As shown in , the end-to-end response time can be less than 100% because there are fewer hops in the network entities. Fig.12 The embodiment shown in . Fig.13By way of example, a gNB is shown that initiates RTT reference signal transmission, wherein the gNB 110 measures the overall RTT and transmits it to the positioning server 120, and the UE 102 measures its processing delay Δ and transmits it to the positioning server 120. However, it should be understood that if desired, the UE 102 may initiate RTT reference signal transmission, wherein the UE 102 measures the overall RTT and transmits it to the positioning server 120, and the gNB 110 measures its corresponding processing delay Δ and transmits it to the positioning server 120.

[0202] As shown in the figure, Fig.13 At stage A in the process, gNB 110-1 transmits a request UE RTT configuration message to UE 102.

[0203] At stage B, UE 102 transmits a UE RTT Configuration Ready response message to gNB 110-1.

[0204] Phases C, D, and E are optional phases for on-demand downlink reference signal transmission. For example, as shown at optional phase C, gNB 110-1 may transmit a request DL configuration message to gNB 110-2.

[0205] At optional stage D, gNB 110-2 may transmit a DL configuration ready response message to gNB110-1.

[0206] At optional stage E, gNB 110-1 may transmit a Clear to Send DL RS message to gNB 110-2.

[0207] At stage F, gNB 110-1 may transmit assistance data (AD) with a participating UE message to gNB 110-2. For example, there may be more than one UE for which RTT measurements are to be determined. The assistance data identifies the UE with which gNB 110 is to engage.

[0208] At stage G, gNB 110-2 transmits a gNB RTT AD Ready Response message to gNB 110-1.

[0209] At stage H, gNB 110-1 transmits UE RTT assistance data with a list of participating gNB messages to UE 102. For example, the assistance data identifies gNB 110 and any other gNBs with which UE 102 should engage in order to make RTT measurements. It should be appreciated that if there are multiple UEs, gNB 110-1 may transmit appropriate assistance data to each UE participating in the RTT determination, if there are multiple UEs.

[0210] At optional stage I, gNB 110-1 transmits a UE RTT clear to transmit UL (uplink) RS message to UE 102. Optional stage I may be performed, for example, when an on-demand UL reference signal is transmitted.

[0211] At stage J, gNBs 110 each send a downlink RTT reference signal to UE 102.

[0212] At stage K, UE 102 sends an uplink RTT reference signal to gNB 110 in response to the downlink RTT reference signal received in stage J and after a processing delay Δ between, for example, the TOA of the downlink RTT reference signal and the TOT of the uplink RTT reference signal, which processing delay is measured by UE 102.

[0213] At stage L, UE 102 transmits an RTT report of the difference between the detected UL TOT and DL TOA (i.e., processing delay Δ) for each gNB 110 of the UE.

[0214] In stage M, gNB 110-1 transmits a gNB RTT report of the difference between the detected UL TOT and DL TOA (i.e., the overall RTT measured by gNB110-1 for all UEs (including UE 102) for which RTT is being measured) to positioning server 107.

[0215] In stage N, gNB 110-2 transmits a gNB RTT report of the difference between the detected UL TOT and DL TOA (i.e., the overall RTT measured by gNB 110-2 for all UEs (including UE 102) for which RTT is being measured) to positioning server 107.

[0216] At stage O, positioning server 120 aggregates the overall RTT measured by each gNB 110 and the gNB reports of the processing delay Δ for all UEs including UE 102.

[0217] At stage P, positioning server 120 may determine the net RTT of each gNB 110, for example, using the processing delay Δ measured by UE 102 for each gNB 110 and the aggregated reported overall RTT measured by each gNB 110 from stage O. Positioning server 120 may determine the location of UE 102 using at least the net RTT of gNB 110 and the known location of gNB 110. It should be understood that although for simplicity, Fig.12 Only two gNBs are shown, but for positioning determination using trilateration, RTT measurements from three or more gNBs may be used.

[0218] As discussed above, if necessary, UE 102 may initiate RTT reference signal transmission (e.g., stage K may occur before stage J), ​​where gNB 110 measures its processing delay Δ at stages M and N and transmits it to positioning server 120, and UE 102 measures the overall RTT, which is used to determine the net RTT in stage P.

[0219] Possible radio access technology (RAT) dependent location solutions include downlink (DL) based solutions; downlink (DL) and uplink (UL) based solutions; and uplink (UL) based solutions;

[0220] An example of a DL-based solution may be OTDOA location determination; an example of a UL-based solution may be UTDOA. Round Trip Time (RTT) location determination is an example of a combined DL- and UL-based solution.

[0221] The NG-RAN location determination procedure is applicable to DL-based location determination methods, UL-based location determination methods, and DL and UL-based location determination methods, such as RTT-based solutions. The procedure can be considered as a general case, in which downlink-based (e.g., OTDOA) and uplink-based (e.g., UTDOA) can be supported as special cases of the proposed procedure.

[0222] OTDOA and UTDOA location determination methods are based on time of arrival (TOA) measurements performed on downlink signals or uplink signals, respectively. Although these methods have been shown to be effective, they still require accurate base station time synchronization, which is difficult to install and maintain. Round trip time (RTT) location determination uses two-way time of arrival measurements and in principle does not require time synchronization between base stations. However, coarse base station time synchronization is required in order to reduce interference from multiple transmission points and increase audibility. The time synchronization requirements are similar to TDD synchronization requirements (e.g., microsecond level synchronization, rather than nanoseconds as in the case of OTDOA / UTDOA).

[0223] For example, in Figure 5A and 5B The principle of obtaining distance information from two-way time of arrival measurements (UL and DL measurements) is shown in . Similar to OTDOA / UTDOA behavior, accurate timing (TOA) measurements are required. RTT ranging measurements also rely on being able to compensate for any delays that the responding device may add when receiving and sending signals. However, multiple responding devices (e.g., base stations) do not need to be accurately synchronized as in, for example, OTDOA / UTDOA positioning. The location of the device can then be determined based on distance (RTT) measurements to multiple base stations, for example, such as Figure 4As shown in .

[0224] The following position determination process can be performed using e.g. Figure 2 NG-RAN location determination architecture shown in . Specifically, the location determination process may use a positioning management component (LMC) 117 included in gNB 110. This allows RTT measurements to be coordinated at the serving gNB 110-1 (e.g., configuring DL-PRS / UL-PRS and instructing neighboring gNBs to perform UL measurements, which will reduce latency and avoid confirming radio-related parameters / information at the LMF in the core network).

[0225] It should be noted that the term UL- / DL position determination reference signal (PRS) is used herein. However, these may not necessarily be new NR reference signals; the "position determination signal" may also reuse existing NR signals and / or configurations, such as synchronization signal blocks (SSBs), channel state information reference signals (CSI-RS), sounding reference signals (SRS), etc. The "position determination signal" may also be the same as or similar to the RTT measurement and response signals).

[0226] The "initiating device" for the location determination process can be the UE or the network. Therefore, the following proposes a network-initiated process and a UE-initiated process.

[0227] Fig.14 A call flow is shown for a network-centric UL / DL (RTT) measurement procedure for a UE 102. It should be understood that although the procedure is described as determining an RTT measurement, in some embodiments, DL measurements may be used for OTDOA, angle of arrival (AOA), or angle of departure (AOD), and / or UL measurements may be used for UTDOA or AOA.

[0228] The LMF 120 or AMF 115 may initiate a measurement process (e.g., after receiving a positioning request for the UE 102 (also referred to herein as the target device 102) from another entity). Fig.14 In the case of initiating the measurement process as shown at stage 1a in FIG. 1 , LMF 120 may request the location determination capability of target device 102 using an LPP capability transfer procedure or other suitable location determination protocol.

[0229] At stage 1b, LMF 120 may determine gNBs (e.g., as indicated by a serving cell of target device 102) near the approximate location of target device 102. If no DL PRS resources are configured on these gNBs or the DL PRS resources are insufficient, the LMF may initiate an NRPPa procedure to configure (or reconfigure) DL-PRS transmission on the gNBs.

[0230] At stage 1c, LMF 120 may transmit an NRPPa POS measurement start request message to serving gNB 110-1. The request includes an indication that RTT UL / DL measurements are requested for UE 102. It should be noted that the NRPPa message may be, for example, an NRPPa E-CID measurement start request message, or a different type of message may be used.

[0231] In the case where the AMF 115 initiates the measurement process, phases 1a, 1b, and 1c may be skipped. As shown, at phase 2a, the AMF 115 transmits a Positioning Report Control message to the serving gNB 110-1 to request positioning of the UE 102. The message may include, among other parameters, the desired QoS and the supported GAD shapes. The gNB 110-1 (e.g., the LMC 117 in the gNB 110-1) decides to initiate the RTT method based on the received QoS and the location determination methods supported by the UE / RAN.

[0232] In phase 2b (e.g., which may occur when phases 1a to 1c occur or when phase 2a occurs), if the target device 102 location determination capabilities are not already known by gNB 110-1, gNB 110-1 may request the location determination capabilities of the target device 102 using the RRC UE Capabilities Transfer procedure. For example, LPP capabilities parameters may be copied or imported into RRC (typically, LPP parameters / messages may be defined as an eight-byte string in RRC). However, the LPP capabilities supported at the RRC level may be different from the capabilities supported at the LPP level (e.g., the target device 102 may use LPP but not provide support using RRC, or vice versa).

[0233] At stage 2c, the serving gNB 110-1 determines a set of neighboring gNBs 110 (or multiple neighboring gNBs 110) that can be used to send a DL PRS to be measured by the UE 102, and / or can measure a UL PRS or other signal sent by the UE 102.

[0234] At stage 3, if stage 1b is not performed and if DL-PRS resources are not configured or are insufficient on the serving gNB and the neighboring gNB (or the serving gNB is unaware of the DL-PRS configuration of the neighboring gNB), the serving gNB 110-1 initiates the XnAP DL-PRS reconfiguration procedure to reconfigure (e.g., increase) DL PRS transmissions from one or more of the neighboring gNBs determined at stage 2c. If the neighboring gNB 110 is not able to configure the requested DL-PRS, a list of possible alternative configurations may be provided in the response. The serving gNB 110-1 may then repeat the process with a different configuration request.

[0235] At stage 4, the serving gNB 110-1 decides the desired UL-PRS configuration (e.g., SRS transmission) and provides the UL PRS configuration in an XnAP ULPOS Measurement Request message to the neighboring gNB 110 determined at stage 2c. The message may include all information required to enable the gNB to perform UL measurements. The message may also include the start time when the gNB should expect UL transmissions from the target device and the search window for UL (e.g., TOA) measurements.

[0236] At stage 5, if the neighboring gNB 110 is able to accept the UL positioning measurement request in stage 4, the gNB 110 responds with an XnAP UL POS measurement confirm message.

[0237] At stage 6, serving gNB 110-1 transmits an RRC DL POS measurement request message to target device 102. The message may include any required assistance data (e.g., cell-ID, DL-PRS configuration, measurement search window, etc.) for target device 102 to perform necessary DL-PRS measurements. The message may also include a request to start UL-PRS transmission (e.g., SRS transmission) and provide UL-PRS configuration parameters (possibly including a transmission start time and / or transmission duration).

[0238] At stage 7a, the target device 102 performs DL-PRS measurements from all gNBs 110 provided in the assistance data at stage 6. The measurements may be TOA measurements or UE Rx-Tx time difference measurements.

[0239] At stage 7b, each gNB configured at stage 4 / 5 measures the UL-PRS transmission from the target device. The measurement can be a TOA measurement or a gNB Rx-Tx time difference measurement.

[0240] At stage 8, the target device 102 reports the DL-PRS measurements to the serving gNB 110-1 in an RRC DL POS measurement report message.

[0241] At stage 9, each gNB 110 reports the UL-PRS measurements to the serving gNB 110-1 in the XnAP UL POS measurement report message.

[0242] At stage 10, gNB 110-1 (e.g., LMC 117 in gNB 110-1) calculates the RTT for each gNB for which corresponding uplink (UL) and downlink (DL) measurements were provided at stages 8 and 9. Different types of RTT calculations may be used. For example, the RTT may be based on a combination of gNB Rx-Tx time difference and UE Rx-Tx time difference (such as Tadv type 1 in LTE), or may be based on a combination of TOA measurements similar to those used by the WLAN fine time measurement procedure.

[0243] At stage 11, if stage 1c is performed, the serving gNB 110-1 transmits an NRPPa POS measurement start response message containing RTT measurements or containing UL and DLPRS measurements to LMF 120. The NRPPa message may be, for example, an NRPPa E-CID measurement start response message, or may be a different message.

[0244] At stage 12, if stage 2a is performed, the serving gNB 110-1 calculates the target device 102 location using the RTT measurement from stage 10 at stage 12a, and transmits the positioning estimate to the AMF 115 in an NGAP location report message at stage 12b.

[0245] Additional options at stage 11, for example, for LMF 120 include serving gNB 110-1 providing one or both of DL and UL measurements to LMF 120, and performing OTDOA, UTDOA, or RTT calculations at LMF 120 (stage 10). Another option is for gNB 110-1 (e.g., LMC 117 in gNB 110-1) to calculate positioning (stage 12a) and provide the positioning estimate to LMF 120; i.e., stage 11 is performed after stage 12a. This may reduce the computational load at LMF 120.

[0246] Therefore, in Fig.14 As can be seen in , OTDOA or UTDOA location determination can be supported as a special case of the UL / DL RTT process. For example, for OTDOA location determination, stages 4, 5, 7b, 9, 10 will not be performed. For UTDOA location determination: stages 1b / 3, 7a, 8, 10 will not be performed. Therefore, in Fig.14 The NRPPa, XnAP and RRC messages introduced in support NR position determination methods based on DL, UL and DL+UL.

[0247] Fig.15A call flow is shown for a UE-centric UL / DL RTT measurement procedure for UE 102. It should be appreciated that although the procedure is described as determining RTT measurements, in some implementations, DL measurements may be used for OTDOA or UL measurements may be used for UTDOA.

[0248] exist Fig.15 At stage 1 in , the target device 102 transmits an RRC Location Measurement Indication message to the serving gNB to request RTT measurement. To this end, the existing Location Measurement Indication procedure of 3GPP Release-15 can be reused by adding an additional entry in the Location Measurement Information Option (LocationMeasurementInfoCHOICE) for RTT measurement. UE 102 can start a timer T pos When the RRC message has been received at stage 5, the UE stops T pos When the timer T pos Upon expiration (ie, no RRC message has been received at stage 5), UE 102 assumes that the request cannot be authorized.

[0249] At stage 2a, the serving gNB 110-1 determines a set of neighboring gNBs 110 (or multiple neighboring gNBs 110) that can be used to send a DL PRS to be measured by the UE 102, and / or can measure a UL PRS or other signal sent by the UE 102.

[0250] At stage 2b, serving gNB 110-1 initiates the XnAP DL-PRS reconfiguration procedure. If the neighboring gNB 110 is not able to configure the requested DL-PRS, a list of possible alternative configurations may be provided in the response. Serving gNB 110-1 may then repeat the procedure with a different configuration request.

[0251] At stage 3, the serving gNB 110-1 decides the desired UL-PRS configuration (e.g., SRS transmission) and provides the UL PRS configuration to the neighboring gNB 110 in an XnAP ULPOS Measurement Request message. The message may include all information required to enable the gNB to perform UL measurements. The message may also include the start time when the gNB should expect UL transmissions from the target device and the search window for UL (e.g., TOA) measurements.

[0252] At stage 4, if the neighboring gNB 110 is able to accept the UL positioning measurement request in stage 4, the gNB 110 responds with an XnAP UL POS measurement confirm message.

[0253] At stage 5, serving gNB 110-1 transmits an RRC DL POS measurement request message to target device 102. The message may include any required assistance data (e.g., cell-ID, DL-PRS configuration, measurement search window, etc.) for target device 102 to perform the necessary DL-PRS measurements. The message may also include a request to start UL-PRS transmission (e.g., SRS transmission) and provide UL-PRS configuration parameters (possibly including a transmission start time).

[0254] At stage 6a, the target device 102 performs DL-PRS measurements from all gNBs 110 provided in the assistance data at stage 6. The measurements may be TOA measurements or UE Rx-Tx time difference measurements.

[0255] At stage 6b, each gNB configured at stage 3 / 4 measures the UL-PRS transmission from the target device. The measurement can be a TOA measurement or a gNB Rx-Tx time difference measurement.

[0256] At stage 7, each gNB 110 reports the UL-PRS measurements to the serving gNB 110-1 in the XnAP UL POS measurement report message.

[0257] At stage 8, the serving gNB 110-1 forwards the UL-PRS measurements to the target device 102 in an RRC Positioning Measurement Transfer message. The RRC message (e.g., stage 5, 8) may only include an octet string container with parameters defined in the LPP (assuming that the LPP continues to be used for NR position determination).

[0258] At stage 9, UE 102 calculates the RTT for each gNB, where measurements were provided for each gNB at stages 8 and 6a.

[0259] At stage 10, UE 102 computes its position using the RTT measurements from stage 9 (possibly together with other measurements, e.g., from a RAT independent method such as GNSS, using assistance data gNB location provided in stage 5 or available from broadcast messages, etc.).

[0260] Similar to Fig.14 The network-centric UL / DL RTT measurement process in UE-centric OTDOA or UTDOA positioning can be used as Fig.15. For example, for OTDOA position determination, stages 3, 4, 6b, 7, 8, 9 will not be performed. For UTDOA position determination, stages 2, 6a, 9 will not be performed. Therefore, UE-based UTDOA can also be supported with this procedure, for example to allow a mix of various position determination measurements at the target device.

[0261] In addition, if necessary, the conventional MO-LR process can be used to support the UE-centric UL / DL (RTT) measurement process. For example, UE 102 can provide a MO-LR request to AMF 115 or LMF 120, and can perform Fig.14 The MO-LR result may then be provided to UE 102 by AMF 115 or LMF 120.

[0262] Fig.16 An exemplary method 1600 performed by a user equipment (UE) 102 for determining a location of a UE (e.g., UE 102) is shown. The method 1600 may be performed by, for example, Figure 1B and 2 The communication system 100 shown in FIG. 1 employs the communication system 100 described herein (such as Fig.15 or Figures 9 to 14 Any of ) is performed by one or more of the call flows described.

[0263] At 1602, the UE receives assistance data for a plurality of gNBs from a serving gNB such as gNB 110-1, the plurality of gNBs including the serving gNB, such as in Fig.15 As shown in stage 5 of .

[0264] At 1604, the UE sends an uplink reference signal to multiple gNBs, e.g., as in Fig.15 As shown at stage 6B in .

[0265] At 1606, the UE receives uplink reference signal measurements measured by each of a plurality of gNBs from a serving gNB, wherein the serving gNB receives uplink reference signal measurements from other gNBs in the plurality of gNBs, e.g., as in Fig.15 As shown in stage 8 in .

[0266] At 1608, the UE determines a location of the UE based on uplink reference signal measurements measured by each of the plurality of gNBs and assistance data of the plurality of gNBs, e.g., as in Fig.15 As shown in stages 9 and 10 of FIG. 1 , for example, the UE may use uplink time difference of arrival (UTDOA) to determine the position.

[0267] In one aspect, the method may further include the UE obtaining downlink reference signal measurements of downlink reference signals received from a plurality of gNBs, e.g., as in Fig.15 The location of the UE may then be further determined based on downlink reference signal measurements of downlink reference signals received from multiple gNBs, as in Fig.15 9 and 10 in . For example, the location may be determined based on one or more of UTDOA, OTDOA, AOD, AOA, or RTT. In addition, in one aspect, determining the location of the UE may include: the UE determines a round trip time (RTT) for each of the multiple gNBs using uplink reference signal measurements measured by each of the multiple gNBs and downlink reference signal measurements received from the multiple gNBs, as in Fig.15 ; and performing multilateration using the RTT of each gNB and the positioning of each gNB received in the assistance data, as in Fig.15 As shown at stage 10 in .

[0268] In one aspect, the method may further include the UE sending a request for positioning to a serving gNB, wherein the serving gNB generates assistance data for a plurality of gNBs in response to the request for positioning and sends the assistance data to the UE, as in Fig.15 Stages 1 and 2 to 5 are shown in FIG.

[0269] In a variant of method 1600, the UE may receive assistance data at 1602 and receive UL reference signal measurements at 1606 from an LMF (e.g., LMF 120) or an LMC (e.g., LMC 117) rather than from a serving gNB, wherein the LMF or LMC receives UL reference signal measurements from all gNBs in a plurality of gNBs, respectively.

[0270] Fig.17 An exemplary method 1700 for determining a location of a user equipment (UE) (e.g., UE 102) performed by a serving gNB (e.g., gNB 110-1) of the UE is shown. The method 1700 may be performed by, for example, Figure 1B and 2 The communication system 100 shown in FIG. 1 employs the communication system 100 described herein (such as Fig.14 and 15 ) to execute one or more of the call flows described.

[0271] At 1702, the serving gNB receives a positioning request for the UE from another entity, e.g., as in Fig.14 In stages 1c and 2a, Fig.15As shown at stage 1 in . The other entity may be a UE, a serving AMF for the UE (e.g., AMF 115), or a LMF (e.g., LMF 120).

[0272] At 1704 and in response to the request at 1702, the serving gNB determines a plurality of neighboring gNBs (e.g., gNBs from which the UE may be able to measure downlink reference signal transmissions and which may be able to measure uplink reference signal transmissions by the UE), e.g., as in Fig.14 At stage 2c and at Fig.15 As shown at stage 2a in .

[0273] At 1706, the serving gNB transmits a request to each of the plurality of neighboring gNBs to increase downlink reference signal transmission and measure uplink reference signal transmission (e.g., UL PRS) from the UE. The serving gNB may provide a start time and duration of uplink reference signal transmission, and configuration parameters (e.g., frequency, bandwidth, and coding) for uplink reference signal transmission, e.g., as in Fig.14 In stages 3 and 4 and in Fig.15 This is shown in stages 2b and 3.

[0274] At 1708, the serving gNB generates assistance data for a plurality of neighboring gNBs, for example, as respectively Fig.14 and 15 As shown in stages 6 and 5 in . The auxiliary data may include configuration parameters of the DL PRS sent by each of the multiple gNBs and possibly an identity of each gNB.

[0275] At 1710, the serving gNB sends assistance data of a plurality of neighboring gNBs to the UE in a message (e.g., an RRC message), e.g., as respectively provided in Fig.14 and 15 The serving gNB may also include in the message a request for the UE to send a UL reference signal (e.g., a UL PRS signal), and may include a start time and duration for the transmission, as well as configuration parameters of the signal (e.g., frequency, bandwidth, and coding).

[0276] At 1712, the serving gNB receives an uplink reference signal transmission from the UE, e.g., as respectively Fig.14 and 15 As shown in stages 7b and 6b in FIG.

[0277] At 1714, the serving gNB generates (e.g., obtains) uplink reference signal measurements for uplink reference signal transmissions, e.g., as described in Fig.14 and 15As shown in stages 7b and 6b in FIG.

[0278] At 1716, the serving gNB receives one or more uplink reference signal measurements from each of a plurality of neighboring gNBs, wherein the one or more uplink reference signal measurements are generated by uplink reference signal transmissions from the UE to the neighboring gNB, e.g., as respectively described in Fig.14 and 15 As shown in stages 9 and 7.

[0279] At 1718 (optional as indicated by dotted lines), the serving gNB may receive from the UE one or more downlink reference signal measurements of downlink reference signal transmissions by multiple gNBs, e.g., as in Fig.14 As shown in stage 8 in .

[0280] At 1720, the serving gNB generates positioning information (e.g., Fig.14 UE positioning during network-centric UL / DL (RTT) measurements, or from Fig.15 UL-PRS measurements of the serving gNB and other gNBs during UE-centric UL / DL RTT measurement), e.g., as in Fig.14 In stages 10 and 12a and at Fig.15 As shown in stage 8 in .

[0281] At 1722, the serving gNB sends the positioning information to another entity, e.g., as in Fig.14 In stages 11 and 12b and in Fig.15 As shown in stage 8 in .

[0282] In one aspect, the positioning information may be a positioning measurement message including an uplink reference signal measurement from a serving gNB and one or more uplink reference signal measurements from a neighboring gNB, and the positioning measurement message may be sent to a UE for determining a position of the UE, for example, as in Fig.15 In one aspect, the determination of the location of the UE is performed by the UE using an uplink time difference of arrival (UTDOA). The method may also include sending a downlink reference signal to be measured by the UE, such as in Fig.15 The determination of the position of the UE is performed by the UE using the round trip time (RTT) of the signal, which is determined using uplink reference signal measurements and downlink reference signal measurements measured by the UE from downlink reference signal transmissions, for example, as in Fig.15 In one aspect, the other entity is a UE, and the assistance data is generated in response to a request for positioning and sent to the UE, e.g., as in Fig.15 As shown in stages 1 and 5.

[0283] In one aspect, the positioning information may be a positioning measurement message including an uplink reference signal measurement from a serving gNB and one or more uplink reference signal measurements from a neighboring gNB, and wherein the positioning measurement message is sent to a network entity such as AMF 115 or LMF 120, for example, as in Fig.14 The method may also include: the serving gNB sends a downlink reference signal to be measured by the UE, for example, as in Fig.14 and receiving a downlink reference signal measurement measured by the UE from a downlink reference signal received by the UE, as in Fig.14 The positioning measurement message may include, for example, a downlink reference signal measurement measured by the UE, for example, as shown in Fig.14 As shown in stage 11 in .

[0284] In one aspect, generating the positioning information may include determining, by the serving gNB, the location of the UE based on uplink reference signal measurements measured by each of a plurality of neighboring gNBs, e.g., as in Fig.14 The method may also include: the serving gNB sends a downlink reference signal to be measured by the UE, for example, as in Fig.14 and receiving a downlink reference signal measurement measured by the UE from a downlink reference signal received by the UE, as in Fig.14 Determining the location of the UE may be based on downlink reference signal measurements measured by the UE. For example, determining the location of the UE may include determining a round trip time (RTT) for each gNB using uplink reference signal measurements measured by each gNB and downlink reference signal measurements measured by the UE, as in Fig.14 ; and performing multilateration using the RTT of each gNB and the known positioning of each gNB, as in Fig.14 As shown at stage 12a in .

[0285] On the one hand, the serving gNB may send a downlink reference signal to be measured by the UE, such as Fig.14 and receiving a downlink reference signal measurement measured by the UE from a downlink reference signal received by the UE, as shown in stage 7a of Fig.14Generating the positioning information may include determining a round trip time (RTT) for each gNB using uplink reference signal measurements measured by each gNB and downlink reference signal measurements measured by the UE, for example, as in Fig.14 As shown at stage 10 in .

[0286] In a variation of method 1700, the LMF (e.g., LMF 120) or LMC (e.g., LMC 117) may perform the operations described above at 1702, 1704, 1706, 1708, 1710, 1716, 1718, 1720, and / or 1722 for the serving gNB (e.g., as described above for the serving gNB). Fig. 9 In the same or another variation of method 1700, the RP (e.g., RP 113) or TRP may perform the actions described above at 1712 and 1714 for the serving gNB.

[0287] Fig.18 1800 (such as Figures 1A to 4 1 and 15. UE 1800 may include hardware components such as, for example, a wireless transceiver 1802 to communicate with an NG-RAN 135 (e.g., such as a gNB 110 or ng-eNB 114 ( Figures 1B to 2 UE 1800 may also include additional transceivers (such as a wireless local area network (WLAN) transceiver 1806) and a base station for receiving wireless signals from SPS SV 190 ( Figure 1B 1800) receives and measures the SPS receiver 1808 of the signal. UE 1800 may also include one or more sensors 1810, such as a camera, an accelerometer, a gyroscope, an electronic compass, a magnetometer, a barometer, etc. UE 1800 may also include a user interface 1812, which may include, for example, a display, a keypad or other input device, such as a virtual keypad on a display, through which a user can interact with UE 1800. UE 1800 also includes one or more processors 1804 and a memory 1820, which may be coupled to bus 1816. One or more processors 1804 and other components of UE 1800 may be similarly coupled to bus 1816, a separate bus, or may be directly connected together or coupled using a combination of the foregoing. The memory 1820 may contain executable code or software instructions that, when executed by one or more processors 1804, cause the one or more processors to act as a processor programmed to perform the methods and procedures disclosed herein (e.g., such as Fig.16 A dedicated computer for use with the process flow 1600 shown in FIG.

[0288] like Fig.18 As shown, the memory 1820 may include one or more components or modules that can be implemented by the one or more processors 1804 to perform the methods described herein. Although the components or modules are shown as software in the memory 1820 that can be executed by the one or more processors 1804, it should be understood that the components or modules can be firmware or dedicated hardware in or outside the one or more processors 1804.

[0289] As shown, the memory 1820 may include a positioning request sending module 1821, which, when implemented by one or more processors 1804, configures one or more processors 1804 to send a positioning request via the wireless transceiver 1802, for example. Fig.16 The assistance data receiving module 1822, when implemented by the one or more processors 1804, configures the one or more processors 1804 to receive assistance data of multiple gNBs from the serving gNB via the wireless transceiver 1802, and processes the assistance data, for example, as described in Fig.16 The uplink reference signal transmission module 1824, when implemented by one or more processors 1804, configures one or more processors 1804 to transmit uplink reference signals to multiple gNBs via the wireless transceiver 1802, for example, as in Fig.16 The uplink reference signal measurement receiving module 1826, when implemented by the one or more processors 1804, configures the one or more processors 1804 to receive uplink reference signal measurements measured by multiple gNBs from the serving gNB via the wireless transceiver 1802, for example, as in Fig.16 The downlink reference signal measurement module 1828, when implemented by the one or more processors 1804, configures the one or more processors 1804 to receive downlink reference signals sent by multiple gNBs via the wireless transceiver 1802 and measure the downlink reference signals, for example, Fig.16 The round trip time (RTT) determination module 1830, when implemented by the one or more processors 1804, configures the one or more processors 1804 to determine the RTT of a signal between the UE 1800 and each of the plurality of gNBs using the received uplink reference signal measurements and the measured downlink reference signal measurements, e.g., Fig.16The location determination module 1832, when implemented by the one or more processors 1804, configures the one or more processors 1804 to determine the location of the UE 1800 using the determined RTT and the location of the gNB provided in the assistance data or using an uplink time difference of arrival (UTDOA) (e.g., if downlink reference signal measurements are not performed), e.g., as described in Fig.16 As discussed in box 1608 in .

[0290] Depending on the application, the methods described herein can be implemented in various ways. For example, the methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementations, one or more processors 1804 can 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.

[0291] For implementations of UE 1800 involving firmware and / or software, the methods can be implemented with modules (e.g., programs, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methods described herein. For example, software codes can be stored in a memory (e.g., memory 1820) and executed by one or more processors 1804, so that one or more processors 1804 act as a special-purpose computer programmed to perform the technology disclosed herein. The memory can be implemented within one or more processors 1804 or outside one or more processors 1804. 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 a particular amount of memory, or the type of medium on which the memory is stored.

[0292] If implemented in firmware and / or software, the functions performed by UE 1800 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium, such as memory 1820. 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 may 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, magnetic disk storage media, semiconductor storage devices or other magnetic storage devices, or any other medium that can be used to store 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 with lasers. The above combinations should also be included within the scope of computer-readable media.

[0293] In addition to being stored on a computer-readable storage medium, instructions and / or data for UE 1800 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 UE 1800 may include a transceiver having a signal indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium such as memory 1820, and are configured to cause one or more processors 1804 to act as a dedicated computer programmed to perform the technology disclosed herein. That is, the communication device includes a transmission medium having a signal indicating information for performing the disclosed function. At a first time, the transmission medium included in the communication device may include a first portion of information to perform the disclosed function, and at a second time, the transmission medium included in the communication device may include a second portion of information to perform the disclosed function.

[0294] Thus, a UE, such as UE 1800, capable of determining the location of the UE, may include means for receiving assistance data of multiple gNBs from a serving gNB, the multiple gNBs including the serving gNB, which means may be, for example, a wireless transceiver 1802 and one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in a memory 1820, such as an AD receiving module 1822. Means for sending uplink reference signals to multiple gNBs may be, for example, a wireless transceiver 1802 and one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in a memory 1820, such as an uplink reference signal sending module 1824. The means for receiving uplink reference signal measurements measured by each of the plurality of gNBs from the serving gNB, wherein the serving gNB receives uplink reference signal measurements from other gNBs in the plurality of gNBs, may be, for example, a wireless transceiver 1802 and one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in memory 1820, such as an uplink reference signal measurement receiving module 1826. The means for determining the position of the UE based on the uplink reference signal measurements measured by each of the plurality of gNBs and assistance data of the plurality of gNBs may be, for example, one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in memory 1820, such as a position determination module 1832.

[0295] On the one hand, the UE 1800 may also include a component for generating downlink reference signal measurements of downlink reference signals received from multiple gNBs, wherein determining the position of the UE is also based on the downlink reference signal measurements of the downlink reference signals received from multiple gNBs, and the component may be, for example, a wireless transceiver 1802 and one or more processors 1804 having dedicated hardware or implementing executable code or software instructions (such as a downlink reference signal measurement module 1828) in the memory 1820. The components for determining the position of the UE may include: a component for determining the round trip time (RTT) of each of the multiple gNBs using uplink reference signal measurements measured by each of the multiple gNBs and downlink reference signal measurements of downlink reference signals received from the multiple gNBs, which component may be, for example, one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in memory 1820 (such as RTT determination module 1830); and a component for performing multi-lateration positioning using the RTT of each gNB and the positioning of each gNB received in the auxiliary data, which component may be, for example, one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in memory 1820 (such as position determination module 1832).

[0296] On the one hand, the UE 1800 may also include a component for sending a request for positioning to a serving gNB, wherein the serving gNB generates auxiliary data of multiple gNBs in response to the request for positioning and sends it to the UE, and the component may be, for example, a wireless transceiver 1802 and one or more processors 1804 having dedicated hardware or implementing executable code or software instructions in a memory 1820 (such as a positioning request sending module 1821).

[0297] Fig.19 is a schematic diagram illustrating an example of a hardware implementation of a base station 1900 (such as any of the gNBs 110 shown in FIGS. 1 , 2 , 4 , and 9 to 15 ). The base station 1900 may perform Fig.17 1700. Base station 1900 includes, for example, hardware components such as external interface 1902, which may include one or more wired and / or wireless interfaces, which can be connected to and communicate with the following devices directly or through one or more intermediate networks and / or one or more network entities: user equipment such as UE 102, other base stations such as gNBs 110-2 and 110-3, and entities within the wireless network such as AMF 115 or LMF 120, as well as other elements in the wireless network, such as Figure 1A and 1B The external interface 1902 may include one or more antennas ( Fig.19 1906) to support a wireless interface to the UE 102 and / or a wireless backhaul to elements in the wireless network. The base station 1900 includes one or more processors 1904 and a memory 1910, which may be coupled to the bus 1906. The memory 1910 may contain executable code or software instructions that, when executed by the one or more processors 1904, cause the one or more processors 1904 to function as a processor programmed to perform the techniques disclosed herein (e.g., such as Fig.17 A dedicated computer for use with the process flow 1700 shown in FIG.

[0298] like Fig.19 As shown, the memory 1910 may include one or more components or modules that can be implemented by the one or more processors 1904 to perform the methods described herein. Although the components or modules are shown as software in the memory 1910 that can be executed by the one or more processors 1904, it should be understood that the components or modules can be firmware or dedicated hardware in or outside the one or more processors 1904.

[0299] As shown, the memory 1910 may include a positioning request receiving module 1912, which, when implemented by one or more processors 1904, configures one or more processors 1904 to receive, for example, a positioning request of a UE (UE 102), a serving AMF (e.g., AMF 115) or an LMF (e.g., LMF 120) for the UE via the external interface 1902, for example, as in Fig.17 1702 in the description. The memory 1910 may include a neighbor gNB determination module 1914 that, when implemented by the one or more processors 1904, configures the one or more processors 1904 to determine a plurality of neighboring gNBs, e.g., gNBs from which the UE may be able to measure downlink reference signal transmissions and / or gNBs from which the UE may be able to measure uplink reference signal transmissions by the UE, e.g., as in Fig.17 The configuration gNB module 1916, when implemented by the one or more processors 1904, configures the one or more processors 1904 to transmit a request to each neighboring gNB via the external interface 1902 to increase downlink reference signal transmission and measure uplink reference signal transmission from the UE, as in Fig.17 The module 1918 for generating AD for the gNB, when implemented by the one or more processors 1904, configures the one or more processors 1904 to generate auxiliary data for the neighboring gNB, as in Fig.17 The auxiliary data transmission module 1920, when implemented by the one or more processors 1904, configures the one or more processors 1904 to send auxiliary data of the neighboring gNB to the UE via the external interface 1902, as in Fig.17 The uplink reference signal measurement module 1922, when implemented by the one or more processors 1904, configures the one or more processors 1904 to receive uplink reference signal transmissions from the UE via the external interface 1902 and to generate measurements of the uplink reference signal transmissions, as in Fig.17 The uplink reference signal measurement receiving module 1924, when implemented by the one or more processors 1904, configures the one or more processors 1904 to receive one or more uplink reference signal measurements from each neighboring gNB, which are generated by uplink reference signal transmissions from the UE to each neighboring gNB, as described in Fig.17 The downlink reference signal transmission module 1926, when implemented by the one or more processors 1904, configures the one or more processors 1904 to transmit a downlink reference signal to be measured by the UE via the external interface 1902, as discussed in block 1716 of FIG. Fig.17The downlink reference signal measurement receiving module 1928, when implemented by the one or more processors 1904, configures the one or more processors 1904 to receive downlink reference signal measurements measured by the UE from the UE via the external interface 1902, as described in Fig.17 The positioning information generation module 1930, when implemented by the one or more processors 1904, configures the one or more processors 1904 to generate positioning information based on the measured uplink reference signal measurements and the uplink reference signal measurements received from the neighboring gNBs, as described in Fig.17 The positioning information generation module 1930 may include an uplink / downlink measurement module 1932, which, when implemented by the one or more processors 1904, configures the one or more processors 1904 to combine the measured uplink reference signal measurements and the uplink reference signal measurements received from the neighboring gNB, and / or the received downlink reference signal measurements, as in Fig.17 The positioning information generation module 1930 may include an RTT determination module 1934 that, when implemented by the one or more processors 1904, configures the one or more processors 1904 to determine a round trip time (RTT) for each gNB using uplink reference signal measurements and downlink reference signal measurements measured by the UE, as described in Fig.17 The positioning information generation module 1930 may include a position determination module 1936 that, when implemented by the one or more processors 1904, configures the one or more processors 1904 to determine the position of the UE based on an uplink-based solution or a downlink-based solution (e.g., in a UTDOA or ODOA-based solution) or a combined uplink- and downlink-based solution (e.g., RTT, such as using trilateration using the RTT of each gNB and the known positioning of each gNB), as described in Fig.17 The positioning information sending module 1938, when implemented by the one or more processors 1904, configures the one or more processors 1904 to send positioning information to another entity via the external interface 1902, such as in Fig.17 as discussed in Box 1722 of .

[0300] Depending on the application, the methods described herein may be implemented in various ways. For example, the methods may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementations, one or more processors 1904 may be implemented within 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.

[0301] For implementations of the base station 1900 involving firmware and / or software, the methods can be implemented with modules (e.g., programs, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methods described herein. For example, the software code can be stored in a memory (e.g., memory 1910) and executed by one or more processors 1904, so that one or more processors 1904 act as a special-purpose computer programmed to perform the technology disclosed herein. The memory can be implemented within one or more processors 1904 or outside one or more processors 1904. 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 a particular amount of memory, or the type of medium on which the memory is stored.

[0302] When implemented in firmware and / or software, the functions performed by the base station 1900 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium, such as memory 1910. 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, magnetic disk storage media, semiconductor storage devices or other magnetic storage devices, or any other medium that can be used to store 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 optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically by lasers. The above combinations should also be included within the scope of computer-readable media.

[0303] In addition to being stored on a computer-readable storage medium, instructions and / or data for base station 1900 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 base station 1900 may include a transceiver having a signal indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium such as memory 1910, and are configured to cause one or more processors 1904 to act as a dedicated computer programmed to perform the technology 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 part of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second part of information for performing the disclosed functions.

[0304] Thus, the base station 1900 may include means for receiving a positioning request for a UE from another entity, which means may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a positioning receiving module 1912. The means for determining a plurality of neighboring gNBs may be, for example, one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a neighboring gNB determination module 1914. The means for transmitting a request to each of the plurality of neighboring gNBs to increase downlink reference signal transmissions and measure uplink reference signal transmissions from the UE may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a configure gNB module 1916. The means for generating assistance data for multiple neighboring gNBs may be, for example, one or more processors 1904 with dedicated hardware or executable code or software instructions in memory 1910, such as module 1918 for generating AD for gNBs. The means for sending assistance data for multiple neighboring gNBs to the UE may be, for example, an external interface 1902 and one or more processors 1904 with dedicated hardware or executable code or software instructions in memory 1910, such as AD sending module 1920. The means for receiving uplink reference signal transmissions from the UE may be, for example, an external interface 1902 and one or more processors 1904 with dedicated hardware or executable code or software instructions in memory 1910, such as uplink reference signal measurement module 1922. The means for generating uplink reference signal measurements for uplink reference signal transmissions may be, for example, an external interface 1902 and one or more processors 1904 with dedicated hardware or executable code or software instructions in memory 1910, such as uplink reference signal measurement module 1922. Means for receiving one or more uplink reference signal measurements from each of a plurality of neighboring gNBs, wherein the one or more uplink reference signal measurements are generated by uplink reference signal transmissions from a UE to a neighboring gNB, may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as an uplink reference signal measurement receiving module 1924. Means for generating positioning information based on uplink reference signal measurements from a serving gNB and one or more uplink reference signal measurements from a neighboring gNB may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a positioning information generation module 1930.The means for sending the positioning information to another entity may be, for example, the external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in the memory 1910 (such as the positioning information sending module 1938).

[0305] In some embodiments of the base station 1900, the positioning information is a positioning measurement message including an uplink reference signal measurement from a serving gNB and one or more uplink reference signal measurements from a neighboring gNB, and the positioning measurement message is sent to the UE in order to determine the position of the UE. Determining the position of the UE is performed by the UE using an uplink time difference of arrival (UTDOA). The base station 1900 may also include, for example, a component for sending a downlink reference signal to be measured by the UE, which may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in a memory 1910 (such as a downlink reference signal transmission module 1926). Wherein, determining the position of the UE is performed by the UE using a round trip time (RTT) of the signal, which is determined using uplink reference signal measurements and downlink reference signal measurements measured by the UE from downlink reference signal transmissions. The other entity may be a UE, and the assistance data may be generated in response to a request for positioning and sent to the UE.

[0306] In some embodiments of the base station 1900, the positioning information is a positioning measurement message including an uplink reference signal measurement from a serving gNB and one or more uplink reference signal measurements from a neighboring gNB, and the positioning measurement message is sent to a network entity. The base station 1900 may include, for example, a component for sending a downlink reference signal to be measured by a UE, which may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in a memory 1910 (such as a downlink reference signal sending module 1926); and a component for receiving from a UE a downlink reference signal measurement measured by the UE from a downlink reference signal received by the UE, which may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in a memory 1910 (such as a downlink reference signal measurement receiving module 1928). The positioning measurement message may also include a downlink reference signal measurement measured by the UE. In some embodiments, the components for generating positioning information may include components for determining a round trip time (RTT) for each gNB using uplink reference signal measurements measured by each gNB and downlink reference signal measurements measured by the UE, which components may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910 (such as an RTT determination module 1934).

[0307] In some embodiments, the means for generating positioning information may include means for determining, by the serving gNB, the location of the UE based on uplink reference signal measurements measured by each of a plurality of neighboring gNBs, which means may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a location determination module 1936. The base station 1900 may include, for example: means for sending a downlink reference signal to be measured by the UE, which means may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a downlink reference signal sending module 1926; and means for receiving from the UE downlink reference signal measurements measured by the UE from the downlink reference signal received by the UE, which means may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910, such as a downlink reference signal measurement receiving module 1928. Determining the location of the UE may be further based on downlink reference signal measurements measured by the UE. For example, the components for determining the location of the UE may include: a component for determining the round trip time (RTT) of each gNB using uplink reference signal measurements measured by each gNB and downlink reference signal measurements measured by the UE, which may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910 (such as RTT determination module 1934); and a component for performing multi-lateration positioning using the RTT of each gNB and the known location of each gNB, which may be, for example, an external interface 1902 and one or more processors 1904 having dedicated hardware or implementing executable code or software instructions in memory 1910 (such as location determination module 1936).

[0308] Can be implemented in a variety of ways consistent with the teachings herein Figures 18 to 19 The functionality of the modules of the present invention may be implemented as one or more electronic components. In some designs, the functionality of these blocks may be implemented as a processing system including one or more processor components. In some designs, the functionality of these modules may be implemented using, for example, at least a portion of one or more integrated circuits (e.g., ASICs). As discussed herein, an integrated circuit may include a processor, software, other related components, or some combination thereof. Thus, the functionality of different modules may be implemented as, for example, different subsets of an integrated circuit, different subsets of a set of software modules, or a combination thereof. Moreover, it should be understood that a given subset (e.g., a subset of an integrated circuit and / or a set of software modules) may provide at least a portion of the functionality for more than one module.

[0309] Additionally, any suitable components may be used to implement the Figures 18 to 19 The components and functions represented by the present invention and other components and functions described herein. Such components may also be implemented at least in part using corresponding structures as taught herein. For example, the above combined Figures 18 to 19 Components described as “a means for…” may also correspond to similarly designated “means for…” functionality. Thus, in some aspects, one or more of such components may be implemented using one or more of the processor components, integrated circuits, or other suitable structures taught herein.

[0310] Those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0311] In addition, it will be appreciated by those skilled in the art that the various illustrative logic blocks, modules, circuits and algorithm phases described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, frames, modules, circuits and phases have been generally described in terms of their functions above. Whether this functionality is implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. The technician can implement the described functionality in different ways for each specific application, but this implementation decision should not be interpreted as causing a departure from the scope of the present disclosure.

[0312] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0313] The steps of the methods, sequences and / or algorithms described in conjunction with the aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integrated with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0314] In one or more exemplary aspects, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or sent via the computer-readable medium as one or more instructions or codes. Computer-readable media includes both computer storage media and communication media, and the communication media includes any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store any other medium with a desired program code in the form of an instruction or data structure and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if software is sent from a website, server, or other remote source using coaxial cable, optical cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, optical fiber cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves, are all included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0315] Although the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and / or actions of the method claims according to the aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although elements of the present disclosure may be described or claimed in the singular, plural forms may be contemplated unless limitation to the singular is explicitly stated.

Claims

1. A method for determining a location of a user equipment UE, the method comprising: include: receiving, from a serving gNB, assistance data for a plurality of gNBs, the plurality of gNBs including the serving gNB; Sending an uplink reference signal to the plurality of gNBs; receiving, from the serving gNB, uplink reference signal measurements measured by each of the plurality of gNBs, wherein the serving gNB receives the uplink reference signal measurements from other gNBs in the plurality of gNBs, the uplink reference signal measurements being time of arrival (TOA) measurements; The position of the UE is determined based on the uplink reference signal measurements measured by each of the multiple gNBs and the assistance data of the multiple gNBs.

2. The method according to claim 1, in, Determining the position of the UE uses uplink time difference of arrival UTDOA.

3. The method according to claim 1, further comprising: include: generating downlink reference signal measurements of downlink reference signals received from the plurality of gNBs; Wherein, determining the position of the UE is also based on the downlink reference signal measurement of the downlink reference signals received from the multiple gNBs.

4. The method according to claim 3, in, Determining the location of the UE includes: determining a round trip time (RTT) for each of the plurality of gNBs using the uplink reference signal measurements measured by each of the plurality of gNBs and the downlink reference signal measurements of the downlink reference signals received from the plurality of gNBs; and Multilateration is performed using the RTT of each gNB and the positioning of each gNB received in the assistance data.

5. The method according to claim 1, further comprising: include: Sending a request for positioning to the serving gNB; The serving gNB generates the auxiliary data of the multiple gNBs in response to the request for positioning and sends the auxiliary data of the multiple gNBs to the UE.

6. A user equipment UE, configured to determine a location of the UE, the UE include: a transceiver configured to communicate with the gNB; at least one memory; as well as at least one processor coupled to the transceiver and the at least one memory, the at least one processor configured to: receiving, via the transceiver, assistance data of a plurality of gNBs from a serving gNB, the plurality of gNBs including the serving gNB; sending, via the transceiver, an uplink reference signal to the plurality of gNBs; receiving, via the transceiver, from the serving gNB uplink reference signal measurements measured by each of the plurality of gNBs, wherein the serving gNB receives the uplink reference signal measurements from other gNBs in the plurality of gNBs, the uplink reference signal measurements being time of arrival (TOA) measurements; as well as The position of the UE is determined based on the uplink reference signal measurements measured by each of the multiple gNBs and the assistance data of the multiple gNBs.

7. The UE according to claim 6, in, The at least one processor is configured to determine the location of the UE using an uplink time difference of arrival (UTDOA).

8. The UE according to claim 6, in, The at least one processor is further configured to: generating downlink reference signal measurements of downlink reference signals received from the plurality of gNBs via the transceiver; Therein, the at least one processor is configured to determine the position of the UE also based on the downlink reference signal measurements of the downlink reference signals received from the multiple gNBs.

9. The UE according to claim 8, in, The at least one processor is configured to determine the location of the UE by being configured to: determining a round trip time (RTT) for each of the plurality of gNBs using the uplink reference signal measurements measured by each of the plurality of gNBs and the downlink reference signal measurements of the downlink reference signals received from the plurality of gNBs; as well as Multilateration is performed using the RTT of each gNB and the positioning of each gNB received in the assistance data.

10. The UE according to claim 6, in, The at least one processor is further configured to: sending, via the transceiver, a request for positioning to the serving gNB; The serving gNB generates the auxiliary data of the multiple gNBs in response to the request for positioning and sends the auxiliary data of the multiple gNBs to the UE.

11. A method for determining a location of a user equipment UE, performed by a serving gNB of the UE, the method include: receiving a positioning request for the UE from another entity; determining a plurality of neighboring gNBs from which the UE can measure downlink reference signal transmissions and from which uplink reference signal transmissions can be measured by the UE; transmitting a request to each of the plurality of neighboring gNBs to increase downlink reference signal transmission and measure uplink reference signal transmission from the UE; generating assistance data for the serving gNB and for the plurality of neighboring gNBs; sending the assistance data for the serving gNB and for the plurality of neighboring gNBs to the UE; receiving an uplink reference signal transmission from the UE; generating an uplink reference signal measurement for the uplink reference signal transmission; receiving one or more uplink reference signal measurements for each of the plurality of neighboring gNBs, wherein the uplink reference signal measurements are time of arrival (TOA) measurements; generating positioning information based on the uplink reference signal measurements from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB; and Sending the positioning information to the UE, The positioning information is a positioning measurement message including the uplink reference signal measurement from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB, and the positioning measurement message is sent to the UE.

12. The method according to claim 11, further comprising: include: sending a downlink reference signal to be measured by the UE; Wherein, determining the position of the UE is performed by the UE using a round trip time RTT of a signal, wherein the round trip time is determined using the uplink reference signal measurement and a downlink reference signal measurement measured by the UE from the downlink reference signal transmission.

13. The method according to claim 11, in, The other entity is the UE, and wherein the assistance data is generated in response to the positioning request and sent to the UE.

14. The method according to claim 11, in, The positioning information is a positioning measurement message including the uplink reference signal measurement from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB, and wherein the positioning measurement message is sent to a network entity.

15. The method according to claim 14, further comprising: include: sending a downlink reference signal to be measured by the UE; as well as receiving a downlink reference signal measurement from the UE, the downlink reference signal measurement being measured by the UE from a downlink reference signal received by the UE; The positioning measurement message also includes the downlink reference signal measurement measured by the UE.

16. The method according to claim 11, in, Generating the positioning information includes determining, by the serving gNB, the position of the UE based on the uplink reference signal measurements, wherein the uplink reference signal measurements are measured by each of the plurality of neighboring gNBs.

17. The method according to claim 16, further comprising: include: sending a downlink reference signal to be measured by the UE; as well as receiving a downlink reference signal measurement from the UE, the downlink reference signal measurement being measured by the UE from a downlink reference signal received by the UE; Wherein, determining the position of the UE is also based on the downlink reference signal measurement measured by the UE.

18. The method according to claim 17, in, Determining the location of the UE includes: determining a round trip time (RTT) for each gNB using the uplink reference signal measurements measured by each gNB and the downlink reference signal measurements measured by the UE; and Multilateration is performed using the RTT of each gNB and the known positioning of each gNB.

19. The method according to claim 14, further comprising: include: sending a downlink reference signal to be measured by the UE; as well as receiving a downlink reference signal measurement from the UE, the downlink reference signal measurement being measured by the UE from a downlink reference signal received by the UE; Wherein, generating the positioning information includes determining the round trip time RTT of each gNB using the uplink reference signal measurement measured by each gNB and the downlink reference signal measurement measured by the UE.

20. A gNB configured to determine a location of a user equipment UE, wherein include: at least one external interface configured to communicate with the UE, with other gNBs and with entities in the wireless network; at least one memory; as well as at least one processor coupled to the at least one external interface and the at least one memory, the at least one processor being configured to: receiving, from the UE, a location request for the UE; determining a plurality of neighboring gNBs from which the UE can measure downlink reference signal transmissions and from which uplink reference signal transmissions can be measured by the UE; transmitting a request to each of the plurality of neighboring gNBs to increase downlink reference signal transmission and measure uplink reference signal transmission from the UE; generating assistance data for the serving gNB and for the plurality of neighboring gNBs; sending, via the at least one external interface, the assistance data of the plurality of neighboring gNBs to the UE; receiving an uplink reference signal transmission from the UE via the at least one external interface; generating an uplink reference signal measurement for the uplink reference signal transmission; receiving, via the at least one external interface, one or more uplink reference signal measurements for each of the plurality of neighboring gNBs, wherein the uplink reference signal measurements are time of arrival (TOA) measurements; generating positioning information based on the uplink reference signal measurements from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB; and sending the positioning information to the UE via the at least one external interface, The positioning information is a positioning measurement message including the uplink reference signal measurement from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB, and the positioning measurement message is sent to the UE.

21. The gNB according to claim 20, in, The at least one processor is further configured to: sending, via the external interface, a downlink reference signal to be measured by the UE; Wherein, determining the position of the UE is performed by the UE using a round trip time RTT of a signal, wherein the round trip time is determined using the uplink reference signal measurement and a downlink reference signal measurement measured by the UE from the downlink reference signal transmission.

22. The gNB according to claim 20, in, The other entity is the UE, and wherein the assistance data is generated in response to the positioning request and sent to the UE.

23. The gNB according to claim 20, in, The positioning information is a positioning measurement message including the uplink reference signal measurement from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB, and wherein the positioning measurement message is sent to a network entity.

24. The gNB according to claim 23, in, The at least one processor is further configured to: sending, via the external interface, a downlink reference signal to be measured by the UE; as well as receiving, via the external interface, a downlink reference signal measurement from the UE, the downlink reference signal measurement being measured by the UE from a downlink reference signal received by the UE; The positioning measurement message also includes the downlink reference signal measurement measured by the UE.

25. The gNB of claim 20, wherein the at least one processor is configured to generate the positioning information by being configured to perform: determining, by the serving gNB, the position of the UE based on the uplink reference signal measurements measured by each of the plurality of neighboring gNBs.

26. The gNB according to claim 25, in, The at least one processor is further configured to: sending, via the external interface, a downlink reference signal to be measured by the UE; as well as receiving, via the external interface, a downlink reference signal measurement from the UE, the downlink reference signal measurement being measured by the UE from a downlink reference signal received by the UE; Therein, the position of the UE is also based on the downlink reference signal measurement measured by the UE.

27. The gNB according to claim 26, in, The at least one processor is configured to determine the location of the UE by being configured to: determining a round trip time (RTT) for each gNB using the uplink reference signal measurements measured by each gNB and the downlink reference signal measurements measured by the UE; as well as Multilateration is performed using the RTT of each gNB and the known positioning of each gNB.

28. The gNB according to claim 23, in, The at least one processor is further configured to: sending, via the external interface, a downlink reference signal to be measured by the UE; as well as receiving, via the external interface, a downlink reference signal measurement, the downlink reference signal measurement being measured by the UE from a downlink reference signal received by the UE; The at least one processor is configured to generate the positioning information by being configured to perform the following items: determine the round-trip time RTT of each gNB using the uplink reference signal measurement measured by each gNB and the downlink reference signal measurement measured by the UE.

29. A computer readable storage medium having stored thereon computer instructions which, when executed, cause a processor to: receiving, from a serving gNB, assistance data for a plurality of gNBs, the plurality of gNBs including the serving gNB; Sending an uplink reference signal to the plurality of gNBs; receiving, from the serving gNB, uplink reference signal measurements measured by each of the plurality of gNBs, wherein: The serving gNB receives the uplink reference signal measurement from other gNBs in the plurality of gNBs, the uplink reference signal measurement being a time of arrival TOA measurement; Determine a location of the UE based on the uplink reference signal measurements measured by each of the multiple gNBs and the assistance data of the multiple gNBs.

30. A computer readable storage medium having stored thereon computer instructions which, when executed, cause a processor to: receiving, from a UE, a location request for the UE; determining a plurality of neighboring gNBs from which the UE can measure downlink reference signal transmissions and from which uplink reference signal transmissions can be measured by the UE; transmitting a request to each of the plurality of neighboring gNBs to increase downlink reference signal transmission and measure uplink reference signal transmission from the UE; generating assistance data for the serving gNB and for the plurality of neighboring gNBs; Sending the assistance data of the plurality of neighboring gNBs to the UE; receiving an uplink reference signal transmission from the UE; generating uplink reference signal measurements for the serving gNB and for the uplink reference signal transmission; receiving one or more uplink reference signal measurements for each of the plurality of neighboring gNBs, wherein the uplink reference signal measurements are time of arrival (TOA) measurements; generating positioning information based on the uplink reference signal measurements from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB; and Sending the positioning information to the UE, The positioning information is a positioning measurement message including the uplink reference signal measurement from the serving gNB and the one or more uplink reference signal measurements from the neighboring gNB, and the positioning measurement message is sent to the UE.

Citation Information

Patent Citations

  • System and methods for supporting uplink and downlink positioning procedures in a wireless network

    US20200137715A1

  • Network-based location of mobile transmitters

    CN103026253A

  • Positioning beacons with wireless backhaul

    CN106415300A

  • Method for providing network-based measurements for user equipment-based positioning

    US20120258733A1

  • Methods and Arrangements for Estimating Timing Offset Differences in a Cellular Network

    US20140016621A1