Patent Description:
Standardization bodies such as Third Generation Partnership Project (3GPP) are studying potential solutions for efficient operation of wireless communication in new radio (NR) networks. The next generation mobile wireless communication system <NUM>/NR will support a diverse set of use cases and a diverse set of deployment scenarios. The later includes deployment at both low frequencies (e.g. <NUM> of MHz), similar to LTE today, and very high frequencies (e.g. mm waves in the tens of GHz). Besides the typical mobile broadband use case, NR is being developed to also support machine type communication (MTC), ultra-low latency critical communications (URLCC), side-link device-to-device (D2D) and other use cases.

Positioning and location services have been topics in LTE standardization since 3GPP Release <NUM>. An objective was to fulfill regulatory requirements for emergency call positioning but other use case like positioning for Industrial Internet of Things (I-IoT) are also considered. Positioning in NR is supported by the example architecture shown in <FIG>. LMF 108A represents the location management function entity in NR. There are also interactions between the LMF 108A and the gNodeB <NUM> via the NRPPa protocol. The interactions between the gNodeB <NUM> and the device (UE) <NUM> are supported via the Radio Resource Control (RRC) protocol, while the location node 108A interfaces with the UE <NUM> via the LTE positioning protocol (LPP). LPP is common to both NR and LTE technologies. Other network nodes, such as Access and Mobility Management Function (AMF) 108B and evolved Serving Mobile Location Center (e-SMLC) 108C, may be involved in positioning support.

It will be appreciated that while <FIG> shows gNB 110B and ng-eNB 110A, both may not always be present. It is noted that when both the gNB 110B and ng-eNB 110A are present, the NG-C interface is generally only present for one of them.

In the legacy LTE standards, the following techniques are supported:.

The NR positioning for Release <NUM>, based on the 3GPP NR radio-technology, is positioned to provide added value in terms of enhanced location capabilities. The operation in low and high frequency bands (i.e. below and above <NUM>) and utilization of massive antenna arrays provide additional degrees of freedom to substantially improve the positioning accuracy. The possibility to use wide signal bandwidth in low and especially in high bands brings new performance bounds for user location for well-known positioning techniques based on OTDOA and UTDOA, Cell-ID or E-Cell-ID etc., utilizing timing measurements to locate a UE.

In NR Release <NUM>, several positioning features have been specified including reference signals, measurements, and positioning methods.

NR positioning supports the following methods:.

<NUM>, the following UE measurements are specified:.

<NUM>, the following gNB measurements are specified:.

In NR Release <NUM>, the DL PRS is configured by each cell separately, and the location server (LMF) collects all configuration via the NRPPa protocol, before sending an assistance data (AD) message to the UE via the LPP protocol. In the uplink, the SRS signal is configured in RRC by the serving gNB, which in turn forwards appropriate SRS configuration parameters to the LMF upon request.

NR Release <NUM> DL PRS is organized in a <NUM>-level hierarchy:.

Similar to LTE, in NR a unique reference signal is transmitted from each antenna port at the gNB for downlink channel estimation at a UE. Reference signals for downlink channel estimation are commonly referred to as channel state information reference signal (CSI-RS).

A CSI-RS signal is transmitted on a set of time-frequency resource elements (REs) associated with an antenna port. For channel estimation over a system bandwidth, CSI-RS is typically transmitted over the whole system bandwidth. The set of REs used for CSI-RS transmission is referred to as CSI-RS resource. From a UE point of view, an antenna port is equivalent to a CSI-RS that the UE shall use to measure the channel. Up to <NUM> (i.e. Ntx = <NUM>) antenna ports are supported in NR and thus <NUM> CSI-RS signals can be configured for a UE.

In NR, the following three types of CSI-RS transmissions are supported:.

A cell can consist of multiple TRPs with each TRP located in distinct coordinates, an example of which is shown in <FIG>. This sort of configuration is expected to be used in I-IOT scenarios. As an example, one cell with <NUM>, <NUM> or even more TRPs may be used to cover a complete factory hall.

For positioning, as such, three distinct co-ordinates are required to perform multilateration. With this sort of scenario where a serving cell has multiple TRPs located in distinct co-ordinates, it should be possible to exploit this for positioning.

In NR release <NUM>, the PRS-based measurements (including PRS RSRP, RSTD for OTDOA and UE Rx-Tx for RTT) are all made in the presence of measurement gaps. During a measurement gap, the UE can expect that the network will not transmit any data and thus the UE can tune itself specifically to measure the PRS. For example, to measure PRS (i.e., DL PRS), the UE will potentially utilize a different bandwidth than the active bandwidth part it is configured with to receive data.

In NR release <NUM>, it has been agreed to specify enhancements to enable measuring the DL PRS without the need for measurement gaps. If the bandwidth part of the UE is wide enough to cover the DL PRS bandwidth, the UE can measure the PRS without requesting measurement gaps. In the RAN1#<NUM>-e meeting, it was agreed that when a downlink channel or another downlink reference signal with higher priority collides with DL PRS measurement/processing, then the UE can drop the DL PRS measurement/processing.

In NR release <NUM>, the positioning procedures are triggered by location request or deferred location request associated with specific events associated with the target UE, i.e., UE availability, area, periodic location, and motion. The positioning measurements are triggered when the UE receives LPP request location information, and/or the gNB receives NRPPa measurement request, and the measurements are carried out as soon as the positioning resources are available and measurement gap are configured (if required for DL positioning methods).

In NR release <NUM>, it has been agreed to enable positioning measurements at a scheduled location time T, which is a further time specified by an external LCS Client, AF or the UE. In RAN procedures, T can be interpreted as a measurement window around T (configured by LMF) based on QoS requirement(s) and available PRS resource(s). When a UE and/or gNB receive a measurement window, they are supposed to perform DL and/or UL measurements with the positioning signals inside that measurement window.

Document "<NPL> pertains to support of on-demand DL PRS. The following observations and proposals were made. Proposal <NUM>: The endorsed PRS Configuration Exchange procedure is used for both LMF (network)-initiated and UE-initiated DL PRS transmission. Proposal <NUM>: the LMF determines a number of PRS configurations, based on a crowdsourcing approach from e.g. different UE LPP measurements reports. The LMF can ask the gNB to set-up or update the PRS transmission with an index to a pre-determined configuration. Observation <NUM>: It is beneficial if the LMF asks the gNB to modify the configuration of an on-going DL PRS transmission. Observation <NUM>: Since RAN3 has defined the PRS Configuration Exchange as class1 procedure it is possible for the gNB to ACK the configuration index, if successful. Proposal <NUM>: Since we do not exchange RAN capabilities over RAN3 interfaces, we can rely on OAM or proprietary signalling during dedicated deployments.

Document "Remaining issues on physical layer procedure for NR positioning", vivo, 3GPP draft R1-<NUM> may be construed to disclose and evaluation of on remaining issues on physical-layer procedures for Rel-<NUM> NR positioning. Inter alia, the following proposals were made. Observation <NUM>: The definition of positioning frequency layer in NR is not the same as in LTE. Observation <NUM>: Such network indicated priority of positioning layer may restrict UE's ability to measure different positioning frequency layer. Proposal <NUM>: Positioning frequency layers in NR are not sorted according to priority. Proposal <NUM>: LMF recommends some PRS resources in high priority to measure while the actual PRS resources to be measured is still decided by the UE. Proposal <NUM>: When a UE is configured in the assistance data of a positioning method with a number of PRS resources beyond its capability (FG <NUM>-<NUM>,<NUM>-<NUM>,<NUM>-<NUM> for AoD, TDOA, MRTT respectively), the UE assumes the DL-PRS Resources in the assistance data are sorted in a decreasing order of measurement priority. Specifically, according to the current RAN2 structure of the assistance data, the following priority is assumed: The resources of the set are divided into M measurement groups. The priority of measurement groups of a PRS resource set are sorted according to the priority order of PRS resource set first, then by the order of TRP, at last followed by the next measurement group of the same PRS resource set. Proposal <NUM>: The sorted PRS resource priority is assumed only within the measurement gap window on the UE side.

It is an object of the present disclosure to obviate or mitigate at least one disadvantage of the prior art.

There are provided systems and methods for configuring periodization of PRS measurements. According to the present disclosure, there are provided methods, computer-readable media, a gNB and an LMF/gNB-CU according to the independent claims. Further developments are set forth in the dependent claims.

In a first aspect there is provided a method performed by an access node. The access node comprises a radio interface and processing circuitry and be configured to receive, from a network node, a configuration request to configure a positioning reference signal (PRS) measurement window for a wireless device. The access node determines whether to configure the PRS measurement window in accordance with a priority associated with the PRS measurement. Responsive to configuring the PRS measurement window in accordance with the priority, the access nodes transmits a configuration response to the network node; and/or responsive to not configuring the PRS measurement window in accordance with the priority, the access node transmits a configuration failure to the network node.

In some embodiments, the access node can determine a priority between data reception and PRS measurement.

In some embodiments, the access node can transmit, to the wireless device, configuration information associated with the PRS measurement window. In some embodiments, the access node can transmit, to the wireless device, an indication of the priority associated with the PRS measurement. In some embodiments, the access node can receive, from the wireless device, an indication that a PRS measurement has been skipped in accordance with the priority.

In another aspect there is provided a method performed by a network node. The network node comprises a radio interface and processing circuitry and be configured to generate configuration information associated with a positioning reference signal (PRS) measurement window. The network node transmits, to an access node, a configuration request to configure the positioning reference signal (PRS) measurement window for a wireless device. The access node receives, from the access node, at least one of: a configuration response indicating that the PRS measurement window has been successfully configured and/or a configuration failure indicating that the PRS measurement window has not been configured.

The network node is a Location Management Function (LMF) or a gNB Control Unit (gNB-CU).

Moreover, the network node receives, from the wireless device, an indication that a PRS measurement has been skipped in accordance with the priority.

In some embodiments, the configuration request includes an indication of the priority associated with the PRS measurement.

In some embodiments, at least one of the configuration request, the configuration response, and the configuration failure messages can be transmitted and/or received via NRPPa signaling.

In some embodiments, at least one of the configuration request, the configuration response, and the configuration failure messages can be transmitted and/or received via F1AP signaling.

In some embodiments, the configuration response indicates that the PRS measurement window has been successfully configured by the access node.

In some embodiments, the configuration failure indicates that the PRS measurement window has not been configured by the access node.

The various aspects and embodiments described herein can be combined alternatively, optionally and/or in addition to one another.

Embodiments of the present disclosure will now be described, by way of example only, with reference to the attached Figures, wherein:.

In the following description, numerous specific details are set forth. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not to obscure the understanding of the description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue experimentation.

Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

<FIG> illustrates an example of a communication system <NUM> in accordance with some embodiments.

In the example, the communication system <NUM> includes a telecommunication network <NUM> that includes an access network <NUM>, such as a radio access network (RAN), and a core network <NUM>, which includes one or more core network nodes <NUM>. The access network <NUM> includes one or more access network nodes, such as network nodes 110A and 110B (one or more of which may be generally referred to as network nodes <NUM>), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes <NUM> facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112A, 112B, 112C, and 112D (one or more of which may be generally referred to as UEs <NUM>) to the core network <NUM> over one or more wireless connections.

The core network <NUM> includes one or more core network nodes (e.g. core network node <NUM>) that are structured with hardware and software components. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Location Management Function (LMF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

Examples of such applications include live and prerecorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable <NUM>, <NUM>, <NUM>, <NUM> standards, or any applicable future generation standard (e.g. <NUM>); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, the UEs <NUM> are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network <NUM> on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network <NUM>. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub <NUM> communicates with the access network <NUM> to facilitate indirect communication between one or more UEs (e.g. UE 112C and/or 112D) and network nodes (e.g. network node 110B). In some examples, the hub <NUM> may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub <NUM> may be a broadband router enabling access to the core network <NUM> for the UEs. As another example, the hub <NUM> may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes <NUM>, or by executable code, script, process, or other instructions in the hub <NUM>. As another example, the hub <NUM> may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub <NUM> may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub <NUM> may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub <NUM> then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub <NUM> acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

The hub <NUM> may have a constant/persistent or intermittent connection to the network node 110B. The hub <NUM> may also allow for a different communication scheme and/or schedule between the hub <NUM> and UEs (e.g. UE 112C and/or 112D), and between the hub <NUM> and the core network <NUM>. In other examples, the hub <NUM> is connected to the core network <NUM> and/or one or more UEs via a wired connection. Moreover, the hub <NUM> may be configured to connect to an M2M service provider over the access network <NUM> and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes <NUM> while still connected via the hub <NUM> via a wired or wireless connection. In some embodiments, the hub <NUM> may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 110B. In other embodiments, the hub <NUM> may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Note that, in the description herein, reference may be made to the term "cell". However, particularly with respect to <NUM>/NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

Returning to the discussion of conventional PRS-based measurements made with measurement gaps, in NR Release <NUM>, it was agreed to specify enhancements to enable measuring the DL PRS without the need for measurement gaps. If the bandwidth part (BWP) of the UE is wide enough to cover the DL PRS bandwidth, the UE can measure the PRS without requesting measurement gap(s). However, collision with the data channels and other downlink reference signals may be an issue to be addressed.

Even though it is agreed that the UE can drop the DL PRS measurement/processing when the DL PRS collides with a DL channel and/or another DL reference signal with higher priority, the UE procedure for the case when such dropping happens is not known. Hence, what procedures a UE performs when a DL PRS measurement/processing is about to be dropped due to DL PRS collision with a DL channel or another DL reference signal with higher priority remains to be solved. It should be noted that the entity which may decide to prioritize the radio resource for certain specific usage may not have all the necessary information. How to configure positioning related priority in radio node remains an issue. Configuration and signaling details of DL PRS priority across different NW entities are currently not known. Hence, how to configure the UE with DL PRS priorities and associated signaling is another open issue to be addressed.

Some embodiments described herein are directed towards the configuration and/or indication of priority of DL PRS to the UE with respect to other colliding DL channels/reference signals; handshaking messages between LMF and serving gNB on the priority of DL PRS; UE procedures when the measurement/processing of DL PRS is dropped due to collision with a DL channel/other DL reference signal with higher priority; and solutions for prioritizing positioning measurement with the use of different windows (measurement gap and positioning measurement window).

In some embodiments, methods to configure positioning measurements priority over other downlink channel reception or other downlink reference signal receptions/measurements are specified. How a gNB considers different input(s) from other network entities or UE(s) to make an informed decision will be described.

In some embodiments, methods have been proposed such that UE understands whether it should prioritize positioning measurements or reception of data.

In some embodiments, methods which facilitate in minimizing the need for asking for measurement gaps to the network from the UE have been provided.

In some embodiments, methods have been proposed such that UE informs the LMF that a measurement/processing of PRS is skipped/dropped due to collision with a DL channel/DL reference signal with higher priority.

In some embodiments, methods for prioritizing positioning measurement with the use of different windows (measurement gap and positioning measurement window) have been specified.

In one embodiment, the LMF can signal a configuration of DL PRS resources with different priorities to the UE via the LPP protocol. For instance, a priority indicator can be included as part of PRS configuration with different values of the priority indicator indicating different priorities (e.g. a priority indicator value of <NUM> indicating a lower priority DL PRS, and a priority indicator value of <NUM> indicating a higher priority DL PRS). For example, the priority indicator can be configured as part of the <NPL>.

The priority indicator sent by the LMF to the UE for each PRS resource can be used to relay what the gNB scheduler has decided. In one embodiment, the gNB can include the priority indicator in the NR Positioning Protocol A (NRPPa) message used to transmit the PRS configuration(s) to the LMF. In another embodiment, the LMF may request, also via NRPPa, the gNB to provide (if the gNB initially did not provide a priority indication of PRS resource(s) explicitly) a specific priority for a given PRS. The gNB can then responds to the LMF with a request denied/granted message related to the request for providing PRS priority.

In some cases, the priority indication can consist of two or more priority levels, and two of these levels can be associated with a timer. When the priority is indicated to the LMF, one priority level is initially used (for example, PRS is set to be of highest priority over data). When the timer expires, the LMF is expected to change the PRS priority to the second associated level (for example, PRS is deprioritized over data).

In some cases, the priority indicator can be configured at the DL PRS resource set level (e.g. as part of NR-DL-PRS-ResourceSet-r16 as defined in the <NPL>) which means that the priority indicated by the priority indicator applies to all of the DL PRS resources in that DL PRS resource set.

In another case, the priority indicator can be configured at the DL PRS resource level (e.g. as part of NR-DL-PRS-Resource-r16 as defined in the <NPL>). In this case, it is possible to configure different DL PRS resources in a given DL PRS resource set with different priorities (e.g. DL PRS resource <NUM> of a DL PRS resource set configured with higher priority and DL PRS resource <NUM> of the DL PRS resource set configured with lower priority).

It should be noted that the priorities of DL PRS discussed above are with respect to DL channels and/or other DL reference signals that may collide with the DL PRS measurement/processing. In one example, a DL PRS with a "higher priority" indicator configured means that the DL PRS shall be measured/processed by the UE over DL channels and/or other DL reference signals that may collide with the DL PRS measurement/processing. A DL PRS with a "lower priority" indicator configured means that the DL PRS measurement/processing shall be dropped (or in other words skipped) by the UE in which case the UE shall prioritize the measurement/reception/decoding of DL channels and/or other DL reference signals that may collide with the DL PRS.

In another embodiment, whether a DL PRS shall be measured/processed or dropped by the UE can depend on both the priority indicated for the DL PRS and a priority indicated for the colliding DL channels and/or other DL reference signals. Note that the priority indicated for the colliding DL channels and/or other DL reference signals may be indicated to the UE from the serving gNB. For instance, this embodiment may cover the following examples:.

It is noted that even though a colliding PDSCH is used in the above examples, this embodiment is not limited to only PDSCH and is applicable to any other colliding DL channels and/or DL reference signals.

In some embodiments, at least three levels of priority can be configured for DL PRS (e.g. higher priority, medium priority, lower priority). In one example, a DL PRS with a higher priority indicator configured means that the DL PRS shall be measured/processed by the UE over DL channels and/or other DL reference signals that may collide with the DL PRS measurement/processing. A DL PRS with a lower priority indicator configured means that the DL PRS measurement/processing shall be dropped (or in other words skipped) by the UE in which case the UE shall prioritize the measurement/reception/decoding of DL channels and/or other DL reference signals that may collide with the DL PRS. In one example, a DL PRS with a medium priority indicator configured means that the UE shall perform the following:.

The above embodiment may be generalized to N levels of priority for DL PRS, where each level of priority can apply to a subset of the DL channels and/or other DL reference signals.

It is noted that collisions between DL channels and/or other DL reference signals with DL PRS measurement/processing in this disclosure may be defined as any one of the following:.

The DL channels in the above embodiments may include, but are not limited to, one or more of: PDCCH, dynamically scheduled PDSCH (PDSCH with dynamic grant scheduled via a DL DCI scrambled with C-RNTI), and semi-persistently scheduled (SPS) PDSCH (downlink semi-persistent transmission configured by the SPS-Config information element in 3GPP TS <NUM> V16.

The other DL reference signals in the above embodiments may include, but are not limited to, one or more of: periodic NZP CSI-RS, aperiodic NZP CSI-RS, semi-persistent NZP CSI-RS, periodic TRS and aperiodic TRS as defined in 3GPP TS <NUM> and 3GPP TS <NUM>.

<FIG> is a signaling diagram illustrating an example embodiment where the LMF <NUM> indicates the configured priority of one or more DL PRS resources to the serving gNB <NUM> via NRPPa.

Step <NUM>: LMF <NUM> indicates the priority of Positioning session to gNB <NUM> via NRPPa signaling based on, for example, quality of service requirements for positioning. The priority can also include the type of positioning session such as regulatory or commercial, for example, or some requirements in terms of ascending or descending order with some number indexing (e.g. <NUM> to <NUM>). In one embodiment, the signaling of this prioritization information can be achieved via incorporating the priority information in existing NRPPa messages defined in Rel-<NUM> version of TS <NUM>. In another embodiment, the signaling can be done by enhancing the PRS Configuration Exchange procedure defined in rel-<NUM> version of TS <NUM>. An example is provided below:.

This message is sent by LMF to request NG-RAN node configuring the PRS transmission.

This IE contains the requested PRS configuration for transmission by the LMF.

In another embodiment, the prioritization can be signaled using one or more new NRPPa messages or can be left to OAM.

Step <NUM>: The gNB <NUM> can use this input to determine what shall be prioritized; whether data (i.e. either dynamically scheduled PDSCH or SPS PDSCH) or any other reference signal over PRS; or whether PRS is prioritized over data channels and reference signal.

Step <NUM>: The gNB <NUM> indicates the priority using an existing field in DCI, an existing field in DCI with one or more codepoints in the field reinterpreted for priority indication, a new field in DCI, a new DCI format, or using MAC control element. The serving gNB <NUM> may also indicate to the UE <NUM> to drop PRS with associated priority above certain number (for example above <NUM>; where priority <NUM> and above may be associated to low priority PRS configurations).

Step <NUM>: In the case where gNB <NUM> prioritizes data or any other reference signal over PRS (i.e. if PRS is not transmitted or UE is asked not to perform PRS measurement but to obtain DL data), the UE <NUM> can skip the PRS measurements in accordance with the prioritization.

In the alternative case, where gNB <NUM> prioritizes PRS over other data or reference signal(s), the UE <NUM> can perform the PRS measurements in accordance with the prioritization.

Step <NUM>: gNB <NUM> indicates the decision to LMF <NUM> using NRPPa. In one embodiment, the response of the gNB's decision related to PRS prioritization can be included in one of the existing NRPPa response messages defined in Rel-<NUM> version of TS <NUM>. In another embodiment, the signaling can be done by enhancing the PRS Configuration Exchange procedure defined in rel-<NUM> version of TS <NUM>. An example provided below:.

This message is sent by NG-RAN node to acknowledge configuring/updating the PRS transmission.

In an alternative embodiment, the signaling can be done via the PRS configuration failure message as shown below:.

This message is sent by NG-RAN node to indicate that it cannot configure the PRS transmission.

In another embodiment, the indication can be signaled using one or more new NRPPa messages or can be left to OAM.

Step <NUM>: The UE can inform the LMF using LPP that the PRS was dropped/skipped. In some embodiments, the signaling can be included as an error. An example is provided below, including indications of no PRS detected and/or PRS measurement skipped:.

The IE NR-DL-TDOA-TargetDeviceErrorCauses is used by the target device to provide NR DL-TDOA error reasons to the location server.

In some embodiments, the signaling can be more explicit, including indication of the deprioritized PRS measurement(s), as in the following example:
<IMG>
<IMG>
<IMG>.

In some embodiments, supplementary information can be signaled over the F1 interface in split-gNB scenario, between a gNB-CU and a gNB-DU, such as signaling new indications over F1AP messages that would be equivalent to the NRPPa messages described in step <NUM> and step <NUM> of <FIG>.

<FIG> is a signaling diagram illustrating an example embodiment related to an overlapping window.

In some other embodiments, the gNB may indicate the configured priority of one or more DL PRS resources to its gNB-DU(s) over F1 interface.

In some other embodiments, the serving gNB may exchange the configured priority of one or more DL PRS resources with its neighbour nodes over Xn interface.

In an alternative embodiment, multiple one-bit DL PRS priority indicators are used to indicate the priority of the DL PRS over other signals and channels. Each one-bit DL PRS priority indicator indicates the DL PRS priority relative to one specific signal or channel, or alternatively to a set of signals and/or channels. As an example, a one-bit DL PRS priority indicator could be defined so that a bit is set to one would indicate that the DL PRS is prioritized while a bit set to zero would indicate that the specific signal or channel, or set of signals and/or channels would be prioritized.

In one embodiment, the one-bit DL PRS priority indicators would be signaled as a bit-string where each bit would correspond to one priority indicator, defining the priority for a specific predefined signal or channel, or set of signals and/or channels.

To give some examples a one-bit DL PRS priority indicator could define the DL PRS priority relative to one of the following signal or channels or sets of signals or channels, or relative to a subset of these:.

In one embodiment, the one-bit DL PRS priority indicators are signaled to the UE by the LMF over LPP.

In one embodiment, the one-bit DL PRS priority indicators are signaled to the UE by the gNB over RRC.

In one embodiment, one or more of the one-bit DL PRS priority indicators are signaled to the UE by the gNB as part of the configuration of the signal or channel to which the DL PRS priority indicator applies. As an example, a one-bit DL PRS priority indicator would be included in the CSI-RS configuration to define prioritization between a specific CSI-RS and DL PRSs.

It is noted that in NR, PDCCH coresets can be located anywhere in a slot. This is useful to reduce latency, e.g. for URLLC. However, with multiple coresets in each slot there may be too little space remaining to fit a DL PRS and to allow UE processing of the DL PRS. To balance latency requirements versus positioning requirements one solution is allow different prioritization for different coresets as described above.

Some of the mechanisms described herein allow the UE to prioritize data channels, control channels, other downlink reference signals and/or positioning measurements. If there any issues in handling both, the network can provide a priority so that UE knows what to prioritize and what to drop. Some embodiments can provide lower positioning latency and even further improved accuracy by focusing on prioritized positioning resources for measurements. The gNB is able to provide efficient prioritization of data/control channels (for instance urgent URLLC data/instructions) and positioning measurements.

<FIG> is a flow chart illustrating a method which can be performed in a wireless device, such as a UE <NUM> as described herein. The method can include:
Step <NUM>: Optionally, the wireless device obtains measurement window configuration information. The configuration information can be received from an access node and/or a network node. In some embodiments, this includes receiving a configuration message (e.g. a LPP message) from a network node, such as LMF <NUM>. The configuration information can include parameters (e.g. start time, end time) associated with a measurement window for performing PRS measurements.

The wireless device can receive further configuration information including at least one resource for measuring one or more reference signal(s) (e.g. PRS) and for deriving positioning measurements. The configuration parameters can include a periodicity, an offset, a starting PRB, a bandwidth, an ending PRB, a starting symbol, a number of consecutive symbols, an end symbol, and/or other configuration parameters defining the position in frequency, time, and/or bandwidth of the reserved resource.

Step <NUM>: The wireless device can receive an indication of priority associated with one or more PRS measurement(s). The indication can be received from an access node, such as gNB <NUM>. The indication can be included in a DCI message received from the access node. In some embodiments, the indication can indicate for the wireless device to prioritize data or other reference signal(s) over PRS.

Step <NUM>: The wireless device can determine to skip one or more PRS measurement(s) in accordance with the indication of priority.

Step <NUM>: Optionally, the wireless device can transmit, to the access node or the network node, a report indicating that the PRS measurement(s) were skipped or not performed.

It will be appreciated that in some embodiments, the wireless device can communicate (e.g. transmit/receive messages) directly with a network node such as location server <NUM>. In other embodiments, messages and signals between the entities may be communicated via other nodes, such as radio access node (e.g. gNB, eNB) <NUM>.

It will be appreciated that one or more of the above steps can be performed simultaneously and/or in a different order. Also, steps illustrated in dashed lines are optional and can be omitted in some embodiments.

<FIG> is a flow chart illustrating a method which can be performed in an access node, such as a gNB <NUM> as described herein. The method can include:.

Step <NUM>: The access node obtains configuration information. The configuration information can be received from a network node such as a location server (LMF). The configuration information can be a configuration request to configure a positioning reference signal (PRS) measurement window for at least one wireless device and can include an indication of priority associated with one or more PRS measurement(s). The configuration information can be received via NRPPa signaling and/or F1AP signaling.

Step <NUM>: The access node determines prioritization of one or more PRS measurement(s) in accordance with the configuration information. In some embodiments, data traffic can be prioritized over PRS. In other embodiments, PRS can be prioritized over other data traffic. In some embodiments, the access node can determine to prioritize PRS measurements within a measurement window.

Step <NUM>: Optionally, the access node transmits an indication of the determined priority to one or more wireless device(s). The access node can signal the priority indication via a DCI message. In some embodiment, the access node can also transmit an indication of priority to a network node, such as LMF <NUM>. The access node can transmit the indication to the network node via a NRPPa message. The indication can indicate that one or more PRS(s) has been deprioritized.

Step <NUM>: The access node transmits a configuration response to the network node. In some embodiments, responsive to configuring the PRS measurement window in accordance with the priority, the access node transmits a configuration response to indicate that the PRS measurement window has been successfully configured for the wireless device. In some embodiments, responsive to not configuring the PRS measurement window in accordance with the priority, the access node transmits a configuration failure to indicate that the PRS measurement window has not been configured for the wireless device. The configuration response(s) can be transmitted via NRPPa signaling and/or F1AP signaling.

It will be appreciated that in some embodiments, the access node can communicate (e.g. transmit/receive messages) directly with a target wireless device <NUM>. In other embodiments, messages and signals between the entities may be communicated via other nodes, such as other radio access node (e.g. gNB, eNB) <NUM>.

<FIG> is a flow chart illustrating a method which can be performed in a network node, such as a location server (e.g. LMF <NUM>) as described herein. The method can include:
Step <NUM>: The network node generates configuration information. The configuration information can include measurement window configuration information and/or an indication of priority associated with one or more PRS measurement(s).

In some embodiments, the configuration information can further include at least one resource for measuring one or more reference signal(s) (e.g. PRS) and for deriving positioning measurements. The configuration of resource(s) can include a periodicity, an offset, a starting PRB, a bandwidth, an ending PRB, a starting symbol, a number of consecutive symbols, an end symbol, and/or other configuration parameters defining the position in frequency, time, and/or bandwidth of the reserved resource.

Step <NUM>: The network node transmits the generated configuration information. The configuration information can be transmitted to an access node and/or a wireless device. The information can be transmitted in a configuration request message to configure the positioning reference signal (PRS) measurement window for at least one wireless device. The configuration request can include an indication of the priority associated with the PRS measurement. Configuration information can be transmitted to the access node via NRPPa signaling and/or F1AP signaling and transmitted to the wireless device via LPP signaling.

Step <NUM>: The network node can receive, from the access node and/or the wireless device, a configuration response. The configuration response can indicate that the PRS measurement window has been successfully configured for the wireless device or, alternatively, indicate that the PRS measurement window has not been configured. In some embodiments, this can include an indication that one or more PRS/PRS measurement has been deprioritized. The configuration response(s) can be received via NRPPa signaling and/or F1AP signaling.

Step <NUM>: Optionally, the network node can receive, from the access node and/or the wireless device, an indication that one or more PRS measurement has skipped or not performed.

It will be appreciated that in some embodiments, the network node can communicate (e.g. transmit/receive messages) directly with a target wireless device <NUM>. In other embodiments, messages and signals between the entities may be communicated via other nodes, such as radio access node (e.g. gNB, eNB) <NUM>.

<FIG> shows a UE <NUM>, which may be an embodiment of the UE <NUM> of <FIG> in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Nonlimiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE <NUM> shown in <FIG>.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone's speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

<FIG> shows a network node <NUM>, which may be an embodiment of the access node <NUM> or the core network node <NUM> of <FIG>, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.

Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as <FIG> and <FIG>, such that the descriptions thereof are generally applicable to the corresponding components of host <NUM>.

Applications <NUM> (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment <NUM> to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware <NUM> includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers <NUM> (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs <NUM>), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer <NUM> may present a virtual operating platform that appears like networking hardware to the VMs <NUM>.

NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

Hardware <NUM> may be implemented in a standalone network node with generic or specific components. Hardware <NUM> may implement some functions via virtualization. Alternatively, hardware <NUM> may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration <NUM>, which, among others, oversees lifecycle management of applications <NUM>. In some embodiments, hardware <NUM> is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system <NUM> which may alternatively be used for communication between hardware nodes and radio units.

<FIG> shows a communication diagram of a host <NUM> communicating via a network node <NUM> with a UE <NUM> over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112A of <FIG> and/or UE <NUM> of <FIG>), network node (such as network node 110A of <FIG> and/or network node <NUM> of <FIG>), and host (such as host <NUM> of <FIG> and/or host <NUM> of <FIG>) discussed in the preceding paragraphs will now be described with reference to <FIG>.

One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve the handling of colliding signals and/or channels and thereby provide benefits such as improving measurement latency and bypassing the measurement gap request procedure to improve positioning quality.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection <NUM> between the host <NUM> and UE <NUM>, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host <NUM> and/or UE <NUM>. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection <NUM> passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection <NUM> may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node <NUM>. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host <NUM>. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection <NUM> while monitoring propagation times, errors, etc..

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Claim 1:
A method performed by a gNB (<NUM>), the method comprising:
receiving (<NUM>, <NUM>, <NUM>), from a Location Management Function, LMF/gNB Control Unit, gNB-CU, (<NUM>), a configuration request to configure a positioning reference signal, PRS, measurement window for a wireless device (<NUM>);
determining (<NUM>, <NUM>, <NUM>) whether to configure the PRS measurement window in accordance with a priority associated with the PRS measurement; and
responsive to configuring the PRS measurement window in accordance with the priority, transmitting (<NUM>, <NUM>, <NUM>) a configuration response to the LMF/gNB-CU to confirm successful configuration of the PRS measurement window, wherein the configuration response includes an indication that a PRS measurement has been skipped.