Method and device for defining and signaling a preconfigured positioning reference signal (PRS) - Patents.com
Patent Information
- Application Number
- JP2023578884
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-06-22
- Filing Date
- 2022-06-20
- Publication Date
- 2025-06-30
- Estimated Expiration
- 2042-06-20
AI Technical Summary
Current 5G NR networks face challenges in efficiently transmitting positioning reference signals (PRS) due to issues with on-demand PRS configurations, including unclear responses to UE requests for specific PRS configurations and insufficient criteria for selecting PRS settings, leading to inefficient energy consumption and suboptimal positioning accuracy.
Implement a system that allows UEs and RAN nodes to select and configure PRS settings based on predefined configurations, differentiated by parameters such as transmission periodicity, bandwidth, and energy consumption, using selection rules to ensure efficient and network-friendly PRS transmission.
This approach enhances UE positioning accuracy by selecting suitable PRS settings for multiple UEs, reduces energy consumption by avoiding unnecessary PRS transmissions, and adapts to changing network conditions, providing a flexible and efficient technique for on-demand PRS configurations.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates generally to wireless communication networks, and more particularly to network transmission of positioning reference signals (PRS) that can be used to determine the geographic location of a user equipment (UE). [Background technology]
[0002] Currently, the fifth generation of cellular systems ("5G"), also called New Radio (NR), is being standardized within the Third Generation Partnership Project (3GPP). NR is being developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced Mobile Broadband (eMBB), machine-based communications (MTC), ultra-reliable low-latency communications (URLLC), sidelink device-to-device (D2D), and several other use cases.
[0003] FIG. 1 illustrates an example high-level diagram of a 5G network architecture consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198. The NG-RAN 199 may include a set of gNBs connected to the 5GC via one or more NG interfaces, such as g Node Bs (gNBs) 100, 150 connected via interfaces 102, 152, respectively. Additionally, the gNBs may be connected to each other via one or more Xn interfaces, such as the Xn interface 140 between gNB 100 and gNB 150. With respect to the NR interface to the UE, each of the gNBs may support Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination thereof.
[0004] The NG-RAN 199 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 the interfaces between the NG-RAN logical nodes, are specified as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the related TNL protocols and functions are specified. The TNL provides services for user plane transport and signaling transport.
[0005] The NG RAN logical node shown in FIG. 1 includes a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 100 includes gNB-CU 110 and gNB-DU 120 and 130. The CU is a logical node that hosts higher layer protocols and performs various gNB functions, such as controlling the operation of the DU, and the DU is a logical node that hosts lower layer protocols and can include various subsets of gNB functions. Thus, each of the CU and DU can include various circuits required to perform their respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power supply circuits.
[0006] The gNB-CU connects to the gNB-DU on a respective F1 logical interface, such as interfaces 122 and 132 shown in Figure 1. The gNB-CU and connected gNB-DU only appear as gNBs to other gNBs and 5GCs. In other words, the F1 interface is not visible beyond the gNB-CU.
[0007] 5G / NR technology shares many similarities with fourth-generation (4G) Long-Term Evolution (LTE) technology. For example, NR uses cyclic prefix orthogonal frequency division multiplexing (OFDM) 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 physical resources and NR UL physical resources are organized into equal-sized, 1 ms subframes. The subframes are further divided into multiple slots of equal duration, each slot containing multiple OFDM-based symbols. However, time-frequency resources may be configured much more flexibly for NR cells than for LTE cells. For example, rather than a fixed 15 kHz OFDM subcarrier spacing (SCS) as in LTE, the NR SCS may range from 15 to 240 kHz, with even larger SCSs being considered for future NR releases.
[0008] In addition to providing coverage via cells, as in LTE, NR networks also provide coverage via "beams." Generally, a downlink (DL, i.e., network to UE) "beam" is a coverage area of a network-transmitted reference signal (RS) that can be measured or monitored by a UE. In NR, for example, the RS can include any of the synchronization signal / PBCH block (SSB), channel state information RS (CSI-RS), tertiary reference signal (or any other synchronization signal), positioning RS (PRS), demodulation-oriented RS (DMRS), phase tracking RS (PTRS), etc. Generally, the SSB is available to all UEs regardless of the state of their connection with the network, while the other RSs (e.g., CSI-RS, DM-RS, PTRS) are associated with a particular UE that has a network connection.
[0009] 3GPP standards provide various ways to position (e.g., determine the position, locate, and / or determine the location of) UEs operating in NR networks. Generally, a positioning node configures a target device (e.g., UE) and / or a radio network node (RNN, e.g., gNB, ng-eNB, or an RNN dedicated to positioning measurements) to perform one or more positioning measurements according to one or more positioning methods. For example, the positioning measurements may include timing (and / or timing difference) measurements for UE, network, and / or satellite transmissions. The positioning measurements are used by the target device, the measurement node, and / or the positioning node to determine the location of the target device.
[0010] Positioning in NR Rel-16 is developed based on network transmitted positioning reference signals (PRS), which can enhance location capabilities. For example, PRS transmission in low and high frequency bands (i.e., below and above 6 GHz) and the use of large antenna arrays provide additional flexibility to significantly improve positioning accuracy. Further enhancements are planned for NR Rel-17, including "on-demand PRS," whereby a UE can request the network to transmit a PRS in a configuration that facilitates UE positioning measurements and (optionally) position determination. Summary of the Invention
[0011] However, applicant has recognized that there are various issues, problems, and / or difficulties associated with transmitting PRS in the split-node architecture illustrated in FIG.
[0012] Embodiments of the present disclosure provide certain improvements to positioning of UEs in wireless networks, such as by providing, enabling, and / or facilitating solutions to overcome the example problems summarized above and described in more detail below.
[0013] Embodiments include a method (eg, a procedure) for a UE configured for positioning in a radio access network (RAN).
[0014] These example methods may include receiving, from a positioning node associated with the RAN, a plurality of configurations for a PRS transmitted by a node of the RAN and a corresponding plurality of configuration indexes associated with the plurality of configurations. In other words, each configuration is represented by, corresponds to, and / or is associated with a configuration index, and vice versa. For example, the positioning node may be an LMF. These example methods may also include determining a need to receive the PRS and selecting one or more of the plurality of configurations based on one or more selection rules. These example methods may also include transmitting, to the positioning node, one or more requests for a TRS transmission by the RAN. The one or more requests include one or more configuration indexes associated with the selected one or more configurations.
[0015] In various embodiments, the plurality of settings may include the following characteristics or parameters: ·PRS transmission periodicity, PRS transmission bandwidth, The number of PRS transmit frequency layers used, The particular PRS transmit frequency layer being used, · number of RAN nodes sending PRS, The particular RAN node transmitting the PRS; The geographical configuration of the RAN nodes transmitting the PRS; Number of PRS resource sets per node, · Number of PRSs per PRS resource set, the energy consumption and / or signaling overhead associated with transmitting the PRS according to the configuration; the relevant geographic area; Positioning spatial dimension, Positioning accuracy Quality of Service (QoS), as well as Positioning Latency QoS may be distinguished from one another based on one or more of:
[0016] In some embodiments, these example methods may also include receiving, from the positioning node, an indication of a characteristic or parameter by which the plurality of configurations are distinguished. In such embodiments, selecting one or more of the plurality of configurations may be based on the indicated characteristic or parameter. In some embodiments, these example methods may also include receiving a selection rule from the positioning node.
[0017] In some embodiments, the plurality of configurations includes a first configuration including default values for configuration parameters and one or more further configurations. Each further configuration includes only configuration parameters of the configuration parameters that have values different from the default values. In some of these embodiments, the first configuration may be received via a first broadcasted system information block (SIB), and the one or more further configurations may be received via a second broadcasted SIB. In some of these embodiments, the first SIB indicates that the first configuration is one of a default configuration or an active configuration.
[0018] In some embodiments, each request includes an index associated with a selected configuration. In some of these embodiments, the selection rule includes a sequential order in which the respective configurations may be requested by the UE.
[0019] In others of these embodiments, the one or more requests include an initial request and one or more subsequent requests, and the selection rule includes a first rule that identifies a first subset of settings that may be requested by the UE in the initial request and a second rule that identifies a second subset of settings that may be requested by the UE in the subsequent request. In some variations, the first subset of settings includes a first setting that requires the lowest energy for transmitting the PRS, and the second subset includes at least one setting that requires more energy for transmitting the PRS than the first setting.
[0020] In some examples of these variations, the act of selecting may include determining whether positioning based on PRS transmissions according to a first configuration will satisfy a positioning quality of service (QoS) threshold, selecting the first configuration when it is determined that the positioning QoS threshold will be satisfied, and selecting the second subset of configurations when it is determined that the positioning QoS threshold will not be satisfied. In some cases, the positioning QoS threshold is related to accuracy and / or latency.
[0021] In other examples of these variations, the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting. Further, the one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request, and the second rule identifies that the second setting may be selected for the first subsequent request and that the third setting may be selected for the second subsequent request.
[0022] In other embodiments, the one or more requests include a single request including at least two configuration indexes. The selection rule includes a third rule that indicates one of more configuration parameters that must be common between the at least two configurations associated with the at least two configuration indexes included in the single request. In some variations, the third rule indicates that at least the following parameters must be common between the at least two configurations: PRS transmission periodicity and the particular RAN node transmitting the PRS.
[0023] In some of these embodiments, these example methods may also include performing positioning measurements on PRSs that are coherently transmitted according to at least two configurations associated with the at least two configuration indexes included in the single request.
[0024] Another embodiment includes a method (eg, a procedure) for a positioning node associated with a RAN.
[0025] The example methods may include determining a plurality of configurations for a PRS transmitted by a node of the RAN. The plurality of configurations are associated with a corresponding plurality of configuration indexes. The example methods may also include sending the plurality of configurations and the associated plurality of configuration indexes to the RAN node and to a UE operating in the RAN. The example methods may also include receiving one or more requests for PRS transmission by the RAN from the UE. The one or more requests include one or more of the plurality of configuration indexes associated with one or more of the plurality of configurations selected by the UE.
[0026] In various embodiments, the multiple configurations may be distinguished from one another based on any of the characteristics or parameters summarized above with respect to the UE embodiments. In some embodiments, these example methods may also include sending to the UE an indication of the characteristics or parameters by which the multiple configurations are distinguished.
[0027] In some embodiments, the plurality of configurations may include a first configuration including default values for configuration parameters and one or more further configurations. Each further configuration includes only configuration parameters of the configuration parameters that have values different from the default values. In some of these embodiments, the first configuration may be sent by the RAN via broadcast of a first SIB, and the one or more further configurations may be sent by the RAN via broadcast of a second SIB. In some of these embodiments, the first SIB indicates that the first configuration is one of a default configuration or an active configuration.
[0028] In some embodiments, these example methods may also include configuring the RAN node to transmit the PRS according to one of the one or more configurations selected by the UE or one or more further configurations selected by the positioning node. In some of these embodiments, these example methods may also include sending to the UE a selection rule for selecting between the multiple configurations.
[0029] In some of these embodiments, each request includes an index associated with a configuration selected by the UE. In some variations of these embodiments, the selection rules may include a sequential order in which the respective configurations may be requested by the UE.
[0030] In other variations of these embodiments, the one or more requests may include an initial request and one or more subsequent requests, and the selection rule may include a first rule that identifies a first subset of settings that may be requested by the UE in the initial request and a second rule that identifies a second subset of settings that may be requested by the UE in the subsequent request.
[0031] In some variations, the first subset includes a first configuration that requires the lowest energy for transmitting the PRS, and the second subset includes at least one configuration that requires more energy for transmitting the PRS than the first configuration. In some examples of these variations, the selection rule can include a positioning QoS threshold for selecting between the first configuration and the second subset of configurations. In some cases, the positioning QoS threshold is related to accuracy and / or latency.
[0032] In other examples of these variations, the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting. Further, the one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request, and the second rule identifies that the second setting may be selected for the first subsequent request and that the third setting may be selected for the second subsequent request.
[0033] In others of these embodiments, the one or more requests include a single request including at least two configuration indexes. The selection rule includes a third rule that indicates one of more configuration parameters that must be common between the at least two configurations associated with the at least two configuration indexes included in the single request. In some variations, the third rule indicates that at least the following parameters must be common between the at least two configurations: PRS transmission periodicity and the particular RAN node transmitting the PRS. In some of these embodiments, configuring the RAN node includes configuring a plurality of RAN nodes to coherently transmit the PRS according to the at least two configurations associated with the at least two configuration indexes included in the single request.
[0034] In some embodiments, determining the plurality of configurations includes obtaining a default configuration for PRS transmission and determining the plurality of configurations (e.g., sent to the UE and the RAN node) for: Measurements made by the UE on the transmitted PRS according to default settings, · the node's ability to transmit PRS, The number of UEs operating in the RAN, and One or more distinguishing characteristics or parameters (e.g., as described above) and determining based on the
[0035] In some embodiments, determining the plurality of settings comprises: Measurements made by the UE on PRS transmitted according to multiple configurations; -Updated capabilities of the nodes, The updated number of UEs operating in the RAN, and one or more distinguishing characteristics or parameters The method may include adapting the method based on one or more of:
[0036] Another embodiment includes a method (e.g., a procedure) for a RAN node.
[0037] These example methods may include receiving, from a positioning node (e.g., an LMF) associated with the RAN, a plurality of configurations for a PRS transmitted by a node of the RAN and a corresponding plurality of configuration indexes associated with the plurality of configurations. In other words, each configuration is represented by, corresponds to, and / or is associated with a configuration index, and vice versa. These example methods may also include thereafter receiving, from the positioning node, one or more requests for a PRS transmission. The one or more requests include one or more of the plurality of configuration indexes. These example methods may also include transmitting the PRS according to one or more of the configurations associated with the one or more configuration indexes included in the one or more requests.
[0038] In various embodiments, the multiple configurations may be distinguished from one another based on any of the characteristics or parameters described above with respect to the UE embodiment.
[0039] In some embodiments, the plurality of configurations may include a first configuration including a default value for a configuration parameter and one or more additional configurations. Each additional configuration includes only configuration parameters among the configuration parameters that have a value different from the default value. In some of these embodiments, the exemplary methods may also include broadcasting the first configuration in a first SIB and broadcasting the one or more additional configurations in a second SIB. In some of these embodiments, the first SIB indicates that the first configuration is one of a default configuration or an active configuration.
[0040] In some embodiments, the one or more requests include an initial request and one or more subsequent requests, and the configurations include a first subset of settings that may be requested by the UE in the initial request and a second subset of settings that may be requested by the UE in the subsequent requests. In some of these embodiments, the first subset of settings includes a first setting that requires the lowest energy for transmitting the PRS, and the second subset includes at least one setting that requires more energy for transmitting the PRS than the first setting. In some variations, the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting.
[0041] In other embodiments, the one or more requests include a single request including at least two configuration indexes. At least the PRS transmission periodicity is common between the at least two configurations associated with the at least two configuration indexes included in the single request. In some of these embodiments, transmitting the PRS can coherently transmit the PRS according to the at least two configurations associated with the at least two configuration indexes included in the single request.
[0042] Other embodiments include a UE (e.g., a wireless device, etc.), a positioning node (e.g., an LMF, an E-SMLC, a SUPL node, etc.), and a RAN node (e.g., a base station, an eNB, a gNB, an ng-eNB, a TRP, etc.) configured to perform operations corresponding to any of the example methods described herein. Other embodiments include a non-transitory computer-readable medium storing program instructions that, when executed by a processing circuit, configure such a UE, positioning node, or RAN node to perform operations corresponding to any of the example methods described herein.
[0043] The embodiments described herein provide flexible and efficient techniques for supporting on-demand PRS transmissions when network conditions change. The embodiments can also be used to select a PRS configuration that is suitable for many UEs, not just one, which provides more efficient UE positioning based on DL PRS transmissions. The embodiments can also reduce energy consumption of RAN nodes by avoiding transmission of PRS resources that are not needed.
[0044] These and other objects, features and advantages of the embodiments of the present disclosure will become apparent from a reading of the following detailed description in light of the drawings briefly described below. [Brief description of the drawings]
[0045] [Figure 1] FIG. 1 is a high-level diagram of an example 5G / NR network architecture. [Diagram 2] FIG. 1 is a high-level diagram of an example 5G / NR network architecture. [Diagram 3] A diagram illustrating exemplary NR user plane (UP) and control plane (CP) protocol layers. [Figure 4] FIG. 1 is a block diagram showing a high-level architecture for UE positioning in an NR network. [Diagram 5] FIG. 11 is a signal flow diagram for an example multi-RTT positioning procedure. [Figure 6] FIG. 2 illustrates an example partitioning of positioning-related functions in the split gNB architecture shown in FIG. [Figure 7] FIG. 1 illustrates an example hybrid transmit beamforming configuration. [Figure 8] 1A-B show two exemplary beam sweeping configurations with two and three subarrays, respectively. [Figure 9] A diagram showing example signaling procedures used to obtain positioning reference signal (PRS) configuration according to different scenarios. [Figure 10] A diagram showing example signaling procedures used to obtain positioning reference signal (PRS) configuration according to different scenarios. [Figure 11] FIG. 13 illustrates an ASN.1 data structure for an exemplary OnDemand-PRS-ClassificationCriteria field in accordance with various embodiments of the present disclosure. [Figure 12] FIG. 1 illustrates a signaling flow between a positioning node (e.g., an LMF) and a RAN node (e.g., a gNB) in accordance with various embodiments of the present disclosure. [Figure 13] 1 is a flow diagram of an example method (e.g., a procedure) for a UE, in accordance with various embodiments of the present disclosure. [Figure 14] 1 is a flow diagram of an example method (e.g., procedure) for a positioning node (e.g., LMF) in accordance with various embodiments of the present disclosure. [Figure 15] FIG. 1 is a flow diagram of an example method (e.g., procedure) for a RAN node (e.g., gNB, TRP, etc.) in accordance with various embodiments of the present disclosure. [Figure 16] FIG. 1 illustrates a communication system in accordance with various embodiments of the present disclosure. [Figure 17] FIG. 2 illustrates a UE in accordance with various embodiments of the present disclosure. [Figure 18] FIG. 2 illustrates a network node according to various embodiments of the present disclosure. [Figure 19] FIG. 2 illustrates a host computing system in accordance with various embodiments of the present disclosure. [Figure 20] FIG. 1 is a block diagram of a virtualization environment in which functionality implemented by some embodiments of the present disclosure may be virtualized. [Figure 21] FIG. 1 illustrates communication between a host computing system, a network node, and a UE over multiple connections, at least one of which is wireless, in accordance with various embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0046] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.
[0047] Generally, all terms used herein should be interpreted according to the ordinary meaning of those terms in the relevant technical field, unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to a / an / the element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method and / or procedure disclosed herein need not be performed in the exact order disclosed, unless a step is expressly 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 may be applied to any other embodiment, wherever appropriate. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will become apparent from the following description.
[0048] Additionally, the following terminology is used throughout the description provided below: Wireless Node: As used herein, a "wireless node" may be either a "wireless access node" or a "wireless device." Radio Access Node: As used herein, a "radio access node" (or equivalently, a "radio network node", "radio access network node", or "RAN node") may be any node in a radio access network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, base stations (e.g., a new radio (NR) base station (gNB) in a 3GPP fifth generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), high power or macro base stations, low power base stations (e.g., micro base station, pico base station, femto base station, or home base station, etc.), radio access backhaul integrated transmission (IAB) nodes, transmission points (TPs), transmit reception points (TRPs), remote radio units (RRUs or RRHs), and relay nodes. Core Network Node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Serving Gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a Location Management Function (LMF), etc. Wireless Device: As used herein, a "wireless device" (or "WD" for short) is any type of device that has access to (i.e., is served by) a cellular communications network by communicating wirelessly with network nodes and / or other wireless devices. Communicating wirelessly can involve sending and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. Unless otherwise noted, the term "wireless device" is used interchangeably herein with "user equipment" (or "UE" for short). Some examples of wireless devices include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), mobile telecommunications (MTC) devices, Internet of Things (IoT) devices, vehicle mounted wireless terminal devices, and the like. Network Node: As used herein, a "network node" is any node that is part of either a radio access network (e.g., radio access node or equivalent designation as described above) or a core network (e.g., core network node as described above) of a cellular communications network. Functionally, a network node is equipment that is capable of, set up, configured, and / or operative to communicate, directly or indirectly, with wireless devices and / or with other network nodes or equipment in the cellular communications network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., administration) in the cellular communications network. Base Station: As used herein, a "base station" may include a physical or logical node that transmits or controls the transmission of wireless signals, e.g., eNB, gNB, ng-eNB, en-gNB, Centralized Unit (CU) / Distributed Unit (DU), transmitting radio network node, Transmission Point (TP), Transmit Receiving Point (TRP), Remote Radio Head (RRH), Remote Radio Unit (RRU), Distributed Antenna System (DAS), relay, etc. Location Server: As used herein, a "location server" may refer to a network node with positioning functionality, e.g., the ability to provide assistance data and / or request positioning measurements and / or calculate a location based on measured positioning. A location server may or may not be part of a base station. Positioning Signal: As used herein, "positioning signal" may include any signal or channel that should be received by a UE to perform positioning measurements, such as DL reference signals, PRS, SSB, synchronization signals, DM-RS, CSI-RS, etc. Positioning measurements: As used herein, "positioning measurements" may include timing measurements (e.g., Time Difference of Arrival (TDOA), RSTD, Time of Arrival (TOA), Rx-Tx, RTT, etc.), power-based measurements (e.g., RSRP, RSRQ, SINR, etc.), and / or identifier detection / measurements (e.g., Cell ID, Beam ID, etc.) configured for a positioning method (e.g., OTDOA, E-CID, etc.). UE positioning measurements may be reported to a network node or used by the UE for positioning purposes. Positioning Beam: As used herein, a "positioning beam" may include any beam that carries at least one positioning signal and / or is used for positioning purposes, such as for measurements supporting one or more positioning methods (e.g., OTDOA, AOA, etc.). A positioning beam may have its own explicit identity or may be identified through an index associated with the particular signal that the beam carries.
[0049] The above definitions are not intended to be exclusive. In other words, various of the above terms may be explained and / or explained elsewhere in this disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and / or explanations conflict with the above definitions, the above definitions shall control.
[0050] It should be noted that the description given herein focuses on 3GPP cellular communication systems, and thus 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems. Furthermore, although the term "cell" is used herein, it should be understood that beams may be used instead of cells (especially with respect to 5G NR), and thus the concepts described herein apply equally to both cells and beams.
[0051] 2 illustrates another high-level view of an example 5G network architecture including an NG-RAN 299 and a 5GC 298. The NG-RAN 299 may include gNBs (e.g., 210a,b) and ng-eNBs (e.g., 220a,b) interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected to the 5GC 298 via an NG interface, and more specifically to an Access and Mobility Management Function (AMF, e.g., 230a,b) via respective NG-C interfaces and to a User Plane Function (UPF, e.g., 240a,b) via respective NG-U interfaces. Moreover, the AMF may communicate with one or more Policy Control Functions (PCF, e.g., 250a,b) and Network Publication Functions (NEF, e.g., NEF 260a,b).
[0052] Each of the gNBs 210 may support an NR air interface, including Frequency Division Duplex (FDD), Time Division Duplex (TDD), or a combination thereof. Each of the ng-eNBs 220 may support a Fourth Generation (4G) Long-Term Evolution (LTE) air interface. However, unlike a conventional LTE eNB, the ng-eNB 220 connects to the 5GC via an NG interface. Each of the gNBs and ng-eNBs may serve a geographic coverage area that includes one more cell, such as cells 211a-b and 221a-b shown in FIG. 2. Depending on the particular cell in which the UE 205 is located, the UE 205 may communicate with the gNB or ng-eNB serving that particular cell over an NR or LTE air interface, respectively. Although FIG. 2 illustrates the gNB and ng-eNB separately, it is also possible for a single NG-RAN node to provide both types of functionality.
[0053] Positioning related information, such as assistance data and positioning measurements, may be communicated between the network and the UE via the User Plane (UP) and Control Plane (CP). Figure 3 illustrates an example configuration of NR UP and CP protocol layers between the UE (310), gNB (320), and AMF (330), such as those illustrated in Figures 1-2. The physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, and packet data convergence protocol (PDCP) layer between the UE and gNB are common to UP and CP. The PDCP layer provides encryption / decryption, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP. Additionally, PDCP provides header compression and retransmission for UP data.
[0054] On the UP side, Internet Protocol (IP) packets arrive at the PDCP layer as Service Data Units (SDUs), which creates Protocol Data Units (PDUs) for delivery to the RLC. The Service Data Adaptation Protocol (SDAP) layer handles Quality of Service (QoS), including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS Flow Identifiers (QFIs) in UL and DL packets. The RLC layer forwards PDCP PDUs to the MAC through Logical Channels (LCHs). The RLC provides error detection / correction, concatenation, segmentation / reassembly, sequence numbering, and reordering of data forwarded to / from higher layers. The MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing to / demultiplexing from Transport Blocks (TBs), Hybrid ARQ (HARQ) error correction, and dynamic scheduling (gNB side). The PHY layer provides transport channel services to the MAC layer and handles transmissions over the NR air interface, e.g., via modulation, coding, antenna mapping, and beamforming.
[0055] On the CP side, the Non-Access Stratum (NAS) layer is between the UE and the AMF and handles UE / gNB authentication, mobility management, and security control. The RRC layer is below the NAS in the UE but terminates in the gNB instead of the AMF. The RRC controls the communication between the UE and the gNB in the air interface, as well as the mobility of the UE between cells in the NG-RAN. The RRC also broadcasts system information (SI) and performs the establishment, configuration, maintenance, and release of DRBs and signaling radio bearers (SRBs) used by the UE. In addition, the RRC controls the addition, modification, and release of carrier aggregation (CA) and dual connectivity (DC) configurations for the UE. The RRC also performs various security functions such as key management.
[0056] After the UE is powered on, the UE will be in the RRC_IDLE state until an RRC connection with the network is established, at which time the UE will transition to the RRC_CONNECTED state (e.g., where data transfer may occur). The UE returns to RRC_IDLE after the connection with the network is released. In the RRC_IDLE state, the UE's radio is active on a discontinuous reception (DRX) schedule set by higher layers. During the DRX active period (also called the "DRX on duration"), the RRC_IDLE UE receives SI broadcasts in the cell in which the UE is camped, performs measurements of neighbor cells to support cell reselection, and monitors the paging channel on the PDCCH for pages from the 5GC via the gNB. An NR UE in the RRC_IDLE state is not known to the gNB serving the cell in which the UE is camped. However, NR RRC includes an RRC_INACTIVE state in which the UE is known by the serving gNB (e.g., via the UE context). RRC_INACTIVE has some properties like the "suspended" condition used in LTE.
[0057] The three key functional elements of the 3GPP positioning architecture are the LCS client, the LCS target, and the LCS server. The LCS server is a physical or logical entity (e.g., a location server) that manages positioning for an LCS target (e.g., a UE) by collecting measurements and other location information, assisting the LCS target in measurements when necessary, and estimating the LCS target location. The LCS client is a software and / or hardware entity that interacts with the LCS server for the purpose of obtaining location information for one or more LCS targets (i.e., entities being positioned), such as a UE. The LCS client may also reside in the LCS target itself. The LCS client sends requests to obtain location information to the LCS server, which processes and serves the received requests and sends the positioning results and, optionally, a speed estimate to the LCS client. The positioning request may originate from a terminal or a network node or an external client. For example, the position calculation may be performed by an LCS server (eg, an E-SMLC or an SLP) or by an LCS target (eg, a UE).
[0058] In addition, the following positioning methods are supported in NR: · Extended Cell ID (E-CID), which utilizes information to associate the UE with the geographical area of the serving cell and additional information to determine finer granularity location. The following measurements are supported for E-CID: AoA (base station only), UE Rx-Tx time difference, Timing Advance (TA) types 1 and 2, Reference Signal Received Power (RSRP), and Reference Signal Received Quality (RSRQ). Aided GNSS. GNSS information retrieved by the UE, supported by aiding information provided to the UE by the E-SMLC. · OTDOA (Observed Time Difference of Arrival). The UE receives and measures Global Navigation Satellite System (GNSS) signals supported by aiding information provided to the UE by the E-SMLC. · UTDOA (Uplink TDOA). The UE is required to transmit a specific waveform that is detected by multiple Location Measurement Units (LMUs) (which can be standalone, co-located or embedded in the eNB) at known locations. These measurements are forwarded to the E-SMLC for multilateration. Multi-RTT: A device (e.g., UE) calculates the UE Rx-Tx time difference and the gNB calculates the gNB Rx-Tx time difference. The results are combined to find the UE location based on a round trip time (RTT) calculation. DL Angle of Departure (DL-AoD): The gNB or LMF calculates the UE angular position based on the UE DL RSRP measurements (e.g., of the PRS transmitted by the RAN node). · UL Angle of Arrival (UL-AoA): The gNB calculates the UL AoA based on measurements of the UE’s UL SRS transmission.
[0059] Additionally, in each of the positioning methods listed above, one or more of the following positioning modes may be utilized. · UE Assisted: The UE performs measurements with or without assistance from the network and sends these to the E-SMLC where location calculation can be performed. · UE based: The UE performs measurements and calculates its own location with assistance from the network. · Standalone: The UE performs measurements and calculates its own position without any network assistance.
[0060] The detailed assistance data may include information regarding network node locations, beam directions, etc. The assistance data may be provided to the UE via unicast or via broadcast.
[0061] Figure 4 is a block diagram illustrating a high-level architecture for supporting UE positioning in an NR network. The NG-RAN 420 may include nodes, such as a gNB 422 and an ng-eNB 421, similar to the architecture shown in Figure 2. Each ng-eNB may control several transmission points (TPs), such as remote radio heads. Similarly, each gNB may control several transmit reception points (TRPs). Some or all of the TPs / TRPs may be dedicated to DL-PRS for support of PRS-based TBS.
[0062] Additionally, the NG-RAN nodes communicate with the AMF 430 in 5GC via respective NG-C interfaces (both of which may or may not be present), which in turn communicates with a Location Management Function (LMF) 440 via an NLs interface 441. The LMF supports various functions related to determining the UE location, including determining the location for the UE and obtaining DL location measurements or location estimates from the UE, UL location measurements from the NG RAN, and non-UE related assistance data from the NG RAN.
[0063] Furthermore, positioning related communications between the UE 410 and the NG-RAN node are performed via the RRC protocol, and positioning related communications between the NG-RAN node and the LMF are performed via the NRPPa protocol. Optionally, the LMF can also communicate with an Enhanced Serving Mobile Location Center (E-SMLC) 450 and a Secure UP Location (SUPL) Location Platform (SLP) 460 via communication interfaces 451 and 461, respectively. The communication interfaces 451 and 461 may utilize and / or be based on standardized protocols, proprietary protocols, or a combination thereof. The E-SMLC 450 is responsible for UE positioning via LTE CP, and the SLP 460 is responsible for UE positioning via UP.
[0064] The LMF 440 may also include or be associated with various processing circuits 442, by which the LMF performs various operations described herein. The processing circuits 442 may include similar types of processing circuits as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20). The LMF 440 may also include or be associated with non-transitory computer-readable medium 443 that stores instructions (also referred to as a computer program product) that may facilitate the operation of the processing circuits 442. The medium 443 may include similar types of computer memory as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20). Additionally, the LMF 440 may include various communication interface circuits 441 (e.g., Ethernet, optical, and / or wireless transceivers) that may be used, for example, for communication over the NLs interface. For example, the communications interface circuitry 441 may be similar to other communications interface circuitry described herein with respect to other network nodes (eg, see the description of Figures 18 and 20).
[0065] Similarly, the E-SMLC 450 may also include or be associated with various processing circuits 452, by which the E-SMLC performs various operations described herein. The processing circuits 452 may include similar types of processing circuits as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20). The E-SMLC 450 may also include or be associated with a non-transitory computer-readable medium 453 that stores instructions (also referred to as a computer program product) that may facilitate the operation of the processing circuits 452. The medium 453 may include similar types of computer memory as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20). The E-SMLC 450 may also have a communication interface circuit suitable for communicating over the interface 451, which may be similar to other communication interface circuits as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20).
[0066] Similarly, the SLP 460 may also include or be associated with various processing circuits 462, by which the SLP performs the various operations described herein. The processing circuits 662 may include similar types of processing circuits as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20). The SLP 460 may also include or be associated with a non-transitory computer-readable medium 463 that stores instructions (also referred to as a computer program product) that may facilitate the operation of the processing circuits 462. The medium 463 may include similar types of computer memory as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20). The SLP 460 may also have a communications interface circuit suitable for communicating over the interface 461, which may be similar to other communications interface circuitry as described herein with respect to other network nodes (see, e.g., the description of FIG. 18 and FIG. 20).
[0067] In general operation, the AMF may receive a request for location services related to a particular target UE from another entity (e.g., a Gateway Mobile Location Center (GMLC)), or the AMF itself may initiate some location services on behalf of a particular target UE (e.g., in case of an emergency call from the UE). The AMF then sends a location service (LS) request to the LMF. The LMF processes the LS request, which may include forwarding assistance data to the target UE (i.e., to assist in UE-based and / or UE-assisted positioning) and / or determining the location of the target UE. The LMF then returns the results of these operations (e.g., a position estimate for the UE and / or an indication of any assistance data to be forwarded to the UE) to the AMF or to another entity (e.g., GMLC) that requested the LS.
[0068] Various interfaces and protocols are used for or involved in NR positioning. The LTE Positioning Protocol (LPP) is used between the target device (e.g., the UE in the control plane or the SET in the user plane) and the positioning server (e.g., the LMF in the control plane, the SLP in the user plane). The LPP can use either the CP or UP protocol as the underlying transport. The NRPP is terminated between the target device and the LMF. The RRC protocol is used between the UE and the gNB (over the NR radio interface) and between the UE and the ng-eNB (over the LTE radio interface).
[0069] Furthermore, the NR Positioning Protocol A (NRPPa) carries information between NG-RAN nodes and the LMF and is transparent to the AMF. Thus, the AMF routes NRPPa PDUs transparently (e.g., without knowledge of the involved NRPPa transactions) on the NG-C interface based on the routing ID corresponding to the involved LMF. More specifically, the AMF carries NRPPa PDUs on the NG-C interface in either a UE-associated mode or a non-UE-associated mode. The NGAP protocol between the AMF and the NG-RAN node (e.g., gNB or ng-eNB) is used as a transport for LPP and NRPPa messages on the NG-C interface. The NGAP is also used to trigger and terminate NG-RAN related positioning procedures.
[0070] The LPP / NRPP is used to deliver messages such as positioning capability request, OTDOA positioning measurement request, and OTDOA assistance data from a positioning node (e.g., location server) to a UE. The LPP / NRPP is also used to deliver messages from the UE to the positioning node, including, for example, UE capabilities, UE measurements for UE-assisted OTDOA positioning, UE requests for additional assistance data, UE configuration parameter(s) to be used to create UE-specific OTDOA assistance data, etc. The NRPPa is used to deliver information in both directions between the ng-eNB / gNB and the LMF. This can include the LMF requesting some information from the ng-eNB / gNB and the ng-eNB / gNB providing some information to the LMF. For example, this can include information about the PRS sent by the ng-eNB / gNB that should be used by the UE for OTDOA positioning measurements.
[0071] NR Rel-16 includes support for broadcasting positioning assistance data via the Positioning System Information Block (posSIB), as specified in 3GPP TS38.331 (v16.2.0). The posSIB is carried in the RRC System Information (SI) message. The supported posSibTypes are shown in Table 1 below (also 3GPP TS38.331 Table 7.2-1). The GNSS Common and Generic Assistance Data Information Element (IE) is specified in 3GPP TS37.355 (v16.2.0) section 6.5.2.2. The OTDOA Assistance Data IE and the NR DL-TDOA / DL-AoD Assistance Data IE are specified in 3GPP TS37.355 section 7.4.2. The Barometric Assistance Data IE is specified in 3GPP TS37.355 section 6.5.5.8. The TBS Assistance Data IE (based on the MBS signal) is specified in 3GPP TS37.355 section 6.5.4.8. TIFF2024528449000002.tif221170
[0072] PRS was introduced in LTE Rel-9 because cell-specific reference signals (CRS) were not sufficient for positioning. In particular, CRS could not guarantee the necessary probability of detection for at least three different cells required to determine the position. In general, the synchronization signals (PSS / SSS) and reference signals of neighboring cells are generally detectable when the signal-to-interference-and-noise ratio (SINR) is ≧-6 dB. However, simulations have shown that this SINR is available for the third best detected cell in ≦70% of all cases, and thus, in ≧30% of cases, only two neighbor cells are detected. Even this level of performance is based on an interference-free environment, which is unrealistic in real-world scenarios.
[0073] Even so, the PRS has some similarities to the CRS: for example, the PRS is a pseudorandom QPSK sequence that is mapped in a diagonal pattern with shifts in frequency and time to avoid collisions with the CRS and overlaps with the control channel (PDCCH).
[0074] 5 shows a signal flow diagram for an example multi-RTT positioning procedure between a UE and a serving gNB / TRP and multiple neighbor gNB / TRPs and an LMF. Further details are provided in 3GPP TS38.305 (v16.2.0) section 8.10.4, which is incorporated herein by reference in its entirety. In this procedure, the UE measures the DL-PRS transmitted by each gNB / TRP (operation 9a), and those gNBs / TRPs also measure the UL-SRS transmitted by the UE (operation 9b).
[0075] Figure 6 shows an example partitioning of positioning related functions in the split gNB architecture shown in Figure 1. The gNB-DU hosts the TRP function shown in Figure 4, which may be split into a transmission point (TP) and a reception point (RP). Location management messages may be transferred between the gNB-CU and the gNB-DU over the F1-C interface. For example, the gNB-CU may request TRP information and / or positioning measurements from the gNB-DU, and the gNB-DU may respond with the requested information (if available).
[0076] Recent advances in massive antenna systems (massive MIMO) can provide additional degrees of freedom to enable more accurate user location estimation by exploiting the spatial and angular domains of the propagation channel in combination with time measurements. These spatial techniques, also called "beamforming," can be used by the network or by the UE on the transmit and / or receive beams.
[0077] Currently, two NR frequency ranges, FR1 (below 6 GHz) and FR2 (above 6 GHz), are explicitly distinguished in 3GPP. It is known that high frequency wireless communication above 6 GHz suffers from significant path loss and penetration loss. One solution to address this issue is to deploy large antenna arrays to achieve high beamforming gain, which is a reasonable solution due to the small wavelength of high frequency signals. Such a solution is often called multiple input multiple output (MIMO), or in the case of large antenna arrays, massive MIMO is anticipated for NR. In particular, for FR2, up to 64 beams are supported. Furthermore, it is expected that a larger number of antenna elements will also be used in FR1 to obtain more beamforming and multiplexing gain.
[0078] In massive MIMO, three approaches to beamforming were discussed: analog, digital, and hybrid (a combination of analog and digital). Analog beamforming can compensate for the high path loss in NR scenarios, and digital precoding can provide additional performance gains (e.g., similar to MIMO for FR1) necessary to achieve reasonable coverage. The implementation complexity of analog beamforming is significantly smaller than digital because analog beamforming can utilize simple phase shifters, but analog beamforming is limited in terms of multi-directional flexibility (i.e., a single beam can be formed at a time, and then the beam is switched in the time domain), limited in terms of transmission bandwidth (i.e., it is not possible to transmit on sub-bands), limited in terms of inaccuracies in the analog domain, etc.
[0079] 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, offers the best performance in terms of data rate and multiplexing capabilities. For example, multiple beams across multiple subbands 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.
[0080] Therefore, hybrid beamforming, which offers the cost benefits from analog beamforming and the capacity benefits from digital beamforming, is desirable for NR. FIG. 7 shows an exemplary hybrid transmit (TX) beamforming configuration including a digital precoding section and an analog beamforming (BF) section coupled by an intermediate conversion circuit. As shown in FIG. 7, the analog BF section includes an independent analog circuit for each of the N subarrays of antenna elements. For each subarray, the analog circuit includes a mixer (e.g., IF to RF), a phase shifter, and a power amplifier (PA). Each subarray can generate a beam separate from the other subarrays. The conversion circuit includes an independent IFFT modulator, a parallel-to-serial converter (P / S), and a digital-to-analog converter (DAC) for each of the N channels of the analog BF circuit.
[0081] The analog beams of the subarrays may be steered towards a single direction on each OFDM symbol, and thus the number of subarrays determines the number of beam directions and corresponding coverage on each OFDM symbol. However, the number of beams to cover the entire served area is generally larger than the number of subarrays, especially when the individual beam widths are narrow. Therefore, multiple transmissions with narrow beams steered differently in the time domain may be required to cover the entire served area. Providing multiple narrow coverage beams for this purpose may be referred to as "beam sweeping". Figure 8 shows two exemplary beam sweeping configurations with two subarrays (Figure 8A) and three subarrays (Figure 8B).
[0082] In analog and hybrid beamforming, beam sweeping may be crucial to provide the necessary coverage in NR networks. For this purpose, multiple OFDM symbols may be allocated and periodically transmitted, in which differently steered beams may be transmitted through subarrays. The base station generally performs transmit beam sweeping for DL transmissions and may also implement receive beam sweeping for UL reception. The UE generally performs receive beam sweeping for DL reception, but may also implement transmit beam sweeping for UL transmissions.
[0083] The UE and gNB also perform beam measurements to assess the quality of the received signals on the DL and UL beams, respectively. For example, the UE measures the quality on the SSB beam based on parameters such as SS-SINR (signal to interference and noise ratio), SS-RSRP (reference signal received power), and SS-RSRQ (reference signal received quality). The gNB performs similar measurements on the UL beams (e.g., SRS) from the UE, but the gNB measurements are not specified by 3GPP and are left to vendor implementation.
[0084] The UE and the gNB also perform beam determination to determine the best or most suitable DL beam and UL beam, respectively, based on the beam measurements. The UE also reports the beam quality measurements and the beam determination results to the gNB. Furthermore, when a UE in RRC_CONNECTED state experiences poor channel conditions, the UE can receive a beam failure indication from its lower layer (e.g., PHY) and request beam failure recovery by sending a message to the UE's serving gNB.
[0085] The term "spatial relationship" refers to a relationship between a UL RS and another RS, which can be either a DL RS or a UL RS. This is also defined from the UE perspective. If a UL RS is spatially related to a DL RS, it means that the UE should transmit the UL RS in the opposite (opposite) direction in which the UE received the corresponding DL RS. More precisely, the UE should apply the "same" Tx spatial filtering (or beamforming) setting for transmitting the spatially related UL RS as the Rx spatial filtering (or beamforming) setting that the UE used to receive the corresponding DL RS.
[0086] Spatial relationships may also be used for PRS. In particular, each DL PRS is constructed as a DL PRS resource set consisting of multiple DL PRS resources. Each DL PRS resource is transmitted via a separate beam. UL SRS may have a spatial relationship to the DL PRS resources that is signaled through a combination of DL PRS resource set ID and DL PRS resource ID. The UE will then transmit the UL SRS using the same antenna panel that the UE uses to receive the corresponding DL PRS resource and using the same (opposite) beam that the UE uses to receive the DL PRS resource.
[0087] 3GPP Rel-17 NR positioning extensions include ongoing work on supporting "on-demand PRS" in the network. This can involve two different scenarios or use cases. In the first scenario, on-demand PRS can involve configuring the PRS as needed, based on the precondition that the PRS has not been transmitted. When an LCS client (e.g., GMLC, UE) requests positioning, the LMF needs to determine the preferred PRS configuration from the beginning. The second scenario is when the PRS has already been transmitted and either the UE may request to modify the current configuration or the LMF may need to modify the current configuration.
[0088] The first scenario is similar to the scenario occurring in real LTE PRS deployments: the PRS is being transmitted but the LMF is uncertain about the closest TRP to the UE or cell to be included in the assistance data. In this case, E-CID is used as a mandatory procedure to provide the LMF with the required information. In the case of an on-demand PRS that is not currently being transmitted, the LMF may also request the gNB to perform E-CID to obtain SSB and CSI-RS RSRP measurements that can facilitate the triggering of the on-demand PRS transmission.
[0089] 9 shows an example signaling procedure used to obtain a PRS configuration according to this scenario. Although some operations are given numerical labels, these are intended to facilitate the following description without implying or requiring any particular order of operations unless otherwise specified.
[0090] In operation 1, the AMF forwards an LCS service request to the LMF. The LCS service request is received by the AMF from an LCS client present in the GMLC or UE. If the LCS client is in the UE, the LCS client may include measurement reports (e.g., CSI-RS and SSB RSRP, E-CID reports) as part of the MO-LR request message. The LCS client of the UE may also provide other details, such as the number of TRPs, beam direction, start time and duration for DL-PRS transmission, which may also be forwarded from the AMF to the LMF. In operation 1a, as an alternative, the LMF may receive measurement reports (e.g., CSI-RS and SSB RSRP) from the gNB according to the UL NR E-CID procedure specified in 3GPP TS38.455. In operation 2, if the LCS client is a GMLC or measurements are not available in operation 1, the LMF may request measurements from the UE. In action 3, the UE provides the measurements requested in action 2 to the LMF.
[0091] In operations 4-5, the LMF determines the required DL-PRS transmission resources and requests DL-PRS transmission from different gNBs (e.g., TRPs), which may include the UE's serving gNB(s) and other non-serving gNBs. In operation 6, the gNB may provide an acknowledgement to the LMF to initiate the PRS transmission or indicate a failure if it is unable to initiate the PRS transmission. In case of acknowledgement / success in operation 6, the LMF prepares the PRS configuration accordingly and provides it to the UE in operation 7.
[0092] In the second scenario described above, when the LCS client wants to position the UE, some DL-PRS have already been transmitted by the RAN. For example, there may be multiple predefined PRS configurations, and the UE may request one of the predefined configurations. Furthermore, the LMF may also change between different predefined PRS configurations. Figure 10 shows an example signaling procedure used to obtain a PRS configuration according to this scenario. Although some operations are given numerical labels, these are intended to facilitate the following description, rather than implying or requiring any particular order of operations.
[0093] In operation 1, the LMF provides a PRS configuration to the UE via LPP. Alternatively or additionally, in operation 1a, the PRS configuration may be provided to the UE via RRC broadcast. In operation 2, the UE performs positioning measurement based on the PRS configuration(s) received in operation 1 / 1a. If the UE is operating in a UE-based positioning mode and some conditions such as positioning QoS are not satisfied, or based on measurement quality, reliability level, etc., the UE may determine the need to request an on-demand PRS.
[0094] In operation 3, the UE sends an on-demand PRS request with a preferred configuration (e.g., configuration index) of the PRS, or a request to increase / decrease DL-PRS resources. In operation 4, the LMF determines whether the PRS configuration needs to be changed when requested. The LMF may make the decision based on inputs received from multiple UEs. In operation 5, based on the determination in operation 4, the LMF requests (via NRPPa) the serving gNB and non-serving gNBs (e.g., TRP) for the UE to change the current PRS configuration. In operation 6, the gNB provides a PRS transmission update or an acknowledgement in an NRPPa response message accordingly.
[0095] In operation 7, the LMF provides the updated on-demand PRS configuration to the UE via LPP. Alternatively or additionally, in operations 7a-7b, the LMF provides the on-demand PRS configuration to the gNBs, which provide the same to the UE via RRC broadcast.
[0096] Currently, there are several issues, problems, and / or difficulties with the on-demand PRS configuration described above. For example, when a UE is provided with multiple predefined PRS configurations, it is not clear how the LMF should respond to a request from the UE for a specific one of these configurations (e.g., based on a configuration index). More specifically, since the predefined PRS configurations are used by all UEs, should the LMF change the currently used PRS configuration based on a request from one UE? When and how is the LMF forced to act on the request even if the requested configuration is preferred by the UE? Can the network wait until several UEs request the same PRS configuration for it to make a change?
[0097] Current predefined PRS configurations are generally related to quality of service (QoS). For example, one configuration (index 1) may be for high QoS with large bandwidth and short periodicity PRS, a second configuration (index 2) may be for medium QoS with medium bandwidth and medium periodicity PRS, etc. However, defining PRS configurations based only on QoS may be insufficient to cover all use cases and / or scenarios.
[0098] Furthermore, it is unclear what restrictions (if any) should be placed on the UE's choice of which PRS configuration to request. For example, it may be necessary to ensure that the UE does not always request the most resource intensive configuration, even if it provides the UE with the best positioning performance. In other words, rules may be needed to align UE requests with actual UE needs.
[0099] Furthermore, pre-defined PRS configurations require collaboration between the LMF and the gNB that actually transmits the DL-PRS, both in creating such pre-defined configurations and in using those configurations. For example, if the gNB is currently using the configuration associated with a first index, can the LMF request a change to any other pre-defined configurations, or only a subset of the other pre-defined configurations (e.g., the next more resource intensive or the next less resource intensive)?
[0100] Thus, embodiments of the present disclosure provide flexible and efficient techniques for defining a set of PRS configurations for on-demand PRS requests, UE selection among pre-defined PRS configurations for such requests, LMF selection among pre-defined PRS configurations for configuring a gNB / TRP, etc.
[0101] The embodiments can provide a network-friendly approach to support on-demand PRS transmissions when network conditions change. The embodiments can also be used to select a PRS configuration that is suitable for all UEs, not just one, which provides more efficient UE positioning based on DL PRS transmissions. The embodiments can reduce energy consumption of RAN nodes by avoiding transmission of PRS resources that are not needed.
[0102] For example, rather than positioning QoS, the LMF may prescribe PRS configuration based on any of the following, individually or in any combination: ·posSIB broadcast size limit. For example, the number of frequency layers, TRPs, DL-PRS resource sets, DL-PRS resources, etc. that can be accommodated in one posSIB with no segmentation or with a maximum upper limit / limit of segmentation, upper limit X is a predefined number (e.g. X=3, X=5, etc.). · A default configuration indicated by the existing posSIB and a delta configuration provided in the new posSIB. The delta configuration indicates what attributes (e.g. PRS configuration) may differ for the TRPs contained in the default configuration. The configuration index therefore indicates the different parameter configurations that are possible for the TRP contents in the default configuration. The number of TRPs and their associated resources (i.e. DL-PRS resource sets and resources per set) required for acceptable performance of the positioning method. For example, in DL-TDOA, distant TRPs may be required for sufficient GDOP, but this can still be detected at some acceptable level of SNR, SINR, RSSI, etc. Different sets or groups of TRPs, e.g., group 1 having one LOS, GDOP, or DL-PRS periodicity characteristic, group 2 having another LOS, GDOP, or DL-PRS periodicity characteristic, etc. Energy reduction and / or latency reduction. Positioning orientation, e.g. horizontal, vertical, or another specific spatial dimension.
[0103] As another example, the UE may select a preferred configuration to indicate in an on-demand PRS request based on any of the following: · UE mapping of estimated or required error levels to preferred configuration indices. Network configured order of configuration indexes. In other words, the network sorts the indexes in some order and requests the UE to select an index in that order. As a more specific example, if a PRS configuration corresponding to index 3 is provided, the UE may select either index 2 or index 4 for an on-demand PRS request, but may not select other indexes (e.g., index 1 or index 5+).
[0104] Similar techniques may be used between the LMF and the gNB to constrain the LMF or gNB selection of pre-configured PRS settings, including any of the following: LMF mapping of the estimated or required error level to one or more preferred configuration indices, which the LMF can then request the gNB to use. For example, the LMF can request the gNB to consider indices 2, 4, and 5, for example, in a preferred order, in a list of indices. · The order of preference for configuration indices provided by the gNB. In other words, the gNB sorts the indices in some order and requests the LMF to select the indices in that order. As a more specific example, if a PRS configuration corresponding to index 3 is used, the LMF may select either index 2 or index 4 for on-demand requests to the gNB, but may not select other indices (e.g. index 1 or index 5+). Independent of UE on-demand requests. For example, if a configuration with index 1 is currently active and the positioning errors of all UEs meet some requirements, the LMF can change to index 2, which has a longer periodicity.
[0105] In some embodiments, the LMF can determine the predefined PRS configuration based on a reinforcement learning scheme, which can be useful when on-demand PRS transmission has not yet started. For example, the predefined PRS configuration can be based on X UEs initially present in the cell, Y TRPs deployed, Z default radio conditions, etc.
[0106] These initial PRS configurations may then be extended after PRS transmissions are initiated. For example, the LMF may extend a pattern that progressively follows multiple positioning sessions using learning techniques to make different configurations that will fit different scenarios. This may be considered a form of "crowdsourcing." When a new on-demand PRS request is received, the LMF may utilize this crowdsourced PRS information to determine which on-demand configuration works best for the UE(s) and which modifications the gNB / TRP should use, rather than having to select the configuration dictated by the particular UE.
[0107] As shown in Table 1 above, the NR DL-TDOA / DL-AoD assistance data includes three SIBs, namely, posSibType6-1, posSibType6-2, and posSibType6-3.
[0108] In some embodiments, posSIBType6-1(NR-DL-PRS-AssistanceData) may indicate a default PRS configuration that includes a set of PRS configurations for a list of TRPs. In such embodiments, the default PRS configuration may be fixed.
[0109] In other embodiments, posSIBType6-1(NR-DL-PRS-AssistanceData) may indicate an active PRS configuration including a set of PRS configurations for a list of TRPs. In such embodiments, the active PRS configuration may be dynamically changed.
[0110] In other embodiments, a new posSIB type may be defined (e.g., posSibType6-4) to contain different setting indexes and their differential (or delta) settings relative to the default or active DLPRS settings indicated by posSIBType6-1. Example content of posSibType6-4 may include: · Configuration index 1: Larger bandwidth (BW) but the same periodicity compared to the default or active configuration provided in posSibType6-1. · Configuration index 2: shorter periodicity but same BW compared to the default or active configuration provided in posSibType6-1. · Configuration index 3: shorter periodicity and larger BW compared to the default or active configuration provided in posSibType6-1.
[0111] Although only BW and periodicity are mentioned in the above examples, the settings are not limited to these parameters and may include other parameters such as positioning frequency layer (PFL), TRP information, etc.
[0112] In some embodiments, the LMF may provide various rules that restrict the UE's selection of configuration indexes to include in the on-demand PRS request. For example, either index 1 or index 2 may be requested initially, but index 3 may be requested only after the PRS configuration associated with index 1 or index 2 has been provided to the UE. Furthermore, the UE may be restricted to request index 3 only when a configuration based on index 1 or index 2 does not achieve the UE's positioning QoS or measurement quality, when the UE's positioning reliability level is below a certain threshold, etc. These rules may be expressed as the following configuration settings: firstRequestRestrictedTo-INTEGER(1...n), where n=2 in the above example, so the UE may not initiate a request for configuration index 3. · SecondRequestAllowedFor-INTEGER(n...m), where n=3 and 3≦m≦a predetermined maximum index value.
[0113] In some embodiments, there may be additional rules for subsequent requests of the UE.
[0114] In some embodiments, the multiple DL PRS reference signals may be transmitted coherently such that the UE can process the multiple DL PRS reference signals coherently / jointly to improve positioning accuracy. In such an embodiment, the multiple DL PRS reference signals may be configured as follows: Configuration index 1: Larger bandwidth (BW1), but with the same periodicity as the default / active configuration provided in posSibType6-1; the PRS corresponding to configuration index 1 is transmitted in positioning frequency layer (PFL) 1. Configuration index 2: Larger bandwidth (BW2), but same periodicity as the default / active configuration provided in posSibType6-1, the PRS corresponding to configuration index 2 is transmitted in PFL2.
[0115] In some embodiments, if the UE needs improved positioning accuracy, the UE may include multiple (e.g., two) configuration indexes in an on-demand PRS request to the LMF. This may indicate that the UE requests PRS reference signals corresponding to the multiple indexes to be transmitted coherently. To facilitate coherent transmission / reception, some parameters, such as periodicity and TRP index, should be the same for the multiple requested PRS configurations.
[0116] In some embodiments, the PRS configurations may be grouped based on TRP capabilities for on-demand PRS, e.g., all TRPs with the same or similar capabilities are part of one group associated with one or more configuration indexes.
[0117] In some embodiments, PRS configurations may be differentiated and / or grouped based on GDOP (or other geometric classification), detectability by the UE, line of sight (LOS) versus non-LOS transmission, etc. This may be based on previous UE measurement reports or other received information.
[0118] In some embodiments, the configurations associated with each index may be differentiated and / or grouped based on energy consumption (e.g., for the TRP and / or the UE). The following example includes indexes that correspond to three different levels of energy consumption: Configuration index 1: P PFLs, T TRPs in every PFL, Y PRS resource sets in every TRP, Z resources per resource set. In some cases, P, T, X, and / or Z may be a function of the posSIB maximum size, which is about 3000 bits. Thus, the configuration corresponding to index 1 is selected in such a way that it is smaller than this maximum size. · Configuration index 2: P / 2 PFLs, T / 2 TRPs in every PFL, Y / 2 PRS resource sets per TRP, Z / 2 resources per resource set. · Configuration index 3: P / 3 PFLs, T / 3 TRPs in every PFL, Y / 3 PRS resource sets per TRP, Z / 3 resources per resource set.
[0119] This configuration is based on PRS overhead reduction, which leads to energy savings. For example, the LMF may provide the lowest energy configuration index 3 when there are a small number of UEs that need to be positioned. If the number of UEs increases or the obtained positioning QoS is not satisfied, the LMF may switch the configuration to, for example, configuration index 2, which requires more energy.
[0120] As mentioned above, in some embodiments, the UE may be constrained in choosing between these configuration indices as well. For example, if the UE has been provided with a configuration associated with index 3 (lowest energy), the UE may only be allowed to request configuration index 2. If, after being provided with a configuration associated with index 2, the UE is unable to fulfill some requirements and / or conditions with this configuration, the UE is allowed to request configuration index 1 (highest energy).
[0121] In some embodiments, the LMF may set conditions and / or requirements for the UE that adjust the UE's requirements. For example, the LMF may provide positioning error or accuracy thresholds (e.g., 50 m), positioning latency thresholds (e.g., 10 s), etc. Such thresholds may be provided / used individually or in various combinations. Based on these rules and thresholds, the network can balance UE positioning requirements with network energy consumption, interference, etc. associated with increased PRS transmissions.
[0122] In some embodiments, the LMF (optionally in conjunction with the gNB) may associate a distinguishing attribute or characteristic with the pre-defined PRS configuration. In other words, the LMF can indicate the attribute or characteristic used to distinguish the pre-defined PRS configuration. Exemplary distinguishing characteristics include QoS-latency, QoS-accuracy, path loss (or radio conditions), PRS-overhead (or energy savings), etc. The LMF can indicate this distinguishing characteristic to the UE, which can base their configuration index selection for on-demand PRS requests on the distinguishing characteristic.
[0123] 11 shows an ASN.1 data structure for an exemplary OnDemand-PRS-ClassificationCriteria field with different enumerated values for distinguishing characteristics, in accordance with these embodiments. In addition to the characteristics described above, FIG. 11 includes an enumerated value of "areaSpecific," which indicates that the configuration is valid for a certain area and that the UE may request new configurations when the UE moves outside of that area.
[0124] In some embodiments, distinguishing characteristic alternatives may be associated with different UE selection rules and / or different selection thresholds. For example, when distinguishing characteristic A is used, the UE may be allowed to request configuration indexes in any order, and when distinguishing characteristic B is used, the UE may be constrained to request indexes in a fixed order (e.g., ascending or descending order, as described above).
[0125] In some embodiments, the LMF can send an NRPPa message to request the gNB to modify its current DL-PRS transmission configuration to a different one of the pre-configured PRS configurations. In some embodiments, the existing assistance information control message can be used for this purpose. In other embodiments, a newly defined PRS modification request message can be used to modify ongoing PRS transmission for a specific set of TRPs or the entire network. Figure 12 illustrates a signaling flow between a positioning node (e.g., LMF) and a RAN node (e.g., gNB) according to these embodiments. As shown in Figure 12, the RAN node responds to the positioning node with a newly defined PRS modification response message. Tables 2 and 3 below provide example contents of the PRS modification request message and the PRS modification response message, respectively. For example, messages with these contents can be added to 3GPP TS38.455 (v16.3.0). TIFF2024528449000003.tif134170TIFF2024528449000004.tif66170
[0126] In some embodiments, the LMF may have a default PRS configuration that the LMF is provided with during initial deployment, e.g., by an Operations, Administration, and Maintenance (OAM) function, and that may be used for initial signaling of on-demand PRS transmissions.
[0127] In some embodiments, the LMF may receive UE measurements (e.g., RRM beam measurements or PRS beam measurements) via the LPP and create a database including multiple configurations for on-demand PRS transmissions based on such measurements. For example, the LMF may create some or all of the configurations based on factors such as the number of UEs, RRM statistics, TRP capabilities, SSB patterns, estimated reports, positioning orientation (e.g., vertical / horizontal), etc.
[0128] In some embodiments, the LMF can use machine learning (ML) to create such PRS configurations in the LMF's database. Reinforcement learning (RL) is a particular type of ML that may be beneficial for such embodiments. In RL, the model continuously interacts with the model's environment and is provided with implicit (and sometimes delayed) feedback in the form of a "reward signal." RL performs short-term reward maximization, but may also make decisions that are irrational in the short term while providing long-term gains. More generally, RL models attempt to maximize expected future rewards by leveraging already existing knowledge and exploring the space of actions in different scenarios, e.g., network and / or UE configurations.
[0129] In some embodiments, when the LCS client triggers a location request and an on-demand PRS is requested by the UE, the LMF fetches one of the LMF's stored PRS configurations and sends the PRS configuration to one or more gNBs via NRPPa signaling. Based on the gNB feedback (e.g., NRPPa success response message), the LMF updates the LMF's PRS configuration database. In some embodiments, the LMF can also update the LMF's PRS configuration database based on UE feedback, such as positioning measurements and / or location estimates.
[0130] In some embodiments, during an ongoing positioning session, when a DL-PRS has already been transmitted, the LMF may send an NRPPa message to the gNB to modify the current PRS transmission with one of the PRS settings from the LMF's database. This may be done, for example, using the example procedure shown in Figure 12. Alternatively, an existing NRPPa message may be modified for the same purpose.
[0131] Various features of the embodiments described above correspond to various operations illustrated in Figures 13-15, which illustrate example methods (e.g., procedures) for a UE, a positioning node, and a RAN node, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the example methods illustrated in Figures 13-15 may be used cooperatively to provide various benefits, advantages, and / or solutions to problems described herein. Although Figures 13-15 illustrate certain blocks in a particular order, the operations of the example methods may be performed in a different order than shown, and may be combined and / or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.
[0132] In particular, Figure 13 illustrates an example method (e.g., procedure) for a UE configured for positioning in a RAN, in accordance with various embodiments of the present disclosure. The example method may be performed by a UE (e.g., a wireless device, etc.) as described elsewhere herein.
[0133] The example method may include operations of block 1310, where the UE may receive, from a positioning node associated with the RAN, a plurality of configurations for the PRS transmitted by the node of the RAN and a corresponding plurality of configuration indexes associated with the plurality of configurations. In other words, each configuration is represented by, corresponds to, and / or is associated with a configuration index, and vice versa. For example, the positioning node may be an LMF.
[0134] The example method may also include operations of block 1340, where the UE may determine a need to receive the PRS and select one or more of the multiple configurations based on one or more selection rules. The example method may also include operations of block 1350, where the UE may transmit one or more requests for TRS transmission by the RAN to the positioning node. The one or more requests include one or more configuration indexes associated with the one or more configurations selected in block 1340.
[0135] In some embodiments, the example method may also include the operation of block 1330, where the UE may receive the selection rule from the positioning node.
[0136] In various embodiments, the plurality of settings may include the following characteristics or parameters: ·PRS transmission periodicity, PRS transmission bandwidth, The number of PRS transmit frequency layers used, The particular PRS transmit frequency layer being used, · number of RAN nodes sending PRS, The particular RAN node transmitting the PRS; The geographical configuration of the RAN nodes transmitting the PRS; Number of PRS resource sets per node, · Number of PRSs per PRS resource set, the energy consumption and / or signaling overhead associated with transmitting the PRS according to the configuration; the relevant geographic area; Positioning spatial dimension, Positioning accuracy Quality of Service (QoS), as well as Positioning Latency QoS may be distinguished from one another based on one or more of:
[0137] In some embodiments, the example method may also include the operations of block 1320, where the UE may receive from the positioning node an indication of a characteristic or parameter by which the multiple configurations are distinguished. In such embodiments, selecting one or more of the multiple configurations (e.g., at block 1340) may be based on the indicated characteristic or parameter. An example indication according to these embodiments is shown in FIG. 11. In some embodiments, the example method may also include the operations of block 1320, where the UE may receive from the positioning node a selection rule (e.g., for use in block 1340).
[0138] In some embodiments, the plurality of configurations includes a first configuration including default values for configuration parameters and one or more further configurations. Each further configuration includes only configuration parameters of the configuration parameters that have values different from the default values. In some of these embodiments, the first configuration may be received via a broadcasted first SIB, and the one or more further configurations may be received via a broadcasted second SIB. Exemplary SIBs have been described above. In some of these embodiments, the first SIB indicates that the first configuration is one of a default configuration or an active configuration.
[0139] In some embodiments, each request includes an index associated with a configuration selected by the UE. In some of these embodiments, the selection rule includes a sequential order in which the respective configurations may be requested by the UE.
[0140] In others of these embodiments, the one or more requests include an initial request and one or more subsequent requests, and the selection rule includes a first rule that identifies a first subset of settings that may be requested by the UE in the initial request and a second rule that identifies a second subset of settings that may be requested by the UE in the subsequent request. In some variations, the first subset of settings includes a first setting that requires the lowest energy for transmitting the PRS, and the second subset includes at least one setting that requires more energy for transmitting the PRS than the first setting.
[0141] In some examples of these variations, the selecting operation of block 1340 may include operations of sub-blocks 1341-1343, where the UE may determine whether positioning based on PRS transmissions according to a first configuration will satisfy a positioning QoS threshold, select the first configuration when it is determined that the positioning QoS threshold will be satisfied, and select the second subset of configurations when it is determined that the positioning QoS threshold will not be satisfied. In some cases, the positioning QoS threshold is related to accuracy and / or latency.
[0142] In other examples of these variations, the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting. Further, the one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request, and the second rule identifies that the second setting may be selected for the first subsequent request and that the third setting may be selected for the second subsequent request.
[0143] In other embodiments, the one or more requests include a single request including at least two configuration indexes. The selection rule includes a third rule that indicates one of more configuration parameters that must be common between the at least two configurations associated with the at least two configuration indexes included in the single request. In some variations, the third rule indicates that at least the following parameters must be common between the at least two configurations: PRS transmission periodicity and the particular RAN node transmitting the PRS. In some of these embodiments, the example method may also include the operation of block 1360, where the UE may perform positioning measurements on the PRS transmitted coherently according to the at least two configurations associated with the at least two configuration indexes included in the single request.
[0144] 14 illustrates an example method (e.g., procedure) for a positioning node associated with a RAN, according to various embodiments of the present disclosure. The example method may be performed by a positioning node (e.g., LMF, E-SMLC, SUPL, etc.), as described elsewhere herein.
[0145] The exemplary method may include operations of block 1410, where the positioning node may determine a plurality of configurations for a PRS transmitted by a RAN node. The plurality of configurations may be associated with a respective plurality of configuration indexes. The exemplary method may also include operations of block 1420, where the positioning node may send the plurality of configurations and the associated plurality of configuration indexes to a node of the RAN and to a UE operating in the RAN. The exemplary method may also include operations of block 1450, where the positioning node may receive one or more requests for a PRS transmission by the RAN from the UE. The one or more requests may include one or more of the plurality of configuration indexes associated with one or more of the plurality of configurations selected by the UE.
[0146] In various embodiments, the multiple configurations may be distinguished from one another based on any of the characteristics or parameters described above with respect to the UE embodiment. In some embodiments, the example method may also include the operation of block 1430, where the positioning node may send to the UE an indication of the characteristics or parameters by which the multiple configurations were distinguished. An example indication according to these embodiments is shown in FIG.
[0147] In some embodiments, the plurality of configurations may include a first configuration including default values for configuration parameters and one or more further configurations. Each further configuration includes only configuration parameters among the configuration parameters that have values different from the default values. In some of these embodiments, the first configuration may be sent by the RAN via broadcast of a first SIB, and the one or more further configurations may be sent by the RAN via broadcast of a second SIB. Exemplary SIBs have been described above. In some of these embodiments, the first SIB indicates that the first configuration is one of a default configuration or an active configuration.
[0148] In some embodiments, the example method may also include the operation of block 1460, where the positioning node may configure the RAN node to transmit the PRS in accordance with one of the one or more configurations indicated by the UE or one or more further configurations selected by the positioning node.
[0149] In some of these embodiments, the example method may also include the operation of block 1440, where the positioning node may send to the UE a selection rule for selecting between the multiple configurations.
[0150] In some of these embodiments, each request includes an index associated with a selected configuration. In some variations, the selection rules (e.g., sent at block 1440) may include a sequential order in which the respective configurations may be requested by the UE.
[0151] In others of these embodiments, the one or more requests (e.g., received at block 1450) may include an initial request and one or more subsequent requests, and the selection rule may include a first rule that identifies a first subset of settings that may be requested by the UE in the initial request and a second rule that identifies a second subset of settings that may be requested by the UE in the subsequent request.
[0152] In some variations of these embodiments, the first subset includes a first configuration that requires the lowest energy for transmitting the PRS, and the second subset includes at least one configuration that requires more energy for transmitting the PRS than the first configuration. In some examples of these variations, the selection rule can include a positioning QoS threshold for selecting between the first configuration and the second subset of configurations. In some cases, the positioning QoS threshold is related to accuracy and / or latency.
[0153] In other examples of these variations, the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting. Further, the one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request. The second rule identifies that the second setting may be selected for the first subsequent request and that the third setting may be selected for the second subsequent request.
[0154] In others of these embodiments, the one or more requests (e.g., received in block 1450) include a single request including at least two configuration indexes. The selection rule includes a third rule that indicates one of more configuration parameters that must be common between the at least two configurations identified by the at least two configuration indexes included in the single request. In some variations, the third rule indicates that at least the following parameters must be common between the at least two configurations: PRS transmission periodicity and the particular RAN node transmitting the PRS. In some of these embodiments, the configuration operation of block 1460 may include operations of sub-block 1461, where the positioning node may configure multiple nodes to coherently transmit PRS according to at least two configurations associated with the at least two configuration indexes included in the single request.
[0155] In some embodiments, determining the plurality of configurations in block 1410 may include operations of sub-blocks 1411-1412, where the positioning node obtains a default configuration for PRS transmission (e.g., from OAM at system initialization) and determines the plurality of configurations (e.g., sent in block 1420) as: Measurements made by the UE on the transmitted PRS according to default settings, · the node's ability to transmit PRS, The number of UEs operating in the RAN, and One or more distinguishing characteristics or parameters (e.g., as described above) Based on the above, a decision can be made.
[0156] In some embodiments, determining the plurality of configurations in block 1410 may include the operations of sub-block 1413, where the positioning node determines the plurality of configurations as: Measurements made by the UE on PRS transmitted according to multiple configurations; -Updated capabilities of the nodes, The updated number of UEs operating in the RAN, and one or more distinguishing characteristics or parameters The adaptation may be based on one or more of:
[0157] For example, the positioning node may use ML (eg, RL) techniques for adapting to multiple configurations, as described above.
[0158] 15 illustrates an example method (e.g., procedure) for a RAN node, in accordance with various embodiments of the present disclosure. The example method may be performed by a RAN node (e.g., a base station, eNB, gNB, ng-eNB, TRP, etc.), as described elsewhere herein.
[0159] An example method may include the operations of block 1510, where a RAN node may receive, from a positioning node associated with the RAN, a plurality of configurations for a PRS transmitted by the node of the RAN and a corresponding plurality of configuration indexes associated with the plurality of configurations. In other words, each configuration is represented by, corresponds to, and / or is associated with a configuration index, and vice versa. For example, the positioning node may be an LMF.
[0160] The example method may also include operations of block 1530, where the RAN node may subsequently receive one or more requests for PRS transmission from the positioning node. The one or more requests may include one or more of the multiple configuration indexes (e.g., received in block 1510). The example method may also include operations of block 1540, where the RAN node may transmit the PRS according to one or more of the configurations associated with the one or more configuration indexes included in the one or more requests.
[0161] In various embodiments, the multiple configurations may be distinguished from one another based on any of the characteristics or parameters described above with respect to the UE embodiment.
[0162] In some embodiments, the plurality of configurations may include a first configuration including default values for configuration parameters and one or more additional configurations. Each additional configuration includes only configuration parameters among the configuration parameters that have values different from the default values. In some of these embodiments, the exemplary method may also include the operation of block 1520, where the RAN node may broadcast the first configuration in a first SIB and the one or more additional configurations in a second SIB. Exemplary SIBs are described above. In some of these embodiments, the first SIB indicates that the first configuration is one of a default configuration or an active configuration.
[0163] In some embodiments, the one or more requests include an initial request and one or more subsequent requests, and the multiple settings include a first subset of settings that may be requested by the UE in the initial request and a second subset of settings that may be requested by the UE in the subsequent requests. In some of these embodiments, the first subset of settings includes a first setting that requires the lowest energy for transmitting the PRS, and the second subset includes at least one setting that requires more energy for transmitting the PRS than the first setting. In some variations, the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting.
[0164] In other embodiments, the one or more requests include a single request including at least two configuration indexes, where at least the PRS transmission periodicity is common between the at least two configurations associated with the at least two configuration indexes included in the single request. In some of these embodiments, the transmit operations of block 1540 may include operations of sub-block 1541, where the RAN node may coherently transmit the PRS according to the at least two configurations associated with the at least two configuration indexes included in the single request.
[0165] While various embodiments have been described above with respect to methods, techniques, and / or procedures, those skilled in the art will readily appreciate that such methods, techniques, and / or procedures may be embodied in various combinations of hardware and software in a variety of systems, communication devices, computing devices, control devices, apparatus, non-transitory computer readable media, computer program products, and the like.
[0166] 16 illustrates an example of a communications system 1600 according to some embodiments. In this example, the communications system 1600 includes a communications network 1602 including an access network 1604 (e.g., a RAN) and a core network 1606 including one or more core network nodes 1608. The access network 1604 includes one or more access network nodes (one or more of which may be generally referred to as network nodes 1610), such as network nodes 1610a and 1610b, or any other similar 3GPP access nodes or non-3GPP access points. The network nodes 1610 facilitate direct or indirect connectivity of UEs 1612a, 1612b, 1612c, and 1612d (one or more of which may be generally referred to as UEs 1612) to the core network 1606 over one or more wireless connections.
[0167] Exemplary wireless communication over a wireless connection includes transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system 1600 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar types of systems.
[0168] The UE 1612 may be any of a wide variety of communications devices, including a wireless device configured, configured, and / or operable to wirelessly communicate with the network node 1610 and other communications devices. Similarly, the network node 1610 is configured, capable, configured, and / or operable to communicate, directly or indirectly, with the UE 1612 and / or with other network nodes or equipment in the communications network 1602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the communications network 1602.
[0169] In the illustrated example, the core network 1606 connects the network node 1610 to one or more hosts, such as the host 1616. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 1606 includes one or more core network nodes (e.g., the core network node 1608) structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, and therefore those descriptions are generally applicable to the corresponding components of the core network node 1608. Exemplary core network nodes include nodes that can host and / or implement any of the following network functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Publishing Function (NEF), Location Management Function (LMF), SUPL Location Platform (SUPL), Enhanced Serving Mobile Location Center (E-SMLC), and User Plane Function (UPF).
[0170] The host 1616 may be owned or under the control of, and operated by or on behalf of, a service provider other than an operator or provider of the access network 1604 and / or the communication network 1602. The host 1616 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data regarding various ambient conditions detected by multiple UEs, analytics functions, social media, functions for controlling or possibly interacting with remote devices, functions for an alarm and surveillance center, or any other such functions implemented by a server.
[0171] Overall, the communication system 1600 of Figure 16 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G), a wireless local area network (WLAN) standard, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communications (NFC) ZigBee, LiFi, and / or any low power wide area network (LPWAN) standard, such as LoRa and Sigfox.
[0172] In some examples, the communication network 1602 is a cellular network implementing 3GPP standardized features. Thus, the communication network 1602 may support network slicing to provide different logical networks to different devices connected to the communication network 1602. For example, the communication network 1602 may provide ultra-reliable low latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or providing massive machine-based communication (mMTC) / massive IoT services to still further UEs.
[0173] In some examples, the UE 1612 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 1604 on a predefined schedule, when triggered by an internal or external event, or in response to a request from the access network 1604. Additionally, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may operate in any one or combination of Wi-Fi, NR, and LTE, such as in multi-radio dual connectivity (MR-DC) with the network.
[0174] In this example, the hub 1614 communicates with the access network 1604 to facilitate indirect communication between one or more UEs (e.g., UEs 1612c and / or 1612d) and a network node (e.g., network node 1610b). In some examples, the hub 1614 may be a controller, a router, a content source and content analysis, or any of the other communication devices described herein with respect to UEs. For example, the hub 1614 may be a broadband router that allows access to the core network 1606 for the UE. As another example, the hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1610, or may be due to executable code, scripts, processes, or other instructions in the hub 1614. As another example, the hub 1614 may be a data collector that acts as a temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub 1614 may retrieve, via a network node, VR assets, video, audio, or other media or data related to sensory information, which the hub 1614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 1614 acts as a proxy server or orchestrator for the UEs, particularly in the case where one or more of the UEs are low energy IoT devices.
[0175] The hub 1614 may have a full-time / permanent or intermittent connection to the network node 1610b. The hub 1614 may also enable different communication schemes and / or schedules between the hub 1614 and the UEs (e.g., UEs 1612c and / or 1612d) and between the hub 1614 and the core network 1606. In other examples, the hub 1614 is connected to the core network 1606 and / or one or more UEs via a wired connection. Moreover, the hub 1614 may be configured to connect to an M2M service provider over the access network 1604 and / or to another UE over a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 1610 while still being connected via a wired or wireless connection through the hub 1614. In some embodiments, the hub 1614 may be a dedicated hub, i.e., a hub whose main function is to route communications from the UE to / from the network node 1610b to the UE. In other embodiments, the hub 1614 may be a non-dedicated hub, i.e., a device that is capable of operating to route communications between the UE and the network node 1610b, but that is further capable of operating as a communication initiation and / or termination point for some data channels.
[0176] FIG. 17 illustrates a UE 1700, according to some embodiments. A UE, as used herein, refers to a device capable of, set up, configured, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), vehicle mounted or vehicle embedded / integrated wireless devices, and the like. Other examples include any UE type specified and / or identified by 3GPP, including narrowband Internet of Things (NB-IoT) UE, machine type communication (MTC) UE, and / or enhanced MTC (eMTC) UE.
[0177] A UE may support device-to-device (D2D) communications, for example, by implementing sidelink (SL) communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications, and / or vehicle-to-everything (V2X) communications. In other examples, a UE is not necessarily associated with a particular human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not initially be associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by a human user, but may be associated with or operated for the benefit of a user.
[0178] The UE 1700 includes a processing circuit 1702 operably coupled to an input / output interface 1706, a power source 1708, a memory 1710, a communication interface 1712, and / or any other components, or any combination thereof, via a bus 1704. Some UEs may utilize all or a subset of the components shown in FIG. 17. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0179] The processing circuit 1702 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1710 as a machine-readable computer program. The processing circuit 1702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), programmable logic together with appropriate firmware, one or more stored computer programs, such as a microprocessor or digital signal processor (DSP) together with appropriate software, a general-purpose processor, or any combination of the above. For example, the processing circuit 1702 may include multiple central processing units (CPUs).
[0180] In this example, the input / output interface 1706 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. An input device may allow a user to capture information to the UE 1700. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a universal serial bus (USB) port may be used to provide an input device and an output device.
[0181] In some embodiments, the power source 1708 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power source 1708 may further include a power circuit for delivering power to various parts of the UE 1700 from the power source 1708 itself and / or from an external power source via an input circuit, or an interface such as a power cable. Delivering power may be for charging the power source 1708, for example. The power circuit may perform any formatting, conversion, or other modification on the power from the power source 1708 to make it suitable for the respective component of the UE 1700 to which it is powered.
[0182] The memory 1710 may be or be configured to include memory, such as random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, etc. In one example, the memory 1710 includes one or more application programs 1714, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 1716. The memory 1710 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 1700.
[0183] The memory 1710 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory, such as a tamper-proof module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or an ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly known as a "SIM card". The memory 1710 may enable the UE 1700 to access instructions, application programs, and the like stored on a temporary or non-transitory memory medium, to offload data, or to upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in the memory 1710, which may be or comprise a device-readable storage medium.
[0184] The processing circuit 1702 may be configured to communicate with an access network or other networks using a communication interface 1712. The communication interface 1712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1722. The communication interface 1712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1718 and / or a receiver 1720 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Moreover, the transmitter 1718 and receiver 1720 may be coupled to one or more antennas (e.g., antenna 1722) and may share circuit components, software or firmware, or may alternatively be implemented separately.
[0185] In the embodiment shown, the communication capabilities of communication interface 1712 may include cellular communications, Wi-Fi communications, LPWAN communications, data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a Global Positioning System (GPS) to determine location, another similar communication capability, or any combination thereof. Communications may be implemented according to one or more communications protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.
[0186] Regardless of the type of sensor, the UE may provide an output of data captured by the UE's sensors to a network node via a wireless connection through the UE's communications interface 1712. Data captured by the UE's sensors may be communicated to a network node via another UE over a wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting detected temperature), in response to a triggering event (e.g., an alert is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to even out the load from reporting from several sensors), or a continuous stream (e.g., a live video feed of a patient).
[0187] As another example, the UE comprises an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch may change. For example, the UE may comprise a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.
[0188] The UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application areas, including, but not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in connected refrigerators or freezers, TVs, connected lighting devices, power meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, water inundation / humidity sensors, electronic door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic augmentation or sensory augmentation, water sprinklers, animal or product tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as a heart rate monitor or a remote-controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software depending on the intended application of the IoT device, in addition to the other components described with respect to UE 1700 shown in FIG. 17.
[0189] As yet another particular example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another UE and / or network node. The UE may in this case be an M2M device, which may be referred to as an MTC device in the 3GPP context. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other equipment capable of monitoring and / or reporting on its operating status or other functions related to its operation.
[0190] In fact, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller that operates the drone. When a user makes a change from the remote controller, the first UE may adjust a throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include two or more of the functions described above. For example, a UE may comprise a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.
[0191] 18 illustrates a network node 1800 according to some embodiments. A network node, as used herein, refers to a device capable of, set up, configured, and / or operable to communicate, directly or indirectly, with UEs and / or other network nodes or devices in a communication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., wireless base stations, Node Bs, eNBs, gNBs).
[0192] Base stations may be categorized based on the amount of coverage they provide (or, stated another way, their transmit power level) and may therefore be referred to as femto, pico, micro, or macro base stations depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0193] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., E-SMLC, SLP, LMF), and / or a minimized drive test (MDT).
[0194] The network node 1800 includes a processing circuit 1802, a memory 1804, a communication interface 1806, and a power source 1808. The network node 1800 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In some scenarios in which the network node 1800 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control several Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some cases. In some embodiments, the network node 1800 may be configured to support several radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1804 for different RATs) and some components may be reused (e.g., the same antenna 1810 may be shared by different RATs). Network node 1800 may also include multiple sets of the various shown components for different wireless technologies, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies, integrated into network node 1800. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within network node 1800.
[0195] The processing circuit 1802 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resources, or combinations of hardware, software, and / or coded logic, either alone or in conjunction with other network node 1800 components, such as memory 1804, operable to provide network node 1800 functionality.
[0196] In some embodiments, the processing circuit 1802 comprises a system on a chip (SOC). In some embodiments, the processing circuit 1802 includes one or more of a radio frequency (RF) transceiver circuit 1812 and a baseband processing circuit 1814. In some embodiments, the radio frequency (RF) transceiver circuit 1812 and the baseband processing circuit 1814 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 1812 and the baseband processing circuit 1814 may be on the same chip or set of chips, board, or unit.
[0197] The memory 1804 may comprise any form of volatile or non-volatile computer readable memory, including, but not limited to, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 1802. The memory 1804 may store any suitable instructions, data or information, including applications including one or more of computer programs, software, logic, rules, code, tables, and / or other instructions (collectively denoted computer program product 1804a) that may be executed by the processing circuit 1802 and utilized by the network node 1800. The memory 1804 may be used to store calculations performed by the processing circuit 1802 and / or data received via the communications interface 1806. In some embodiments, the processing circuit 1802 and the memory 1804 are integrated.
[0198] The communication interface 1806 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface 1806 comprises port(s) / terminal(s) 1816 for sending and receiving data to and from a network, for example over a wired connection. The communication interface 1806 also includes a radio front-end circuit 1818 that is coupled to an antenna 1810 or, in some embodiments, may be part of the antenna 1810. The radio front-end circuit 1818 comprises a filter 1820 and an amplifier 1822. The radio front-end circuit 1818 may be connected to the antenna 1810 and the processing circuit 1802. The radio front-end circuit may be configured to condition signals communicated between the antenna 1810 and the processing circuit 1802. The radio front-end circuit 1818 may receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1818 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1820 and / or amplifiers 1822. The radio signal may then be transmitted via the antenna 1810. Similarly, when receiving data, the antenna 1810 may collect the radio signal, which is then converted into digital data by the radio front-end circuitry 1818. The digital data may be passed to the processing circuitry 1802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0199] In some alternative embodiments, the network node 1800 does not include a separate radio front-end circuit 1818, and instead the processing circuit 1802 includes the radio front-end circuitry and is connected to the antenna 1810. Similarly, in some embodiments all or a portion of the RF transceiver circuitry 1812 is part of the communications interface 1806. In still other embodiments, the communications interface 1806 includes one or more ports or terminals 1816, the radio front-end circuitry 1818, and the RF transceiver circuitry 1812 as part of a radio unit (not shown), and the communications interface 1806 communicates with baseband processing circuitry 1814 that is part of a digital unit (not shown).
[0200] The antenna 1810 may include one or more antennas or an antenna array configured to send and / or receive wireless signals. The antenna 1810 may be coupled to the radio front-end circuitry 1818 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 1810 is separate from the network node 1800 and connectable to the network node 1800 through an interface or port.
[0201] The antenna 1810, the communication interface 1806, and / or the processing circuit 1802 may be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1810, the communication interface 1806, and / or the processing circuit 1802 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a UE, another network node, and / or any other network equipment.
[0202] The power source 1808 provides power to the various components of the network node 1800 in a form suitable for each component (e.g., at voltage and current levels required for each respective component). The power source 1808 may further comprise or be coupled to a power management circuit for supplying the components of the network node 1800 with power for performing the functions described herein. For example, the network node 1800 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuit of the power source 1808. As a further example, the power source 1808 may comprise a power source in the form of a battery or battery pack connected to or integrated in the power circuit. The battery may provide backup power in the event that the external power source fails.
[0203] Embodiments of network node 1800 may include additional components other than those shown in Figure 18 to provide certain aspects of the functionality of the network node, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 1800 may include user interface devices to enable input of information into network node 1800 and output of information from network node 1800. This may enable a user to perform diagnostics, maintenance, repair, and other administrative functions for network node 1800.
[0204] 19 is a block diagram of a host 1900, which may be an embodiment of the host 1616 of FIG. 16, in accordance with various aspects described herein. The host 1900, as used herein, may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The host 1900 may provide one or more services to one or more UEs.
[0205] The host 1900 includes a processing circuit 1902 operably coupled to an input / output interface 1906, a network interface 1908, a power source 1910, and a memory 1912 via a bus 1904. In other embodiments, other components may be included. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 17 and 18, and therefore those descriptions are generally applicable to the corresponding components of the host 1900.
[0206] The memory 1912 may include one or more computer programs including one or more host application programs 1914 and data 1916, which may include user data, e.g., data generated by the UE for the host 1900 or data generated by the host 1900 for the UE. An embodiment of the host 1900 may utilize only a subset or all of the components shown. The host application programs 1914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1914 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in the core network or on the edge of the core network. Thus, the host 1900 may select and / or direct different hosts for over-the-top services for the UE. The host application programs 1914 may support a variety of protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0207] FIG. 20 is a block diagram illustrating a virtualization environment 2000 in which functionality implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization as used herein may apply to any device described herein, or components thereof, and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2000 hosted by one or more of the hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which a virtual node does not require wireless connectivity (e.g., a core network node or a host), the node may be fully virtualized.
[0208] An application 2002 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) is run in the virtualized environment 2000 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0209] The hardware 2004 includes a processing circuit, memory that stores software and / or instructions (collectively denoted as computer program product 2004a) executable by the hardware processing circuit, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software may be executed by the processing circuit to instantiate one or more virtualization layers 2006 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 2008a and 2008b (one or more of which are commonly referred to as VMs 2008), and / or implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 2006 may present to the VMs 2008 a virtual operating platform that appears to be networking hardware.
[0210] The VMs 2008 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 2006. Different embodiments of the virtual appliance 2002 instance may be implemented on one or more of the VMs 2008, and the implementation may be done in different ways. Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.
[0211] In the context of NFV, a VM 2008 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each VM 2008 and the portion of the hardware 2004 on which it runs, whether hardware dedicated to that VM and / or hardware shared by that VM with other of the VMs, form a separate virtual network element. Further in the context of NFV, a virtual network function is responsible for handling a particular network function running in one or more VMs 2008 on the hardware 2004 and corresponds to the application 2002.
[0212] The hardware 2004 may be implemented in a standalone network node with general or specific components. The hardware 2004 may implement some functions via virtualization. Alternatively, the hardware 2004 may be part of a larger cluster of hardware (such as in a data center or CPE, for example) where many hardware nodes work together and are managed via a management and orchestration 2010 that oversees, among other things, the lifecycle management of the application 2002. In some embodiments, the hardware 2004 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in combination with virtual components to provide a virtual node with wireless capabilities, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system 2012, which may alternatively be used for communication between the hardware nodes and the radio units.
[0213] 21 illustrates a communication diagram of a host 2102 communicating with a UE 2106 via a network node 2104 over a partial wireless connection, according to some embodiments. Exemplary implementations according to various embodiments of a UE (such as the UE 1612a of FIG. 16 and / or the UE 1700 of FIG. 17), a network node (such as the network node 1610a of FIG. 16 and / or the network node 1800 of FIG. 18), and a host (such as the host 1616 of FIG. 16 and / or the host 1900 of FIG. 19) described in the previous paragraphs will now be described with reference to FIG.
[0214] Similar to the host 1900, an embodiment of the host 2102 includes hardware, such as a communications interface, processing circuitry, and memory. The host 2102 also includes software stored on or accessible by the host 2102 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 2106 connecting via an over-the-top (OTT) connection 2150 extending between the UE 2106 and the host 2102. In providing services to a remote user, the host application may provide user data that is transmitted using the OTT connection 2150.
[0215] The network node 2104 includes hardware that enables the network node 2104 to communicate with the host 2102 and the UE 2106. The connection 2160 may be direct or may pass through one or more other intermediate networks, such as a core network (similar to the core network 1606 of FIG. 16) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.
[0216] The UE 2106 includes hardware and software stored in or accessible by the UE 2106 and executable by processing circuitry of the UE. The software includes a client application, such as a web browser or an operator-specific "app," that may be operable to provide services to a human or non-human user via the UE 2106 with the support of the host 2102. At the host 2102, an executing host application may communicate with an executing client application via an OTT connection 2150 that terminates at the UE 2106 and the host 2102. In providing services to a user, the client application of the UE may receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 2150 may transfer both the request data and the user data. The client application of the UE may interact with the user to generate user data that the client application of the UE provides to the host application through the OTT connection 2150.
[0217] The OTT connection 2150 may extend through a connection 2160 between the host 2102 and a network node 2104 and through a wireless connection 2170 between the network node 2104 and the UE 2106 to provide a connection between the host 2102 and the UE 2106. The connections 2160 and wireless connections 2170 through which the OTT connection 2150 may be provided are depicted abstractly to show communication between the host 2102 and the UE 2106 through the network node 2104, without explicit reference to intermediary devices and the precise routing of messages through these devices.
[0218] As an example of transmitting data over the OTT connection 2150, in step 2108 the host 2102 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2106. In other embodiments, the user data is associated with a UE 2106 that shares data with the host 2102 without explicit human interaction. In step 2110, the host 2102 initiates a transmission conveying the user data towards the UE 2106. The host 2102 may initiate the transmission in response to a request transmitted by the UE 2106. The request may be triggered by human interaction with the UE 2106 or by the operation of a client application executing on the UE 2106. The transmission may proceed via the network node 2104 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 2112, the network node 2104 transmits the user data carried in the transmission initiated by the host 2102 to the UE 2106, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2114, the UE 2106 receives the user data carried in the transmission, which may be performed by a client application executing on the UE 2106 associated with the host application executed by the host 2102.
[0219] In some examples, the UE 2106 executes a client application that provides user data to the host 2102. The user data may be provided in reaction or response to data received from the host 2102. Thus, in step 2116, the UE 2106 may provide the user data, which may be implemented by executing the client application. In providing the user data, the client application may further take into account user input received from a user via an input / output interface of the UE 2106. Regardless of the particular manner in which the user data is provided, the UE 2106 initiates transmission of the user data towards the host 2102 via the network node 2104 in step 2118. In step 2120, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2104 receives the user data from the UE 2106 and initiates transmission of the received user data towards the host 2102. In step 2122, the host 2102 receives the user data carried in the transmission initiated by the UE 2106.
[0220] One or more of the various embodiments improve the performance of OTT services provided to the UE 2106 using the OTT connection 2150, of which the radio connection 2170 forms the last segment. More precisely, the embodiments described herein can provide flexible and efficient techniques for supporting on-demand PRS transmissions when network conditions change. The embodiments can also be used to select a PRS configuration that is suitable for many UEs, not just one, which provides more efficient UE positioning based on DL PRS transmissions. The embodiments can also reduce energy consumption of RAN nodes by avoiding transmission of PRS resources that are not needed. In this way, the embodiments can improve the delivery of positioning-based OTT services by wireless networks, which increases the value of such services to end users and OTT service providers.
[0221] In an exemplary scenario, factory status information may be collected and analyzed by the host 2102. As another example, the host 2102 may process audio and video data that may have been retrieved from the UE for use in creating a map. As another example, the host 2102 may collect and analyze real-time data to assist in controlling vehicular congestion (e.g., controlling traffic signals). As another example, the host 2102 may store surveillance videos uploaded by the UE. As another example, the host 2102 may store or control access to media content, such as video, audio, VR or AR, that the host 2102 may broadcast, multicast, or unicast to the UE. As other examples, the host 2102 may be used for energy pricing, remote control of non-time-constrained electrical loads to balance power generation needs, location services, presentation services (such as compiling diagrams, etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.
[0222] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function to reconfigure the OTT connection 2150 between the host 2102 and the UE 2106 in response to fluctuations in the measurement results. The measurement procedures and / or the network function to reconfigure the OTT connection may be implemented in software and hardware of the host 2102 and / or the UE 2106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2150 passes, and the sensors may participate in the measurement procedures by providing values of the monitored quantities exemplified above, or other physical quantities from which software may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2150 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly change the operation of the network node 2104. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates measurements by the host 2102 of throughput, propagation time, latency, etc. The measurements may be implemented in causing messages to be sent, particularly empty or "dummy" messages, using the OTT connection 2150 while software monitors propagation times, errors, etc.
[0223] The above merely illustrates the principles of the present disclosure. In light of the teachings herein, various modifications and alterations of the described embodiments will become apparent to those skilled in the art. It will thus be appreciated that those skilled in the art can devise numerous systems, configurations, and procedures that are not explicitly shown or described herein, but which embody the principles of the present disclosure and thus fall within the spirit and scope of the present disclosure. As should be understood by those skilled in the art, the various embodiments can be used together and interchangeably with each other.
[0224] The term unit as used herein may have its usual meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described herein.
[0225] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.
[0226] As described herein, the devices and / or apparatus may be represented by semiconductor chips, chipsets, or (hardware) modules comprising such chips or chipsets, but this does not exclude the possibility that the functionality of the device or apparatus may instead be implemented as a software module, such as a computer program or computer program product comprising executable software code portions for execution on or running on a processor. Furthermore, the functionality of the device or apparatus may be implemented by any combination of hardware and software. A device or apparatus may also be considered as an assembly of multiple devices and / or apparatus, whether functionally cooperating with each other or independent of each other. Moreover, devices and apparatus may be implemented distributed throughout a system, as long as the functionality of the device or apparatus is preserved. Such and similar principles are considered to be known to those skilled in the art.
[0227] Unless otherwise specified, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning in accordance with the meaning of those terms in the context of this specification and related art, and are not to be interpreted in an ideal or overly formal sense unless expressly so defined herein.
[0228] Furthermore, some terms used in this disclosure, including the specification and drawings, may be used synonymously in some instances (e.g., "data" and "information"). It should be understood that although these terms (and / or other terms that may be synonymous with each other) may be used synonymously herein, there may be instances where it is intended that such words are not used synonymously. Furthermore, to the extent that prior art knowledge has not been expressly incorporated herein by reference above, the prior art knowledge is expressly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entirety.
[0229] Additionally, embodiments of the techniques and apparatus described herein include, but are not limited to, the following listed examples. A1. A method for a user equipment (UE) configured for positioning in a radio access network (RAN), the method comprising: receiving, from a positioning node associated with the RAN, a plurality of configurations for positioning reference signals (PRS) transmitted by the nodes of the RAN, the plurality of configurations being associated with respective plurality of configuration indexes; determining a need to receive the PRS and selecting one or more of the plurality of configurations based on one or more selection rules; sending, to the positioning node, one or more requests for TRS transmission by the RAN, the one or more requests including one or more configuration indexes associated with the selected one or more configurations; A method comprising: A2. Multiple configurations are based on the following characteristics or parameters: PRS transmission periodicity, PRS transmit bandwidth, The number of PRS transmit frequency layers used, The particular PRS transmission frequency layer being used, the number of RAN nodes transmitting the PRS, A particular RAN node transmitting the PRS; The geographical configuration of the RAN nodes transmitting the PRS; Number of PRS resource sets per node, Number of PRSs per PRS resource set, the energy consumption and / or signaling overhead associated with transmitting the PRS in accordance with the configuration; the relevant geographic area; Positioning space dimension, Positioning accuracy Quality of Service (QoS), as well as Positioning Latency QoS The method of embodiment A1, wherein the two or more of the following are distinguished from one another based on one or more of: A2a. The method of embodiment A2, further comprising receiving from the positioning node an indication of a characteristic or parameter by which the plurality of configurations are distinguished, and selecting one or more of the plurality of configurations is based on the indicated characteristic or parameter. A2b. The method of any one of embodiments A1-A2a, further comprising receiving a selection rule from a positioning node. A3. Multiple settings, a first configuration including default values for configuration parameters; one or more further settings, each further setting including only configuration parameters of the configuration parameters having a value different from the default value; The method of any one of embodiments A1 to A2b, comprising: A4. The method of embodiment A3, in which the first configuration is received via a first broadcasted system information block (SIB) and the one or more further configurations are received via a second broadcasted SIB. A5. The method of embodiment A4, in which the first SIB indicates that the first setting is one of a default setting or an active setting. A6. The method of any one of embodiments A1 to A5, wherein each request includes an index associated with one selected setting. A7. The method of embodiment A6, in which the selection rule includes a consecutive order in which each configuration may be requested by the UE. A8. The one or more requests include an initial request and one or more subsequent requests, and the selection rule is: A first rule that identifies a first subset of configurations that may be requested by the UE in an initial request; and a second rule that identifies a second subset of settings that may be requested by the UE in a subsequent request; The method of embodiment A6, comprising: A9. The first subset of configurations includes a first configuration that requires the lowest energy for transmitting the PRS; the second subset includes at least one configuration that requires more energy to transmit the PRS than the first configuration; The method of embodiment A8. A10. Selecting one or more of a number of settings based on one or more selection rules is determining whether positioning based on the PRS transmission according to the first configuration will satisfy a positioning quality of service (QoS) threshold; selecting a first configuration when it is determined that a positioning QoS threshold will be met; and selecting a second subset of configurations when it is determined that the positioning QoS threshold will not be met; The method of embodiment A9, comprising: A11. The method of embodiment A10, wherein the positioning QoS threshold is related to one or more of accuracy and latency. A12. The second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting; the one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request; The second rule identifies that the second setting may be selected for a first subsequent request and that the third setting may be selected for a second subsequent request. The method of embodiment A9. A13. One or more requests include a single request that includes at least two configuration indexes; the selection rules include a third rule indicating one of more configuration parameters that must be common between the at least two configurations identified by the at least two configuration indexes; The method according to any one of embodiments A1 to A5. A14. The method of embodiment A13, wherein the third rule indicates that at least the following parameters must be common among the multiple selected configurations: PRS transmission periodicity and the specific RAN node transmitting the PRS. A15. The method of any one of embodiments A13 to A14, further comprising performing positioning measurements on PRSs that are coherently transmitted according to at least two configurations. B1. A method for a positioning node associated with a Radio Access Network (RAN), the method comprising: determining a plurality of configurations for a positioning reference signal (PRS) transmitted by a node of the RAN, the plurality of configurations being associated with respective plurality of configuration indexes; sending a plurality of configurations and associated plurality of configuration indexes to a node of the RAN and to a user equipment (UE) operating in the RAN; receiving, from the UE, one or more requests for PRS transmission by the RAN according to one or more configurations indicated by associated one or more configuration indexes; A method comprising: B1a. The method of embodiment B1, further comprising configuring the node to transmit the PRS according to one of the one or more settings indicated by the UE or one or more further settings selected by the positioning node. B2. Multiple configurations are based on the following characteristics or parameters: PRS transmission periodicity, PRS transmit bandwidth, The number of PRS transmit frequency layers used, The particular PRS transmission frequency layer being used, the number of RAN nodes transmitting the PRS, A particular RAN node transmitting the PRS; The geographical configuration of the RAN nodes transmitting the PRS; Number of PRS resource sets per node, Number of PRSs per PRS resource set, the energy consumption and / or signaling overhead associated with transmitting the PRS in accordance with the configuration; the relevant geographic area; Positioning space dimension, Positioning accuracy Quality of Service (QoS), as well as Positioning Latency QoS The method of embodiment B1 or B1a, distinguished from each other on one or more of: B2a. The method of embodiment B2, further comprising sending, to the UE, an indication of the characteristics or parameters with different configurations. B3. Multiple settings: a first configuration including default values for configuration parameters; one or more further settings, each further setting including only configuration parameters of the configuration parameters having a value different from the default value; The method of any one of embodiments B1 to B2a, comprising: B4. The method of embodiment B3, in which the first configuration is sent by the RAN via broadcast of a first system information block (SIB), and the one or more further configurations are sent by the RAN via broadcast of a second SIB. B5. The method of embodiment B4, in which the first SIB indicates that the first setting is one of a default setting or an active setting. B5a. The method of any one of embodiments B1-B5, further comprising sending, to the UE, a selection rule for selecting between the multiple configurations. B6. The method of embodiment B5a, in which each request includes an index associated with a selected setting. B7. The method of embodiment B5a or B6, in which the selection rule includes a sequential order in which each configuration may be requested by the UE. B8. The one or more requests include an initial request and one or more subsequent requests, and the selection rule is: A first rule that identifies a first subset of configurations that may be requested by the UE in an initial request; and a second rule that identifies a second subset of settings that may be requested by the UE in a subsequent request; The method of embodiment B5a or B6, comprising: B9. The first subset includes a first configuration requiring the lowest energy for transmitting the PRS; the second subset includes at least one configuration that requires more energy to transmit the PRS than the first configuration; The method of embodiment B8. B10. The method of embodiment B9, wherein the selection rule includes a positioning quality of service (QoS) threshold for selecting between the first configuration and the second subset of configurations. B11. The method of embodiment B10, wherein the positioning QoS threshold is related to one or more of accuracy and latency. B12. the second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting; the one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request; The second rule identifies that the second setting may be selected for a first subsequent request and that the third setting may be selected for a second subsequent request. The method of embodiment B9. B13. One or more requests include a single request that includes at least two configuration indexes; the selection rules include a third rule indicating one of more configuration parameters that must be common between the at least two configurations identified by the at least two configuration indexes; The method according to embodiment B5a. B14. The method of embodiment B13, wherein the third rule indicates that at least the following parameters must be common between at least two configurations: PRS transmission periodicity and the particular RAN node transmitting the PRS. B15. The method of embodiment B13 or B14, in which configuring the nodes includes configuring a plurality of nodes to coherently transmit PRS according to at least two configurations. B16. Determining multiple settings Obtaining default settings for PRS transmission; Multiple settings, Measurements made by the UE on the transmitted PRS according to default configuration; Node capabilities, The number of UEs operating in the RAN; and One or more distinguishing characteristics or parameters Based on this, The method of any one of embodiments B1 to B15, comprising: B17. Determining multiple settings means determining multiple settings. Measurements made by the UE on PRSs transmitted according to multiple configurations; The updated capabilities of the node, an updated number of UEs operating in the RAN; and One or more distinguishing characteristics or parameters The method of embodiment B16, comprising adapting based on one or more of: C1. A method for a network node of a Radio Access Network (RAN), the method comprising: receiving, from a positioning node, a plurality of configurations for positioning reference signal (PRS) transmission, the plurality of configurations being associated with respective plurality of configuration indexes; thereafter receiving, from the positioning node, one or more requests for PRS transmission according to one or more of the configurations identified by the associated one or more configuration indexes; transmitting the PRS according to one or more of the configurations identified by the associated one or more configuration indexes; A method comprising: C2. Multiple configurations are provided for the following characteristics or parameters: PRS transmission periodicity, PRS transmit bandwidth, The number of PRS transmit frequency layers used, The particular PRS transmission frequency layer being used, the number of RAN nodes transmitting the PRS, A particular RAN node transmitting the PRS; The geographical configuration of the RAN nodes transmitting the PRS; Number of PRS resource sets per node, Number of PRSs per PRS resource set, the energy consumption and / or signaling overhead associated with transmitting the PRS in accordance with the configuration; the relevant geographic area; Positioning space dimension, Positioning accuracy Quality of Service (QoS), as well as Positioning Latency QoS The method of embodiment C1, wherein the two or more of the following are distinguished from one another based on one or more of: C3. Multiple settings: a first configuration including default values for configuration parameters; one or more further settings, each further setting including only configuration parameters of the configuration parameters having a value different from the default value; The method of embodiment C1 or C2, comprising: C4. The method of embodiment C3, further comprising broadcasting a first configuration in a first system information block (SIB) and one or more additional configurations in a second SIB. C5. The method of embodiment C4, in which the first SIB indicates that the first setting is one of a default setting or an active setting. C6. The one or more requests include an initial request and one or more subsequent requests, and the configuration is: a first subset of configurations that may be requested by the UE in an initial request; and a second subset of settings that may be requested by the UE in a subsequent request; The method of any one of embodiments C1 to C5, comprising: C7. The first subset of configurations includes a first configuration requiring the lowest energy for transmitting the PRS; the second subset includes at least one configuration that requires more energy to transmit the PRS than the first configuration; The method of embodiment C6. C8. The method of embodiment C7, wherein the second subset includes a second setting that requires more energy than the first setting, and a third setting that requires more energy than the second setting. C9. The one or more requests include a single request that includes at least two configuration indexes; At least a PRS transmission periodicity is common between at least two configurations identified by at least two configuration indexes; The method of any one of embodiments C1 to C5. C10. The method of embodiment C9, in which transmitting the PRS includes coherently transmitting the PRS according to at least two configurations. D1. A user equipment (UE) configured for positioning in a radio access network (RAN), the UE comprising: a communications interface circuit configured to communicate with nodes of the RAN and with a positioning node associated with the RAN; a processing circuit operably coupled to the wireless transceiver circuit, whereby the processing circuit and the wireless transceiver circuit are configured to perform operations corresponding to any of the methods described in any of embodiments A1 to A15; A user equipment (UE) comprising: D2. A user equipment (UE) configured for positioning in a radio access network (RAN), the UE being further configured to perform an operation corresponding to any of the methods described in embodiments A1 to A15. D3. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured for positioning in a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods described in embodiments A1 to A15. D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured for positioning in a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods described in embodiments A1 to A15. E1. A positioning node configured to operate with a Radio Access Network (RAN), the positioning node comprising: a communications interface circuit configured to communicate with nodes of the RAN and with user equipment (UE) operating in the RAN; a processing circuit operably coupled to the communications interface circuit, whereby the processing circuit and the communications interface circuit are configured to perform operations corresponding to any of the methods described in embodiments B1 to B170; A positioning node comprising: E2. A positioning node configured to operate with a radio access network (RAN), the positioning node further configured to perform operations corresponding to any of the methods described in embodiments B1 to B17. E3. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a positioning node configured to operate with a radio access network (RAN), configure the positioning node to perform operations corresponding to any of the methods described in embodiments B1 to B17. E4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a positioning node configured to operate with a radio access network (RAN), configure the positioning node to perform operations corresponding to any of the methods described in embodiments B1 to B17. F1. A network node of a Radio Access Network (RAN), the network node comprising: a communications interface circuit configured to communicate with a user equipment (UE) and a positioning node; a processing circuit operably coupled to the communications interface circuit, whereby the processing circuit and the communications interface circuit are configured to perform operations corresponding to any of the methods described in embodiments C1 to C10; A network node comprising: F2. A network node of a radio access network (RAN), the network node being configured to perform operations corresponding to any of the methods described in embodiments C1 to C10. F3. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node of a radio access network (RAN), configure the network node to perform operations corresponding to any of the methods described in embodiments C1 to C10. F4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node of a radio access network (RAN), configure the network node to perform operations corresponding to any of the methods described in embodiments C1 to C10.
Claims
1. A method for a user equipment (UE) configured for positioning in a radio access network (RAN), the method comprising: receiving (1310) from a positioning node associated with the RAN: a plurality of configurations for positioning reference signals (PRSs) transmitted by the RAN; and corresponding plurality of configuration indices associated with the plurality of configurations; determining a need to receive a PRS and selecting (1340) one or more of the plurality of configurations based on one or more selection rules; and transmitting (1350) to the positioning node one or more requests for PRS transmission by the RAN, the one or more requests including one or more configuration indices associated with the selected one or more configurations. A method comprising the above.
2. The method of claim 1, wherein the plurality of configurations are distinguished from each other based on one or more of the following characteristics or parameters, namely: PRS transmission periodicity; PRS transmission bandwidth; number of PRS transmission frequency layers used; specific PRS transmission frequency layer used; number of RAN nodes transmitting PRS; specific RAN node transmitting PRS; geographical configuration of RAN nodes transmitting PRS; number of PRS resource sets per node; number of PRSs per PRS resource set; energy consumption and / or signaling overhead associated with transmitting a PRS according to the configuration; associated geographical area; positioning space dimension; positioning accuracy service quality (QoS); and positioning latency QoS.
3. The method of claim 2, further comprising receiving (1320) from the positioning node an indication of the characteristics or parameters by which the plurality of configurations are distinguished, and selecting one or more of the plurality of configurations based on the indicated characteristics or parameters.
4. The method of claim 1, further comprising receiving (1330) the selection rules from the positioning node, the selection rules including a sequential order such that each configuration can be requested by the UE in that order.
5. The plurality of configurations include: a first configuration including default values for configuration parameters; One or more additional settings, each additional setting including only those of the setting parameters having a value different from the default value The method according to claim 1, comprising
6. The first setting is received via a broadcast first system information block (SIB), The one or more additional settings are received via a broadcast second SIB, The first SIB indicates that the first setting is one of a default setting or an active setting, The method according to claim 5
7. The method according to claim 1, wherein each request includes one index related to one selected setting
8. The one or more requests include an initial request and one or more subsequent requests, and the selection rule is A first rule for identifying a first subset of settings that can be requested by the UE in the initial request, A second rule for identifying a second subset of settings that can be requested by the UE in the subsequent request The method according to claim 4, comprising
9. The first subset of settings includes a first setting that requires a minimum energy for transmitting a PRS, The second subset includes at least one setting that requires more energy for transmitting a PRS than the first setting, The method according to claim 8
10. Selecting one or more of the plurality of settings (1340) based on one or more selection rules includes Determining (1341) whether positioning based on PRS transmission according to the first setting will meet a positioning service quality (QoS) threshold, Selecting (1342) the first setting when it is determined that the positioning QoS threshold will be met, Selecting (1341) the settings of the second subset when it is determined that the positioning QoS threshold will not be met And The positioning QoS threshold relates to one or more of accuracy and latency, The method according to claim 9
11. The second subset includes a second setting that requires more energy than the first setting and a third setting that requires more energy than the second setting, The one or more subsequent requests include a first subsequent request and a second subsequent request after the first subsequent request, The second rule identifies that the second setting can be selected for the first subsequent request and that the third setting can be selected for the second subsequent request, The method according to claim 9.
12. The one or more requests include a single request that includes at least two setting indexes, The selection rule includes a third rule that indicates one or more setting parameters that must be common among at least two settings associated with the at least two setting indexes included in the single request, The method according to claim 1.
13. The method according to claim 12, wherein the third rule indicates that at least the following parameters, namely, the PRS transmission periodicity and the specific RAN node that transmits the PRS, must be common among the at least selected settings.
14. The method according to claim 12, further comprising performing a positioning measurement (1360) on a PRS that is transmitted coherently according to the at least two settings associated with the at least two setting indexes included in the single request.
15. A method for a positioning node associated with a radio access network (RAN), the method comprising: determining (1410) a plurality of settings for a positioning reference signal (PRS) transmitted by a RAN node, the plurality of settings being associated with a corresponding plurality of setting indexes, sending (1420) the plurality of settings and the associated plurality of setting indexes to the RAN node and to a user equipment (UE) operating in the RAN, receiving (1450) from the UE one or more requests regarding PRS transmission by the RAN, the one or more requests including one or more of the plurality of setting indexes associated with one or more of the plurality of settings selected by the UE, A method comprising.
16. Determining (1410) the plurality of settings comprises obtaining (1411) a default setting for PRS transmission, the plurality of settings being measurements made by the UE on a PRS transmitted according to the default setting, the capabilities of the nodes, the number of UEs operating in the RAN, and one or more differentiating characteristics or parameters to determine (1412) based on; and A method according to claim 15, comprising. **Claim 17** Determining (1410) the plurality of configurations causes the plurality of configurations to be measurements made by a UE on PRSs transmitted according to the plurality of configurations, the updated capabilities of the nodes, the updated number of UEs operating in the RAN, and the one or more differentiating characteristics or parameters to adapt (1413) based on one or more of; A method according to claim 16, comprising. **Claim 18** A method for a radio access network (RAN) node, the method comprising: from a positioning node associated with the RAN, a plurality of configurations for transmitting positioning reference signals (PRSs), and a corresponding plurality of configuration indices associated with the plurality of configurations to receive (1510); and subsequently, from the positioning node, to receive (1530) one or more requests for PRS transmission, wherein the one or more requests include one or more of the plurality of configuration indices; to transmit (1540) a PRS according to one or more of the configurations associated with the one or more configuration indices included in the one or more requests A method comprising. **Claim 19** A user equipment (UE) (205, 310, 410, 1612, 1700, 2106) configured for positioning in a radio access network (RAN) (199, 299, 420, 1604), the UE comprising: from a positioning node (440, 450, 460, 1220, 1800, 2002) associated with the RAN, a plurality of configurations for positioning reference signals (PRSs) transmitted by the RAN, and a corresponding plurality of configuration indices associated with the plurality of configurations to receive; to determine a need to receive a PRS and, based on one or more selection rules, to select one or more of the plurality of configurations; to transmit to the positioning node one or more requests for PRS transmission by the RAN, the one or more requests including one or more configuration indices associated with the selected one or more configurations A user equipment (UE) (205, 310, 410, 1612, 1700, 2106) further configured to perform
20. The UE according to claim 19, further configured to perform an operation corresponding to the method according to any one of claims 2 to 14.
21. A computer program comprising computer-executable instructions that, when executed by a processing circuit (1702) of a user equipment (UE) (205, 310, 410, 1612, 1700, 2106) configured for positioning in a radio access network (RAN) (199, 299, 420, 1604), configure the UE to perform an operation corresponding to the method according to any one of claims 1 to 14.
22. A positioning node (440, 450, 460, 1220, 1800, 2002) configured to operate with a radio access network (RAN) (199, 299, 420, 1604), the positioning node determining a plurality of settings for a positioning reference signal (PRS) transmitted by a RAN node (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104), the plurality of settings being related to a corresponding plurality of setting indices, sending the plurality of settings and the related plurality of setting indices to the RAN node and to a user equipment (UE) (205, 310, 410, 1612, 1700, 2106) operating in the RAN, receiving from the UE one or more requests for PRS transmission by the RAN, the one or more requests including one or more of the plurality of setting indices related to one or more of the plurality of settings selected by the UE, A positioning node (440, 450, 460, 1220, 1800, 2002) further configured to perform
23. A computer program comprising computer-executable instructions that, when executed by a processing circuit (442, 452, 462, 1802, 2004) of a positioning node (440, 450, 460, 1220, 1800, 2002) configured to operate with a radio access network (RAN) (199, 299, 420, 1604), configure the positioning node to perform an operation corresponding to the method according to any one of claims 15 to 17.
24. A radio access network (RAN) node (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104) configured to support positioning of a user equipment (UE) (205, 310, 410, 1612, 1700, 2106), wherein the RAN node receives from a positioning node (440, 450, 460, 1220, 1800, 2002) associated with the RAN a plurality of settings for transmitting a positioning reference signal (PRS), and corresponding plurality of setting indexes associated with the plurality of settings and then receives from the positioning node one or more requests for PRS transmission, wherein the one or more requests include one or more of the plurality of setting indexes, and further configured to transmit a PRS in accordance with one or more of the settings associated with the one or more setting indexes included in the one or more requests. A radio access network (RAN) node (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104).
25. A computer program comprising computer-executable instructions that, when executed by a processing circuit (1802, 2004) of a radio access network (RAN) node (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104), configure the RAN node to perform an operation corresponding to any of the methods according to claim 18.