Method and device for defining and signaling a pre-configured positioning reference signal (PRS).

Abstract

An embodiment includes a method for a user equipment (UE) configured for positioning in a radio access network (RAN). Such a method includes receiving, from a positioning node associated with the RAN, a plurality of configurations for a positioning reference signal (PRS) transmitted by the RAN and a corresponding plurality of configuration indexes associated with the plurality of configurations. Such a method includes determining a need to receive the PRS and selecting one or more of the plurality of configurations based on one or more selection rules, and transmitting, to the positioning node, one or more requests for PRS transmission by the RAN. The one or more requests include one or more configuration indexes associated with the selected one or more configurations. Other embodiments include complementary methods for the positioning node and for the RAN node, as well as UEs, positioning nodes, and RAN nodes configured to implement such methods.

Description

[Technical Field]

[0001] The present disclosure relates generally to wireless communication networks, and more specifically to network transmission of positioning reference signals (PRS) that can be used to determine the geographical location of user equipment (UE). [Background Art]

[0002] Currently, the fifth generation ("5G") of cellular systems, also called New Radio (NR), is being standardized within the 3rd Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine-type communication (MTC), ultra-reliable low-latency communication (URLLC), sidelink D2D (device-to-device), and several other use cases.

[0003] FIG. 1 shows an exemplary high-level diagram of a 5G network architecture consisting of a next generation RAN (NG-RAN) 199 and a 5G core (5GC) 198. NG-RAN 199 may comprise a set of gNBs connected to 5GC via one or more NG interfaces, such as gNodeBs (gNBs) 100 and 150 connected via interfaces 102 and 152, respectively. Further, gNBs may be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNB 100 and gNB 150. For the NR interface to UE, each gNB may support Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination thereof.

[0004] NG-RAN199 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 them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the relevant 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 Figure 1 includes a centralized (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB100 includes gNB-CU110 and gNB-DU120 and 130. A CU is a logical node that performs various gNB functions, such as hosting higher-layer protocols and controlling the operation of DUs, while a DU is a logical node that hosts lower-layer protocols and can include various subsets of gNB functions. Thus, each CU and DU can include processing circuits and various circuits required to perform their respective functions, including transceiver circuits (for example, for communication) and power supply circuits.

[0006] The gNB-CU connects to the gNB-DU on their respective F1 logical interfaces, such as interfaces 122 and 132 shown in Figure 1. The gNB-CU and the connected gNB-DU are only visible 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 CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing (OFDM)) in DL and both CP-OFDM and DFT-Spread OFDM (DFT-S-OFDM) in UL. As another example, in the time domain, NR DL and NR UL physical resources are organized into 1ms subframes of equal size. These subframes are further divided into multiple slots of equal duration, each containing multiple OFDM base symbols. However, time-frequency resources can be configured much more flexibly for NR cells than for LTE cells. For example, instead of a fixed 15kHz OFDM subcarrier spacing (SCS) as in LTE, the NR SCS can range from 15 to 240kHz, and even larger SCSs may be considered for future NR releases.

[0008] In addition to providing coverage via cells, as in the case of LTE, NR networks also provide coverage via "beams." Generally, a downlink (DL, i.e., network to UE) "beam" is the coverage area of ​​network-transmitted reference signals (RS) that can be measured or monitored by the UE. In NR, for example, RS can include any of the following: Synchronization Signal / PBCH Block (SSB), Channel State Information RS (CSI-RS), Third-Order Reference Signal (or any other synchronization signal), Positioning RS (PRS), Demodulation RS (DMRS), Phase Tracking RS (PTRS), etc. Generally, SSB is available to all UEs, regardless of the state of their connectivity to the network, while other RSs (e.g., CSI-RS, DM-RS, PTRS) are relevant to specific UEs with network connectivity.

[0009] The 3GPP standard provides various ways of positioning UEs operating in an NR network (e.g., determining their location, localizing them, and / or determining their location). Generally, a positioning node configures a target device (e.g., a UE) and / or a radio network node (RNN, e.g., a 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, a positioning measurement may include timing (and / or timing difference) measurements relating to the UE, the network, and / or satellite transmissions. 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 based on network-transmitted positioning reference signals (PRS), which can extend 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 degrees of flexibility to significantly improve positioning accuracy. Further enhancements, including "on-demand PRS," are planned for NR Rel-17, which will allow UEs to request the network to transmit PRS in settings that facilitate UE positioning measurement and (optionally) location determination. [Overview of the project]

[0011] However, the applicant recognized that there are various issues, problems, and / or difficulties related to PRS transmission in the split node architecture shown in Figure 1.

[0012] Embodiments of this disclosure provide specific improvements to UE positioning in wireless networks, such as by providing, enabling, and / or facilitating solutions to overcome exemplary problems summarized above and described in more detail below.

[0013] Embodiments include methods (e.g., procedures) for a UE configured for positioning in a radio access network (RAN).

[0014] These exemplary methods may include receiving from a positioning node associated with a RAN multiple settings for PRS transmitted by the RAN's nodes, and multiple corresponding setting indices associated with the multiple settings. In other words, each setting is represented by a setting index, corresponds to a setting index, and / or is associated with a setting index, and vice versa. For example, a positioning node may be an LMF. These exemplary methods may also include determining the need to receive a PRS and selecting one or more of the multiple settings based on one or more selection rules. These exemplary methods may also include sending one or more requests to the positioning node for TRS transmission by the RAN. One or more requests include one or more setting indices associated with the one or more selected settings.

[0015] In various embodiments, multiple settings may have the following characteristics or parameters, namely: ·PRS transmission periodicity, • PRS transmission bandwidth, • Number of PRS transmit frequency layers used, • Specific PRS transmit frequency layers used, • Number of RAN nodes that send PRS, • A specific RAN node that sends PRS, • Geographic configuration of RAN nodes that transmit PRS, • Number of PRS resource sets per node, • Number of PRS per PRS resource set, • Energy consumption and / or signaling overhead associated with transmitting PRS according to the settings. • Relevant geographical area, • Positioning spatial dimension, • Positioning accuracy, Quality of Service (QoS), and Positioning Latency QoS They can be distinguished from one or more of the following:

[0016] In some embodiments, these exemplary methods may also include receiving instructions from a positioning node for characteristics or parameters, where multiple settings are distinguished. In such embodiments, selecting one or more of the multiple settings may be based on the indicated characteristics or parameters. In some embodiments, these exemplary methods may also include receiving selection rules from a positioning node.

[0017] In some embodiments, the configuration includes a first configuration containing default values ​​for configuration parameters, and one or more further configurations. Each further configuration includes only the configuration parameters among 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 system information block (SIB), and one or more further configurations may be received via a broadcasted second SIB. In some of these embodiments, the first SIB indicates that the first configuration is either a default configuration or an active configuration.

[0018] In some embodiments, each request includes one index associated with one selected setting. In some of these embodiments, the selection rule includes a sequential order in which each setting may be requested by the UE.

[0019] In other embodiments of these, 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 requests. In some variants, the first subset of settings includes a first setting that requires the minimum energy to transmit a PRS, and the second subset includes at least one setting that requires more energy to transmit a PRS than the first setting.

[0020] In some examples of these variations, the selected action may include determining whether positioning based on PRS transmissions following a first setting will meet the positioning quality of service (QoS) threshold, selecting the first setting when it is determined that the positioning QoS threshold will be met, and selecting a second subset of settings when it is determined that the positioning QoS threshold will not be met. In some cases, the positioning QoS threshold relates 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. Furthermore, one or more subsequent requests include a first subsequent request and a second subsequent request following 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 comprise a single request including at least two configuration indexes. The selection rule includes a third rule that indicates one of a plurality of configuration parameters that must be common between 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, i.e., PRS transmission periodicity and a specific RAN node that transmits the PRS, must be common between the at least two configurations.

[0023] In some of these embodiments, these exemplary methods can also include performing positioning measurements on PRS that are coherently transmitted in accordance with at least two configurations associated with at least two configuration indexes included in a single request.

[0024] Other embodiments include a method (e.g., a procedure) for a positioning node associated with a RAN.

[0025] These exemplary methods can include determining a plurality of configurations for PRS transmitted by a node of the RAN. The plurality of configurations are associated with a corresponding plurality of configuration indexes. These exemplary methods can also include sending the plurality of configurations and the associated plurality of configuration indexes to a RAN node and to a UE operating in the RAN. These exemplary methods can also include receiving one or more requests for PRS transmission by the RAN from the UE, wherein 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 plurality of configurations may be distinguished from each other based on any of the characteristics or parameters summarized above with reference to UE embodiments. In some embodiments, these exemplary methods can also include sending an indication of the characteristics or parameters based on which the plurality of configurations are distinguished to the UE.

[0027] In some embodiments, the configuration may include a first configuration that includes default values ​​for configuration parameters, and one or more further configurations. Each further configuration may include only the 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 a broadcast of a first SIB, and one or more further configurations may be sent by the RAN via a broadcast of a second SIB. In some of these embodiments, the first SIB indicates that the first configuration is either the default configuration or one of the active configurations.

[0028] In some embodiments, these exemplary methods may also include configuring a RAN node to transmit a PRS according to one or more settings selected by the UE, or one or more further settings selected by the positioning node. In some of these embodiments, these exemplary methods may also include sending a selection rule to the UE for selecting among a plurality of settings.

[0029] In some of these embodiments, each request includes one index related to one setting selected by the UE. In some variations of these embodiments, the selection rule may include a sequential order in which each setting may be requested by the UE.

[0030] In other variations of these embodiments, 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 requests.

[0031] In some variants, a first subset includes a first setting that requires the minimum energy to transmit a PRS, and a second subset includes at least one setting that requires more energy to transmit a PRS than the first setting. In some examples of these variants, the selection rule may include a positioning QoS threshold for selecting between the first setting and the settings in the second subset. In some cases, the positioning QoS threshold relates 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. Furthermore, one or more subsequent requests include a first subsequent request and a second subsequent request following 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 other embodiments of these, one or more requests include a single request containing at least two configuration indices. The selection rule includes a third rule indicating one of more configuration parameters that must be common among at least two configurations related to at least two configuration indices included in the single request. In some variants, the third rule indicates that at least the following parameters, namely PRS transmission periodicity and the specific RAN node that transmits the PRS, must be common among at least two configurations. In some embodiments of these, configuring a RAN node includes configuring multiple RAN nodes to coherently transmit PRS according to at least two configurations related to at least two configuration indices included in the single request.

[0034] In some embodiments, determining multiple settings involves obtaining a default setting for PRS transmission and multiple settings (to be sent, for example, to UE and RAN nodes). • Measurements performed by the UE on PRS sent according to default settings. • The ability of the node to send PRS • The number of UEs operating in RAN, and • One or more distinguishing characteristics or parameters (for example, as described above) This includes making decisions based on [the following].

[0035] In some embodiments, determining multiple settings means that multiple settings • Measurements performed by the UE on PRS transmitted according to multiple settings. · Node's updated capabilities, • The number of updated UEs operating in RAN, and • One or more distinguishing characteristics or parameters This may include adapting based on one or more of the following.

[0036] Other embodiments include methods (e.g., procedures) for RAN nodes.

[0037] These exemplary methods may include receiving from a positioning node associated with the RAN (e.g., LMF) a set of settings for a PRS to be transmitted by a node in the RAN, and a set of corresponding setting indices associated with the set of settings. In other words, each setting is represented by a setting index, corresponds to a setting index, and / or is associated with a setting index, and vice versa. These exemplary methods may also include receiving one or more requests from the positioning node for a PRS transmission. One or more requests may include one or more of the set of settings. These exemplary methods may also include transmitting a PRS according to one or more of the settings associated with one or more setting indices included in one or more requests.

[0038] In various embodiments, multiple settings may be distinguished from one another based on either the characteristics or parameters described above with respect to the UE embodiment.

[0039] In some embodiments, the configuration may include a first configuration that includes default values ​​for configuration parameters, and one or more further configurations. Each further configuration may include only the configuration parameters among the configuration parameters that have values ​​different from the default values. In some of these embodiments, these exemplary methods may also include broadcasting the first configuration in a first SIB and broadcasting one or more further configurations in a second SIB. In some of these embodiments, the first SIB indicates that the first configuration is either a default configuration or one of the active configurations.

[0040] In some embodiments, one or more requests include an initial request and one or more subsequent requests, and a configuration includes a first subset of configurations that can be requested by the UE in the initial request and a second subset of configurations that can be requested by the UE in the subsequent requests. In some of these embodiments, the first subset of configurations includes a first configuration that requires the minimum energy to transmit a PRS, and the second subset includes at least one configuration that requires more energy to transmit a PRS than the first configuration. In some variants, the second subset includes a second configuration that requires more energy than the first configuration and a third configuration that requires more energy than the second configuration.

[0041] In other embodiments, one or more requests include a single request that includes at least two configuration indices. At least the PRS transmission periodicity is common among at least two settings associated with at least two configuration indices included in the single request. In some of these embodiments, transmitting a PRS can be done coherently according to at least two settings associated with at least two configuration indices included in the single request.

[0042] Other embodiments include a UE (e.g., a radio device) configured to perform an operation corresponding to any of the exemplary methods described herein, a positioning node (e.g., an LMF, E-SMLC, SUPL node), and a RAN node (e.g., a base station, eNB, gNB, ng-eNB, TRP). Other embodiments include a non-temporary computer-readable medium that stores program instructions that, when executed by a processing circuit, configure such a UE, positioning node, or RAN node to perform an operation corresponding to any of the exemplary methods described herein.

[0043] The embodiments described herein provide flexible and efficient techniques for supporting on-demand PRS transmissions as network conditions change. The embodiments can also be used to select a PRS configuration suitable for not just one, but many UEs, which provides more efficient UE positioning based on DL PRS transmissions. The embodiments can also reduce energy consumption of RAN nodes by avoiding the transmission of unnecessary PRS resources.

[0044] These and other purposes, features and advantages of the embodiments of this disclosure will become apparent from reading the embodiments for carrying out the invention described below in view of the drawings, which are briefly described below. [Brief explanation of the drawing]

[0045] [Figure 1] This is a high-level diagram of an exemplary 5G / NR network architecture. [Figure 2] This is a high-level diagram of an exemplary 5G / NR network architecture. [Figure 3] This diagram shows exemplary NR user plane (UP) and control plane (CP) protocol layers. [Figure 4] This is a block diagram showing a high-level architecture for UE positioning in an NR network. [Figure 5] This is a signal flow diagram for an exemplary multi-RTT positioning procedure. [Figure 6] Figure 1 shows an illustrative breakdown of positioning relationship functions in the split gNB architecture. [Figure 7] This figure shows an exemplary hybrid transmit beamforming configuration. [Figure 8] Figures A and B show two exemplary beam sweep configurations with two and three subarrays, respectively. [Figure 9] This figure shows exemplary signaling procedures used to obtain positioning reference signal (PRS) settings under different scenarios. [Figure 10] This figure shows exemplary signaling procedures used to obtain positioning reference signal (PRS) settings under different scenarios. [Figure 11] This figure shows the ASN.1 data structure for an exemplary OnDemand-PRS-ClassificationCriteria field in various embodiments of the present disclosure. [Figure 12] This figure shows the signaling flow between a positioning node (e.g., LMF) and a RAN node (e.g., gNB) according to various embodiments of the present disclosure. [Figure 13] This is a flowchart of exemplary methods (e.g., procedures) for UE according to various embodiments of the present disclosure. [Figure 14] This is a flowchart of exemplary methods (e.g., procedures) for a positioning node (e.g., LMF) according to various embodiments of the present disclosure. [Figure 15] This is a flowchart of exemplary methods (e.g., procedures) for RAN nodes (e.g., gNB, TRP, etc.) according to various embodiments of the present disclosure. [Figure 16] This figure shows a communication system according to various embodiments of the present disclosure. [Figure 17] This figure shows UEs according to various embodiments of the present disclosure. [Figure 18] This figure shows network nodes according to various embodiments of the present disclosure. [Figure 19] This figure shows a host computing system according to various embodiments of the present disclosure. [Figure 20] This is a block diagram of a virtualization environment in which the functions implemented by some embodiments of this disclosure may be virtualized. [Figure 21] This figure shows a communication between a host computing system, a network node, and an UE via multiple connections, according to various embodiments of the present disclosure, wherein at least one of the connections is wireless. [Modes for carrying out the invention]

[0046] Next, some of the embodiments intended herein will be described more thoroughly with reference to the accompanying drawings. 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 only to the embodiments described herein. Rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0047] In general, all terms used herein should be interpreted according to their ordinary meanings in the relevant art, unless otherwise explicitly stated and / or implied by the context in which they are used. All references to one (a / an) / that (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 otherwise expressly stated. No step of any method and / or procedure disclosed herein has to be performed in the strict order disclosed unless the step is expressly described as following or preceding another step, and / or if it is implicit that a step must follow or precede another step. Any feature of any embodiment disclosed herein may, in any case, be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment 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] Furthermore, the following terms will be used throughout the explanation given below. • Wireless node: As used herein, “wireless node” may be either a “wireless access node” or a “wireless device”. • Radio access node: As used herein, “radio access node” (or equivalently, “radio network node,” “radio access network node,” or “RAN node”) can be any node in the radio access network (RAN) of a cellular communication 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., new radio (NR) base stations (gNBs) in 3GPP fifth-generation (5G) NR networks, or extended or evolved node B (eNBs) in 3GPP LTE networks), base station distributed components (e.g., CUs and DUs), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, femto base stations, or home base stations), radio access backhaul integrated transmission (IAB) nodes, transmit points (TPs), transmit / receive points (TRPs), remote radio units (RRUs or RRHs), and relay nodes. • Core Network Nodes: As used herein, “core network nodes” refers to any type of node in the core network. Some examples of core network nodes include, for example, Mobility Management Entity (MME), Serving Gateway (SGW), PDN Gateway (P-GW), Policy and Billing Rule Function (PCRF), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Billing Function (CHF), Policy Control Function (PCF), Authentication Server Function (AUSF), Location Management Function (LMF), etc. • Wireless device: As used herein, “wireless device” (or abbreviated “WD”) is any type of device that has access to a cellular communication network (i.e., is served by a cellular communication network) by communicating wirelessly with network nodes and / or other wireless devices. Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information in the air. Unless otherwise stated, the term “wireless device” is used herein interchangeably with “user equipment” (or abbreviated “UE”). 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 devices, wearable devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop-based devices (LMEs), smart devices, wireless customer premises equipment (CPEs), mobile communications (MTC) devices, Internet of Things (IoT) devices, and in-vehicle wireless terminal devices. • Network Node: As used herein, “Network Node” refers to any node that is part of either a wireless access network (e.g., a wireless access node as described above or an equivalent name) or the core network of a cellular communication network (e.g., a core network node as described above). Functionally, a network node is a device that is configured, set up, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in the cellular communication network to enable and / or provide wireless access to wireless devices and / or to perform other functions in the cellular communication network (e.g., administration). • Base station: As used herein, “base station” may include physical or logical nodes that transmit or control the transmission of radio signals, such as eNBs, gNBs, ng-eNBs, en-gNBs, centralized units (CUs) / distributed units (DUs), transmitting radio network nodes, transmitting points (TPs), transmitting receiving points (TRPs), remote radio heads (RRHs), remote radio units (RRUs), distributed antenna systems (DASs), relays, and the like. • Location Server: As used herein, “Location Server” may refer to a network node that has the ability to perform positioning functions, such as providing support data and / or requesting positioning measurements and / or calculating a location based on the 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 to be received by the UE in order to perform a positioning measurement, such as DL reference signal, PRS, SSB, synchronization signal, DM-RS, CSI-RS, etc. • Positioning Measurements: As used herein, “positioning measurements” may include timing measurements (e.g., Time to Arrive Difference (TDOA), RSTD, Time to Arrive (TOA), Rx-Tx, RTT, etc.), power-based measurements (e.g., RSRP, RSRQ, SINR, etc.), and / or identifier detection / measurement (e.g., cell ID, beam ID, etc.) set up for positioning methods (e.g., OTDOA, E-CID, etc.). UE positioning measurements may be reported to network nodes or used by the UE for positioning purposes. • Positioning beam: As used herein, “positioning beam” may include any beam used for positioning purposes, such as for a measurement that carries at least one positioning signal and / or supports one or more positioning methods (e.g., OTDOA, AOA, etc.). A positioning beam may have explicit identification information of its own, or it may be identified through an index associated with the particular signal that the beam carries.

[0049] The above provisions are not intended to be exclusive. In other words, various terms among the above terms may be explained and / or described elsewhere in this disclosure using the same or similar technical terms. Nevertheless, to the extent that such other explanations and / or descriptions conflict with the above provisions, the above provisions should prevail.

[0050] Please note that the descriptions provided herein focus on 3GPP cellular communication systems, and therefore, 3GPP terminology or similar terminology will be frequently used. However, the concepts disclosed herein are not limited to 3GPP systems. Furthermore, although the term “cell” is used herein, a “beam” may be used instead of a cell (particularly with respect to 5G NR), and therefore, please understand that the concepts described herein apply equally to both cells and beams.

[0051] Figure 2 shows another high-level diagram of an exemplary 5G network architecture including NG-RAN299 and 5GC298. NG-RAN299 can include gNBs (e.g., 210a, b) and ng-eNBs (e.g., 220a, b) interconnected with each other via their respective Xn interfaces. The gNBs and ng-eNBs are also connected to 5GC298 via NG interfaces, and more specifically, to access and mobility management functions (AMFs, e.g., 230a, b) via their respective NG-C interfaces and to user plane functions (UPFs, e.g., 240a, b) via their respective NG-U interfaces. Furthermore, the AMFs can communicate with one or more policy control functions (PCFs, e.g., 250a, b) and network exposure functions (NEFs, e.g., NEF260a, b).

[0052] Each gNB210 can support an NR radio interface, including frequency division duplex (FDD), time division duplex (TDD), or a combination thereof. Each ng-eNB220 can support a fourth-generation (4G) Long-Term Evolution (LTE) radio interface. However, unlike conventional LTE eNBs, the ng-eNB220 connects to 5GC via the NG interface. Each gNB and ng-eNB can serve a geographical coverage area that includes another cell, such as cells 211a~b and 221a~b shown in Figure 2. Depending on the specific cell in which UE205 is located, UE205 can communicate with the gNB or ng-eNB serving that particular cell, respectively, via the NR or LTE radio interface. Although Figure 2 shows gNBs and ng-eNBs separately, it is also possible for a single NG-RAN node to provide both types of functionality.

[0053] Positioning-related information, such as support data and positioning measurements, can be communicated between the network and the UE via the User Plane (UP) and Control Plane (CP). Figure 3 shows an exemplary configuration of the NR UP and CP protocol layers between the UE (310), gNB (320), and AMF (330), as shown in Figures 1 and 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 both the UP and CP. The PDCP layer provides encryption / decryption, integrity protection, sequence numbering, sorting, and duplicate detection for both CP and UP. Furthermore, 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), and the PDCP creates Protocol Data Units (PDUs) for distribution to the RLC. The Service Data Adaptive Protocol (SDAP) layer handles QoS, including mapping QoS flows to 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 sorting of data forwarded to and from higher layers. The MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing to or 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, handling transmissions on the NR radio interface, for example, through modulation, coding, antenna mapping, and beamforming.

[0055] On the CP side, the Non-Accessible Layer (NAS) layer lies between the UE and AMF, handling UE / gNB authentication, mobility management, and security control. The RRC layer is below the NAS in the UE, but terminates in the gNB rather than the AMF. The RRC controls communication between the UE and gNB on the radio interface, as well as the mobility of UEs 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) for use by the UE. Furthermore, 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, it will be in the RRC_IDLE state until an RRC connection with the network is established, at which point the UE will transition to the RRC_CONNECTED state (where, for example, data transfer may occur). The UE will return to RRC_IDLE after the connection with the network is released. In the RRC_IDLE state, the UE's radio is active on the intermittent receive (DRX) schedule set by the higher layer. During the DRX active period (also called the "DRX-on duration"), the RRC_IDLE UE receives SI broadcasts in the cell the UE is camping, performs neighbor cell measurements 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 unknown to the gNB serving the cell the UE is camping. However, NR RRC includes the RRC_INACTIVE state, where the UE is known by the serving gNB (for example, via the UE context). RRC_INACTIVE has several properties, such as 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 measurement and other location information, assisting the LCS target in measurements when needed, 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., the entity being positioned), such as a UE. The LCS client may also reside within the LCS target itself. The LCS client sends a request to the LCS server to obtain location information, and the LCS server processes and serves the received request, sending the positioning results and optionally a speed estimate to the LCS client. Positioning requests can originate from a terminal, network node, or external client. For example, position calculations can be performed by an LCS server (e.g., E-SMLC or SLP) or by an LCS target (e.g., UE).

[0058] Furthermore, the following positioning methods are supported in NR. • Extended Cell ID (E-CID). This utilizes information to associate a UE with the geographical area of ​​a serving cell, and additional information to determine a more granular location. The following measurements are supported for E-CID: AoA (base stations only), UE Rx-Tx time difference, Timing Advance (TA) types 1 and 2, Reference Signal Received Power (RSRP), and Reference Signal Received Quality (RSRQ). • Supported GNSS. GNSS information extracted by the UE, supported by support information provided from E-SMLC to the UE. • OTDOA (Observation Time of Arrival Difference). The UE receives and measures Global Navigation Satellite System (GNSS) signals, supported by information provided to the UE from E-SMLC. • UTDOA (Uplink TOA): The UE is required to transmit specific waveforms detected by multiple Location Measurement Units (LMUs) (which may be standalone, collated, or integrated into the eNB) at known locations. These measurements are forwarded to the E-SMLC for multilatency. • Multi-RTT: A device (e.g., UE) calculates the UE Rx-Tx time difference, and a gNB calculates the gNB Rx-Tx time difference. The results are combined to find the UE location based on the round-trip time (RTT) calculation. • DL Departure Angle (DL-AoD): gNB or LMF calculates the UE angular position based on the UE DL RSRP measurement results (e.g., PRS transmitted by the RAN node). • UL Angle of Arrival (UL-AoA): gNB calculates the UL AoA based on measurements of the UE's UL SRS transmission.

[0059] Furthermore, in each of the positioning methods listed above, one or more of the following positioning modes may be used. • UE support: The UE performs measurements with or without network support and sends these measurements to the E-SMLC, where position calculations can be performed. • UE-based: The UE, with assistance from the network, performs measurements and calculates its own location. • Standalone: ​​The UE performs measurements and calculates its own location without network assistance.

[0060] Detailed support data may include information such as network node location and beam direction. This support data may be provided to the UE via unicast or broadcast.

[0061] Figure 4 is a block diagram showing a high-level architecture for supporting UE positioning in an NR network. The NG-RAN420 can include nodes such as the gNB422 and ng-eNB421, similar to the architecture shown in Figure 2. Each ng-eNB may control several transmit points (TPs), such as remote radio heads. Similarly, each gNB may control several transmit / receive points (TRPs). Some or all of the TPs / TRPs may be DL-PRS dedicated to supporting PRS-based TBS.

[0062] Furthermore, NG-RAN nodes communicate with AMF430 in 5GC via their respective NG-C interfaces (both may or may not be present), and AMF430 communicates with Location Management Function (LMF) 440 via NLs interface 441. The LMF supports various functions related to UE location determination, including location determination for UEs and obtaining DL location measurements or location estimations from UEs, UL location measurements from NG RAN, and non-UE related support data from NG RAN.

[0063] Furthermore, positioning relationship communication between the UE410 and the NG-RAN node is conducted via the RRC protocol, and positioning relationship communication between the NG-RAN node and the LMF is conducted via the NRPPa protocol. Optionally, the LMF can also communicate with the Extended Serving Mobile Location Center (E-SMLC) 450 and the Secure UP Location (SUPL) Location Platform (SLP) 460 via communication interfaces 451 and 461, respectively. 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 LMF440 may also include, or be associated with, various processing circuits 442, thereby enabling the LMF to perform the various operations described herein. The processing circuits 442 may include processing circuits of a similar type to those described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20). The LMF440 may also include, or be associated with, a non-temporary computer-readable medium 443 for storing instructions (also known as computer program products), which can facilitate the operation of the processing circuits 442. The medium 443 may include computer memory of a similar type to those described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20). Furthermore, the LMF440 may include various communication interface circuits 441 (e.g., Ethernet, optical, and / or wireless transceivers) that can be used for communication via NLs interfaces, for example. For example, the communication interface circuit 441 may be similar to other communication interface circuits described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20).

[0065] Similarly, the E-SMLC450 may also include, or be associated with, various processing circuits 452, thereby enabling the E-SMLC to perform the various operations described herein. The processing circuits 452 may include processing circuits of a similar type to those described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20). The E-SMLC450 may also include, or be associated with, a non-temporary computer-readable medium 453 for storing instructions (also called computer program products) that can facilitate the operation of the processing circuits 452. The medium 453 may include computer memory of a similar type to those described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20). The E-SMLC450 may also have a communication interface circuit suitable for communicating via interface 451, which may be similar to other communication interface circuits described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20).

[0066] Similarly, the SLP460 may also include, or be associated with, various processing circuits 462, thereby enabling the SLP to perform the various operations described herein. The processing circuits 662 may include processing circuits of a similar type to those described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20). The SLP460 may also include, or be associated with, a non-temporary computer-readable medium 463 for storing instructions (also known as computer program products), which can facilitate the operation of the processing circuits 462. The medium 463 may include computer memory of a similar type to those described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20). The SLP460 may also have a communication interface circuit suitable for communicating via interface 461, which may be similar to other communication interface circuits described herein with respect to other network nodes (see, for example, the descriptions of Figures 18 and 20).

[0067] In typical operation, the AMF may receive a request from another entity (e.g., a Gateway Mobile Location Center (GMLC)) for location services related to a particular target UE, or the AMF itself may initiate some location services on behalf of a particular target UE (e.g., in the case of an emergency call from a UE). The AMF then sends a Location Service (LS) request to the LMF. The LMF processes the LS request, which may include forwarding support data to the target UE (i.e., to support UE-based and / or UE-assisted positioning), and / or determining the location of the target UE. The LMF then returns to the AMF, or to the other entity that requested the LS (e.g., a GMLC), the results of these operations (e.g., a location estimate for the UE and / or instructions for any support data to be forwarded to the UE).

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

[0069] Furthermore, the NR positioning protocol A (NRPPa) carries information between NG-RAN nodes and LMFs and is transparent to the AMF. Therefore, the AMF transparently routes NRPPa PDUs over the NG-C interface (e.g., without knowledge of the NRPPa transactions involved) based on the routing ID corresponding to the LMF involved. More specifically, the AMF carries NRPPa PDUs over the NG-C interface in either UE-related or non-UE-related mode. The NGAP protocol between the AMF and NG-RAN nodes (e.g., gNB or ng-eNB) is used as the transport for LPP and NRPPa messages over the NG-C interface. NGAP is also used to trigger and terminate positioning procedures in NG-RAN relationships.

[0070] LPP / NRPP is used to deliver messages from a positioning node (e.g., a location server) to a UE, such as positioning capability requests, OTDOA positioning measurement requests, and OTDOA support data. LPP / NRPP is also used to deliver messages from a UE to a positioning node, such as UE capability, UE measurements for UE-supported OTDOA positioning, UE requests for additional support data, and (one or more) UE configuration parameters that should be used to create UE-specific OTDOA support data. NRPPa is used to deliver information bidirectionally between ng-eNB / gNB and LMF. This may include the LMF requesting some information from ng-eNB / gNB and ng-eNB / gNB providing some information to the LMF. For example, this may include information about PRS sent by 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 positioning system information blocks (posSIB), as specified in 3GPP TS38.331 (v16.2.0). posSIB is carried in RRC system information (SI) messages. Supported posSibTypes are shown in Table 1 below (also Table 7.2-1 of 3GPP TS38.331). GNSS common and general assistance data information elements (IEs) are defined in 3GPP TS37.355 (v16.2.0) section 6.5.2.2. OTDOA assistance data IEs and NR DL-TDOA / DL-AoD assistance data IEs are defined in 3GPP TS37.355 section 7.4.2. Barometric pressure assistance data IEs are defined in 3GPP TS37.355 section 6.5.5.8. TBS-supported data IE (based on MBS signals) is specified in 3GPP TS37.355 Section 6.5.4.8. TIFF0007918215000001.tif221170

[0072] PRS was introduced in LTE Rel-9 because the Cell-Specific Reference Signal (CRS) was insufficient for positioning. Specifically, the CRS could not guarantee the necessary probability of detection for at least three different cells required to determine location. Generally, neighbor cell synchronization signals (PSS / SSS) and reference signals are detectable if the signal-to-interference noise ratio (SINR) is ≥ -6 dB. However, simulations showed that this SINR is available for the third-best detected cell in ≤ 70% of all cases, and therefore only two neighbor cells are detected in ≥ 30% of cases. Even this level of performance, based on an interference-free environment, is unrealistic in real-world scenarios.

[0073] Even so, PRS has some similarities to CRS. For example, PRS is a pseudo-random QPSK sequence mapped with a diagonal pattern with frequency and time shifts to avoid collisions with CRS and overlap with the control channel (PDCCH).

[0074] Figure 5 shows a signal flow diagram for an exemplary multi-RTT positioning procedure between the UE, 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 gNB / TRPs also measure the UL-SRS transmitted by the UE (operation 9b).

[0075] Figure 6 shows an exemplary division of positioning relationship functions in the split gNB architecture shown in Figure 1. The gNB-DU hosts the TRP function shown in Figure 4, which can be divided into a transmit point (TP) and a receive point (RP). Location management messages can be transferred between the gNB-CU and the gNB-DU via the F1-C interface. For example, the gNB-CU can request TRP information and / or positioning measurements from the gNB-DU, and the gNB-DU can respond with the requested information (if available).

[0076] Recent advances in large-scale antenna systems (large-scale MIMO) can provide additional degrees of freedom to enable more accurate user location estimation by leveraging the spatial and angular domains of propagation channels in combination with time measurements. These spatial techniques, also known as "beamforming," can be used by the network or by the UE on the transmit beam and / or receive beam.

[0077] Currently, two NR frequency ranges, namely FR1 (below 6 GHz) and FR2 (above 6 GHz), are explicitly distinguished in 3GPP. High-frequency radio communications above 6 GHz are known to suffer from significant path loss and transmission loss. One solution to address this problem is to deploy large antenna arrays to achieve high beamforming gain, which is a reasonable solution given the small wavelengths of high-frequency signals. Such solutions are often referred to as multiple-input multiple-output (MIMO), or, in the case of large antenna arrays, large-scale MIMO is expected for NR. In particular, up to 64 beams are supported in FR2. Furthermore, it is expected that even more antenna elements will be used in FR1 to obtain greater beamforming and multiplexing gains.

[0078] In large-scale MIMO, three beamforming techniques were discussed: analog, digital, and hybrid (a combination of analog and digital). Analog beamforming can compensate for high path loss in NR scenarios, and digital precoding can provide additional performance gains necessary to achieve reasonable coverage (similar to MIMO for FR1, for example). The implementation complexity of analog beamforming is significantly lower than digital because it can utilize simple phase shifters, but analog beamforming is limited in terms of multidirectional flexibility (i.e., a single beam can be formed at once, and then the beam is switched in the time domain), limited in terms of transmit bandwidth (i.e., it is not possible to transmit over subbands), and 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 capability. 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 gain of digital beamforming increases more slowly.

[0080] Therefore, hybrid beamforming, which offers cost benefits from analog beamforming and capacity benefits from digital beamforming, is desirable for NR. Figure 7 shows an exemplary hybrid transmit (TX) beamforming configuration, which includes a digital precoding section and an analog beamforming (BF) section coupled by an intermediate converter circuit. As shown in Figure 7, the analog BF section includes independent analog circuits 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 distinct from the other subarrays. The converter circuit includes independent IFFT modulators, parallel-to-series converters (P / S), and digital-to-analog converters (DACs) for each of the N channels of the analog BF circuit.

[0081] The analog beams of a subarray can be steered in a single direction on each OFDM symbol; therefore, the number of subarrays determines the beam direction and the corresponding number of coverages on each OFDM symbol. However, the number of beams required to cover the entire area to be served is generally greater 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 area to be served. Providing multiple narrow coverage beams for this purpose is sometimes called "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 can be crucial for providing the necessary coverage in an NR network. For this purpose, multiple OFDM symbols, each with a differently steered beam, may be assigned and transmitted periodically through a subarray. Base stations typically perform transmit beam sweeping for DL ​​transmission and may implement receive beam sweeping for UL reception. UEs typically perform receive beam sweeping for DL ​​reception but may also implement transmit beam sweeping for UL transmission.

[0083] UEs and gNBs also perform beam measurements to evaluate the quality of received signals on DL and UL beams, respectively. For example, a UE measures quality on an SSB beam based on parameters such as SS-SINR (signal-to-interference noise ratio), SS-RSRP (reference signal received power), and SS-RSRQ (reference signal received quality). A gNB performs similar measurements on an UL beam (e.g., SRS) from a UE, although gNB measurements are not specified by 3GPP and are left to vendor implementation.

[0084] The UE and gNB also perform beam determination to determine the best or most suitable DL beam and UL beam, respectively, based on beam measurements. The UE also reports the beam quality measurements and beam determination results to the gNB. Furthermore, when a UE in the RRC_CONNECTED state experiences inadequate channel conditions, the UE can receive beam fault indications from its lower layers (e.g., PHY) and request beam fault recovery by sending a message to the UE's serving gNB.

[0085] The term "spatial relationship" refers to the relationship between a UL RS and another RS, which may be either a DL RS or another UL RS. This is also defined from the UE's 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 (contradictory) direction in which the UE received the corresponding DL RS. More precisely, the UE should apply the "same" Tx spatial filtering (or beamforming) settings to transmit the spatially related UL RS as the Rx spatial filtering (or beamforming) settings used to receive the corresponding DL RS.

[0086] Spatial relationships can also be used in the case of 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 spatial relationships to DL PRS resources such that they are signaled through a combination of DL PRS resource set ID and DL PRS resource ID. UE then transmits the UL SRS using the same antenna panel that UE uses to receive the corresponding DL PRS resource, and using the same (opposing) beam that UE uses to receive the DL PRS resource.

[0087] The 3GPP Rel-17 NR positioning extension includes 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 may involve configuring the PRS as needed, based on the premise that no PRS has been transmitted. When an LCS client (e.g., GMLC, UE) requests positioning, the LMF needs to determine a suitable PRS configuration from the outset. The second scenario is when a PRS has already been transmitted and either the UE may request a modification of the current configuration, or the LMF may need to modify the current configuration.

[0088] The first scenario is similar to one that occurs in a real-world LTE PRS deployment, where the PRS is being transmitted, but the LMF is uncertain about the nearest TRP to the UE or cell that should be included in the supporting data. In this case, E-CID is used as a mandatory procedure to provide the LMF with the necessary information. For 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, which can facilitate the initiation of on-demand PRS transmissions.

[0089] Figure 9 shows an exemplary signaling procedure used to obtain the PRS settings in this scenario. Some actions are given numerical labels, but these are intended to facilitate the following explanation and do not imply or require any particular sequence of actions unless explicitly stated otherwise.

[0090] In Operation 1, the AMF forwards the LCS service request to the LMF. The LCS service request is received by the AMF from an LCS client located 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 report) as part of the MO-LR request message. The LCS client in the UE may also provide other details about the DL-PRS transmission, such as the number of TRPs, beam direction, start time, and duration, which may also be forwarded from the AMF to the LMF. In Operation 1a, alternatively, the LMF may receive measurement reports (e.g., CSI-RS and SSB RSRP) from the gNB in ​​accordance with the UL NR E-CID procedure specified in 3GPP TS38.455. In Operation 2, if the LCS client is the GMLC or if the measurement is not available in Operation 1, the LMF may request the measurement from the UE. In operation 3, the UE provides the LMF with the measurements requested in operation 2.

[0091] In operations 4-5, the LMF determines the required DL-PRS transmission resources and requests DL-PRS transmissions from different gNBs (e.g., TRPs), which may include one or more serving gNBs of the UE and other non-serving gNBs. In operation 6, the gNBs may provide the LMF with an acknowledgment to initiate PRS transmissions or indicate a failure if they are unable to initiate PRS transmissions. If an acknowledgment / success is received 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 wishes to position the UE, several DL-PRS signals have already been transmitted by the RAN. For example, there may be multiple predefined PRS settings, and the UE may request one of these predefined settings. Furthermore, the LMF may also change between different predefined PRS settings. Figure 10 shows an exemplary signaling procedure used to obtain the PRS settings according to this scenario. Some operations are given numerical labels, but these are intended to facilitate the following explanation and not to imply or require any particular sequence of operations.

[0093] In operation 1, the LMF provides the PRS settings to the UE via LPP. Alternatively or additionally, in operation 1a, the PRS settings may be provided to the UE via RRC broadcast. In operation 2, the UE performs positioning measurements based on the (one or more) PRS settings received in operation 1 / 1a. If the UE is operating in UE-based positioning mode and certain conditions such as positioning QoS are not met, or based on measurement quality, reliability level, etc., the UE may decide to request on-demand PRS.

[0094] In operation 3, the UE sends an on-demand PRS request with a preferred PRS setting (e.g., setting index), or a request to increase / decrease DL-PRS resources. In operation 4, the LMF decides whether it is necessary to change the PRS setting when requested. The LMF may make this decision based on inputs received from multiple UEs. In operation 5, based on the decision in operation 4, the LMF requests the serving gNB and non-serving gNB (e.g., TRP) for the UE to change the current PRS setting (via NRPPa). In operation 6, the gNB provides a PRS send update or acknowledgment in the 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 gNB, which then provides the same to the UE via RRC broadcast.

[0096] Currently, there are several issues, problems, and / or difficulties regarding the on-demand PRS configuration described above. For example, when a UE is provided with multiple predefined PRS configurations, it is unclear how the LMF should respond to a request from the UE for a specific configuration (e.g., based on a configuration index). More specifically, since predefined PRS configurations are used by all UEs, should the LMF change the currently used PRS configuration based on a request from one UE? Even if the requested configuration is preferred by the UE, when and how is the LMF compelled to act on requests? Can the network wait until several UEs request the same PRS configuration for the change?

[0097] Current predefined PRS settings are generally related to quality of service (QoS). For example, one setting (index 1) might represent high QoS with high bandwidth and short periodicity of PRS, while a second setting (index 2) might represent intermediate QoS with intermediate bandwidth and intermediate periodicity of PRS. However, defining PRS settings based solely on QoS may be insufficient to cover all use cases and / or scenarios.

[0098] Furthermore, it is unclear what restrictions (if any) should be imposed on the UE's selection of PRS settings for requesting. For example, it may be necessary to ensure that a UE does not always request the most resource-intensive settings, even if they provide the best positioning performance for the UE. In other words, rules may be needed to align UE requests with actual UE needs.

[0099] Furthermore, predefined PRS settings require collaboration between the LMF and the gNB that actually sends the DL-PRS, both in creating such predefined settings and in using them. For example, if a gNB is currently using settings associated with a first index, can the LMF request changes to any other predefined settings, or only a subset of other predefined settings (e.g., one more resource-intensive than the other)?

[0100] Accordingly, embodiments of the present disclosure provide a flexible and efficient technique for defining a set of PRS settings for on-demand PRS requests, UE selection among predefined PRS settings for such requests, LMF selection among predefined PRS settings for setting gNB / TRP, and so on.

[0101] The embodiment can provide a network-friendly method for supporting on-demand PRS transmission when network conditions change. The embodiment 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 transmission. The embodiment can reduce energy consumption of RAN nodes by avoiding the transmission of unnecessary PRS resources.

[0102] For example, instead of positioning QoS, LMF can define PRS settings individually or in any combination based on any of the following: • posSIB broadcast size limit. For example, the number of frequency layers, TRPs, DL-PRS resource sets, DL-PRS resources, etc., that can be contained within a single posSIB without segmentation or with a maximum upper limit / limit on segmentation, where the upper limit X is a predetermined number (e.g., X=3, X=5, etc.). • Default settings indicated by existing posSIBs, and delta settings provided in new posSIBs. Delta settings indicate what attributes (e.g., PRS settings) may differ for TRPs included in the default settings. Thus, the configuration index points out the different parameter settings possible for TRP content in the default settings. The number of TRPs and associated resources for those TRPs (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 these can still be detected at an acceptable level of SNR, SINR, RSSI, etc. • Different sets or groups of TRPs, for example, Group 1 having one LOS, GDOP, or DL-PRS periodicity characteristic, and Group 2 having another LOS, GDOP, or DL-PRS periodicity characteristic, and so on. • Energy reduction and / or latency reduction. • Positioning and orientation, for example, horizontal, vertical, or another specific spatial dimension.

[0103] As another example, the UE may select a preferred setting to specify in the on-demand PRS request based on one of the following: • UE mapping of estimated or required error levels to preferred configuration indices. • The network-configured order of the configured indexes. In other words, the network sorts the indexes in some order and requires the UE to select the index in that order. As a more specific example, if a PRS configuration corresponding to index 3 is provided, the UE can select either index 2 or index 4 for an on-demand PRS request, but cannot select any other index (e.g., index 1 or index 5+).

[0104] Similar techniques may be used between LMF and gNB to constrain the LMF or gNB selection for a pre-configured PRS setting, which may include any of the following: LMF mapping of estimated or required error levels to one or more preferred setting indices, LMF can then request gNB to use this mapping. For example, LMF can request gNB to consider indices 2, 4, and 5 in a preferred order in the list of indices. The order of preference for configuration indices, as 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 can select either index 2 or index 4 for an on-demand request to the gNB, but cannot select any other index (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 all UE positioning errors satisfy certain requirements, the LMF can change to index 2, which has a longer periodicity.

[0105] In some embodiments, the LMF can determine a predefined PRS configuration based on a reinforcement learning scheme. This can be useful when on-demand PRS transmission has not yet begun. For example, the predefined PRS configuration may be based on the X number of UEs initially present in the cell, the Y number of deployed TRPs, the Z number of default radio states, etc.

[0106] These initial PRS settings can then be expanded after PRS transmission has been initiated. For example, the LMF can use learning techniques to expand a pattern that progressively follows multiple positioning sessions to create different settings that will suit different scenarios. This can be seen as a form of "crowdsourcing." When a new on-demand PRS request is received, the LMF does not have to select a setting instructed by a specific UE, but can leverage this crowdsourced PRS information to determine which on-demand setting works best for (one or more) UEs and which modifications the gNB / TRP should use.

[0107] As shown in Table 1 above, the NR DL-TDOA / DL-AoD support data includes three SIBs: posSibType6-1, posSibType6-2, and posSibType6-3.

[0108] In some embodiments, posSIBType6-1(NR-DL-PRS-AssistanceData) can specify a default PRS setting that includes a set of PRS settings for a list of TRPs. In such embodiments, the default PRS setting can be fixed.

[0109] In other embodiments, posSIBType6-1(NR-DL-PRS-AssistanceData) can indicate an active PRS setting which includes a set of PRS settings for a list of TRPs. In such embodiments, the active PRS setting can be changed dynamically.

[0110] In other embodiments, a new posSIB type may be defined to include different configuration indices and their difference (or delta) configurations for the default DLPRS configuration or active DLPRS configuration indicated by posSIBType6-1 (e.g., posSibType6-4). An example of posSibType6-4 content may include: • Configuration index 1: Compared to the default or active settings provided in posSibType6-1, this provides a larger bandwidth (BW) but the same periodicity. • Setting index 2: Shorter periodicity, but the same BW, compared to the default or active setting provided in posSibType6-1. • Setting index 3: Compared to the default or active setting provided in posSibType6-1, shorter periodicity and larger BW.

[0111] Although only BW and periodicity were mentioned in the example above, the settings are not limited to these parameters and may include other parameters such as positioning frequency layer (PFL) and TRP information.

[0112] In some embodiments, the LMF may provide various rules that restrict the UE's selection of configuration indices to be included in an on-demand PRS request. For example, either index 1 or index 2 may be requested initially, but index 3 may only be requested after the UE has been provided with PRS settings related to index 1 or index 2. Furthermore, the UE may be restricted to requesting index 3 only when the settings based on index 1 or index 2 do not achieve the UE's positioning QoS or measurement quality, or when the UE's positioning reliability level falls below a certain threshold. These rules may be expressed as the following configuration settings. • firstRequestRestrictedTo-INTEGER(1...n), where n=2 in the example above, and therefore the UE may not initiate a request for setting 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 regarding subsequent requests from the UE.

[0114] In some embodiments, multiple DL PRS reference signals may be transmitted coherently so that the UE can process the multiple DL PRS reference signals coherently / together to improve positioning accuracy. In such embodiments, the multiple DL PRS reference signals may be configured as follows: • Setting index 1: Larger bandwidth (BW1), but with the same periodicity as the default / active setting provided in posSibType6-1. The PRS corresponding to setting index 1 is transmitted in positioning frequency layer (PFL) 1. • Configuration index 2: Higher bandwidth (BW2), but with the 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 requires improved positioning accuracy, the UE may include multiple (e.g., two) setting indices during an on-demand PRS request to the LMF. This can instruct the UE to request PRS reference signals corresponding to multiple indices to be transmitted coherently. To facilitate coherent transmission / reception, several parameters, such as periodicity and TRP index, should be the same for multiple requested PRS settings.

[0116] In some embodiments, PRS settings may be grouped based on TRP capabilities for on-demand PRS. For example, all TRPs with the same or similar capabilities are part of a single group associated with one or more setting indices.

[0117] In some embodiments, PRS settings may be distinguished and / or grouped based on GDOP (or other geometric classifications), detectability by UE, line-of-sight (LOS) vs. non-LOS transmissions, etc. This may be based on previous UE measurement reports or other received information.

[0118] In some embodiments, the settings associated with each index may be distinguished and / or grouped based on energy consumption (for example, for TRP and / or UE). The following example includes indices corresponding to three different levels of energy consumption. • Configuration index 1: P PFLs, T TRPs in each PFL, Y PRS resource sets in each TRP, and Z resources per resource set. In some cases, P, T, X, and / or Z can be functions with a maximum posSIB size of approximately 3000 bits. Therefore, 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 any PFL, Y / 2 PRS resource sets per TRP, Z / 2 resources per resource set. • Configuration index 3: P / 3 PFLs, T / 3 TRPs in any 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 a minimum energy setting index 3 when there are a small number of UEs that need to be positioned. If the number of UEs increases or the acquired positioning QoS is not satisfactory, the LMF may switch the setting to, for example, setting index 2, which requires more energy.

[0120] As described above, in some embodiments, the UE may also be constrained in its selection between these setting indices. For example, if the UE is provided with a setting associated with index 3 (lowest energy), the UE may only be allowed to request setting index 2. After being provided with a setting associated with index 2, if the UE cannot meet certain requirements and / or conditions with this setting, the UE may be allowed to request setting index 1 (highest energy).

[0121] In some embodiments, the LMF may set conditions and / or requirements for the UE to adjust its demands. For example, the LMF may provide positioning error or accuracy thresholds (e.g., 50m), positioning latency thresholds (e.g., 10s), etc. Such thresholds may be provided / used individually or in various combinations. Based on these rules and thresholds, the network can balance the UE positioning requirements, including network energy consumption, interference, etc., associated with increased PRS transmissions.

[0122] In some embodiments, the LMF (optionally, in conjunction with a gNB) may associate a distinguishing attribute or characteristic with a predefined PRS configuration. In other words, the LMF can specify the attribute or characteristic used to distinguish a predefined PRS configuration. Exemplary distinguishing characteristics include QoS-latency, QoS-accuracy, path loss (or radio state), PRS-overhead (or energy saving), etc. The LMF can specify this distinguishing characteristic to the UE, which can then base its configuration index selection for on-demand PRS requests on the distinguishing characteristic.

[0123] Figure 11 shows an ASN.1 data structure for an exemplary OnDemand-PRS-ClassificationCriteria field with different enumeration values ​​for the distinction criterion according to these embodiments. In addition to the criterion described above, Figure 11 includes an enumeration value for “areaSpecific,” which indicates that the setting is valid in an area and that the UE may request a new setting when it moves outside that area.

[0124] In some embodiments, the distinction characteristic alternatives may relate to different UE selection rules and / or different selection thresholds. For example, when distinction characteristic A is used, the UE may be allowed to request set indices in any order, while when distinction characteristic B is used, the UE may be constrained to request indices in a fixed order (e.g., ascending or descending, as described above).

[0125] In some embodiments, the LMF may send an NRPPa message to the gNB requesting that it modify its current DL-PRS transmission setting to one of a different pre-configured PRS setting. In some embodiments, an existing support information control message may be used for this purpose. In other embodiments, a newly defined PRS modification request message may be used to modify an ongoing PRS transmission for a particular set of TRPs or for the entire network. Figure 12 shows the 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 exemplary content for the PRS modification request message and the PRS modification response message, respectively. For example, a message with this content may be added to 3GPP TS38.455 (v16.3.0). TIFF0007918215000002.tif134170TIFF0007918215000003.tif66170

[0126] In some embodiments, the LMF may have default PRS settings provided during initial deployment, for example, by an Operational Administration and Maintenance (OAM) function. These default settings may be used for initial signaling of on-demand PRS transmissions.

[0127] In some embodiments, the LMF can receive UE measurements (e.g., RRM beam measurements or PRS beam measurements) via the LPP and, based on such measurements, create a database containing multiple settings for on-demand PRS transmission. For example, the LMF can create some or all of the settings based on factors such as the number of UEs, RRM statistics, TRP capability, SSB pattern, estimated report, and positioning orientation (e.g., vertical / horizontal).

[0128] In some embodiments, LMFs can use machine learning (ML) to create such PRS settings in the LMF 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 environment and is provided with implicit (and sometimes delayed) feedback in the form of “reward signals.” RL implements short-term reward maximization but may also make decisions that are irrational in the short term while providing long-term gains. More generally, an RL model attempts to maximize expected future rewards by leveraging existing knowledge and exploring different scenarios, e.g., the space of actions in network and / or UE settings.

[0129] In some embodiments, when an 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 settings and sends that PRS setting to one or more gNBs via NRPPa signaling. Based on gNB feedback (e.g., an NRPPa success response message), the LMF updates its PRS setting database. In some embodiments, the LMF may also update its PRS setting database based on UE feedback, such as positioning measurements and / or location estimation.

[0130] In some embodiments, during an ongoing positioning session, if a DL-PRS has already been transmitted, the LMF may send an NRPPa message to the gNB to modify the current PRS transmission using one of the PRS settings from the LMF's database. This can be done, for example, using the exemplary procedure shown in Figure 12. Alternatively, an existing NRPPa message may be modified for the same purpose.

[0131] The various features of the embodiments described above correspond to the various operations shown in Figures 13–15, each illustrating exemplary methods (e.g., procedures) for UE, positioning nodes, and RAN nodes. In other words, the various features of the operations described below correspond to the various embodiments described above. Furthermore, the exemplary methods shown in Figures 13–15 can be used collaboratively to provide various benefits, advantages, and / or solutions to problems described herein. While Figures 13–15 show specific blocks in a particular order, the operations of the exemplary methods may be performed in a different order than shown, combined into blocks having different functions than shown, and / or divided. Optional blocks or operations are indicated by dashed lines.

[0132] In particular, Figure 13 shows an exemplary method (e.g., procedure) for a UE configured for positioning in a RAN, according to various embodiments of this disclosure. The exemplary method may be carried out by a UE (e.g., a wireless device) as described elsewhere in this specification.

[0133] An exemplary method may include the operation of block 1310, where the UE can receive from a positioning node associated with the RAN a plurality of settings for the PRS transmitted by the nodes of the RAN, and a plurality of corresponding setting indices associated with the plurality of settings. In other words, each setting is represented by a setting index, corresponds to a setting index, and / or is associated with a setting index, and vice versa. For example, the positioning node may be an LMF.

[0134] An exemplary method may also include the operation of block 1340, where the UE determines the need to receive a PRS and can select one or more of several settings based on one or more selection rules. An exemplary method may also include the operation of block 1350, where the UE can send one or more requests to the positioning node for TRS transmission via RAN. One or more requests include one or more setting indices related to one or more settings selected in block 1340.

[0135] In some embodiments, the exemplary method may also include the operation of block 1330, where the UE can receive selection rules from the positioning node.

[0136] In various embodiments, multiple settings may have the following characteristics or parameters, namely: ·PRS transmission periodicity, • PRS transmission bandwidth, • Number of PRS transmit frequency layers used, • Specific PRS transmit frequency layers used, • Number of RAN nodes that send PRS, • A specific RAN node that sends PRS, • Geographic configuration of RAN nodes that transmit PRS, • Number of PRS resource sets per node, • Number of PRS per PRS resource set, • Energy consumption and / or signaling overhead associated with transmitting PRS according to the settings. • Relevant geographical area, • Positioning spatial dimension, • Positioning accuracy, Quality of Service (QoS), and Positioning Latency QoS They can be distinguished from one or more of the following:

[0137] In some embodiments, the exemplary method may also include the operation of block 1320, where the UE can receive instructions from the positioning node for characteristics or parameters, with multiple settings distinguished. In such embodiments, the selection of one or more of the multiple settings (for example, in block 1340) may be based on the indicated characteristics or parameters. Exemplary instructions according to these embodiments are shown in Figure 11. In some embodiments, the exemplary method may also include the operation of block 1320, where the UE can receive selection rules (for example, used in block 1340) from the positioning node.

[0138] In some embodiments, the configuration includes a first configuration containing default values ​​for configuration parameters and one or more further configurations. Each further configuration includes only the configuration parameters among 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 one or more further configurations may be received via a broadcasted second SIB. Exemplary SIBs are described above. In some of these embodiments, the first SIB indicates that the first configuration is either a default configuration or one of the active configurations.

[0139] In some embodiments, each request includes one index related to one setting selected by the UE. In some of these embodiments, the selection rule includes a sequential order in which each setting may be requested by the UE.

[0140] In other embodiments of these, 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 requests. In some variants, the first subset of settings includes a first setting that requires the minimum energy to transmit a PRS, and the second subset includes at least one setting that requires more energy to transmit a PRS than the first setting.

[0141] In some examples of these variations, the action selected in block 1340 may include the actions of subblocks 1341-1343, where the UE determines whether positioning based on PRS transmissions following a first setting will satisfy the positioning QoS threshold; if it is determined that the positioning QoS threshold will be satisfied, the UE may select the first setting; and if it is determined that the positioning QoS threshold will not be satisfied, the UE may select a second subset of settings. In some cases, the positioning QoS threshold relates 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. Furthermore, one or more subsequent requests include a first subsequent request and a second subsequent request following 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, one or more requests include a single request containing at least two configuration indices. The selection rule includes a third rule indicating one of more configuration parameters that must be common among at least two configurations associated with at least two configuration indices included in the single request. In some variants, the third rule indicates that at least the following parameters, namely the PRS transmission periodicity and the specific RAN node from which the PRS is transmitted, must be common among at least two configurations. In some of these embodiments, the exemplary method may also include the operation of block 1360, where the UE can perform positioning measurements on PRS transmitted coherently according to at least two configurations associated with at least two configuration indices included in the single request.

[0144] Furthermore, Figure 14 shows exemplary methods (e.g., procedures) for a RAN-related positioning node according to various embodiments of this disclosure. These exemplary methods may be carried out by positioning nodes (e.g., LMF, E-SMLC, SUPL, etc.) as described elsewhere in this specification.

[0145] An exemplary method may include the operation of block 1410, where a positioning node can determine multiple settings for a PRS transmitted by a RAN node. The multiple settings are associated with each of several setting indices. An exemplary method may also include the operation of block 1420, where a positioning node can send multiple settings and associated setting indices to a node in the RAN and to a UE operating in the RAN. An exemplary method may also include the operation of block 1450, where a positioning node can receive one or more requests from a UE for a PRS transmission by the RAN. One or more requests include one or more setting indices associated with one or more of the multiple settings selected by the UE.

[0146] In various embodiments, multiple settings may be distinguished from one another based on either the characteristics or parameters described above with respect to the UE embodiment. In some embodiments, exemplary methods may also include the operation of block 1430, where the positioning node can send instructions to the UE for the characteristics or parameters that distinguish the multiple settings. Exemplary instructions according to these embodiments are shown in Figure 11.

[0147] In some embodiments, a set of settings may include a first setting that includes default values ​​for setting parameters and one or more further settings. Each further setting includes only the setting parameters among the setting parameters that have values ​​different from the default values. In some of these embodiments, the first setting may be sent by the RAN via a broadcast of a first SIB, and one or more further settings may be sent by the RAN via a broadcast of a second SIB. Exemplary SIBs are described above. In some of these embodiments, the first SIB indicates that the first setting is either a default setting or one of the active settings.

[0148] In some embodiments, the exemplary method may also include the operation of block 1460, where the positioning node can configure the RAN node to transmit PRS according to one or more settings indicated by the UE, or one or more further settings selected by the positioning node.

[0149] In some of these embodiments, the exemplary method may also include the operation of block 1440, where the positioning node can send a selection rule to the UE for selecting among several settings.

[0150] In some of these embodiments, each request includes one index associated with one selected setting. In some variants, the selection rule (for example, sent in block 1440) may include a sequential order in which each setting may be requested by the UE.

[0151] In other embodiments of these, one or more requests (for example, received in 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 requests.

[0152] In some variations of these embodiments, a first subset includes a first setting that requires the minimum energy to transmit a PRS, and a second subset includes at least one setting that requires more energy to transmit a PRS than the first setting. In some examples of these variations, the selection rule may include a positioning QoS threshold for selecting between the first setting and the settings of the second subset. In some cases, the positioning QoS threshold relates 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. Furthermore, one or more subsequent requests include a first subsequent request and a second subsequent request following 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 other embodiments of these, one or more requests (for example, received in block 1450) include a single request containing at least two configuration indices. The selection rule includes a third rule indicating one of more configuration parameters that must be common among at least two configurations identified by the at least two configuration indices included in the single request. In some variants, the third rule indicates that at least the following parameters, namely PRS transmission periodicity and the specific RAN node transmitting the PRS, must be common among at least two configurations. In some embodiments of these, the configuration operation in block 1460 may include the operation in subblock 1461, where positioning nodes can be configured to coherently transmit PRS according to at least two configurations associated with the at least two configuration indices included in the single request.

[0155] In some embodiments, determining multiple settings in block 1410 may include the operation of subblocks 1411-1412, where the positioning node obtains default settings for PRS transmission (e.g., from OAM during system initialization) and multiple settings (e.g., sent in block 1420), • Measurements performed by the UE on PRS sent according to default settings. • The ability of the node to send PRS • The number of UEs operating in RAN, and • One or more distinguishing characteristics or parameters (for example, as described above) Based on this, decisions can be made and actions can be taken.

[0156] In some embodiments, determining multiple settings in block 1410 may include the operation of subblock 1413, where the positioning node determines multiple settings • Measurements performed by the UE on PRS transmitted according to multiple settings. · Node's updated capabilities, • The number of updated UEs operating in RAN, and • One or more distinguishing characteristics or parameters It can be adapted based on one or more of the following.

[0157] For example, a positioning node can use ML (e.g., RL) techniques to adapt multiple settings, as described above.

[0158] Furthermore, Figure 15 shows exemplary methods (e.g., procedures) for a RAN node according to various embodiments of the present disclosure. These exemplary methods may be implemented by a RAN node (e.g., a base station, eNB, gNB, ng-eNB, TRP, etc.) as described elsewhere in this specification.

[0159] An exemplary method may include the operation of block 1510, where a RAN node can receive from a positioning node associated with the RAN multiple settings for PRS transmitted by the nodes of the RAN, and multiple corresponding setting indices associated with the multiple settings. In other words, each setting is represented by a setting index, corresponds to a setting index, and / or is associated with a setting index, and vice versa. For example, a positioning node may be an LMF.

[0160] An exemplary method may also include the operation of block 1530, where a RAN node can then receive one or more requests from a positioning node for PRS transmission. One or more requests include one or more of a plurality of configuration indices (for example, received in block 1510). An exemplary method may also include the operation of block 1540, where a RAN node can transmit a PRS according to one or more of the configurations associated with one or more of the configuration indices included in one or more requests.

[0161] In various embodiments, multiple settings may be distinguished from one another based on either the characteristics or parameters described above with respect to the UE embodiment.

[0162] In some embodiments, the configuration may include a first configuration containing default values ​​for configuration parameters and one or more further configurations. Each further configuration may include only the 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 a RAN node can broadcast the first configuration in a first SIB and one or more further configurations in a second SIB. An exemplary SIB is described above. In some of these embodiments, the first SIB indicates that the first configuration is either a default configuration or one of the active configurations.

[0163] In some embodiments, 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 can be requested by the UE in the initial request and a second subset of settings that can 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 minimum energy to transmit a PRS, and the second subset includes at least one setting that requires more energy to transmit a 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, one or more requests include a single request that includes at least two configuration indices. At least the PRS transmission periodicity is common among at least two settings associated with at least two configuration indices included in the single request. In some of these embodiments, the transmission operation of block 1540 may include the operation of subblock 1541, where a RAN node can coherently transmit PRS according to at least two settings associated with at least two configuration indices included in the single request.

[0165] While various embodiments have been described above in relation to methods, techniques, and / or procedures, those skilled in the art will readily understand that such methods, techniques, and / or procedures can be embodied in various systems, communication devices, computing devices, control devices, apparatus, non-temporary computer-readable media, computer program products, and the like through various combinations of hardware and software.

[0166] Figure 16 shows an example of a communication system 1600 according to several embodiments. In this example, the communication system 1600 includes a communication network 1602, which includes an access network 1604 (e.g., RAN) and a core network 1606, which includes one or more core network nodes 1608. The access network 1604 includes one or more access network nodes (one or more of which may generally be 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. Network nodes 1610 facilitate direct or indirect connections of UEs, such as by connecting UEs 1612a, 1612b, 1612c, and 1612d (one or more of which may generally be referred to as UE1612) to the core network 1606 over one or more wireless connections.

[0167] Exemplary wireless communication over a wireless connection involves transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wires, cables, or other material conductors. Furthermore, 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 can 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] UE1612 may be any of a wide variety of communication devices, including a wireless device configured, set up, and / or operable to communicate wirelessly with network node 1610 and other communication devices. Similarly, network node 1610 is configured, capable, set up, and / or operable to communicate directly or indirectly with UE1612 and / or with other network nodes or devices in communication network 1602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in communication network 1602.

[0169] In the illustrated example, the core network 1606 connects network node 1610 to one or more hosts, such as host 1616. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1606 includes one or more core network nodes (e.g., core network node 1608) structured with hardware and software components. The characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, and therefore their descriptions are generally applicable to the corresponding components of core network node 1608. An exemplary core network node includes a node capable of hosting and / or implementing 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 Protected Proxy (SEPP), Network Exposure Function (NEF), Location Management Function (LMF), SUPL Location Platform (SUPL), Extended Serving Mobile Location Center (E-SMLC), and User Plane Function (UPF).

[0170] Host 1616 may be owned or under the control of a service provider other than the operator or provider of the access network 1604 and / or the communication network 1602, and may be operated by or on behalf of the service provider. Host 1616 may host a variety of applications to provide one or more services. Examples of such applications include data acquisition services such as extracting and compiling live and pre-recorded audio / video content, data on various ambient conditions detected by multiple UEs, analytical functions, social media, functions for controlling or possibly interacting with remote devices, functions for alarms and surveillance centers, or any other such functions performed by the server.

[0171] Overall, the communication system 1600 in Figure 16 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system may be configured to operate according to predefined rules or procedures, including, but not limited to, the Pan-European Digital Mobile Telephone System (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), wireless local area network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as global interoperability for microwave access (WiMAX), Bluetooth, Z-Wave, near-field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox, as well as any low-power wide area network (LPWAN) standards.

[0172] In some examples, the communication network 1602 is a cellular network implementing 3GPP standardized features. Therefore, 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-high reliability low latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or also provide massive machine-type communication (mMTC) / massive IoT services to further UEs.

[0173] In some examples, UE1612 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 1604 on a predetermined schedule when triggered by an internal or external event, or in response to a request from access network 1604. Furthermore, the UE may be configured to operate in single, multi-RAT, or multi-standard modes. For example, the UE may operate with one or a combination of Wi-Fi, NR, and LTE, such as in multi-radio dual connectivity (MR-DC) with a network.

[0174] In this example, hub 1614 communicates with access network 1604 to facilitate indirect communication between one or more UEs (e.g., UE1612c and / or 1612d) and a network node (e.g., network node 1610b). In some examples, hub 1614 may be a controller, router, content source and content analysis, or any other communication device described herein with respect to the UE. For example, hub 1614 may be a broadband router that enables access to the core network 1606 for the UE. In another example, hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node 1610, or by executable code, scripts, processes, or other instructions in hub 1614. In yet another example, hub 1614 may be a data collector acting as temporary storage for UE data, and in some embodiments may perform data analysis or other processing. In yet another example, hub 1614 may be a content source. For example, with respect to a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub 1614 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes, 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 UE, particularly when one or more of the UEs are low-energy IoT devices.

[0175] Hub 1614 may have always-on / persistent or intermittent connections to network node 1610b. Hub 1614 may also enable different communication methods and / or schedules between Hub 1614 and UEs (e.g., UE 1612c and / or 1612d), and between Hub 1614 and the core network 1606. In other examples, Hub 1614 connects to the core network 1606 and / or one or more UEs via wired connections. Furthermore, Hub 1614 may be configured to connect to an M2M service provider on the access network 1604 and / or another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 1610 while still being connected via wired or wireless connections through Hub 1614. In some embodiments, Hub 1614 may be a dedicated hub, i.e., a hub whose primary function is to route communication from the UE to network node 1610b and from network node 1610b to the UE. In other embodiments, the hub 1614 may be a non-dedicated hub, i.e., a device that can operate to route communication between the UE and the network node 1610b, but can also operate as a communication start and / or end point for several data channels.

[0176] Figure 17 shows UE1700 in several embodiments. As used herein, UE refers to a device that is capable of, configured, and / or operable of communicating wirelessly 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 devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), and vehicle-mounted or vehicle-embedded / integrated wireless devices. Other examples include any UE type designated and / or identified by 3GPP, including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0177] A UE may support device-to-device (D2D) communication by implementing, for example, sidelink (SL) communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and / or vehicle-to-everything (V2X) communication. In other examples, a UE is not necessarily associated with a specific human user who owns and / or operates the relevant device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with a specific human user, or may not be associated with a specific human user in the first place. Alternatively, a UE may represent a device (e.g., a smart electricity meter) that is not intended to be sold to or operated by a human user, but may be associated with or operate for the benefit of a user.

[0178] The UE1700 includes a processing circuit 1702 operably coupled via bus 1704 to an input / output interface 1706, a power supply 1708, memory 1710, a communication interface 1712, and / or any other components, or any combination thereof. Some UEs may utilize all or a subset of the components shown in Figure 17. The level of integration between components may vary from UE to UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, and receivers.

[0179] The processing circuit 1702 is configured to process instructions and data and may be configured to implement any sequential state machine capable of executing instructions stored in 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, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, a microprocessor or digital signal processor (DSP) with appropriate software, one or more stored computer programs, 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 an input device, an output device, or one or more interfaces to one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may allow a user to capture information to the UE1700. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors for detecting user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0181] In some embodiments, the power supply 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 supply 1708 may further include a power circuit for distributing power from the power supply 1708 itself and / or from an external power source via an interface such as an input circuit or power cable. Distributing power may, for example, be for charging the power supply 1708. The power circuit may perform any formatting, conversion, or other modifications to the power from the power supply 1708 to make that power suitable for each component of the UE 1700 to which the power is supplied.

[0182] Memory 1710 may be memory, or configured to contain 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 disks, optical disks, hard disks, removable cartridges, flash drives, etc. In one example, memory 1710 may contain one or more application programs 1714, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1716. Memory 1710 may store any of a variety of operating systems or combinations of operating systems for use by UE 1700.

[0183] Memory 1710 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-density digital versatile disk (HD-DVD) optical disk drives, internal hard disk drives, Blu-ray optical disk drives, holographic digital data storage (HDDS) optical disk drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smart card memory such as a tamper-proof module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs) such as USIM and / or 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". Memory 1710 may enable UE 1700 to access instructions, application programs, etc., stored in temporary or non-temporary memory media, to offload data, or to upload data. Products such as products utilizing a communication system may be tangibly embodied as memory 1710 or within memory 1710, and memory 1710 may be a device-readable storage medium 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 network node in the access network). Each transceiver may include a transmitter 1718 and / or receiver 1720 suitable for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, 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 alternatively, may be implemented separately.

[0185] In the embodiments shown, the communication functions of the communication interface 1712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine location, other similar communication functions, or any combination thereof. The communication may be implemented in accordance with one or more communication 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 sensor type, the UE may provide the output of data captured by the UE's sensors to network nodes via a wireless connection through the UE's communication interface 1712. The data captured by the UE's sensors may be communicated to network nodes via another UE through a wireless connection. The output may be periodic (e.g., once every 15 minutes if reporting detected temperature), in response to a triggering event (e.g., an alarm is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to equalize the load from reports from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0187] As another example, the UE may include an actuator, motor, or switch relating to a communication interface configured to receive radio input from a network node via a wireless connection. In response to the received radio input, the state of the actuator, motor, or switch may change. For example, the UE may include a motor that adjusts the 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] A UE, in the form of an Internet of Things (IoT) device, can be a device for use in one or more application areas, which include, but are not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are connected refrigerators or freezers, TVs, connected lighting devices, energy meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, immersion / 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, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic augmentation or perceptual 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 remotely controlled surgical robot, or devices embedded in them. The UE in the form of an IoT device comprises circuitry and / or software according to the intended application of the IoT device, in addition to the other components described with respect to the UE1700 shown in Figure 17.

[0189] In another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE could be an M2M device, which is sometimes called an MTC device in a 3GPP context. In one specific 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 its operational status and / or reporting on its operational status, or performing other functions related to its operation.

[0190] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be the drone itself, or integrated within the drone, providing the drone's speed information (obtained through a speed sensor) to the second UE, which is the remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UEs may also include two or more of the functions described above. For example, the UE may have sensors and actuators and handle the communication of data about both the speed sensor and the actuator.

[0191] Figure 18 shows a network node 1800 according to several embodiments. As used herein, a network node refers to a device that is configured, set up, and / or operable to communicate directly or indirectly with UEs in a communication network and / or with other network nodes or devices. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, node B, eNB, gNB).

[0192] Base stations can be categorized based on the amount of coverage they provide (or, in other words, the base station's transmit power level), and are therefore sometimes called femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage they provide. A base station can be a relay node or relay donor node that controls relays. Network nodes may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or remote radio unit (RRU), sometimes called 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 are sometimes called nodes in a distributed antenna system (DAS).

[0193] Other examples of network nodes include multiple transmit point (multi-TRP) 5G access nodes, MSR equipment such as multi-standard radio (MSR) BS, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base station transceiver stations (BTSs), transmit points, transmit nodes, multi-cell / multicast cooperative entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., E-SMLC, SLP, LMF), and / or drive test minimization (MDT).

[0194] Network node 1800 includes a processing circuit 1802, a memory 1804, a communication interface 1806, and a power supply 1808. Network node 1800 can be assembled from multiple physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own respective components. In some scenarios where network node 1800 has multiple distinct components (e.g., BTS components and BSC components), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single distinct network node. In some embodiments, network node 1800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1804 for different RATs), and some components may be reused (e.g., the same antenna 1810 may be shared by different RATs). The network node 1800 may also include multiple sets of various indicated components for different radio technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth radio technologies, which are integrated into the network node 1800. These radio technologies may be integrated into the same or different chips or sets of chips, and other components within the network node 1800.

[0195] The processing circuit 1802 may include one or more combinations of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic, which are capable of operating to provide network node 1800 functionality, either on its own or in combination with other network node 1800 components such as memory 1804.

[0196] In some embodiments, the processing circuit 1802 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 1802 includes one or more of the radio frequency (RF) transceiver circuit 1812 and the 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 radio and digital units. 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] Memory 1804 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid memory, remote-mount 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 disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory device for storing information, data, and / or instructions that can be used by the processing circuit 1802. Memory 1804 may store any suitable instructions, data, or information, including other instructions (collectively referred to as computer program product 1804a) that can be executed by the processing circuit 1802 and utilized by the network node 1800, including applications that include one or more computer programs, software, logic, rules, code, and tables. The memory 1804 may be used to store calculations performed by the processing circuit 1802 and / or data received via the communication interface 1806. In some embodiments, the processing circuit 1802 and the memory 1804 are integrated.

[0198] Communication interface 1806 is used in wired or wireless signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 1806 includes (one or more) ports / (one or more) terminals 1816 for sending and receiving data to and from the network, for example, over a wired connection. Communication interface 1806 also includes a wireless front-end circuit 1818, which is coupled to or, in some embodiments, may be part of antenna 1810. The wireless front-end circuit 1818 includes a filter 1820 and an amplifier 1822. The wireless front-end circuit 1818 may be connected to antenna 1810 and processing circuit 1802. The wireless front-end circuit may be configured to adjust signals communicated between antenna 1810 and processing circuit 1802. The wireless front-end circuit 1818 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit 1818 can convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter 1820 and / or amplifier 1822. The radio signal can then be transmitted via antenna 1810. Similarly, when receiving data, antenna 1810 can collect a radio signal, which is then converted into digital data by the wireless front-end circuit 1818. The digital data can then be passed to processing circuit 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; instead, the processing circuit 1802 includes the radio front-end circuit and is connected to the antenna 1810. Similarly, in some embodiments, all or part of the RF transceiver circuit 1812 is part of the communication interface 1806. In yet another embodiment, the communication interface 1806, as part of a radio unit (not shown), includes one or more ports or terminals 1816, the radio front-end circuit 1818, and the RF transceiver circuit 1812, and the communication interface 1806 communicates with a baseband processing circuit 1814, which is part of a digital unit (not shown).

[0200] Antenna 1810 may include one or more antennas or antenna arrays configured to transmit and / or receive radio signals. Antenna 1810 may be coupled to the radio front-end circuit 1818 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1810 is separate from the network node 1800 and can be connected to the network node 1800 through an interface or port.

[0201] Antenna 1810, communication interface 1806, and / or processing circuit 1802 may be configured to perform any receiving operations and / or certain acquisition operations as described herein as being performed by a network node. Any information, data, and / or signals may be received from the UE, another network node, and / or any other network equipment. Similarly, antenna 1810, communication interface 1806, and / or processing circuit 1802 may be configured to perform any transmitting operations as described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to the UE, another network node, and / or any other network equipment.

[0202] Power supply 1808 provides power to various components of network node 1800 in a form suitable for each component (for example, at the voltage and current levels required for each respective component). Power supply 1808 may further include, or be coupled to, a power management circuit for supplying power to the components of network node 1800 to perform the functions described herein. For example, 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, thereby the external power source powers the power circuit of power supply 1808. As a further example, power supply 1808 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. The battery may provide backup power in the event of an external power failure.

[0203] Embodiments of network node 1800 may include additional components other than those shown in Figure 18 to provide several aspects of the network node's functionality, including any of the functions described herein and / or functions necessary to support the subject matter described herein. For example, network node 1800 may include user interface equipment for enabling information input to and output from network node 1800. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1800.

[0204] Figure 19 is a block diagram of host 1900, which may be one embodiment of host 1616 of Figure 16, according to various aspects described herein. Host 1900 as used herein may be a variety of combinations of hardware and / or software, including standalone servers, blade servers, cloud implementation servers, distributed servers, virtual machines, containers, or processing resources in a server farm. 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 supply 1910, and a memory 1912 via a bus 1904. Other embodiments may include other components. The features of these components may be substantially similar to those described with respect to the devices in previous figures, such as Figures 17 and 18, and therefore their descriptions are generally applicable to the corresponding components of the host 1900.

[0206] Memory 1912 may include one or more computer programs, each containing one or more host application programs 1914 and data 1916, the data 1916 of which may include user data, for example, data generated by the UE for host 1900, or data generated by host 1900 for the UE. Embodiments of host 1900 may utilize only a subset or all of the components shown. Host application programs 1914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multipurpose 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 the UE (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application program 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 a device at the edge of the core network. Thus, host 1900 may select and / or direct different hosts for over-the-top services for the UE. The host application program 1914 may support various protocols, including HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0207] Figure 20 is a block diagram showing a virtualization environment 2000 in which functions implemented by several embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein may apply to any device or its components described herein and relates to an implementation in which at least a portion of the 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 virtualization environments 2000 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require wireless connectivity (e.g., core network nodes or hosts), the nodes may be fully virtualized.

[0208] Application 2002 (which may alternatively be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) runs in a virtualized environment 2000 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0209] Hardware 2004 includes processing circuits, memory for storing software (collectively referred to as Computer Program Product 2004a) and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 2006 (also called hypervisors or virtual machine monitors (VMMs)), providing VM2008a and 2008b (one or more of which are commonly referred to as VM2008), and / or may implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 2006 may present VM2008 with a virtual operating platform that looks like networking hardware.

[0210] VM2008 provides virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by the corresponding virtualization layer 2006. Different embodiments of the virtual appliance 2002 example may be implemented on one or more of VM2008, and the implementation may be done in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment onto industry-standard high-volume server hardware, physical switches, and physical storage, which may reside in data centers and customer premises equipment.

[0211] In the context of NFV, VM2008 can be a software implementation of a physical machine, where programs run as if they were running on a physical, non-virtualized machine. Each VM2008 and its portion of the hardware 2004 on which it runs, whether that hardware is dedicated to that VM and / or shared by that VM with other VMs in the VM, form a separate virtual network element. Furthermore, in the context of NFV, the virtual network function is responsible for handling specific network functions running in one or more VM2008s on the hardware 2004, and corresponds to application 2002.

[0212] Hardware 2004 may be implemented in a standalone network node with general or specific components. Hardware 2004 may implement some functions through virtualization. Alternatively, Hardware 2004 may be part of a larger cluster of hardware (such as in a data center or CPE) where many hardware nodes cooperate and are managed via management and orchestration 2010, particularly overseeing the lifecycle management of applications 2002. In some embodiments, 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 suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio 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 be used alternatively for communication between the hardware nodes and the radio units.

[0213] Figure 21 shows a communication diagram of host 2102 communicating with UE 2106 via network node 2104 over a partial wireless connection, according to several embodiments. Next, exemplary implementations of various embodiments of the UE (such as UE 1612a in Figure 16 and / or UE 1700 in Figure 17), network nodes (such as network node 1610a in Figure 16 and / or network node 1800 in Figure 18), and hosts (such as host 1616 in Figure 16 and / or host 1900 in Figure 19), as described in the previous paragraph, will be described with reference to Figure 21.

[0214] Similar to host 1900, embodiments of host 2102 include hardware such as a communication interface, processing circuitry, and memory. Host 2102 also includes software that is stored in or accessible by host 2102 and executable by the processing circuitry. The software includes a host application that may be capable of operating to serve a remote user, such as UE 2106 connected via an over-the-top (OTT) connection 2150 extending between UE 2106 and host 2102. When serving a remote user, the host application may provide user data transmitted using the OTT connection 2150.

[0215] Network node 2104 includes hardware that enables network node 2104 to communicate with host 2102 and UE 2106. The connection 2160 may be direct or pass through a core network (similar to core network 1606 in Figure 16) and / or one or more other intermediate networks, such as one or more public networks, private networks, or hosted networks. For example, the intermediate network could be a backbone network or the internet.

[0216] UE2106 includes hardware and software that is stored in or accessible by UE2106 and executable by the UE's processing circuitry. The software includes client applications, such as a web browser or operator-specific “app,” which may be capable of operating to serve human or non-human users through UE2106, with the support of host 2102. On host 2102, the running host application may communicate with the running client application via an OTT connection 2150 that terminates at UE2106 and host 2102. When serving a user, the UE's client application may receive request data from the host's host application 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 UE's client application may interact with the user to generate user data that the UE's client application provides to the host application via the OTT connection 2150.

[0217] The OTT connection 2150 may extend via connection 2160 between host 2102 and network node 2104, and via wireless connection 2170 between network node 2104 and UE 2106, in order to provide a connection between host 2102 and UE 2106. Connections 2160 and wireless connection 2170, through which the OTT connection 2150 may be provided, are depicted abstractly to illustrate communication between host 2102 and UE 2106 via 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 via the OTT connection 2150, in step 2108, host 2102 provides user data, which may be done by running a host application. In some embodiments, the user data relates to a specific human user interacting with UE 2106. In other embodiments, the user data relates to UE 2106 sharing data with host 2102 without explicit human interaction. In step 2110, host 2102 initiates a transmission to carry user data toward UE 2106. Host 2102 may initiate a transmission in response to a request sent by UE 2106. The request may be triggered by human interaction with UE 2106 or by the operation of a client application running on UE 2106. The transmission may proceed through network node 2104 in accordance with the teachings of embodiments described throughout this disclosure. Accordingly, in step 2112, the network node 2104 transmits the user data carried in the transmission initiated by host 2102 to UE 2106, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2114, UE 2106 receives the user data carried in the transmission, which may be done by a client application running on UE 2106 related to a host application run by host 2102.

[0219] In some examples, UE2106 runs a client application that provides user data to host 2102. User data may be provided in response to or in reaction to data received from host 2102. Thus, in step 2116, UE2106 may provide user data, which may be done by running a client application. When providing user data, the client application may further consider user input received from the user via the input / output interface of UE2106. Regardless of the particular form in which the user data is provided, UE2106 initiates a transmission of the user data to host 2102 via network node 2104 in step 2118. In step 2120, in accordance with the teachings of embodiments described throughout this disclosure, network node 2104 receives user data from UE2106 and initiates a transmission of the received user data to host 2102. In step 2122, host 2102 receives the user data carried in the transmission initiated by UE2106.

[0220] One or more of the various embodiments improve the performance of OTT services provided to UE 2106 by using OTT connection 2150, in which wireless connection 2170 forms the final segment. More precisely, the embodiments described herein can provide a flexible and efficient technique for supporting on-demand PRS transmissions as network conditions change. Embodiments can also be used to select a PRS configuration that is suitable for not just one, but many UEs, which provides more efficient UE positioning based on DL PRS transmissions. Embodiments can also reduce energy consumption of RAN nodes by avoiding the transmission of PRS resources that are not needed. In this way, embodiments can improve the delivery of positioning-based OTT services over 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 host 2102. As another example, host 2102 may process audio and video data that may be extracted from the UE for use in creating maps. As yet another example, host 2102 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic signals). As yet another example, host 2102 may store surveillance video uploaded by the UE. As yet another example, host 2102 may store or control access to media content, such as video, audio, VR, or AR, which host 2102 can broadcast, multicast, or unicast to the UE. As yet another example, host 2102 may be used for energy pricing, remote control of non-time-constrained electrical loads to balance generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, extracting, storing, analyzing, and / or transmitting data.

[0222] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors, which are improved by one or more embodiments. Further optional network functions may be provided for reconfiguring the OTT connection 2150 between host 2102 and UE 2106 in response to variations in measurement results. Measurement procedures and / or network functions for reconfiguring the OTT connection may be implemented in software and hardware of host 2102 and / or UE 2106. In some embodiments, sensors (not shown) may be deployed in or in relation to other devices through which the OTT connection 2150 passes, and the sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above, or values ​​of other physical quantities that the software can calculate or estimate the monitored quantities of. Reconfiguring the OTT connection 2150 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration does not require a direct change in the operation of network node 2104. Such procedures and functions are known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling by host 2102 to facilitate measurements such as throughput, propagation time, and latency. The measurements may be implemented in which software uses the OTT connection 2150 to cause messages, particularly empty or "dummy" messages, to be sent while monitoring propagation time, errors, etc.

[0223] The foregoing is merely an illustration of the principles of this disclosure. In view of the teachings herein, various modifications and alterations of the embodiments described will become apparent to those skilled in the art. Therefore, it will be understood that a number of systems, configurations, and procedures not expressly shown or described herein, but which embody the principles of this disclosure and thus fall within the spirit and scope of this disclosure, can be devised by those skilled in the art. Various embodiments can be used together and interchangeably with one another, as should be understood by those skilled in the art.

[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 solids and / or individual devices, computer programs or instructions, etc., for performing their respective tasks, procedures, calculations, outputs, and / or display functions, such as those described herein.

[0225] Any suitable step, method, feature, function, or benefit 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 circuits, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuits may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory may include program instructions for executing one or more communication and / or data communication protocols, and instructions for performing one or more of the techniques described herein. In some implementations, the processing circuits may be used to cause each functional unit to perform the corresponding function according to one or more embodiments of the Disclosure.

[0226] As described herein, 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 be implemented as a software module, such as a computer program or computer program product, comprising executable software code portions for or running on a processor, instead of being implemented in hardware. Furthermore, the functionality of a 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 across a system, as long as the functionality of the device or apparatus is maintained. Such and similar principles are considered to be known to those skilled in the art.

[0227] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as they would ordinarily be understood by those skilled in the art to which this disclosure belongs. Terms used herein should be interpreted as having the meanings of those terms in the context of this specification and the related art, and not in an ideal or overly formal sense unless expressly provided herein.

[0228] Furthermore, some terms used in this disclosure, including in the specification and drawings, may be used synonymously in some instances (for example, “data” and “information”). It should be understood that while these terms (and / or other terms that may be synonymous with each other) may be used synonymously in this specification, there may be instances where such words are not intended to be used synonymously. Furthermore, unless prior art knowledge is expressly incorporated herein by reference above, the entirety of the prior art knowledge is expressly incorporated herein. All referenced publications are incorporated herein by reference in their entirety.

[0229] Furthermore, embodiments of the techniques and apparatus described herein include, but are not limited to, the following listed examples. A1. A method for a user device (UE) configured for positioning in a radio access network (RAN), the method being: Receiving multiple settings for the positioning reference signal (PRS) transmitted by the RAN nodes from a positioning node associated with the RAN, wherein the multiple settings are associated with each of the multiple setting indices. Determine whether you need to receive PRS and select one or more of several settings based on one or more selection rules. Sending one or more requests to a positioning node for TRS transmission via RAN, wherein one or more requests include one or more configuration indices related to one or more selected configurations. Methods that include... A2. Multiple settings have the following characteristics or parameters, namely: PRS transmission periodicity, PRS transmission bandwidth, The number of PRS transmission frequency layers used, The specific PRS transmit frequency layer used, Number of RAN nodes that send PRS, A specific RAN node that sends PRS, Geographic configuration of RAN nodes that transmit PRS, Number of PRS resource sets per node, Number of PRS per PRS resource set, Energy consumption and / or signaling overhead associated with transmitting PRS according to the settings, Related geographical areas, Positioning spatial dimension, Positioning accuracy, quality of service (QoS), and Positioning Latency QoS The method according to Embodiment A1, distinguished from each other based on one or more of the following. A2a. The method according to Embodiment A2, further comprising receiving instructions for characteristics or parameters, in which multiple settings are distinguished, from a positioning node, and selecting one or more of the multiple settings based on the indicated characteristics or parameters. A2b. The method according to any one of embodiments A1 to A2a, further comprising receiving selection rules from a positioning node. A3. Multiple settings are, A first setting that includes default values ​​for the setting parameters, One or more further settings, where each further setting includes only the setting parameters among the setting parameters that have a value different from the default value, and A method according to any one of embodiments A1 to A2b, including the method described above. A4. The method according to Embodiment A3, wherein a first setting is received via a broadcasted first system information block (SIB), and one or more further settings are received via a broadcasted second SIB. A5. The method according to Embodiment A4, wherein the first SIB indicates that the first setting is either the default setting or the active setting. A6. The method according to any one of Embodiments A1 to A5, wherein each request includes one index related to one selected setting. A7. The method according to Embodiment A6, wherein the selection rule includes a sequential order in which each setting may be requested by the UE. A8. 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 settings that may be requested by the UE in the initial request, A second rule that identifies a second subset of settings that may be requested by the UE in subsequent requests, The method according to embodiment A6, including the method described in embodiment A6. A9. A first subset of settings includes a first setting that requires the minimum energy to transmit PRS, The second subset includes at least one configuration that requires more energy to transmit PRS than the first configuration. The method described in Embodiment A8. A10. Selecting one or more of multiple settings based on one or more selection rules is possible. To determine whether positioning based on PRS transmission according to the first setting will satisfy the positioning quality of service (QoS) threshold, When it is determined that the positioning QoS threshold will be met, select the first setting, When it is determined that the positioning QoS threshold will not be met, select a second subset of settings. The method according to Embodiment A9, including the method described in Embodiment A9. A11. The method according to Embodiment A10, wherein the positioning QoS threshold relates 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. One or more subsequent requests include a first subsequent request and a second subsequent request following the first subsequent request. The second rule identifies when a second setting may be selected for a first subsequent request, and when a third setting may be selected for a second subsequent request. The method according to Embodiment A9. A13. One or more requests include a single request that contains at least two configuration indexes. The selection rule must include a third rule that indicates one of more configuration parameters, which must be common among at least two configurations identified by at least two configuration indices. The method according to any one of Embodiments A1 to A5. A14. The method according to Embodiment A13, wherein the third rule indicates that at least the following parameters, namely the PRS transmission periodicity and the specific RAN node from which the PRS is transmitted, must be common among a plurality of selected configurations. A15. The method according to embodiment A13 or A14, further comprising performing positioning measurements on a PRS transmitted coherently according to at least two settings. B1. A method for a positioning node related to a radio access network (RAN), the method being: Determining multiple settings for a positioning reference signal (PRS) transmitted by a RAN node, wherein the multiple settings are associated with each of the multiple setting indices. Sending multiple configurations and associated configuration indices to RAN nodes and user equipment (UEs) operating within the RAN, The UE receives one or more requests for PRS transmission via RAN, according to one or more settings indicated by one or more associated setting indices. Methods that include... B1a. The method according to Embodiment B1, further comprising configuring a node to transmit a PRS according to one or more settings instructed by the UE, or one or more further settings selected by the positioning node. B2. 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, the number of PRS transmission frequency layers used, a specific PRS transmission frequency layer used, the number of RAN nodes that transmit PRS, a specific RAN node that transmits PRS, the geographical configuration of RAN nodes that transmit PRS, the number of PRS resource sets per node, the number of PRS per PRS resource set, energy consumption and / or signaling overhead associated with transmitting PRS in accordance with the configuration, a relevant geographical area, a positioning spatial dimension, positioning accuracy quality of service (QoS), and positioning latency QoS The method according to embodiment B1 or B1a, wherein the plurality of configurations are distinguished from each other based on one or more of the above. B2a. The method according to embodiment B2, further comprising: sending, to a UE, an indication of the characteristic or parameter for which the plurality of configurations are distinguished. B3. The plurality of configurations comprise: a first configuration including default values for configuration parameters, and one or more further configurations, wherein each further configuration includes only those configuration parameters among the configuration parameters that have a value different from the default value, The method according to any one of embodiments B1 to B2a, comprising the above. B4. The method according to embodiment B3, wherein 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 according to Embodiment B4, wherein the first SIB indicates that the first setting is either the default setting or the active setting. B5a. The method according to any one of Embodiments B1 to B5, further comprising sending a selection rule to the UE for selecting between multiple settings. B6. The method according to embodiment B5a, wherein each request includes one index associated with one selected setting. B7. The method according to Embodiment B5a or B6, wherein the selection rule includes a sequential order in which each setting may be requested by the UE. B8. 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 settings that may be requested by the UE in the initial request, A second rule that identifies a second subset of settings that may be requested by the UE in subsequent requests, and The method according to embodiment B5a or B6, including the method described in embodiment B5a or B6. B9. The first subset includes a first configuration that requires the minimum energy to transmit the PRS, The second subset includes at least one configuration that requires more energy to transmit PRS than the first configuration. The method described in Embodiment B8. B10. The method according to Embodiment B9, wherein the selection rule includes a positioning quality of service (QoS) threshold for selecting between a first setting and a second subset of settings. B11. The method according to Embodiment B10, wherein the positioning QoS threshold relates 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. One or more subsequent requests include a first subsequent request and a second subsequent request following the first subsequent request. The second rule identifies when a second setting may be selected for a first subsequent request, and when a third setting may be selected for a second subsequent request. The method described in Embodiment B9. B13. One or more requests include a single request that contains at least two configuration indices. The selection rule must include a third rule that indicates one of more configuration parameters, which must be common among at least two configurations identified by at least two configuration indices. The method described in embodiment B5a. B14. The method according to Embodiment B13, wherein the third rule indicates that at least the following parameters, namely the PRS transmission periodicity and the specific RAN node from which the PRS is transmitted, must be common between at least two settings. B15. The method according to embodiment B13 or B14, wherein configuring a node includes configuring multiple nodes to coherently transmit PRS according to at least two settings. B16. It is possible to determine multiple settings. To obtain the default settings for PRS transmission, Multiple settings, Measurements performed by the UE on PRS sent according to default settings. Node capabilities, The number of UEs operating in the RAN, and One or more distinguishing characteristics or parameters Based on this, the decision will be made. A method according to any one of embodiments B1 to B15, including the method described above. B17. Determining multiple settings is possible, Measurements performed by the UE on PRS transmitted according to multiple settings, Node's updated capabilities, The number of updated UEs operating in RAN, and One or more distinguishing characteristics or parameters The method according to 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, wherein the plurality of configurations are associated with respective plurality of configuration indices; thereafter receiving, from the positioning node, one or more requests for PRS transmission in accordance with one or more of the configurations identified by the associated one or more configuration indices; and transmitting a PRS in accordance with one or more of the configurations identified by the associated one or more configuration indices , the method comprising. C2. The plurality of configurations are distinguished from each other based on one or more of the following characteristics or parameters, that is: PRS transmission periodicity, PRS transmission bandwidth, the number of PRS transmission frequency layers used, a specific PRS transmission frequency layer used, the number of RAN nodes transmitting the PRS, a specific RAN node transmitting the PRS, the geographical configuration of RAN nodes transmitting the PRS, the number of PRS resource sets per node, the number of PRSs per PRS resource set, energy consumption and / or signaling overhead associated with transmitting a PRS in accordance with the configuration, a relevant geographical area, positioning space dimension, positioning accuracy quality of service (QoS), and positioning latency QoS The method according to Embodiment C1, which is distinguished from each other based on one or more of C3. The plurality of configurations are a first configuration comprising a default value for a configuration parameter, and One or more further settings, where each further setting includes only the setting parameters among the setting parameters that have a value different from the default value, and A method according to embodiment C1 or C2, including the method described in embodiment C1 or C2. C4. The method according to embodiment C3, further comprising broadcasting a first setting in a first system information block (SIB) and broadcasting one or more further settings in a second SIB. C5. The method according to embodiment C4, wherein the first SIB indicates that the first setting is one of the default setting or the active setting. C6. One or more requests include an initial request and one or more subsequent requests, and the settings are A first subset of settings that may be requested by the UE in the initial request, A second subset of settings that may be requested by the UE in subsequent requests and A method according to any one of embodiments C1 to C5, including the method described above. C7. A first subset of settings includes a first setting that requires the minimum energy to transmit PRS. The second subset includes at least one configuration that requires more energy to transmit PRS than the first configuration. The method according to Embodiment C6. C8. The method according to 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. One or more requests include a single request that contains at least two configuration indexes. At least the PRS transmission periodicity is common among at least two settings identified by at least two setting indices. The method according to any one of embodiments C1 to C5. C10. The method according to embodiment C9, wherein transmitting a PRS includes coherently transmitting a PRS according to at least two settings. D1. User equipment (UE) configured for positioning in a wireless access network (RAN), wherein the UE is A communication interface circuit configured to communicate with RAN nodes and positioning nodes associated with RAN, A processing circuit operably coupled to a wireless transceiver circuit, wherein the processing circuit and the wireless transceiver circuit are configured to perform an operation corresponding to any of the methods described in Embodiments A1 to A15. User equipment (UE) equipped with these features. D2. A user device (UE) configured for positioning in a radio access network (RAN), wherein the UE is further configured to perform operations corresponding to any of the methods described in embodiments A1 to A15. D3. A non-temporary computer-readable medium that stores computer-executable instructions that, when executed by the processing circuitry of a user device (UE) configured for positioning in a wireless access network (RAN), cause the UE to perform an operation corresponding to any of the methods described in Embodiments A1 to A15. D4. A computer program product comprising computer-executable instructions, when executed by a processing circuit of a user device (UE) configured for positioning in a wireless access network (RAN), that configures the UE to perform an operation 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), wherein the positioning node is A communication interface circuit configured to communicate with RAN nodes and user equipment (UEs) operating in the RAN, A processing circuit operably coupled to a communication interface circuit, wherein the processing circuit and the communication interface circuit are configured to perform an operation corresponding to any of the methods described in Embodiments B1 to B170. A positioning node equipped with the following features. E2. A positioning node configured to operate with a radio access network (RAN), wherein the positioning node is further configured to perform operations corresponding to any of the methods described in Embodiments B1 to B17. E3. A non-temporary computer-readable medium that stores computer-executable instructions that, when executed by the processing circuitry of a positioning node configured to operate with a radio access network (RAN), configure the positioning node to perform an operation corresponding to any of the methods described in Embodiments B1 to B17. E4. A computer program product comprising computer-executable instructions, when executed by a processing circuit of a positioning node configured to operate with a radio access network (RAN), that configures the positioning node to perform an operation corresponding to any of the methods described in Embodiments B1 to B17. F1. A network node of a wireless access network (RAN), where a network node is A communication interface circuit configured to communicate with user equipment (UE) and positioning nodes, A processing circuit operably coupled to a communication interface circuit, wherein the processing circuit and the communication interface circuit are configured to perform an operation corresponding to any of the methods described in Embodiments C1 to C10. A network node equipped with these features. F2. A network node of a wireless access network (RAN), wherein the network node is configured to perform an operation corresponding to any of the methods described in embodiments C1 to C10. F3. A non-temporary computer-readable medium for storing computer-executable instructions that, when executed by a processing circuit of a network node of a wireless access network (RAN), configure the network node to perform an operation 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 a processing circuit of a network node of a wireless access network (RAN), configure the network node to perform an operation corresponding to any of the methods described in embodiments C1 to C10.

Claims

1. A method for a user device (UE) configured for positioning in a wireless access network (RAN), wherein the method is: From the positioning node associated with the aforementioned RAN, Multiple settings for the positioning reference signal (PRS) transmitted by the RAN, Multiple corresponding setting indices related to the aforementioned multiple settings and Receiving (1310), Determining the need to receive PRS and selecting one or more of the above settings based on one or more selection rules (1340), Sending one or more requests to the positioning node for PRS transmission by the RAN (1350), wherein the one or more requests include one or more setting indices related to the one or more selected settings. Includes, The selection rule includes a method that includes a sequential order in which each setting may be requested by the UE in that order.

2. The aforementioned multiple settings have the following characteristics or parameters, namely, PRS transmission periodicity, PRS transmission bandwidth, The number of PRS transmission frequency layers used, The specific PRS transmission frequency layer used, Number of RAN nodes that send PRS, A specific RAN node that sends PRS, Geographic configuration of RAN nodes transmitting PRS, Number of PRS resource sets per node, Number of PRS per PRS resource set, Energy consumption and / or signaling overhead associated with transmitting PRS according to the above settings, Related geographical areas, Positioning spatial dimension, Positioning accuracy, quality of service (QoS), and Positioning Latency QoS The method according to claim 1, characterized in that the members are distinguished from one or more of the following.

3. The method of claim 2, further comprising receiving instructions from the positioning node for the characteristics or parameters which distinguish the plurality of settings (1320), and selecting one or more of the plurality of settings based on the indicated characteristics or parameters.

4. The method according to claim 1, further comprising receiving the selection rule from the positioning node (1330).

5. The aforementioned multiple settings are, A first setting including default values ​​for the setting parameters, One or more further settings, each of which includes only the setting parameters among the setting parameters having a value different from the default value, and The method according to claim 1, including the method described in claim 1.

6. The first setting is received via the broadcasted first system information block (SIB), The one or more of the above-mentioned settings are received via the broadcasted second SIB, The first SIB indicates that the first setting is either the default setting or the active setting. The method according to claim 5.

7. The method according to claim 1, wherein each request includes one index associated with 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 that identifies a first subset of settings that may be requested by the UE in the initial request, A second rule for identifying a second subset of settings that may be requested by the UE in the subsequent request: The method according to claim 1, including the method described in claim 1.

9. The first subset of settings includes a first setting that requires the minimum energy for transmitting the PRS, The second subset includes at least one setting that requires more energy to transmit PRS than the first setting. The method according to claim 8.

10. Selecting one or more of the above settings based on one or more selection rules (1340) To determine whether positioning based on PRS transmission according to the first setting will satisfy the positioning service quality (QoS) threshold (1341), When it is determined that the positioning QoS threshold will be met, the first setting is selected (1342), When it is determined that the positioning QoS threshold will not be met, select the setting of the second subset (1343) Includes, The positioning QoS threshold relates to one or more of the following: 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 following 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. The method according to claim 9.

12. The one or more requests include a single request that includes at least two setting indices, The selection rule includes a third rule that specifies one or more configuration parameters, such that the selection rule must be common among at least two configurations related to the at least two configuration indices 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 transmitting the PRS, must be common among the at least selected settings.

14. The method of claim 12, further comprising performing a positioning measurement (1360) on a PRS that is transmitted coherently according to the at least two settings related to the at least two setting indices included in the single request.

15. A method for a positioning node related to a radio access network (RAN), wherein the method is Determining a plurality of settings for a positioning reference signal (PRS) transmitted by a RAN node (1410), wherein the plurality of settings are related to a plurality of corresponding setting indices, Sending the plurality of settings and the plurality of associated setting indices to the RAN node and to user equipment (UE) operating in the RAN (1420), Receiving one or more requests from the UE for PRS transmission by the RAN (1450), wherein the one or more requests include one or more of the setting indices relating to one or more of the settings selected by the UE based on one or more selection rules, the selection rules include a sequential order such that each setting can be requested by the UE in that order. Methods that include...

16. Determining the above-mentioned multiple settings (1410) Obtaining the default settings for PRS transmission (1411), The above multiple settings, Measurements performed by the UE on the PRS transmitted according to the default settings, The capabilities of the aforementioned RAN node, The number of UEs operating in the aforementioned RAN, and One or more distinguishing characteristics or parameters Based on that, to make a decision (1412) The method according to claim 15, including the method described in claim 15.

17. Determining the above-mentioned multiple settings (1410) means that the above-mentioned multiple settings Measurements performed by the UE on the PRS transmitted according to the above multiple settings, The updated capabilities of the aforementioned RAN node, The number of updated UEs operating in the aforementioned RAN, and The one or more distinguishing characteristics or parameters The method according to claim 16, comprising adapting based on one or more of the following (1413).

18. A method for a wireless access network (RAN) node, the method is From the positioning node associated with the aforementioned RAN, Multiple settings for transmitting positioning reference signals (PRS), Multiple corresponding setting indices related to the aforementioned multiple settings and Receiving (1510), Subsequently, receiving one or more requests for PRS transmission from the positioning node (1530), wherein the one or more requests include one or more of the plurality of setting indices, Sending a PRS according to one or more of the settings related to the one or more setting index included in the one or more requests (1540) Includes, The one or more requests include an initial request and one or more subsequent requests, and the setting is A first subset of settings that may be requested by the UE in the aforementioned initial request, A second subset of settings that may be requested by the UE in the subsequent request: Methods that include...

19. User equipment (UE) (205, 310, 410, 1612, 1700, 2106) configured for positioning in a wireless access network (RAN) (199, 299, 420, 1604), wherein the UE is, From the positioning nodes associated with the aforementioned RAN (440, 450, 460, 1220, 1800, 2002), Multiple settings for the positioning reference signal (PRS) transmitted by the RAN, Multiple corresponding setting indices related to the aforementioned multiple settings and Receiving and To determine the need to receive PRS, and to select one or more of the above settings based on one or more selection rules, Sending one or more requests to the positioning node for PRS transmission by the RAN, wherein the one or more requests include one or more setting indices related to the one or more selected settings. Further settings are configured to do so, The selection rule includes a sequential order of user equipment (UE) (205, 310, 410, 1612, 1700, 2106) such that each setting may be requested by the UE in that order.

20. The UE according to claim 19, further configured to perform an operation corresponding to the method described in any one of claims 2 to 14.

21. A computer program comprising a computer-executable instruction, when executed by a processing circuit (1702) of a user device (UE) (205, 310, 410, 1612, 1700, 2106) configured for positioning in a wireless access network (RAN) (199, 299, 420, 1604), that configures the UE to perform an operation corresponding to the method of any one of claims 1 to 14.

22. Positioning nodes (440, 450, 460, 1220, 1800, 2002) configured to operate with wireless access networks (RANs) (199, 299, 420, 1604), wherein the positioning nodes are Determining multiple settings for positioning reference signals (PRS) transmitted by RAN nodes (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104), wherein the multiple settings relate to a plurality of corresponding setting indices. Sending the multiple settings and the associated multiple setting indices to the RAN node and to the user equipment (UE) (205, 310, 410, 1612, 1700, 2106) operating in the RAN, Receiving one or more requests from the UE for PRS transmission by the RAN, wherein the one or more requests include one or more of the setting indices relating to one or more of the settings selected by the UE based on one or more selection rules, and the selection rules include a sequential order such that each setting can be requested by the UE in that order. Positioning nodes (440, 450, 460, 1220, 1800, 2002) have been further configured to perform this function.

23. A computer program comprising computer-executable instructions, which, when executed by the processing circuits (442, 452, 462, 1802, 2004) of a positioning node (440, 450, 460, 1220, 1800, 2002) configured to operate with a wireless access network (RAN) (199, 299, 420, 1604), configure the positioning node to perform an operation corresponding to the method of any one of claims 15 to 17.

24. Radio access network (RAN) nodes (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104) configured to support the positioning of user equipment (UE) (205, 310, 410, 1612, 1700, 2106), wherein the RAN nodes are, From the positioning nodes associated with RAN (440, 450, 460, 1220, 1800, 2002), Multiple settings for transmitting positioning reference signals (PRS), Multiple corresponding setting indices related to the aforementioned multiple settings and Receiving and Subsequently, the positioning node receives one or more requests for PRS transmission, wherein the one or more requests include one or more of the plurality of setting indices. Sending a PRS according to one or more of the settings related to the one or more setting indexes included in the one or more requests Further settings are configured to do so, The one or more requests include an initial request and one or more subsequent requests, and the setting is A first subset of settings that may be requested by the UE in the initial request, A second subset of settings that may be requested by the UE in the subsequent request: This includes wireless access network (RAN) nodes (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104).

25. A computer program comprising a computer-executable instruction, when executed by the processing circuits (1802, 2004) of a wireless access network (RAN) node (100, 210, 220, 421, 422, 610, 1210, 1610, 1800, 2002, 2104), that causes the RAN node to perform an operation corresponding to any of the methods described in claim 18.

Images