Signaling and procedures for supporting reference location devices

Abstract

Techniques for communication are disclosed. In one aspect, a location server receives a registration request from a network entity serving a reference device for the reference device to operate as a reference location device (RLD), the registration request includes one or more parameters that enable the location server to communicate with the reference device via the positioning protocol, triggers a positioning procedure with the reference device via a positioning protocol based on the one or more parameters, receives one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol, and determines one or more correction terms for positioning one or more user equipments (UEs) based at least in part on a location of the reference device and the one or more reference positioning measurements.

Description

Priority claims

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to Greek Patent Application No. 20210100208, entitled "SIGNALING AND PROCEDURES FOR SUPPORTING REFERENCE LOCATION DEVICES," filed March 30, 2021, which is assigned to the assignee of the present application and is expressly incorporated herein by reference in its entirety. [Technical Field]

[0002] Aspects of the present disclosure generally relate to wireless communications. [Background technology]

[0003] Wireless communication systems have evolved through various generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including intermediate 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-enabled wireless service, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular and personal communications services (PCS) systems. Examples of known cellular systems include the Cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), etc.

[0004]

[0004] The fifth-generation (5G) wireless standard, known as New Radio (NR), requires, among other improvements, higher data rates, a greater number of connections, and better coverage. The 5G standard from the Next Generation Mobile Network Alliance is designed to provide data rates of tens of megabits per second to each of tens of thousands of users and 1 gigabit per second to dozens of workers on an office floor. To support large sensor deployments, hundreds of thousands of simultaneous connections should be supported. Therefore, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signaling efficiency should be enhanced and latency should be significantly reduced compared to current standards. Summary of the Invention

[0005] The following presents a simplified summary related to one or more aspects disclosed herein. As such, the following summary is not intended to be an extensive overview related to all contemplated aspects, nor is it intended to identify key or critical elements related to all contemplated aspects or to delineate the scope related to particular aspects. As such, the following summary has the sole purpose of presenting some concepts related to one or more aspects related to the mechanisms disclosed herein in a simplified form as a prelude to the detailed description presented below.

[0006]

[0006] In one aspect, a method of communication performed by a location server includes receiving a registration request from a network entity serving a reference device, the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; instigating a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; and determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements.

[0007]

[0007] In one aspect, a method of communication performed by a reference device includes sending a registration request to a network entity requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters indicating the capability of the reference device to operate as an RLD; receiving a request to perform one or more reference positioning measurements from a location server via a positioning protocol; performing one or more reference positioning measurements based on receiving the request; and sending the one or more reference positioning measurements to the location server via the positioning protocol.

[0008]

[0008] In one aspect, a method of communication implemented by a location server includes sending a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages including a location information request for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; receiving one or more second NRPPa messages from the network entity from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least one or more reference positioning measurements; and determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements.

[0009]

[0009] In one aspect, a method of communication implemented by a location server includes sending a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) in the RAN node; receiving one or more second NRPPa messages from the RAN node from the network entity, the one or more second NRPPa messages including an SRS configuration defining an SRS to be transmitted by the RLD in the RAN node.

[0010]

[0010] In one aspect, the location server includes a memory, a communication interface, and at least one processor communicatively coupled to the memory and the communication interface, wherein the at least one processor is configured to: receive, via the communication interface, a registration request from a network entity serving the reference device requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; initiate a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receive, via the communication interface, one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; and determine one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements.

[0011]

[0011] In one aspect, the reference device includes a memory, a communication interface, and at least one processor communicatively coupled to the memory and the communication interface, and the at least one processor is configured to: cause the communication interface to send a registration request to a network entity requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters indicating the capability of the reference device to operate as an RLD; receive a request to perform one or more reference positioning measurements from a location server via a positioning protocol via the communication interface; perform one or more reference positioning measurements based on receiving the request; and cause the communication interface to send the one or more reference positioning measurements to the location server via the positioning protocol.

[0012] In one aspect, a location server includes a memory, a communication interface, and at least one processor communicatively coupled to the memory and the communication interface, wherein the at least one processor causes the communication interface to send, to a network entity, a request to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages being transmitted to the RAN node. receiving, via a communication interface from a network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least one or more reference positioning measurements; and determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements.

[0013]

[0013] In one aspect, a location server includes a memory, a communication interface, and at least one processor communicatively coupled to the memory and the communication interface, wherein the at least one processor is configured to: cause the communication interface to send a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) in the RAN node; receive one or more second NRPPa messages from the RAN node via the communication interface from the network entity, the one or more second NRPPa messages including an SRS configuration defining an SRS to be transmitted by the RLD in the RAN node.

[0014]

[0014] In one aspect, the location server includes means for receiving a registration request from a network entity serving the reference device requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; means for initiating a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; means for receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; and means for determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements.

[0015]

[0015] In one aspect, the reference device includes means for sending a registration request to a network entity requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters indicating the capability of the reference device to operate as an RLD; means for receiving a request from a location server via a positioning protocol to perform one or more reference positioning measurements; means for performing one or more reference positioning measurements based on receiving the request, and means for sending the one or more reference positioning measurements to the location server via the positioning protocol.

[0016]

[0016] In one aspect, the location server includes means for sending a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages including a location information request for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; means for receiving from the network entity one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least one or more reference positioning measurements; and means for determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements.

[0017]

[0017] In one aspect, the location server includes means for sending a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, wherein the one or more first NRPPa messages include a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) in the RAN node; and means for receiving from the network entity one or more second NRPPa messages from the RAN node, wherein the one or more second NRPPa messages include an SRS configuration defining an SRS to be transmitted by the RLD in the RAN node.

[0018]

[0018] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: receive a registration request from a network entity serving the reference device requesting that the reference device act as a reference location device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; initiate a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receive one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; and determine one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements.

[0019]

[0019] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a reference device, cause the reference device to send a registration request to a network entity requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters indicating the reference device's ability to operate as an RLD; receive a request to perform one or more reference positioning measurements from a location server via a positioning protocol; perform one or more reference positioning measurements based on receiving the request and send the one or more reference positioning measurements to the location server via the positioning protocol.

[0020] In one aspect, a non-transitory computer-readable medium includes computer-executable instructions that, when executed by a location server, cause the location server to send a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages being received from a Reference Location Device (RLD) at the RAN node. receiving, from a network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least one or more reference positioning measurements; and determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements.

[0021]

[0021] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to send a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) in the RAN node; and receive one or more second NRPPa messages from the network entity from the RAN node, the one or more second NRPPa messages including an SRS configuration defining an SRS to be transmitted by an RLD in the RAN node.

[0022] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description.

[0023]

[0023] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided merely to illustrate, not to limit, the aspects. [Brief explanation of the drawings]

[0024] [Figure 1]

[0024] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 2A]

[0025] FIG. 1 illustrates an example wireless network structure, according to aspects of the present disclosure. [Figure 2B] FIG. 1 illustrates an example wireless network structure, according to aspects of the present disclosure. [Figure 3A]

[0026] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communication as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a base station and configured to support communication as taught herein; [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a network entity and configured to support communications as taught herein; [Figure 4]

[0027] FIG. 1 illustrates an example wireless communication network in which reference location devices (RLDs) are used to assist in positioning UEs, according to aspects of the present disclosure. [Figure 5]

[0028] 1 illustrates an exemplary positioning operation according to aspects of the present disclosure. [Figure 6]

[0029] FIG. 1 illustrates an example RLD positioning operation according to an aspect of the disclosure. [Figure 7]

[0030] FIG. 1 illustrates two principle architectural options for supporting RLD in a network, according to an aspect of the present disclosure. [Figure 8]

[0031] FIG. 1 is a diagram of a control plane protocol stack, according to an aspect of the present disclosure. [Figure 9]

[0032] FIG. 1 illustrates an example RLD positioning operation using RLD access registration, according to an aspect of the disclosure. [Figure 10]

[0033] FIG. 1 illustrates an example Long Term Evolution (LTE) Positioning Protocol (LPP) Protocol Data Unit (PDU) transfer between a location server and an RLD, according to an aspect of the present disclosure. [Figure 11]

[0034] FIG. 1 illustrates an example RLD-related New Radio Positioning Protocol type A (NRPPa) PDU transfer between an LMF and a Radio Access Network (RAN) node, according to an aspect of the present disclosure. [Figure 12]

[0035] FIG. 1 illustrates an example RLD positioning operation with RLD registration using supplementary services, according to an aspect of the disclosure. [Figure 13]

[0036] FIG. 1 illustrates an exemplary F1 protocol stack. [Figure 14]

[0037] FIG. 10 illustrates an example RLD positioning operation for a scenario in which the RLD operates as part of a base station, according to aspects of the disclosure. [Figure 15]

[0038] 1 illustrates an example RLD sounding reference signal (SRS) configuration procedure, according to an aspect of the present disclosure. [Figure 16]

[0039] FIG. 1 illustrates an exemplary method of communication according to an aspect of the present disclosure. [Figure 17] FIG. 1 illustrates an exemplary method of communication according to an aspect of the present disclosure. [Figure 18] FIG. 1 illustrates an exemplary method of communication according to an aspect of the present disclosure. [Figure 19] FIG. 1 illustrates an exemplary method of communication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0025]

[0040] Aspects of the present disclosure are provided in the following description and related drawings, directed to various examples provided for purposes of illustration. Alternative aspects may be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the present disclosure.

[0026]

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

[0027]

[0042] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0028]

[0043] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that various actions described herein may be performed by particular circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or a combination of both. Furthermore, a sequence of actions described herein may be considered to be embodied as a whole in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, cause or instruct associated processors of a device to perform the functions described herein. Accordingly, various aspects of the present disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, “logic configured to” perform the described actions.

[0029]

[0044] The terms “user equipment” (UE) and “base station,” as used herein, are not intended to be specific to or otherwise limited to any particular radio access technology (RAT) unless otherwise specified. Generally, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., an automobile, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or (e.g., at some times) stationary and may communicate with a radio access network (RAN). The term “UE” as used herein may be referred to interchangeably as an “access terminal” or “AT,” “client device,” “wireless device,” “subscriber device,” “subscriber terminal,” “subscriber station,” “user terminal” or “UT,” “mobile device,” “mobile terminal,” “mobile station,” or variations thereof. Generally, a UE can communicate with a core network via a RAN, through which the UE can be connected to external networks such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0030]

[0045] Depending on the network in which it is deployed, a base station may operate according to one of several RATs in communication with UEs and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), next-generation eNB (ng-eNB), new radio (NR) Node B (also referred to as gNB or gNode B), etc. Base stations may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide purely edge node signaling functionality, while in other systems, it may provide additional control and / or network management functions. A communication link through which a UE can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term Traffic Channel (TCH) may refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0031]

[0046] The term "base station" may refer to a single physical transmit receiving point (TRP) or multiple physical TRPs, which may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to the base station's cell (or several cell sectors). When the term "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-collocated physical TRPs may be a serving base station that receives measurement reports from a UE and a neighbor base station whose reference radio frequency (RF) signal the UE is measuring. A TRP is a point from which a base station transmits and receives wireless signals, and therefore, as used herein, references to transmission from or reception at a base station should be understood as referring to the particular TRP of the base station.

[0032]

[0047] In some implementations that support UE positioning, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may transmit reference signals to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to the UE) and / or a location measurement unit (e.g., when receiving and measuring signals from the UE).

[0033]

[0048] An "RF signal" comprises electromagnetic waves of a given frequency that transport information through space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through a multipath channel. The same transmitted RF signal on different paths between a transmitter and a receiver is sometimes referred to as a "multipath" RF signal.

[0034]

[0049] 1 illustrates an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs where the wireless communication system 100 corresponds to an LTE network, or gNBs where the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0035]

[0050] The base stations 102 collectively form the RAN and may interface with a core network 170 (e.g., Evolved Packet Core (EPC) or 5G Core (5GC)) through backhaul links 122 and to one or more location servers 172 (e.g., a Location Management Function (LMF) or a Secure User Plane Location (SUPL) Location Platform (SLP)) through the core network 170. The location server(s) 172 may be part of the core network 170 or may be external to the core network 170. In addition to other functions, the base stations 102 may perform functions related to one or more of the following: forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for Non-Access Stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracing, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0036]

[0051] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In one aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., physical cell identifier (PCI), extended cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access to different types of UEs. Because a cell is supported by a particular base station, the term “cell” may refer to either or both the logical communication entity and the base station that supports it, depending on the context. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, so long as the carrier frequency can be detected and used for communication within some portion of the geographic coverage area 110.

[0037]

[0052] The geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in handover regions), but some of the geographic coverage areas 110 may be significantly overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that significantly overlaps with the geographic coverage area 110 of one or more macrocell base stations 102. A network including both small cell and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include Home eNBs (HeNBs) that may serve restricted groups known as Closed Subscriber Groups (CSGs).

[0038]

[0053] The communication link 120 between the base station 102 and the UE 104 may include uplink transmissions (also called reverse link) from the UE 104 to the base station 102, and / or downlink (DL) transmissions (also called forward link) from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

[0039]

[0054] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 communicating with a WLAN station (STA) 152 via a communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in the unlicensed frequency spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) procedure or a listen-before-talk (LBT) procedure before communicating to determine whether a channel is available.

[0040]

[0055] The small cell base station 102' may operate in licensed and / or unlicensed frequency spectrums. When operating in the unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. A small cell base station 102' employing LTE / 5G in the unlicensed frequency spectrum may boost coverage to and / or increase the capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MultiFire.

[0041]

[0056] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW and / or near-mmW frequencies in communication with the UE 182. Extremely high frequency (EHF) is the RF portion of the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 and 10 millimeters. Radio waves in this band are sometimes referred to as millimeter waves. Near-mmW may extend down to frequencies of 3 GHz with wavelengths of 100 millimeters. The very high frequency (SHF) band, also referred to as centimeter wave, extends between 3 GHz and 30 GHz. Communications using the mmW / near-mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the above description is by way of example only and should not be construed as limiting various aspects disclosed herein.

[0042]

[0057] Transmit beamforming is a technique for focusing an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that particular direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device(s). To change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (called a “phased array” or “antenna array”) that creates beams of RF waves that can be “steered” to point in different directions without actually moving the antennas. In particular, RF current from the transmitter is supplied to individual antennas with the proper phase relationship so that the waves from the separate antennas add together to increase radiation in desired directions while canceling and suppressing radiation in undesired directions.

[0043]

[0058] A transmit beam may be quasi-colocated, meaning that the transmit beam appears to a receiver (e.g., a UE) to have the same parameters regardless of whether the network node's transmit antennas themselves are physically colocated. In NR, there are four types of quasi-colocation (QCL) relationships. In particular, a given type of QCL relationship means that some parameters related to a second reference RF signal on a second beam can be derived from information about the source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, mean delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and mean delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0044]

[0059] In receive beamforming, a receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) an RF signal received from that direction. Thus, when a receiver is said to beamform in a direction, it means that the beam gain in that direction is higher relative to the beam gains along other directions, or that the beam gain in that direction is highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signal received from that direction.

[0045]

[0060] The transmit beam and the receive beam may be spatially related. The spatial relationship means that parameters for a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0046]

[0061] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if the UE forms a downlink beam, it is a receive beam to receive the downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if the base station forms an uplink beam, it is an uplink receive beam, and if the UE forms an uplink beam, it is an uplink transmit beam.

[0047]

[0062] In 5G, the frequency spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges: FR1 (450 to 6000 MHz), FR2 (24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). The mmW frequency band generally includes the FR2, FR3, and FR4 frequency ranges. Thus, the terms “mmW” and “FR2” or “FR3” or “FR4” may generally be used interchangeably.

[0048]

[0063] In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and may be a carrier in licensed frequencies (although this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in unlicensed frequencies. The secondary carrier may contain only the necessary signaling information and signals; for example, since both the primary uplink carrier and the primary downlink carrier are typically UE-specific, nothing UE-specific may be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether a PCell or an SCell) corresponds to the carrier frequency / component carrier over which some base station is communicating, terms such as "cell," "serving cell," "component carrier," and "carrier frequency" may be used interchangeably.

[0049]

[0064] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or “PCell”), and other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a doubling of the data rate (i.e., 40 MHz) compared to that achieved by a single 20 MHz carrier.

[0050]

[0065] Wireless communications system 100 may further include a UE 164, which may communicate with macrocell base station 102 via communications link 120 and / or with mmW base station 180 via mmW communications link 184. For example, macrocell base station 102 may support a PCell and one or more SCells for UE 164, and mmW base station 180 may support one or more SCells for UE 164.

[0051]

[0066] In the example of FIG. 1, one or more Earth-orbiting Satellite Positioning System (SPS) space vehicles (SVs) 112 (e.g., satellites) may be used as independent sources of location information for any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity). The UE 104 may include one or more dedicated SPS receivers specially designed to receive SPS signals 124 to derive geolocation information from the SVs 112. An SPS generally includes a system of transmitters positioned to enable a receiver (e.g., a UE 104) to determine its location on or above the Earth based at least in part on signals (e.g., SPS signals 124) received from a transmitter (e.g., the SV 112). Such transmitters typically transmit signals marked with a repetitive pseudorandom noise (PN) code of a set number of chips. While typically located in the SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104.

[0052]

[0067] Use of SPS signals 124 may be augmented by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation system(s) that provide integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS)-aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), etc. Thus, as used herein, SPS may include any combination of one or more global and / or regional navigation satellite systems and / or augmentation systems, and SPS signals 124 may include SPS signals, SPS-like signals, and / or other signals related to such one or more SPSs.

[0053]

[0068] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity). In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct® (WiFi®-D), Bluetooth®, etc.

[0054]

[0069] 2A illustrates an exemplary wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) may be functionally considered to have control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.) that operate cooperatively to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect a gNB 222 to the 5GC 210, specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the ng-eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both an ng-eNB 224 and a gNB 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0055]

[0070] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance to the UE(s) 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, may each correspond to a single server. The location servers 230 may be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, the 5GC 210, and / or the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network or alternatively may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0056]

[0071] 2B shows another example wireless network structure 250. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A ) may be considered functionally as control plane functions provided by an Access and Mobility Management Function (AMF) 264 and user plane functions provided by a User Plane Function (UPF) 262, which operate cooperatively to form a core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a Session Management Function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and a Short Message Service Function (SMSF) (not shown), and a Security Anchor Function (SEAF). The AMF 264 also interacts with an Authentication Server Function (AUSF) (not shown) and the UE 204 and receives intermediate keys established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, the AMF 264 retrieves security material from the AUSF. The AMF 264's functions also include Security Context Management (SCM). The SCM receives keys from the SEAF that it uses to derive access network-specific keys. The AMF 264's functions also include location service management for barred services, transport for location service messages between the UE 204 and the Location Management Function (LMF) 270 (acting as the location server 230), transport for location service messages between the NG-RAN 220 and the LMF 270, EPS bearer identifier allocation for interworking with the Evolved Packet System (EPS), and UE 204 mobility event notification.Additionally, AMF264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0057]

[0072] The functions of the UPF 262 include serving as an anchor point for intra / inter-RAT mobility (when applicable), serving as an outer protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "termination markers" to the source RAN node. The UPF 262 may also support the transfer of location service messages over the user plane between the UE 204 and a location server such as the SLP 272.

[0058]

[0073] The functions of the SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF 262 to route traffic to the appropriate destination, control of policy enforcement and parts of QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0059]

[0074] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, may each correspond to a single server. The LMF 270 may be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via a core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functions as the LMF 270, but the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 on the control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and the SLP 272 may communicate with the UE 204 and external clients (not shown in FIG. 2B) on the user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0060]

[0075] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, particularly the UPF 262 and the AMF 264, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as the “Xn-C” interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as the “Uu” interface.

[0061]

[0076] The functions of the gNB 222 are divided between a gNB central unit (gNB-CU) 226 and one or more gNB distributed units (gNB-DUs) 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" or F1 access point (F1AP) interface. The gNB-CU 226 is a logical node that includes base station functions such as forwarding user data, mobility control, radio access network sharing, positioning, and session management, except for functions allocated exclusively to the gNB-DU(s). More specifically, the gNB-CU 226 hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that hosts the Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or multiple cells, and one cell is supported by only one gNB-DU 228. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, and with the gNB-DU 228 via the RLC, MAC, and PHY layers.

[0062]

[0077] 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated in a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or perform any of the network functions described herein, including a location server 230 and an LMF 270, or alternatively, may be unrelated to the NG-RAN 220 and / or 5GC 210 / 260 infrastructure shown in FIGS. 2A and 2B, such as a private network) to support file transmission operations taught herein. It will be appreciated that these components may be implemented in different types of devices (e.g., in an ASIC, in a system-on-chip (SoC), etc.) in different implementations. The illustrated components may also be incorporated in other devices in a communication system. For example, other devices in the system may include similar components to those described to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0063]

[0078] The UE 302 and the base station 304 each include at least one wireless wide area network (WWAN) transceiver 310 and 350, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for adjusting, means for refraining from transmitting, etc.) over one or more wireless communications networks (not shown), such as an NR network, an LTE network, a GSM network, etc. The WWAN transceivers 310 and 350 may be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., over at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communications medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358, respectively (e.g., messages, instructions, information, etc.), and conversely, for receiving and decoding signals 318 and 358, respectively (e.g., messages, instructions, information, pilots, etc.) in accordance with a designated RAT. In particular, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0064]

[0079] The UE 302 and the base station 304 also each, in at least some cases, include at least one short-range wireless transceiver 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and may provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for adjusting, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee, Z-Wave, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near field communications (NFC), etc.) over the wireless communications medium of interest. The short-range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368, respectively (e.g., messages, instructions, information, etc.), and conversely, for receiving and decoding signals 328 and 368, respectively (e.g., messages, instructions, information, pilots, etc.) in accordance with a designated RAT. In particular, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, and include one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368. As particular examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth transceivers, Zigbee and / or Z-Wave transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0065]

[0080] A transceiver circuit including at least one transmitter and at least one receiver may, in some implementations, comprise an integrated device (e.g., integrated as transmitter and receiver circuitry in a single communications device), in some implementations, comprise separate transmitter and receiver devices, or in other implementations, may be integrated in other ways. In one aspect, a transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that enable each device to perform transmit “beamforming” as described herein. Similarly, a receiver may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that enable each device to perform receive beamforming as described herein. In one aspect, a transmitter and a receiver may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that each device can only receive or transmit at a given time, rather than both receive and transmit simultaneously. The wireless communication device of the UE 302 and / or base station 304 (e.g., one or both of the transceivers 310 and 320 and / or 350 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0066]

[0081] The UE 302 and base station 304 also, in at least some cases, include satellite positioning system (SPS) receivers 330 and 370. The SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide a means for receiving and / or measuring SPS signals 338 and 378, respectively, such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. The SPS receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing the SPS signals 338 and 378, respectively. The SPS receivers 330 and 370 request information and actions from other systems as appropriate and perform the calculations necessary to determine the positions of the UE 302 and base station 304 using the measurements obtained via any suitable SPS algorithms.

[0067]

[0082] The base station 304 and the network entity 306 each include at least one network interface 380 and 390, each providing a means for communicating (e.g., a means for transmitting, a means for receiving, etc.) with other network entities. For example, the network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wire-based or wireless backhaul connection. In some aspects, the network interfaces 380 and 390 may be implemented as transceivers configured to support wire-based or wireless signal communication. This communication may involve, for example, sending and receiving messages, parameters, and / or other types of information.

[0068]

[0083] In one aspect, the at least one WWAN transceiver 310 and / or the at least one short-range wireless transceiver 320 may form a (wireless) communication interface of the UE 302. Similarly, the at least one WWAN transceiver 350, the at least one short-range wireless transceiver 360, and / or the at least one network interface 380 may form a (wireless) communication interface of the base station 304. Similarly, the at least one network interface 390 may form a (wireless) communication interface of the network entity 306. The various wireless transceivers (e.g., transceivers 310, 320, 350, and 360) and wired transceivers (e.g., network interfaces 380 and 390) may be generally characterized as at least one transceiver or, alternatively, as at least one communication interface. Thus, whether a particular transceiver or communication interface relates to a wired or wireless transceiver or communication interface, respectively, can be inferred from the type of communication being performed (e.g., backhaul communication between network devices or servers generally involves signaling via at least one wired transceiver).

[0069]

[0084] The UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with the operations disclosed herein. The UE 302, base station 304, and network entity 306 each include at least one processor 332, 384, and 394, e.g., to provide functionality related to wireless communications and to provide other processing functions. The processors 332, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, and means for directing. In one aspect, the processors 332, 384, and 394 may include, for example, at least one general-purpose processor, multi-core processor, central processing unit (CPU), ASIC, digital signal processor (DSP), field programmable gate array (FPGA), other programmable logic device or processing circuitry, or various combinations thereof.

[0070]

[0085] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memory components 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). The memory components 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning components 342, 388, and 398, respectively. The positioning components 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. In other aspects, the positioning components 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 may be memory modules stored in the memory components 340, 386, and 396, respectively, that, when executed by the processors 332, 384, and 394 (or modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. Figure 3A shows possible locations of the positioning component 342, which may be, for example, part of the at least one WWAN transceiver 310, the memory component 340, the at least one processor 332, or any combination thereof, or may be a standalone component. FIG. 3B shows possible locations of a positioning component 388, which may be part of, for example, at least one WWAN transceiver 350, a memory component 386, at least one processor 384, or any combination thereof, or may be a standalone component.FIG. 3C shows possible locations for a positioning component 398, which may be part of, for example, at least one network interface 390, a memory component 396, at least one processor 394, or any combination thereof, or may be a stand-alone component.

[0071]

[0086] The UE 302 may include one or more sensors 344 coupled to the at least one processor 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of movement data derived from signals received by the at least one WWAN transceiver 310, the at least one short-range wireless transceiver 320, and / or the SPS receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of movement detection sensor. Moreover, the sensor(s) 344 may include multiple different types of devices and combine their outputs to provide movement information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0072]

[0087] Additionally, the UE 302 includes a user interface 346 that provides means for providing instructions (e.g., audible and / or visual instructions) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such as a keypad, touchscreen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0073]

[0088] Referring more particularly to the at least one processor 384, in the downlink, IP packets from the network entity 306 may be provided to the at least one processor 384. The at least one processor 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The at least one processor 384 may provide RRC layer functions related to broadcasting of system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to transfer of upper layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0074]

[0089] The transmitter 354 and receiver 352 may implement Layer 1 (L1) functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), multi-level quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined with each other using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol streams are spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with each spatial stream for transmission.

[0075]

[0090] At the UE 302, the receiver 312 receives signals through its respective antenna(s) 316. The receiver 312 recovers information modulated onto RF carriers and provides the information to at least one processor 332. The transmitter 314 and receiver 312 implement Layer 1 functionality related to various signal processing functions. The receiver 312 may perform spatial processing on the information to recover spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency-domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to at least one processor 332 that implements Layer 3 (L3) and Layer 2 (L2) functions.

[0076]

[0091] In the uplink, at least one processor 332 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the core network. At least one processor 332 is also responsible for error detection.

[0077]

[0092] Similar to the functionality described with respect to downlink transmission by the base station 304, the at least one processor 332 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0078]

[0093] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select an appropriate coding and modulation scheme and to enable spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with each spatial stream for transmission.

[0079]

[0094] Uplink transmissions are processed at the base station 304 in a manner similar to that described with respect to the receiver function at the UE 302. The receiver 352 receives signals through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to at least one processor 384.

[0080]

[0095] In the uplink, the at least one processor 384 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 302. The IP packets from the at least one processor 384 may be provided to the core network. The at least one processor 384 is also responsible for error detection.

[0081]

[0096] For convenience, the UE 302, the base station 304, and / or the network entity 306 are illustrated in Figures 3A-3C as including various components that may be configured in accordance with various examples described herein, although it will be appreciated that the illustrated components may have different functionality in different designs.

[0082]

[0097] Various components of the UE 302, the base station 304, and the network entity 306 may communicate with one another via data buses 334, 382, ​​and 392, respectively. In one aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces of the UE 302, the base station 304, and the network entity 306, respectively. For example, when different logical entities are implemented in the same device (e.g., gNB functionality and location server functionality incorporated in the same base station 304), the data buses 334, 382, ​​and 392 may provide communication therebetween.

[0083]

[0098] The components of Figures 3A-3C may be implemented in various ways. In some implementations, the components of Figures 3A-3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide its functionality. For example, some or all of the functionality represented by blocks 310-346 may be implemented by a processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350-388 may be implemented by a processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Additionally, some or all of the functionality represented by blocks 390-398 may be implemented by a processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, acts, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it will be appreciated that such operations, acts, and / or functions may actually be performed by particular components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memory components 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0084]

[0099] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be separate from the network operator or operation of the cellular network infrastructure (e.g., the NG RAN 220 and / or the 5GC 210 / 260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 through the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0085]

[0100] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle of departure (DL-AoD) in NR. In an OTDOA or DL-TDOA positioning procedure, a UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from a pair of base stations, called reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives an identifier (ID) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in the assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity can estimate the location of the UE.

[0086]

[0101] For DL-AoD positioning, the positioning entity uses beam reports from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

[0087]

[0102] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on an uplink reference signal (e.g., a sounding reference signal (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.

[0088]

[0103] Downlink and uplink-based positioning methods include extended cell ID (E-CID) positioning and multi-round trip time (RTT) positioning (also called "multi-cell RTT"). In the RTT procedure, an initiator (base station or UE) transmits an RTT measurement signal (e.g., PRS or SRS) to a responder (UE or base station), and the responder transmits an RTT response signal (e.g., SRS or PRS) back to the initiator. The RTT response signal includes the difference between the ToA of the RTT measurement signal and the transmission time of the RTT response signal, called the receive-transmit (Rx-Tx) time difference. The initiator calculates the difference between the transmission time of the RTT measurement signal and the ToA of the RTT response signal, called the transmit-receive (Tx-Rx) time difference. The propagation time (also called "time of flight") between the initiator and the responder can be calculated from the Tx-Rx and Rx-Tx time differences. Based on the propagation time and the known speed of light, the distance between the initiator and responder may be determined. For multi-RTT positioning, the UE performs RTT procedures with multiple base stations to allow its location to be determined based on the known locations of the base stations (e.g., using multilateration). RTT and multi-RTT methods may be combined with other positioning techniques, such as UL-AoA and DL-AoD, to improve location accuracy.

[0089]

[0104] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identities, estimated timing, and signal strength of detected neighbor base stations. The location of the UE is then estimated based on this information and the known locations of the base station(s).

[0090]

[0105] To assist positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include identifiers of base stations (or base station cells / TRPs) from which to measure reference signals, reference signal configuration parameters (e.g., number of consecutive positioning subframes, periodicity of the positioning subframes, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighbor network nodes on its own without using assistance data.

[0091]

[0106] For OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and associated uncertainty, or a search window around the expected RSTD. In some cases, the expected RSTD value range may be + / - 500 microseconds (μs). In some cases, when any of the resources used for the positioning measurements are in FR1, the expected RSTD uncertainty value range may be + / - 32 μs. In other cases, when all of the resources used for the positioning measurement(s) are in FR2, the expected RSTD uncertainty value range may be + / - 8 μs.

[0092]

[0107] A location estimate may be called a position estimate, location, position, position fix, fix, or other names. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of the location. A location estimate may also be defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume that the location is expected to cover with some specified or default confidence level).

[0093]

[0108] To improve positioning performance, reference location devices (RLDs) have been introduced to assist NR positioning procedures. The RLD knows its location and can perform positioning measurements (e.g., RSTD, RSRP, Rx-Tx time difference, etc.) and report these measurements to a location server. Additionally, the RLD can transmit UL-PRS (e.g., SRS) to enable the TRP to measure and report uplink positioning measurements (e.g., RTOA, UL-AoA, gNB Rx-Tx time difference, etc.) from the device at its known location. The RLD's actual measurements can be compared to measurements that would be expected at the RLD's known location to determine correction terms for nearby UEs. Similarly, uplink measurements from the TRP can be compared to measurements that would be expected at the TRP from the RLD's transmitted signal at its known location. Downlink and / or uplink location measurements for other UEs can then be corrected based on the previously determined correction terms. The correction terms may represent calibration errors (e.g., group delay errors in the transmit and receive chains between the UE and the TRP, time synchronization errors between the TRPs, etc.) This principle is known from differential Global Navigation Satellite System (GNSS) operation.

[0094]

[0109] 4 is a diagram 400 of an example wireless communication network in which an RLD 410 (also referred to as a reference device) is used to assist in positioning of a UE 404, according to an aspect of the disclosure. In the example of FIG. 4, a UE 404 (e.g., any of the UEs described herein) is engaged in a positioning session with three TRPs 402-1, 402-2, and 402-3 (collectively, TRPs 402), labeled “TRP1,” “TRP2,” and “TRP3,” respectively. The TRPs 402 are transmitting downlink reference signals (e.g., DL-PRSs) toward the UE 404 to enable the UE 404 to perform positioning measurements on the reference signals (e.g., RSTD measurements in the example of FIG. 4).

[0095]

[0110] The RLD 410 also receives and measures downlink reference signals from the TRPs 402 and reports the measurements (e.g., RSTD) to a location server (not shown). If the TRP 402-1 is the reference TRP, the RSTD for the TRP 402-2 measured by the RLD 410 is RSTD meas = t2 - t1. The location server knows the locations of the RLD 410 and the TRP 402 and can therefore calculate the "true" (expected) RSTD at the location of the RLD 410 as follows:

[0096]

number

[0097] where c is the speed of light, (x0,y0) (represented in FIG. 4 as (x0,y0)) is the known location of RLD 410, (x1,y1) (represented in FIG. 4 as (x1,y1)) is the known location of TRP 402-1, and (x2,y2) (represented in FIG. 4 as (x2,y2)) is the known location of TRP 402-2.

[0098]

[0111] The location server can then determine the error term (e) as follows:

[0099]

number

[0100]

[0112] When a normal UE 404 (in an unknown location) is measuring the RSTD between TRP 402-1 and TRP 402-2, the location server can use the previously determined error term to correct the measured RSTD of the UE 404 as follows:

[0101]

number

[0102]

[0113] The location server can then use the corrected RSTD to estimate the location of the UE 404. The same principle applies to uplink positioning methods, where the RLD transmits uplink positioning signals (e.g., SRS) that are measured by the TRP. Given the known locations of the RLD and TRP, the TRP uplink measurements can be compared to "true" (expected) uplink measurements (e.g., UL-AoA, UL-RTOA, etc.). The difference between the "true" (expected) uplink measurements and the actually performed measurements will define an error term that can be used to correct the UE's uplink measurements.

[0103]

[0114] To support NR positioning techniques, an RLD with known location is expected to support the following functions: Measure DL-PRS and report relevant measurements (e.g. RSTD, Rx-Tx time difference, RSRP, etc.) to the location server. Transmits SRS, enabling the TRP to measure and report measurements related to the reference device (e.g., RTOA, Rx-Tx time difference, AoA) to the location server.

[0104]

[0115] The RLD may also support the following features: Reporting signaling, measurements, parameters related to receive and transmit timing delays, AoD and AoA extensions, and measurement calibration details. Reporting device location coordinate information to LMF if LMF does not have the information. The RLD with known location is a UE and / or a gNB. · The accuracy with which the location of the reference device is known.

[0105]

[0116] The RLD performs positioning measurements like a normal UE, but at a pre-known location, so the positioning protocol terminated in the RLD and TRP can be the same protocol used for positioning of a normal UE.

[0106]

[0117] 5 illustrates an example UE positioning operation 500 according to an aspect of the present disclosure. The UE positioning operation 500 may be performed by the UE 204, an NG-RAN node 502 in the NG-RAN 220 (e.g., a gNB 222, a gNB-CU 226, an ng-eNB 224, or other node in the NG-RAN 220), the AMF 264, the LMF 270, and a 5GC location services (LCS) entity 580 (e.g., any third-party application requesting the location of the UE 204, a public service access point (PSAP), an E-911 server, etc.).

[0107]

[0118] A location service request to obtain the location of the target (i.e., UE 204) can be initiated by the 5GC LCS entity 580, the AMF 264 serving the UE 204, or the UE 204 itself. Figure 5 illustrates these options as stages 510a, 510b, and 510c, respectively. In particular, in stage 510a, the 5GC LCS entity 580 sends a location service request to the AMF 264. Alternatively, in stage 510b, the AMF 264 generates the location service request itself. Alternatively, in stage 510c, the UE 204 sends a location service request to the AMF 264.

[0108]

[0119] Upon receiving (or generating) the location service request, the AMF 264 forwards the location service request to the LMF 270 in step 520. The LMF 270 then performs an NG-RAN positioning procedure with the NG-RAN node 502 in step 530a and a UE positioning procedure with the UE 204 in step 530b. The specific NG-RAN positioning procedure and UE positioning procedure may depend on the type of positioning method used to locate the UE 204, which may depend on the capabilities of the UE 204. The positioning method may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, and DL-AoD), uplink-based (e.g., UL-TDOA and UL-AoA), and / or downlink- and uplink-based (e.g., LTE / NR E-CID and RTT), as described above. Corresponding positioning procedures are described in detail in 3GPP Technical Specification (TS) 38.305, which is published and incorporated herein by reference in its entirety.

[0109]

[0120] The NG-RAN and UE positioning procedures may utilize LTE Positioning Protocol (LPP) signaling between the UE 204 and the LMF 270 and LPP Type A (LPPa) or NR Positioning Protocol Type A (NRPPa) signaling between the NG-RAN node 502 and the LMF 270. LPP is used point-to-point between a location server (e.g., the LMF 270) and a UE (e.g., the UE 204) to obtain location measurements or estimates or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single MT-LR, MO-LR, or network-induced location request (NI-LR)). Multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions, each performing a single operation (e.g., capability exchange, assistance data transfer, location information transfer). LPP transactions are referred to as LPP procedures.

[0110]

[0121] A prerequisite for step 530 is that an LCS correlation identifier (ID) and an AMF ID have been passed to the LMF 270 by the serving AMF 264. Both the LCS correlation ID and the AMF ID may be represented as strings selected by the AMF 264. The LCS correlation ID and the AMF ID are provided to the LMF 270 by the AMF 264 during the location service request in step 520. Then, when the LMF 270 instigates step 530, the LMF 270 also includes the LCS correlation ID for this location session along with the AMF ID indicating the AMF instance serving the UE 204. The LCS correlation identifier is used during a positioning session between the LMF 270 and the UE 204 to ensure that a positioning response message from the UE 204 is returned by the AMF 264 to the correct LMF 270 and carries an indication (LCS correlation identifier) ​​that can be recognized by the LMF 270.

[0111]

[0122] As described in more detail in 3GPP TS 23.273, which is published and incorporated herein by reference in its entirety, it should be noted that the LCS correlation ID serves as a location session identifier that may be used to identify messages exchanged between the AMF 264 and the LMF 270 for a particular location session for a UE. As described above and shown in stage 520, a location session between the AMF 264 and the LMF 270 for a particular UE is instigated by the AMF 264, and the LCS correlation ID may be used to identify this location session (e.g., may be used by the AMF 264 to identify state information for this location session, etc.).

[0112]

[0123] LPP positioning methods and associated signaling content are defined in the 3GPP LPP standard (3GPP TS37.355, which is published and incorporated herein by reference in its entirety). LPP signaling can be used to request and report measurements related to LTE-OTDOA, DL-TDOA, A-GNSS, E-CID, Sensor, TBS, WLAN, Bluetooth, DL-AoD, UL-AoA, and Multi-RTT positioning methods. Currently, an LPP measurement report may include the following measurements: (1) one or more ToA, TDOA, RSTD, or Rx-Tx measurements; (2) one or more AoA and / or AoD measurements (currently only for base stations that report UL-AoA and DL-AoD to LMF270); (3) one or more multipath measurements (ToA, RSRP, AoA / AoD per path); (4) one or more motion states (e.g., walking, driving, etc.) and trajectories (currently only for UE204); and (5) one or more report quality indications.

[0113]

[0124] As part of the NG-RAN node positioning procedure (stage 530a) and the UE positioning procedure (stage 530b), the LMF 270 may provide LPP assistance data in the form of DL-PRS configuration information for the selected positioning method to the NG-RAN node 502 and the UE 204. Alternatively or additionally, the NG-RAN node 502 may provide DL-PRS and / or UL-PRS configuration information for the selected positioning method to the UE 204. It should be noted that although FIG. 5 shows a single NG-RAN node 502, there may be multiple NG-RAN nodes 502 involved in a positioning session.

[0114]

[0125] When configured in DL-PRS and UL-PRS configurations, the NG-RAN node 502 and the UE 204 transmit and receive / measure their respective PRS at scheduled times. The NG-RAN node 502 and the UE 204 then send their respective measurements to the LMF 270.

[0115]

[0126] When the LMF 270 obtains measurements from the UE 204 and / or the NG-RAN node 502 (depending on the type of positioning method), it uses these measurements to calculate an estimate of the location of the UE 204. Then, in stage 540, the LMF 270 sends a location service response to the AMF 264 that includes the location estimate for the UE 204. The AMF 264 then forwards the location service response to the entity that generated the location service request in stage 510. In particular, if in stage 510a a location service request was received from the 5GC LCS entity 580, then in stage 550a the AMF 264 sends the location service response to the 5GC LCS entity 580. However, if in stage 510c a location service request was received from the UE 204, then in stage 550c the AMF 264 sends the location service response to the UE 204. Alternatively, if the AMF 264 generated a location service request in step 510b, then in step 550b the AMF 264 stores / uses the location service response itself.

[0116]

[0127] Note that while the above describes the UE positioning operation 500 as a UE-assisted positioning operation, it may instead be a UE-based positioning operation. A UE-assisted positioning operation is one in which the LMF 270 estimates the location of the UE 204, while a UE-based positioning operation is one in which the UE 204 estimates its own location.

[0117]

[0128] Referring to an RLD in the context of FIG. 5, any RLD location measurements will be used by the LMF 270 to correct measurements for the target UE 204. That is, the consumer of the RLD location information is the LMF 270, and therefore steps 510 and 520 are not performed for the RLD. This essentially means that the LMF 270 becomes the "LCS client" for the RLD and needs to be enabled to instigate a location session with the RLD in the absence of steps 510 and 520. Thus, for an RLD, the AMF 264 / LMF 270 will not receive location requests from an LCS client; instead, the location client for the RLD measurements will be the LMF 270 itself.

[0118]

[0129] As a result of the above, for an RLD positioning operation, steps 510 and 520 of Figure 5 may be replaced by an "RLD registration" procedure to make the LMF aware of the RLD in the network, and thus the LMF is enabled to instigate an LPP or NRPPa session with the desired RLD or NG-RAN serving the RLD, respectively. Figure 6 shows an example RLD positioning operation 600 according to an aspect of the disclosure. The RLD positioning operation 600 may be performed by an RLD 604 (e.g., any of the RLDs described herein), an NG-RAN node 602 (e.g., gNB 222, ng-eNB 224), an AMF 264, and an LMF 270.

[0119]

[0130] In step 610, an RLD registration procedure is performed to make the LMF 270 aware of the RLD 604 in the network. The registration procedure varies depending on whether the RLD 604 is a UE or a gNB; different registration procedures are described below. In step 620, the LMF 270 internally initiates a location service request to obtain the location of the target RLD 604 to determine correction data for UE positioning. The LMF 270 then performs an NG-RAN procedure with the NG-RAN node 602 in step 630a and an RLD procedure with the RLD 604 in step 630b. The RLD registration procedure in step 610 enables the LMF 270 to instigate the positioning procedure in step 630 in the same manner as currently specified for the target UE. In step 640, the LMF 270 determines correction data for UE positioning as described above with reference to FIG. 4.

[0120]

[0131] FIG. 7 illustrates two principle architecture options for supporting RLDs in a network according to aspects of the present disclosure. As a first option, as illustrated by diagram 700, an RLD 710 (e.g., any of the RLDs described herein) is considered a UE (e.g., UE 204) from the perspective of the LMF 270. Such an RLD may be any device that supports a control plane protocol stack and LPP positioning methods. This may include a normal (mobile) UE, a dedicated UE (which may generally be at a fixed location but may also be mobile), a mobile terminal (MT) in an integrated access and backhaul (IAB) node, a MT in a smart repeater, etc. As an example, such an RLD may be a UE 302, as shown in FIG. 3A.

[0121]

[0132] FIG. 8 is a diagram 800 of a control plane protocol stack 800 according to an aspect of the present disclosure. As indicated by the double-arrowed lines in FIG. 8, each layer of the protocol stack 800 implemented by the RLD 710 communicates with the same layer in the gNB 222, the AMF 264, and the LMF 270, and vice versa. A particular instance of a protocol layer is referred to as a protocol “entity.” Thus, the terms “protocol layer” and “protocol entity” may be used interchangeably. Two corresponding protocol layers / entities are referred to as “peers,” “peer entities,” etc. Collectively, the PDCP layer, the RLC layer, and the MAC layer are referred to as “Layer 2” or “L2.” The PHY layer is referred to as “Layer 1” or “L1.”

[0122]

[0133] As a second option, as shown by diagram 750, the RLD is considered as part of the gNB 222 from the perspective of the LMF 270, either the gNB-DU 228 (RLD 722) or the enhanced TRP (eTRP) (RLD 720). The eTRP consists of an enhanced transmission point (eTP) and an enhanced reception point (eRP). Such an RLD may be any device that has an F1 protocol stack (as shown in FIG. 13) and supports the LPP positioning method. As an example, such an RLD may be the base station 304, as shown in FIG. 3B. As described in more detail below, in this option, the LPP message is encapsulated in an NRPPa. The gNB-CU 226 (terminating the NRPPa) extracts the LPP PDU and forwards it to the eTRP 720 using the F1 interface. Both the first and second options are described below.

[0123]

[0134] If the RLD can be considered a “UE” from the perspective of the LMF (as illustrated by diagram 700 in FIG. 7 ), two general RLD registration procedures are possible: (1) an RLD access registration procedure and (2) an RLD registration using a supplementary service procedure. FIG. 9 illustrates an example RLD positioning operation 900 using RLD access registration according to an aspect of the present disclosure. In the example of FIG. 9 , the RLD 710 can be a UE (e.g., UE 204). In this solution, the RLD 710 registers with the gNB and the 5G core network (e.g., 5G CORE 260) like a normal UE (e.g., UE 204). As part of this registration procedure, the UE provides an indication to the serving AMF 264 of whether the device can function as the RLD 710. The serving AMF 264 then registers the RLD 710 with the LMF 270 using a new reference device registration request service operation directed to the LMF 270. The reference device registration operation enables the LMF 270 to exchange LPP and NRPPa messages between the LMF 270 and the RLD 710 and the NG-RAN 220, respectively, later when the LMF 270 requires location measurements from the (registered) RLD 710.

[0124]

[0135] Steps 905 to 955 are similar to the general procedure used for registration of a UE to a gNB and 5G core network with the addition of steps 920 and 925.

[0125]

[0136] In step 905, the RLD 710 and the NG-RAN node 902 perform a 5G-NR RRC connection setup procedure (as a normal UE would). At the end of this procedure, the RLD 710 sends an RRC Setup Complete message with a "Registration Request" in the dedicated NAS-Message field to the NG-RAN node 902. The NAS Registration Request includes a 5G Mobility Management (5GMM) Capability Information Element (IE). This IE includes an indication of whether the UE currently supports LPP and 5G-LCS notification mechanisms. In one aspect, this IE also includes an indication of whether the UE is capable of operating as an RLD 710. For example, an additional bit may be allocated to indicate whether the UE is capable of operating as an RLD 710.

[0126]

[0137] At step 910, the gNB selects an AMF 264 and allocates a "RAN UE NGAP ID". The AMF 264 will use this ID to address the RLD context on the gNB. The gNB then sends an NGAP (NG Application Protocol) initial UE message to the selected AMF 264. The message carries the "Registration Request" message received from the RLD 710 in the RRC Setup Complete message at step 905. The "RAN UE NGAP ID" and the "RRC Establishment Reason" are also included in the message.

[0127]

[0138] In step 915, the RLD 710 and the 5GC perform NAS authentication and security procedures.

[0128]

[0139] In step 920, if the 5GMM capabilities IE received in step 910 indicates support for "RLD functionality," the AMF 264 invokes a "Reference Device Registration Request" service operation (e.g., an "Nlmf_Location_ReferenceDeviceRegistrationRequest" message) toward the LMF 270 selected to register the RLD 710 in the LMF 270. The service operation includes an LCS correlation identifier (assigned by the AMF 264) and an AMF identification along with a serving cell identification, and may also include a subscription permanent identifier (SUPI) and permanent equipment identifier (PEI) of the RLD 710. The LMF 270 maintains a database of RLDs 710. Each RLD 710 is associated with an LCS correlation ID and the AMF ID of the AMF instance serving the RLD 710.

[0129]

[0140] In step 925, if the LMF 270 can handle the RLD registration request, the LMF 270 returns an acknowledgement to the AMF 264 in a reference device registration response service operation (e.g., an "Nlmf_Location_ReferenceDeviceRegistrationResponse" message) directed to the AMF 264 that includes the LCS correlation identifier received in step 920. The LMF 270 stores the LCS correlation identifier and the AMF ID for later use in step 965.

[0130]

[0141] The Nlmf_ReferenceDevice service enables the LMF 270 to obtain RLD information and associated parameters. The service operations defined for the Nlmf_ReferenceDevice service are (1) a ReferenceDeviceRegistration request and response, which provides reference device information for an RLD 710 from the AMF 264 to the LMF 270, (2) a ReferenceDeviceRegistrationUpdate, which provides updated reference device information from the AMF 264 to the LMF 270 for a previously registered RLD 710, and (3) a ReferenceDeviceDeregistration, which allows the AMF 264 to deregister a previously registered RLD 710 in the LMF 270. Deregistration can also be considered a special case for ReferenceDeviceRegistrationUpdate.

[0131]

[0142] At stage 930, the AMF 264, the NG-RAN 220, and the RLD 710 continue with the typical registration procedure for a normal UE. The AMF 264 may initiate session setup with the gNB. The message typically includes a registration accept NAS message. The NAS registration accept may include an indication in the LMF 270 that the RLD registration was successful. The message may be an NGAP initial context setup request.

[0132]

[0143] In stage 935, the RLD 710 and the gNB perform an AS security procedure.

[0133]

[0144] In step 940, an RRC reconfiguration message is generally sent to the RLD 710 to set up radio bearers, etc. The message includes the 5GS registration result received in the registration accept message in step 930. The 5GS registration result informs the UE whether registration at the LMF 270 was successful. This step may not be required, but will inform the RLD 710 that registration at the LMF 270 was successful and that the RLD 710 can next expect a location request for calibration purposes.

[0134]

[0145] Steps 945 through 955 are similar to completing a normal registration procedure.

[0135]

[0146] At a later time in step 960, the LMF 270 may determine that location measurements are required from an RLD 710 previously registered at the LMF 270 and may instigate an LPP and / or NRPPa session with the RLD 710 or the NG-RAN 220 serving the RLD 710 in steps 965a and 965b (collectively step 965), respectively.

[0136]

[0147] The procedures in steps 965a and 965b may then be performed in a manner similar to that currently defined for a normal UE.

[0137]

[0148] At step 965a of Figure 9, the LMF 270 may instigate an LPP session with the RLD 710 comprising the transfer of one or more LPP PDUs to the RLD 710 and the receipt of one or more LPP PDUs from the RLD 710. The LPP PDUs may include an LPP Capability Request / Provide, an LPP Assistance Data Request / Provide, or an LPP Location Information Request / Provide message. The procedure for LPP PDU transfer is shown in Figure 10.

[0138]

[0149] In step 1005, the LMF 270 invokes the Namf_Communication_N1N2MessageTransfer service operation for this RLD 710 toward the AMF 264 that previously registered the RLD 710 at the LMF 270. This service operation contains one or more LPP PDUs that must be transferred to the RLD 710. This service operation contains the LCS correlation ID and AMF ID that were previously given to the LMF 270 in step 920 of Figure 9 and stored in the LMF 270. The AMF instance belonging to the AMF ID / LCS correlation ID is used to transfer the LPP message to the RLD 710.

[0139]

[0150] At stage 1010, if the RLD 710 is in a CM idle state, the AMF 264 initiates a network-triggered service request procedure defined in 3GPP TS 23.502 (published and incorporated herein by reference in its entirety) to establish a signaling connection with the RLD 710.

[0140]

[0151] In steps 1015a and 1015b, the AMF 264 includes the LPP PDU in the payload container of the NAS transport message and a routing identifier set to the LCS correlation ID that identifies the LMF 270 in the additional information of the NAS transport message as defined in 3GPP TS 24.501 (published and incorporated herein by reference in its entirety). The AMF 264 then sends the DL NAS transport message to the serving NG-RAN node 902 in an NGAP Downlink NAS Transport message as defined in 3GPP TS 38.413 (published and incorporated herein by reference in its entirety). The NG-RAN node 902 then forwards the DL NAS transport message to the RLD 710 in an RRC DL Information Transfer message.

[0141]

[0152] At stage 1020, if the LPP PDU is of type "Location Information Request", the RLD 710 performs the requested reference measurements (eg, RSTD, RSRP, UE Rx-Tx time difference measurements).

[0142]

[0153] In step 1025, if the RLD 710 entered the CM idle state during step 1020, the RLD 710 triggers a UE-triggered service request as defined in 3GPP TS 23.502 to establish a signaling connection with the AMF 264.

[0143]

[0154] In steps 1030a and 1030b, the RLD 710 includes the LPP PDU with the acquired reference measurements (if requested in step 1015) from step 1020 in the payload container of the UL NAS transport message and the routing identifier received in step 1015 in the additional information of the UL NAS transport message defined in 3GPP TS 24.501. The RLD 710 then sends the UL NAS transport message in an RRC UL Information Transfer message to the serving NG-RAN node 902. The NG-RAN node 902 forwards the UL NAS transport message to the AMF 264 in an NGAP Uplink NAS Transport message.

[0144]

[0155] At stage 1035, the AMF 264 invokes a Namf_Communication_N1MessageNotify service operation towards the LMF 270 indicated by the routing identifier received at stage 1030. The service operation includes the LPP message received at stage 1030 and the LCS correlation identifier in the N1 message container defined in 3GPP TS 29.518 (published and incorporated herein by reference in its entirety).

[0145]

[0156] 9 , at stage 965b, the LMF 270 may initiate an NRPPa session with the serving NG-RAN node 902 of the RLD 710 comprising the transfer of one or more NRPPa PDUs to the NG-RAN node 902 and the receipt of one or more NRPPa PDUs from the NG-RAN node 902. The NRPPa PDUs may include messages related to E-CID location information transfer, OTDOA information transfer, assistance information transfer, positioning information transfer, TRP information transfer, and measurement information transfer as defined in 3GPP TS 38.455 (published and incorporated by reference herein in its entirety). A procedure 1100 for NRPPa PDU transfer is shown in FIG. 11 .

[0146]

[0157] In step 1105, the LMF 270 invokes a Namf_Communication_N1N2MessageTransfer service operation for this RLD 710 towards the AMF 264 that previously registered the RLD 710 at the LMF 270. This service operation contains one or more NRPPa PDUs that must be transferred to the NG-RAN node 902. This service operation contains the LCS correlation ID and AMF ID that were previously provided to the LMF 270 in step 920 of Figure 9 and stored in the LMF 270.

[0147]

[0158] At stage 1110, if the RLD 710 is in CM idle state, the AMF 264 initiates a network-triggered service request procedure defined in 3GPP TS 23.502 to establish a signaling connection with the RLD 710.

[0148]

[0159] In step 1115, the AMF 264 forwards the NRPPa message to the serving NG-RAN node 902 in a UE-related NRPPa transport message of the NGAP DL via the NG signaling connection corresponding to the RLD 710 and includes a routing ID identifying the LMF 270 (e.g., the global address of the LMF 270).

[0149]

[0160] In stage 1120, the serving NG-RAN node 902 performs the actions for the RLD 710 requested by the NRPPa message in stage 1115. This may include determining an SRS configuration for the RLD 710, providing the RLD 710 with an SRS configuration, or activating a previously configured SRS in the RLD 710.

[0150]

[0161] In step 1125, the serving NG-RAN node 902 returns an NRPPa response message to the AMF 264 in a UE-related NRPPa transport message in the NGAP UL and includes the routing ID received in step 1115.

[0151]

[0162] At stage 1130, the AMF 264 invokes the Namf_Communication_N2InfoNotify service towards the LMF 270 indicated by the routing ID received at stage 1125. The service operation includes the NRPPa message received at stage 1125 and the LCS correlation ID from stage 1105 in the N2 information container defined in 3GPP TS 29.518.

[0152]

[0163] Returning to Figure 9, in step 970, the LMF 970 determines correction terms from the RLD or NG-RAN node measurements received in step 965 using the known location of the RLD 710, as described above with reference to Figure 4. The LMF 270 stores the correction terms and uses them to correct location measurements for other UEs. The LMF 270 repeats steps 965 through 970 whenever new or updated RLD measurements are needed.

[0153]

[0164] For this solution, a new service operation is required to enable the AMF 264 to register the RLD 710 in the LMF 270, as shown by steps 920 and 925 in FIG. 9. This operation may be part of the Nlmf_Location service operation or may be a new service operation (e.g., an Nlmf_ReferenceDevice service operation). In addition to the RLD registration, RLD deregistration and RLP registration update service operations may also be required. For example, - Reference Device Registration: Provides the LMF with RLD information including LCS Correlation ID, AMF ID, Extended CGI (ECGI), NR CGI (NCGI), RLD SUPI, and RLD PEI. Reference Device Registration Update: Provides the LMF with updated reference device information (e.g., new ECGI or NCGI in case the serving NG-RAN node changes, or the RLD location changes, etc.) for a previously registered reference device. - Reference device deregistration: Allows the AMF to deregister a reference device previously registered in the LMF (for example, when the serving AMF for the RLD changes or the RLD is switched off).

[0154]

[0165] As explained above, location procedures between the LMF and the RLD may be performed in a similar manner to a normal UE. NRPPa may be used as currently specified for uplink-based (e.g., UL-AoA, UL-TDOA) and downlink- and uplink-based (e.g., multi-RTT) positioning methods, and no changes to the NRPPa protocol appear to be necessary. LPP may also be used as currently defined, although some RLD-specific additions may be required.

[0155]

[0166] For example, referring to LPP capability transfer, positioning method capabilities (e.g., for UL-TDOA, UL-AoA, DL-TDOA, DL-AoD, or multi-RTT) apply equally to the RLD. They provide the LMF with the positioning-specific capabilities (e.g., supported measurements, etc.) supported by the RLD. The LPP capability provision message may include additional parameters / attributes such as the RLD's location (latitude / longitude / altitude along with uncertainty shape), location source (e.g., GNSS, A-GNSS, DL-TDOA, DL-AoD, actual measurement), velocity, whether the RLD is static / fixed or mobile, and whether the RLD is battery-powered or mains-operated (i.e., plugged in).

[0156]

[0167] For LPP assistance data transfer, no RLD specific additions appear to be required for delivery of assistance data: assistance data specific to regular (UE-assisted) positioning methods will apply equally to RLDs.

[0157]

[0168] For LPP location information transfer, positioning method specific request / provide messages are equally applicable to the RLD to request and provide location information for the UE (e.g., "NR-Multi-RTT-ProvideLocationInformation", "NR-DL-AoD-ProvideLocationInformation", "NR-DL-TDOA-ProvideLocationInformation"). However, some additions to "CommonIEsRequestLocationInformation" may be required. "CommonIEsRequestLocationInformation", which carries the common IEs for location information request LPP message types, contains a (mandatory) "LocationInformationType", which indicates whether the server requires location estimation or location measurement, whether location measurement is preferred but location estimation is also enabled, or whether location estimation is preferred but location measurement is also enabled.

[0158]

[0169] Location estimation shall not be applicable to RLD, since the (precise) location of the reference device needs to be known and only location measurements have to be reported. The reference device location and the reference device measurements shall be independent, i.e. the reference device measurements shall not be used to determine the location of the reference device. An additional entry in 'LocationInformationType' can avoid mixing 'Location Measurements' and 'Location Estimation', which are used for normal UE positioning and would be applicable only to RLD. This IE may have the name 'referenceMeasurementsRequired'.

[0159]

[0170] 12 illustrates an example RLD positioning operation 1200 with RLD registration using supplementary services, according to an aspect of the disclosure. In this solution, the RLD 710 registers with the LMF 270 using a new supplementary service message pair. The LMF 270 and the RLD 710 can then exchange LPP messages via the serving AMF 264. This solution can avoid any impact to the AMF 264 and the gNB (e.g., gNB 222), and can also avoid any impact to the LPP.

[0160]

[0171] In stage 1205, the RLD 710 performs a service request triggered by the UE via the NG-RAN node 1202 to establish a signaling connection with the AMF 264.

[0161]

[0172] In step 1210, the RLD 710 sends a supplementary service (SS) LCS Reference Location Device Registration Request message in an uplink NAS transport message to the serving AMF 264. The RLD 710 sets the payload container type to "Location Service Message Container" and includes a "Routing Identifier" in the "Additional Information" IE. The routing identifier in the uplink NAS transport message may be preconfigured in the RLD 710 to indicate a specific LMF 270. The LCS Reference Location Device Registration Request message includes the location of the RLD 710 (latitude, longitude, altitude along with uncertainty geometry) and other RLD capabilities, such as whether the device is fixed or mobile, battery-powered or mains-powered. Alternatively, this information may also be provided in an LPP PDU embedded in the LCS Reference Location Device Registration Request message. However, providing this information as part of the SS LCS Reference Location Device Registration Request message and specified in the SS means that no LPP changes may be required. The RLD 710 and LMF 270 can assume that all LPP messages exchanged during step 1240 relate to the reference location of the RLD 710 .

[0162]

[0173] In step 1215, the AMF 264 determines the LMF 270 from the routing identifier received in the additional information IE of the uplink NAS transport message in step 1210 and forwards the LCS reference location device registration request message to the LMF 270 by triggering a Namf_Communication_N1MessageNotify service operation toward the LMF 270. The AMF 264 also includes the payload container type and the LCS correlation identifier set to the routing identifier received in step 1210. The AMF 264 includes the SUPI of the RLD 710 or the PEI of the RLD in the N1MessageNotification. The LMF 270 stores the serving AMF ID included in the N1 message container for later use in step 1240. The LMF 270 also maintains a database of RLDs 710. Each RLD 710 is associated with an LCS correlation ID and the AMF ID of the AMF instance serving the RLD 710.

[0163]

[0174] In stage 1220, the LMF 270 may verify whether the RLD 710 is authorized from the SUPI or authorized from the PEI to act as a reference device in the network. The SUPI or PEI of the authorized RLD 710 in the LMF 270 may be pre-configured.

[0164]

[0175] In step 1225, the LMF 270 returns a supplementary service acknowledgement message to the RLD 710 via triggering a Namf_Communication_N1N2MessageTransfer service operation to the serving AMF 264. The acknowledgement indicates to the RLD 710 that it has successfully registered with the LMF 270. The LMF 270 also assigns and includes an LCS correlation identifier that identifies the LMF 270.

[0165]

[0176] In step 1230, upon receiving an acknowledgement message from the LMF 270, the AMF 264 sets the payload container type in the downlink NAS transport to "Location Service Message Container" and includes the LCS correlation ID in the "Additional Information" IE.

[0166]

[0177] At a later time in stage 1235, the LMF 270 may determine that location measurements are required from an RLD 710 previously registered at the LMF 270 and may trigger an LPP and / or NRPPa session with the RLD 710 or the NG-RAN serving the RLD 710 in stages 1240a and 1240b (collectively stage 1240), respectively.

[0167]

[0178] The procedures in steps 1240a and 1240b may then be performed as steps 965a and 965b in the solution shown in Figure 9 with the following modifications: First, an LCS correlation identifier is assigned by the LMF 270 that indicates the LMF 270 and the positioning session for use in step 1005 of Figure 10. The LCS correlation identifier is used in steps 1005, 1015, 1030, and 1035 in procedure 1000 of Figure 10 to ensure that, during a positioning session between the LMF 270 and the RLD 710, the positioning response message from the RLD 710 is returned by the AMF 264 to the correct LMF 270 and carries an indication (LCS correlation identifier) ​​that can be recognized by the LMF 270. Second, to enable the AMF 264 to distinguish between an LCS correlation identifier assigned by the AMF 264 and an LCS correlation identifier assigned by the LMF 270 (used in this procedure), the two types of LCS correlation identifiers may be selected from different ranges.

[0168]

[0179] In stage 1245, the LMF 270 determines correction terms from the received RLD measurements using the known location of the RLD 710. The LMF 270 stores the correction terms and uses them to correct location measurements from other UEs (e.g., UE 204).

[0169]

[0180] The LMF 270 repeats step 1240 whenever a new RLD measurement is needed. If the RLD 710 moves to a new AMF 264, the RLD 710 may repeat the registration in step 1210.

[0170]

[0181] Next, we refer to a scenario in which the RLD operates as part of the gNB from the perspective of the LMF. If the RLD can be considered part of the gNB from the perspective of the LMF (e.g., part of the gNB-DU, TRP), the RLD registration procedure shown in step 610 of Figure 6 is not strictly necessary. "RLD registration" may be performed by the deployment / operator, similar to providing NB information to the LMF (typically via some operation and maintenance function). The RLD may be part of the regular gNB / TRP database in the LMF, sometimes referred to as the "base station almanac." Specific RLD information may be requested by the LMF using the TRP information exchange procedure for the regular gNB / TRP.

[0171]

[0182] In one aspect, the RLD may be defined as an eTRP, which may be part of the gNB-DU or may be separate, as shown in Figure 7. The eTRP essentially has inverse functions compared to the regular TRP: it transmits the UL-PRS (whereas the regular TRP transmits the DL-PRS) and receives the DL-PRS (whereas the regular TRP receives the UL-PRS). One benefit of this solution is that a UE-independent NRPPa procedure may be used, which may avoid RLD registration as described above.

[0172]

[0183] LPP may also be used if the RLD is part of the gNB, since LPP provides all the functionality for positioning capability transfer, assistance data delivery, and location information transfer. LPP PDUs may be transported within NRPPa message containers. NRPPa will then enable the gNB-CU to perform message routing according to the signaling principles between the gNB and the LMF. However, the payload of the actual positioning message may be an LPP PDU, as shown in Figure 13. In particular, Figure 13 is a diagram 1300 illustrating an example F1 protocol stack for supporting LPP for eTRP. Note that in Figure 13, the acronym "SCTP" stands for "Stream Control Transmission Protocol."

[0173]

[0184] 14 illustrates an example RLD positioning operation 1400 for a scenario in which the RLD operates as part of a gNB, according to an aspect of the present disclosure. The RLD positioning operation 1400 includes RLD capability exchange over an LPP, delivery of assistance data, and transfer of location information.

[0174]

[0185] In stage 1405, the LMF 270 invokes a Namf_Communication_NonUeN2MessageTransfer service operation towards the AMF 264 to request the transfer of an NRPPa PDU to the NG-RAN node (gNB-CU 226). The NRPPa message includes an embedded LPP PDU. The LPP PDU may request location information from the RLD 720, provide assistance data to the RLD 720, or inquire about the capabilities of the RLD 720. The service operation includes the identity of the target NG-RAN node.

[0175]

[0186] In step 1410, the AMF 264 forwards the NRPPa PDU (including the embedded LPP PDU) to the gNB-CU 226 identified in the NGAP downlink UE-unrelated NRPPa transport message and includes a routing ID identifying the LMF 270.

[0176]

[0187] In step 1415, the gNB-CU226 extracts the LPP PDU from the received NRPPa message and forwards the LPP PDU to the eTRP720 identified in the F1AP downlink transport container.

[0177]

[0188] The target eTRP(RLD) 720 extracts the LPP PDU and decodes the LPP message in stage 1420. If the LPP message is of type location information request, the eTRP(RLD) 720 obtains the requested location measurements (e.g., RSTD, RSRP, Rx-Tx time difference measurements).

[0178]

[0189] In step 1425, the target eTRP (RLD) 720 returns the location information obtained in step 1420 to the gNB-CU 226 in an F1AP uplink transport container. The F1AP uplink transport container includes an LPP PDU.

[0179]

[0190] At stage 1430, the target gNB-CU 226 extracts the LPP PDU from the F1AP message and includes the LPP PDU in an NRPPa message. The gNB-CU 226 then provides the NRPPa PDU (including the LPP PDU) to the AMF 264 in an NGAP uplink UE-unassociated NRPPa transport message. The gNB-CU 226 also includes a routing identifier in the NGAP uplink UE-unassociated NRPPa transport message received at stage 1410.

[0180]

[0191] In stage 1435, the AMF 264 invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF 270 indicated by the routing identifier received in stage 1430. The service operation includes the NRPPa PDU with the embedded LPP PDU received in stage 1430 in an N2 information container.

[0181]

[0192] In step 1440, the LMF 270 determines correction terms from the received RLD measurements using the known location of the RLD 720. The LMF 270 stores the correction terms and uses them to correct location measurements from other UEs.

[0182]

[0193] The LMF repeats steps 1405 to 1435 whenever measurements of a new reference device are required. This solution has minimal impact on current positioning procedures and signaling. An additional impact would be to define new NRPPa and F1AP messages that can carry embedded LPP PDU containers.

[0183]

[0194] For transmission of UL-PRS (SRS), the current NRPPa and F1AP procedures may still be reused, however, due to the PDU transport between the LMF 270 and the gNB 222, the corresponding messages will also be non-UE related, similar to Figure 14.

[0184]

[0195] FIG. 15 illustrates an example RLD SRS configuration procedure 1500 for requesting SRS configuration / SRS transmission from an eTRP RLD to support uplink positioning reference measurements according to an aspect of the present disclosure. In this aspect, the eTRP RLD is configured to transmit a UL-PRS (e.g., an SRS) to enable the gNB-DU / TRP to measure the eTRP RLD UL-PRS and report the associated measurements to a location server as part of a standard uplink positioning procedure. Thus, uplink positioning measurements of a standard UL positioning procedure (e.g., UL-AoA, RTOA, gNB Rx-Tx time difference measurements) are performed by the gNB / TRP using the UL-PRS transmitted by the eTRP RLD at a known location. These uplink measurements can then be compared to measurements that would be expected at the gNB / TRP location from the eTRP RLD at a known RLD location to determine correction terms for nearby UEs.

[0185]

[0196] In stage 1505, the LMF 270 invokes the Namf_Communication_NonUeN2MessageTransfer service operation towards the AMF 264 to request the transfer of an NRPPa PDU. The NRPPa PDU contains a Positioning Information Request message to request SRS configuration information from the eTRP(RLD) 720. The message may include requested UL-SRS transmission characteristics that provide recommended SRS configuration parameters for the eTRP(RLD) 720. The service operation includes the identity of the target NG-RAN node.

[0186]

[0197] In step 1510, the AMF 264 forwards the NRPPa PDU to the gNB-CU 226 identified in the NGAP downlink UE-unrelated NRPPa transport message and includes a routing ID identifying the LMF 270.

[0187]

[0198] In step 1515, because the NRPPa PDU is received by the gNB-CU 226 in an NRPPa transport message that is not associated with a UE, the gNB-CU 226 understands that the NRPPa positioning information request message is not intended for a normal UE, but for the target eTRP / RLD 720. The NRPPa positioning information request message includes the eTRP ID for the target eTRP / RLD 720. The gNB-CU 226 sends an F1AP positioning information request message to the eTRP / RLD 720 (as indicated in the NRPPa message received in step 1510) to indicate to the eTRP / RLD 720 the need to transmit SRS and to retrieve the SRS configuration from the eTRP / RLD 720.

[0188]

[0199] In step 1520, the eTRP / RLD 720 takes into account the requested SRS transmission characteristic information included in the F1AP positioning information request message when determining the SRS configuration. If the requested SRS transmission characteristic indicates periodic SRS, the eTRP / RLD 720 begins transmitting the SRS. Otherwise (e.g., in the case of semi-persistent SRS), the eTRP / RLD 720 waits until an F1AP positioning activation request message is received, with the transmission of the SRS using the same general procedure as in FIG. 15 , except that the NRPPa PDU in steps 1505 and 1510 includes an NRPPa positioning activation request message to request activation of the SRS, which is provided to the eTRP / RLD as an F1AP positioning activation request message in step 1515.

[0189]

[0200] In stage 1525, the target eTRP (RLD) 720 returns an F1AP positioning information response message including the SRS configuration information configured in the gNB-CU 226.

[0190]

[0201] In step 1530, the target gNB-CU 226 encodes the information received in step 1525 into an NRPPa Positioning Information Response message and provides an NRPPa PDU (including the NRPPa Positioning Information Response message) in an NGAP uplink UE-non-associated NRPPa transport message to the AMF 264. The gNB-CU 226 also includes a routing identifier in the NGAP uplink UE-non-associated NRPPa transport message received in step 1510.

[0191]

[0202] At stage 1535, the AMF 264 invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF 270 indicated by the routing identifier received at stage 1530. The service operation includes the NRPPa PDU with the NRPPa positioning information response message received at stage 1530 in an N2 information container.

[0192]

[0203] The same procedure as above can be used for other NRPPa / F1AP messages, such as positioning activation request / response, to semi-persistently activate or trigger aperiodic SRS transmissions by the eTRP / RLD 720. Thus, if the RLD is considered to be part of the gNB (gNB-DU / eTRP), the current NRPPa and F1AP positioning messages can be reused for the RLD. Instead of using UE-related transport procedures for these messages, a UE-independent transport mechanism would be used in this solution, which requires only minor modifications of the NRPPa / F1AP messages to include the identity of the target gNB-DU / eTRP 720. Thus, a dedicated RLD registration procedure, as described above, would not be necessary, since the target gNB-DU / eTRP identity can be provided to the LMF 270 as part of the base station almanac.

[0193]

[0204] 16 illustrates an example method 1600 of communication according to an aspect of the present disclosure. In one aspect, the method 1600 may be performed by a location server (e.g., LMF 270).

[0194]

[0205] At 1610, the location server receives a registration request from a network entity (e.g., AMF 264) serving the reference device (e.g., RLD 710), as in stages 920 and 1215, for the reference device to operate as an RLD. In one aspect, the registration request includes one or more parameters that enable the location server to communicate with the reference device via a positioning protocol (e.g., LPP). In one aspect, operation 1610 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0195]

[0206] At 1620, the location server initiates a positioning procedure with the reference device via a positioning protocol based on one or more parameters, as in steps 965a and 1240a. In one aspect, operation 1620 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0196]

[0207] At 1630, the location server receives one or more reference positioning measurements from a reference device during a positioning procedure via a positioning protocol, as in stages 965a and 1240a. In one aspect, operation 1630 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0197]

[0208] At 1640, the location server determines one or more correction terms for positioning one or more UEs (e.g., UE 204) based at least in part on the location of the reference device and the one or more reference positioning measurements, as in stages 970 and 1245. In one aspect, operation 1640 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0198]

[0209] 17 illustrates an example method 1700 of communication according to an aspect of the disclosure. In one aspect, the method 1700 may be performed by a reference device (e.g., the RLD 710).

[0199]

[0210] At 1710, the reference device transmits a registration request to a network entity (e.g., AMF 264) requesting that the reference device operate as an RLD, as in stages 905 and 1210. In one aspect, the registration request includes one or more parameters indicating the reference device's ability to operate as an RLD. In one aspect, operation 1710 may be performed by at least one WWAN transceiver 310, at least one processor 332, a memory component 340, and / or a positioning component 342, any or all of which may be considered a means for performing this operation.

[0200]

[0211] At 1720, the reference device receives a request to perform one or more reference positioning measurements from a location server via a positioning protocol (e.g., LPP), as in stages 965a and 1240a. In one aspect, operation 1720 may be performed by at least one WWAN transceiver 310, at least one processor 332, a memory component 340, and / or a positioning component 342, any or all of which may be considered means for performing this operation.

[0201]

[0212] At 1730, the reference device performs one or more reference positioning measurements based on receipt of the request, as in stages 965a and 1240a. In one aspect, operation 1730 may be performed by at least one WWAN transceiver 310, at least one processor 332, memory component 340, and / or positioning component 342, any or all of which may be considered a means for performing this operation.

[0202]

[0213] At 1740, the reference device transmits one or more reference positioning measurements to the location server via a positioning protocol, as in steps 965a and 1240a. In one aspect, operation 1740 may be performed by at least one WWAN transceiver 310, at least one processor 332, a memory component 340, and / or a positioning component 342, any or all of which may be considered a means for performing this operation.

[0203]

[0214] 18 illustrates an example method 1800 of communication according to an aspect of the disclosure. In one aspect, the method 1800 may be performed by a location server (e.g., the LMF 270).

[0204]

[0215] At 1810, the location server sends a request to a network entity (e.g., AMF 264) to forward one or more first NRPPa messages to a RAN node (e.g., gNB 222, gNB-CU 226, gNB-DU 228), as in stages 1405 and 1505. In one aspect, the one or more first NRPPa messages include one or more first LPP messages, the one or more first LPP messages including a location information request for one or more reference positioning measurements from an RLD (e.g., RLD 720) at the RAN node. In one aspect, operation 1810 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0205]

[0216] At 1820, the location server receives one or more second NRPPa messages from the RAN node from a network entity, as in stages 1435 and 1535. In one aspect, the one or more second NRPPa messages include one or more second LPP messages, the one or more second LPP messages including at least one or more reference positioning measurements. In one aspect, operation 1820 may be performed by at least one network interface 390, at least one processor 394, memory component 396, and / or positioning component 398, any or all of which may be considered a means for performing this operation.

[0206]

[0217] At 1830, the location server determines one or more correction terms for positioning one or more UEs based at least in part on the locations of the RLDs and the one or more reference positioning measurements, as in stage 1440. In one aspect, operation 1830 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0207]

[0218] 19 illustrates an example method 1900 of communication according to an aspect of the present disclosure. In one aspect, the method 1900 may be performed by a location server (e.g., the LMF 270).

[0208]

[0219] At 1910, the location server sends a request to a network entity to forward one or more first NRPPa messages to the RAN node, the one or more first NRPPa messages including a request for the RAN node to provide an SRS configuration for transmission of the SRS by an RLD at the RAN node. In an aspect, operation 1910 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0209]

[0220] At 1920, the location server receives, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including an SRS configuration defining an SRS to be transmitted by an RLD in the RAN node. In an aspect, operation 1920 may be performed by at least one network interface 390, at least one processor 394, a memory component 396, and / or a positioning component 398, any or all of which may be considered a means for performing this operation.

[0210]

[0221] As will be appreciated, a technical advantage of methods 1600 through 1900 is that they enable signaling between a location server (e.g., LMF 270) and an RLD (e.g., RLD 710, 720), thereby utilizing the use of the RLD to enable obtaining reference measurements to correct the UE's positioning measurements, thereby improving positioning performance.

[0211]

[0222] In the above detailed description, it can be seen that different features are grouped together in examples. This mode of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly set forth in each clause. Rather, various embodiments of the present disclosure may include fewer than all features of each disclosed exemplary clause. Accordingly, the following clauses should be considered incorporated herein, with each clause standing as a separate example by itself. While each dependent clause may refer to a specific combination with one of the other clauses in the clause, the aspect(s) of that dependent clause are not limited to that specific combination. It will be appreciated that other exemplary clauses may also include combinations of the dependent clause(s) aspect(s) with the subject matter of any other dependent clause or independent clause, or any combination of features with other dependent and independent clauses. The various embodiments disclosed herein expressly include combinations of specific combinations (e.g., inconsistent aspects, such as defining an element as both an insulator and a conductor) unless these combinations are expressly expressed or can be readily inferred to be unintended. Furthermore, it is also contemplated that aspects of a clause may be included in any other independent clause, even if that clause is not directly dependent on that independent clause.

[0212]

[0223] Example implementations are described in the numbered clauses below.

[0213]

[0224] Clause 1. A method of communication implemented by a location server, comprising: receiving a registration request from a network entity serving a reference device, the registration request requesting that the reference device act as a reference location device (RLD); the registration request including one or more parameters that enable the location server to communicate with the reference device via the positioning protocol; initiating a positioning procedure with the reference device via a positioning protocol based on the one or more parameters; receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; and determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements.

[0214]

[0225] Clause 2. The method of clause 1, wherein the one or more parameters include an identifier of the reference device, an identifier of a network entity, an identifier of a serving cell of the reference device, a Location Services (LCS) correlation identifier, a Subscription Persistent Identifier (SUPI) of the reference device, a Persistent Equipment Identifier (PEI) of the reference device, or any combination thereof.

[0215]

[0226] Clause 3. The method of clause 2, wherein the LCS correlation identifier is set to a routing identifier associated with the location server.

[0216]

[0227] Clause 4. The method of any of clauses 1 to 3, wherein the registration request further includes one or more parameters indicating the capability of the reference device to act as an RLD.

[0217]

[0228] Clause 5. The method of clause 4, wherein the one or more parameters indicative of the reference device's ability to operate as an RLD include the location of the reference device, the location uncertainty, the location source for the location, the velocity of the reference device, whether the reference device is in a fixed or mobile operating state, whether the reference device is battery powered or mains operated, or any combination thereof.

[0218]

[0229] Clause 6. The method of any of clauses 4 to 5, wherein the one or more parameters indicating the capability of the reference device to operate as an RLD comprise a flag (e.g., a 1-bit field) indicating whether the reference device is capable of operating as an RLD.

[0219]

[0230] Clause 7. The method of any of clauses 1 to 6, further comprising registering the reference device as an RLD by storing an LCS correlation identifier and an identifier of the network entity.

[0220]

[0231] Clause 8. The method of any of clauses 1 to 7, further comprising sending a registration response to the network entity, the registration response indicating whether the reference device was successfully registered as an RLD.

[0221]

[0232] Clause 9. The method of any of clauses 1 to 8, wherein the location server initiates a positioning procedure with a reference device based on a determination that one or more reference positioning measurements are required to position one or more UEs.

[0222]

[0233] Clause 10. The method of any of clauses 1 to 9, further comprising applying one or more correction terms to positioning measurements received from one or more UEs.

[0223]

[0234] Clause 11. The method of any of clauses 1 to 10, wherein the reference device comprises a mobile UE, a UE dedicated to operating as an RLD, a mobile terminal (MT) of an integrated access and backhaul (IAB) node, or an MT of a smart repeater.

[0224]

[0235] Clause 12. The method of any of clauses 1 to 11, wherein the positioning protocol is the Long Term Evolution (LTE) Positioning Protocol (LPP).

[0225]

[0236] Clause 13. The method according to any one of clauses 1 to 12, wherein the location server is a Location Management Function (LMF) and the network entity is an Access and Mobility Management Function (AMF).

[0226]

[0237] Clause 14. A method of communication performed by a reference device, the method comprising: sending to a network entity a registration request for the reference device to act as a Reference Location Device (RLD), the registration request including one or more parameters indicative of the reference device's ability to act as an RLD; receiving a request to perform one or more reference positioning measurements from a location server via a positioning protocol; performing one or more reference positioning measurements based on receiving the request; and transmitting the one or more reference positioning measurements to the location server via the positioning protocol.

[0227]

[0238] Clause 15. The method of clause 14, wherein the one or more parameters indicative of the capability of the reference device to operate as an RLD include the location of the reference device, the location uncertainty, the location source for the location, the velocity of the reference device, whether the reference device is in a fixed or mobile operating state, whether the reference device is battery powered or mains operated, or any combination thereof.

[0228]

[0239] Clause 16. The method of any of clauses 14 to 15, wherein the one or more parameters indicative of the capability of the reference device to act as an RLD comprise a flag indicating whether the reference device is capable of acting as an RLD.

[0229]

[0240] Clause 17. The method of any of clauses 14 to 16, wherein the registration request is included in a Radio Resource Control (RRC) Setup Complete message.

[0230]

[0241] Clause 18. The method of any of clauses 14 to 16, wherein the registration request is included in a Non-Access Stratum (NAS) uplink transport message.

[0231]

[0242] Clause 19. The method of clause 18, wherein the registration request comprises a supplementary service LCS reference device registration request.

[0232]

[0243] Clause 20. The method of any of clauses 14 to 19, further comprising receiving a registration response from the location server, the registration response indicating whether the reference device has been successfully registered as an RLD.

[0233]

[0244] Clause 21. The method of any of clauses 14 to 20, wherein the reference device comprises a mobile UE, a UE dedicated to operating as an RLD, a mobile terminal (MT) of an integrated access and backhaul (IAB) node, or an MT of a smart repeater.

[0234]

[0245] Clause 22. The method of any of clauses 14 to 21, wherein the positioning protocol is the Long Term Evolution (LTE) Positioning Protocol (LPP).

[0235]

[0246] Clause 23. The method according to any of clauses 14 to 22, wherein the location server is a Location Management Function (LMF) and the network entity is an Access and Mobility Management Function (AMF).

[0236]

[0247] Clause 24. A method of communication implemented by a location server, comprising: sending a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages including location information requests for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; receiving from the network entity one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least one or more reference positioning measurements; and determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements.

[0237]

[0248] Clause 25. The method of clause 24, wherein the one or more first NRPPa messages comprise one or more first NRPPa protocol data units (PDUs), the one or more second NRPPa messages comprise one or more second NRPPa PDUs, the one or more first LPP messages comprise one or more first LPP PDUs, and the one or more second LPP messages comprise one or more second LPP PDUs.

[0238]

[0249] Clause 26. The method of any of clauses 24 to 25, wherein the one or more first NRPPa messages and the one or more second NRPPa messages are part of an NRPPa transport procedure that is not associated with the UE.

[0239]

[0250] Clause 27. The method of any of clauses 24 to 26, wherein the RLD is an enhanced transmitting / receiving point (eTRP), the eTRP transmitting a sounding reference signal (SRS) and receiving a positioning reference signal (PRS).

[0240]

[0251] Clause 28. The method of any of clauses 24 to 27, wherein the one or more first LPP messages include a location information request, assistance data for the RLD, a query for RLD capabilities of the RLD, a request for SRS configuration for the RLD, or any combination thereof.

[0241]

[0252] Clause 29. The method of any of clauses 24 to 28, wherein the location server sends a request to the network entity based on the RAN node being registered with the location server as an RLD.

[0242]

[0253] Clause 30. The method of any of clauses 24 to 29, further comprising applying one or more correction terms to positioning measurements received from one or more UEs.

[0243]

[0254] Clause 31. The method of any of clauses 24 to 30, wherein the RLD comprises a new Radio Node B (gNB), a gNB Central Unit (gNB-CU), a gNB Distributed Unit (gNB-DU), or an eTRP.

[0244]

[0255] Clause 32. The method according to any of clauses 24 to 31, wherein the location server is a Location Management Function (LMF) and the network entity is an Access and Mobility Management Function (AMF).

[0245]

[0256] Clause 33. A method of communication implemented by a location server, comprising: sending to a network entity a request to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) in the RAN node; and receiving from the network entity one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including an SRS configuration defining an SRS to be transmitted by the RLD in the RAN node.

[0246]

[0257] Clause 34. The method of clause 33, further comprising instigating an uplink positioning procedure with one or more RAN nodes not acting as RLDs, wherein the one or more RAN nodes measure SRS from the RLDs at the RAN nodes to determine the uplink positioning measurements.

[0247]

[0258] Clause 35. The method of clause 34, further comprising determining one or more correction terms for positioning one or more UEs based at least in part on the locations of one or more RAN nodes and one or more uplink positioning measurements.

[0248]

[0259] Clause 36. The method of any of clauses 33 to 35, wherein the one or more first NRPPa messages and the one or more second NRPPa messages are part of an NRPPa transport procedure that is not associated with the UE.

[0249]

[0260] Clause 37. The method of any of clauses 33 to 36, wherein the RLD comprises a new Radio Node B (gNB), a gNB Central Unit (gNB-CU), a gNB Distributed Unit (gNB-DU), or an enhanced Transmission / Reception Point (eTRP).

[0250]

[0261] Clause 38. The method according to any of clauses 33 to 37, wherein the location server is a Location Management Function (LMF) and the network entity is an Access and Mobility Management Function (AMF).

[0251]

[0262] Clause 39. An apparatus comprising: a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, wherein the memory, the communication interface, and the at least one processor are configured to perform a method according to any one of clauses 1 to 38.

[0252]

[0263] Clause 40. Apparatus comprising means for carrying out the method according to any of clauses 1 to 38.

[0253]

[0264] Clause 41. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable comprising at least one instruction for causing a computer or processor to perform a method according to any of clauses 1 to 38.

[0254]

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

[0255]

[0266] Furthermore, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0256]

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

[0257]

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

[0258]

[0269] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy discs, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0259]

[0270] While the above disclosure sets forth exemplary embodiments of the present disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and / or actions of the method claims in accordance with the embodiments of the present disclosure described herein need not be performed in any particular order. Furthermore, although elements of the present disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. The inventions described in the claims of the present application as originally filed are set forth below. [C1] 1. A method of communication implemented by a location server, comprising: receiving a registration request from a network entity serving a reference device for the reference device to operate as a Reference Location Device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; initiating a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements; A method comprising: [C2] The one or more parameters are: an identifier of the reference device; an identifier of the network entity; an identifier of a serving cell of the reference device; Location Services (LCS) correlation identifier, a Subscription Persistent Identifier (SUPI) of said reference device; the Persistent Equipment Identifier (PEI) of said reference device; or any combination thereof, The method according to C1, comprising: [C3] The method of C2, wherein the LCS correlation identifier is set to a routing identifier associated with the location server. [C4] The method of C1, wherein the registration request further includes one or more parameters indicating an ability of the reference device to act as the RLD. [C5] The one or more parameters indicative of the capability of the reference device to operate as the RLD are: the location of the reference device; the location uncertainty; a location source for said location; the velocity of the reference device; whether the reference device is in a fixed or mobile state; whether the reference device is battery-powered or mains-powered; or any combination thereof, The method according to C4, comprising: [C6] The method of C4, wherein the one or more parameters indicative of the capability of the reference device to act as the RLD comprise a flag indicating whether the reference device is capable of acting as the RLD. [C7] registering the reference device as the RLD by storing an LCS correlation identifier and an identifier of the network entity; The method of C1, further comprising: [C8] sending a registration response to the network entity, the registration response indicating whether the reference device was successfully registered as the RLD; The method of C1, further comprising: [C9] The method of C1, wherein the location server initiates the positioning procedure with the reference device based on a determination that the one or more reference positioning measurements are required to position the one or more UEs. [C10] applying the one or more correction terms to positioning measurements received from the one or more UEs; The method of C1, further comprising: [C11] The reference device is Mobile UE, a UE dedicated to operating as the RLD; Mobile Terminal (MT) in an Integrated Access and Backhaul (IAB) node, or Smart repeater MT, The method of claim C1, comprising: [C12] The method of C1, wherein the positioning protocol is a Long Term Evolution (LTE) Positioning Protocol (LPP). [C13] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); The method described in C1. [C14] 1. A method of communication implemented by a reference device, comprising: sending a registration request to a network entity requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters indicating an ability of the reference device to operate as the RLD; receiving a request from a location server via a positioning protocol to perform one or more reference positioning measurements; performing the one or more reference positioning measurements based on receiving the request; and transmitting the one or more reference positioning measurements to the location server via the positioning protocol; A method comprising: [C15] The one or more parameters indicative of the capability of the reference device to operate as the RLD are: the location of the reference device; the location uncertainty; a location source for said location; the velocity of the reference device; whether the reference device is in a fixed or mobile state; whether the reference device is battery-powered or mains-powered; or any combination thereof, The method according to C14, comprising: [C16] The method of C14, wherein the one or more parameters indicating the capability of the reference device to operate as the RLD comprise a flag indicating whether the reference device can operate as the RLD. [C17] The method of C14, wherein the registration request is included in a radio resource control (RRC) setup complete message. [C18] The method of C14, wherein the registration request is included in a non-access stratum (NAS) uplink transport message. [C19] The method of C18, wherein the registration request comprises a supplementary service LCS reference device registration request. [C20] receiving a registration response from the location server, the registration response indicating whether the reference device was successfully registered as the RLD; The method of C14, further comprising: [C21] The reference device is Mobile UE, a UE dedicated to operating as the RLD; Mobile Terminal (MT) in an Integrated Access and Backhaul (IAB) node, or Smart Repeater MT The method of claim C14, comprising: [C22] The method of claim 14, wherein the positioning protocol is a Long Term Evolution (LTE) Positioning Protocol (LPP). [C23] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); The method described in C14. [C24] 1. A method of communication implemented by a location server, comprising: sending, to a network entity, a request to transmit one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages comprising one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages comprising a location information request for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; receiving, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least the one or more reference positioning measurements; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements; A method comprising: [C25] the one or more first NRPPa messages comprise one or more first NRPPa protocol data units (PDUs); the one or more second NRPPa messages comprise one or more second NRPPa PDUs; the one or more first LPP messages comprise one or more first LPP PDUs; the one or more second LPP messages comprise one or more second LPP PDUs; The method described in C24. [C26] The method of C24, wherein the one or more first NRPPa messages and the one or more second NRPPa messages are part of an NRPPa transport procedure that is not associated with a UE. [C27] the RLD is an enhanced transmission / reception point (eTRP); The eTRP transmits a sounding reference signal (SRS) and receives a positioning reference signal (PRS); The method described in C24. [C28] 25. The method of claim 24, wherein the one or more LPP messages include the location information request, assistance data for the RLD, a query for RLD capability of the RLD, a request for SRS configuration for the RLD, or any combination thereof. [C29] The method of claim 24, wherein the location server sends the request to the network entity based on the RAN node being registered on the location server as the RLD. [C30] applying the one or more correction terms to positioning measurements received from the one or more UEs; The method of C24, further comprising: [C31] The RLD is New Wireless Node B (gNB), gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), or eTRP, The method of claim C24, comprising: [C32] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); The method described in C24. [C33] 1. A method of communication implemented by a location server, comprising: sending, to a network entity, a request to transmit one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) at the RAN node; receiving, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including the SRS configuration defining the SRS to be transmitted by the RLD in the RAN node; A method comprising: [C34] initiating an uplink positioning procedure with one or more RAN nodes not acting as RLDs, wherein the one or more RAN nodes measure the SRS from the RLDs at the RAN nodes to determine uplink positioning measurements; The method of C33, further comprising: [C35] determining one or more correction terms for positioning one or more UEs based at least in part on the locations of the one or more RAN nodes and the one or more uplink positioning measurements; The method of C34, further comprising: [C36] The method of C33, wherein the one or more first NRPPa messages and the one or more second NRPPa messages are part of an NRPPa transport procedure that is not associated with a UE. [C37] The RLD is New Wireless Node B (gNB), gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), or Enhanced Transmission / Reception Point (eTRP), The method of C33, comprising: [C38] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); The method described in C33. [C39] a location server, Memory and a communication interface; at least one processor communicatively coupled to the memory and the communication interface; wherein the at least one processor: receiving, via the communication interface, a registration request from a network entity serving a reference device for the reference device to operate as a reference location device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; initiating a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receiving, via the communication interface, one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements; a location server configured to: [C40] The one or more parameters are: an identifier of the reference device; an identifier of the network entity; an identifier of a serving cell of the reference device; Location Services (LCS) correlation identifier, a Subscription Persistent Identifier (SUPI) of said reference device; the Persistent Equipment Identifier (PEI) of said reference device; or any combination thereof, 3. The location server of claim 2, further comprising: [C41] The location server of C40, wherein the LCS correlation identifier is set to a routing identifier associated with the location server. [C42] The location server of C39, wherein the registration request further includes one or more parameters indicating an ability of the reference device to act as the RLD. [C43] The one or more parameters indicative of the capability of the reference device to operate as the RLD are: the location of the reference device; the location uncertainty; a location source for said location; the velocity of the reference device; whether the reference device is in a fixed or mobile state; whether the reference device is battery-powered or mains-powered; or any combination thereof, 4. The location server of claim 3, further comprising: [C44] 43. The location server of claim 42, wherein the one or more parameters indicating the capability of the reference device to act as the RLD comprise a flag indicating whether the reference device is capable of acting as the RLD. [C45] The at least one processor: registering the reference device as the RLD by storing an LCS correlation identifier and an identifier of the network entity; 30. The location server of claim 29, further configured to: [C46] The at least one processor: causing the communication interface to send a registration response to the network entity, the registration response indicating whether the reference device was successfully registered as the RLD; 30. The location server of claim 29, further configured to: [C47] The location server of C39, wherein the location server triggers the positioning procedure with the reference device based on a determination that the one or more reference positioning measurements are required to position the one or more UEs. [C48] The at least one processor: applying the one or more correction terms to positioning measurements received from the one or more UEs. 30. The location server of claim 29, further configured to: [C49] The reference device is Mobile UE, a UE dedicated to operating as the RLD; Mobile Terminal (MT) in an Integrated Access and Backhaul (IAB) node, or Smart Repeater MT 30. The location server of claim 29, comprising: [C50] The location server of C39, wherein the positioning protocol is a Long Term Evolution (LTE) Positioning Protocol (LPP). [C51] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); A location server as described in C39. [C52] a reference device, Memory and a communication interface; at least one processor communicatively coupled to the memory and the communication interface; wherein the at least one processor: causing the communication interface to send to a network entity a registration request for the reference device to operate as a reference location device (RLD), the registration request including one or more parameters indicating an ability of the reference device to operate as the RLD; receiving, via the communication interface, a request from a location server via a positioning protocol to perform one or more reference positioning measurements; performing the one or more reference positioning measurements based on receiving the request; and causing the communication interface to transmit the one or more reference positioning measurements to the location server via the positioning protocol; a reference device configured to: [C53] The one or more parameters indicative of the capability of the reference device to operate as the RLD are: the location of the reference device; the location uncertainty; a location source for said location; the velocity of the reference device; whether the reference device is in a fixed or mobile state; whether the reference device is battery-powered or mains-powered; or any combination thereof, 5. The reference device of claim 4, comprising: [C54] 5. The reference device of claim 2, wherein the one or more parameters indicating the capability of the reference device to operate as the RLD comprise a flag indicating whether the reference device can operate as the RLD. [C55] The reference device of C52, wherein the registration request is included in a radio resource control (RRC) setup complete message. [C56] The reference device of C52, wherein the registration request is included in a Non-Access Stratum (NAS) uplink transport message. [C57] The reference device of C56, wherein the registration request comprises a supplementary service LCS reference device registration request. [C58] The at least one processor: receiving a registration response from the location server via the communication interface, the registration response indicating whether the reference device was successfully registered as the RLD; 5. The reference device of claim 2, further configured to: [C59] The reference device is Mobile UE, a UE dedicated to operating as the RLD; Mobile Terminal (MT) in an Integrated Access and Backhaul (IAB) node, or Smart repeater MT, 5. The reference device of claim 4, comprising: [C60] The reference device of C52, wherein the positioning protocol is a Long Term Evolution (LTE) Positioning Protocol (LPP). [C61] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); Reference device as described in C52. [C62] a location server, Memory and a communication interface; at least one processor communicatively coupled to the memory and the communication interface; wherein the at least one processor: causing the communications interface to send a request to a network entity to transfer one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages comprising one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages comprising a location information request for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; receiving, from the network entity via the communications interface, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least the one or more reference positioning measurements; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements; a location server configured to: [C63] the one or more first NRPPa messages comprise one or more first NRPPa protocol data units (PDUs); the one or more second NRPPa messages comprise one or more second NRPPa PDUs; the one or more first LPP messages comprise one or more first LPP PDUs; the one or more second LPP messages comprise one or more second LPP PDUs; The location server according to C62. [C64] The location server of C62, wherein the one or more first NRPPa messages and the one or more second NRPPa messages are part of an NRPPa transport procedure that is not related to the UE. [C65] the RLD is an enhanced transmission / reception point (eTRP); The eTRP transmits a sounding reference signal (SRS) and receives a positioning reference signal (PRS); The location server according to C62. [C66] The location server of C62, wherein the one or more first LPP messages include the location information request, assistance data for the RLD, a query for RLD capabilities of the RLD, a request for SRS configuration for the RLD, or any combination thereof. [C67] The location server of C62, wherein the location server sends the request to the network entity based on the RAN node being registered with the location server as the RLD. [C68] The at least one processor: applying the one or more correction terms to positioning measurements received from the one or more UEs; The location server according to C62, further configured to: [C69] The RLD is New Wireless Node B (gNB), gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), or eTRP, The location server according to C62, comprising: [C70] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); The location server according to C62. [C71] a location server, Memory and a communication interface; at least one processor communicatively coupled to the memory and the communication interface; wherein the at least one processor: causing the communications interface to send a request to a network entity to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) at the RAN node; receiving, from the network entity via the communication interface, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including the SRS configuration defining the SRS to be transmitted by the RLD in the RAN node; a location server configured to: [C72] The at least one processor: initiating an uplink positioning procedure with one or more RAN nodes not acting as RLDs, wherein the one or more RAN nodes measure the SRS from the RLDs at the RAN nodes to determine uplink positioning measurements; The location server according to C71, further configured to: [C73] The at least one processor: determining one or more correction terms for positioning one or more UEs based at least in part on the locations of the one or more RAN nodes and the one or more uplink positioning measurements; The location server of C72, further configured to: [C74] The location server of C71, wherein the one or more first NRPPa messages and the one or more second NRPPa messages are part of an NRPPa transport procedure that is not related to the UE. [C75] The RLD is New Wireless Node B (gNB), gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), or Enhanced Transmission / Reception Point (eTRP) The location server according to C71, comprising: [C76] the location server is a location management function (LMF); the network entity is an Access and Mobility Management Function (AMF); The location server according to C71. [C77] a location server, means for receiving a registration request from a network entity serving a reference device, the reference device requesting that the reference device operate as a Reference Location Device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; means for initiating a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; means for receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; means for determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on a location of the reference device and the one or more reference positioning measurements; A location server comprising: [C78] a reference device, means for transmitting to a network entity a registration request for the reference device to operate as a Reference Location Device (RLD), the registration request including one or more parameters indicating an ability of the reference device to operate as the RLD; means for receiving a request to perform one or more reference positioning measurements from a location server via a positioning protocol; means for performing the one or more reference positioning measurements based on receiving the request; means for transmitting the one or more reference positioning measurements to the location server via the positioning protocol; a reference device comprising: [C79] a location server, means for sending, to a network entity, a request to transfer one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages comprising one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages comprising a location information request for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; means for receiving, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least the one or more reference positioning measurements; means for determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements; A location server comprising: [C80] a location server, means for sending, to a network entity, a request to forward one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) at the RAN node; means for receiving, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including the SRS configuration defining the SRS to be transmitted by the RLD in the RAN node; A location server comprising: [C81] A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: receiving a registration request from a network entity serving a reference device for the reference device to operate as a Reference Location Device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; triggering a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the reference device and the one or more reference positioning measurements; A non-transitory computer-readable medium for causing [C82] A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a reference device, cause the reference device to: sending a registration request to a network entity requesting that the reference device operate as a reference location device (RLD), the registration request including one or more parameters indicating an ability of the reference device to operate as the RLD; receiving a request from a location server via a positioning protocol to perform one or more reference positioning measurements; performing the one or more reference positioning measurements based on receiving the request; and transmitting the one or more reference positioning measurements to the location server via the positioning protocol; A non-transitory computer-readable medium for causing [C83] A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: sending, to a network entity, a request to transmit one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages comprising one or more first Long Term Evolution (LTE) Positioning Protocol (LPP) messages, the one or more first LPP messages comprising a location information request for one or more reference positioning measurements from a Reference Location Device (RLD) at the RAN node; receiving, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including one or more second LPP messages, the one or more second LPP messages including at least the one or more reference positioning measurements; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on the location of the RLD and the one or more reference positioning measurements; A non-transitory computer-readable medium for causing [C84] A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: sending, to a network entity, a request to transmit one or more first New Radio Positioning Protocol type A (NRPPa) messages to a Radio Access Network (RAN) node, the one or more first NRPPa messages including a request for the RAN node to provide a Sounding Reference Signal (SRS) configuration for transmission of an SRS by a Reference Location Device (RLD) at the RAN node; receiving, from the network entity, one or more second NRPPa messages from the RAN node, the one or more second NRPPa messages including the SRS configuration defining the SRS to be transmitted by the RLD in the RAN node; A non-transitory computer-readable medium for causing

Claims

1. 1. A method of communication implemented by a location server, comprising: receiving a registration request from a network entity serving a reference device for the reference device to operate as a Reference Location Device (RLD), the registration request including one or more parameters that enable the location server to communicate with the reference device via a positioning protocol; initiating a positioning procedure with the reference device via the positioning protocol based on the one or more parameters; receiving one or more reference positioning measurements from the reference device during the positioning procedure via the positioning protocol; determining one or more correction terms for positioning one or more user equipments (UEs) based at least in part on a location of the reference device and the one or more reference positioning measurements, wherein: the location server is a Location Management Function (LMF); the network entity is an Access and Mobility Management Function (AMF); A method comprising:

2. The one or more parameters are: an identifier of the reference device; an identifier of the network entity; an identifier of a serving cell of the reference device; Location Services (LCS) correlation identifier, a Subscription Persistent Identifier (SUPI) of the reference device; the Persistent Equipment Identifier (PEI) of said reference device; or any combination thereof, The method of claim 1 , comprising:

3. The method of claim 2 , wherein the LCS correlation identifier is set to a routing identifier associated with the location server.

4. The method of claim 1 , wherein the registration request further includes one or more parameters indicating an ability of the reference device to act as the RLD.

5. The one or more parameters indicative of the capability of the reference device to operate as the RLD are: the location of the reference device; the location uncertainty; a location source for said location; the velocity of the reference device; whether the reference device is in a fixed or mobile state; whether the reference device is battery-powered or mains-powered; or any combination thereof, The method of claim 4, comprising:

6. The method of claim 4 , wherein the one or more parameters indicative of the capability of the reference device to operate as the RLD comprise a flag indicating whether the reference device is capable of operating as the RLD.

7. registering the reference device as the RLD by storing an LCS correlation identifier and an identifier of the network entity; The method of claim 1 further comprising:

8. sending a registration response to the network entity, the registration response indicating whether the reference device was successfully registered as the RLD; The method of claim 1 further comprising:

9. 1. A method of communication implemented by a reference device, comprising: sending a registration request to a network entity requesting that the reference device operate as a Reference Location Device (RLD), the registration request including one or more parameters indicating an ability of the reference device to operate as the RLD; receiving a request from a location server via a positioning protocol to perform one or more reference positioning measurements; performing the one or more reference positioning measurements based on receiving the request; and transmitting the one or more reference positioning measurements to the location server via the positioning protocol; and the location server is a Location Management Function (LMF); the network entity is an Access and Mobility Management Function (AMF); A method comprising:

10. The one or more parameters indicative of the capability of the reference device to operate as the RLD are: the location of the reference device; the location uncertainty; a location source for said location; the velocity of the reference device; whether the reference device is in a fixed or mobile state; whether the reference device is battery-powered or mains-powered; or any combination thereof, 10. The method of claim 9, comprising:

11. The method of claim 9 , wherein the one or more parameters indicative of the capability of the reference device to operate as the RLD comprise a flag indicating whether the reference device is capable of operating as the RLD.

12. 10. The method of claim 9, wherein the registration request is included in a radio resource control (RRC) setup complete message.

13. 10. The method of claim 9, wherein the registration request is included in a Non-Access Stratum (NAS) uplink transport message.

14. The method of claim 13 , wherein the registration request comprises a supplementary service LCS reference device registration request.

15. receiving a registration response from the location server, the registration response indicating whether the reference device was successfully registered as the RLD; The method of claim 9 further comprising:

Images