System and method for ultra-low latency positioning services in wireless networks

By using control plane signaling and protocol-level positioning measurement in wireless networks, combined with RSTD and Rx-Tx measurements, the problems of insufficient positioning delay and accuracy in the prior art are solved, and high accuracy in smart factories and hazardous places are achieved Low-latency positioning service.

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

Patent Information

Application Number
CN201980080992.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-12-11
Filing Date
2019-12-12
Publication Date
2024-11-15
Estimated Expiration
2039-12-12

AI Technical Summary

Technical Problem

Existing wireless network positioning solutions cannot provide positioning accuracy of less than 1 meter and delays of less than 1 second in 1 second, especially in applications in smart factories, warehouses and hazardous places, which cannot meet high-precision and low-delay need.

Method used

By using control plane signaling between the user equipment (UE) and the serving base station, combining positioning measurements at the Layer 1 and Layer 2 protocol levels, such as reference signal time difference (RSTD) and reception time-transmission time difference (Rx-Tx) Measure, reduce end-to-end delay, and send positioning reports using user plane signaling.

Benefits of technology

It realizes the provision of high-precision and low-latency positioning services in applications such as smart factories, warehouses and dangerous places, meeting the needs of fast positioning of mobile objects, reducing delays and improving positioning accuracy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113170278B_ABST
    Figure CN113170278B_ABST
Patent Text Reader

Abstract

The external client requests the positioning of the UE using control plane signaling. The UE sends downlink positioning measurements, such as reference signal time difference, for multiple BSs to a serving base station (BS) at a first periodic interval at a layer 1 or layer 2 protocol level. The UE and the multiple BSs send additional positioning measurements, such as receive time ‑ transmit time difference, to the serving BS at a second periodic interval that is longer than the first periodic interval. The serving BS uses the additional positioning measurements and the downlink positioning measurements to determine timing information, such as real time difference, for the multiple BSs. The serving BS determines the positioning of the UE using the downlink positioning measurements and the timing information at the first periodic interval and sends the positioning to the external client using user plane signaling to reduce latency.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the U.S. Provisional Application No. 62 / 778,852, filed on December 12, 2018, entitled “SYSTEMS AND METHODS FOR LOCATION REPORTING WITH LOW LATENCY FOR FIFTH GENERATION WIRELESS NETWORKS”, U.S. Provisional Application No. 62 / 783,123, filed on December 20, 2018, entitled “SYSTEMS AND METHODS FOR LOCATION REPORTING WITH LOW LATENCY FOR FIFTH GENERATION WIRELESS NETWORKS”, U.S. Provisional Application No. 62 / 805,029, filed on February 13, 2019, entitled “SYSTEMS AND METHODS FOR SUPER LOWLATENCY LOCATION SERVICE FOR FIFTH GENERATION WIRELESS NETWORKS”, and U.S. Provisional Application No. 62 / 816,031, filed on December 9, 2019, entitled “SYSTEMS AND METHODS FOR LOCATION REPORTING WITH LOW LATENCY FOR FIFTH GENERATION WIRELESS NETWORKS”. The present invention relates to the benefit of U.S. Provisional Application No. 62 / 945,664, entitled “SYSTEMS AND METHODS FOR SUPER LOW LATENCY LOCATION SERVICE FOR WIRELESS NETWORKS,” filed on December 11, 2019, which are assigned to their assignees and are expressly incorporated herein by reference in their entireties. Technical Field

[0003] The present disclosure relates generally to communications, and more particularly, to techniques for supporting positioning services for user equipment (UE). Background Art

[0004] Certain positioning use cases require very low latency when providing the location of a mobile device to external clients. Examples include: smart (automated) factories and warehouses, where the location of tools, items being manufactured, and packages may need to be known with an accuracy of 10 centimeters (cm) or less and a latency of less than 1 second; drones that may need to know their location with an accuracy of 1 meter within one second; public safety first responders in hazardous locations (such as inside a burning or partially collapsed building); and use cases associated with moving vehicles and pedestrians (referred to as V2X). Other use cases associated with very high positioning accuracy may also have very low latency requirements due to the rapid deterioration of positioning accuracy for moving objects. For example, even at 4mph (normal walking speed), an object will move 1.79 meters in 1 second, thereby negating the benefit of 1 meter positioning accuracy after less than 1 second.

[0005] Current positioning solutions may have a latency of 5 to 10 seconds or more, and there is no known positioning solution for wireless networks that has a latency that is consistently less than 1 second, except for solutions that use mobile device-based positioning, where the mobile device or an app in the mobile device is also the client of the determined location. Summary of the invention

[0006] Methods and techniques for reducing end-to-end latency in positioning determination of a user equipment (UE) are described. Control plane signaling can be used to support positioning requests for a UE from an external client because the control plane signaling can be performed only occasionally. The external client requests positioning of the UE using control plane signaling. The UE sends downlink positioning measurements, such as reference signal time differences, to a serving base station (BS) at a layer 1 or layer 2 protocol level and at a first periodic interval for multiple BSs. The UE and the multiple BSs send additional positioning measurements, such as receive time-transmit time differences, to the serving BS at a second periodic interval that is longer than the first periodic interval. The serving BS uses the additional positioning measurements and the downlink positioning measurements to determine timing information, such as real time differences, for the multiple BSs. The serving BS uses the downlink positioning measurements and the timing information to determine the positioning of the UE at a first periodic interval, and sends the positioning to the external client using user plane signaling to reduce latency.

[0007] In one implementation, a method for locating a user equipment (UE) performed by a positioning server function located at a serving base station for the UE in a radio access network (RAN) includes: receiving a request to locate the UE, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling; receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level; using the positioning information to calculate the positioning of the UE; and sending a positioning report including the positioning of the UE to the external client using user plane signaling.

[0008] In one implementation, a positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and capable of locating the UE includes: an external interface configured to communicate with one or more base stations, one or more network nodes, and one or more UEs in the RAN; at least one memory; at least one processor coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: receive a request to locate the UE via the external interface, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling; receive positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level via the external interface; calculate the positioning of the UE using the positioning information; and send a positioning report including the positioning of the UE to the external client using user plane signaling via the external interface.

[0009] In one implementation, a positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and configured to locate the UE includes: a component for receiving a request to locate the UE, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling; a component for receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level; a component for calculating the positioning of the UE using the positioning information; and a component for sending a positioning report including the positioning of the UE to the external client using user plane signaling.

[0010] In one implementation, a non-transitory computer-readable medium includes program code stored thereon, the program code being operable to configure at least one processor in a positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and configured to locate the UE, the program code including: program code for receiving a request to locate the UE, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling; program code for receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level; program code for calculating the positioning of the UE using the positioning information; and program code for sending a positioning report including the positioning of the UE to the external client using user plane signaling.

[0011] In one implementation, a method for locating a user equipment (UE) performed by the UE includes: receiving a first request for a first positioning measurement and a second request for a second positioning measurement from a serving base station in a radio access network (RAN); sending the first positioning measurement to the serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval; and sending the second positioning measurement to the serving base station at a second periodic interval, wherein the first periodic interval is shorter than the second periodic interval.

[0012] In one implementation, a user equipment (UE) capable of supporting positioning includes a wireless transceiver configured to wirelessly communicate with a base station in a radio access network (RAN); at least one memory; at least one processor coupled to the wireless transceiver and the at least one memory, wherein the at least one processor is configured to: receive a first request for a first positioning measurement and a second request for a second positioning measurement from a serving base station in the radio access network (RAN) via the wireless transceiver; send the first positioning measurement to the serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval via the wireless transceiver; and send the second positioning measurement to the serving base station at a second periodic interval via the wireless transceiver, wherein the first periodic interval is shorter than the second periodic interval.

[0013] In one implementation, a user equipment (UE) capable of supporting positioning of the UE includes a component for receiving a first request for a first positioning measurement and a second request for a second positioning measurement from a serving base station in a radio access network (RAN); a component for sending the first positioning measurement to the serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval; and a component for sending the second positioning measurement to the serving base station at a second periodic interval, wherein the first periodic interval is shorter than the second periodic interval.

[0014] In one implementation, a non-transitory computer-readable medium includes program code stored thereon, the program code being operable to configure at least one processor in a user equipment (UE) capable of supporting positioning of the UE, the code comprising: program code for receiving a first request for a first positioning measurement and a second request for a second positioning measurement from a serving base station in a radio access network (RAN); program code for sending the first positioning measurement to the serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval; and program code for sending the second positioning measurement to the serving base station at a second periodic interval, wherein the first periodic interval is shorter than the second periodic interval. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] An understanding of the nature and advantages of the various embodiments may be achieved by reference to the following drawings.

[0016] Figure 1 is a simplified block diagram showing a network architecture supporting very low latency location services (SLLLS) for non-roaming UEs.

[0017] Figure 2 It is a representation of the protocol stack of the control plane between the UE and the serving base station.

[0018] Figure 3 is a representation of the protocol layers that may be used when a base station in a radio access network (RAN) transmits a positioning report for a target UE to an external client.

[0019] Figure 4 A positioning session establishment and reporting procedure for supporting SLLLS applicable to a positioning server function in a serving base station is shown.

[0020] Figure 5 A process for supporting positioning measurement configuration of a positioning server function in a serving base station to support SLLLS is shown.

[0021] Figure 6 A process for a serving base station to support positioning reporting to support SLLLS is shown.

[0022] Figure 7 A process for supporting changing a serving base station for a target UE in an RRC connected state or an RRC inactive state is shown.

[0023] Figure 8 A process flow illustrating a method performed by a positioning server function in a serving base station in a wireless network for locating a user equipment (UE) is shown.

[0024] Fig. 9 A process flow illustrating a method performed by a user equipment (UE) for locating the UE is shown.

[0025] Fig.10 is a block diagram of an embodiment of a positioning server function or a serving base station supporting SLLLS.

[0026] Fig.11 is a block diagram of an embodiment of a user equipment supporting SLLLS.

[0027] According to some example implementations, the same reference numerals and symbols in the various drawings represent the same elements. In addition, multiple instances of an element can be indicated by adding a letter or hyphen to the first digit of the element and a second digit. For example, multiple instances of element 110 can be indicated as 110-1, 110-2, 110-3, etc. When only the first digit is used to refer to such an element, it should be understood that any instance of the element (e.g., element 110 in the previous example will refer to elements 110-1, 110-2, and 110-3). DETAILED DESCRIPTION

[0028] The user equipment (UE) of the Industrial IoT (IIoT) may be, or may be attached to or embedded in some tools, objects, parts or components used in a smart (automated) factory, or may be attached to or embedded in a package, object or component in a smart (automated) warehouse or supply station. Such UEs may need to be positioned with high accuracy to allow fast, efficient and smooth operation of the smart factory, warehouse or supply station. Possible positioning requirements (e.g., as determined by the Third Generation Partnership Project (3GPP)) may include: (1) very high positioning accuracy (e.g., a maximum positioning error of 1-10 cm); (2) very low latency (e.g., less than 1 second and possibly less than 100 milliseconds (ms)) in obtaining and reporting UE positioning to external clients; and (3) low or limited cost to support positioning of all UEs. Existing wireless network solutions do not appear to be able to achieve all three of these goals. However, positioning support associated with wireless networks (e.g., 5G wireless networks) may be attractive to smart factories and warehouses because of the ability to use wireless networks to similarly control the operations of smart factories and warehouses via high-speed, high-bandwidth, and low-latency data communications between mobile elements (such as objects, tools, parts, packages) and servers that monitor and control these mobile elements.

[0029] One implementation of positioning support suitable for IIoT and other uses that can achieve the above three goals as part of fifth generation (5G) wireless networks can use one or more of the five separate components described below.

[0030] Component 1: A target device (e.g., a factory tool) with an embedded UE sends a 5G reference signal time difference (RSTD) or other positioning measurement to a serving base station (SBS) for the embedded UE at a low latency and low periodicity interval (e.g., every 50-200 ms) at a Layer 1 (L1) or Layer 2 (L2) protocol level. Using Layer 1 / Layer 2 (L1 / L2) signaling can reduce latency and enable reporting at a lower periodicity interval (also known as a lower periodicity or higher frequency) than using a higher protocol level (such as Layer 3 (L3) which may correspond to a radio resource control (RRC) protocol layer). The UE may use L1 / L2 signaling when in an RRC connected state. For a UE in an RRC idle state or an RRC inactive state, the UE may send RSTD or other positioning measurements to the SBS at the L3 level (e.g., using RRC) and latency may be reduced by not entering an RRC connected state. Note that the terms "protocol layer" and "protocol level" are used interchangeably herein.

[0031] Component 2: Positioning reports may be encrypted to ensure privacy if not otherwise encrypted at L1 / L2. The encryption key may be provided by a higher protocol layer (e.g. using the non-access stratum protocol layer (NAS) from the service access and mobility management function (AMF) or the RRC layer from the SBS).

[0032] Component 3: The SBS for the target UE calculates the UE positioning at low periodic intervals (e.g., every 50-200ms) using the observed time difference of arrival (OTDOA) applied to the RSTD measurements received from the UE, and sends the UE positioning to an external client (e.g., which can be part of a factory server or controller) at the user plane level (e.g., using TCP / IP) to reduce latency.

[0033] Component 4: Other base stations and UEs may send positioning measurements, such as time of arrival (TOA) measurements and / or receive time-transmit time difference (Rx-Tx) measurements (and possible AOA / AOD measurements) to the SBS at higher periodic intervals (also referred to as higher periodicity or lower frequency) (e.g., every 1-5 seconds). Higher periodicity intervals may be used because base station to base station (BS) communications may occur at higher protocol layers and may pass through intermediate entities (e.g., other BSs), which will increase latency. The SBS may use positioning measurements (e.g., TOA or Rx-Tx measurements) to calculate the round-trip signal propagation time (RTT) between the UE and each BS. The RTT is then combined with the RSTD measurements from component 1 to calculate (using known equations) the real time difference (RTD) between the BSs, which is required to calculate positioning using OTDOA as part of component 3. Typically, the RTD will be stable, so the calculation of the RTD is primarily used to verify stability and detect any small changes. This may be equivalent to periodic RTD recalibration. Specifically, although individual UE positions may be calculated and reported at a higher frequency according to components 1-3, in order to implement component 3, RTD may be obtained at a lower frequency according to component 4.

[0034] Component 5: The Rx-Tx measurements of component 4 can be obtained from multiple UEs (e.g., of the same SBS) and used to determine (or recalibrate) the same RTD, which can reduce the load on individual UEs and on the BS and improve the accuracy, latency and reliability of RTD determination or recalibration.

[0035] Derivation of the RTD according to components 4 and 5 avoids the need for costly synchronization of the BSs using other methods (e.g., using a GPS receiver with an external antenna in each BS). In indoor mmWave RF environments with line of sight (LOS) between the UE and the BS, positioning accuracy using OTDOA can be very high due to the ability to use very high bandwidth signals (e.g., 100-400 MHz or higher). Likewise, the latency of the user plane being transmitted from the SBS to nearby external clients can be very low.

[0036] Therefore, in order to minimize latency, the positioning server function at the SBS for the UE can use control plane signaling to receive a request from an external client to locate the UE. Control plane signaling can be used to support positioning requests from external clients without affecting latency, because the positioning request for the UE can be performed only once or infrequently. Positioning information from the UE can be received by the SBS at the L1 or L2 protocol level, which can be, for example, RSTD measurements. Encryption of positioning information can be used for privacy considerations. The positioning information can be used to determine the location of the UE and reported to the external client using user plane signaling to minimize latency.

[0037] Additional positioning information may be provided by the UE, such as Rx-Tx measurements for multiple base stations. The positioning server function in the SBS may receive measurements of uplink (UL) signals sent by the UE from each of the multiple base stations, such as TOA or Rx-Tx measurements. Using the additional measurements received from the UE and the base stations, the positioning server function may determine timing information for the multiple base stations, such as RTD, which may be used to help determine the positioning of the UE. If necessary, measurements of other UEs may be used to determine the timing information of the base stations.

[0038] The UE may send a first positioning measurement, such as an RSTD measurement, at a first cycle interval, and send a second positioning measurement, such as an Rx-Tx measurement, at a second cycle interval. However, because the second measurement (and the measurement of the UE's UL signal from the base station) is used to determine relatively stable timing information (such as RTD), the first cycle interval may be shorter than the second cycle interval and may be shorter than the interval at which the UE sends the UL signal.

[0039] Figure 1 The network architecture supporting Very Low Latency Location Services (SLLLS) for non-roaming UEs is shown and may be consistent with the 3GPP positioning solution expected in Release 16 of 5GCN and NG-RAN with some minor extensions.

[0040] Figure 1 A communication system 100 is shown that includes a UE 105, which is referred to herein as a "target UE" because the UE 105 may be the target of a positioning request. Figure 1Also shown are components of a fifth generation (5G) network, including a next generation radio access network (NG-RAN) 112 including base stations (BSs) sometimes referred to as new radio (NR) NodeBs or gNBs 110-1, 110-2, 110-3, and 110-4 (collectively referred to herein as gNBs 110), and a 5G core network (5GCN) 150 that communicates with external clients 130. A 5G network may also be referred to as a new radio (NR) network or a 5G system (5GS); NG-RAN 112 may be referred to as NG-RAN or 5G RAN; and 5GCN 150 may be referred to as a next generation (NG) core network (NGC). The communication system 100 may also utilize information from a space vehicle (SV) 190 for a global navigation satellite system (GNSS), such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional satellite positioning system (SPS), such as IRNSS, EGNOS, or WAAS (e.g., when operating partially or completely outdoors, or when an outdoor antenna is available). Additional components of the communication system 100 are described below. The communication system 100 may include additional or alternative components.

[0041] Figure 1Also shown are a serving gNB (SgNB) 110-1 and neighboring gNBs (NgNBs) 110-2, 110-3, 110-4 for the target UE 105. The NgNB 110 may be any gNB 110 capable of receiving and measuring uplink (UL) signals sent by the target UE 105 and / or capable of sending downlink (DL) reference signals (RS) that may be received and measured by the target UE 105. The SgNB 110-1 supports a positioning server function, which may be referred to as a positioning management component (LMC) or a local positioning management function (LLMF). The functions supported by SgNB 110-1 may include one or more of the following: receiving a request for positioning of target UE 105 from AMF 154; coordinating the positioning of target UE 105 by obtaining a series of positioning estimates for target UE 105 (e.g., periodic or triggered positioning); configuring positioning measurements for target UE 105 in other gNBs 110 (e.g., NgNB 110) and / or target UE 105; configuring the transmission of UL signals (e.g., UL RS) of target UE 105 (to be measured by gNB 110) and / or the transmission of DL RS of gNB 110 (to be measured by target UE 105); receiving positioning measurements for target UE 105 from target UE 105 and / or from other gNBs 110; calculating a positioning estimate for target UE 105; transmitting the positioning estimate to external client 130; and supporting SgNB 110-1 due to the target UE 105 moving to a new SgNB 110-1. Changes of 110-1.

[0042] The SgNB 110-1 itself may perform the positioning server function, or a physically separate server that does not support the gNB function but is located at and / or connected to the SgNB 110-1 may perform the positioning server function. Such a physically separate positioning server function may be referred to as an LMC server or an LLMF server. For ease of reference, the SgNB 110-1 will be described herein as performing the positioning server function. All or a subset of the control functions for positioning services may be performed by the SgNB 110-1, or some of the control functions may be performed by another NgNB 110 or some further away gNB 110.

[0043] Figure 1A user plane aggregator (UPA) 153 is also shown. The UPA 153 is optional and enables the external client 130 to receive positioning reports for target UEs by interacting only with the UPA 153. When the UPA 153 is not present, the external client 130 will need to interact with the SgNB 110-1 for each target UE for which the external client 130 has initiated a positioning report, which may be less efficient (e.g., when the SgNB 110-1 for the target UE 105 changes) and / or may be a security risk for the SgNB and / or the external client 130. The UPA 153 avoids the need for the SgNB 110-1 to establish positioning reporting sessions to multiple external clients and for the external client to establish positioning reporting sessions to multiple SgNBs. The UPA 153 may also provide security for the NG-RAN 112 and / or the external client 130 by authenticating and authorizing the external client 130 and / or the SgNB 110-1. UPA 153 may be part of 5GCN 150, or may be external to 5GCN 150 (eg, may be associated with external client 130).

[0044] The NG-RAN 112 may also include a positioning measurement unit (LMU) ( Figure 1 Not shown) and / or positioning transmission unit (LTU) ( Figure 1 The positioning measurement unit may receive and measure signals from the target UE 105 but may not send signals to the UE in normal network operation. The positioning transmission unit may send reference signals to be measured by the target UE 105 but may not receive signals from the UE in normal network operation. The LMU or LTU may be connected to one or more other gNBs 110 and / or AMF 154. The LMU and LTU may be combined in the same physical entity. The LTU and / or LMU may also perform some positioning server functions.

[0045] The entity in the NG-RAN 112 that transmits DL reference signals (RS) for a particular positioning session to be measured by the target UE 105 is generally referred to as a "transmission point (TP)", and may include one or more of the SgNB 110-1, NgNB 110-2, 110-3, 110-4, and LTU (not shown). In some cases, the SgNB 110-1, NgNB 110 and / or LTU may each include multiple TPs (e.g., where each TP is associated with a different cell and / or uses a different antenna or a different set of antenna elements).

[0046] The entity in the NG-RAN that receives and measures the UL signals (e.g., RS) sent by the target UE 105 for a particular positioning session is generally referred to as a "reception point (RP)" and may include one or more of the SgNB 110-1, NgNB 110-2, 110-3, 110-4, and LMU (not shown). In some cases, the SgNB 110-1, NgNB 110, and / or LMU may each include multiple RPs (e.g., where each RP is associated with a different cell and / or uses a different antenna or a different set of antenna elements).

[0047] It should be noted that Figure 1 Only a general description of the various components is provided, any or all of which may be used as appropriate, and each of which may be repeated or omitted as desired. Specifically, although only one UE 105 is shown, it should be understood that multiple UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include a greater or lesser number of SVs 190, gNBs 110, external clients 130, and / or other components. The connections shown 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.

[0048] Although Figure 1 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), and IEEE 802.11 WiFi, etc. For example, in the case of a wireless local area network (WLAN) (e.g., an IEEE 802.11 radio interface), the UE 105 may communicate with an access network (AN) (rather than an NG-RAN), and thus, the component 112 is sometimes referred to herein as a radio access network (RAN), represented by the terms "RAN," "(R)AN," or "(R)AN 112." In the case of an AN (e.g., an IEEE 802.11 AN), the AN may be connected to a non-3GPP interworking function (N3IWF) (e.g., in the 5GCN 150) ( Figure 1 ), and N3IWF is connected to AMF 154.

[0049] As used herein, target UE 105 can be any electronic device, and can be referred to as device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), terminal (SET) enabling secure user plane positioning (SUPL) or some other name.Target UE 105 can be an independent device, or can be embedded in another device (such as factory tool) to be monitored or tracked.In addition, UE 105 can correspond to smart watch, digital glasses, fitness monitor, smart car, smart appliance, mobile phone, smart phone, laptop computer, tablet computer, PDA, tracking device, control device or some other portable or removable device.UE 105 can include a single entity, or can include multiple entities, such as an entity in a personal area network where a user can use audio, video and / or data I / O devices and / or body sensors and separated wired or wireless modems. Typically, although not necessarily, the UE 105 can support wireless communications using one or more radio access technologies (RATs), such as GSM, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 112 and 5GCN 150), etc. UE 105 may also support wireless communications using a wireless local area network (WLAN), which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or a packet cable. The use of one or more of these RATs may allow UE 105 to communicate with external clients 130 (e.g., via Figure 1 Elements of the 5GCN 150 not shown in the figure, or possibly via a Gateway Mobile Location Center (GMLC) 155), and / or allowing an external client 130 to receive positioning information about the UE 105 (e.g., via the GMLC 155).

[0050] UE 105 may enter a connected state with a wireless communication network, which may include NG-RAN 112. In one example, UE 105 may communicate with a cellular communication network by sending or receiving wireless signals to or from a cellular transceiver, such as gNB 110, in NG-RAN 112. The transceiver provides user and control plane protocol termination for UE 105 and may be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a radio network controller, a transceiver function, a base station subsystem (BSS), an extended service set (ESS), or some other suitable terminology.

[0051] In a particular implementation, the UE 105 may have circuitry and processing resources capable of obtaining positioning-related measurements. The positioning-related measurements obtained by the UE 105 may include measurements of signals received from a SV 190 belonging to a satellite positioning system (SPS) or a global navigation satellite system (GNSS) (such as GPS, GLONASS, Galileo, or BeiDou), and / or may include measurements of signals received from a ground transmitter fixed at a known location (e.g., gNB 110). The UE 105 or the SgNB 110-1 to which the UE 105 may send the measurements may then obtain a positioning estimate for the UE 105 based on these positioning-related measurements using any of a number of positioning methods, such as GNSS, Assisted GNSS (A-GNSS), Advanced Forward Link Trilateration (AFLT), Observed Time Difference of Arrival (OTDOA), WLAN (also known as WiFi) positioning, Angle of Departure (AOD), Angle of Arrival (AOA), Multi-cell Round Trip Time (Multi-RTT), or Enhanced Cell ID (ECID), or a combination thereof. In some of these techniques (e.g., A-GNSS, AFLT, and OTDOA), pseudoranges or timing differences can be measured at the UE 105 relative to three or more terrestrial transmitters (e.g., gNB 110) fixed at known locations, or relative to four or more SVs 190 with precisely known orbit data, or relative to a combination thereof, based at least in part on pilots, positioning reference signals (PRS), or other positioning-related signals transmitted by transmitters or satellites and received at the UE 105.

[0052] SgNB 110-1 or other positioning server (e.g., LMC server or LLMF server) may be able to provide positioning assistance data to UE 105, including, for example, information about signals to be measured (e.g., expected signal timing, signal coding, signal frequency, signal Doppler), the location and identification of ground transmitters (e.g., gNB 110), and / or signal, timing, and orbit information for GNSS SV 190 to facilitate positioning techniques such as A-GNSS, AFLT, OTDOA, AOD, Multi-RTT, and ECID. This facilitation may include improving signal acquisition and measurement accuracy for UE 105, and in some cases, enabling UE 105 to calculate its estimated position based on positioning measurements. For example, an LMC server, LLMF server, or other positioning server (e.g., SgNB 110-1) may include an almanac (also known as a base station almanac (BSA) that indicates the location and identification of local transceivers and / or cellular transceivers (e.g., gNB 110) in one or more specific areas such as a specific location) and may provide information describing signals sent by a cellular base station or AP (e.g., gNB 110), such as transmit power and signal timing. UE 105 can obtain measurements of signal strength (e.g., received signal strength indication (RSSI)) of signals received from a cellular transceiver and / or a local transceiver, and / or can obtain a signal-to-noise ratio (S / N), a reference signal received power (RSRP), a reference signal received quality (RSRQ), a time of arrival (TOA), an angle of arrival (AOA), an angle of departure (AOD), a receive time-transmit time difference (Rx-Tx), or a round-trip signal propagation time (RTT) between UE 105 and a cellular transceiver (e.g., gNB 110) or a local transceiver (e.g., a WiFi access point (AP)). UE 105 may send these measurements to a positioning server (such as SgNB 110-1) to determine the position of UE 105, or in some implementations, these measurements may be used together with assistance data (e.g., terrestrial almanac data or GNSS satellite data such as GNSS almanac and / or GNSS ephemeris information) received from an LMC server, LLMF server, or other positioning server (e.g., SgNB110-1) or broadcast by a base station in NG-RAN 112 (e.g., gNB 110) to determine the position of UE 105.

[0053] In the case of OTDOA, UE 105 may measure a reference signal time difference (RSTD) between signals, such as a positioning reference signal (PRS), a cell-specific reference signal (CRS), or a tracking reference signal (TRS) transmitted by a nearby transceiver and a base station (e.g., gNB 110). The RSTD measurement may provide an arrival time difference between signals (e.g., TRS, CRS, or PRS) received from two different transceivers at UE 105. UE 105 may return the measured RSTD to an LMC server, LLMF server, or other positioning server (e.g., SgNB 110-1), which may calculate an estimated position of UE 105 based on the known positions of the measured transceivers and the known signal timing.

[0054] In some implementations of OTDOA, the signals used for RSTD measurements (e.g., PRS or CRS signals) may be precisely synchronized by the transceivers to a common universal time, such as GPS time or Coordinated Universal Time (UTC), e.g., using a GPS or GNSS receiver at each transceiver to accurately obtain the common universal time. In the techniques described herein, precise synchronization of the gNBs 110 may not be required because the RTD between a pair of gNBs 110 can be obtained. Such RTD may also be used to help precisely (or approximately) synchronize the gNBs 110 without requiring a GPS or GNSS receiver in each gNB 110.

[0055] In some implementations, network-based positioning methods may be used to locate the target UE 105. Using these methods, entities in the network (such as the gNB 110 and / or LMU) may measure UL signals transmitted by the UE 105. The UL signals may include or contain UL reference signals, such as UL positioning reference signals (PRS). The entity (e.g., the gNB 110 and / or LMU) that obtains the positioning measurements may then send the positioning measurements to a positioning server (e.g., SgNB 110-1), which may calculate the position of the target UE 105. Examples of UL positioning measurements may include RSSI, RSRP, RSRQ, TOA, Rx-Tx, AOA, and RTT. Examples of positioning methods may include an uplink time difference of arrival (UTDOA) method, which may utilize TOA measurements obtained by a gNB 110 and / or LMU whose timing is precisely synchronized or aligned with a common absolute time, such as GPS time. Another example positioning method may be ECID, which may utilize any of RSSI, RSRP, RSRQ, TOA, Rx-Tx, AOA, and RTT measurements.

[0056] With a UE-assisted positioning method, UE 105 may obtain positioning measurements (e.g., measurements of RSSI, Rx-Tx, RTT, RSTD, RSRP, and / or RSRQ for gNB 110, or measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190) and send the measurements to an entity performing positioning server functions (such as SgNB 110-1) for use in calculating a positioning estimate for UE 105. With a UE-based positioning method, UE 105 may obtain positioning measurements (e.g., which may be the same or similar to positioning measurements of a UE-assisted positioning method) and may additionally calculate the positioning of UE 105 (e.g., with the aid of assistance data received by a point-to-point component from a positioning server (such as SgNB 110-1) or broadcast by gNB 110).

[0057] The estimate of the location of the UE 105 may be referred to as a location, a location estimate, a location fix, a fix, a position, a location estimate, or a location fix, and may be geographic, thereby providing location coordinates (e.g., latitude and longitude) for the UE 105, which may or may not include a height component (e.g., height above sea level, height above ground level, floor level, or basement level, or depth below). Alternatively, the location of the UE 105 may be expressed as an urban location (e.g., as a postal address or a designation of a point or small area in a building (such as a particular room or floor)). The location of the UE 105 may also be expressed as an area or volume (defined in geographic or urban terms) in which the UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The positioning of UE105 can also be relative positioning, which includes, for example, distance and direction, or relative X, Y (and Z) coordinates defined relative to a certain origin at a known positioning location, which can be defined geographically, in urban terms, or by referring to a point, area or volume indicated on a map, floor plan or building plan. The positioning can be expressed as an absolute positioning estimate (such as positioning coordinates or address) to the UE, or as a relative positioning estimate (such as the distance and direction from a previous positioning estimate or a known absolute positioning) to the UE. The positioning of UE 105 can include linear velocity, angular velocity, linear acceleration, angular acceleration, angular orientation of UE 105 (for example, the orientation of UE 105 relative to a fixed global or local coordinate system), an identifier of a triggering event for positioning UE 105, or some combination of these. For example, a triggering event can include a regional event, a motion event or a speed event. For example, a regional event can be that UE 105 moves into a defined area, moves outside the area, and / or stays in the area. For example, a motion event may include a UE 105 moving a threshold straight-line distance or a threshold distance along the trajectory of the UE 105. For example, a speed event may include a UE 105 reaching a minimum or maximum speed, a threshold increase and / or decrease in speed, and / or a threshold change in direction. In the description contained herein, unless otherwise indicated, the use of the term "positioning" may include any of these variations. When calculating the position of the UE 105, local x, y, and (possibly) z coordinates are typically solved, and then, if necessary, the local coordinates are converted to absolute coordinates (e.g., latitude, longitude, and altitude above or below mean sea level).

[0058] like Figure 1 As shown, the gNB 110 pairs in the NG-RAN 112 can be connected to each other, for example, as Figure 1The UE 105 may be directly connected as shown or indirectly connected via other gNBs 110. The UE 105 may be provided with access to the 5G network through wireless communication between the UE 105 and one or more of the gNBs 110. The gNB 110 may provide wireless communication access to the 5GCN 150 using 5G (e.g., NR) on behalf of the UE 105. Figure 1 , it is assumed that the serving gNB for UE 105 (SgNB) is gNB 110-1, although other gNBs (e.g., gNB 110-2 and / or gNB 110-3) may serve as serving gNBs if UE 105 moves to another location, or may serve as auxiliary gNBs to provide additional throughput and bandwidth to UE 105. Figure 1 Some of the gNBs 110 (e.g., gNB 110-2 or gNB 110-3) may be configured to function as positioning-dedicated beacons (referred to herein as LTUs), which may send signals (e.g., directional PRSs) to assist in locating UE 105, but may not receive signals from UE 105 or other UEs.

[0059] As mentioned above, although Figure 1 Nodes configured to communicate according to a 5G communication protocol are depicted, but nodes configured to communicate according to other communication protocols (e.g., LTE protocols) may be used. Such nodes configured to communicate using different protocols may be controlled, at least in part, by the 5GCN 150. Thus, the NG-RAN 112 may include any combination of gNBs, evolved Node Bs (eNBs), or other types of base stations or access points. As an example, the NG-RAN 112 may include one or more next-generation eNBs (ng-eNBs) ( Figure 1 ), which provides LTE wireless access to UE 105 and can connect to entities in 5GCN 150 (such as AMF 154).

[0060] The gNB 110 and / or ng-eNB may communicate with an access and mobility management function (AMF) 154, which may communicate with a location management function (LMF) 152 for positioning functions. The AMF 154 may support the mobility of the UE 105, including cell changes and handovers, and may participate in supporting signaling connections to the UE 105 and may assist in establishing and releasing protocol data unit (PDU) sessions for the UE 105 supported by the UPF 151. Other functions of the AMF 154 may include: terminating the control plane (CP) interface from the NG-RAN 112; terminating the non-access stratum (NAS) signaling connection, NAS ciphering and integrity protection from a UE such as the UE 105; registration management; connection management; reachability management; mobility management; access authentication and authorization.

[0061] The LMF 152 or SgNB 110-1 may support positioning of the UE 105 when the UE 105 accesses the NG-RAN 112, and may support positioning 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), WLAN positioning, Multi-RTT, UTDOA, and / or other positioning methods. The SgNB 110-1 or LMF 152 may also process positioning service requests for the UE 105, for example, requests received directly or indirectly from the GMLC 155 or NEF 159. In some embodiments, the node / system implementing the SgNB 110-1 and / or LMF 152 may additionally or alternatively implement other types of positioning support modules, such as an Enhanced Serving Mobile Positioning Center (E-SMLC) or a Secure User Plane Location (SUPL) Positioning Platform (SLP). It will be noted that in some embodiments, at least a portion of the positioning functionality (including deriving the position of the UE 105) may be performed at the UE 105 (e.g., using signal measurements of signals transmitted by wireless nodes and assistance data provided to the UE 105).

[0062] The GMLC 155 may support positioning requests for the UE 105 received from the external client 130, and may forward such positioning requests to the serving AMF 154 for the UE 105. The AMF 154 may then forward the positioning request to the SgNB 110-1, which may obtain one or more positioning estimates for the UE 105 (e.g., based on the request from the external client 130), and may return the positioning estimate(s) to the external client 130 via the UPF 151 and the UPA 153 (if present). The GMLC 155 may contain subscription information for the external client 130, and may authenticate and authorize positioning requests for the UE 105 from the external client 130. The GMLC 155 may also initiate a positioning session for the UE 105 by sending a positioning request for the UE 105 to the AMF 154, and may include in the positioning request an identification of the UE 105 and the type of positioning being requested (e.g., current positioning or a sequence of periodic or triggered positioning).

[0063] For positioning purposes, the SgNB 110-1 and the UE 105 may communicate using the LTE Positioning Protocol (LPP) defined in 3GPP Technical Specification (TS) 36.355 or TS 37.355, wherein LPP messages are sent in radio resource control (RRC) transport messages between the UE 105 and the SgNB 110-1. The LPP protocol may be used to support positioning of the UE 105 using UE-assisted and / or UE-based positioning methods, such as Assisted GNSS (A-GNSS), Real-Time Kinematics (RTK), Wireless Local Area Network (WLAN), Observed Time Difference of Arrival (OTDOA), Multi-RTT, AOD, AOA, Sensor, and / or Enhanced Cell Identity (ECID).

[0064] GNB 110 may communicate with AMF 154 using a Next Generation Application Protocol (NGAP), such as defined in 3GPP TS 38.413. NGAP may enable AMF 154 to request positioning of target UE 105 from SgNB 110-1 for target UE 105, and may enable SgNB 110-1 to return positioning of UE 105 and / or confirm a request for positioning of target UE 105 to AMF 154.

[0065] The GNBs 110 may communicate with each other using an Xn Application Protocol (XnAP), e.g., as defined in 3GPP TS 38.423. The XnAP may allow one gNB 110 to request another gNB 110 to obtain UL positioning measurements for a target UE and return the UL positioning measurements. The XnAP may also enable a gNB 110 to request another gNB 110 to send a downlink (DL) RS or PRS to enable the target UE to obtain DL positioning measurements of the sent DL RS or PRS. In some implementations, the XnAP may be used to transmit positioning-related messages belonging to a higher protocol level (e.g., NR Positioning Protocol A (NRPPa) defined in 3GPP TS 38.455) between gNBs 110 to request UL positioning measurements and / or the transmission of DL RS or PRS signals, in which case the XnAP may be used only as a transmission protocol between pairs of gNBs 110.

[0066] The gNB (e.g., SgNB 110-1) may communicate with the target UE 105 using a radio resource control (RRC) protocol, e.g., as defined in 3GPP TS 38.331. RRC may allow the gNB 110 (e.g., SgNB 110-1) to request positioning measurements of a DL RS or DL ​​PRS transmitted by the gNB 110 and / or other gNBs 110 from the target UE 105 and return the positioning measurements. RRC may also enable the gNB 110 (e.g., SgNB 110-1) to request the target UE 105 to transmit an UL RS or PRS so that the gNB 110 and / or other gNBs 110 can obtain UL positioning measurements of the transmitted UL RS or PRS. The gNB (e.g., SgNB 110-1) may also communicate with the target UE 105 using lower protocol levels (e.g., L1 and L2 protocol levels), which may be used by the UE 105 to return positioning measurements. As previously described, RRC may also be used to transmit LPP messages between UE 105 and SgNB 110-1. For example, LPP messages or RRC messages may be used by SgNB 110-1 to request positioning measurements from target UE 105 and / or request target UE 105 to send UL RS or PRS.

[0067] The information provided to SgNB 110-1 by other gNBs 110 (e.g., using XnAP or NRPPa transmitted by XnAP) may include timing and configuration information for PRS transmission and positioning coordinates of gNB 110. SgNB 110-1 may then provide some or all of this information to UE 105 in an RRC message, an LPP message, or via a broadcast as assistance data. In some implementations, when LPP is used, an RRC message sent from SgNB 110-1 to UE 105 may include an embedded LPP message.

[0068] Depending on the desired functionality, the RRC and / or LPP messages sent from the SgNB 110-1 to the UE 105 may instruct the UE 105 to do any of a variety of things. For example, the LPP and / or RRC messages may contain instructions to the UE 105 to obtain measurements for GNSS (or A-GNSS), WLAN, AOD, Multi-RTT, and / or OTDOA (or some other location method), or to send uplink (UL) signals such as positioning reference signals, sounding reference signals (SRS), or both. In the case of OTDOA, the LPP and / or RRC messages may instruct the UE 105 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a particular cell supported by a particular gNB 110. The UE 105 may send the measurements back to the SgNB 110-1 in the RRC and / or LPP messages or at a lower protocol level (e.g., L1 or L2 protocol level).

[0069] In some embodiments, LPP can be enhanced or replaced by a NR or NG positioning protocol (NPP or NRPP) that supports positioning methods such as OTDOA, AOD, multi-RTT, and ECID for NG radio access. For example, an LPP message can contain an embedded NPP message, or can be replaced by an NPP message.

[0070] The gNB 110 in the NG-RAN 112 may also broadcast positioning assistance data to UEs such as UE 105.

[0071] like Figure 1 As shown, a unified data management (UDM) 156 may be connected to the GMLC 155. The UDM 156 is similar to a home subscriber server (HSS) for LTE access, and the UDM 156 may be combined with the HSS if necessary. The UDM 156 is a central database that contains user-related and subscription-related information of the UE 105 and may perform the following functions: UE authentication, UE identification, access authorization, registration and mobility management, subscription management, and short message service management.

[0072] To support services including location services from external clients 130, a network exposure function (NEF) 159 may be included in the 5GCN 150. The NEF may also be referred to as a service capability exposure function (SCEF), for example, for a UE 105 having LTE access to an enhanced packet core (EPC) rather than 5G NR radio access to the 5GCN 150. The NEF 159 may support secure exposure of capabilities and events about the 5GCN 150 and the UE 105 to external clients 130 (which may then be referred to as application functions (AFs)), and may enable secure provision of information from the external clients 130 to the 5GCN 150. In the context of location services, the NEF 159 may be used to obtain the current or last known location of the UE 105, may obtain an indication of a change in the location of the UE 105, or may obtain an indication of when the UE 105 becomes available (or reachable). The external client 130 may access the NEF 159 directly, or may access a service capability server (SCS, in the Figure 1 15), the service capability server may access the NEF 159 on behalf of the external client 130 to provide the external client 130 with positioning information for the UE 105 via the SCS. The NEF 159 may be connected to the GMLC 155 to support the last known location, current location, and / or deferred periodic and triggered location of the UE 105. If desired, the NEF 159 may include the GMLC 155, or may be combined therewith.

[0073] The user plane function (UPF) 151 may support voice and data bearers for the UE 105 and may enable the UE 105 to have voice and data access to other networks such as the Internet. The UPF 151 functions may include: external PDU session interconnection points to data networks, packet (e.g., Internet Protocol (IP)) routing and forwarding, user plane portion of packet inspection and policy rule enforcement, quality of service (QoS) processing for the user plane, downlink packet buffering, and downlink data notification triggering. Positioning reports for the UE 105 (e.g., including a positioning estimate determined by the SgNB 110-1) may be returned by the SgNB 110-1 to the external client 130 via the UPF 151 and the UPA 153 (if present).

[0074] It should be understood that although Figure 1 The network architecture for non-roaming UEs is shown, but a corresponding network architecture may be provided for roaming UEs with appropriate well-known variations.

[0075] Figure 1How a positioning session is established by the SgNB 110-1 at a high level and how positioning reporting is supported is shown by the thick arrows. To establish (or cancel) a positioning session for a target UE 105, a control plane (CP) signaling path may be used, as indicated by the thick arrow 161. With the control plane path, a control plane procedure may be used, where the external client 130 sends a positioning request to the GMLC 155 or NEF 159, which forwards the positioning request to the serving AMF 154 for the target UE 105. The serving AMF 154 then forwards the positioning request to the serving SgNB 110-1 for the target UE 105, which acts as a positioning server function for the positioning session. Figure 1 Only positioning establishment via GMLC 155 and not via NEF 159 is shown. For positioning reporting, a user plane (UP) signaling path may be used, as indicated by thick arrows 162 and 163. Using the user plane signaling path, SgNB 110-1 sends positioning reports to external client 130 through UPF 151 via a user plane connection between SgNB 110-1 and external client 130 when UPA 153 is not used, or via a user plane connection between SgNB 110-1 and UPA 153 and a second user plane connection between UPA 153 and external client 130 when UPA 153 is used. UPF 151 may support protocol data unit (PDU) sessions to SgNB 110-1 (but not to UE 105 in this case), which may enable IP (and possibly local area network (LAN)) access from SgNB 110-1 to external networks and entities such as external client 130. When the two endpoints are not in the same trust domain, the user plane connection(s) may use encryption and mutual authentication. This would typically occur in a user plane connection between the SgNB 110-1 and the external client 130, between the SgNB 110-1 and the UPA 153 when the UPA 153 is outside the 5GCN 150, or between the UPA 153 and the external client 130 when the UPA 153 is inside the 5GCN 150.

[0076] For positioning reporting via the user plane from the SgNB 110-1, the UE 105 may need to remain in a connection management (CM) connected state and an RRC connected state or an RRC inactive state so that the UE 105 always has the SgNB 110-1. If the target UE 105 is to transition to the CM idle state, the SgNB 110-1 may not be able to access the target UE 105 (e.g., to reconfigure DL positioning measurements or transmission of UL signals by the target UE 105) and may not know which gNBs 110 and LMUs to configure to obtain UL positioning measurements for the UE 105. The target UE 105 may be in the CM connected state if the serving AMF 154 for the target UE 105 remains aware of the positioning session and avoids placing the target UE 105 in the CM idle state.

[0077] Figure 2 A protocol stack 200 for control plane signaling between UE 105 and SgNB 110-1 is shown. Layer 1 (L1) of the protocol stack 200 is the physical layer (PHY), whose endpoints are Figure 2 202 and 212. Layer 2 (L2) is divided into the following sublayers: (i) Medium Access Control (MAC) with endpoints 204 and 214; (iii) Radio Link Control (RLC) with endpoints 206 and 216; and (iii) Packet Data Convergence Protocol (PDCP) with endpoints 208 and 218. The physical layer (PHY) provides data and signaling transmission services to the MAC sublayer via transport channels, signals hybrid automatic repeat request (HARQ) feedback, and signals scheduling requests. The MAC sublayer provides logical channels, data and signaling transmission, and radio resource allocation to the RLC sublayer. The RLC sublayer provides data transmission to the PDCP sublayer in unacknowledged mode (UM), acknowledged mode (AM), and transparent mode (TM). PDCP provides user plane data transmission, control plane data transmission, header compression, encryption, and integrity protection to the RRC layer. As shown in FIG. Figure 2 As shown, the RRC protocol (when used) utilizes the PDCP layer and has endpoints 210 and 220 in the UE 105 and SgNB 110-1, respectively.

[0078] For a UE 105 in an RRC connected state with an SgNB 110-1 (e.g., where a signaling association or connection may exist between the UE 105 and the SgNB 110-1), positioning measurement information obtained by the UE 105 may be transmitted to the SgNB 110-1 at a physical (PHY) layer (L1) by encoding the positioning measurement information into a bit sequence (e.g., which may include additional forward error correction bits), the bit sequence being included in one or more UL subframes transmitted by the UE 105, wherein the transmission of the UL subframes by the UE 105 was previously authorized by the SgNB 110-1. The bit sequence may also include an identity of the UE 105 and / or an identity of a positioning session for the UE 105, and possibly additional bits to enable authentication of the identity(ies) by the SgNB 110-1. The positioning measurement information may also be encrypted by the UE 105 (e.g., using an encryption key previously provided to the UE 105 by the SgNB 110-1).

[0079] Alternatively, for a UE 105 in an RRC connected state with an SgNB 110-1, the positioning measurement information obtained by the UE 105 may be transmitted to the SgNB 110-1 at the RLC layer or the PDCP layer (L2) by being included in an RLC control protocol data unit (PDU) or a PDCP control PDU, respectively. Transmission at the PDCP level may be encrypted and authenticated by the PDCP layer, and additional encryption and authentication of the positioning measurement may not be required. However, transmission at the RLC level may require the UE 105 to include additional information for an identity of the UE 105, an identity of the positioning session, authentication of (multiple) identities, and to encrypt the positioning measurement information, as previously described for transmitting positioning measurement information at the PHY layer. For transmission at the PHY or RLC layer, the SgNB 110-1 may authenticate the information using any authentication information, and decrypt the information if the positioning measurement information is encrypted. Benefits of transmitting positioning measurement information at the PHY, RLC, or PDCP layer may include reduced latency due to the UE 105 and SgNB 110-1 processing fewer protocol layers, and the ability to send the information in any available UL signaling subframe of the UE 105.

[0080] For a UE 105 in an RRC inactive state (e.g., where the UE 105 may have a serving gNB 110-1, but no signaling connection to the SgNB 110-1), the UE 105 may initiate a message exchange with the SgNB 110-1 by sending a request (e.g., a random access channel (RACH) request) for permission to send an RRC message to the SgNB 110-1 or another gNB 110. The request may be sent on a common control channel (e.g., a RACH channel). The SgNB 110-1 or another gNB 110 may return an RRC message indicating permission to send the RRC message and providing UL transmission resources (e.g., such as available UL subframes and available bandwidth) to use to send the RRC message. The UE 105 may then send an RRC message on the common control channel and may include positioning measurement information, which may be encrypted, an identity of the UE 105 (e.g., which may include an identity of the SgNB 110-1), an identity of the positioning session, and additional information that enables authentication of the identity(ies) by the SgNB 110-1. Since the RRC message is the third message transmitted between the UE 105 and the SgNB 110-1 in this message exchange, it may be referred to as "Message 3". In the case of sending the RRC message to another gNB 110, the other gNB 110 may forward the positioning measurement information, the identity of the UE 105, the identity of the positioning session, and the additional authentication information to the SgNB 110-1. The SgNB 110-1 may then use the authentication information to authenticate the positioning measurement information and, if the positioning information is encrypted, decrypt the positioning information.

[0081] Figure 3A protocol hierarchy 300 is shown that may be used when the SgNB 110-1 sends a positioning report for the target UE 105 to the external client 130. The protocol hierarchy between the SgNB 110-1 and the UPF 151 corresponds to the protocol hierarchy defined for the N2 reference point between the NG-RAN 112 and the 5GCN 150 (e.g., as defined in 3GPP TS 38.300 and TS 23.501), except that the SgNB 110-1 also supports the Internet Protocol (IP) layer. When the UPA 153 is not present, the protocol hierarchy between the UPF 151 and the external client 130 corresponds to the protocol hierarchy supported by the UPF 151 for any other external data entity. At upper layers, the SgNB 110-1 and external clients 130 support the Transmission Control Protocol (TCP), (optionally) Transport Layer Security (TLS), and the Hypertext Transfer Protocol (HTTP) (e.g., HTTP / 2) or User Plane Positioning Protocol (ULP) defined by the Open Mobile Alliance for the Secure User Plane Location (SUPL) solution. When the UPA 153 is present, the UPA 153 intercepts the IP, TCP, and (when present) TLS layers and relays HTTP or ULP messages between the SgNB 110-1 and the external clients 130. An advantage of the ULP may be the existing support in the ULP for transmitting the positioning information (e.g., positioning estimate) of the target UE 105, and support for authentication and encryption using TLS. An advantage of HTTP may be the low implementation impact and widespread support of the external clients 130.

[0082] Figure 3 The protocol layering shown allows the SgNB 110-1 to transmit HTTP or ULP messages containing positioning reports of the target UE 105 to the external client 130. TLS can be used to achieve mutual authentication and support encryption. TCP is used to provide reliable delivery. Since the gNB 110 may already support GPRS Tunneling Protocol (GTP-U) for user plane access, User Datagram Protocol with IP (UDP / IP), and Layer 1 and Layer 2 (L1 and L2) towards UPF 151, the new impact is the addition of IP, TCP, (optionally) TLS, and HTTP or ULP. If UPA 153 exists inside 5GCN 150, SgNB 110-1 may not require TLS support.

[0083] In some alternative implementations, Figure 3 The HTTP or ULP in may be replaced by a different protocol, such as Simple Mail Transfer Protocol (SMTP) or Simple Object Access Protocol (SOAP), and if the external client 130 is accessed via a Local Area Network (LAN), the IP may be replaced or augmented by a LAN protocol.

[0084] For each target UE being located, there may be one TCP connection and an optional corresponding TLS session between the SgNB 110-1 and the external client 130 or UPA 153. Alternatively, one TCP connection and an optional corresponding TLS session may be shared among multiple UEs by being used to support positioning reports for some or all target UEs for which positioning reports need to be sent by the SgNB 110-1 to the external client 130 or UPA 153. The positioning report sent at the HTTP or ULP (or other equivalent) protocol level may include an identification or reference (e.g., General Public Subscription Identifier (GPSI), Subscription Permanent Identifier (SUPI)) of the target UE 105, an identification or address of the external client 130 (e.g., when the positioning report is sent via the UPA 153), a positioning session reference or identifier, and the positioning related information being reported.

[0085] Information referred to as “positioning context information” may be required among participating entities (e.g., UE 105 and gNB 110) to support the transmission of UL and DL RS, obtain UL and DL positioning measurements, transmit positioning measurements to SgNB 110-1, and / or deliver positioning reports to external clients 130.

[0086] For positioning reporting to the target UE 105 using SgNB 110-1, Table 1 summarizes the positioning context information that can be stored in each type of entity and the events that can create, update, or delete the information.

[0087] Table 1

[0088]

[0089]

[0090] A positioning session identifier (e.g., as shown in Table 1) may be used to identify a positioning request for a target UE 105 and an associated positioning session used by SgNB 110-1 to support the positioning request. The positioning session identifier may also be used to associate signaling messages and positioning measurements with a positioning session. In the case of UL positioning measurements, the RP may send UL positioning measurements to SgNB 110-2 and may include a positioning session identifier in each message used to transmit the UL positioning measurements to allow SgNB 110-1 to associate each message with a positioning session. In the case of DL positioning measurements, the target UE 105 may send DL positioning measurements to SgNB 110-1 and may include a positioning session identifier in each message used to transmit the DL positioning measurement messages (e.g., as shown in Table 1). Figure 2Described as sent at the PHY, RLC, PDCP or RRC layer).

[0091] Figure 4 The positioning session establishment and reporting procedure for supporting SLLLS applicable to the use of SgNB 110-1 is shown. The procedure details how the external client 130 requests the positioning report via user plane signaling and how the positioning report via user plane signaling is configured in the participating entities. The procedure is applicable to Figure 1 A non-roaming target UE 105 in the communication system 100.

[0092] like Figure 4As shown, the external client 130 may send a positioning request for the target UE 105 to the NEF 159 or GMLC 155 in the 5GCN 150. For a request via the NEF 159, stages 1-4 are performed and stages 5-8 are omitted. For a request via the GMLC 155, stages 1-4 are omitted and stages 5-8 are performed. For a request via NEF 159, the positioning request sent to NEF 159 in stage 1 may include: (i) an identification of the target UE 105 (e.g., GPSI or SUPI); (ii) criteria for sending back a positioning report in stage 18 (e.g., a positioning report triggering event, such as an area event trigger or a UE motion trigger or parameters for periodically sending positioning reports); (iii) quality of service (QoS) parameters, such as required positioning accuracy, positioning report latency, and positioning report reliability; (iv) minimum and / or maximum positioning report intervals; (v) criteria for starting and stopping positioning reports (e.g., start time, stop time, maximum number of reports, maximum report duration); (vi) positioning report content (e.g., supported geographic area description (GAD) shapes and whether UE speed and / or UE position should be reported); (vii) an identification of the external client 130 (e.g., a client name, a fully qualified domain name (FQDN) or an IP address); and / or (viii) a positioning session reference (e.g., a numeric or alphanumeric sequence) that is later used to identify the positioning report in stage 18. The positioning request of phase 1 may also include a request to send a positioning report via the user plane (e.g., in phase 18) and an address (e.g., an IP address, a uniform resource identifier (URI), or a FQDN) to which the positioning report should be sent via the user plane, as well as security information. The security information may include an encryption and / or authentication key (or keys) and an identification of the external client 130, which may be available for establishing a TLS session between the SgNB 110-1 and the external client 130, as described later. When the positioning report of phase 18 uses the UPA 153, the security information may not be present or may be ignored by the NEF 159. As part of phase 1, the NEF 159 may authenticate the external client 130 and verify that the external client 130 is authorized to locate the target UE 105. For example, the NEF 159 may verify the privacy requirements of the target UE 105 (e.g., by requesting the privacy requirements of the target UE 105 stored in the UDM 156), and that the privacy requirements allow the target UE 105 to be located by the external client 130.

[0093] exist Figure 4In stage 2, if the NEF 159 does not know the serving AMF 154 of the target UE 105, the NEF 159 may query the UDM 156 for the address of the serving AMF 154 by calling the Nudm_UEContextManagement_GetService operation. The UDM 156 then returns the serving AMF address.

[0094] In phase 3, the NEF 159 forwards the positioning request received in phase 1 to the serving AMF 154 of the target UE 105 by calling the Namf_EventExposure subscription service operation. The forwarded positioning request may contain some or all of the information included in phase 1. The serving AMF 154 may return a response to the NEF 159 confirming acceptance of the positioning request.

[0095] Note that in a variation of this process, NEF 159 may be provided via UDM 156 ( Figure 4 (not shown) sends a positioning request to the serving AMF 154, in which case phase 2 is not executed.

[0096] In phase 4, NEF 159 may return a first response to external client 130, which first response confirms that the positioning request sent in phase 1 is accepted by the network.

[0097] Note that in this variation of the procedure ( Figure 4 ), NEF 159 may forward the positioning request to GMLC 155 after phase 1, in which case GMLC 155 may perform phases 6 and 7 and return a positioning response to NEF 159. In this variation, phases 2 and 3 are not performed.

[0098] exist Figure 4 In stage 5 of the present invention, for a request via the GMLC, the positioning request may include the same or similar information as described in stage 1 for the positioning request via the NEF 159. As part of stage 5, the GMLC 155 may authenticate the external client 130 and verify that the external client 130 is authorized to locate the target UE 105 (e.g., as described in stage 1 for the NEF 159).

[0099] In stage 6, if the GMLC 155 does not know the serving AMF 154 of the target UE 105, the GMLC 155 may query the UDM 156 for the address of the serving AMF 154 by calling the Nudm_UEContextManagement_GetService operation. The UDM 156 then returns the serving AMF 154 address.

[0100] In phase 7, the GMLC 155 forwards the positioning request received in phase 5 to the serving AMF 154 for the target UE by invoking the Namf_Location_ProvidePositioningInfo service operation. The forwarded positioning request may contain some or all of the information included in phase 5. The serving AMF 154 may return a response to the GMLC 155 confirming acceptance of the positioning request.

[0101] In stage 8, GMLC 155 may return a first response to external client 130, which first response confirms that the positioning request sent in stage 5 is accepted by the network.

[0102] exist Figure 4 In stage 9 (which applies to positioning requests sent via NEF 159 or GMLC 155), the serving AMF 154 waits for the target UE 105 to become reachable (for example, if the target UE 105 is initially unreachable due to the use of discontinuous reception (DRX) or power saving mode (PSM)).

[0103] In stage 10, if the target UE 105 is not in the CM connected state (e.g., does not have SgNB 110-1), the serving AMF 154 performs a network-triggered service request to place the target UE 105 in the CM connected state. Once the UE 105 is in the CM connected state, the serving AMF 154 may verify the privacy of the target UE 105 by sending a message (e.g., a supplementary service message) to the target UE 105 indicating the requested positioning of the target UE 105 and (possibly) identifying the external client 130. The target UE 105 (e.g., after notifying and obtaining a response from the user of the target UE 105) may return a response to the serving AMF 154 indicating whether the positioning request is allowed. If the positioning request is not allowed, the serving AMF 154 may return a response to the external client 130 in stages 14-17 indicating that the positioning request was not accepted by the target UE 105, and the remainder of the process may be omitted.

[0104] In stage 11, the serving AMF 154 (rather than the LMF 152) determines to use the positioning service capabilities in the NG-RAN 112. This determination may be configured in the serving AMF 154 for all target UEs (e.g., if the 5GCN 150 does not include the LMF 152), or may be based on the type of positioning request received in stage 3 or stage 7 (e.g., may be based on a positioning request including a QoS specifying very low latency (such as a latency of less than 1 second), and / or a positioning request specifying positioning reporting via the user plane). The serving AMF 154 then sends a NGAP positioning request message (e.g., a NGAP Positioning Reporting Control (LRC) message) to the SgNB 110-1 for the target UE 105. The NGAP positioning request message may be sent using control plane signaling. The NGAP positioning request message may include "positioning request information" that includes some or all of the information in the positioning request received by the serving AMF 154 in stage 3 or stage 7. In some implementations, the NGAP positioning request message may be or may serve as a transport message and may include a message for a higher protocol level (e.g., a message for operation based on an LMF service) that includes positioning request information. The SgNB 110-1 may store some or all of the positioning request information, which may form part of the positioning context for the target UE 105 in the SgNB 110-1, as described in Table 1.

[0105] In stage 12, SgNB 110-1 configures positioning measurements for the target UE 105 to support the positioning request received in stage 11. Figure 5 The measurement configuration for stage 12 is described in more detail in .

[0106] In phase 13, SgNB 110-1 returns a NGAP positioning response (e.g., an NGAP positioning report message or a higher protocol level transport message carrying a positioning response) to serving AMF 154, which confirms that the positioning request for the target UE 105 has been activated. In some embodiments, phase 13 may occur before phase 12.

[0107] In phase 14, for a request from NEF 159 (e.g., in the case of executing phases 1-4 or in the case where NEF 159 sends a positioning request to serving AMF 154 via UDM 156), serving AMF 154 calls the Namf_EventExposureNotify service operation to send an indication to NEF 159 that the positioning request of phase 1 has been activated.

[0108] At stage 15 , NEF 159 forwards the indication received at stage 14 to external client 130 .

[0109] In phase 16, for a request from GMLC 155 (e.g., in the case of performing phase 7), the serving AMF 154 invokes the Namf_Location_EventNotify service operation to send an indication to GMLC 155 that the positioning request of phase 5 (or phase 1 if NEF 159 forwards the positioning request to GMLC 155) has been activated.

[0110] At stage 17 , GMLC 155 forwards the indication received at stage 16 to external client 130 .

[0111] In stage 18, SgNB 110-1 performs positioning reporting of target UE 105 via the user plane, such as Figure 6 Described in more detail in .

[0112] In phase 19, the target UE 105, SgNB 110-1, GMLC 155, NEF 159 or external client 130 may cancel the positioning request by directly or indirectly sending a positioning cancellation request to other entities participating in the positioning report. Other entities participating in the positioning report may include any one of the target UE 105, SgNB 110-1, GMLC 155, NEF 159 and external client 130 that did not initiate the positioning cancellation and participated in at least one of phases 1-18.

[0113] Figure 5 A process for supporting positioning measurement configuration of SgNB 110-1 to support SLLLS is shown. The process may be used to support Figure 4 Stage 12 of this process applies to Figure 1 A non-roaming target UE 105 is shown.

[0114] exist Figure 5 In phase 1 of the present invention, SgNB 110-1 may obtain the positioning capabilities of target UE 105 by sending an RRC request message to UE 105 and receiving an RRC response message including the positioning capabilities from UE 105. In some embodiments, the RRC request message and the RRC response message may each include an LPP message including a request for capabilities and positioning capabilities, respectively. In one embodiment, the RRC request message may include an embedded LPP request message (e.g., LPP request capabilities), and the RRC response message may include an embedded LPP response message (e.g., LPP offer capabilities), wherein the LPP response message includes the positioning capabilities of UE 105. For example, the positioning capabilities received from UE 105 may indicate the ability to send positioning information at the layer 1 (L1) or layer 2 (L2) protocol level, and the ability to support OTDOA and multi-RTT.

[0115] In stage 2, SgNB 110-1 determines one or more positioning methods for obtaining a positioning estimate and other positioning information for target UE 105. The positioning methods may include, for example, multi-RTT, OTDOA, and use of inertial sensors. The positioning method may be based on the positioning capabilities of UE 105 obtained in stage 1 and / or the QoS requested by the positioning request for target UE 105 (e.g., Figure 4 The UL positioning measurement may be determined based on the QoS received in stage 11 of the SgNB 110-1. For example, the determined (multiple) positioning method(s) may include only the positioning methods indicated as supported by the target UE 105 and that can support or help support the requested QoS. The SgNB 110-1 may also select one or more receiving points (RPs) to obtain UL positioning measurements for the target UE 105 to support the determined (multiple) positioning methods. The RP may include the SgNB 110-1 and one or more NgNBs 110-2, 110-3, 110-4. The SgNB 110-1 may also determine one or more UL positioning measurements to be obtained by each RP and the criteria for obtaining the UL positioning measurements. The UL positioning measurement may be determined based on the determined (multiple) positioning method(s), the positioning QoS and / or the positioning capability of the selected measurement entity (e.g., as configured in the SgNB 110-1). For example, the UL positioning measurement may include one or more of TOA, Rx-Tx, AOA, RSSI, RSRP, RSRQ. Typically, the criterion for obtaining UL positioning measurements will be to obtain measurements at fixed periodic intervals. SgNB 110-1 may also determine one or more DL positioning measurements to be obtained by the target UE 105 and the criteria for obtaining DL positioning measurements. DL positioning measurements may be determined based on the determined (multiple) location methods, positioning QoS, and / or the positioning capabilities of the target UE 105 obtained in stage 1. For example, DL positioning measurements may include one or more of Rx-Tx, AOA, RSSI, RSRP, RSRQ, RSTD. The criterion for obtaining DL positioning measurements may be to obtain measurements at fixed periodic intervals. However, as previously described, DL measurements of RSTD may be obtained by UE 105 at a lower (i.e., shorter) periodic interval than the UL measurements obtained by gNB 110, and at a lower periodic interval than the DL Rx-Tx measurements obtained by UE 105. SgNB 110-1 may also determine the key to be used to encrypt the positioning information provided by UE 105 at the L1 or L2 protocol level.

[0116] In one embodiment, as part of Phase 2, SgNB 110-1 may determine “additional measurements” to be obtained by UE 105, which may be reported by UE 105 along with the DL positioning measurements. As an example, the additional measurements may include or comprise sensor measurements (e.g., measurements of changes in positioning, velocity, changes in speed, and / or acceleration of UE 105). The additional measurements may be useful to enable SgNB 110-1 to determine the positioning of UE 105 as UE 105 moves while obtaining DL positioning measurements. For example, the additional measurements may enable SgNB 110-1 to determine the relative positioning of UE 105 at which UE 105 obtains each DL positioning measurement, which may help avoid errors caused by assuming that the DL positioning measurements all correspond to a single positioning of UE 105. This may enable SgNB 110-1 to locate UE 105 with greater reliability and accuracy.

[0117] In phase 3 (optional), SgNB 110-1 may select one or more transmission points (TPs) including gNB 110 (e.g., other NgNBs 110-2, 110-3, 110-4, and SgNB 110-1) or TPs within gNB 110 to transmit DL reference signals (RS) to be measured later by target UE 105 to support some or all of the DL positioning measurements determined in phase 2. Reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), and other types of RS, and may include omnidirectional RS and / or directional (e.g., beamforming) RS. SgNB 110-1 may then send an XnAP message to each selected TP that is not part of SgNB 110-1 to configure each selected TP's transmission of the DL RS. In some embodiments, the XnAP message sent to each selected TP in phase 3 may include an NRPPa message containing information for configuring the transmission of the DL RS by the selected TP. The transmission time of the configured RS may be timed to coincide with the required or selected positioning report for the target UE 105. For example, if the external client 130 Figure 4If the target UE 105 requests periodic positioning reports for the target UE 105 at intervals of 200 milliseconds (ms) in stage 1 or stage 5 of the UE 105, the SgNB 110-1 can configure each TP to send a DL RS at least once in a short period (e.g., 1 ms) before each 200 ms reporting interval. Since the target UE 105 may need to measure the DL RS from each of multiple TPs (e.g., 10-20 TPs) before each periodic positioning report of the UE 105 to ensure accurate positioning determination for the UE 105, the SgNB 110-1 can use "time separation" of the DL RS by configuring each TP to send DL RS to some or all of the other TPs at different times. This can enable the UE 105 to measure only one DL RS at any particular time and avoid the UE 105 from measuring two or more DL RSs at the same time, which may be difficult or impossible for some UEs.

[0118] In one embodiment, "time separation" of DL RSs can be achieved by assigning a common set of RS transmission (or positioning) opportunities to all RSs, during each RS transmission (or positioning) opportunity, only some TPs (e.g., one or a few TPs) transmit DL RSs, while the remaining TPs silence DL RS transmission (by not transmitting DL signals within the frequency range allocated for DL ​​RS transmission) to reduce interference to the TPs that are transmitting DL RSs. Interference to DL RSs can also be reduced by adopting "frequency separation" or "code separation", in which different DL RSs are transmitted in different non-overlapping frequency ranges, or "code separation", in which different DL RSs are encoded at the bit, chip, symbol or other physical level according to different (e.g., orthogonal) coding sequences. In the case where the selected TP is already transmitting RSs to support positioning of other UEs, SgNB 110-1 can modify the transmission by requesting an increase in RS transmission (e.g., using a higher bandwidth and / or a higher transmission frequency) and / or by requesting an improved time interval, improved code interval and / or improved frequency interval for DL ​​RSs. Configuration of TPs may be supported by sending an XnAP message (possibly including an NRRPa message) from SgNB 110-1 to each selected TP (except SgNB 110-1) indicating the desired DL RS transmission. The configuration information sent to each TP may include RS details (e.g., RF carrier frequency, bandwidth, transmission period, allocated transmission or positioning opportunities, silent opportunities, coding sequence, duration of DL RS transmission) and start and end times. Each TP may return a response (e.g., an XnAP and / or NRPPa response) to SgNB 110-1 that confirms whether the requested DL RS configuration can be performed.

[0119] In stage 4 (optional), if an RP including or being part of other gNBs 110 or LMUs is selected in stage 2, the SgNB 110-1 sends an XnAP request message (e.g., an XnAP Positioning Measurement Request) to each RP, which requests UL positioning measurements of signals to be sent by the target UE 105. Each request may indicate the type of (multiple) signals to be sent later by the target UE 105 (e.g., whether this is a UL PRS, UL SRS, or other type of UL RS), and may include characteristics of the (multiple) signals, such as RF carrier frequency, bandwidth, coding, and transmission timing. Each request may also indicate the type of UL positioning measurement requested, and may indicate the QoS for the measurement (e.g., accuracy, latency to obtain the measurement, reliability). Each request may also indicate a series of measurement occasions, at each of which the UL positioning measurement will be obtained. The measurement occasions may be periodic, in which case the SgNB 110-1 may provide the period as well as the start time and end time. As previously described, the UL positioning measurements requested in stage 4 may include Rx-Tx or TOA measurements to be obtained by the RP at fixed periodic intervals. In some embodiments, the XnAP positioning measurement request message sent to each RP in stage 4 may be an XnAP transmission message that includes an NRPPa message containing some or all of the information for configuring the UL positioning measurements for the RP.

[0120] In phase 5, if phase 4 occurs, each RP that receives the request (as part of phase 4) sends an XnAP response message (e.g., an XnAP Positioning Measurement Response or an XnAP Transport message containing an NRPPa message) to SgNB 110-1, indicating whether the UL positioning measurement requested in phase 4 can be supported. In some variants, the messages of phases 4 and 5 (e.g., XnAP and / or NRPPa messages) may be combined with messages used to support phase 3.

[0121] In stage 6, SgNB 110-1 sends an RRC request message (e.g., RRC Positioning Measurement Request) to target UE 105 to request UL transmission of UL RS (e.g., UL PRS or UL SRS) by target UE 105 to support the UL positioning measurement selected in stage 2, and / or to request DL positioning measurements of DL signals received from SgNB 110-1 and NgNBs 110-2, 110-3, and 110-4 selected in stage 2 (and possibly requesting additional positioning measurements as described for stage 2). The RRC request may include details of the DL signals to be measured by UE 105. The RRC request may request UE 105 to send positioning information (e.g., DL positioning measurements and additional positioning measurements) to SgNB 110-1 at the L1 or L2 protocol level, for example, if UE 105 indicated positioning capability to do so in stage 1. The RRC request may also include, for example, an encryption key determined in stage 2, which will be used by the UE 105 to encrypt the positioning information to be provided to the SgNB 110-1. The RRC request may also include details about the required UL RS (e.g., RF coding, bandwidth, RF carrier frequency, periodicity and timing of transmission, and / or start time and end time of transmission). The request may also indicate the QoS for DL ​​positioning measurements (e.g., accuracy, latency to obtain measurements, reliability) and a series of measurement occasions at each of which the target UE 105 will obtain DL positioning measurements. The measurement occasions may be defined by criteria such as fixed periodic intervals, trigger conditions such as the target UE 105 moving more than a threshold distance, and / or defined by a start time and end time. As previously described, the DL positioning measurements requested in stage 4 may include RSTD measurements to be obtained by the UE 105 at fixed periodic intervals that are lower (i.e., shorter) than the fixed periodic interval at which the RP is requested to obtain UL positioning measurements in stage 4. The DL positioning measurements requested at stage 4 may also include Rx-Tx measurements to be obtained by the UE 105 at fixed periodic intervals that are the same as the fixed periodic intervals at which the RP is requested to obtain UL positioning measurements at stage 4.

[0122] The SgNB 110-1 may send multiple measurement requests to the UE 105 in stage 6, for example, a first request for a first positioning measurement and a second request for a second positioning measurement, wherein the first positioning measurement is to be sent by the UE 105 at a L1 or L2 protocol level at a first cycle interval, and the second positioning measurement is to be sent by the UE 105 at a second cycle interval, wherein the first cycle interval is shorter (i.e., smaller) than the second cycle interval. The request for the second positioning measurement may indicate that the second positioning measurement is to be sent by the UE 105 at a radio resource control (RRC) protocol level or at the L1 or L2 protocol level. The requested first positioning measurement may be, for example, a reference signal time difference (RSTD) measurement, and the requested second positioning measurement may be, for example, a receive time-transmit time (Rx-Tx) measurement. The request for the UE 105 to send an uplink (UL) signal may indicate that the UL signal is to be sent by the UE 105 at a third cycle interval, wherein the first cycle interval is shorter than the third cycle interval. The first request, the second request, and the request to send a UL signal may be sent by SgNB 110-1 and received by UE 105 in corresponding first, second, and third messages of an RRC protocol or LPP transmitted over radio resource control (RRC), or may be sent and received in the same RRC or LPP message.

[0123] In some embodiments, one or more RRC requests sent to the target UE 105 in stage 6 may each be an RRC transmission message that includes an LPP message (e.g., LPP requesting positioning information and / or LPP providing assistance data) that contains some or all of the information for configuring the target UE 105's UL RS transmission and / or DL ​​positioning measurements (e.g., including using the L1 or L2 protocol level for positioning measurement reporting).

[0124] In stage 7, the target UE 105 returns an RRC and / or LPP response to the SgNB 110-1, which confirms whether the requested UL RS transmission and / or DL ​​positioning measurement can be supported by the target UE 105.

[0125] In stage 8, each of the TPs selected and configured in stage 3 transmits the DL RS requested in stage 3 (e.g., at periodic intervals), which can be received and measured by the target UE 105. The transmission of DL RS by each TP can continue for the positioning reporting period of the target UE 105, or until the transmission of DL RS is canceled or reconfigured by the SgNB 110-1 or (in the case where the target UE 105 moves to a new SgNB 110-1) by another SgNB 110-1.

[0126] In stage 9, if SgNB 110-1 configured the target UE 105 to transmit UL RS in stage 6, the target UE 105 begins transmitting the configured UL RS (as requested in stage 6) and may continue for the positioning reporting period of the target UE 105, or until the transmission of UL RS is canceled or reconfigured by SgNB 110-1 or (in the case where the target UE 105 moves to a new SgNB 110-1) by another SgNB 110-1. The UL signal may be a positioning reference signal, a sounding reference signal, or both. The UL signal transmitted by UE 105 may be transmitted at a periodic interval that may be longer than the periodic interval at which UE 105 measures DL signals from gNB 110, for example, using reference signal time difference (RSTD) measurements. The transmitted UL signal enables positioning measurement of UE 105 by RP (e.g., gNB), which includes SgNB 110-1 and NgNB 110-2, 110-3 and 110-4.

[0127] Figure 6 A process for supporting positioning reporting of SgNB 110-1 to support SLLLS is shown. This process may be used to support Figure 4 Stage 18 of this process applies to Figure 1 A non-roaming target UE 105 is shown.

[0128] exist Figure 6 In phase 1, if there is currently no TCP connection and optional TLS session available between SgNB 110-1 and external client 130 or UPA 153 (when UPA 153 is used) for sending positioning reports to target UE 105, SgNB 110-1 establishes a TCP connection and optional TLS session with external client 130 or UPA 153 (if used). This can occur at Figure 4 To report positioning directly to external client 130, SgNB 110-1 may use Figure 4 The address or identification of the external client 130 received in stage 11 is used to establish a TCP connection, and the Figure 4 For positioning reporting via UPA 153, SgNB 110-1 may use the address of UPA 153 and, optionally, the encryption and authentication key(s) to establish a TCP connection and an optional TLS session with UPA 153 ( Figure 6 For example, the address of UPA 153 and any encryption and authentication key(s) may be configured in SgNB 110-1 or in Figure 4The UPA 153 (if used) may already have a TCP connection and an optional TLS session with the external client 130, but if the UPA 153 is not used, a TCP connection and an optional TLS session may be established with the external client 130 as part of Phase 1 after a TCP connection and a TLS session have been established with the SgNB 110-1, or after a first positioning report is received from the SgNB 110-1 in Phase 6.

[0129] In a variation of Phase 1, when SUPL ULP (rather than HTTP) is used to send positioning reports, if there is no current SUPL session, SgNB 110-1 may establish a SUPL session with external client 130 or UPA 153, which may include establishing a TCP connection and an optional TLS session as described above. In this variation, SgNB 110-1 may indicate (e.g., at the ULP level, and optionally in a SUPL START or SUPLTRIGGERED START message sent to external client 130 or UPA 153 as part of Phase 1) that the SUPL session is initiated with the external client 130 or UPA 153. Figure 4 For example, SgNB 110-1 may be associated with a positioning request sent in phase 1 or phase 5 of Figure 6 The SUPL START or SUPL TRIGGERED START message sent to the external client 130 or UPA 153 as part of Phase 1 includes the information provided by the external client 130 in Figure 4 A positioning session reference sent in Phase 1 or Phase 5.

[0130] exist Figure 6 In block 602, the location of UE 105 is determined by SgNB 110-1 and reported to external client 130. Block 602 includes stages 2-7. In stage 2 of block 602, Figure 5 The SgNB 110-1, NgNB 110-2 to 110-4 and other TPs selected and configured in stage 3 send DL RSs that can be received by the target UE 105, such as for Figure 5 The transmission of DL RS by each TP may continue for the positioning reporting period of the target UE 105, or until the transmission of DL RS is canceled or reconfigured by SgNB 110-1 or (in the case where the target UE 105 moves to a new SgNB 110-1) by another SgNB 110-1.

[0131] In phase 3, if the target UE 105 was previously requested by SgNB 110-1 to obtain DL positioning measurements (and possible additional positioning measurements) (e.g. Figure 5In step 6 of step 7), the target UE 105 obtains the requested DL positioning measurement (and additional positioning measurement). For example, the DL positioning measurement can be a reference signal time difference (RSTD) measurement, an RSRP measurement, and / or a receive time-transmit time (Rx-Tx) measurement. The additional positioning measurement can be a measurement obtained from an inertial sensor of the UE 105.

[0132] In stage 4, if stage 3 occurs and if the UE is in the RRC connected state, the target UE 105 sends a Layer 1 or Layer 2 Positioning Measurement Report message to SgNB 110-1 and includes the DL positioning measurements obtained in stage 3 (and additional positioning measurements such as sensor measurements). Figure 2 As discussed, the Layer 1 (L1) or Layer 2 (L2) protocol layer may be one of: (i) a physical (PHY) layer; (ii) a medium access control (MAC) layer that may be supported by the PHY layer; (iii) a radio link control (RLC) layer that may be supported by the PHY and MAC layers; or (iv) a packet data convergence protocol (PDCP) layer that may be supported by the PHY, MAC, and RLC layers. For example, the DL positioning measurement may be a reference signal time difference (RSTD) measurement, an RSRP measurement, and / or a receive time-transmit time (Rx-Tx) measurement. For example, if the DL positioning measurement is sent at the PHY, MAC, or RLC layer, the UE 105 may use, for example, a method sent by the SgNB 110-1 at the time before sending the positioning measurement report to the SgNB 110-1. Figure 5 The DL positioning measurements (and additional positioning measurements) are encrypted using the encryption key provided in stage 6 of .

[0133] In one embodiment, if UE 105 is in RRC inactive state, UE 105 may send an RRC positioning measurement report message to SgNB 110-1 or another gNB 110 in stage 4, such as Figure 2 The RRC Positioning Measurement Report message may be an RRC transport message including an embedded LPP message containing DL positioning measurements obtained by the target UE 105 for the measurement opportunity. In this embodiment, the gNB 110 that receives the RRC Positioning Measurement Report message and is not SgNB 110-1 may forward the RRC message or the embedded LPP message to SgNB 110-1 using XnAP.

[0134] In another embodiment, while UE 105 is in the RRC connected state, it may send the DL positioning measurements (and additional positioning measurements) obtained in stage 3 to SgNB 110-1 in an RRC message in stage 4, where the sending of the RRC message may be supported by the PHY, MAC, RLC, and / or PDCP protocol layers. Although this embodiment may be less efficient than using L1 or L2, it may be less affected by the implementation of UE 105 and SgNB 110-1.

[0135] In stage 5, SgNB 110-1 determines the DL positioning measurement (and additional positioning measurement) received in stage 4 and determines the DL positioning measurement (and additional positioning measurement) received in stage 5. Figure 5 The positioning method(s) selected in stage 2 of the present invention may determine the positioning of the target UE 105. The positioning determination in stage 5 may also be based on timing information of the SgNB 110-1, NgNBs 110-2 to 110-4, and other TPs obtained or determined by the SgNB 110-1, as further described below with respect to block 604. For example, the DL positioning measurements may include RSTD measurements, the timing information may include RTD, and the SgNB 110-1 may use OTDOA to determine the positioning of the UE 105 in stage 5. Alternatively, or in addition, the DL positioning measurements may include RSRP measurements of the directional beamformed RS sent in stage 2, and the SgNB 110-1 may use AOD, at least in part, to determine the positioning of the UE 105 in stage 5. The SgNB 110-1 may also determine other positioning information of the target UE 105, such as speed and / or orientation, based on the DL positioning measurements (and additional positioning measurements).

[0136] In Phase 6, based on Figure 4 Based on the criteria for reporting the positioning of the target UE 105 received in stage 11 of the present invention, the SgNB 110-1 determines whether to report the positioning information obtained in stage 5 to the external client 130. If the SgNB 110-1 determines to report the positioning information, the SgNB 110-1 sends a notification to the external client 130 or the UPA 153 (if used) ( Figure 6 The positioning report may include some or all of the positioning information determined in stage 5, as well as the target UE 105 identifier (e.g., GPSI or SUPI), the positioning session reference, and / or the address or indication of the external client 130. Figure 3The positioning report may be sent as a user plane message based on the protocol layering described in the foregoing. For example, the user plane signaling may be based on at least one of the following: Internet Protocol (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), or some combination of these. When the positioning report is sent to the UPA 153, the UPA 153 may forward the positioning report to the external client 130 using a separate TCP connection and an optional TLS session, such as for Figure 3 If HTTP is used to send the positioning report in phase 6, the positioning report may include an HTTP POST message. If ULP is used to send the positioning report in phase 6, the positioning report may include a ULP message, such as a SUPL POS message, a SUPL POS INIT message, or a SUPL REPORT message.

[0137] In phase 7, the external client 130 may optionally return an acknowledgment to the SgNB 110-1 and via the UPA 153 (if UPA 153 is used). If a TCP-level acknowledgment is deemed sufficient, then an acknowledgment may not be required. In some variants, the phase 7 acknowledgment or a separate message from the external client 130 to the SgNB 110-1 may request some changes to the positioning report, such as a higher or lower positioning reporting period or a higher or lower positioning QoS or cancellation of the positioning report. If the positioning report was sent using HTTP in phase 6, the acknowledgment in phase 7 may include an HTTP status 204 (no content) message or an HTTP status 200 OK message.

[0138] exist Figure 6 In block 604, timing information of SgNB 110-1, NgNBs 110-2 to 110-4, and other TPs is determined by SgNB 110-1 and used to update previous timing information. For example, the timing information may include RTD between gNB 110 pairs. Block 604 includes stages 8-11. In stage 8 of block 604, target UE 105 sends a message transmitted by SgNB 110-1, NgNBs 110-2, 110-3, 110-4, and other RPs ( Figure 6 (not shown) in one or more of the received configured UL RS, such as for Figure 5 as described in Stage 9.

[0139] exist Figure 6 At stage 9, if Figure 5In stage 4 of the present invention, one or more of SgNB 110-1, NgNB 110-2, 110-3, 110-4 and other RPs are selected (and configured) to obtain UL positioning measurements, then SgNB 110-1, NgNB 110-2, 110-3, 110-4 and other RPs obtain UL positioning measurements of the UL RS sent by the target UE 105 in stage 8. For example, the UL positioning measurements may include Rx-Tx and / or TOA measurements.

[0140] In stage 10, if stage 9 occurs, each of NgNB 110-2, 110-3, 110-4 and other RPs that obtained UL positioning measurements in stage 9 sends an XnAP message (e.g., an XnAP positioning measurement report) to SgNB 110-1 and includes the UL positioning measurements obtained in stage 9. In some embodiments, the XnAP positioning measurement report message sent to SgNB 110-1 in stage 10 can be an XnAP transmission message, which includes an NRPPa message including the UL positioning measurements obtained for the measurement opportunity.

[0141] In phase 10A, if phase 3 occurs, the target UE 105 obtains DL positioning measurements of DL signals sent by SgNB 110-1, NgNB 110, and other TPs, and sends these to SgNB 110-1 (e.g., in an RRC message or at layer 1 or layer 2). In contrast to the DL positioning measurements sent in phase 4, the DL positioning measurements sent in phase 10A may be used only to help SgNB 110-1 obtain timing information for gNB 110 and other RPs. The DL positioning measurements obtained and sent in phase 10A may be receive time-transmit time (Rx-Tx) measurements. In some embodiments, phase 10A may include or contain phase 3 and phase 4. In one example herein, a second DL positioning measurement (e.g., Rx-Tx measurement) may need to be sent at 5 second intervals in phase 10A to enable timing information to be obtained by SgNB 110-1, and a first DL positioning measurement (e.g., RSTD measurement) and additional measurements may need to be sent at 200 ms intervals to enable positioning of UE 105 to be obtained by SgNB 110-1. In this example, UE 105 may obtain and send the first DL positioning measurement and additional positioning measurement in a layer 1 or layer 2 positioning measurement report (or RRC message) every 200 ms according to phases 3 and 4, and may obtain and include the second DL positioning measurement in a layer 1 or layer 2 positioning measurement report (or RRC message) every 5 seconds according to phases 3 and 4.

[0142] In stage 11, SgNB 110-1 may determine timing information for each of NgNB 110 and other RPs and SgNB 110-1 based at least in part on DL positioning measurements received from UE in stage 4, DL positioning measurements received in stage 10A, and UL measurements received in stage 10. For example, the DL positioning measurements obtained from UE 105 in stage 4 may be (or may include) reference signal time difference (RSTD) measurements, the DL positioning measurements obtained from UE 105 in stage 10A may be (or may include) Rx-Tx measurements, and the UL positioning measurements obtained from SgNB 110-1, NgNB 110, and other RPs may be (or may include) time of arrival (TOA) measurements or Rx-Tx measurements or both. The timing information determined for each NgNB 110 and RP (or TP) in stage 11 may be a real time difference (RTD) between NgNB 110 pairs and / or RS pairs. The determined or updated timing information may be used to help determine the location of UE 105—eg, in stage 5.

[0143] The determination and reporting of the location of UE 105 as in block 602 may be performed in stages 12, 13 and Figure 6 The other stages not shown in the figure are repeated periodically at the first periodic interval. As shown in block 604, the timing information of SgNB 110-1 and other gNBs 110 may be obtained in stages 14 and Figure 6 Other stages not shown in the figure are periodically determined and / or updated repeatedly at a second periodic interval. Because the timing information of SgNB 110-1 and other gNBs 110 and RPs (e.g., RTD between gNB 110 and / or RP pairs) can be stable and only change by a very small value (e.g., 10 nanoseconds (ms) or less) within a period of several seconds, the second periodic intervals can each last for several seconds (e.g., 1-10 seconds) or longer. In contrast, if UE 105 may be moving and needs to be tracked with low latency (e.g., 50-200ms) and high positioning accuracy (e.g., 30 cm error or less), the first periodic interval can be much shorter than the second periodic interval (e.g., can be 50-200ms).

[0144] In some embodiments, UE 105 may Figure 6 4 in the L1 or L2 (or RRC) protocol level to send a positioning measurement report for a first DL positioning measurement (e.g., RSTD measurement) to SgNB 110-1 at a first periodic interval. UE 105 may also send a positioning measurement report for a first DL positioning measurement (e.g., RSTD measurement) at the same first periodic interval (e.g., Figure 6The first periodic interval may be shorter than the second periodic interval. The positioning measurement report for the second DL positioning measurement may be sent at the L1 or L2 protocol level (e.g., at the L1 or L2 protocol level). Figure 6 4 or Stage 10A), or may be sent by UE 105 to SgNB 110-1 at the radio resource control (RRC) protocol level (as in Stage 4 or Stage 10A).

[0145] In some implementations, SgNB 110-1 may receive DL positioning measurements of DL signals sent by two or more gNBs 110 or other TPs (including SgNB 110-1) from each of a plurality of UEs (e.g., UEs other than UE 105 or UEs other than UE 105). The DL positioning measurements may be received by SgNB 110-1 from each of the plurality of UEs in a manner similar to or consistent with the DL positioning measurements for the DL signals sent by two or more gNBs 110 or other TPs (including SgNB 110-1). Figure 6 The SgNB 110-1 may also receive UL positioning measurements for each of the plurality of UEs from each of one or more gNBs 110 or other RPs (including SgNB 110-1). The UL positioning measurements may be received by SgNB 110-1 from each of the gNB 110 or other RPs in a manner similar to or similar to that for the UEs described in Stage 4 of the present disclosure. Figure 6 As an example, SgNB 110-1 may receive a positioning request (e.g., external client 130 or another external client) for each of the plurality of UEs initiated by an external client (e.g., external client 130 or another external client). Figure 4 ), DL and UL positioning measurements may be initiated for each of the multiple UEs (eg Figure 5 ), and may perform positioning reporting for each of the plurality of UEs (e.g. Figure 6 The DL positioning measurements and UL positioning measurements for each of the multiple UEs may be similar to or the same as those described above for UE 105. In this case, SgNB 110-1 may Figure 6Stage 11 of determining common timing information for SgNB 110-1 and other gNBs 110 based on received UL and DL positioning measurements for each of a plurality of UEs. Because the timing information (e.g., RTD between gNB 110 and / or other TP pairs) may not significantly depend on which UE the UL and DL positioning measurements are provided for, the frequency at which gNB 110 performs UL positioning measurements and the frequency at which each UE sends UL RS signals may be reduced compared to the frequency at which positioning of each UE is obtained, which may reduce network resource usage and resource usage for each of a plurality of UEs. In addition, by obtaining timing information for SgNB 110-1 and other gNBs 110 and / or TPs based on UL and DL positioning measurements for a plurality of UEs rather than just one UE 105, SgNB 110-01 may be able to obtain more accurate timing information (e.g., more accurate RTD) for SgNB 110-1 and other gNBs 110 and / or TPs.

[0146] exist Figure 6 Phase 5 determines the location of UE 105 and Figure 6 The determination of the timing information of the gNB 110 in stage 11 may be based on the following observations. As is well known in the art, OTDOA positioning (as in stage 5) may be based on three quantities: time difference of arrival (TDOA), real time difference (RTD), and geometric time difference (GTD). TDOA may be the time interval observed by the UE 105 between receiving a DL RS from each of two different TPs and may correspond to an RSTD measurement. If a DL RS from TP 1 is received by the UE 105 at time t1 and a corresponding DL RS from TP 2 is received by the UE 105 at time t2, the TDOA value is (t2-t1) (or its negative). RTD may represent the relative synchronization difference in the network between the two TPs. If TP1 transmits a DL RS at time t3 and TP 2 transmits a corresponding DL RS at time t4, the RTD therebetween is (t4-t3). If the TPs transmit at exactly the same time, the TPs are synchronized and the RTD is zero. GTD is the time difference between receiving a DL RS from each of two different TPs due to geometric relationships. If the length of the propagation path between TP 1 and UE 105 is d1, and the length of the propagation path between TP 2 and UE 105 is d2, then the GTD is ((d2-d1) / c), where c is the speed of the radio waves. The relationship between these three quantities is:

[0147] TDOA = RTD + GTD (Equation 1)

[0148] GTD is a quantity that is useful for positioning purposes (e.g., using OTDOA) because it contains information about the position of UE 105. If only the TDOA value is known (e.g., measured RSTD), the positioning of UE 105 cannot generally be calculated with asynchronous networks because the RTD value must also be known. However, if the RTD value is also available (e.g., as in Figure 6 1), then SgNB 110-1 can determine the positioning of UE 105 in stage 5 based on Equation 1, where Equation 1 is applied to each pair of at least three pairs of TPs and typically more TPs (e.g., 10-20 pairs of TPs, where one TP in all pairs can be a common TP).

[0149] In a synchronous network, RTD is typically zero (or close to zero). In an asynchronous network, as in stage 11, RTD can be determined using TDOA (RSTD) and RTT measurements. If the RTT between the UE 105 and each of the two TPs (TP 1 and TP 2) is measured, and the UE 105 also measures the TDOA (e.g., RSTD) between the two TPs, then the RTD can be determined (e.g., in stage 11) as:

[0150] RTD=TDOA–GTD (Equation 2)

[0151] Given:

[0152] RTD=TDOA–(RTT2–RTT1) / 2 (Equation 3)

[0153] Among them, RTT1 is the RTT between UE 105 and TP1, and RTT2 is the RTT between UE 105 and TP2.

[0154] Therefore, SgNB 110-1 can use Equation 3 in stage 11 to determine the timing information in the form of RTD for the TP (e.g., gNB 110) pair.

[0155] Note that, as is well known in the art, RTT may be obtained as the sum of Rx-Tx measurements between UE 105 and gNB 110 or other combined TP / RP as follows:

[0156] RTT = Rx-Tx1 + Rx-Tx2 (Equation 4)

[0157] To utilize Equation 4, UE 105 may send a UL RS to gNB 110 or TP / RP at UE time T1, which is then received by gNB 110 or TP / RP at gNB 110 or TP / RP time T2. gNB 110 or TP / RP may also send a DL RS to UE 105 at gNB 110 or TP / RP time T3, which is then received by UE 105 at UE 105 time T4. UE 105 then determines Rx-Tx1 as (T4-T1), and gNB 110 or TP / RP determines Rx-Tx2 as (T2-T3). Equation 4 may then be applied to obtain the RTT between UE 105 and gNB 110 or the combined TP / RP.

[0158] Due to the movement of the target UE 105 and / or other factors (such as changes in wireless coverage or network load levels), the target UE 105 may change serving cells and may therefore be assigned a new SgNB.

[0159] Figure 7 A process of supporting a change of SgNB for a target UE 105 that is in an RRC connected state or an RRC inactive state is shown. Figure 7 Two cases are also distinguished, the case where there is "sufficient connectivity" is referred to as case A, and the case where there is "insufficient connectivity" is referred to as case B. These are based on a determination performed by the current SgNB 110-1 (hereinafter referred to as the old SgNB 110-1) as to whether the new SgNB 110-1' has sufficient signaling connectivity to the RPs and TPs currently being used for UE 105 positioning reporting after a handover or cell change and with support for the required QoS and using some or all of the same RPs and TPs to enable positioning reporting of the target UE 105 to continue at the new SgNB 110-1'. The result of this determination is either "sufficient connectivity" (hereinafter referred to as "case A"), or "insufficient connectivity" (hereinafter referred to as "case B").

[0160] Depending on the degree of mobility and network connectivity of the target UE, it is possible that some PLMNs may only need to support one of Case A or Case B. For example, for positioning of objects in a factory, warehouse, or a single building, where all gNBs 110 providing wireless coverage are interconnected, only Case A may need to be supported.

[0161] exist Figure 7In stage 1 of the RRC connection state, if the change of SgNB occurs in the RRC connected state of the target UE 105, stages 1-4 are performed and stages 5-10 are omitted. If the change of SgNB occurs in the RRC inactive state of the target UE 105, stages 1-4 are omitted and stages 5-10 are performed. For the RRC connected state of stage 1, the old SgNB 110-1 determines that a handover is required for the target UE 105 and selects a new cell and / or a new SgNB 110-1'.

[0162] In phase 2, the old SgNB 110-1 determines the connectivity of the new cell and / or the new SgNB 110-1' as described above. This is a binary decision, where the result of the determination is either "sufficient connectivity" or "insufficient connectivity".

[0163] In Phase 3, as part of the normal handover procedure (e.g., as described in 3GPP TS 38.300 and TS 23.502), the old SgNB 110-1 sends a handover request message to the new SgNB 110-1'. The handover request message may be sent directly over the Xn interface (and possibly via one or more intermediate gNBs 110), or may be sent via the old serving AMF and the new serving AMF when the AMF 154 changes (as part of the handover). The handover request message may be sent using control plane signaling. The old SgNB 110-1 includes an SgNB positioning context (e.g., as described in Table 1) in the handover request, which may include: (i) information about the positioning request initiated by the external client 130; (ii) an indication of the type of positioning information being received from the UE 105; (iii) an indication of UL positioning measurements of the UE 105 being obtained by the old SgNB 110-1; (iv) an indication of UL positioning measurements of the UE 105 being obtained by other gNBs 110 and / or other RPs and the identities of the other gNBs 110 and / or other RPs; (v) an indication of DL reference signals (RS) being sent by other gNBs 110 and / or other TPs and the identities of the other gNBs 110 and / or other TPs; (vi) an indication of UL signals being sent by the UE 105; (vii) a positioning session identifier; (viii) an indication of whether the UE uses the L1 or L2 protocol level to send positioning information; (ix) the positioning capabilities of the UE; or (x) some combination of these. The old SgNB 110-1 may also include the results of the connectivity determination in Phase 2.

[0164] In Phase 4, the remainder of the handover procedure occurs as described in 3GPP TS 38.300 and TS 23.502.

[0165] In stage 5, for the RRC Inactive state, and as part of normal UE 105 operation not specifically associated with positioning reporting, the target UE 105 determines to transition to the RRC Connected state (e.g., to send and receive data or to send DL positioning measurements, such as Figure 6 Stage 4 in) or initiating a RAN-based Notification Area (RNA) update, for example due to a change in RNA or for periodic RNA updates.

[0166] In stage 6, the target UE 105 sends an RRC recovery request message to the new SgNB 110-1' associated with the new cell for the target UE 105. The RRC recovery request includes an indication of the RNA update when the UE 105 detected in stage 5 that it is located in a new RNA, and also includes the identification of the old SgNB 110-1.

[0167] In stage 7, if the old SgNB 110-1 is reachable from the new SgNB 110-1', the new SgNB 110-1' sends a Retrieve UE Context Request message to the old SgNB 110-1. Stages 5-7 may be performed as defined in 3GPP TS 38.300 and TS 23.502 without any changes to the positioning reports.

[0168] In stage 8, as described in stage 2, the old SgNB 110-1 determines the connectivity of the new SgNB 110-1'.

[0169] In stage 9, the old SgNB 110-1 returns a Retrieve UE Context Response message to the new SgNB 110-1' as described in 3GPP TS 38.300 to provide the new SgNB 110-1' with information of the target UE 105. The old SgNB 110-1 also includes the old SgNB 110-1 positioning context in the Retrieve UE Context Response, similar to that discussed in stage 3. The Retrieve UE Context Response message may be sent using control plane signaling. The old SgNB 110-1 may also include the results of the connectivity determination in stage 8.

[0170] At stage 10, the remainder of the process for transitioning the target UE 105 to the RRC connected state or completing the RNA update occurs as described in 3GPP TS 38.300.

[0171] In stage 11, if case A applies, the new SgNB 110-1' performs measurement reconfiguration for the target UE 105 based on the current configuration of UL and DL positioning measurements and UL and DL RS transmissions indicated in the positioning context received from the old SgNB 110-1. For example, the new SgNB 110-1' may optionally reconfigure some gNBs 110 and RPs to perform UL positioning measurements and / or optionally reconfigure some gNBs 110 and TPs to transmit DL RSs based on the address of the new SgNB 110-1' and / or the new serving cell identity. Since the new SgNB 110-1' address and / or the new serving cell identity may indicate some movement of the target UE 105, some previous gNBs 110 and RPs (e.g., as in Figure 5 2) may no longer be able to obtain accurate UL positioning measurements for UL signals sent by the target UE 105, and / or some previous gNB 110 and TP (e.g., as in Figure 5 2) may no longer be able to effectively send DL RS that can be accurately measured by the target UE. However, there may be other gNBs 110 and RSs that were not selected by the old SgNB 110-1, which can obtain accurate UL positioning measurements of the UL signals sent by the target UE 105. Similarly, there may be other gNBs 110 and TPs that were not selected by the old SgNB 110-1, which can effectively send DL RS that can be accurately measured by the target UE 105. Therefore, the new SgNB 110-1' can determine: (i) the RP set, referred to herein as "RP Set 1", for which the ongoing UL positioning measurement will be canceled; (ii) the RP set, referred to herein as "RP Set 2", for which new UL positioning measurement will be requested; (iii) the TP set, referred to herein as "TP Set 1", for which the ongoing DL RS transmission will be canceled; and / or (iv) the TP set, referred to herein as "TP Set 2", for which new DL RS transmission will be requested. Then, the new SgNB 110-1′ can perform similar operations on the TPs in TP Set 1 and TP Set 2. Figure 5 The RPs in RP Set 1 and RP Set 2 are executed in the same manner as Figure 5 The reconfiguration is performed in stages 4 and 5 of TP and RP Set 1, wherein, in the case of TP Set 1 and RP Set 1, an XnAP message requesting cancellation (rather than a request for a new transmission or a new measurement) is sent by the old SgNB 110-1. After (or possibly before) the new SgNB 110-1' has reconfigured the TPs and RPs in TP and RP Sets 1 and 2, the new SgNB 110-1' may perform a similar Figure 51′ may request the target UE 105 to stop obtaining DL positioning measurements for DL ​​RSs transmitted by TPs in TP set 1 and start obtaining DL positioning measurements for DL ​​RSs transmitted by TPs in TP set 2. After the reconfiguration, the TPs in TP set 1 may stop obtaining DL positioning measurements for DL ​​RSs transmitted by TPs in TP set 2. Figure 5 In the DL RS transmission of stage 8, the TPs in TP set 2 can start as follows Figure 5 8, and if the new SgNB 110-1′ requests a change in the UL RS transmission of the target UE 105, the target UE 105 may modify Figure 5 In addition to adding and / or canceling UL positioning measurements and / or DL ​​RS transmission in some RPs and TPs, the new SgNB 110-1' also sends an XnAP positioning measurement request to each previously selected RP, where the UL positioning measurement is unchanged, thereby notifying the RP to now send an XnAP positioning measurement report to the new SgNB 110-1' instead of to the old SgNB 110-1 (e.g. Figure 6 stage 10).

[0172] In stage 12, if case B applies, based on “insufficient connectivity”, the old SgNB 110-1 performs a similar Figure 5 The old SgNB 110-1 performs stages 3-7 of stages 3-7 of the old SgNB 110-1 to cancel all UL positioning measurements, DL positioning measurements, UL RS transmissions, and DL RS transmissions that were previously configured to support positioning reporting to the target UE 105 in the selected RP, TP, and target UE 105. The old SgNB 110-1 then deletes all positioning context information.

[0173] In stage 13, if case B applies, then based on the indication of "insufficient connectivity" received in stage 3 or stage 9, or based on the new SgNB 110-1' making this determination, the new SgNB 110-1' configures new positioning measurements for the target UE 105 to support the positioning request indicated by the old SgNB 110-1 positioning context received in stage 3 or stage 9. The measurement configuration of stage 13 may be as described for Figure 5 described.

[0174] At stage 14, for case A and case B, the positioning report is as follows Figure 6 The process continues as described, with the difference that the positioning reporting is now performed by the new SgNB 110-1' according to the measurement configuration performed in stage 11 or 13.

[0175] Figure 8A process flow 800 is shown that illustrates a method for locating a user equipment (UE), such as a target UE 105, performed by a positioning server function located at (or attached to) a serving base station, such as SgNB 110-1, for the UE in a radio access network (RAN). For example, the positioning server function may be performed by the serving base station or by an LMC server or LLMF server attached to the serving base station.

[0176] Process flow 800 may begin at block 802, where a request to locate a UE is received, wherein the request to locate the UE is based on a positioning request initiated by an external client (e.g., external client 130) and is received using control plane signaling, such as, for example, Figure 4 Stage 11 or Figure 7 At block 804, the positioning server function receives positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level, such as Figure 6 and Figure 2 In block 806, the positioning server function uses the positioning information to calculate the position of the UE, for example, as Figure 6 At block 808, the positioning server function sends a positioning report including the positioning of the UE to the external client using user plane signaling, for example, Figure 4 Stage 18 Figure 6 Stage 6 and Figure 3 As described.

[0177] In one implementation, the user plane signaling is based on at least one of the following: Internet Protocol (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), or some combination of these, e.g., as described for Figure 3 , Figure 4 Stage 18 and Figure 6 as described in Stage 6 of

[0178] In one implementation, the positioning report is sent to the external client using user plane signaling by sending a message for Hypertext Transfer Protocol (HTTP) or Secure User Plane Location (SUPL) User Plane Location Protocol (ULP), for example, as for Figure 6 The message for HTTP may be an HTTP POST message, and the message for SUPL ULP may be a SUPL POS message, a SUPL POS INIT message, or a SUPL REPORT message.

[0179] In one implementation, the L1 or L2 protocol level includes one of: (i) a physical layer; (ii) a medium access control (MAC) layer; (iii) a radio link control (RLC) layer; or (iv) a packet data convergence protocol (PDCP) layer, or (v) some combination of these, such as in Figure 6 and Figure 2 as described in Stage 4.

[0180] In one implementation, the positioning information received from the UE includes reference signal time difference (RSTD) measurements, sensor measurements, or both RSTD and sensor measurements, such as Figure 6 In one implementation, the positioning information is used to calculate the positioning of the UE using observed time difference of arrival (OTDOA), for example, as Figure 6 as described in Stage 5 of .

[0181] In one implementation, the positioning server function may also receive, from the UE, a first measurement of a downlink (DL) signal sent by one or more first base stations among a plurality of base stations in the RAN, wherein the one or more first base stations include a serving base station, such as Figure 5 Stage 8 and Figure 6 The positioning server function may receive, from each of the plurality of base stations, a second measurement of an uplink (UL) signal sent by the UE, such as, for example, Figure 5 Stage 9 and Figure 6 The UL signal may be a positioning reference signal, a sounding reference signal, or both. The positioning server function may determine timing information of the plurality of base stations based at least in part on the first measurement and the second measurement, for example, as Figure 6 The positioning server function may use the positioning information and the timing information of multiple base stations to calculate the position of the UE, for example, Figure 6 For example, in one implementation, the first measurement may include a receive time-transmit time (Rx-Tx) measurement or a reference signal time difference (RSTD) measurement or both, and the second measurement may include a time of arrival (TOA) measurement or an Rx-Tx measurement or both, wherein the timing information of the plurality of base stations includes a real-time time difference (RTD) between pairs of base stations in the plurality of base stations, for example, as for Figure 6 as described in Stage 11 of .

[0182] In one implementation, the positioning server function may send a request to the UE to send the first measurement (eg, Figure 56 in step 1), and a request to send a second measurement may be sent to each of the plurality of base stations, for example, as Figure 5 as described in Stage 4 of .

[0183] In one implementation, positioning information is received from a UE at a first cycle interval, and a positioning report is sent to an external client, wherein a first measurement is received from the UE at a second cycle interval, wherein a second measurement is received from each of a plurality of base stations at a third cycle interval, wherein the first cycle interval is shorter than the second cycle interval and the third cycle interval, for example, as for Figure 6 described.

[0184] In one implementation, the positioning server function receives, from the plurality of UEs, third measurements of DL signals transmitted by one or more second base stations of the plurality of base stations, wherein the one or more second base stations include a serving base station, such as Figure 6 The positioning server function receives fourth measurements of UL signals sent by each of the plurality of UEs from the plurality of base stations, for example, as for Figure 6 The positioning server function may determine timing information for each of the plurality of base stations based at least in part on the third measurement and the fourth measurement, for example, as for Figure 6 The third measurement may be a receive time-transmit time (Rx-Tx) measurement or a reference signal time difference (RSTD) measurement or both, and the fourth measurement may be a time of arrival (TOA) measurement or an Rx-Tx measurement or both, and the timing information of each of the plurality of base stations may be a real time difference (RTD) between a pair of base stations in the plurality of base stations.

[0185] In one implementation, the positioning server function may receive the positioning capability of the UE from the UE, wherein the positioning capability indicates the ability to send positioning information at the L1 or L2 protocol level, for example, as in Figure 5 The positioning server function may send a request to the UE to send positioning information at the L1 or L2 protocol level, for example, Figure 5 as discussed in Phase 6.

[0186] In one implementation, the positioning information is encrypted, for example, Figure 6 As described in stage 4 of , the positioning server function can determine the encryption key; and send the encryption key to the UE, wherein the positioning information is encrypted by the UE based on the encryption key, for example, as Figure 5 as described in stages 2 and 6.

[0187] In one implementation, the RAN may be a next generation radio access network (e.g., NG-RAN 112) that provides 5G New Radio (NR) wireless access to the UE, and the serving base station is a serving NR Node B (SgNB) for the UE (e.g., serving Node B 110-1). For example, the request to locate the UE may be received from an access and mobility management function (e.g., AMF 154) or a previous SgNB for the UE, for example, as in Figure 4 Stage 11 or Figure 7 For example, in one implementation, the positioning server function may identify a change in the SgNB for the UE, where the change in the SgNB is to a new SgNB, such as Figure 7 As discussed in stage 1 or stage 7 of the present invention, a positioning context for the UE may be sent to the new SgNB, wherein the positioning context enables the new SgNB to continue positioning reporting to the UE, for example, Figure 7 as discussed in stage 3 or stage 9 of . Identifying a change in the SgNB for the UE may be based on determining a handover of the UE to a serving cell of the new SgNB when the UE is in a connected state, or based on receiving a request for a UE context from a new SgNB when the UE is in an inactive state. The positioning context may include one of: (i) information of a positioning request initiated by an external client; (ii) an indication of the type of positioning information being received from the UE; (iii) an indication of UL positioning measurements for the UE being obtained by the SgNB; (iv) an indication of UL positioning measurements for the UE being obtained by other gNBs or RPs and identities of the other gNBs or RPs; (v) an indication of DLRS being sent by other gNBs or TPs and identities of the other gNBs or TPs; (vi) an indication of UL signals being sent by the UE; (vii) a positioning session identifier; (viii) an indication of whether the UE uses an L1 or L2 protocol level to send positioning information; (ix) positioning capabilities of the UE; or (x) some combination of these, for example, as described in Figure 7 discussed in Phases 3 and 9 of this document.

[0188] In one implementation, the positioning server function may receive a type of measurement from a plurality of neighboring NR Node Bs (e.g., NgNB 110) in the RAN, wherein calculating the positioning of the UE or calculating the timing information of the plurality of NgNBs is based in part on the type of measurement, for example, as for Figure 6 The positioning server function may determine whether there is sufficient or insufficient signaling connectivity at the new SgNB to allow the new SgNB to receive measurements of this type from multiple NgNBs, such as Figure 7When it is determined that signaling connectivity is insufficient, the positioning server function may cancel this type of measurement in multiple NgNBs after the SgNB change, for example, as Figure 7 When it is determined that signaling connectivity is sufficient, the positioning server function may refrain from canceling this type of measurement in multiple NgNBs after a SgNB change, for example, as Figure 7 The positioning server function may send an indication of determining sufficient or insufficient signaling connectivity to the new SgNB, wherein when the signaling connectivity is sufficient, the indication enables the new SgNB to configure at least some of the multiple NgNBs to send measurements of the type to the new SgNB, wherein when the signaling connectivity is insufficient, the indication enables the new SgNB to refrain from configuring multiple NgNBs, for example, as in Figure 7 Stages 3 and 9 are discussed.

[0189] Fig. 9 A process flow 900 illustrating a method performed by a UE for locating a user equipment (UE), such as UE 105, is shown.

[0190] Process flow 900 may begin at block 902, where a first request for a first positioning measurement and a second request for a second positioning measurement are received from a serving base station in a radio access network (RAN), such as for example Figure 5 At block 904, the UE sends a first positioning measurement to a serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval, for example, as for Figure 6 In block 906, the UE sends a second positioning measurement to the serving base station at a second cycle interval, wherein the first cycle interval is shorter than the second cycle interval, for example, as for Figure 6 Described in Stage 10A.

[0191] In one implementation, the L1 or L2 protocol layer includes one of the following: (i) a physical layer; (ii) a medium access control (MAC) layer; (iii) a radio link control (RLC) layer; (iv) a packet data convergence protocol (PDCP) layer, or (v) some combination of these, such as for example Figure 6 and Figure 2 as described in Stage 4.

[0192] In one implementation, the first positioning measurement and the second positioning measurement include positioning measurements of downlink (DL) signals received from a plurality of base stations in the RAN, wherein the plurality of base stations include a serving base station, such as Figure 5 Stage 8 and Figure 6In one implementation, the first positioning measurement may be a reference signal time difference (RSTD) measurement, a sensor measurement, or both RSTD and sensor measurements, such as Figure 6 The second positioning measurement may be a receive time-transmit time (Rx-Tx) measurement, for example, Figure 6 For example, the DL signal may be a positioning reference signal, a tracking reference signal, or both.

[0193] In one implementation, the UE may receive a request for the positioning capability of the UE from the serving base station, and may send the positioning capability of the UE to the serving base station, wherein the positioning capability indicates the ability to send the first positioning measurement at the L1 or L2 protocol level, for example, as in Figure 5 as discussed in Phase 1.

[0194] In one implementation, the first request for the first positioning measurement includes an encryption key, such as Figure 5 As described in stages 2 and 6 of the present invention, the UE may encrypt the first positioning measurement using the encryption key before sending (at the L1 or L2 protocol level) the first positioning measurement to the serving base station, for example, Figure 6 as described in Stage 4.

[0195] In one implementation, the RAN is a next generation radio access network (e.g., NG-RAN 112) that provides 5G New Radio (NR) wireless access to the UE, and the serving base station is a serving NR Node B (SgNB) for the UE (e.g., serving Node B 110-1).

[0196] In one implementation, the second positioning measurement is sent to the serving base station at the radio resource control (RRC) protocol level or at the L1 or L2 protocol level, for example, as for Figure 6 as described in Stage 10A.

[0197] In one implementation, the UE may also receive a third request from the serving base station to send an uplink (UL) signal, for example, Figure 5 The UE may send an uplink (UL) signal at a third cycle interval, wherein the first cycle interval is shorter than the third cycle interval, wherein the UL signal enables multiple base stations in the RAN to perform positioning measurements on the UE, wherein the multiple base stations include a serving base station, such as Figure 5 The UL signal may be a positioning reference signal, a sounding reference signal, or both. The first request, the second request, and the third request may be received in respective first, second, and third messages of a radio resource control (RRC) protocol, such as Figure 5The first, second, and third messages may be the same message.

[0198] Fig.10 is a diagram showing an example of a hardware implementation of a positioning server function 1000 located at or connected to a serving base station in a radio access network, such as a serving gNB (SgNB) 110-1, as discussed herein and described in Figure 1-8 The positioning server function 1000 may be performed by an entity (e.g., an LMC server or an LLMF server) at (or connected to) a serving base station, or by a serving base station, and may be part of a wireless network such as a 5G system (5GS), and may be implemented in a network such as Figure 1 1000 is a NG-RAN of the NG-RAN 112 shown. The positioning server function 1000 includes, for example, hardware components, such as an external interface 1002, which can be a wired or wireless interface, capable of connecting to the AMF 154, the UPF 151, base stations within the RAN (such as neighboring NgNBs 110-2, 110-3, 110-4), and wirelessly connected to one or more UEs 105, and connecting to a new positioning server function at a new serving base station during handover. The positioning server function 1000 includes one or more processors 1004 and a memory 1010, which can be coupled together via a bus 1006. The memory 1010 can store data and can contain executable code or software instructions that, when executed by one or more processors 1004, cause the one or more processors 1004 to operate as a special-purpose computer programmed to perform the processes and techniques disclosed herein (e.g., process flow 800).

[0199] like Fig.10 As shown, the memory 1010 includes one or more components or modules that, when implemented by one or more processors 1004, implement the methods described herein. Although the components or modules are shown as software in the memory 1010 that can be executed by one or more processors 1004, it should be understood that the components or modules can be dedicated hardware or firmware in or outside the processor 1004. As shown, the memory 1010 may include a positioning request receiving unit 1012, which enables the one or more processors 1004 to receive a request for positioning the UE from an entity in the wireless network (such as AMF 154 or another SgNB 110-1) via the external interface 1002 during handover, wherein the request for positioning the UE is based on a positioning request initiated by an external client (e.g., external client 130) and is received using control plane signaling.

[0200] The memory 1010 may also include a positioning information obtaining unit 1014, which enables one or more processors 1004 to receive positioning information from the UE via the external interface 1002 at a layer 1 (L1) or layer 2 (L2) protocol layer (e.g., one or more of a physical layer, a MAC layer, an RLC layer, and a packet data convergence protocol (PDCP) layer). The positioning information from the UE may be, for example, an RSTD measurement or an Rx-Tx measurement or both. In addition, positioning information may be obtained from the UE at the RRC protocol layer. The positioning information obtaining unit 1014 may also enable one or more processors 1004 to receive positioning information obtained from multiple UEs via the external interface 1002. The positioning information obtaining unit 1014 may also enable one or more processors 1004 to receive positioning information obtained from other base stations (e.g., NgNB 110-2, 110-3, 110-4) via the external interface 1002, which may be, for example, a UL signal sent by the UE 105 or a TOA measurement or Rx-Tx measurement from other UEs.

[0201] The memory 1010 may also include a positioning determination unit 1016 that enables the one or more processors 1004 to determine a positioning estimate for the UE using the received positioning information. For example, the positioning estimate may be determined using OTDOA based on the received RSTD measurements.

[0202] The memory 1010 may also include a positioning information reporting unit 1018, which enables one or more processors 1004 to send a positioning report including an estimated positioning of the UE to an external client via the external interface 1002 using user plane signaling, and the user plane signaling may be based on at least one of the following: Internet Protocol (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), or some combination of these.

[0203] The memory 1010 may also include a timing information unit 1020 that enables the one or more processors 1004 to determine timing information for multiple base stations using measurements of DL signals sent by base stations received from the UE 105 (e.g., Rx-Tx measurements or RSTD measurements or both), and measurements of UL signals sent by the UE 105 received from the base stations (e.g., TOA measurements or Rx-Tx measurements or both). For example, the timing information may be the RTD between a pair of base stations. The positioning determination unit 1016 may enable the one or more processors 1004 to determine a positioning estimate for the UE using the received positioning information and the timing information of the multiple base stations. The timing information unit 1020 may also enable the one or more processors 1004 to determine timing information for multiple base stations using measurements of DL signals sent by base stations received from multiple UEs (including or in addition to the UE 105) (e.g., Rx-Tx measurements or RSTD measurements or both), and measurements of UL signals sent by multiple UEs received from the base stations (e.g., TOA measurements or Rx-Tx measurements or both).

[0204] The memory 1010 may also include a positioning request unit 1022 that enables the one or more processors 1004 to send a positioning measurement request to the UE. The positioning request unit 1022 may enable the one or more processors 1004 to request different types of positioning information, including RSTD measurements or Rx-Tx measurements of DL signals from a base station, and the UE will send one or more of the different types of positioning information at the L1 or L2 protocol level. The positioning request unit 1022 may also enable the one or more processors 1004 to send a positioning measurement request to a base station (e.g., NgNB 110-2, 110-3, 110-4), for example, to request measurements such as TOA measurements or Rx-Tx measurements of UL signals from UE 105 and / or multiple other UEs.

[0205] The memory 1010 may also include a positioning capability unit 1024, which enables one or more processors 1004 to send a request for positioning capability to the UE via the external interface 1002, and receive a positioning capability response from the UE via the external interface 1002, wherein the positioning capability may indicate the ability of the UE to send positioning information to the positioning server function 1000 at the L1 or L2 protocol level.

[0206] The memory 1010 may also include an encryption unit 1026, which enables the one or more processors 1004 to determine an encryption key, which can be sent to the UE together with, for example, a positioning measurement request, so that the UE can use the encryption key to encrypt the positioning information and send the encryption key to the UE via the external interface 1002.

[0207] The memory 1010 may also include a switching unit 1028 that enables the one or more processors 1004 to, for example, identify a change in a serving cell or serving base station for the UE when the UE is in a connected state, or to receive an indication of a new serving cell or new serving base station for the UE and an indication of connectivity via the external interface 1002 when the UE is in an inactive state. When the positioning server function 1000 receives a certain type of measurement from multiple neighboring base stations for calculating the positioning of the UE, the switching unit 1028 may enable the one or more processors 1004 to determine whether there is sufficient or insufficient signaling connectivity at the new serving base station to allow the new serving base station to receive measurements from multiple base stations for determining a positioning estimate for the UE 105. For example, the switching unit 1028 may enable the one or more processors 1004 to cancel the type of measurement in the multiple base stations when it is determined that the connectivity is insufficient, or to avoid cancellation if there is sufficient connectivity. The memory 1010 may also include a connectivity unit 1030 that enables the one or more processors 1004 to send an indication of determining sufficient or insufficient connectivity to the new serving base station, which enables the new serving base station to configure at least some of the multiple base stations to send measurements of the type to the new serving base station when sufficient connectivity is indicated, and wherein the indication enables the new serving base station to refrain from configuring multiple base stations when insufficient connectivity is indicated. The memory 1010 may also include a positioning context unit 1032 that enables the one or more processors 1004 to send a positioning context for the UE to the new serving base station, wherein the positioning context enables the new serving base station to continue positioning reporting to the UE. For example, the positioning context may be one or more of the following: (i) information of a positioning request initiated by an external client; (ii) an indication of the type of positioning information being received from the UE; (iii) an indication of UL positioning measurements of the UE being obtained by the SgNB; (iv) an indication of UL positioning measurements of the UE being obtained by other gNBs or RPs and the identities of the other gNBs or RPs; (v) an indication of DL RSs being sent by other gNBs or TPs and the identities of the other gNBs or TPs; (vi) an indication of UL signals being sent by the UE; (vii) a positioning session identifier; (viii) an indication that the UE uses the L1 or L2 protocol level to send positioning information; (ix) the positioning capabilities of the UE; or (x) some combination of these.

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

[0209] For implementations involving firmware and / or software, the method can be implemented with a module (e.g., a process, a function, etc.) that performs the separation functions described herein. Any machine-readable medium that tangibly contains instructions can be used to implement the methods described herein. For example, the software code can be stored in a memory (e.g., memory 1010) and executed by one or more processor units (e.g., processor 1004) so ​​that the processor unit operates as a special-purpose computer programmed to perform the techniques and processes disclosed herein. The memory can be implemented within the processor unit or outside the processor unit. 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 number of memories, or the type of medium on which the memory is stored.

[0210] If implemented in firmware and / or software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium. Examples 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. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor memory, or other storage device, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; the disks and optical disks used herein 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.

[0211] In addition to being stored on a computer-readable storage medium, instructions and / or data may be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver having a signal indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 1010) and are configured to cause one or more processors (e.g., processor 1004) to operate as a special-purpose computer programmed to perform the techniques and processes disclosed herein. That is, the communication device includes a transmission medium with a signal indicating the information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first part of the 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 the information for performing the disclosed functions.

[0212] Thus, a positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and configured to locate the UE may include a component for receiving a request to locate the UE, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling, which component may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in a memory 1010, such as a positioning request receiving unit 1010. The component for receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in a memory 1010, such as a positioning information obtaining unit 1014. The component for calculating the positioning of the UE using the positioning information may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in a memory 1010, such as a positioning determining unit 1016. The means for sending the positioning report including the UE positioning to the external client using user plane signaling may be, for example, the external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010 , such as the positioning information reporting unit 1018 .

[0213] In one implementation, the positioning server function may include means for receiving from the UE a first measurement of a downlink (DL) signal transmitted by one or more first base stations of a plurality of base stations in the RAN, wherein the one or more first base stations include a serving base station, which means may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning information obtaining unit 1014. Means for receiving from each of the plurality of base stations a second measurement of an uplink (UL) signal transmitted by the UE may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning information obtaining unit 1014. Means for determining timing information of the plurality of base stations based at least in part on the first measurement and the second measurement may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a timing information obtaining unit 1020. The means for calculating the position of the UE using the positioning information and the timing information of the plurality of base stations may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the positioning determination unit 1016. In one implementation, the positioning server function may also include means for sending a request to send a first measurement to the UE, which may be, for example, the external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the positioning request unit 1022. The means for sending a request to send a second measurement to each of the plurality of base stations may be, for example, the external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the positioning request unit 1022. In one implementation, the positioning server function may also include a component for receiving, from the plurality of UEs, a third measurement of a DL signal transmitted by one or more second base stations in the plurality of base stations, wherein the one or more second base stations include a serving base station, which component may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a positioning information obtaining unit 1014. The component for receiving, from the plurality of base stations, a fourth measurement of a UL signal transmitted by each of the plurality of UEs may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a positioning information obtaining unit 1014.The means for determining timing information for each of the plurality of base stations based at least in part on the third and fourth measurements may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in memory 1010 , such as timing information unit 1020 .

[0214] In one implementation, the positioning server function may include a means for receiving a positioning capability of the UE from the UE, wherein the positioning capability indicates the ability to send positioning information at the L1 or L2 protocol level, which means may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a positioning capability unit 1024. The means for sending a request to send positioning information at the L1 or L2 protocol level to the UE may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a positioning request unit 1022.

[0215] In one implementation, the positioning information is encrypted, and the positioning server function may include a component for determining an encryption key, which may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the encryption unit 1026. The component for sending the encryption key to the UE (where the positioning information is encrypted by the UE based on the encryption key) may be, for example, the external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the encryption unit 1026.

[0216] In one implementation, the positioning server function may include a component for identifying a change of an SgNB for a UE, wherein the change of the SgNB is to a new SgNB, which may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in a memory 1010, such as a switching unit 1028. A component for sending a positioning context for the UE to a new SgNB, wherein the positioning context enables the new SgNB to continue positioning reporting for the UE, which may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in a memory 1010, such as a positioning context unit 1032. For example, in some implementations, the positioning server function may also include a component for receiving a type of measurement from multiple neighboring NR Node Bs (NgNBs) in the RAN, wherein calculating the positioning of the UE or calculating the timing information of the multiple NgNBs is based in part on the type of measurement, which component may be, for example, an external interface 1002 and one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a positioning information obtaining unit 1014. The component for determining whether there is sufficient or insufficient signaling connectivity at the new SgNB to allow the new SgNB to receive the type of measurement from the multiple NgNBs may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a switching unit 1028. The component for canceling the type of measurement in the multiple NgNBs after the SgNB change when insufficient connectivity is determined may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a switching unit 1028. The means for refraining from canceling the type of measurements in the plurality of NgNBs after the SgNB change when it is determined that the signaling connectivity is sufficient may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the switching unit 1028. The means for sending an indication of determining sufficient or insufficient signaling connectivity to the new SgNB may be, for example, one or more processors 1004 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as the connecting unit 1030, wherein when the signaling connectivity is indicated to be sufficient, the indication enables the new SgNB to configure at least some of the plurality of NgNBs to send the type of measurements to the new SgNB, wherein when the signaling connectivity is indicated to be insufficient, the indication enables the new SgNB to refrain from configuring the plurality of gNBs.

[0217] Fig.11 1 is a diagram showing a UE 1100 (such as Figure 1105) is shown in FIG. 100. The UE 1100 may include a wireless transceiver 1102 for wirelessly communicating with a base station in a radio access network (such as a serving gNB (SgNB) 110-1 or a positioning server function located at the SgNB 110-1), as discussed herein and as shown in FIG. Figure 1 , 2 , 4-7 and 9. UE 1100 may also include additional transceivers, such as a wireless local area network (WLAN) transceiver 1106, and a transceiver for receiving and measuring signals from SPS SV 190 (such as Figure 1 1100). The UE 1100 may also include one or more sensors 1110, such as a camera, an accelerometer, a gyroscope, an electronic compass, a magnetometer, a barometer, etc. The UE 1100 may also include a user interface 1112, which may include, for example, a display, a keyboard or other input device, such as a virtual keyboard on a display, through which a user can interface with the UE 1100. The UE 1100 also includes one or more processors 1104 and a memory 1120, which may be coupled together via a bus 1116. The one or more processors 1104 and other components of the UE 1100 may be similarly coupled together via a bus 1116 (a separate bus), or may be directly connected together or coupled using a combination of the foregoing. The memory 1120 may store data and may contain executable code or software instructions that, when executed by one or more processors 1104, cause the one or more processors to operate as a special-purpose computer programmed to perform the algorithms disclosed herein.

[0218] like Fig.11As shown, the memory 1120 may include one or more components or modules that can be implemented by one or more processors 1104 to perform the methods described herein. Although the components or modules are shown as software executable by one or more processors 1104 in the memory 1120, it should be understood that the components or modules can be dedicated hardware or firmware in or outside the one or more processors 1104. As shown, the memory 1120 may include a positioning measurement request unit 1122 that configures the one or more processors 1104 to receive a positioning measurement request from a serving base station (such as SgNB 110-1) via the wireless transceiver 1102. For example, the positioning measurement request unit 1122 can configure the one or more processors 1104 to receive a first request for a first positioning measurement and a second request for a second positioning measurement, which can be positioning measurements of DL signals (e.g., one or both of positioning reference signals and tracking reference signals) received from multiple base stations (e.g., SgNB 110-1 and NgNBs 110-2, 110-3, 110-4). For example, the first request may be for RSTD measurements and the second request may be for Rx-Tx measurements.The first request and the second request may be received in one or more messages using the RRC protocol.

[0219] The positioning measurement unit 1124 configures the one or more processors 1104 to perform the requested positioning measurements, which may be, for example, RSTD and / or Rx-Tx measurements. If desired, other types of measurements may be performed, such as time of arrival (TOA), round trip signal propagation time (RTT), angle of arrival (AOA), angle of departure (AOD), received signal strength indication (RSSI), reference signal received power (RSRP), reference signal received quality (RSRQ), global navigation satellite system (GNSS) code phase, GNSS carrier phase, WiFi AP RTT, WiFi AP RSSI, sensor measurements, or some combination of these.

[0220] The positioning measurement sending unit 1126 configures the one or more processors 1104 to send a first positioning measurement to the serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval, for example, via the wireless transceiver 1102, and send a second positioning measurement to the serving base station at a second periodic interval, wherein the first periodic interval is shorter than the second periodic interval. The L1 or L2 protocol level can be, for example, one or more of a physical layer, a MAC layer, an RLC layer, and a packet data convergence protocol (PDCP) layer. The second positioning measurement can be sent, for example, at the L1 or L2 protocol level or at the RRC protocol level.

[0221] The memory 1120 may also include a positioning capability unit 1128, which enables one or more processors 1104 to receive a request for positioning capability from a serving base station via the wireless transceiver 1102, and send a positioning capability response to the serving base station via the wireless transceiver 1102, wherein the positioning capability may indicate the ability of the UE to send positioning information to the positioning server function 1000 at the L1 or L2 protocol level.

[0222] The memory 1120 may also include an encryption unit 1130 that enables the one or more processors 1104 to receive an encryption key that may be in a first request for a first positioning measurement from a serving base station via the wireless transceiver 1102, and to encrypt the first positioning measurement using the encryption key before sending the first positioning measurement to the serving base station (at the L1 or L2 protocol level).

[0223] The memory 1120 may also include a UL transmission request unit 1132 that enables the one or more processors 1104 to receive a request to transmit a UL signal from the serving base station via the wireless transceiver 1102. The request to transmit the UL signal may be received in a message using the RRC protocol. The request to transmit the UL signal may be received in the same message as the first request and the second request for positioning measurements. The UL transmission unit 1134 enables the one or more processors 1104 to transmit a UL signal (e.g., a positioning reference signal, a sounding reference signal, or both) via the wireless transceiver 1102 at a third cycle interval, wherein the first cycle interval is shorter than the third cycle interval, and wherein the UL signal enables multiple base stations including the serving base station to perform positioning measurements for the UE.

[0224] The methods described herein may be implemented by various means depending on the application. For example, these methods may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the one or more processors 1104 may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0225] For implementations of UE 1100 involving firmware and / or software, the method may be implemented using modules (e.g., procedures, functions, etc.) that perform the separated functions described herein. Any machine-readable medium that tangibly contains instructions may be used to implement the methods described herein. For example, software codes may be stored in a memory (e.g., memory 1120) and executed by one or more processors 1104, prompting the one or more processors 1104 to operate as a special-purpose computer programmed to perform the technology disclosed herein. Memory may be implemented within one or more processors 1104 or outside one or more processors 1104. The term "memory" used herein refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any specific type of memory or the number of memories, or the type of medium on which the memory is stored.

[0226] If implemented in firmware and / or software, the functions performed by UE 1100 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as memory 1120). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. Storage media can be any available media that a computer can access. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor memory, or other storage device, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; magnetic disks and optical disks used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where magnetic disks typically reproduce data magnetically, while optical disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0227] In addition to being stored on a computer-readable storage medium, instructions and / or data for UE 1100 may be provided as signals on a transmission medium included in the communication device. For example, a communication device including part or all of UE 1100 may include a transceiver with a signal indicating instructions and data. Instructions and data are stored on a non-transitory computer-readable medium (e.g., memory 1120) and are configured to cause one or more processors 1104 to operate as a special-purpose computer programmed to perform the technology disclosed herein. That is, the communication device includes a transmission medium with a signal indicating the execution of the disclosed function. At a first time, the transmission medium included in the communication device may include a first part of the information for executing the disclosed function, and at a second time, the transmission medium included in the communication device may include a second part of the information for executing the disclosed function.

[0228] Thus, a UE capable of supporting positioning UE may include a component for receiving a first request for a first positioning measurement and a second request for a second positioning measurement from a serving base station in a radio access network (RAN), which component may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning measurement request unit 1122. The component for sending the first positioning measurement to the serving base station at a layer 1 (L1) or layer 2 (L2) protocol level at a first periodic interval may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning measurement sending unit 1126. The component for sending the second positioning measurement to the serving base station at a second periodic interval (where the first periodic interval is shorter than the second periodic interval) may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning measurement sending unit 1126.

[0229] In one implementation, the UE may include means for receiving a request for positioning capabilities of the UE from a serving base station, which means may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning capabilities unit 1128. Means for sending the positioning capabilities of the UE to the serving base station, wherein the positioning capabilities indicate the ability to send a first positioning measurement at an L1 or L2 protocol level, may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in memory 1010, such as a positioning capabilities unit 1128.

[0230] In one implementation, the UE may include a component for receiving a third request to send an uplink (UL) signal from a serving base station, which may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a UL send request unit 1132. The component for sending an uplink (UL) signal at a third cycle interval (wherein the first cycle interval is shorter than the third cycle interval, where the UL signal enables multiple base stations in the RAN to perform positioning measurements on the UE, where the multiple base stations include the serving base station) may be, for example, a wireless transceiver 1102 and one or more processors 1104 having dedicated hardware or implementing executable code or software instructions in the memory 1010, such as a UL send unit 1134.

[0231] One implementation can be described as follows:

[0232] 1. A method for locating a user equipment (UE), the method being performed by a positioning server function located at a serving base station for the UE in a radio access network (RAN), the method comprising:

[0233] receiving a request for locating the UE, wherein the request for locating the UE is based on a positioning request initiated by an external client and is received using control plane signaling;

[0234] receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level;

[0235] Using the positioning information to calculate the positioning of the UE; and

[0236] A positioning report including the positioning of the UE is sent to the external client using user plane signaling.

[0237] 2. The method of claim 1, wherein the user plane signaling is based on at least one of: Internet Protocol (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), or some combination of these.

[0238] 3. The method of claim 1, wherein the positioning report is sent to the external client using user plane signaling by sending a message for Hypertext Transfer Protocol (HTTP) or Secure User Plane Location (SUPL) User Plane Positioning Protocol (ULP).

[0239] 4 . The method of claim 3 , wherein the message for the HTTP comprises an HTTP POST message, and the message for the SUPL ULP comprises a SUPL POS message, a SUPL POS INIT message, or a SUPL REPORT message.

[0240] 5. The method of claim 1, wherein the L1 or L2 protocol level comprises one of the following:

[0241] (i) Physical layer;

[0242] (ii) Medium Access Control (MAC) layer;

[0243] (iii) Radio Link Control (RLC) layer; or

[0244] (iv) Packet Data Convergence Protocol (PDCP) layer; or

[0245] (v) some combination of these.

[0246] 6. The method of claim 1, wherein the positioning information received from the UE comprises reference signal time difference (RSTD) measurements, sensor measurements, or both RTSD and sensor measurements.

[0247] 7. The method of claim 4, wherein calculating the positioning of the UE using the positioning information uses Observed Time Difference of Arrival (OTDOA).

[0248] 8. The method according to claim 1, further comprising:

[0249] receiving, from the UE, a first measurement of a downlink (DL) signal sent by one or more first base stations among a plurality of base stations in the RAN, wherein the one or more first base stations include the serving base station;

[0250] receiving, from each of the plurality of base stations, a second measurement of an uplink (UL) signal transmitted by the UE;

[0251] determining timing information for the plurality of base stations based at least in part on the first measurement and the second measurement; and

[0252] The positioning information and the timing information of the plurality of base stations are used to calculate the positioning of the UE.

[0253] 9. The method of claim 6, wherein the first measurement comprises a receive time-transmit time (Rx-Tx) measurement or a reference signal time difference (RSTD) measurement or both, wherein the second measurement comprises an arrival time (TOA) measurement or an Rx-Tx measurement or both, wherein the timing information of the plurality of base stations comprises a real time difference (RTD) between pairs of base stations in the plurality of base stations.

[0254] 10. The method of claim 6, wherein the DL signal comprises a positioning reference signal, a tracking reference signal, or both.

[0255] 11. The method of claim 6, wherein the UL signal comprises a positioning reference signal, a sounding reference signal, or both.

[0256] 12. The method according to claim 6, further comprising:

[0257] sending a request to the UE to send the first measurement; and

[0258] A request to send the second measurement is sent to each of the plurality of base stations.

[0259] 13. The method of claim 6, wherein the positioning information is received from the UE at a first periodic interval and the positioning report is sent to the external client, wherein the first measurement is received from the UE at a second periodic interval, wherein the second measurement is received from each of the multiple base stations at a third periodic interval, wherein the first periodic interval is shorter than the second periodic interval and the third periodic interval.

[0260] 14. The method according to claim 6, further comprising:

[0261] receiving, from a plurality of UEs, third measurements of DL signals transmitted by one or more second base stations of the plurality of base stations, wherein the one or more second base stations include the serving base station;

[0262] receiving, from the plurality of base stations, a fourth measurement of a UL signal transmitted by each of the plurality of UEs; and

[0263] Timing information for each of the plurality of base stations is determined based at least in part on the third measurement and the fourth measurement.

[0264] 15. The method of claim 12, wherein the third measurement comprises a receive time-transmit time (Rx-Tx) measurement or a reference signal time difference (RSTD) measurement or both, wherein the fourth measurement comprises a time of arrival (TOA) measurement or an Rx-Tx measurement or both, wherein the timing information of each of the plurality of base stations comprises a real time difference (RTD) between pairs of base stations in the plurality of base stations.

[0265] 16. The method according to claim 1, further comprising:

[0266] receiving, from the UE, a positioning capability of the UE, wherein the positioning capability indicates a capability of sending the positioning information at an L1 or L2 protocol level; and

[0267] A request is sent to the UE to send the positioning information at the L1 or L2 protocol level.

[0268] 17. The method according to claim 1, wherein the positioning information is encrypted, and the method further comprises:

[0269] Determining encryption keys; and

[0270] The encryption key is sent to the UE, wherein the positioning information is encrypted by the UE based on the encryption key.

[0271] 18. The method of claim 1, wherein said positioning server function is located at said serving base station.

[0272] 19. The method of claim 1, wherein the RAN is a Next Generation Radio Access Network (NG-RAN) that provides 5G New Radio (NR) wireless access to the UE, and the serving base station is a serving NR Node B (SgNB) for the UE.

[0273] 20. The method of claim 17, wherein the request to locate the UE is received from an access and mobility management function (AMF) or a previous SgNB for the UE.

[0274] 21. The method of claim 17, further comprising:

[0275] identifying a change of an SgNB for the UE, wherein the change of the SgNB is to a new SgNB; and

[0276] Send a positioning context for the UE to the new SgNB, wherein the positioning context enables the new SgNB to continue positioning reporting for the UE.

[0277] 22. The method of claim 19, wherein identifying the change of the SgNB for the UE is based on determining a handover of the UE to a serving cell of the new SgNB when the UE is in a connected state, or based on receiving a request for the UE context from the new SgNB when the UE is in an inactive state.

[0278] 23. The method of claim 19, wherein the positioning context comprises one of:

[0279] (i) information of the positioning request initiated by the external client;

[0280] (ii) an indication of the type of positioning information being received from the UE;

[0281] (iii) an indication of uplink (UL) positioning measurements being obtained by the SgNB for the UE;

[0282] (iv) an indication of UL positioning measurements being obtained for the UE by other NR Node Bs (gNBs) or Reception Points (RPs) and the identities of the other gNBs or RPs;

[0283] (v) an indication of DL Reference Signals (RS) being transmitted by other gNBs or Transmission Points (TPs) and the identities of the other gNBs or TPs;

[0284] (vi) an indication of a UL signal being sent by the UE;

[0285] (vii) locate the session identifier;

[0286] (viii) an indication to the UE to use the L1 or L2 protocol level for sending the positioning information;

[0287] (ix) the positioning capability of the UE; or

[0288] (x) Some combination of these.

[0289] 24. The method of claim 19, further comprising:

[0290] receiving a type of measurement from a plurality of neighboring NR Node Bs (NgNBs) in the RAN, wherein calculating positioning of the UE or calculating timing information for the plurality of NgNBs is based in part on the type of measurement;

[0291] determining whether there is sufficient or insufficient signaling connectivity at the new SgNB to allow the new SgNB to receive the type of measurements from the plurality of NgNBs;

[0292] When it is determined that the signaling connectivity is insufficient, canceling the type of measurement in the plurality of NgNBs after the SgNB is changed;

[0293] When it is determined that signaling connectivity is sufficient, refraining from canceling the type of measurements in the plurality of NgNBs after the SgNB change; and

[0294] sending an indication of a determination of sufficient or insufficient signaling connectivity to the new SgNB, wherein when the indication is sufficient signaling connectivity, the indication enables the new SgNB to configure at least some of the multiple NgNBs to send the type of measurement to the new SgNB, wherein when the indication is insufficient signaling connectivity, the indication enables the new SgNB to refrain from configuring the multiple NgNBs.

[0295] 25. A positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and capable of locating the UE, the positioning server function comprising:

[0296] an external interface configured to communicate with one or more base stations, one or more network nodes, and one or more UEs in the RAN;

[0297] at least one memory;

[0298] at least one processor coupled to the external interface and to the at least one memory, wherein the at least one processor is configured to:

[0299] receiving, via the external interface, a request to locate the UE, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling;

[0300] receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level via the external interface;

[0301] Using the positioning information to calculate the positioning of the UE; and

[0302] A positioning report including the location of the UE is sent to the external client using user plane signaling via the external interface.

[0303] 26. The positioning server function of claim 23, wherein the user plane signaling is based on at least one of: Internet Protocol (IP), Transmission Control Protocol (TCP), Transport Layer Security (TLS), or some combination of these.

[0304] 27. The positioning server function of claim 23, wherein the positioning report is sent to the external client using user plane signaling by sending a message for Hypertext Transfer Protocol (HTTP) or Secure User Plane Location (SUPL) User Plane Location Protocol (ULP).

[0305] 28. The positioning server function of claim 27, wherein the message for the HTTP comprises an HTTP POST message, and the message for the SUPL ULP comprises a SUPL POS message, a SUPL POS INIT message, or a SUPLREPORT message.

[0306] 29. The positioning server function of claim 23, wherein the L1 or L2 protocol level comprises one of the following:

[0307] (i) Physical layer;

[0308] (ii) Medium Access Control (MAC) layer;

[0309] (iii) Radio Link Control (RLC) layer; or

[0310] (iv) Packet Data Convergence Protocol (PDCP) layer; or

[0311] (v) some combination of these.

[0312] 30. The positioning server function of claim 23, wherein the positioning information received from the UE comprises reference signal time difference (RSTD) measurements, sensor measurements, or both RTSD and sensor measurements.

[0313] 31. The positioning server function of claim 26, wherein the at least one processor is configured to use Observed Time Difference of Arrival (OTDOA) to calculate a position of the UE using the positioning information.

[0314] 32. The positioning server function of claim 23, wherein the at least one processor is further configured to:

[0315] receiving, from the UE via the external interface, a first measurement of downlink (DL) signals sent by one or more first base stations among a plurality of base stations in the RAN, wherein the one or more first base stations include the serving base station;

[0316] receiving, via the external interface, from each of the plurality of base stations, a second measurement of an uplink (UL) signal sent by the UE;

[0317] determining timing information for the plurality of base stations based at least in part on the first measurement and the second measurement; and

[0318] The positioning information and the timing information of the plurality of base stations are used to calculate the positioning of the UE.

[0319] 33. The positioning server function of claim 28, wherein the first measurement comprises a receive time-transmit time (Rx-Tx) measurement or a reference signal time difference (RSTD) measurement or both, wherein the second measurement comprises a time of arrival (TOA) measurement or an Rx-Tx measurement or both, and wherein the timing information of the plurality of base stations comprises a real time difference (RTD) between pairs of base stations in the plurality of base stations.

[0320] 34. The positioning server function of claim 28, wherein the DL signal comprises a positioning reference signal, a tracking reference signal, or both.

[0321] 35. The positioning server function of claim 28, wherein the UL signal comprises a positioning reference signal, a sounding reference signal, or both.

[0322] 36. The positioning server function of claim 28, wherein the at least one processor is further configured to:

[0323] sending, via the external interface, to the UE a request to send the first measurement; and

[0324] A request to send the second measurement is sent to each of the plurality of base stations via the external interface.

[0325] 37. The positioning server function of claim 28, wherein the positioning information is received from the UE at a first periodic interval and the positioning report is sent to the external client, wherein the first measurement is received from the UE at a second periodic interval, wherein the second measurement is received from each of the multiple base stations at a third periodic interval, wherein the first periodic interval is shorter than the second periodic interval and the third periodic interval.

[0326] 38. The positioning server function of claim 28, wherein the at least one processor is further configured to:

[0327] receiving, via the external interface, from a plurality of UEs, third measurements of DL signals transmitted by one or more second base stations of the plurality of base stations, wherein the one or more second base stations include the serving base station;

[0328] receiving, from the plurality of base stations via the external interface, a fourth measurement of a UL signal transmitted by each of the plurality of UEs; and

[0329] Timing information for each of the plurality of base stations is determined based at least in part on the third measurement and the fourth measurement.

[0330] 39. The positioning server function of claim 34, wherein the third measurement comprises a receive time-transmit time (Rx-Tx) measurement or a reference signal time difference (RSTD) measurement or both, wherein the fourth measurement comprises a time of arrival (TOA) measurement or an Rx-Tx measurement or both, and wherein the timing information of each of the plurality of base stations comprises a real time difference (RTD) between pairs of base stations in the plurality of base stations.

[0331] 40. The positioning server function of claim 23, wherein the at least one processor is further configured to:

[0332] receiving, from the UE via the external interface, positioning capabilities of the UE, wherein the positioning capabilities indicate a capability of sending the positioning information at an L1 or L2 protocol level; and

[0333] A request to send the positioning information at the L1 or L2 protocol level is sent to the UE via the external interface.

[0334] 41. The positioning server function of claim 23, wherein the positioning information is encrypted and the at least one processor is further configured to:

[0335] Determining encryption keys; and

[0336] The encryption key is sent to the UE via an external interface, wherein the positioning information is encrypted by the UE based on the encryption key.

[0337] 42. The positioning server function of claim 23, wherein the positioning server function is located at the serving base station.

[0338] 43. The positioning server function of claim 23, wherein the RAN is a Next Generation Radio Access Network (NG-RAN) that provides 5G New Radio (NR) wireless access to the UE, and the serving base station is a serving NR Node B (SgNB) of the UE.

[0339] 44. The positioning server function of claim 39, wherein the request to locate the UE is received from an access and mobility management function (AMF) or a previous SgNB for the UE.

[0340] 45. The positioning server function of claim 39, wherein the at least one processor is further configured to:

[0341] identifying a change of an SgNB of the UE, wherein the change of the SgNB is to a new SgNB; and

[0342] Send a positioning context for the UE to the new SgNB via the external interface, wherein the positioning context enables the new SgNB to continue positioning reporting for the UE.

[0343] 46. ​​A positioning server function according to claim 41, wherein the at least one processor is configured to identify a change of the SgNB of the UE by being configured to determine a handover of the UE to a serving cell of the new SgNB when the UE is in a connected state, or to receive a request for a UE context from the new SgNB when the UE is in an inactive state.

[0344] 47. The positioning server function of claim 41 , wherein the positioning context comprises one of:

[0345] (i) information of the positioning request initiated by the external client;

[0346] (ii) an indication of the type of positioning information received from the UE;

[0347] (iii) an indication of uplink (UL) positioning measurements for the UE being obtained by the SgNB;

[0348] (iv) an indication of UL positioning measurements for the UE being obtained by other NR Node Bs (gNBs) or Reception Points (RPs) and the identities of the other gNBs or RPs;

[0349] (v) an indication of DL Reference Signals (RS) being transmitted by other gNBs or Transmission Points (TPs) and the identities of the other gNBs or TPs;

[0350] (vi) an indication of a UL signal being sent by the UE;

[0351] (vii) locate the session identifier;

[0352] (viii) an indication to the UE to use the L1 or L2 protocol level for sending the positioning information;

[0353] (ix) the positioning capability of the UE; or

[0354] (x) Some combination of these.

[0355] 48. The positioning server function of claim 41, wherein the at least one processor is further configured to:

[0356] receiving, via the external interface, a type of measurement from a plurality of neighboring NR Node Bs (NgNBs) in the RAN, wherein calculating positioning of the UE or calculating timing information of the plurality of NgNBs is based in part on the type of measurement;

[0357] determining whether there is sufficient or insufficient signaling connectivity at the new SgNB to allow the new SgNB to receive the type of measurements from the plurality of NgNBs;

[0358] When it is determined that the signaling connectivity is insufficient, canceling the type of measurement in the plurality of NgNBs after the SgNB is changed;

[0359] When it is determined that signaling connectivity is sufficient, refraining from canceling the type of measurements in the plurality of NgNBs after the SgNB change; and

[0360] An indication of a determination of sufficient or insufficient signaling connectivity is sent to the new SgNB via the external interface, wherein when the indication of sufficient signaling connectivity is provided, the indication enables the new SgNB to configure at least some of the multiple NgNBs to send the type of measurements to the new SgNB, wherein when the indication of insufficient signaling connectivity is provided, the indication enables the new SgNB to refrain from configuring the multiple NgNBs.

[0361] 49. A positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and configured to locate the UE, the positioning server function comprising:

[0362] means for receiving a request for locating the UE, wherein the request for locating the UE is based on a positioning request initiated by an external client and is received using control plane signaling;

[0363] means for receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level;

[0364] means for calculating the position of the UE using the positioning information; and

[0365] Means for sending a location report including the location of the UE to the external client using user plane signaling.

[0366] 50. A non-transitory computer readable medium comprising program code stored thereon, the program code being operable to configure at least one processor in a positioning server function located at a serving base station for a user equipment (UE) in a radio access network (RAN) and configured to locate the UE, the program code comprising:

[0367] program code for receiving a request to locate the UE, wherein the request to locate the UE is based on a positioning request initiated by an external client and is received using control plane signaling;

[0368] program code for receiving positioning information from the UE at a layer 1 (L1) or layer 2 (L2) protocol level;

[0369] Program code for calculating a position of the UE using the positioning information; and

[0370] Program code for sending a location report including the location of the UE to the external client using user plane signaling.

[0371] References throughout this specification to "one example," "example," "some examples," or "exemplary implementations" mean that the particular feature, structure, or characteristic described in conjunction with that feature and / or example may be included in at least one feature and / or example of the claimed subject matter. Thus, the appearances of the phrases "in one example," "example," "in some examples," or "in some implementations," or other similar phrases throughout this specification do not necessarily all refer to the same features, examples, and / or limitations. Furthermore, particular features, structures, or characteristics may be combined in one or more examples and / or features.

[0372] Some parts of the detailed description included herein are presented according to the algorithm or symbolic representation of the operation of the binary digital signal stored in the memory of a specific device or a special computing device or platform. In the context of this specific specification, the term specific device or similar term includes a general-purpose computer (once it is programmed to perform specific operations according to instructions from program software). Algorithmic description or symbolic representation is an example of a technology used by ordinary technicians in signal processing or related fields to convey the essence of their work to other technicians in the field. Algorithms are considered here, and are generally considered to be self-consistent sequences of operations or similar signal processing that produce desired results. In this context, operations or processing involve physical manipulation of physical quantities. Generally, although not necessarily, these quantities can take the form of electrical or magnetic signals that can be stored, transferred, combined, compared or otherwise manipulated. It has been proven that sometimes (mainly for public use) it is convenient to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals, etc. However, it should be understood that all of these or similar terms should be associated with appropriate physical quantities and are only convenient labels. Unless otherwise specifically stated, as is apparent from the discussion herein, it should be understood that throughout the specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," and the like refer to actions or processes of a specific device, such as a special-purpose computer, a special-purpose computing device, or a similar special-purpose electronic computing device. Thus, in the context of this specification, a special-purpose computer or a similar special-purpose electronic computing device is capable of manipulating or transforming signals, which are typically represented as physical electronic or magnetic quantities within a memory, register, or other information storage device, transmission device, or display device of the special-purpose computer or a similar special-purpose electronic computing device.

[0373] In the foregoing detailed description, numerous specific details have been set forth to provide a comprehensive understanding of the claimed subject matter. However, those skilled in the art will appreciate that the claimed subject matter may be practiced without these specific details. In other instances, methods and apparatus known to those of ordinary skill in the art have not been described in detail in order to avoid obscuring the claimed subject matter.

[0374] As used herein, the terms "and," "or," and "and / or" may include multiple meanings, which are also expected to depend at least in part on the context in which such terms are used. In general, if "or" is used to relate a list such as A, B, or C, "or" is intended to mean A, B, and C used in an inclusive sense, as well as A, B, or C used in an exclusive sense. In addition, as used herein, the term "one or more" may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a plurality of features, structures, or characteristics, or some other combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example.

[0375] While there has been shown and described what are presently considered to be exemplary features, it will be appreciated by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the claimed subject matter. Furthermore, many modifications may be made to adapt a particular situation to the teachings of the claimed subject matter without departing from the central concepts described herein.

[0376] Therefore, it is intended that the claimed subject matter not be limited to the particular examples disclosed, but that such claimed subject matter may also include all aspects falling within the scope of the appended claims and their equivalents.

Claims

1. A method for locating a user equipment UE, the method comprising: receiving, from a serving base station in a radio access network RAN, a first request for a first positioning measurement and a second request for a second positioning measurement; Then the method comprises the following steps: Sending the first positioning measurement to the serving base station at a layer 1 L1 or layer 2 L2 protocol level at a first periodic interval; and sending the second positioning measurement to the serving base station at a second cycle interval, wherein the first cycle interval is shorter than the second cycle interval, The first positioning measurement and the second positioning measurement are used to determine timing information of multiple base stations, and the first positioning measurement and the timing information are used by the serving base station to determine the positioning of the UE, wherein the first positioning measurement and the second positioning measurement include positioning measurements of downlink DL signals received from a plurality of base stations in the RAN, the first positioning measurement includes a reference signal time difference RSTD measurement, a sensor measurement, or both RSTD and sensor measurement, the second positioning measurement includes a receive time-transmit time Rx-Tx measurement, and The L1 or L2 protocol level includes one of the following: (i) Physical layer; (ii) Media Access Control (MAC) layer; (iii) Radio Link Control (RLC) layer; (iv) Packet Data Convergence Protocol (PDCP) layer; or (v) some combination of these.

2. The method according to claim 1, wherein: The plurality of base stations include the serving base station.

3. The method according to claim 2, wherein: The DL signal includes a positioning reference signal, a tracking reference signal, or both.

4. The method according to claim 1, further comprising: receiving a request for positioning capability of the UE from the serving base station; as well as The positioning capability of the UE is sent to the serving base station, wherein the positioning capability indicates a capability of sending the first positioning measurement at the L1 or L2 protocol level.

5. The method according to claim 1, wherein: The first request for the first positioning measurement includes an encryption key, and the method further includes encrypting the first positioning measurement using the encryption key before sending the first positioning measurement to the serving base station at the L1 or L2 protocol level.

6. The method according to claim 1, wherein: The RAN is a next generation radio access network NG-RAN that provides 5G New Radio NR wireless access to the UE, and the serving base station is a serving NR Node B SgNB for the UE.

7. The method of claim 1, wherein the second positioning measurement is sent to the serving base station at a Radio Resource Control (RRC) protocol level or at the L1 or L2 protocol level.

8. The method according to claim 1, further comprising: receiving a third request to send an uplink (UL) signal from the serving base station; as well as The uplink (UL) signal is sent at a third cycle interval, wherein the first cycle interval is shorter than the third cycle interval, wherein the UL signal enables a plurality of base stations in the RAN to perform positioning measurements for the UE, wherein the plurality of base stations include the serving base station.

9. The method according to claim 8, wherein: The UL signal includes a positioning reference signal, a sounding reference signal, or both.

10. The method according to claim 8, wherein: The first request, the second request, and the third request are received in respective first, second, and third messages of a Radio Resource Control, RRC, protocol.

11. The method according to claim 10, wherein: The first, second, and third messages are the same message.

12. A UE capable of supporting positioning of a user equipment UE, the UE comprising: a wireless transceiver configured to communicate wirelessly with a base station in a radio access network RAN; at least one memory; at least one processor coupled to the wireless transceiver and the at least one memory, wherein the at least one processor is configured to: receiving, via the wireless transceiver, a first request for a first positioning measurement and a second request for a second positioning measurement from a serving base station in a radio access network RAN; wherein the at least one processor is configured to then: Sending the first positioning measurement to the serving base station at a layer 1 L1 or layer 2 L2 protocol level via the wireless transceiver at a first periodic interval; and sending the second positioning measurement to the serving base station via the wireless transceiver at a second cycle interval, wherein the first cycle interval is shorter than the second cycle interval, The first positioning measurement and the second positioning measurement are used to determine timing information of multiple base stations, and the first positioning measurement and the timing information are used by the serving base station to determine the positioning of the UE, wherein the first positioning measurement and the second positioning measurement include positioning measurements of downlink DL signals received from a plurality of base stations in the RAN, the first positioning measurement includes a reference signal time difference RSTD measurement, a sensor measurement, or both RSTD and sensor measurement, the second positioning measurement includes a receive time-transmit time Rx-Tx measurement, and The L1 or L2 protocol level includes one of the following: (i) Physical layer; (ii) Media Access Control (MAC) layer; (iii) Radio Link Control (RLC) layer; (iv) Packet Data Convergence Protocol (PDCP) layer; or (v) some combination of these.

13. The UE according to claim 12, wherein: The plurality of base stations include the serving base station.

14. The UE according to claim 13, wherein: The DL signal includes a positioning reference signal, a tracking reference signal, or both.

15. The UE according to claim 12, wherein: The at least one processor is further configured to: receiving, via the wireless transceiver, a request for positioning capabilities of the UE from the serving base station; and The positioning capability of the UE is sent to the serving base station via the wireless transceiver, wherein the positioning capability indicates a capability of sending the first positioning measurement at the L1 or L2 protocol level.

16. The UE according to claim 12, wherein: The first request for the first positioning measurement includes an encryption key, and the at least one processor is further configured to encrypt the first positioning measurement using the encryption key before sending the first positioning measurement to the serving base station at the L1 or L2 protocol level.

17. The UE according to claim 12, wherein: The RAN is a next generation radio access network NG-RAN that provides 5G New Radio NR wireless access to the UE, and the serving base station is a serving NR Node B SgNB for the UE.

18. The UE according to claim 12, wherein: The second positioning measurement is sent to the serving base station at a radio resource control, RRC, protocol level or at the L1 or L2 protocol level.

19. The UE of claim 12, wherein the at least one processor is further configured to: receiving, via the wireless transceiver, a third request to send an uplink (UL) signal from the serving base station; and The uplink (UL) signal is sent via the wireless transceiver at a third cycle interval, wherein the first cycle interval is shorter than the third cycle interval, wherein the UL signal enables multiple base stations in the RAN to perform positioning measurements for the UE, wherein the multiple base stations include the serving base station.

20. The UE of claim 19, wherein the UL signal comprises a positioning reference signal, a sounding reference signal, or both.

21. The UE of claim 19, wherein the first request, the second request, and the third request are received in respective first, second, and third messages of a Radio Resource Control (RRC) protocol.

22. The UE according to claim 21, wherein: The first, second, and third messages are the same message.

23. A UE capable of supporting positioning of a user equipment UE, the UE comprising: means for receiving, from a serving base station in a radio access network RAN, a first request for a first positioning measurement and a second request for a second positioning measurement; The UE comprises: means for then sending the first positioning measurement to the serving base station at a layer 1 L1 or layer 2 L2 protocol level at a first periodic interval and sending the second positioning measurement to the serving base station at a second periodic interval, wherein the first periodic interval is shorter than the second periodic interval, The first positioning measurement and the second positioning measurement are used to determine timing information of multiple base stations, and the first positioning measurement and the timing information are used by the serving base station to determine the positioning of the UE, wherein the first positioning measurement and the second positioning measurement include positioning measurements of downlink DL signals received from a plurality of base stations in the RAN, the first positioning measurement includes a reference signal time difference RSTD measurement, a sensor measurement, or both RSTD and sensor measurement, the second positioning measurement includes a receive time-transmit time Rx-Tx measurement, and The L1 or L2 protocol level includes one of the following: (i) Physical layer; (ii) Media Access Control (MAC) layer; (iii) Radio Link Control (RLC) layer; (iv) Packet Data Convergence Protocol (PDCP) layer; or (v) some combination of these.

24. A non-transitory computer readable medium comprising program code stored thereon, the program code being operable to configure at least one processor in a user equipment (UE) capable of supporting positioning, the code comprising: program code for receiving, from a serving base station in a radio access network RAN, a first request for a first positioning measurement and a second request for a second positioning measurement; wherein the program code is operable to configure the at least one processor in the UE to support positioning of the UE, including program code for then sending the first positioning measurement to the serving base station at a layer 1 L1 or layer 2 L2 protocol level at a first periodic interval and sending the second positioning measurement to the serving base station at a second periodic interval, wherein the first periodic interval is shorter than the second periodic interval, The first positioning measurement and the second positioning measurement are used to determine timing information of multiple base stations, and the first positioning measurement and the timing information are used by the serving base station to determine the positioning of the UE, wherein the first positioning measurement and the second positioning measurement include positioning measurements of downlink DL signals received from a plurality of base stations in the RAN, the first positioning measurement includes a reference signal time difference RSTD measurement, a sensor measurement, or both RSTD and sensor measurement, the second positioning measurement includes a receive time-transmit time Rx-Tx measurement, and The L1 or L2 protocol level includes one of the following: (i) Physical layer; (ii) Media Access Control (MAC) layer; (iii) Radio Link Control (RLC) layer; (iv) Packet Data Convergence Protocol (PDCP) layer; or (v) some combination of these.