Patent Description:
Currently the fifth generation ("<NUM>") of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases. The present disclosure relates generally to NR, but the following description of Long Term Evolution (LTE) technology is provided for context since it shares many features with NR.

LTE is an umbrella term for fourth generation (<NUM>) radio access technologies (RATs) developed within 3GPP and initially standardized in Releases <NUM> and <NUM>, also known as Evolved UTRAN (E-UTRAN). LTE is available in various frequency bands and is accompanied by improvements to non-radio aspects referred to as System Architecture Evolution (SAE), including the Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases.

An overall exemplary architecture of a network comprising LTE and SAE is shown in <FIG>. E-UTRAN <NUM> includes one or more evolved Node B's (eNB), such as eNBs <NUM>, <NUM>, and <NUM>, and one or more user equipment (UE), such as UE <NUM>. As used within the 3GPP standards, "user equipment" or "UE" means any wireless communication device (e.g., smartphone or computing device) that is capable of communicating with 3GPP-standard-compliant network equipment, including E-UTRAN as well as UTRAN and/or GERAN, as the third-generation ("<NUM>") and second-generation ("<NUM>") 3GPP RANs are commonly known.

As specified by 3GPP, E-UTRAN <NUM> is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE. These functions reside in the eNBs, such as eNBs <NUM>, <NUM>, and <NUM>. Each of the eNBs can serve a geographic coverage area including one more cells, including cells <NUM>, <NUM>, and <NUM> served by eNBs <NUM>, <NUM>, and <NUM>, respectively.

The eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in <FIG>. The eNBs also are responsible for the E-UTRAN interface to the EPC <NUM>, specifically the S1 interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs <NUM> and <NUM> in <FIG>. In general, the MME/S-GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as the local mobility anchor for the data bearers when the UE moves between eNBs, such as eNBs <NUM>, <NUM>, and <NUM>.

EPC <NUM> can also include a Home Subscriber Server (HSS) <NUM>, which manages user- and subscriber-related information. HSS <NUM> can also provide support functions in mobility management, call and session setup, user authentication and access authorization. The functions of HSS <NUM> can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations. HSS <NUM> can also communicate with MMEs <NUM> and <NUM> via respective S6a interfaces.

In some embodiments, HSS <NUM> can communicate with a user data repository (UDR) - labelled EPC-UDR <NUM> in <FIG> - via a Ud interface. EPC-UDR <NUM> can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., vendor-specific), such that encrypted credentials stored in EPC-UDR <NUM> are inaccessible by any other vendor than the vendor of HSS <NUM>.

<FIG> illustrates a block diagram of an exemplary control plane (CP) protocol stack between a UE, an eNB, and an MME. The exemplary protocol stack includes Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) layers between the UE and eNB. The PHY layer is concerned with how and what characteristics are used to transfer data over transport channels on the LTE radio interface. The MAC layer provides data transfer services on logical channels, maps logical channels to PHY transport channels, and reallocates PHY resources to support these services. The RLC layer provides error detection and/or correction, concatenation, segmentation, and reassembly, reordering of data transferred to or from the upper layers. The PDCP layer provides ciphering/deciphering and integrity protection for both CP and user plane (UP), as well as other UP functions such as header compression. The exemplary protocol stack also includes non-access stratum (NAS) signaling between the UE and the MME.

The RRC layer controls communications between a UE and an eNB at the radio interface, as well as the mobility of a UE between cells in the E-UTRAN. After a LTE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC_CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE after the connection with the network is released. In RRC_IDLE state, the UE does not belong to any cell, no RRC context has been established for the UE (e.g., in E-UTRAN), and the UE is out of UL synchronization with the network. Even so, a UE in RRC_IDLE state is known in the EPC and has an assigned IP address.

Furthermore, in RRC_IDLE state, the UE's radio is active on a discontinuous reception (DRX) schedule configured by upper layers. During DRX active periods (also referred to as "DRX On durations"), an RRC_IDLE UE receives system information (SI) broadcast by a serving cell, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel for pages from the EPC via an eNB serving the cell in which the UE is camping.

A UE must perform a random-access (RA) procedure to move from RRC_IDLE to RRC_CONNECTED state. In RRC_CONNECTED state, the cell serving the UE is known and an RRC context is established for the UE in the serving eNB, such that the UE and eNB can communicate. For example, a Cell Radio Network Temporary Identifier (C-RNTI) - a UE identity used for signaling between UE and network - is configured for a UE in RRC_CONNECTED state.

LTE Rel-<NUM> adds support for bandwidths larger than <NUM>, while remaining backward compatible with Rel-<NUM>. As such, a wideband LTE Rel-<NUM> carrier (e.g., wider than <NUM>) should appear as a number of carriers (referred to as "component carriers" or "CCs") to an LTE Rel-<NUM> terminal. For an efficient use of a wideband Rel-<NUM> carrier, legacy (e.g., Rel-<NUM>) terminals can be scheduled in all parts of the wideband LTE Rel-<NUM> carrier. One way to achieve this is by Carrier Aggregation (CA), whereby an LTE Rel-<NUM> terminal can receive multiple CCs, each preferably having the same structure as a Rel-<NUM> carrier. Additionally, in the context of CA, the terms "carrier," "component carrier," (or CC, for short) and "cell" are often used interchangeably.

The multiple access scheme for the LTE PHY is based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in the downlink (DL), and on Single-Carrier Frequency Division Multiple Access (SC-FDMA) with a cyclic prefix in the uplink (UL). To support transmission in paired and unpaired spectrum, the LTE PHY supports both Frequency Division Duplexing (FDD) (including both full- and half-duplex operation) and Time Division Duplexing (TDD). The LTE FDD downlink (DL) radio frame has a fixed duration of <NUM> and consists of <NUM><NUM>-ms slots. A <NUM>-ms subframe includes two consecutive slots, each of which includes NDLsymb OFDM symbols comprised of NSC OFDM subcarriers. Similarly, each UL slot consists of NULsymb OFDM symbols, each of which includes NSC OFDM subcarriers. A combination of a particular subcarrier in a particular symbol is known as a resource element (RE).

The LTE PHY maps various DL and UL physical channels to the resources described above. In general, a physical channel corresponds to a set of REs carrying information that originates from higher layers. Within the LTE DL and UL, certain REs within each LTE subframe are reserved for the transmission of reference signals. DL demodulation reference signals (DM-RS) are transmitted to aid the UE in the reception of an associated physical channel (e.g., PDCCH or PDSCH). Other DL reference signals include cell-specific reference signals (CRS), positioning reference signals (PRS), and CSI reference signals (CSI-RS). Other RS-like DL signals include Primary Synchronization Sequence (PSS) and Secondary Synchronization Sequence (SSS), which facilitate the UEs time and frequency synchronization and acquisition of system parameters (e.g., via PBCH). UL reference signals include DM-RS that are transmitted to aid the eNB in the reception of an associated physical channel (e.g., PUCCH or PUSCH); and sounding reference signals (SRS), which are not associated with any uplink channel.

3GPP standards provide various ways for positioning (e.g., determining the position of, locating, and/or determining the location of) UEs operating in LTE networks. In general, an LTE positioning node (referred to as "E-SMLC" or "location server") configures the target device (e.g., UE), an eNB, or a radio network node dedicated for positioning measurements (e.g., a "location measurement unit" or "LMU") to perform one or more positioning measurements according to one or more positioning methods. For example, the positioning measurements can include timing (and/or timing difference) measurements on UE, network, and/or satellite transmissions. The positioning measurements are used by the target device, the measuring node, and/or the positioning node to determine the location of the target device.

UE positioning is expected to be an important feature for NR networks, and may include additional UE positioning use cases, scenarios, and/or applications beyond those for LTE. Positioning in NR Rel-<NUM> is generally based on NR radio technology, which can provide added value in terms of enhanced location capabilities. For example, NR operation in low and high frequency bands (i.e., below and above <NUM>) and utilization of massive antenna arrays provide additional degrees of freedom to substantially improve positioning accuracy. To support these NR-based positioning techniques, however, a UE needs a significant amount of assistance data from the network, some of which is not currently available. This can create various problems, issues, and/or difficulties for positioning based on NR radio technologies.

The document <NPL>) discloses spatial relations between a specified DL RS and a specified UL RS for positioning.

The document <CIT> discloses systems and methods for Semi-Persistent Sounding Reference Signal (SP SRS) resource activation or deactivation.

The document <NPL> discusses a NRPPa procedure to enable an LMF to request activation and deactivation of semi-persistent and aperiodic SRS-for-positioning resource sets from a gNB.

Embodiments of the present disclosure provide specific improvements to positioning of user equipment (UEs) in a wireless network, such as by facilitating solutions to overcome the exemplary problems summarized above and described in more detail below.

Embodiments of the present disclosure include methods (e.g., procedures) for a positioning node (e.g., E-SMLC, LMF, etc.) coupled to a radio access network (RAN). These exemplary methods can include determining first spatial relations between downlink reference signals (DL-RS) and uplink reference signals (UL-RS) used for positioning in a first cell served by a first RAN node, wherein the first cell is a serving cell for a user equipment (UE). These exemplary methods can also include determining second spatial relations between DL-RS and UL-RS used for positioning in one or more second cells served by the second RAN node, wherein the second cells are neighbor cells to the first cell. These exemplary methods can also include configuring the UE to transmit UL-RS according to the first and second spatial relations.

In some embodiments, the configuring operations can include sending a request, to the first RAN node, to configure the UE to transmit UL-RS according to the first and second spatial relations. The request includes the first and second spatial relations. In some of these embodiments, the configuring operations can also include receiving, from the first RAN node, a response including an indication that the UE has been configured to transmit the UL-RS according to the determined spatial relations. In some variants, the response can also include one or more of the following:.

In some of these embodiments, these exemplary methods can also include sending, to the second RAN node, a notification that the UE is configured to transmit UL-RS according to the second spatial relations associated with the second cells.

In some embodiments, the first spatial relations and the second spatial relations are associated with respective DL-RS. For each DL-RS that is a synchronization signal/PBCH block (SSB), the associated first or second spatial relation includes a cell identifier and an SSB index. For each DL-RS that is a positioning reference signal (PRS), the associated first or second spatial relation includes a transmission reception point (TRP) identifier and a PRS resource set identifier.

In some embodiments, these exemplary methods can also include receiving, from the first RAN node, first configuration information for DL-RS and UL-RS used for positioning in the first cell; and receiving, from the second RAN node, second configuration information for DL-RS and UL-RS used for positioning in the one or more second cells. In such embodiments, determining the first spatial relations can be based on the first configuration information, and determining the second spatial relations can be based on the second configuration information.

In some embodiments, these exemplary methods can also include receiving at least one of the following information:.

In such embodiments, determining at least one of the first and second spatial relations can be based on the received information. For example, the first measurements can be used for determining the first spatial relations and the second measurements can be used for determining the second spatial relations. In some variants, the first and second measurements can be positioning measurements, received from the UE. In other variants, the first and second measurements can be received from the first RAN node and can include at least one of the following: radio resource management (RRM) measurements and beam sweep measurements.

In some embodiments, these exemplary methods can also include receiving, from the first RAN node, first positioning measurements of UL-RS transmitted by the UE according to at least one of the first spatial relations; and receiving, from the second RAN node, second positioning measurements of UL-RS transmitted by the UE according to at least one of the second spatial relations. In some of these embodiments, these exemplary methods can also include estimating the UE's geographic location based on the first and second positioning measurements.

Other embodiments include methods (e.g., procedures) for a first RAN node (e.g., base station, eNB, gNB, etc. or component thereof such as a CU or DU) configured to support positioning in the RAN. These exemplary methods can include receiving, from a positioning node, a request to configure a user equipment (UE) to transmit uplink reference signals (UL-RS) for positioning according to first and second spatial relations. The request can include the first and second spatial relations. The first spatial relations are between downlink reference signals (DL-RS) and UL-RS used for positioning in a first cell served by the first RAN node, where the first cell is a serving cell for the UE. The second spatial relations are between DL-RS and UL-RS used for positioning in one or more second cells served by a second RAN node, where the second cells are neighbor cells to the first cell. These exemplary methods can also include determining a plurality of UL-RS configurations corresponding to the first and second spatial relations and configuring the UE to transmit UL-RS according to determined UL-RS configurations.

In some embodiments, these exemplary methods can also include sending, to the positioning node, first configuration information for DL-RS and UL-RS used for positioning in the first cell.

In some embodiments, the determining operations can include selecting UL-RS configurations corresponding to a subset of the first and second spatial relations. In such embodiments, the selected subset can be based on various factors including available UL signal resources in the first cell and/or the one or more second cells, UL configuration capabilities of the UE, etc..

In some embodiments, the determined UL-RS configurations can include the first and second spatial relations. In such embodiments, the configuring operations can include sending, to the UE, a configuration message including the first and second spatial relations. In some embodiments, the configuring operations can include receiving, from the UE, a first response including one or more of the following:.

In some embodiments, these exemplary methods can also include sending, to the positioning node, a second response indicating that the UE has been configured to transmit the UL-RS according to the first and second spatial relations. In some embodiments, the second response can also include one or more of the following:.

In some embodiments, these exemplary methods can also include performing positioning measurements of UL-RS transmitted by the UE according to the determined UL-RS configurations corresponding to first spatial relations; and sending the positioning measurements to the positioning node. In some embodiments, performing the measurements can include combining measurements of UL-RS transmitted by the UE according to two different UL-RS configurations based on the same UE transmit antenna configuration.

In some embodiments, these exemplary methods can also include receive, from the positioning node, a request for the UE to perform at least one of the following measurements:.

Additionally, the first RAN node can obtain the requested measurements from the UE and send, to the positioning node, a response including the requested measurements.

Other embodiments include methods (e.g., procedures) for a user equipment (UE, e.g., wireless device, MTC device, IoT device, etc. or components thereof) configured to support positioning in a radio access network (RAN). These exemplary methods can include receiving, from a first RAN node, a plurality of UL-RS configurations corresponding to first and second spatial relations. The UL-RS configurations can include the first and second spatial relations. The first spatial relations are between DL-RS and UL-RS used for positioning in a first cell served by the first RAN node, where the first cell is a serving cell for the UE. The second spatial relations are between DL-RS and UL-RS used for positioning in one or more second cells served by a second RAN node, where the second cells are neighbor cells to the first cell. These exemplary methods can also include determining transmit antenna configurations corresponding to the respective UL-RS configurations; and transmitting UL-RS according to the respective UL-RS configurations and the corresponding transmit antenna configurations.

In some embodiments, these exemplary methods can also include performing measurements that include first measurements of DL-RS associated with the first cell and/or second measurements of DL-RS associated with the second cells; and sending the measurements to the first RAN node or to a positioning node. In some of these embodiments, the first and/or second measurements are positioning measurements and are sent to the positioning node. In other of these embodiments, the first and/or second measurements are sent to the first RAN node and are radio resource management (RRM) and/or beam sweep measurements.

In some embodiments, the determining operations can include for each received UL-RS configuration, determining a receive antenna configuration for a DL-RS associated with the spatial relation included in the UL-RS configuration and, based on the spatial relation, determining a transmit antenna configuration that results in a transmit beam that is directionally aligned with a receive beam resulting from the receive antenna configuration.

In some of these embodiments, at least two of the transmit antenna configurations can be substantially the same. In such embodiments, these exemplary methods can also include sending, to the first RAN node, a response including one or more of the following:.

In some embodiments, the transmitting operations can include transmitting one or more first UL-RS based on respective one or more first spatial relations associated with the first cell; and transmitting one or more second UL-RS based on respective one or more second spatial relations associated with the second cells.

Other embodiments include positioning nodes (e.g., E-SMLC, LMF, etc.), RAN nodes (e.g., base stations, eNBs, gNBs, ng-eNBs, etc. or components thereof), and user equipment (UEs, e.g., wireless devices, IoT devices, etc. or components thereof) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such positioning nodes, RAN nodes, or UEs to perform operations corresponding to any of the exemplary methods described herein.

These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

The steps of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments can apply to any other embodiments, and vice versa. Other objects, features, and advantages of the enclosed embodiments will be apparent from the following description.

Furthermore, the following terms are used throughout the description given below:.

Note that the description herein focuses on a 3GPP cellular communications system and, as such, 3GPP-specific terminology (or equivalent) is often used. However, the concepts disclosed herein are not limited to a 3GPP system and can be applied to any wireless system having appropriate and/or relevant functionality. Furthermore, although the term "cell" is used herein, it should be understood that (particularly with respect to <NUM> NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.

As briefly mentioned, NR operation in low and high frequency bands (i.e., below and above <NUM>) and utilization of massive antenna arrays provide additional degrees of freedom to substantially improve positioning accuracy. To support these NR-based positioning techniques, however, a UE needs a significant amount of assistance data from the network, some of which is not currently available. This can create various problems, issues, and/or difficulties for positioning based on NR radio technologies. These issues are discussed in more detail below.

<FIG> shows an exemplary positioning architecture within an LTE network. Three important functional elements of the LTE positioning architecture are the LCS Client, the LCS target and the LCS Server. The LCS Server is a physical or logical entity (e.g., as embodied by the E-SMLC or SLP in <FIG>) managing positioning for an LCS target (e.g., as embodiments by the UE in <FIG>) by collecting measurements and other location information, assisting the terminal in measurements when necessary, and estimating the LCS target location. An LCS Client is a software and/or hardware entity that interacts with an LCS Server for the purpose of obtaining location information for one or more LCS targets (i.e., the entities being positioned) such as the UE in <FIG>. LCS Clients may also reside in the LCS targets themselves. An LCS Client sends a request to an LCS Server to obtain location information, and the LCS Server processes and serves the received requests and sends the positioning result and optionally a velocity estimate to the LCS Client. A positioning request can be originated from the terminal or a network node or external client.

In the LTE architecture shown in <FIG>, position calculation can be conducted, for example, by the LCS Server (e.g., E-SMLC or SLP) or by the LCS target (e.g., a UE). The former approach corresponds to the UE-assisted positioning mode when it is based on UE measurements, whilst the latter corresponds to the UE-based positioning mode. The following positioning methods are supported in LTE:.

In addition, one or more of the following positioning modes can be utilized in each of the positioning methods listed above:.

The detailed assistance data may include information about network node locations, beam directions, etc. The assistance data can be provided to the UE via unicast or via broadcast.

<FIG> shows another view of an exemplary positioning architecture in an LTE network. For example, <FIG> illustrates how secure user plane location (SUPL) techniques can be supported in LTE networks. In general, SUPL is run on top of the generic LTE user-plane protocol stack. The SUPL solution includes a location server - known as SUPL location platform, SLP (<NUM>) - that communicates with a SUPL-enabled terminal (SET), which can be software and/or hardware components of a UE. The SLP also may have a proprietary interface to the E-SMLC (<NUM>), which is the location server for control-plane positioning in LTE.

The E-SMLC can communicate with location measurement units (LMUs) via SLm interfaces. As shown in <FIG>, LMUs can be standalone (e.g., LMU <NUM>) or integrated with an eNB <NUM>. An eNB also may include, or be associated with, one or more transmission points (TPs). The E-SMLC communicates to UEs (e.g., UE <NUM>) via the serving MME (<NUM>) and eNB, using the respective SLs, S1, and Uu interfaces shown in <FIG>. Although not shown, the RRC protocol is used to carry positioning-related information (e.g., to/from E-SMLC) between the UE and the eNB.

E-SMLC <NUM> can also include, or be associated with, various processing circuitry <NUM>, by which the E-SMLC performs various operations described herein. Processing circuitry <NUM> can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of <FIG>). E-SMLC <NUM> can also include, or be associated with, a non-transitory computer-readable medium <NUM> storing instructions (also referred to as a computer program product) that can facilitate operations of processing circuitry <NUM>. Medium <NUM> can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of <FIG>). Additionally, E-SMLC <NUM> can include various communication interface circuitry <NUM>, which can be used, e.g., for communication via the SLs interface.

Positioning Reference Signals (PRS) were introduced in LTE Rel-<NUM> for antenna port <NUM> because cell-specific reference signals (CRS) were insufficient for positioning. In particular, CRS could not guarantee the required high probability of detection. In general, a neighbor cell's synchronization signals (PSS/SSS) and reference signals are generally detectable by a UE when the Signal-to-Interference-and-Noise Ratio (SINR) is at least -<NUM> dB.

Nevertheless, simulations during 3GPP standardization have shown that detection can be only guaranteed for <NUM>% of all cases for the third-best detected cell, meaning that in at least <NUM>% of cases only two neighboring cells are detected. Moreover, the simulations assumed an interference-free environment that is generally unobtainable in a real-world scenario. However, PRS have some similarities with CRS. In particular, PRS is a pseudo-random QPSK sequence that is mapped in diagonal patterns with shifts in frequency and time to avoid collision with CRS and an overlap with the control channels (PDCCH).

Fifth-generation (<NUM>) New Radio (NR) technology shares many similarities with fourth-generation LTE. For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the UL. As another example, in the time domain, NR DL and UL physical resources are organized into equal-sized <NUM>-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols. As another example, NR RRC layer includes RRC_IDLE and RRC_CONNECTED states, but adds an additional state known as RRC _INACTIVE, which has some properties similar to a "suspended" condition used in LTE.

In addition to providing coverage via "cells," as in LTE, NR networks also provide coverage via "beams. " In general, a DL "beam" is a coverage area of a network-transmitted RS that may be measured or monitored by a UE. In NR, for example, such RS can include any of the following, alone or in combination: synchronization signal/PBCH block (SSB), CSI-RS, tertiary reference signals (or any other sync signal), positioning RS (PRS), DMRS, phase-tracking reference signals (PTRS), etc. In general, SSB is available to all UEs regardless of RRC state, while other RS (e.g., CSI-RS, DM-RS, PTRS) are associated with specific UEs that have a network connection, i.e., in RRC_CONNECTED state.

As mentioned above, positioning is also expected to be an important application in <NUM>/NR networks. <FIG> shows a high-level view of an exemplary <NUM> network architecture, including a Next Generation Radio Access Network (NG-RAN) <NUM> and a <NUM> Core (5GC) <NUM>. As shown in the figure, NG-RAN <NUM> can include gNBs <NUM> (e.g., 510a,b) and ng-eNBs <NUM> (e.g., 520a,b) that are interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected via the NG interfaces to 5GC <NUM>, more specifically to the AMF (Access and Mobility Management Function) <NUM> (e.g., AMFs 530a,b) via respective NG-C interfaces and to the UPF (User Plane Function) <NUM> (e.g., UPFs 540a,b) via respective NG-U interfaces. In some embodiments, 5GC <NUM> can also include one or more Location Management Functions (LMFs, e.g., LMF 550a,b), which are described in more detail below.

NG-RAN <NUM> is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. In some exemplary configurations, each gNB can be connected to all 5GC nodes within an "AMF Region," which is defined in 3GPP TS <NUM>. If security protection for CP and UP data on TNL of NG-RAN interfaces is supported, NDS/IP can be applied, as defined in 3GPP TS <NUM>.

Each of the gNBs 510a,b can support the NR radio interface, including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. In contrast, each of ng-eNBs 520a,b supports the LTE radio interface but, unlike conventional LTE eNBs (e.g., eNBs <NUM>-<NUM> shown in <FIG>), connect to the 5GC via the NG interface. In addition, the gNBs 510a,b and ng-eNBs 520a,b can provide multi-RAT (radio access technology) dual connectivity (MR-DC) to UEs as described above, including NG-RAN E-UTRA/NR Dual Connectivity (NGEN-DC).

Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, including exemplary cells 511a-b and 521a-b shown in <FIG>. As mentioned above, the gNBs and ng-eNBs can also use various directional beams to provide coverage in the respective cells. Depending on the particular cell in which it is located, a UE <NUM> can communicate with the gNB or ng-eNB serving that particular cell via the NR or LTE radio interface, respectively.

Each of the gNBs 510a,b can include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). A CU connects to DUs over respective F1 logical interfaces. The CU and connected DUs are only visible to other gNBs and the 5GC as a gNB, e.g., the F1 interface is not visible beyond gNB-CU. Each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry. Moreover, the terms "central unit" and "centralized unit" are used interchangeably herein, as are the terms "distributed unit" and "decentralized unit.

CUs can host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. For example, a CU can host higher-layer protocols such as, e.g., F1 application part protocol (FLAP), Stream Control Transmission Protocol (SCTP), GPRS Tunneling Protocol (GTP), Packet Data Convergence Protocol (PDCP), User Datagram Protocol (UDP), Internet Protocol (IP), and Radio Resource Control (RRC) protocol. Likewise, DUs can host lower-layer protocols and can include various subsets of the gNB functions, depending on the functional split. For example, a DU can host lower-layer protocols such as, Radio Link Control (RLC), Medium Access Control (MAC), and physical-layer (PHY) protocols.

<FIG> is a block diagram illustrating a high-level architecture for supporting UE positioning in NR networks. In <FIG>, NG-RAN <NUM> can include nodes such as gNB <NUM> and ng-eNB <NUM>, similar to the architecture shown in <FIG>. Each ng-eNB may control several transmission points (TPs), such as remote radio heads. Moreover, some TPs can be "PRS-only" for supporting positioning reference signal (PRS)-based TBS for E-UTRAN operation.

In addition, the NG-RAN nodes communicate with an AMF <NUM> in the 5GC via respective NG-C interfaces (both of which may or may not be present), while the AMF and LMF <NUM> communicate via an NLs interface. In addition, positioning-related communication between UE <NUM> and the NG-RAN nodes occurs via the RRC protocol, while positioning-related communication between NG-RAN nodes and LMF occurs via an NRPPa protocol. Optionally, the LMF can also communicate with an E-SMLC <NUM> in an LTE network, such as illustrated in <FIG>.

LMF <NUM> can also include, or be associated with, various processing circuitry <NUM>, by which the LMF performs various operations described herein. Processing circuitry <NUM> can include similar types of processing circuitry as described herein in relation to other network nodes (see, e.g., description of <FIG>). LMF <NUM> can also include, or be associated with, a non-transitory computer-readable medium <NUM> storing instructions (also referred to as a computer program product) that can facilitate the operations of processing circuitry <NUM>. Medium <NUM> can include similar types of computer memory as described herein in relation to other network nodes (see, e.g., description of <FIG>). Additionally, LMF <NUM> can include various communication interface circuitry <NUM>, which can be used, e.g., for communication via the NLs interface.

In a typical operation, the AMF can receive a request for a location service associated with a particular target UE from another entity (e.g., a gateway mobile location center (GMLC)), or the AMF itself can initiate some location service on behalf of a particular target UE (e.g., for an emergency call from the UE). The AMF then sends a location services (LS) request to the LMF. The LMF processes the LS request, which may include transferring assistance data to the target UE to assist with UE-based and/or UE-assisted positioning; and/or positioning of the target UE. The LMF then returns the result of the LS (e.g., a position estimate for the UE and/or an indication of any assistance data transferred to the UE) to the AMF or to another entity (e.g., GMLC) that requested the LS.

An LMF may have a signaling connection to an E-SMLC, enabling the LMF to access information from E-UTRAN, e.g., to support E-UTRA OTDOA positioning using downlink measurements obtained by a target UE. An LMF can also have a signaling connection to an SLP, the LTE entity responsible for user-plane positioning.

Various interfaces and protocols are used for, or involved in, NR positioning. The LTE Positioning Protocol (LPP) is used between a target device (e.g., UE in the control-plane, or SET in the user-plane) and a positioning server (e.g., LMF in the control-plane, SLP in the user-plane). LPP can use either the control- or user-plane protocols as underlying transport. NRPP is terminated between a target device and the LMF. RRC protocol is used between UE and gNB (via NR radio interface) and between UE and ng-eNB (via LTE radio interface).

Furthermore, the NR Positioning Protocol A (NRPPa) carries information between the NG-RAN Node and the LMF, and is transparent to the AMF. As such, the AMF routes the NRPPa PDUs transparently (e.g., without knowledge of the involved NRPPa transaction) over NG-C interface based on a Routing ID corresponding to the involved LMF. More specifically, the AMF carries the NRPPa PDUs over NG-C interface either in UE associated mode or non-UE associated mode. The NGAP protocol between the AMF and an NG-RAN node (e.g., gNB or ng-eNB) is used as transport for LPP and NRPPa messages over the NG-C interface. NGAP is also used to instigate and terminate NG-RAN-related positioning procedures.

LPP/NRPP are used to deliver messages such as positioning capability request, OTDOA positioning measurements request, and OTDOA assistance data to the UE from a positioning node (e.g., location server). LPP/NRPP are also used to deliver messages from the UE to the positioning node including, e.g., UE capability, UE measurements for UE-assisted OTDOA positioning, UE request for additional assistance data, UE configuration parameter(s) to be used to create UE-specific OTDOA assistance data, etc. NRPPa is used to deliver the information between ng-eNB/gNB and LMF in both directions. This can include LMF requesting some information from ng-eNB/gNB, and ng-eNB/gNB providing some information to LMF. For example, this can include information about PRS transmitted by ng-eNB/gNB that are to be used for OTDOA positioning measurements by the UE.

NR networks will support positioning methods similar to LTE E-CID, OTDOA, and UTDOA but based on NR measurements. NR may also support one or more of the following position methods:.

Each of the NR positioning methods can be supported in UE-assisted, UE-based or UE-standalone modes, similar to LTE discussed above. <NUM>, a WI is currently ongoing to specify extensive support for these various positioning techniques. This is expected to include a NR DL PRS based on a staggered comb RE pattern as well as extension of Rel-<NUM> sounding reference signal (SRS) configurations for improved positioning support. Support for RSTD measurements that may be used for OTDOA is expected as well as multi cell UE RX-TX time difference measurements that can be used for Round Trip Time (RTT) estimation. Rich reporting of multiple CIR/correlation peaks has been discussed as well as reporting of the strongest CIR/correlation peak.

Recent advances in massive antenna systems (massive MIMO) can provide additional degrees of freedom to enable a more accurate user location estimation by exploiting spatial and angular domains of the propagation channel in combination with time measurements. These spatial techniques, also referred to as "beamforming", can be used on transmission beams and/or reception beams, by the network or by the UE.

Currently, two NR frequency ranges are explicitly distinguished in 3GPP: FR1 (below <NUM>) and FR2 (above <NUM>). It is known that high-frequency radio communication above <NUM> suffers from significant path loss and penetration loss. One solution to address this issue is to deploy large-scale antenna arrays to achieve high beamforming gain, which is a reasonable solution due to the small wavelength of high-frequency signal. Such solutions are often referred to as multiple-input multiple-output (MIMO) or, in the case of large-scale antenna arrays anticipate for NR, massive MIMO. In particular, up to <NUM> beams are supported for FR2. In addition, it is expected that the greater number of antenna elements will also be used in FR1 to obtain more beamforming and multiplexing gain.

With massive MIMO, three approaches to beamforming have been discussed: analog, digital, and hybrid (a combination of analog and digital). Analog beamforming can compensate for high pathloss in NR scenarios, while digital precoding can provide additional performance gains (e.g., similar to MIMO for FR1) necessary to achieve a reasonable coverage. The implementation complexity of analog beamforming is significantly less than digital since it can utilize simple phase shifters, but it is limited in terms of multi-direction flexibility (i.e., a single beam can be formed at a time and the beams are then switched in time domain), transmission bandwidth (i.e., not possible to transmit over a sub-band), inaccuracies in the analog domain, etc..

Digital beamforming requires costly converters between the digital domain and the intermediate frequency (IF) radio domain. However, digital beamforming, which is often used today in LTE networks, provides the best performance in terms of data rate and multiplexing capabilities. For example, multiple beams over multiple sub-bands can be formed simultaneously. Even so, digital beamforming presents challenges in terms of power consumption, integration, and cost. Furthermore, while cost generally scales linearly with the number of transmit/receive units, the gains of digital beamforming increase more slowly.

Hybrid beamforming, which provides cost benefits from analog beamforming and capacity benefits from digital beamforming, is therefore desirable for NR. <FIG> shows an exemplary hybrid transmit (TX) beamforming arrangement, which includes a digital precoding section and an analog beamforming (BF) section that are coupled by intermediate conversion circuitry As shown in <FIG>, the analog BF portion includes independent analog circuitry for each of N subarrays of antenna elements. For each subarray, the analog circuitry includes mixers (e.g., from IF to RF), phase shifters, and power amplifiers (PAs). Each subarray can generate a beam separate from other subarrays. The conversion circuity includes independent IFFT modulators, parallel-to-serial converters (P/S), and digital-to-analog converters (DAC) for each of the N channels of the analog BF circuitry.

The analog beam of a subarray can be steered toward a single direction on each OFDM symbol, and hence the number of subarrays determines the number of beam directions and the corresponding coverage on each OFDM symbol. However, the number of beams to cover an entire served area is typically larger than the number of subarrays, especially when the individual beam-width is narrow. Therefore, to cover the entire served area, multiple transmissions with narrow beams steered differently in time domain are also likely to be needed. The provision of multiple narrow coverage beams for this purpose has been called "beam sweeping". <FIG> shows two exemplary beam sweeping arrangements involving two subarrays (<FIG>) and three subarrays (<FIG>).

For analog and hybrid beamforming, beam sweeping can be very important for providing necessary coverage in NR networks. For this purpose, multiple OFDM symbols, in which differently steered beams can be transmitted through subarrays, can be assigned and periodically transmitted. In general, both RX and TX beam sweeping function in a similar manner at the base station side.

NR Rel-<NUM> positioning will also support beamforming. The DL PRS is constructed as a DL PRS Resource set consisting of multiple DL PRS Resources. Each DL PRS Resource is transmitted over a separate beam. It has been decided in 3GPP RAN1 WG that an UL SRS can have a spatial relation to a DL PRS Resource as signaled through the combination of a DL PRS Resource set ID and a DL PRS Resource ID. The UE will then transmit the UL SRS using the same antenna panel as it uses to receive the corresponding DL PRS resource and using the same (reciprocal) beam as it uses to receive the DL PRS Resource.

NR has adopted the term "spatial relation" to refer to a relationship between an UL RS (e.g., PUCCH/PUSCH DMRS) and another RS, which can be either a DL RS (CSI-RS or SSB) or an UL RS (SRS). This is also defined from a UE perspective. If the UL RS is spatially related to a DL RS, it means that the UE should transmit the UL RS in the opposite (reciprocal) direction from which it received the corresponding DL RS. More precisely, the UE should apply the "same" Tx spatial filtering (or beamforming) configuration for transmitting the spatially-related UL RS as the Rx spatial filtering (or beamforming) configuration that it used for receiving the corresponding DL RS.

The RRC information element (IE) SRS-Config is used to configure SRS transmissions by a UE. The configuration defines a list of SRS-Resources and a list of SRS ResourceSets. Each resource set defines a set of SRS-Resources. The network triggers the transmission of a set of SRS-Resources using a configured aperiodicSRS-ResourceTrigger (L1 downlink control information, DCI). <FIG>, which includes <FIG>, shows an ASN. <NUM> data structure for an exemplary SRS-Config IE. Note that to obtain the complete ASN. <NUM> data structure, <FIG> are appended in sequential order as presented.

The SRS-SpatialRelationInfo-r16 IE shown in <FIG> defines spatial relations for the SRS configured by SRS-Config (with some fields defined in <FIG>). As shown in <FIG>, however, the SRS-SpatialRelationInfo-r16 IE defines spatial relations only for the UE's serving cell with respect to DL SSB, CSI-RS and SRS. Positioning also requires measurements of neighbor cells, so spatial relations are also needed with respect to neighbor cells (e.g., TRPs). Furthermore, it would be beneficial to also have the capability for spatial relations between UL-SRS and DL-PRS since both are used for positioning purposes.

Embodiments of the present disclosure can address these and other problems, issues, and/or difficulties by providing novel, flexible, and efficient techniques for a positioning node (e.g., E-SLMC, LMF) to determine spatial relations from positioning configuration information provided by radio access network (RAN) nodes (e.g., gNBs) serving neighboring cells. The positioning node can then configure the RAN nodes with the determined spatial relations (e.g., via NRPPa signaling), which the RAN nodes can then use to configure UEs for positioning operations (e.g., via RRC signaling). Configured UEs can then use the spatial relations to determine and/or select appropriate antenna configurations for transmitting and/or receiving positioning-related signals (e.g., PRS). RAN node and/or UE measurements of the positioning-related signals can be reported to a positioning node, which can use such measurements to estimate the UE's geographic location.

<FIG> shows a signal flow diagram of an exemplary procedure for determining and configuring spatial relations for positioning-related signals, according to various exemplary embodiments of the present disclosure. Although <FIG> shows operations with numerical labels, these labels are intended to facilitate the following explanation and do not require the operations to be performed in an order corresponding to their numerical labels. In other words, unless specifically noted to the contrary, the operations can be performed in a different order than shown and can be combined and/or divided to form other operations than those specifically shown.

In particular, <FIG> shows an arrangement involving UE <NUM>, gNB1 <NUM> (e.g., the UE's serving gNB), gNB2 <NUM> (e.g., a non-serving gNB), and LMF <NUM>. The reference numbers are omitted in the following description for clarity and conciseness.

In operation <NUM>, gNB <NUM> and gNB2 can provide positioning-related configuration information to the LMF. The configuration can include capabilities related to both UL and DL signals used for positioning. DL signals used for positioning can include SSB, CSI-RS and/or DL-PRS. The SSB information can include detailed SSB configuration (e.g., periodicity, duration, positions in a burst, etc.). UL signals used for positioning can include UL-PRS.

In various embodiments, the configuration information provided by a gNB to the LMF can include information related to one or more of the following:.

In other embodiments, beam-related information (e.g., association between cells and beams for the respective gNBs) can be pre-configured (e.g., via OAM).

In LTE for positioning methods such as OTDOA, a preparation step based on the enhanced cell ID (ECID) positioning method can be beneficial. For example, based upon the ECID results, the E-SMLC can prepare the necessary LPP Assistance Data (AD) for a specific UE for a subject positioning procedure based on the OTDOA method. Similarly, for NR positioning methods such as DL-TDOA, a preparation step based on the method NR-ECID can also be beneficial. Further, other NR positioning methods such as UL-TDOA or Multicell-RTT, which require UL SRS transmission from UE, can also benefit from preparation operations for determining spatial relations. This procedure can either be NR-ECID or a specific beam sweep results obtained from the UE, especially for FR2.

In some embodiments, for positioning measurements based on DL-PRS (e.g., for DL-only positioning), the preparation operation can an NR ECID procedure to obtain UE measurements. In other embodiments, for positioning measurements based on UL-SRS (e.g., for UL-only and multi-RTT positioning), the preparation operation can include a procedure for the configuration and reporting of UE DL-PRS measurements per beam/resource. In other embodiments, for positioning measurements based on UL-SRS (e.g., for UL-only and multi-RTT positioning), the preparation operation can include a procedure for the configuration and reporting of UE SSB or CSI-RS measurements per beam/resource. For example, this could be an NR ECID procedure.

In some embodiments, the LMF can request a gNB to configure a served UE to perform radio resource management (RRM) and/or beam sweep measurements for the purpose of determining spatial relations. In general, an LMF is only allowed to request and/or trigger positioning-related measurements by UE. However, such positioning-related measurements may not provide sufficient basis for determining the necessary spatial relations. Even so, the gNB can trigger RRM and/or beam sweep measurements by the UE, which may be more suitable for determining spatial relations. For example, the LMF can send a UE-specific NRPPa to a gNB, which may accept or reject the request or reject. If the gNB accepts, it configures the measurements via RRC signaling with the UE, receives the results via RRC signaling, and provides the results to the LMF in a responsive NRPPa message. Spatial relation which is UL and DL resource alignment in terms of direction can be considered as RRM related measurements which should be then delegated to gNB.

The optional preparation operations can provide UE measurement information that facilitates the positioning node to determine relevant DL beams/resources/indices for a UE, collectively referred to below as "beam" (singular) or "beams" (plural). For example, the UE measurements (e.g., received signal power) associated with the respective beams can indicate most favorable beams per beam set, per cell, per TRP, etc..

In some embodiments, during the preparation operations, the LMF may request UE capabilities regarding UL signals. The UE can provide the requested capability information, e.g., supported resource sets and resources, supported signal configurations, etc..

Operation <NUM> in <FIG> correspond to the optional preparation operations discussed above. In operation 2a, the LMF prepares and provides a configuration to UE to perform various measurements. Although not shown, this can involve two messages: one from LMF to gNB (e.g., NRPPa), and a second from gNB to UE (e.g., RRC). Exemplary configured measurements can include RRM measurements, E-CID measurements, beam sweep measurements, etc. based on SSB, CSI-RS and/or DL-PRS. In operation 2b, the UE provides results for the configured measurements to the LMF (and optionally UE capabilities). Like operation 2a, operation 2b can involve two messages: one from UE to gNB (e.g., RRC), and a second from gNB to LMF (e.g., NRPPa).

In operation <NUM>, based on the positioning configuration information received in operation <NUM>, and optionally based on UE DL measurements and/or UL capabilities received in operation <NUM>, the LMF can determine a set of spatial relations associated with the UE. For example, the LMF can determine a spatial relation between a DL signal or beam and an uplink signal such as UL-SRS. In operation <NUM>, based on the information received in operation <NUM> (and optionally in operation <NUM>) and the spatial relations determined in operation <NUM>, the LMF can prepare a configuration of positioning signals (e.g., SRS) to be measured in association with a particular positioning method for estimating the UE's geographic location. In operation <NUM>, the LMF sends the configuration, including the determined spatial relations, to the UE's serving gNB as part of an NRPPa request for the gNB to configure the UE for the positioning operation.

For example, in operation <NUM>, the LMF can send a spatial relations list including three (<NUM>) spatial relationships to SSBs, with one SSB from serving cell <NUM> (provided by gNB1) and two from neighbor cell <NUM> (provided by gNB2). In this example, the spatial relations list can include the following three entries:.

In another example, the LMF can send a spatial relations list including three (<NUM>) spatial relationships to DL-PRS, with one DL-PRS from TRP1 and two from TRP2. TRPs <NUM> and <NUM> can be associated with either gNB <NUM> or gNB2. In this example, the spatial relations list can include the following three entries:.

In another example, the LMF can send a spatial relations list including three (<NUM>) spatial relationships to a combination of DL-PRS and SSBs, e.g., one SSB from cell <NUM>, and two DL-PRS transmitted by TRP2. In this example, the spatial relations list can include the following three entries:.

In some embodiments, the number of spatial relations in the list can be implicitly indicated by the length of the relevant beam list, limited to the number of UL signals that the UE supports.

In some embodiments, the LMF can provide an SSB configuration to serving gNB1 together with the spatial relation list. Optionally, the LMF will refrain from sending the SSB configuration to gNB1 if the SSB configuration has been sent earlier, and the SSB configuration is considered to be the same.

As discussed above, in operation 2b, the UE optionally provides capabilities related to UL signals. In such cases, the gNB may include in the configuration sent in operation <NUM> a selection of particular capabilities indicated by the UE in operation 2b.

In operation <NUM>, gNB1 provides an UL signal (e.g., SRS) configuration to the UE via RRC signaling. The gNB can determine the number of UL signals to include in the configuration based on the spatial relations received in operation <NUM>, the number of available uplink signal resources in the UE's serving cell, and (optionally) the UL signal capabilities received from the UE in operation 2b. The UL signal configuration provided to the UE in operation <NUM> also includes spatial relations for the configured UL signals.

In operation <NUM>, based on the configuration received in operation <NUM>, the UE determines an appropriate receive antenna configuration for a DL signal (e.g., CSI-RS, SSB, etc.) associated with each configured spatial relation. In addition, the UE determines a transmit antenna configuration for an UL signal associated with each configured spatial relation. For each spatial relation, the transmit antenna configuration should be the same as, or analogous to, the receive antenna configuration associated determined for the same spatial relation. For example, the transmit antenna configurations can be directionally aligned with the receive antenna configurations.

In operation <NUM>, the UE sends a response message (e.g., via RRC signaling) to gNB1 indicating that the configuration is complete. This can be done, e.g., after the UE has finished the determinations in operation <NUM>.

In some embodiments, the UE may determine that the spatial relations of two different UL signal configurations are associated with the same transmit antenna configuration. In such case, the UE can indicate in the response message that these two UL signal configurations will be transmitted with the same transmit antenna configuration, or the UE can indicate in the response message the one of the two configurations is rejected.

In operation <NUM>, gNB1 can inform the LMF about the UL signal configurations that were provided to and accepted by the UE. In some embodiments, the gNB can also indicate any instances of multiple UL signal configurations that will be transmitted by the UE with a single transmit antenna configuration. In some embodiments, gNB1 can also indicate the spatial relation(s) per UL signal configuration. In case two spatial relations have been mapped to the same uplink transmit antenna configuration, then all these can be indicated as spatially related to the same uplink signal configuration in the response message.

In operation <NUM>, the LMF can forward the UL signal configurations to be used by the UE to one or more gNBs (e.g., gNB2) serving neighbor cells to the UE's serving cell. This information can be provided, e.g., via an NRPPa message. In some embodiments, the LMF only selects gNBs associated with DL signals having spatial relations in the spatial relations list provided in operation <NUM>.

After receiving such information, all concerned gNBs (e.g., gNB1 and gNB2) can measure the UL signals transmitted by the UE according to the UL signal configurations provided by the LMF. In some embodiments, if two or more UL signal configurations are indicated (e.g., by the UE in operation <NUM>) to be associated with the same UE transmit antenna configuration, the gNB combines measurements from these UL signal configurations into a single measurement value.

In operation <NUM>, all concerned gNBs (e.g., gNB1 and gNB2) can report measurement results for the UL signals transmitted by the UE to the LMF. The LMF can estimate the UE's geographic location based on the received measurements.

In some embodiments, the LMF can prepare a configuration in operation <NUM> for a positioning method that involves measurements of both UL signals (e.g., by gNBs) and DL signals (e.g., by the UE). In such embodiments, the UE can also provide measurement results for the DL signals in operation <NUM>. If needed, the LMF can configure the gNBs in operations <NUM> and/or <NUM> to transmit the DL signals to be measured by the UE in support of the positioning method.

The embodiments described above can be further illustrated with reference to <FIG>, which depict exemplary methods (e.g., procedures) for a positioning node, a first RAN node, and a UE, respectively. In other words, various features of the operations described below in relation to <FIG> correspond to various embodiments described above, e.g., with respect to <FIG>. The exemplary methods shown in <FIG> can be used cooperatively (i.e., with each other and/or with the procedure shown in <FIG>) to provide various exemplary advantage, benefits, and/or solutions to problems described herein. Although <FIG> show specific blocks in particular orders, the operations of the blocks can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.

In particular, <FIG> is a flow diagram of an exemplary method (e.g., procedure) for a positioning node coupled to a radio access network (RAN), according to various exemplary embodiments of the present disclosure. The exemplary method can be performed by a positioning node (e.g., E-SMLC, LMF, etc.), such as those described herein with reference to other figures.

The exemplary method can include the operations of block <NUM>, where the positioning node can determine first spatial relations between downlink reference signals (DL-RS) and uplink reference signals (UL-RS) used for positioning in a first cell served by a first RAN node, wherein the first cell is a serving cell for a user equipment (UE). The exemplary method can also include the operations of block <NUM>, where the positioning node can determine second spatial relations between DL-RS and UL-RS used for positioning in one or more second cells served by the second RAN node, wherein the second cells are neighbor cells to the first cell. <FIG> operation <NUM> is an example of the operations of blocks <NUM>-<NUM>.

The exemplary method can also include the operations of block <NUM>, where the positioning node can configure the UE to transmit UL-RS according to the first and second spatial relations. In some embodiments, the configuring operations of block <NUM> can include the operations of sub-block <NUM>, where the positioning node can send a request, to the first RAN node, to configure the UE to transmit UL-RS according to the first and second spatial relations. The request includes the first and second spatial relations. An exemplary request is <FIG> operation <NUM>. In some of these embodiments, the configuring operations of block <NUM> can also include the operations of sub-block <NUM>, where the positioning node can receive, from the first RAN node, a response including an indication that the UE has been configured to transmit the UL-RS according to the determined spatial relations. An exemplary response is <FIG> operation <NUM>. In some variants, the response can also include one or more of the following:.

In some of these embodiments, the exemplary method can also include the operations of block <NUM>, where the positioning node can send, to the second RAN node, a notification that the UE is configured to transmit UL-RS according to the second spatial relations associated with the second cells. An exemplary notification is <FIG> operation <NUM>.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the positioning node can receive, from the first RAN node, first configuration information for DL-RS and UL-RS used for positioning in the first cell. In block <NUM>, the positioning node can receive, from the second RAN node, second configuration information for DL-RS and UL-RS used for positioning in the one or more second cells. <FIG> operation <NUM> is an example of receiving such configuration information. In such embodiments, determining the first spatial relations (e.g., in block <NUM>) can be based on the first configuration information, and determining the second spatial relations (e.g., in block <NUM>) can be based on the second configuration information.

In some embodiments, the exemplary method can also include the operations of block <NUM>, where the positioning node can receive at least one of the following information:.

<FIG> operation 2b is an example of receiving such measurement information. In such embodiments, determining at least one of the first and second spatial relations (e.g., in blocks <NUM> and/or <NUM>) can be based on the received information (e.g., in block <NUM>). For example, the first measurements can be used for determining the first spatial relations and the second measurements can be used for determining the second spatial relations. In some variants, the first and second measurements can be positioning measurements, received from the UE. In other variants, the first and second measurements can be received from the first RAN node and can include at least one of the following: radio resource management (RRM) measurements and beam sweep measurements.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the positioning node can receive, from the first RAN node, first positioning measurements of UL-RS transmitted by the UE according to at least one of the first spatial relations. In block <NUM>, the positioning node can receive, from the second RAN node, second positioning measurements of UL-RS transmitted by the UE according to at least one of the second spatial relations. <FIG> operation <NUM> is an example of receiving such positioning measurements. In some of these embodiments, the exemplary method can also include the operations of block <NUM>, where the positioning node can estimate the UE's geographic location based on the first and second positioning measurements.

In addition, <FIG> (which includes <FIG>) is a flow diagram of an exemplary method (e.g., procedure) for a first radio access network (RAN) node configured to support positioning in the RAN, according to various exemplary embodiments of the present disclosure. The exemplary method can be performed by a RAN node (e.g., base station, eNB, gNB, etc. or component thereof such as a CU or DU), such as described herein with reference to other figures.

The exemplary method can include the operations of block <NUM>, where the first RAN node can receive, from a positioning node, a request to configure a user equipment (UE) to transmit uplink reference signals (UL-RS) for positioning according to first and second spatial relations. The request can include the first and second spatial relations. The first spatial relations are between downlink reference signals (DL-RS) and UL-RS used for positioning in a first cell served by the first RAN node, where the first cell is a serving cell for the UE. The second spatial relations are between DL-RS and UL-RS used for positioning in one or more second cells served by a second RAN node, where the second cells are neighbor cells to the first cell. <FIG> operation <NUM> is an example of the operations of block <NUM>.

The exemplary method can also include the operations of block <NUM>, where the first RAN node can determine a plurality of UL-RS configurations corresponding to the first and second spatial relations. The exemplary method can also include the operations of block <NUM>, where the first RAN node can configure the UE to transmit UL-RS according to determined UL-RS configurations.

In some embodiments, the exemplary method can also include the operations of block <NUM>, where the first RAN node can send, to the positioning node, first configuration information for DL-RS and UL-RS used for positioning in the first cell. Such information can be used by the positioning node, for example, to determine the spatial relations received in block <NUM>. <FIG> operation <NUM> is an example of sending such configuration information.

In some embodiments, the determining operations of block <NUM> can include the operations of sub-block <NUM>, where the first RAN node can select UL-RS configurations corresponding to a subset of the first and second spatial relations. In such embodiments, the selected subset can be based on various factors including available UL signal resources in the first cell and/or the one or more second cells, UL configuration capabilities of the UE, etc..

In some embodiments, the determined UL-RS configurations (e.g., in block <NUM>) can include the first and second spatial relations. In such embodiments, the configuring operations of block <NUM> can include the operations of sub-block <NUM>, where the first RAN node can send, to the UE, a configuration message including the first and second spatial relations. <FIG> operation <NUM> is an example of the operations of block <NUM>. In some embodiments, the configuring operations of block <NUM> can include the operations of sub-block <NUM>, where the first RAN node can receive, from the UE, a first response including one or more of the following:.

<FIG> operation <NUM> is an example of the operations of sub-block <NUM>.

In some embodiments, the exemplary method can also include the operations of block <NUM>, where the first RAN node can send, to the positioning node, a second response indicating that the UE has been configured to transmit the UL-RS according to the first and second spatial relations. <FIG> operation <NUM> is an exemplary second response. This second response can be responsive to the operations of block <NUM> including any optional sub-blocks (e.g., first response). In some embodiments, the second response can also include one or more of the following:.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the first RAN node can perform positioning measurements of UL-RS transmitted by the UE according to the determined UL-RS configurations corresponding to first spatial relations. In block <NUM>, the first RAN node can send the positioning measurements to the positioning node. <FIG> operation <NUM> is an example of the operations of block <NUM>. In some embodiments, performing the measurements (e.g., in block <NUM>) can include the operations of sub-block <NUM>, where the first RAN node can combine measurements of UL-RS transmitted by the UE according to two different UL-RS configurations based on the same UE transmit antenna configuration.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the first RAN node can receive, from the positioning node, a request for the UE to perform at least one of the following measurements:.

In block <NUM>, the first RAN node can obtain the requested measurements from the UE. In block <NUM>, the first RAN node can send, to the positioning node, a response including the requested measurements. <FIG> operations 2a-2b are examples of the operations of blocks <NUM>-<NUM>.

In addition, <FIG> is a flow diagram of an exemplary method (e.g., procedure) for a user equipment (UE) configured to support positioning in a radio access network (RAN), according to various exemplary embodiments of the present disclosure. The exemplary method can be performed by a user equipment (UE, e.g., wireless device, IoT device, etc. or components thereof), such as described herein with reference to other figures.

The exemplary method can include the operations of block <NUM>, where the UE can receive, from a first RAN node, a plurality of UL-RS configurations corresponding to first and second spatial relations. The UL-RS configurations can include the first and second spatial relations. The first spatial relations are between DL-RS and UL-RS used for positioning in a first cell served by the first RAN node, where the first cell is a serving cell for the UE. The second spatial relations are between DL-RS and UL-RS used for positioning in one or more second cells served by a second RAN node, where the second cells are neighbor cells to the first cell. <FIG> operation <NUM> is an example of the operations of block <NUM>.

The exemplary method can also include the operations of block <NUM>, where the UE can determine transmit antenna configurations corresponding to the respective UL-RS configurations. <FIG> operation <NUM> is an example of the operations of block <NUM>. The exemplary method can also include the operations of block <NUM>, where the UE can transmit UL-RS according to the respective UL-RS configurations and the corresponding transmit antenna configurations.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the UE can perform measurements that include first measurements of DL-RS associated with the first cell and/or second measurements of DL-RS associated with the second cells. In block <NUM>, the UE can send the measurements to the first RAN node or to a positioning node. <FIG> operations 2a-2b are examples of the operations of blocks <NUM>-<NUM>. Such information can be used by the positioning node, for example, to determine the spatial relations received in block <NUM>.

In some of these embodiments, the first and/or second measurements (e.g., performed in block <NUM>) are positioning measurements and are sent to the positioning node. In other embodiments, the first and/or second measurements are sent to the first RAN node and are radio resource management (RRM) measurements and/or beam sweep measurements.

In some embodiments, the determining operations of block <NUM> can include the operations of sub-blocks <NUM>-<NUM>, applied to each UL-RS configuration (e.g., received in block <NUM>). In sub-block <NUM>, the UE can determine a receive antenna configuration for a DL-RS associated with the spatial relation included in the UL-RS configuration. In sub-block <NUM>, the UE can, based on the spatial relation, determine a transmit antenna configuration that results in a transmit beam that is directionally aligned with a receive beam resulting from the receive antenna configuration.

In some of these embodiments, at least two of the transmit antenna configurations can be substantially the same. In such embodiments, the exemplary method can also include the operations of block <NUM>, where the UE can send, to the first RAN node, a response including one or more of the following:.

In some embodiments, the transmitting operations in block <NUM> can include the operations of sub-blocks <NUM>-<NUM>. In sub-block <NUM>, the UE can transmit one or more first UL-RS based on respective one or more first spatial relations associated with the first cell served by the first RAN node. In sub-block <NUM>, the UE can transmit one or more second UL-RS based on respective one or more second spatial relations associated with the second cells served by the second RAN node.

Although various embodiments are described above in terms of methods, techniques, and/or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and/or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc..

<FIG> shows a block diagram of an exemplary wireless device or user equipment (UE) <NUM> (referred to hereinafter as "UE <NUM>") according to various embodiments of the present disclosure, including those described above with reference to other figures. For example, UE <NUM> can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.

UE <NUM> can include a processor <NUM> (also referred to as "processing circuitry") that can be operably connected to a program memory <NUM> and/or a data memory <NUM> via a bus <NUM> that can comprise parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art. Program memory <NUM> can store software code, programs, and/or instructions (collectively shown as computer program product <NUM> in <FIG>) that, when executed by processor <NUM>, can configure and/or facilitate UE <NUM> to perform various operations, including operations corresponding to various exemplary methods described herein. As part of or in addition to such operations, execution of such instructions can configure and/or facilitate UE <NUM> to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as those commonly known as <NUM>/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, 1xRTT, CDMA2000, <NUM> WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver <NUM>, user interface <NUM>, and/or control interface <NUM>.

As another example, processor <NUM> can execute program code stored in program memory <NUM> that corresponds to MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and/or LTE). As a further example, processor <NUM> can execute program code stored in program memory <NUM> that, together with radio transceiver <NUM>, implements corresponding PHY layer protocols, such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single-Carrier Frequency Division Multiple Access (SC-FDMA). As another example, processor <NUM> can execute program code stored in program memory <NUM> that, together with radio transceiver <NUM>, implements device-to-device (D2D) communications with other compatible devices and/or UEs.

Program memory <NUM> can also include software code executed by processor <NUM> to control the functions of UE <NUM>, including configuring and controlling various components such as radio transceiver <NUM>, user interface <NUM>, and/or control interface <NUM>. Program memory <NUM> can also comprise one or more application programs and/or modules comprising computer-executable instructions embodying any of the exemplary methods described herein. Such software code can be specified or written using any known or future developed programming language, such as e.g., Java, C++, C, Objective C, HTML, XHTML, machine code, and Assembler, as long as the desired functionality, e.g., as defined by the implemented method steps, is preserved. In addition, or as an alternative, program memory <NUM> can comprise an external storage arrangement (not shown) remote from UE <NUM>, from which the instructions can be downloaded into program memory <NUM> located within or removably coupled to UE <NUM>, so as to enable execution of such instructions.

Data memory <NUM> can include memory area for processor <NUM> to store variables used in protocols, configuration, control, and other functions of UE <NUM>, including operations corresponding to, or comprising, any of the exemplary methods described herein. Moreover, program memory <NUM> and/or data memory <NUM> can include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. Furthermore, data memory <NUM> can comprise a memory slot by which removable memory cards in one or more formats (e.g., SD Card, Memory Stick, Compact Flash, etc.) can be inserted and removed.

Persons of ordinary skill will recognize that processor <NUM> can include multiple individual processors (including, e.g., multi-core processors), each of which implements a portion of the functionality described above. In such cases, multiple individual processors can be commonly connected to program memory <NUM> and data memory <NUM> or individually connected to multiple individual program memories and or data memories. More generally, persons of ordinary skill in the art will recognize that various protocols and other functions of UE <NUM> can be implemented in many different computer arrangements comprising different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and/or programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.

Radio transceiver <NUM> can include radio-frequency transmitter and/or receiver functionality that facilitates the UE <NUM> to communicate with other equipment supporting like wireless communication standards and/or protocols. In some exemplary embodiments, the radio transceiver <NUM> includes one or more transmitters and one or more receivers that enable UE <NUM> to communicate according to various protocols and/or methods proposed for standardization by 3GPP and/or other standards-setting organizations (SSOs). For example, such functionality can operate cooperatively with processor <NUM> to implement a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies, such as described herein with respect to other figures.

In some exemplary embodiments, radio transceiver <NUM> includes one or more transmitters and one or more receivers that can facilitate the UE <NUM> to communicate with various LTE, LTE-Advanced (LTE-A), and/or NR networks according to standards promulgated by 3GPP. In some exemplary embodiments of the present disclosure, the radio transceiver <NUM> includes circuitry, firmware, etc. necessary for the UE <NUM> to communicate with various NR, NR-U, LTE, LTE-A, LTE-LAA, UMTS, and/or GSM/EDGE networks, also according to 3GPP standards. In some embodiments, radio transceiver <NUM> can include circuitry supporting D2D communications between UE <NUM> and other compatible devices.

In some embodiments, radio transceiver <NUM> includes circuitry, firmware, etc. necessary for the UE <NUM> to communicate with various CDMA2000 networks, according to 3GPP2 standards. In some embodiments, the radio transceiver <NUM> can be capable of communicating using radio technologies that operate in unlicensed frequency bands, such as IEEE <NUM> WiFi that operates using frequencies in the regions of <NUM>, <NUM>, and/or <NUM>. In some embodiments, radio transceiver <NUM> can include a transceiver that is capable of wired communication, such as by using IEEE <NUM> Ethernet technology. The functionality particular to each of these embodiments can be coupled with and/or controlled by other circuitry in the UE <NUM>, such as the processor <NUM> executing program code stored in program memory <NUM> in conjunction with, and/or supported by, data memory <NUM>.

User interface <NUM> can take various forms depending on the particular embodiment of UE <NUM>, or can be absent from UE <NUM> entirely. In some embodiments, user interface <NUM> can comprise a microphone, a loudspeaker, slidable buttons, depressible buttons, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and/or any other user-interface features commonly found on mobile phones. In other embodiments, the UE <NUM> can comprise a tablet computing device including a larger touchscreen display. In such embodiments, one or more of the mechanical features of the user interface <NUM> can be replaced by comparable or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using the touchscreen display, as familiar to persons of ordinary skill in the art. In other embodiments, the UE <NUM> can be a digital computing device, such as a laptop computer, desktop computer, workstation, etc. that comprises a mechanical keyboard that can be integrated, detached, or detachable depending on the particular embodiment. Such a digital computing device can also comprise a touch screen display. Many exemplary embodiments of the UE <NUM> having a touch screen display are capable of receiving user inputs, such as inputs related to exemplary methods described herein or otherwise known to persons of ordinary skill.

In some embodiments, UE <NUM> can include an orientation sensor, which can be used in various ways by features and functions of UE <NUM>. For example, the UE <NUM> can use outputs of the orientation sensor to determine when a user has changed the physical orientation of the UE <NUM>'s touch screen display. An indication signal from the orientation sensor can be available to any application program executing on the UE <NUM>, such that an application program can change the orientation of a screen display (e.g., from portrait to landscape) automatically when the indication signal indicates an approximate <NUM>-degree change in physical orientation of the device. In this exemplary manner, the application program can maintain the screen display in a manner that is readable by the user, regardless of the physical orientation of the device. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.

A control interface <NUM> of the UE <NUM> can take various forms depending on the particular exemplary embodiment of UE <NUM> and of the particular interface requirements of other devices that the UE <NUM> is intended to communicate with and/or control. For example, the control interface <NUM> can comprise an RS-<NUM> interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("Firewire") interface, an I<NUM>C interface, a PCMCIA interface, or the like. In some exemplary embodiments of the present disclosure, control interface <NUM> can comprise an IEEE <NUM> Ethernet interface such as described above. In some exemplary embodiments of the present disclosure, the control interface <NUM> can comprise analog interface circuitry including, for example, one or more digital-to-analog converters (DACs) and/or analog-to-digital converters (ADCs).

Persons of ordinary skill in the art can recognize the above list of features, interfaces, and radio-frequency communication standards is merely exemplary, and not limiting to the scope of the present disclosure. In other words, the UE <NUM> can comprise more functionality than is shown in <FIG> including, for example, a video and/or still-image camera, microphone, media player and/or recorder, etc. Moreover, radio transceiver <NUM> can include circuitry necessary to communicate using additional radio-frequency communication standards including Bluetooth, GPS, and/or others. Moreover, the processor <NUM> can execute software code stored in the program memory <NUM> to control such additional functionality. For example, directional velocity and/or position estimates output from a GPS receiver can be available to any application program executing on the UE <NUM>, including any program code corresponding to and/or embodying any exemplary embodiments (e.g., of methods) described herein.

<FIG> shows a block diagram of an exemplary network node <NUM> according to various embodiments of the present disclosure, including those described above with reference to other figures. For example, exemplary network node <NUM> can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein. In some exemplary embodiments, network node <NUM> can comprise a base station, eNB, gNB, or one or more components thereof. For example, network node <NUM> can be configured as a central unit (CU) and one or more distributed units (DUs) according to NR gNB architectures specified by 3GPP. More generally, the functionally of network node <NUM> can be distributed across various physical devices and/or functional units, modules, etc..

Network node <NUM> can include processor <NUM> (also referred to as "processing circuitry") that is operably connected to program memory <NUM> and data memory <NUM> via bus <NUM>, which can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.

Program memory <NUM> can store software code, programs, and/or instructions (collectively shown as computer program product <NUM> in <FIG>) that, when executed by processor <NUM>, can configure and/or facilitate network node <NUM> to perform various operations, including operations corresponding to various exemplary methods described herein. As part of and/or in addition to such operations, program memory <NUM> can also include software code executed by processor <NUM> that can configure and/or facilitate network node <NUM> to communicate with one or more other UEs or network nodes using other protocols or protocol layers, such as one or more of the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and/or NR, or any other higher-layer (e.g., NAS) protocols utilized in conjunction with radio network interface <NUM> and/or core network interface <NUM>. By way of example, core network interface <NUM> can comprise the S1 or NG interface and radio network interface <NUM> can comprise the Uu interface, as standardized by 3GPP. Program memory <NUM> can also comprise software code executed by processor <NUM> to control the functions of network node <NUM>, including configuring and controlling various components such as radio network interface <NUM> and core network interface <NUM>.

Data memory <NUM> can comprise memory area for processor <NUM> to store variables used in protocols, configuration, control, and other functions of network node <NUM>. As such, program memory <NUM> and data memory <NUM> can comprise non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage, or a combination thereof. Persons of ordinary skill in the art will recognize that processor <NUM> can include multiple individual processors (not shown), each of which implements a portion of the functionality described above. In such case, multiple individual processors may be commonly connected to program memory <NUM> and data memory <NUM> or individually connected to multiple individual program memories and/or data memories. More generally, persons of ordinary skill will recognize that various protocols and other functions of network node <NUM> may be implemented in many different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuitry, programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.

Radio network interface <NUM> can comprise transmitters, receivers, signal processors, ASICs, antennas, beamforming units, and other circuitry that enables network node <NUM> to communicate with other equipment such as, in some embodiments, a plurality of compatible user equipment (UE). In some embodiments, interface <NUM> can also enable network node <NUM> to communicate with compatible satellites of a satellite communication network. In some exemplary embodiments, radio network interface <NUM> can comprise various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and/or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc.; improvements thereto such as described herein above; or any other higher-layer protocols utilized in conjunction with radio network interface <NUM>. According to further exemplary embodiments of the present disclosure, the radio network interface <NUM> can comprise a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies. In some embodiments, the functionality of such a PHY layer can be provided cooperatively by radio network interface <NUM> and processor <NUM> (including program code in memory <NUM>).

Core network interface <NUM> can comprise transmitters, receivers, and other circuitry that enables network node <NUM> to communicate with other equipment in a core network such as, in some embodiments, circuit-switched (CS) and/or packet-switched Core (PS) networks. In some embodiments, core network interface <NUM> can comprise the S1 interface standardized by 3GPP. In some embodiments, core network interface <NUM> can comprise the NG interface standardized by 3GPP. In some exemplary embodiments, core network interface <NUM> can comprise one or more interfaces to one or more AMFs, SMFs, SGWs, MMEs, SGSNs, GGSNs, and other physical devices that comprise functionality found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks that are known to persons of ordinary skill in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, lower layers of core network interface <NUM> can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethernet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.

In some embodiments, network node <NUM> can include hardware and/or software that configures and/or facilitates network node <NUM> to communicate with other network nodes in a RAN (also referred to as a "wireless network"), such as with other eNBs, gNBs, ng-eNBs, en-gNBs, IAB nodes, etc. Such hardware and/or software can be part of radio network interface <NUM> and/or core network interface <NUM>, or it can be a separate functional unit (not shown). For example, such hardware and/or software can configure and/or facilitate network node <NUM> to communicate with other RAN nodes via the X2 or Xn interfaces, as standardized by 3GPP.

OA&M interface <NUM> can comprise transmitters, receivers, and other circuitry that enables network node <NUM> to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of network node <NUM> or other network equipment operably connected thereto. Lower layers of OA&M interface <NUM> can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethernet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art. Moreover, in some embodiments, one or more of radio network interface <NUM>, core network interface <NUM>, and OA&M interface <NUM> may be multiplexed together on a single physical interface, such as the examples listed above.

<FIG> is a block diagram of an exemplary communication network configured to provide over-the-top (OTT) data services between a host computer and a user equipment (UE), according to various exemplary embodiments of the present disclosure. UE <NUM> can communicate with radio access network (RAN, also referred to as "wireless network") <NUM> over radio interface <NUM>, which can be based on protocols described above including, e.g., LTE, LTE-A, and <NUM>/NR. For example, UE <NUM> can be configured and/or arranged as shown in other figures discussed above.

RAN <NUM> can include one or more terrestrial network nodes (e.g., base stations, eNBs, gNBs, controllers, etc.) operable in licensed spectrum bands, as well one or more network nodes operable in unlicensed spectrum (using, e.g., LAA or NR-U technology), such as a <NUM>-GHz band and/or a <NUM>-GHz band. In such cases, the network nodes comprising RAN <NUM> can cooperatively operate using licensed and unlicensed spectrum. In some embodiments, RAN <NUM> can include, or be capable of communication with, one or more satellites comprising a satellite access network.

RAN <NUM> can further communicate with core network <NUM> according to various protocols and interfaces described above. For example, one or more apparatus (e.g., base stations, eNBs, gNBs, etc.) comprising RAN <NUM> can communicate to core network <NUM> via core network interface <NUM> described above. In some exemplary embodiments, RAN <NUM> and core network <NUM> can be configured and/or arranged as shown in other figures discussed above. For example, eNBs comprising an E-UTRAN <NUM> can communicate with an EPC core network <NUM> via an S1 interface. As another example, gNBs and ng-eNBs comprising an NG-RAN <NUM> can communicate with a 5GC core network <NUM> via an NG interface.

Core network <NUM> can further communicate with an external packet data network, illustrated in <FIG> as Internet <NUM>, according to various protocols and interfaces known to persons of ordinary skill in the art. Many other devices and/or networks can also connect to and communicate via Internet <NUM>, such as exemplary host computer <NUM>. In some exemplary embodiments, host computer <NUM> can communicate with UE <NUM> using Internet <NUM>, core network <NUM>, and RAN <NUM> as intermediaries. Host computer <NUM> can be a server (e.g., an application server) under ownership and/or control of a service provider. Host computer <NUM> can be operated by the OTT service provider or by another entity on the service provider's behalf.

For example, host computer <NUM> can provide an over-the-top (OTT) packet data service to UE <NUM> using facilities of core network <NUM> and RAN <NUM>, which can be unaware of the routing of an outgoing/incoming communication to/from host computer <NUM>. Similarly, host computer <NUM> can be unaware of routing of a transmission from the host computer to the UE, e.g., the routing of the transmission through RAN <NUM>. Various OTT services can be provided using the exemplary configuration shown in <FIG> including, e.g., streaming (unidirectional) audio and/or video from host computer to UE, interactive (bidirectional) audio and/or video between host computer and UE, interactive messaging or social communication, interactive virtual or augmented reality, etc..

The exemplary network shown in <FIG> can also include measurement procedures and/or sensors that monitor network performance metrics including data rate, latency and other factors that are improved by exemplary embodiments disclosed herein. The exemplary network can also include functionality for reconfiguring the link between the endpoints (e.g., host computer and UE) in response to variations in the measurement results. Such procedures and functionalities are known and practiced; if the network hides or abstracts the radio interface from the OTT service provider, measurements can be facilitated by proprietary signaling between the UE and the host computer.

The embodiments described herein provide novel techniques for configuring and utilizing spatial relations of reference signals that facilitate positioning of UEs based on measurements of these signals. Such techniques can facilitate more accurate and/or more timely UE location estimates by a positioning node (e.g., LMF), as well as reduced network signaling complexity. Such advantages can be very important in certain applications, such as high-precision/high-accuracy positioning and/or low-complexity positioning. When used in NR UEs (e.g., UE <NUM>) and gNBs (e.g., gNBs comprising RAN <NUM>), embodiments described herein can provide various improvements, benefits, and/or advantages that facilitate the use of location-based OTT services. As a consequence, this improves the performance of these services as experienced by OTT service providers and end-users, including more precise delivery of services with lower latency without excessive UE energy consumption or other reductions in user experience.

Furthermore, functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.

In addition, certain terms used in the present disclosure, including the specification, drawings and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g., data and information. It should be understood that, although these words and/or other words that can be synonymous to one another, can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.

As used herein unless expressly stated to the contrary, the phrases "at least one of" and "one or more of," followed by a conjunctive list of enumerated items (e.g., "A and B", "A, B, and C"), are intended to mean "at least one item, with each item selected from the list consisting of" the enumerated items. For example, "at least one of A and B" is intended to mean any of the following: A; B; A and B. Likewise, "one or more of A, B, and C" is intended to mean any of the following: A; B; C; A and B; B and C; A and C; A, B, and C.

Claim 1:
A method for a positioning node coupled to a radio access network, RAN, the method comprising:
determining (<NUM>) first spatial relations between downlink reference signals, DL-RS, and uplink reference signals, UL-RS, used for positioning in a first cell served by a first RAN node, wherein the first cell is a serving cell for a user equipment, UE;
determining (<NUM>) second spatial relations between DL-RS and UL-RS used for positioning in one or more second cells served by a second RAN node, wherein the second cells are neighbor cells to the first cell; and
configuring (<NUM>) the UE to transmit UL-RS according to the first and second spatial relations.