CONFIGURING PRIORITY FOR WIRELESS POSITIONING SIGNALS

TECHNICAL FIELD

Embodiments of the present disclosure are directed to wireless communications and, more particularly, to configuring priority for wireless positioning signals.

BACKGROUND

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Positioning has been a topic in Long Term Evolution (LTE) standardization since Release 9 of the Third Generation Partnership Project (3GPP). The primary objective was initially to fulfill regulatory requirements for emergency call positioning but other use cases like positioning for industrial Internet of things (I-IoT) are becoming important. Positioning in New Radio (NR) is supported, e.g., by the architecture illustrated in FIGURE 1.

FIGURE 1 is a block diagram illustrating next generation radio access network (NG- RAN) Release 15 location services (LCS) protocols. The location management function (LMF) is the location node in NR. There are also interactions between the location node and the gNodeB via the NR Positioning Protocol A (NRPPa). The interactions between the gNodeB and the device is supported via the Radio Resource Control (RRC) protocol, while the location node interfaces with the User Equipment (UE) via the LTE Positioning Protocol (LPP). LPP is common to both NR and LTE. While FIGURE 1 illustrates both a gNB and an ng-eNB, both may not always be present. Further, when both the gNB and the ng-eNB are present, the NG- C is generally only present for one of them.

The legacy LTE standards support the following techniques. Enhanced Cell ID (E-CID) is essentially cell ID information to associate a wireless device to the serving area of a serving cell and additional information to determine a finer granularity position. Assisted Global Navigation Satellite System (GNSS) uses GNSS information retrieved by the wireless device and assistance information provided to the device from Evolved Serving Mobile Location Center (E-SMLC). Using OTDOA (Observed Time Difference of Arrival), a wireless device estimates the time difference of reference signals from different base stations and sends the results to the E-SMLC for multi-lateration. Using UTDOA (Uplink TDOA), a wireless device transmits a specific waveform that is detected by multiple location measurement units (e.g., an eNB) at known positions. The measurements are forwarded to E-SMLC for multi-lateration.

In NR Release 16, a number of positioning features were specified including reference signals, measurements, and positioning methods. The reference signals include a new downlink (DL) reference signal, the NR DL PRS (Positioning Reference Signal). The main benefit of the NR DL PRS signal in relation to the LTE DL PRS is the increased bandwidth, configurable from 24 to 272 resource blocks (RBs), which provides a significant improvement in time of arrival (TO A) accuracy. The NR DL PRS can be configured with a comb factor of 2, 4, 6 or 12. Comb- 12 enables twice as many orthogonal signals as the comb-6 LTE PRS. Beam sweeping is also supported on NR DL PRS in Rel-16.

NR Release 16 also specifies a new uplink (UL) reference signal based on the NR UL Sounding Reference Signal (SRS) and is referred to as “SRS for positioning”. The Release 16 NR SRS for positioning facilitates a longer signal, up to 12 symbols (compared to 4 symbols in Release 15 SRS), and a flexible position in the slot (only last six symbols of the slot can be used in Release 15 SRS). The NR SRS for positioning also facilitates a staggered comb resource element (RE) pattern for improved TOA measurement range and for more orthogonal signals based on comb offsets (comb 2, 4 and 8) and cyclic shifts. The use of cyclic shifts longer than the orthogonal frequency division Multiplexing (OFDM) symbol divided by the comb factor is, however, not supported by Release 16 despite that this is the main advantage of comb- staggering at least in indoor scenarios. Power control based on neighbor cell synchronization signal block (SSB)/DL PRS is supported as well as spatial quasi-colocation (QCL) relations towards a channel state information reference signal (CSI-RS), an SSB, a DL PRS, or another SRS.

NR Release 16 positioning techniques include NR positioning methods already in LTE and enhanced in NR as well as methods newly introduced in NR. The NR positioning methods supported in LTE and enhanced in NR include: DL TDOA (Downlink TDOA), E-CID, RAT independent methods (based on non-3GPP sensors such as GPS, pressure sensors, Wifi signals, Bluetooth, etc.), and UL TDOA (Uplink TDOA). The methods newly introduced in NR include: Multicell RTT, where the LMF collects RTT (round trip time) measurement as the basis for multi-lateration, and DL angle of departure (AoD) and UL angle of arrival (AoA), where multi-lateration is done using angle and power (RSRP) measurements.

NR Release 16 positioning includes measurements. NR Release 16 includes the following UE measurements: DL Reference Signal Time Difference (RSTD), facilitating, e.g., DL TDOA positioning; Multi cell UE Rx-Tx Time Difference measurement, facilitating multi cell round trip time (RTT) measurements; and DL PRS Reference Signal Receive Power (RSRP). NR Release 16 includes the following gNB measurements: Uplink Relative Time of Arrival (UL-RTOA), useful for UL TDOA positioning; gNb Rx-Tx time difference, useful for multi cell RTT measurements; UL SRS-RSRP; and Angle of Arrival (AoA) and Zenith angle of Arrival (ZoA).

NR Release 16 positioning includes signal configurations. In NR Release 16, the DL PRS is configured by each cell separately, and the location server (i.e., 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 turn forwards appropriate SRS configuration parameters to the LMF upon request.

Rel-16 NR DL PRS is organized in a 3 -level hierarchy that includes the PRS frequency layer, PRS resource set, and the PRS resource. The PRS frequency layer gathers PRS resource sets from (potentially) multiple base stations that have particular parameters in common. If two PRS resource sets are in the same frequency layer, they operate in the same band with the same subcarrier spacing, have the same comb factor, and have the same starting PRB and bandwidth.

A PRS Resource set: corresponds to a collection of PRS beams (resources) that all originate from the same transmission and reception point (TRP). All resources in the same set have the same comb factor. A PRS resource corresponds to a beam transmitting the PRS.

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 entire system bandwidth. The set of REs used for CSI-RS transmission is referred to as a 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 a channel. Up to 32 (i.e. N _tx = 32) antenna ports are supported in NR and thus 32 CSI-RS signals can be configured for a UE.

NR supports the three types of CSI-RS transmissions, periodic, aperiodic, and semi- persistent. For periodic CSI-RS Transmission, CSI-RS is transmitted periodically in certain subframes or slots. This CSI-RS transmission is semi-statically configured using parameters such as CSI-RS resource, periodicity and subframe or slot offset similar to LTE.

Aperiodic CSI-RS transmission is a one-shot CSI-RS transmission that occurs in any subframe or slot. One-shot means that CSI-RS transmission only happens once per trigger. The CSI-RS resources (i.e., the resource element locations which consist of subcarrier locations and OFDM symbol locations) for aperiodic CSI-RS are semi-statically configured. The transmission of aperiodic CSI-RS is triggered by dynamic signaling through PDCCH. The triggering may also include selecting a CSI-RS resource from multiple CSI-RS resources.

Semi-persistent CSI-RS (SP CSI-RS) transmission is similar to periodic CSI-RS transmission. Resources for semi-persistent CSI-RS transmissions are semi-statically configured with parameters such as periodicity and subframe or slot offset. Unlike periodic CSI-RS transmission, however, dynamic signaling is used to activate and potentially deactivate the CSI-RS transmission. In NR, activation and deactivation is performed using MAC CE signaling. An example is illustrated in FIGURE 2. FIGURE 2 is a timing diagram illustrating semi-persistent CSI-RS transmission. The horizontal axis represents time. The timeline includes an activation trigger and a de-activation trigger where CSI-RS are periodically transmitted in the indicated subframes.

A cell can consist of multiple TRPs with each TRP located in distinct coordinates as illustrated in FIGURES 3.

FIGURE 3 is a block diagram illustrating a cell with multiple TRPs. The illustrated examples includes three TRPs.

This sort of configuration is expected to be used in I-IOT scenarios. As an example, one cell with 10, 20 or even more TRPs may be used to cover a complete factory hall.

For positioning, 3 distinct coordinates are required to perform multi-lateration. With the scenario where a serving cell has multiple TRPs located in distinct coordinates, these may be used for positioning.

NR Release 17 includes gapless PRS measurement. In Release 16, the PRS-based measurements (including PRS RSRP, RSTD for OTDOA and UE Rx-Tx for RTT) are all measured during 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 use a different bandwidth than the active bandwidth part it is configured with to receive data.

NR release 17 specifies 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 from the network.

SUMMARY

Based on the description above, certain challenges currently exist with controlling priority for wireless positioning signals. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, in particular embodiments the positioning reference signal (PRS) processing window (PPW) is configured via a configuration message sent from the serving gNB to the user equipment (UE).

Particular embodiments include a multi-level signaling of the priority of PRS using the existing PRS hierarchy used in the LPP and NRPPa protocol. In these protocols, the hierarchy is as follows: a transmission/reception point (TRP) can be configured with up to 4 positioning frequency layers; each frequency layer can be configured with up to 2 PRS resource sets; and each resource set can be configured with up to 64 PRS resources.

Particular embodiments re-use the hierarchy to signal the PRS priority across a given level. For example, setting the priority for positioning frequency layer 1 (PFL1) sets the priority in all resources present in all resource sets in PFL1.

In general, particular embodiments include signaling of a priority indicator at the positioning frequency layer level, wherein the signaled priority applies for all PRSs within a positioning frequency layer (PFL). Some embodiments include signaling of a priority indicator at the PRS resource set level, wherein the signaled priority applies for all PRSs within a PRS resource set and within the corresponding PFL. Some embodiments include signaling of a priority indicator at PPW level, wherein a signaled priority applies for all PRSs within a PPW.

According to some embodiments, a method is performed by a wireless device capable of receiving a PRS. The method comprises receiving a PPW configuration from a network node. The PPW configuration comprises a PRS priority indicator that indicates a priority associated with one or more of a PFL, a positioning resource set, and a positioning resource. The priority indicates a priority of the PRS with respect to other signals or channels received by the wireless device during the PPW. The method further comprises monitoring for a PRS during the PPW according to the priority indicator in the PPW configuration for the purpose of measuring/processing the PRS.

In particular embodiments, monitoring for the PRS during the PPW according to the priority indicator in the PPW configuration comprises measuring/processing the PRS when a priority of the PRS is higher than a priority of other signals or channels occurring at the same time as the PRS.

In particular embodiments, the priority indicator includes a priority associated with a PFL, and the indicated priority applies to all positioning resource sets and their positioning resources associated with the PFL. In particular embodiments, the priority indicator includes a priority associated with a PFL and a positioning resource set, and the indicated priority applies to all positioning resources associated with the PFL and the positioning resource set.

In particular embodiments, the priority indicator includes a priority associated with a PFL, a positioning resource set, and a positioning resource, and the indicated priority applies to the indicated positioning resource.

In particular embodiments, the priority indicator comprises a first priority indicator and the PPW configuration further comprises a second priority indicator. The first priority indicator includes a first priority associated with a PFL and the second priority indicator includes a second priority associated with the PFL and a positioning resource set. The first priority indicator applies to all positioning resource sets and their positioning resources associated with the PFL except for the positioning resource set indicated in the second priority indicator.

In particular embodiments, the priority indicator comprises a first priority indicator and the PPW configuration further comprises a second priority indicator. The first priority indicator includes a first priority associated with a PFL and the second priority indicator includes a second priority associated with the PFL, a positioning resource set, and a positioning resource. The first priority indicator applies to all positioning resource sets and their positioning resources associated with the PFL except for the positioning resource indicated in the second priority indicator.

In particular embodiments, the priority indicator comprises a first priority indicator and the PPW configuration further comprises a second priority indicator. The first priority indicator includes a first priority associated with a PFL and a first positioning resource set and the second priority indicator includes a second priority associated with the PFL, a positioning resource set, and a positioning resource. The first priority indicator applies to all positioning resources associated with the PFL and the first positioning resource set except for the positioning resource indicated in the second priority indicator.

According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless device described above.

Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

According to some embodiments, a method is performed by a network node for configuring a PPW. The method comprises determining a PPW configuration for a wireless device. The PPW configuration comprises a PRS priority indicator that indicates a priority associated with one or more of a PFL, a positioning resource set, and a positioning resource. The priority indicates a priority of the PRS with respect to other signals or channels received by the wireless device during the PPW. The method further comprises transmitting the PPW configuration to the wireless device.

In particular embodiments, the method further comprises obtaining positioning priority information from a location management function (LMF). Determining the PPW configuration is based on the obtained positioning priority information.

In particular embodiments, the priority indicator includes a priority associated with a PFL, and the indicated priority applies to all positioning resource sets and their positioning resources associated with the PFL.

According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments enable signaling the priority of PRSs within the PPW with different levels of granularity, while also maintaining a compact and efficient signaling.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 is a block diagram illustrating next generation radio access network (NG- RAN) Release 15 location services (LCS) protocols;

FIGURE 2 is a timing diagram illustrating semi-persistent CSI-RS transmission;

FIGURE 3 is a block diagram illustrating a cell with multiple TRPs;

FIGURE 4 is a signaling diagram illustrating the configuration of a positioning priority for a user equipment (UE);

FIGURE 5 is a block diagram illustrating an example wireless network;

FIGURE 6 illustrates an example user equipment, according to certain embodiments;

FIGURE 7 is flowchart illustrating an example method in a wireless device, according to certain embodiments;

FIGURE 8 is a flowchart illustrating an example method in a network node, according to certain embodiments;

FIGURE 9 illustrates a schematic block diagram of a wireless device and network node in a wireless network, according to certain embodiments;

FIGURE 10 illustrates an example virtualization environment, according to certain embodiments;

FIGURE 11 illustrates an example telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 12 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 13 is a flowchart illustrating a method implemented, according to certain embodiments;

FIGURE 14 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments;

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments; and

FIGURE 16 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments. DETAILED DESCRIPTION

When a downlink channel or another downlink reference signal with higher priority collides with DL PRS measurement/processing, the UE will drop the DL PRS measurement/proce s sing .

NR Release 17 supports, subject to UE capability, PRS measurement outside the measurement gap, within a PRS processing window, and UE measurement inside the active DL BWP with PRS having the same numerology as the active DL BWP. Inside the PRS processing window, subject to the UE determining that DL PRS to be higher priority, support the following UE capabilities, referred to as Capability 1 and Capability 2.

Capability 1 includes PRS prioritization over all other downlink signals/channels in all symbols inside the window. In a Capability 1A, the downlink signals/channels from all downlink component carriers (per UE) are affected. In a Capability IB, only the downlink signals/channels from a certain band/component carrier are affected. Capability 2 includes PRS prioritization over other downlink signals/channels only in the PRS symbols inside the window.

A UE shall be able to declare a PRS processing capability outside a measurement gap.

PRS-related conditions may be specified. For example, measurement support outside of a measurement gap may be applicable to serving cell PRS only or applicable to all PRS under conditions to PRS of non-serving cell.

When the UE determines higher priority for other downlink signals/channels over the PRS measurement/processing, the UE is not expected to measure/process DL PRS, which is applicable to all of the above capability options.

Three different UE capabilities may guide the UE behavior as to how the UE treats the data traffic when PRS is prioritized in a PRS prioritization window (PPW).

For Capability 1 A, the downlink signaling/channels in a per UE fashion (i.e. both across NR and LTE) inside the PRS processing window are dropped if the DL PRS is determined to be higher priority. For Capability IB, only the downlink signaling/channels from a certain band inside the PRS processing window are dropped if the DL PRS is determined to be higher priority.

The following options are supported subject to UE capability for priority handling of PRS when PRS measurement is outside a measurement gap. In Option 1, a UE may indicate support of two priority states. In State 1, PRS is higher priority than all PDCCH/PDSCH/CSI- RS. In State 2, PRS is lower priority than all PDCCH/PDSCH/CSI-RS.

In Option 2, a UE may indicate support of three priority states. In State 1, PRS is higher priority than all PDCCH/PDSCH/CSI-RS. In State 2, PRS is lower priority than PDCCH and URLLC PDSCH and higher priority than other PDSCH/CSI-RS. The URLLC channel corresponds a dynamically scheduled PDSCH whose PUCCH resource for carrying ACK/NAK is marked as high-priority. In State 3, PRS is lower priority than all PDCCH/PDSCH/CSI-RS.

In Option 3, a UE may indicate support of single priority state. In State 1, PRS is higher priority than all PDCCH/PDSCH/CSI-RS.

SSB is a separate issue. The priority of PRS for UE supporting two priority states and three priority states can at least be indicated in RRC.

The following parameters for PRS processing window from the gNB to the UE may be supported: starting slot, periodicity, duration/length, cell and SCS information associated with the above parameters, processing type (associated with the corresponding UE capability 1A/1B/2), band/CC-ID as needed depending on each scenario on which the PRS processing window is applied, and cell and SCS information to determine where/when the PRS processing window is applied.

An indication of processing type does not suggest UE indication of multiple capabilities among (1A/1B/2) is already supported.

Some of the parameters above may not be mandatory for a PRS processing window.

As discussed above, depending on UE capability, there can be three states for the priority of PRS with respect to other DL channels and signals:

1. PRS is higher priority than all PDCCH/PDSCH/CSI-RS

2. PRS is lower priority than PDCCH and URLLC PDSCH and higher priority than other PDSCH/CSLRS, where URLLC PDSCH corresponds to a dynamically scheduled PDSCH whose PUCCH resource for carrying ACK/NAK is marked as high-priority.

3. PRS is lower priority than all PDCCH/PDSCH/CSI-RS.

There currently exist certain challenges. For example, PRS configuration information comes via LMF to gNB. Based upon this information and information on what type of traffic the UE currently has; gNB configures the PRS processing window (PPW) to the UE.

Three possible states for PRS priority exist, but how to configure the priority of the PRS with respect to other downlink channels and signals needs to be determined.

As described above, certain challenges currently exist with controlling priority for wireless positioning signals. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, in particular embodiments the positioning reference signal (PRS) processing window (PPW) is configured via a configuration message sent from the serving gNB to the user equipment (UE). Particular embodiments include a multi-level signaling of the priority of PRS.

Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

The PRS prioritization window is a time window over which the PRS may have a priority higher than other downlink channels (e.g., physical downlink control channel (PDCCH)/physical downlink shared channel (PDSCH)) and signals (e.g., channel state information reference signal (CSI-RS)). For configuring priority of PRS with respect to other downlink channels and signals for a UE, a gNB may configure the PPW with a priority setting for each of the serving PRSs and non-serving PRSs (i.e., a priority indicator is configured for every single PRS resource from either the serving gNB or non-serving gNB). Information on each PRS resource may be forwarded to the serving gNB by the location management function (LMF), which is used by the serving gNB to set the priority for each PRS resource.

In some scenarios, priority for each PRS resource that occurs within a PPW may be configured as part of the PPW configuration by the serving gNB to the UE. However, this solution may require a large overhead because a priority state has to be indicated for each PRS resource in the PPW. For this reason, particular embodiments described herein efficiently signal the priority of the different PRSs within the PPW from the serving gNB to the UE.

Particular embodiments include a priority indicator information element (IE) in 3 GPP TS 38.331. A candidate description of the priority indicator IE in ASN.l pseudo code is as follows:

Priority indicator-r!7 : : = SEQUENCE {

PositioningFrequency layer ID INTEGER ( 0 . . 3 ) , OPTIONAL

PositioningRS_Resource_set~ID INTEGER ( 0 . . 2 ) , OPTIONAL

PositioningRS_Resource_ID INTEGER ( 0 . . 63 ) , OPTIONAL priority state ENUMERATED ( statel , state2 , state3 )

)

The preceding is one example, and particular embodiments may include any suitable implementation.

As shown in the example above, IDs for the positioning frequency layer (PFL), positioning reference signal (PRS) resource set, and PRS resource IDs are optionally included in the IE. One or more such priority indicators may be configured inside each PPW configured by the serving gNB for the UE. The above IE structure enables the configured priority_state to be configured for PRS with different granularities as follows.

If all of PositioningFrequency Jay er JD, PositioningRS_Resource_set_ID and PositioningRS_Resource_ID are omitted from the Priority_indicator-rl7 IE, then only a single priority state is configured inside a configured PPW. In this case, the single priority state applies to all the PRSs (including serving cell PRSs and non-serving cell PRSs) that occur within the configured PPW.

If PositioningRS_Resource_set_ID and PositioningRS_Resource_ID are omitted from Priority_indicator-rl7 IE, and PositioningFrequency_layer_ID is present in Priority Jndicator- rl7 IE, the priority indicator applies to all PRS resources in the PFL identified by its ID, PositioningFrequency Jay er JD. In this embodiment, one priority_state may be configured for each PFL as part of the PPW configuration. For example, if the serving cell and non-serving cell PRSs that occur within the configured PPW belong to S>1 different PFLs (where S is an integer), then there will be S priority states configured in the PPW configuration. This can be configured as a list of S parameters of type Priorityjndicator-rl7 in the PPW configuration, where each of the S parameters contains a PositioningFrequency Jayer JD and a priority_state.

If PositioningRS_ResourceJD is omitted from Priorityjndicator-rl7 IE, and PositioningFrequency Jay er JD and PositioningRS_Resource_setJD are present in Priority Jndicator-r 17 IE, the priority indicator applies to all PRS resources in the resource set identified by PositioningRS_Resource_setJD and the PFL identified by PositioningFrequency Jay er JD. In this embodiment, one priority_state may be configured for each PRS resource set in each PFL as part of the PPW configuration. For example, if the serving cell and non-serving cell PRSs that occur within the configured PPW belong to P>1 different PRS resource sets belonging to one or more PFLs (where P is an integer), then there will be P priority states configured in the PPW configuration. This can be configured as a list of P parameters of type Priority_indicator-rl7 in the PPW configuration, where each of the P parameters contains a PositioningFrequency_layer_ID, a PositioningRS_Resource_set_ID and a priority_state.

In some embodiments, the priority configuration consists of a list of priorities for each PFL, resources set, or PRS resources for which the priority is set.

In some embodiments, the PPW configuration includes a sequence of priority indicators that together configure the priorities of PRSs in the window. Each instance of the priority indicator may modify/complement the previous instances of the priority indicator. In some embodiments, a combination of the different levels of priority indicator may be used to assign the PRS priority, and the order of the priority indicators in the PPW configuration is used to update the PRS priority. For example, the PRS priority may be set to “PRS is higher priority than all PDCCH/PDSCH/CSLRS” for PFL#1 in a first instance of the priority indicator IE, and additionally the PRS priority for PRS resource #1 in resource set#l in PFL#1 may be set to “PRS is lower priority than all PDCCH/PDSCH/CSLRS ” in a second instance of the priority indicator IE. This assigns all PRS in PFL#1 except PRS#1 in set#l in PFL#1 a priority of “PRS is higher priority than all PDCCH/PDSCH/CSLRS”.

In NR Release 17, the PPW is a time window with a start, length and periodicity. In some embodiments, all PRSs that have not been covered by the priority indicator are by default set to default priority state of “PRS is lower priority than all PDCCH/PDSCH/CSLRS.”

In some embodiments, the PRS priority indicator is provided as a single indicator that applies the same priority state to all PRSs within the PPW configuration.

The PRS indicator may also be indicated for all PRS in a given positioning frequency layer. In some embodiments, the PPW can include a PFL priority indicator, which set all PRSs resources within all resource sets in the positioning frequency layer associated to the priority indicator to the same priority state.

The PRS indicator may also be indicated for all PRS in a given resource set within a given positioning frequency layer. In some embodiments, the PPW can include a PRS resource set priority indicator, which sets all PRSs resources within the associated resource set in the associated positioning frequency layer in the priority indicator to the same priority state.

The PRS indicator may also be indicated for each PRS resource in a resource set within a given positioning frequency layer. In one embodiment, the PPW may include a PRS resource priority indicator, which sets a single PRS resource within the associated resource set in the associated positioning frequency layer in the priority indicator to the same priority state.

An example of the signaling described above is illustrated in FIGURE 4.

FIGURE 4 is a signaling diagram illustrating the configuration of a positioning priority for a user equipment. In the illustrated example, the LMF sends an indication of positioning priority with granular information on PFL, positioning resource set, and positioning resources to the gNB. The gNB uses the received positioning priority information to create a PPW configuration for the UE. The gNB transmits the PPW configuration to the UE.

FIGURE 5 illustrates an example wireless network, according to certain embodiments. The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices. Network node 160 and WD 110 comprise various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.

Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.

A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi- standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 5, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 5 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’ s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node.

In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.

For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162.

Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160.

For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 5 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.

In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.

As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A wireless device as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within wireless device 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and be connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, wireless device 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114.

Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other wireless device 110 components, such as device readable medium 130, wireless device 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of wireless device 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.

In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.

In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of wireless device 110, but are enjoyed by wireless device 110, and/or by end users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be integrated. User interface equipment 132 may provide components that allow for a human user to interact with wireless device 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction may be via a touch screen; if wireless device 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).

User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, wireless device 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used, wireless device 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry.

Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of wireless device 110 to which power is supplied.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 5. For simplicity, the wireless network of FIGURE 5 only depicts network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

FIGURE 6 illustrates an example user equipment, according to certain embodiments. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 may be any UE identified by the 3 ^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 6, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3 ^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 6 is a UE, the components discussed herein are equally applicable to a wireless device, and vice-versa.

In FIGURE 6, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may use all the components shown in FIGURE 6, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIGURE 6, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine -readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer. In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205.

An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.

UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch- sensitive or presence- sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 6, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.

Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium. In FIGURE 6, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIGURE 7 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 7 may be performed by wireless device 110 described with respect to FIGURE 5. The wireless device capable of receiving a PRS.

The method begins at step 712, where the wireless device (e.g., wireless device 110) receives a PPW configuration from a network node (e.g., network node 160). The PPW configuration comprises a PRS priority indicator that indicates a priority associated with one or more of a PFL, a positioning resource set, and a positioning resource. The priority indicates a priority of the PRS with respect to other signals or channels received by the wireless device during the PPW.

In particular embodiments, the priority indicator includes a priority associated with a PFL, and the indicated priority applies to all positioning resource sets and their positioning resources associated with the PFL.

The priority indicator may comprise any of the priority indicators described in the embodiments and examples described herein.

At step 714, the wireless device monitors for a PRS during the PPW according to the priority indicator in the PPW configuration for the purpose of measuring/processing the PRS. For example, the monitoring comprises measuring/processing the PRS when a priority of the PRS is higher than a priority of other signals or channels occurring at the same time as the PRS.

Modifications, additions, or omissions may be made to method 700 of FIGURE 7. Additionally, one or more steps in the method of FIGURE 7 may be performed in parallel or in any suitable order. FIGURE 8 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 8 may be performed by network node 160 described with respect to FIGURE 5. The network node is capable of configuring a PPW.

The method begins at step 812, where the network node (e.g., network node 160) may obtain positioning priority information from a location management function (LMF).

At step 814, the network node determines a PPW configuration for a wireless device. The PPW configuration comprises a PRS priority indicator that indicates a priority associated with one or more of a PFL, a positioning resource set, and a positioning resource. The priority indicates a priority of the PRS with respect to other signals or channels received by the wireless device during the PPW.

Determining the PPW configuration may be based on the obtained positioning priority information.

In particular embodiments, the priority indicator includes a priority associated with a PFL, and the indicated priority applies to all positioning resource sets and their positioning resources associated with the PFL.

The priority indicator may comprise any of the priority indicators described in the embodiments and examples described herein.

At step 816, the network node transmits the PPW configuration to the wireless device.

Modifications, additions, or omissions may be made to method 800 of FIGURE 8. Additionally, one or more steps in the method of FIGURE 8 may be performed in parallel or in any suitable order.

FIGURE 9 illustrates a schematic block diagram of two apparatuses in a wireless network (for example, the wireless network illustrated in FIGURE 5). The apparatuses include a wireless device and a network node (e.g., wireless device 110 and network node 160 illustrated in FIGURE 5). Apparatuses 1600 and 1700 are operable to carry out the example methods described with reference to FIGURES 8 and 9, respectively, and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of FIGURES 8 and 9 are not necessarily carried out solely by apparatus 1600 and/or apparatus 1700. At least some operations of the method can be performed by one or more other entities. Virtual apparatuses 1600 and 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.

In some implementations, the processing circuitry may be used to cause receiving module 1602, determining module 1604, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure. Similarly, the processing circuitry described above may be used to cause determining module 1704, transmitting module 1706, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in FIGURE 9, apparatus 1600 includes receiving module 1602 configured to receive PPW configurations according to any of the embodiments and examples described herein. Determining module 1604 is configured to determine PRS priority according to any of the embodiments and examples described herein.

As illustrated in FIGURE 9, apparatus 1700 includes determining module 1704 configured to determine PPW configuration according to any of the embodiments and examples described herein. Transmitting module 1706 is configured to transmit PPW configuration to a wireless device according to any of the embodiments and examples described herein.

FIGURE 10 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIGURE 10, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE). Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in Figure 18.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 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 effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

With reference to FIGURE 11, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 430 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 11 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIGURE 12 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments. Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 12. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 12) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct, or it may pass through a core network (not shown in FIGURE 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 12 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 5, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 12 and independently, the surrounding network topology may be that of FIGURE 5.

In FIGURE 12, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., based on load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery life.

A measurement procedure may be provided for 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 OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 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 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section.

In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section.

In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally, or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section.

In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Modifications, additions, or omissions may be made to the systems and apparatuses disclosed herein without departing from the scope of the invention. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

The foregoing description sets forth numerous specific details. It is understood, however, 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 this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation .

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. 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.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

Example EMBODIMENTS

Group A Embodiments

Example 1. A method performed by a user equipment, the method comprising:

- receiving, from a base station, a positioning reference signal (PRS) priority indicator indicating a PRS priority for all PRS of a positioning frequency layer (PFL)

- applying the PRS priority to all PRS of the PFL.

Example 2. A method performed by a user equipment, the method comprising:

- receiving, from a base station, a positioning reference signal (PRS) priority indicator indicating a PRS priority for all PRS of a PRS resource set;

- applying the PRS priority to all PRS of the PRS resource set.

Example 3. A method performed by a user equipment, the method comprising:

- receiving, from a base station, a positioning reference signal (PRS) priority indicator indicating a PRS priority for all PRS of a PRS processing window (PPW);

- applying the PRS priority to all PRS of the PPW.

Example 4. A method performed by a user equipment, the method comprising:

- any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example 5. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above.

Example 6. The method of any of the previous embodiments, further comprising:

- providing user data; and

- forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

Example 7. A method performed by a base station, the method comprising:

- receiving a positioning reference signal (PRS) priority indicator indicating a PRS priority for all PRS of a positioning frequency layer (PFL)

- transmitting the PRS priority indicator to a user equipment.

Example 8. A method performed by a base station, the method comprising:

- Receiving a positioning reference signal (PRS) priority indicator indicating a PRS priority for all PRS of a PRS resource set;

- transmitting the PRS priority indicator to a user equipment.

Example 9. A method performed by a base station, the method comprising:

- receiving, from a base station, a positioning reference signal (PRS) priority indicator indicating a PRS priority for all PRS of a PRS processing window (PPW);

- transmitting the PRS priority indicator to a user equipment.

Example 10. A method performed by a base station, the method comprising:

- detecting an aerial radar signal; and

- restricting transmission to not interfere with the detected aerial radar. Example 11. The method of the previous embodiment, wherein detecting an aerial radar signal comprises combining antenna ports into a subset of ports for detecting elevation and a subset of ports for detecting azimuth.

Example 12. The method of any one of the previous embodiments, wherein detecting an aerial radar signal comprises beamforming one or more antenna ports towards the horizon.

Example 13. The method of any one of the previous embodiments, wherein detecting an aerial radar signal comprises sharing information with one or more base stations.

Example 14. A method performed by a base station, the method comprising:

- any of the steps, features, or functions described above with respect to a base station, either alone or in combination with other steps, features, or functions described above.

Example 15. The method of any of the previous embodiments, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer or a wireless device.

Group C Embodiments

Example 16. A user equipment comprising:

- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and

- power supply circuitry configured to supply power to the wireless device.

Example 17. A base station comprising:

- processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the wireless device.

Example 18. A user equipment (UE) comprising: - an antenna configured to send and receive wireless signals;

- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

- a battery connected to the processing circuitry and configured to supply power to the UE.

Example 19. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

Example 20. The communication system of the pervious embodiment further including the base station.

Example 21. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Example 22. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and - the UE comprises processing circuitry configured to execute a client application associated with the host application.

Example 23. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

Example 24. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

Example 25. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Example 26. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.

Example 27. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.

Example 28. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. Example 29. The communication system of the previous 2 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application.

Example 30. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

Example 31. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

Example 32. A communication system including a host computer comprising:

- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

Example 33. The communication system of the previous embodiment, further including the UE.

Example 34. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. Example 35. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

Example 36. The communication system of the previous 4 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Example 37. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

Example 38. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

Example 39. The method of the previous 2 embodiments, further comprising:

- at the UE, executing a client application, thereby providing the user data to be transmitted; and

- at the host computer, executing a host application associated with the client application.

Example 40. The method of the previous 3 embodiments, further comprising:

- at the UE, executing a client application; and - at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,

- wherein the user data to be transmitted is provided by the client application in response to the input data.

Example 41. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

Example 42. The communication system of the previous embodiment further including the base station.

Example 43. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Example 44. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application;

- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Example 45. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. Example 46. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

Example 47. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.