Patent Description:
The present disclosure generally relates to wireless communications and wireless communication networks.

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.

Note <NUM>: The gNB 110B and ng-eNB 110A may not always both be present.

Note <NUM>: When both the gNB 110B and ng-eNB 110A are present, the NG-C interface is 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:
Methods already in LTE and enhanced in NR:.

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

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

A new DL reference signal, the NR DL PRS was specified in NR Rel. A benefit of this signal in relation to the LTE DL PRS is the increased bandwidth, configurable from <NUM> to <NUM> RBs, which gives a big improvement in TOA accuracy. The NR DL PRS can be configured with a comb factor of <NUM>, <NUM>, <NUM> or <NUM>. Comb-<NUM> allows for twice as many orthogonal signals as the comb-<NUM> LTE PRS. Beam sweeping is also supported on NR DL PRS in Rel-<NUM>.

<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.

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

<NUM>, enhancements of the NR UL SRS were specified. <NUM> NR SRS for positioning allows for a longer signal, up to <NUM> symbols (compared to <NUM> symbols in Rel. <NUM>), and a flexible position in the slot (only last six symbols of the slot can be used in Rel. It also allows for a staggered comb RE pattern for improved TOA measurement range and for more orthogonal signals based on comb offsets (comb <NUM>, <NUM> and <NUM>) and cyclic shifts. The use of cyclic shifts longer than the OFDM symbol divided by the comb factor is, however, not supported by Rel. <NUM> despite that this is the main advantage of comb-staggering at least in indoor scenarios. Power control based on neighbor cell SSB/DL PRS is supported as well as spatial QCL relations towards a CSI-RS, an SSB, a DL PRS or another SRS.

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 gnodeB, which in turns forward appropriate SRS configuration parameters to the LMF upon request.

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.

Document <CIT> (and its post-published patent family member <CIT>) may be construed to disclose a method for configuring a positioning reference signal resource, a method for configuring a measurement gap, and a related device. The method includes: determining a resource position of a PRS within a BWP based on a start PRB position of a PRS resource and the number of PRBs; and performing measurement on the resource position.

Document "<NPL> may be construed to disclose the summary of the solutions to improve positioning latency for DL and DL+UL methods, in the email discussion assignment in RAN1#<NUM>-e. Inter alia, it was proposed that PRS measurement without Measurement Gaps (MGs) subject to UE capability is supported for latency reduction in Rel-<NUM> at least when the DL PRS is [from the serving cell and] inside the active Downlink (DL) Band-Width Part (BWP).

Document <CIT> constitutes prior art under Art. <NUM>(<NUM>) EPC and may be construed to disclose methods and apparatuses for searcher resource coordination between NR mobility based measurement and LTE (E-UTRA) PRS based measurement without measurement gap in EN-DC mode or NE-DC mode. There are also provided for searcher resource coordination between NR PRS measurement and LTE (E-UTRA) PRS measurement without measurement gap in EN-DC mode or NE-DC mode. There further are searcher resource coordination between NR or LTE (E-UTRA) PRS measurement and NR mobility measurement without measurement gap in EN-DC mode or NE-DC mode.

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

There are provided methods for configuring reserved resources for positioning purposes. According to the present disclosure, there are provided methods, computer-readable media, a wireless device and an access node 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 a wireless device. The wireless device can comprise a radio interface and processing circuitry and be configured to receive a configuration message indicating one or more reserved resources, wherein the wireless device can receive downlink data and perform positioning reference signal (PRS) measurements in a reserved resource without a configured measurement gap. The wireless device determines that PRS measurement is prioritized in the reserved resource; and measures at least one PRS in the reserved resource.

In another aspect there is provided a method performed by a network node such as an access node. The access node can comprise a radio interface and processing circuitry and be configured to generating configuration information including one or more reserved resources, wherein a wireless device can receive downlink data and perform positioning reference signal (PRS) measurements in a reserved resource without a configured measurement gap. The access node transmits, to the wireless device, a configuration message indicating the one or more reserved resources. The access device transmits, to the wireless device, at least one PRS in the reserved resource.

In some embodiments, the configuration message indicates at least one of: a frame number, a subframe number, a slot number, and/or a symbol number where the reserved resource starts. In some embodiments, the configuration message indicates at least one of: a length and/or a periodicity of the reserved resource. In some embodiments, the configuration message indicates a priority between the downlink data reception and the PRS measurement in the reserved resource.

In some embodiments, the downlink data is one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), and/or a Channel State Information Reference Signal (CSI-RS).

The wireless device further receives an activation message, transmitted by the access node, indicating to activate at least one of the one or more reserved resources. In some embodiments, the activation message is a Medium Access Control (MAC) control element (CE) and/or a Downlink Control Information (DCI).

In some embodiments, the wireless device further receives downlink data, transmitted by the access node, in resources outside of the reserved resource.

In some embodiments, the access node further receives, from a network node, a request to configure the one or more reserved resources. The request can be received via NRPPa signaling.

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:.

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description.

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 of the UE is wide enough to cover the DL PRS bandwidth, the UE can measure the PRS without requesting measurement gaps. However, collision with the data channels and other downlink reference signals is an issue needed to be addressed.

Some solutions have been proposed for handling collision of PRS with data channels and other downlink reference signals. In these solutions, configurable priority indicators are introduced for different data channels and other downlink reference signals. Depending on the value of the indicated priority indicator, the UE would either measure/process the PRS to derive positioning measurements or measure/process/decode data channels and other downlink reference signals. When the UE measures/processes the PRS based on the indicated priority, the UE drops the data channels and other downlink reference signals. Conversely, when the UE measures/processes/decodes data channels and other downlink reference signals based on the indicated priority, the UE drops the PRS.

In these solutions, only one of the following items (i.e., the item with the higher indicated priority) is performed by the UE based on the indicated priority:.

The item that is not performed (i.e., the item with the lower indicated priority) is dropped and therefore not processed by the UE.

In some I-IoT use cases, the network may involve ultra-reliable low latency communication (URLLC) support with low latency positioning as an add-on feature. In this scenario, prioritizing only PRS may not make sense. Prioritizing PRS at the expense of dropping URLLC related data channels or reference signals will be expensive since it will hurt the URLLC performance/latency targets. On the other hand, prioritizing URLLC data channels and/or reference signals at the expense of dropping PRS measurements will affect the low latency positioning target. Hence, it is an issue of how to simultaneously ensure URLLC support and low latency positioning.

Certain aspects of this disclosure and their embodiments may provide solutions to these or other challenges. In some embodiments, configuration of reserved resources for PRS are configured from the serving gNB to the UE. If the reserved resources for PRS are periodic, then the reserved resources for PRS can be configured to the UE via RRC signaling. If the reserved resources for PRS are semi-persistent, then the reserved resources for PRS can be activated to the UE via MAC CE signaling. In addition, candidate reserved resource patterns for PRS that may be activated can be configured to the UE via RRC signaling.

If the reserved resources for PRS are aperiodic, then the reserved resources for PRS can be triggered to the UE via DCI signaling. In addition, candidate reserved resource patterns for PRS that may be triggered can be configured to the UE via RRC signaling.

The serving gNB can send data and/or other reference signals in downlink to the UE, wherein the resources allocated to the data and/or other reference signals are resource mapped around the reserved resource(s) for PRS.

The UE can receive one or more DL PRSs in the reserved resources for DL PRS without the need for measurement gaps.

The UE can measure the DL PRSs in the reserved resources and the data/other reference signals in the resources that are mapped around the reserved resources.

The UE can perform data decoding and positioning measurements using DL PRS measurements in a slot. Neither the DL PRS nor data are dropped by the UE.

The UE can perform measurements on other reference signals and positioning measurements using DL PRS measurements in a slot. Neither the DL PRS nor the other reference signal is dropped by the UE.

In other embodiments, the configuration of reserved resources for DL PRS can be performed by the LMF to the UE via LPP signaling. In these alternative embodiments, the LMF can also signal the reserved resources for DL PRS to the serving gNB via NRPPa signaling.

In one embodiment, a reserved resource is defined which is to be used for measuring DL PRS and deriving positioning measurements. The resources for data channels such as PDSCH and PDCCH can be mapped around the reserved resource for DL PRS. Similarly, the resources for other reference signals, such as CSI-RS, can be mapped around the reserved resource. The configuration of reserved resource for measuring DL PRS may include one or more of the following:.

In one embodiment, the configuration parameters defining the position in frequency and the bandwidth of the reserved resource can be optional and, if they are not present, this indicates that the reserved resource extends over the full system bandwidth.

<FIG> shows examples illustrating PDSCH resource mapping around reserved resource for PRS. In <FIG>, the reserved resource for PRS has a starting symbol of <NUM> within the slot, and a symbol length of <NUM>. The bandwidth of the reserved resource is given by RBReserved. As shown in the figure, PDSCH is scheduled in the same slot from symbols <NUM> to <NUM> except for symbol <NUM> which is allocated for the reserved resource for PRS. In other words, the resource for PDSCH is "mapped around" the reserved resource for PRS. Hence, the reserved resource for PRS can also be considered a PDSCH rate matching resource. In the slot which is shown in <FIG>, the UE receives and decodes PDSCH while performing PRS measurement(s) in the same slot. The PRSs are measured in the reserved resource (i.e., symbol <NUM>) and are used to derive positioning measurements (e.g., PRS RSRP, RSTD for OTDOA, and/or UE Rx-Tx for RTT). Since the UE can decode PDSCH and perform positioning measurements, neither the PDSCH nor the PRS is dropped in this embodiment which is beneficial for use cases that involve URLLC support with low latency positioning. Note that the bandwidth of the reserved resource for PRS is shown to be larger than the scheduling bandwidth of the PDSCH in <FIG>. However, this embodiment is non-limiting and can also include the case where the bandwidth of the reserved resource for PRS is smaller than the scheduled bandwidth of the PDSCH. In some embodiments, the bandwidth of the reserved resource for PRS is same as the bandwidth of the active bandwidth part of the UE. In an alternative embodiment, the bandwidth of the reserved resource for PRS can be larger than the bandwidth of the active bandwidth part of the UE.

In <FIG>, the reserved resource for PRS has a starting symbol of <NUM> within the slot, and a symbol length of <NUM>. As shown in the figure, PDSCH is scheduled in the same slot from symbols <NUM> to <NUM> except for symbols <NUM>-<NUM> which are allocated for the reserved resource for PRS. In the slot which is shown in <FIG>, the UE receives and decodes PDSCH while performing PRS measurement(s) in the same slot. The PRSs are measured in the reserved resource (i.e., symbols <NUM>-<NUM>) and are used to derive positioning measurements (e.g., PRS RSRP, RSTD for OTDOA, and/or UE Rx-Tx for RTT).

<FIG> shows examples illustrating resource mapping of CSI-RS around reserved resource for PRS. In <FIG>, the reserved resource for PRS has a starting symbol of <NUM> within the slot, and a symbol length of <NUM>. As shown in the figure, a <NUM>-symbol long CSI-RS is received in the same slot in symbols <NUM>, <NUM>, <NUM> and <NUM>. Note that CSI-RS is not received in symbol <NUM> which is allocated for the reserved resource for PRS. In other words, the resource for CSI-RS is mapped around the reserved resource for PRS. In the slot which is shown in <FIG>, the UE measures the CSI-RS and computes corresponding CSI while performing PRS measurement(s) in the same slot. The PRSs are measured in the reserved resource (i.e., symbol <NUM>) and are used to derive positioning measurements (e.g., PRS RSRP, RSTD for OTDOA, and/or UE Rx-Tx for RTT). Since the UE can measure CSI-RS, compute CSI, and perform positioning measurements, neither the CSI-RS nor the PRS is dropped in this embodiment which is beneficial for use cases that involve urgent CSI (e.g., CSI for URLLC) along with support for low latency positioning. Note that although the bandwidth of the reserved resource for PRS is shown to be larger than the bandwidth of the CSI-RS (which is denoted by RBCSI-RS) in <FIG>, this embodiment is non-limiting and can include the case where the bandwidth of the reserved resource for PRS is smaller than the bandwidth of the CSI-RS.

In <FIG>, the reserved resource for PRS has a starting symbol of <NUM> within the slot, and a symbol length of <NUM>. As shown in the <FIG> different CSI-RS resources (e.g., CSI-RSs <NUM>, <NUM>, <NUM>, and <NUM>) which belong to the same NZP CSI-RS resource set (3GPP TS <NUM>) is received in the same slot in symbols <NUM>, <NUM>, <NUM> and <NUM>. These CSI-RS resources may be transmitted with the same or different downlink spatial domain transmission filters and can be used for identifying the best spatial domain filters (e.g., via L1-RSRP (layer <NUM> RSRP) reporting as defined in 3GPP TS <NUM>). Note that a CSI-RS is not received in symbol <NUM> which is allocated for the reserved resource for PRS. In other words, the CSI-RS resources corresponding the NZP CSI-RS resource set are mapped around the reserved resource for PRS. In the slot which is shown in <FIG>, the UE measures the CSI-RS(s) and computes, for instance, L1-RSRP measurements while performing PRS measurement(s) in the same slot. The PRSs are measured in the reserved resource (i.e., symbol <NUM>) and are used to derive positioning measurements (e.g., PRS RSRP, RSTD for OTDOA, and/or UE Rx-Tx for RTT). Since the UE can measure CSI-RS, compute L1-RSRP, and perform positioning measurements, neither the CSI-RS nor the PRS is dropped in this embodiment which is beneficial for use cases that involve urgent best beam identification (e.g., L1-RSRP reporting for URLLC) along with support for low latency positioning.

In some embodiments, the reserved resource for PRS defined for measuring DL PRS are periodic in the time domain. Hence, the reserved resource configuration contains a periodicity (defined in terms of slots) and a slot offset. A reserved resource occurs every Tperiod slots with a slot offset of Toffset.

In other embodiments, the reserved resource for PRS may be configured to the UE but is aperiodically triggered via a DCI. The reserved resource for PRS is only present in a slot which is indicated via DCI. Since a common use case would be to map the resources of dynamically scheduled (via DCI) PDSCH around reserved resources for PRS, in some embodiments, the resourced resource for PRS can be triggered by the downlink DCI (e.g., DCI formats 1_1 and 1_2) that schedules the PDSCH.

In another embodiment, the reserved resource for PRS may be configured to the UE but is activated semi-persistently either via MAC CE or DCI. The semi-persistently activated reserved resource for PRS has a periodicity Tperiod slots and a slot offset of Toffset. Once the semi-persistent reserved resource for PRS is activated, the reserved resource occurs every Tperiod slots with a slot offset of Toffset until it is deactivated. The deactivation of the semi-persistent reserved resource can be performed via a second MAC CE or DCI, which is different from the activating MAC CE or DCI.

In some embodiments, PRS transmissions from multiple TRPs can be received by the UE within the same reserved resource for PRS. For instance, the PRSs transmitted from TRP1 and TRP2 can be multiplexed in the same symbol and separated by different comb offset values. In one embodiment, TRP1 and TRP2 may both belong to the same serving cell. In some other cases, at least one of TRP1 and TRP2 may belong to a non-serving cell (e.g. neighbouring cell).

Although the reserved resources for DL PRS are shown on symbol level in the above embodiments, the reserved resources may be also defined at slot level or sub-slot level. The sub-slot is defined here as a grouping of multiple symbols within a slot. When the reserved resources for DL PRS are defined at slot level or sub-slot level, data and other reference signals from the serving gNB are resource mapped around these reserved resources for DL PRS.

<FIG> is a signaling diagram illustrating example embodiment where the serving gNB <NUM> configures the UE <NUM> through RRC signaling with reserved resources for DL PRS.

Step <NUM>: The LMF sends a recommended configuration of reserved resource(s) for DL PRS to the serving gNB over NRPPa.

Step <NUM>: The serving gNB can send a confirmation of the configuration of reserved resource(s) for DL PRS to the LMF over NRPPa.

Step <NUM>: The serving gNB configures the UE with reserved resources for DL PRS over RRC signaling.

Step <NUM>: The serving gNB triggers/activates the reserved resources for DL PRS for the UE with a DCI. Note that this step is present only when a DCI triggered (e.g., aperiodic) reserved resource for DL PRS has been configured. When reserved resources for DL PRS are periodic or semi-persistent, this step may not be needed.

Step <NUM>: The serving gNB activates the reserved resources for DL PRS for the UE with a MAC CE. Note that this step is present only when a semi-persistent reserved resource for DL PRS has been configured. When reserved resources for DL PRS are periodic or aperiodic, this step may not be needed.

Step <NUM>: The serving gNB sends data to the UE with PDSCH resource mapped around the reserved resources for DL PRS and the UE receives data over PDSCH resource mapped around the reserved resources for DL PRS.

<FIG> is a signaling diagram illustrating an example embodiment where the LMF <NUM> configures the UE <NUM> through LPP signaling with reserved resources for DL PRS.

Step <NUM>: The LMF configures the UE with reserved resources for DL PRS over LPP signaling.

Step <NUM>: The LMF sends the reserved resource configuration for the UE to the serving gNB over NRPPa signaling.

Step <NUM>: The gNB triggers/activates the reserved resources for DL PRS for the UE with a DCI. Note that this step is present only when a DCI triggered (e.g., aperiodic) reserved resource for DL PRS has been configured. When reserved resources for DL PRS are periodic or semi-persistent, this step may not be needed.

Step <NUM>: The serving gNB sends data to the UE with PDSCH resource mapped around the reserved resources for DL PRS, and the UE receives data over PDSCH resource mapped around the reserved resources for DL PRS.

Selection of reserved resources for DL PRS.

The LMF can determine what reserved resource(s) for DL PRS configuration to configure the UE with/recommend to the serving gNB based on, for example:.

In some embodiments the LMF selects the reserved resources for DL PRS to cover all DL PRS resources/resource sets the UE is configured to perform measurements on.

In some embodiments the LMF selects the reserved resources for DL PRS to cover all DL PRS resources/resource sets the UE is configured to utilize for positioning measurements (as indicated, for example, in the nr-SelectedDL-PRS-IndexList-r16 IE in assistance data) plus some extra resource before and/or after these resources. In some embodiments, the amount (e.g. number of OFDM symbols before and after the resources covering the DL PRS resources) of extra resources configured are based on UE capabilities. The extra resources are configured to give UE the needed time to process the measured DL PRSs in the reserved resource for DL PRS.

In another embodiment, reserved resources are defined in time domain, where one slot is reserved for PRS and another slot is used for CSI-RS. Further, the beam sweeping is designed in such a way that the beam sweeping is based upon PRS transmission from 1st beam and the 2nd beam is based upon CSI-RS. This can be done such that the antenna port transmitting DL-PRS is muted while the antenna port transmitting CSI-RS is enabled in alternate varying pattern so that UE obtains CSI-RS and DL-PRS in alternate varying fashion. UE is informed of the alternating pattern between two different RSs by configurations from LPP and/or RRC. In another embodiment, the CSI-RS and DL-PRS Resources are time multiplexed. That is, resources are shared in time domain such that they occur in alternate pattern or pattern such as <NUM>, where the first <NUM> slots are used for CSI-RS and another <NUM> slots are used for PRS reserved resources. In some cases, even the beam sweeping pattern as mentioned above can be depicted with pattern such as <NUM>; where beam sweeping of first <NUM> beams are based upon CSI-RS and last <NUM> are based upon PRS.

According to some of embodiments described herein, the UE can perform PDSCH/PDCCH decoding and perform positioning measurements with low latency without the need for measurement gaps. One potential advantage is the UE can measure other reference signals and perform positioning measurements with low latency without the need for measurement gaps. Hence, the embodiments described herein can help ensure simultaneous URLLC support and low latency positioning.

<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:.

The configuration information can include at least one reserved resource for measuring one or more reference signal(s) (e.g. PRS) and for deriving positioning measurements. The configuration of the reserved resource(s) can include a length, 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.

In some embodiments, the configuration information can indicate a priority between downlink data reception and PRS measurement in the reserved resource. The wireless device can determine that PRS measurement is prioritized in the reserved resource in accordance with the configuration information.

In some embodiments, the resources for data channels (e.g. PDSCH, PDCCH) and/or other reference signals (e.g. CSI-RS) can be mapped around the reserved resource(s) allocated for the PRS as has been described herein.

Step <NUM>: Optionally, the wireless device can receive a trigger and/or an activation for a reserved resource. In some embodiments, the wireless device can receive a trigger for a configured aperiodic reserved resource. The trigger can be a DCI message received from the access node. In some embodiments, the wireless device can receive an activation for a configured semi-persistent reserved resource. The activation can be a MAC CE message received from the access node.

Step <NUM>: The wireless device performs positioning measurements in accordance with the received configuration information and reserved resource(s). In some embodiments, the wireless device can perform positioning measurements without requesting measurement gap. This can include measuring at least one PRS in the reserved resource. In some embodiments, the wireless device can determine an estimated position of the wireless device in accordance with the positioning measurements.

Step <NUM>: Optionally, the wireless device can transmit, to the access node or the network node, a positioning response/report. The positioning response can include an estimated position, positioning measurements, and/or other positioning related information. The positioning response can be based on positioning actions performed by the wireless device in accordance with the configuration information transmitted by the access node or network node and/or the exchanged capability information.

Step <NUM>: Optionally, the wireless device can receive data, from the access node, on one or more resource(s) that are mapped around the reserved resource for positioning. For example, the wireless device can receive data on a PDSCH or PDDCH resource that does not overlap with the reserved resource for PRS.

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:.

In some embodiments, the access node can configure resources for data channels (e.g. PDSCH, PDCCH) and/or other reference signals (e.g. CSI-RS) associated with the wireless device to be mapped around the reserved resource(s) allocated for the PRS, in accordance with the received configuration information.

Step <NUM>: The access node transmits configuration information indicating one or more reserved resources. The configuration information can be transmitted to a wireless device. In some embodiments, this includes transmitting a configuration message (e.g. an RRC message, a MAC CE message and/or a DCI message). The configuration information can indicate that PRS measurement is prioritized in the reserved resource.

Step <NUM>: Optionally, the access node can transmit a trigger and/or an activation for a reserved resource. In some embodiments, the access node can transmit a trigger for a configured aperiodic reserved resource. The trigger can be a DCI message transmitted to the wireless device. In some embodiments, the access node can transmit an activation for a configured semi-persistent reserved resource. The activation can be a MAC CE message transmitted to the wireless device.

Step <NUM>: Optionally, the access node can transmit, to the wireless device, at least one PRS in the reserved resource, and/or data on one or more resource(s) that are mapped around the reserved resource(s) for positioning. For example, the access node can transmit data on a PDSCH or PDDCH resource that does not overlap with the reserved resource for PRS.

Step <NUM>: Optionally, the access node can receive, from the wireless device, a positioning response/report. The positioning response can include an estimated position, positioning measurements, and/or other positioning related information. The positioning response can be based on positioning actions performed by the wireless device in accordance with the configuration information transmitted by the access node and/or the exchanged capability information. In some embodiments, the access node can determine an estimated position of the wireless device in accordance with the positioning response.

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:.

In some embodiments, the network node can determine the reserved resource(s) for positioning based on one or more of: wireless device capabilities, the resources/resource sets the wireless device is configured to utilize for positioning measurements, a serving cell of the wireless device, and/or a position of the wireless device.

In some embodiments, the network node can generate the reserved resource(s) to include extra resources as has been described herein.

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. Configuration information can be transmitted to the access node via NRPPa signaling and transmitted to the wireless device via LPP signaling.

Step <NUM>: Optionally, the network node can receive, from the access node or the wireless device, a positioning response/report. The positioning response can include an estimated position, positioning measurements, and/or other positioning related information. The positioning response can be based on positioning actions performed by the wireless device in accordance with the configuration information transmitted by the access node and/or the exchanged capability information. In some embodiments, the network node can determine an estimated position of the wireless device in accordance with the positioning response.

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. Non-limiting 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 wireless device (<NUM>, <NUM>), the method comprising:
receiving (<NUM>) a configuration message indicating one or more reserved resources, wherein the wireless device can both receive downlink data channels and other reference signals and perform positioning reference signal, PRS, measurements in the reserved resources without a configured measurement gap;
receiving (<NUM>) an activation message indicating to activate at least one of the reserved resources;
determining that PRS measurement is prioritized in the activated reserved resource; and
measuring (<NUM>) at least one PRS in the activated reserved resource.