Selection of measurement window types for positioning measurements

Abstract

Techniques for wireless communication are disclosed. In one aspect, a user equipment (UE) or network component may select, based on one or more selection criteria, a measurement window type corresponding to a positioning reference signal (PRS) processing window (PPW) or a measurement gap (MG) for measurement processing of each instance of a positioning frequency layer (PFL) for a positioning session for the UE.

Description

Background Art 1. Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications.

[0002] 2. Description of related technologies

[0003] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G enable high-precision positioning based on 5G. Summary of the invention

[0005] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0006] In one aspect, a method of operating a user equipment (UE) includes: receiving a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); receiving a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, the overlapping time domain portion including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and performing the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0007] In one aspect, a method of operating a network component includes: sending a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); sending a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, and the overlapping time domain portion includes an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session for the UE based on one or more selection criteria; and sending to the UE an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0008] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); receive, via the at least one transceiver, a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; select, based on one or more selection criteria, a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE; and perform the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0009] In one aspect, a network component includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send, via the at least one transceiver, a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); send, via the at least one transceiver, a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); select, based on one or more selection criteria, a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE; and send, to the UE, via the at least one transceiver, activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0010] In one aspect, a user equipment (UE) includes: a component for receiving a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); a component for receiving a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, and the overlapping time domain portion includes an instance of a positioning frequency layer (PFL) for a positioning session of the UE; a component for selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and a component for performing the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0011] In one aspect, a network component includes: means for sending a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); means for sending a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, the overlapping time domain portion including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); means for selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and means for sending to the UE an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0012] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); receive a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; select a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and perform the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: send a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); send a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); select a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session for the UE based on one or more selection criteria; and send to the UE an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0014] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0016] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0017] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.

[0018] Figure 3A , Figure 3B and Figure 3Cis a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0019] Figure 4 is a diagram illustrating example interactions between application programs, application services, an operating system (OS), and hardware using various application programming interfaces (APIs) according to aspects of the present disclosure.

[0020] Figure 5A is a diagram illustrating an example frame structure according to aspects of the present disclosure.

[0021] Figure 5B is a diagram of example positioning reference signal (PRS) configurations for PRS transmission for a given base station in accordance with aspects of the present disclosure.

[0022] Figure 6 is a diagram illustrating various downlink channels within an example downlink time slot in accordance with aspects of the present disclosure.

[0023] Figure 7 is a diagram illustrating an example downlink PRS measurement scenario according to aspects of the present disclosure.

[0024] Figure 8 Table illustrating different techniques for reducing physical layer PRS processing latency according to aspects of the present disclosure.

[0025] Fig. 9 is a diagram of an example downlink PRS transmission, processing, and reporting cycle for multiple UEs in accordance with aspects of the present disclosure.

[0026] FIG. 10A to FIG. 10C A table showing various feature groups associated with different types of PRS processing capabilities and corresponding components of those feature groups is illustrated in accordance with aspects of the present disclosure.

[0027] Fig.11 is a diagram illustrating an example downlink positioning reference signal (DL-PRS) configuration for two transmit reception points (TRPs) operating in the same positioning frequency layer in accordance with aspects of the present disclosure.

[0028] Fig.12 A positioning reference signal (PRS) processing window (PPW) activation / deactivation procedure according to aspects of the present disclosure is illustrated.

[0029] Fig.13 Bandwidth part (BWP) configurations according to aspects of the present disclosure are illustrated.

[0030] Fig.14 An exemplary process of communication according to aspects of the present disclosure is illustrated.

[0031] Fig.15 An exemplary process of communication according to aspects of the present disclosure is illustrated.

[0032] Fig.16 BWP configurations according to aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0033] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

[0034] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0035] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0036] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It should be understood that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by a program instruction executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "a logical unit configured to perform the described action".

[0037] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any particular radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", a "client device", a "wireless device", a "subscriber device", a "subscriber terminal", a "subscriber station", a "user terminal" or "UT", a "mobile device", a "mobile terminal", a "mobile station", or variations thereof. Generally speaking, the UE can communicate with the core network via the RAN, and through the core network, the UE can be connected to external networks such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0038] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may only provide edge node signaling functions, while in other systems, a base station may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0039] The term "base station" may refer to a single physical transmit receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0040] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).

[0041] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to either a wireless signal or an RF signal.

[0042] Figure 1An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In one aspect, the macro cell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femto cells, pico cells, micro cells, etc.

[0043] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below), and the like. For signaling purposes, communications between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

[0044] Among other functions, the base station 102 can perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (e.g., through EPC / 5GC) on a backhaul link 134, which can be wired or wireless.

[0045] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., via a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, since the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0046] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage area 110. For example, a small cell base station 102′ (labeled “SC” for “small cell”) may have a geographic coverage area 110′ that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a Home eNB (HeNB) that may provide services to a restricted group referred to as a Closed Subscriber Group (CSG).

[0047] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0048] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

[0049] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.

[0050] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to a frequency of 3 GHz, and a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 can utilize beamforming (sending and / or receiving) on ​​the mmW communication link 184 to compensate for extremely high path loss and short distances. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0051] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, the network node can use an array of antennas (referred to as a "phased array" or "antenna array") that produces RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together in the desired direction to increase radiation, while canceling out in the undesired direction to suppress radiation.

[0052] The transmit beams can be quasi-co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0053] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) the RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.

[0054] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived based on information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.

[0055] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, and if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0056] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0057] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, currently higher frequency bands are being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designation FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0058] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used in this document, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this document, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0059] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are typically UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier through which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0060] For example, still refer to Figure 1, one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0061] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0062] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between UE and base station). SL-UE (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or simply "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may not be able to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, where each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.

[0063] In one aspect, the sidelink 160 can operate on a wireless communication medium of interest, which can be shared with other wireless communications between other vehicles and / or infrastructure access points and other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0064] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102′, access point 150), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming via side link 160.

[0065] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any UE (shown as a single UE 104 in FIG. 1 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 can be part of a satellite positioning system that the UEs 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit a signal with a repeating pseudo-random noise (PN) code marked with a set number of chips. Although typically located in the SVs 112, the transmitters can sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 can include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0066] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, and the like, such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), and the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0067] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from ground base stations 102, UE 104 can receive communication signals (e.g., signal 124) from SV 112.

[0068] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), wait.

[0069] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either (or both) the gNBs 222 or ng-eNBs 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0070] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0071] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the figure can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with an authentication server function (AUSF) (not shown) and UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives keys from the SEAF, which are used by the SCM to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), transmission of location service messages between the NG-RAN 220 and the LMF 270, allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and notification of UE 204 mobility events. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0072] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0073] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0074] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 can support similar functionality as LMF 270, but LMF 270 can communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 can communicate with UE 204 and external clients (e.g., third-party servers 274) on the user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0075] Yet another optional aspect may include a third-party server 274 that can communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimate) of UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or may alternatively each correspond to a single server.

[0076] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, while the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.

[0077] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, SDAP layer, and PDCP layer, communicates with the gNB-DU 228 via the RLC layer and MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0078] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5GNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as a standalone base station or a single-chip base station) or a decomposed base station.

[0079] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0080] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0081] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with a core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via corresponding midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via corresponding fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0082] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0083] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 280. CU 280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU285 for network control and signaling.

[0084] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 285 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.

[0085] Lower layer functionality may be implemented by one or more RUs 287. In some deployments, a RU 287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

[0086] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 261, via the O1 interface. Additionally, in some specific implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via the O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .

[0087] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or in communication with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.

[0088] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0089] Figure 3A , Figure 3B and Figure 3C Several example components (represented by corresponding blocks) are illustrated, which may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may not be dependent on Figure 2A and Figure 2B 220 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, as depicted in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, to support file sending operations as taught herein. It should be understood that these components can be implemented differently in different types of devices (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0090] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for suppressing transmission, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0091] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for suppressing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0092] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 can be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 can be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as appropriate, and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.

[0093] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide components (e.g., components for sending, components for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 can use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 through one or more wired or wireless backhaul links. For another example, the network entity 306 can use one or more network transceivers 390 to communicate with one or more base stations 304 through one or more wired or wireless backhaul links, or communicate with other network entities 306 through one or more wired or wireless core network interfaces.

[0094] The transceiver can be configured to communicate over a wired or wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver can be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), in some implementations can include separate transmitter circuits and separate receiver circuits, or in other implementations can be implemented in other ways. The transmitter circuit and the receiver circuit of the wired transceiver (e.g., in some implementations, the network transceivers 380 and 390) can be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

[0095] As used herein, various wireless transceivers (e.g., in some implementations, transceivers 310, 320, 350, and 360, and network transceivers 380 and 390) and wired transceivers (e.g., in some implementations, network transceivers 380 and 390) may be generally referred to as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0096] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0097] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398 may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which when executed cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388 and 398 can be memory modules stored in the memories 340, 386 and 396, respectively, which, when executed by the processors 332, 384 and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304 and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0098] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0099] In addition, the UE 302 includes a user interface 346, which provides components for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.

[0100] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement the functionality of the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0101] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0102] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If there are multiple spatial streams destined for the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0103] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0104] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0105] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0106] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

[0107] In the uplink, the one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 302. The IP packets from the one or more processors 384 may be provided to the core network. The one or more processors 384 are also responsible for error detection.

[0108] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, are shown to include various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

[0109] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In one aspect, the data buses 334, 382, ​​and 392 may form or be part of a communication interface for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, ​​and 392 may provide for communication between different logical entities.

[0110] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, it should be understood that such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).

[0111] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated differently from a network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0112] Application services are pools of services needed to optimally deploy, run, and improve applications, such as load balancing, application performance monitoring, application acceleration, autoscaling, micro-segmentation, service proxy, service discovery, etc. Services and applications are both software programs, but they usually have different characteristics. Broadly speaking, services usually target smaller and more isolated functions than applications, and applications usually expose and call services, including services in other applications.

[0113] Web services are a type of application services that can be accessed via a Web address for direct application-to-application interaction. Web services can be local, distributed, or Web-based. Web services are based on open standards such as TCP / IP, HTTP, Java, HTML, and XML, and therefore, Web services do not rely on any one operating system or programming language. Therefore, software applications written in various programming languages ​​and running on various platforms can use Web services to exchange data through computer networks (such as the Internet) in a manner similar to inter-process communication on a single computer. For example, a client can call a Web service by transmitting an XML message to a Web service and waiting for a corresponding XML response.

[0114] An application programming interface (API) is an interface that facilitates interaction between different systems (e.g., hardware, firmware, and / or software entities or levels). More specifically, an API is a set of defined rules, commands, permissions, and / or protocols that allow one system to interact with another system and access data from another system. For example, an API can provide an interface for higher-level software (e.g., applications, web services, application services, etc.) to access lower-level software (e.g., microservices, operating systems, BIOS, firmware, device drivers, etc.) or hardware components (e.g., USB controllers, memory controllers, transceivers, etc.). Since web services expose the data and functionality of applications, every web service is actually an API, but not every API is a web service.

[0115] One type of API used to build microservice applications is a representational state transfer API, also known as a "REST API" or "RESTful API." REST API is a collection of Web API architectural principles, which means that to be a REST API, the interface must adhere to certain architectural constraints. REST APIs typically use HTTP commands and Secure Sockets Layer (SSL) encryption. It is language-independent because it can be used to connect applications and microservices written in different programming languages. Common commands for REST APIs include HTTP PUT, HTTP POST, HTTP DELETE, HTTP GET, and HTTP PATCH. Developers can use these REST API commands to perform actions on different "resources" within an application or service, such as data in a database. REST APIs can use Uniform Resource Locators (URLs) to locate and indicate the resources on which actions are performed.

[0116] Microservices are individual small, autonomous, independent services and / or functions that together form a larger microservices-based application. Within the application, each microservice performs a defined function, such as authenticating a user or retrieving a specific type of data. The goal of microservices, which are generally language-independent, is to enable them to fit into any type of application and communicate or collaborate with each other to achieve the overall purpose of a larger microservices-based application. When microservices are connected to create a microservices-based application, APIs define the rules that prevent and allow the actions of individual microservices and the interactions between individual microservices. For example, a REST API can be used as rules, commands, permissions, and / or protocols to integrate separate microservices to act as a single application.

[0117] Webhooks enable interaction between web-based applications using customized callbacks. The use of webhooks allows web-based applications to automatically communicate with other web-based applications. Unlike traditional systems where one system (the "subject" system) continuously polls another system (the "observer" system) to obtain certain data, webhooks allow the observer system to automatically push data to the subject system whenever an event occurs. This reduces the significant load on both systems because calls are only made between the two systems when a specified event occurs.

[0118] Webhooks communicate via HTTP and rely on the presence of a static URL that points to an API in the subject system that should be notified when an event occurs on the observer system. Therefore, the subject system needs to specify one or more URLs that will accept event notifications from the observer system.

[0119] Figure 4 4 is a diagram 400 illustrating example interactions between an application 410, an application service 420, an operating system (OS) 430, and hardware 440 using various APIs according to aspects of the present disclosure. In one aspect, the application 410, the application service 420, the operating system 430, and the hardware 440 may be combined in the same device (e.g., UE, base station, etc.).

[0120] like Figure 4 As shown, application service 420 (which may be a web service) includes two microservices 422a and 422b (collectively referred to as microservices 422). However, it should be understood that application service 420 may include more or less than two microservices 422. In some cases, application program 410 may directly access individual microservices 422 via their respective APIs 424a and 424b (collectively referred to as API 424). Figure 4424b is illustrated by application 410 calling microservice 422b via API 424b. Alternatively, application 410 may call application service 420 via API 424c of application service 420. Application service 420 may then call appropriate microservice 422 via corresponding API 424. Figure 4 4 is illustrated by application service 410 representing application program 410 calling microservice 422a via API 424a.

[0121] If called by application 410, microservice 422 can respond to application 410 via callback 412 of application 410. Alternatively, if called by application service 420, microservice 422 can respond to application service 420 via callback 426c of application service 420. In either case, the client (application 410 or application service 420) can call microservice 422 by transmitting, for example, an XML message to microservice 422 via a corresponding API 424, and microservice 422 can respond to the client by transmitting a corresponding XML response to callback 412.

[0122] Microservices 422 can access various subsystems within operating system 430 via the subsystem's corresponding API. Figure 4 In the example of , operating system 430 includes location subsystem 432a and communication subsystem 432b (collectively referred to as subsystem 432). Location subsystem 432a may include software and / or firmware for determining the location of a mobile device (e.g., UE). The mobile device being located may be a device including operating system 430 (e.g., a UE that calculates its own location, as in the case of UE-based positioning) or another device that does not include operating system 430 (e.g., where a location server estimates the location of the UE). Communication subsystem 432b may similarly include software and / or firmware for enabling a device including operating system 430 to communicate wirelessly. For example, communication subsystem 432b may implement lower layer communication functionality (e.g., MAC layer functionality, RRC layer functionality, etc.).

[0123] The subsystems 432 each expose corresponding APIs 434a and 434b (collectively, APIs 434) to a higher architectural level. The microservices 422 can call the subsystems 432 via their corresponding APIs 434, and the subsystems 432 can respond to the microservices 422 via callbacks 426a and 426b (collectively, callbacks 426) of the microservices 422. Figure 4In the example of , microservice 422a calls location subsystem 432a, and microservice 422b calls communication subsystem 432b within operating system 430. Therefore, microservice 422a can be a location-related microservice, and microservice 422b can be a communication-related microservice. However, it should be understood that any microservice 422 can call any subsystem 432 via its corresponding API 434.

[0124] exist Figure 4 In the example of FIG. 4 , the hardware 440 includes a satellite signal receiver 442 a, one or more WWAN transceivers 442 b, and one or more short-range wireless transceivers 442 c (collectively referred to as hardware components 442 ). The satellite signal receiver 442 a may correspond to, for example, Figure 3A and Figure 3B The satellite signal receiver 330 or 370 in FIG. One or more WWAN transceivers 442 b may correspond to, for example, Figure 3A and Figure 3B One or more WWAN transceivers 310 or 350 in. One or more short-range wireless transceivers 442c may correspond to, for example Figure 3A and Figure 3B One or more short-range wireless transceivers 320 or 360 in.

[0125] exist Figure 4 In the example of FIG. 4 , the location subsystem 432a can transmit commands (e.g., a request for measurement of a reference signal, a request to send a reference signal, etc.) to the satellite signal receiver 442a, the one or more WWAN transceivers 442b, and / or the one or more short-range wireless transceivers 442c via their APIs 444a, 444b, and 444c, respectively. The satellite signal receiver 442a, the one or more WWAN transceivers 442b, and / or the one or more short-range wireless transceivers 442c can transmit responses to the commands (e.g., measurement of a reference signal, confirmation, etc.) to the location subsystem 432a via callback 436a. Similarly, the communication subsystem 432b can transmit information to be wirelessly transmitted (e.g., user data, measurement reports, etc.) to the one or more WWAN transceivers 442b and / or the one or more short-range wireless transceivers 442c via their APIs 444b and 444c, respectively. The one or more WWAN transceivers 442b and / or the one or more short-range wireless transceivers 442c may transmit wirelessly received information (eg, user data, location requests, positioning assistance data, etc.) to the communication subsystem 432b via the callback 436b.

[0126] As Figure 4In a specific positioning example in the context of , a device incorporating the illustrated architecture may be a mobile device, and application 410 may be an application that uses the location of the mobile device (e.g., UE), such as a navigation application (e.g., running locally on the mobile device). Thus, application 410 calls application service 420 (via API 424c), which calls microservice 422a (via API 424a), or the application calls microservice 422a directly (via API 424a). The command from application 410 indicates that application 420 is requesting the location of the mobile device, and may include (or additional commands may include) other information related to the requested location fix, such as the requested quality of service (QoS) (e.g., accuracy and latency).

[0127] Based on the QoS of the location request, the known capabilities of the mobile device (e.g., available positioning technologies, such as satellite-based, NR-based, Wi-Fi-based, etc.), available reference signal configurations (e.g., from nearby base stations), etc., the microservice 422a (via API 434a) calls the location subsystem 432a. It should be noted that the microservice 422a can coordinate with other microservices, other application services, other applications, etc. to obtain the information necessary to locate the mobile device. For example, the microservice 422a may need to access another microservice associated with one or more base stations that the mobile device is expected to measure in order to perform NR-based positioning procedures.

[0128] The microservice 422a may select a positioning technology for obtaining the location of the mobile device based on the known capabilities of the mobile device and the requested QoS. For example, using a satellite signal receiver 442a may provide high accuracy and low latency, but it may be turned off. As another example, using one or more WWAN transceivers 442b may provide low latency, but if the mobile device is indoors, the accuracy may be poor. Based on the selected positioning technology, the microservice 422a transmits one or more commands to the location subsystem 432a, requesting the location subsystem 432a to call the satellite signal receiver 442a, one or more WWAN transceivers 442b, or one or more short-range wireless transceivers 442c. In addition, depending on the type of positioning technology selected, the microservice 422a may provide commands regarding which reference signals to measure, which reference signals to send, etc. In addition, the microservice 422a may indicate the accuracy and latency required for the positioning measurement.

[0129] Based on the command from the microservice 422a, the location subsystem 432a calls the appropriate hardware components (via one or more of the APIs 444). For example, if the positioning technology is NR-based, the location subsystem 432a can send commands to one or more WWAN transceivers 442b to measure and / or send certain reference signals at certain times and frequencies. In addition, based on the requested accuracy and latency, the location subsystem 432a can increase or decrease the amount of power and / or processing resources allocated to one or more WWAN transceivers 442b. For example, for higher accuracy requirements, the location subsystem 432a can dedicate more power and / or processing resources to one or more WWAN transceivers 442b.

[0130] The location subsystem 432a receives (via callback 436a) positioning measurements (e.g., reception time, transmission time, signal strength, etc.) from one or more WWAN transceivers 442b and passes them to the microservice 422a (via callback 426a). The microservice 422a can then calculate the location of the mobile device based on the measurements and any other available information (e.g., the location of the base station that sent the measured reference signal). The microservice 422a provides the calculated location of the mobile device to the application 410 via callback 412 or via application service 420 (depending on which entity calls the microservice 422a).

[0131] In some aspects, the application 410 may provide the microservice 422a with credentials or other authorization indicating that the application 410 is allowed to access the location of the mobile device. Alternatively, upon receiving the request from the application 410, the microservice 422a may determine whether the application 410 is authorized. For example, the check may be performed via another microservice, or by calling the operating system 430 to determine whether the application 410 has permission to access the location of the mobile device. Similarly, the microservice 422a may need to provide the operating system 430 with credentials or other authorization indicating that the microservice 422a is allowed to access the location of the mobile device. Alternatively, upon receiving the request from the microservice 422a, the operating system 430 may determine whether the microservice 422a is authorized.

[0132] In some aspects, the application 410 can use a webhook to obtain the location of the mobile device. In this way, each time the mobile device moves from one location to another, the application 410 will be notified. In this case, the observer system will be the microservice 422a, and the subject system will be the application 410. Instead of the application 410 having to periodically call the microservice 422a to check if the location of the mobile device has changed, the webhook created in the application 410 will allow the microservice 422a to automatically push any changes in the location of the mobile device to the application 410 through the registered URL. The microservice 422a can periodically perform positioning operations to determine the location of the mobile device in order to report changes to the application 410.

[0133] Similarly, microservice 422a can use a webhook to obtain changes in the location of the mobile device. However, in this case, because microservice 422a coordinates location determination for certain types of positioning technologies (e.g., NR-based, Wi-Fi-based), the webhook can only be applied to certain other types of positioning technologies (e.g., satellite-based, sensor-based). For example, if location subsystem 432a coordinates satellite-based positioning via satellite signal receiver 442a, the location subsystem can report any detected location changes to microservice 422a via a webhook.

[0134] In some cases, the application 410, application service 420, operating system 430, and hardware 440 may be distributed across multiple devices (e.g., UE, Web server, location server, etc.). For example, the application 410 may run on a location server (e.g., LMF 270), the application service 420 may run on a Web server, and the operating system 430 and hardware 440 may be combined in a UE (e.g., UE 204).

[0135] NR supports a variety of cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include: observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle of departure (DL-AoD) in NR. In the OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the arrival time (ToA) of the reference signal (e.g., positioning reference signal (PRS)) received from the paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurement), and reports these differences to the positioning entity. More specifically, the UE receives the identifiers (IDs) of the reference base station (e.g., serving base station) and multiple non-reference base stations in the auxiliary data. Then, the UE measures the RSTD between the reference base station and each non-reference base station. Based on the known positions of the base stations involved and the RSTD measurement results, the positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.

[0136] For DL-AoD positioning, the positioning entity uses the measurement reports from the UE on the received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the position of the UE based on the determined angle and the known location of the transmitting base station.

[0137] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but it is based on uplink reference signals (e.g., sounding reference signals (SRS)) sent by the UE. For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurement and the angle of the receive beam to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0138] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference is called the received-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or can be adjusted to include only the time difference between the nearest time slot boundaries of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to another entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) so that the location of the first entity can be determined based on the distance to the second entity and the known location of the second entity (e.g., using multi-point positioning). RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve location accuracy.

[0139] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers of the detected neighboring base stations, the estimated timing and signal strength. The UE's position is then estimated based on this information and the known locations of the base stations.

[0140] To assist the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include: an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the periodicity of consecutive time slots including PRS, a silent sequence, a frequency hopping sequence, a reference signal identifier, a reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in a periodically broadcast overhead message, etc.). In some cases, the UE itself may be able to detect neighboring network nodes without using assistance data.

[0141] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may also include an expected RSTD value and an associated uncertainty or search window around the expected RSTD. In some cases, the value range of the expected RSTD may be + / -500 microseconds (μs). In some cases, when any of the resources used for positioning measurements are in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. In other cases, when all resources used for positioning measurements are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.

[0142] The position estimate may be referred to by other names, such as a positioning estimate, a position, a fix, a positioning fix, a fix, etc. The position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. The position estimate may be further defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). The positioning estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default confidence level).

[0143] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 5A 500A is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0144] LTE (and in some cases NR) utilizes OFDM on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Therefore, for a system bandwidth of 1.25 megahertz (MHz), 2.5MHz, 5MHz, 10MHz, or 20MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into multiple subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

[0145] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple parameter sets (μ), for example, 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17μs, and the maximum nominal system bandwidth (in MHz) is 800 with 4K FFT size.

[0146] exist Figure 5A In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 5A , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0147] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) in the frequency domain (also referred to as physical RBs (PRBs)). A resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 5AIn the parameter set of , for a normal cyclic prefix (CP), an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0148] Some of the REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink communication or downlink communication. Figure 5A Example locations of REs carrying reference signals (labeled "R") are illustrated.

[0149] Downlink PRS (DL-PRS) has been defined for NR positioning, enabling the UE to detect and measure more neighboring TRPs. Several configurations are supported to enable various deployments (e.g., indoor, outdoor, sub-6GHz, mmW). In addition, both UE-assisted positioning (where the network entity estimates the location of the target UE) and UE-based positioning (where the target UE estimates its own location) are supported. The following table illustrates various types of reference signals that can be used for various positioning methods supported in NR.

[0150]

[0151] Table 1

[0152] A set of resource elements (REs) used for transmission of PRS is referred to as a "PRS resource". A set of resource elements may span multiple PRBs in the frequency domain and "N" (such as 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.

[0153] The transmission of PRS resources within a given PRB has a specific comb size (also referred to as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N", the PRS is transmitted in every Nth subcarrier of the symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, for DL-PRS, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported. Figure 5A An example PRS resource configuration for comb-4 (which spans four symbols) is illustrated. That is, the positions of shaded REs (labeled as "R") indicate a comb-4 PRS resource configuration.

[0154] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a timeslot using a full frequency domain staggered pattern. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by higher layers in a timeslot. There may be a constant per-resource element energy (EPRE) for all REs of a given DL-PRS resource. The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol Comb-2: {0, 1}; 4-symbol Comb-2: {0, 1, 0, 1}; 6-symbol Comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol Comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol Comb-4: {0, 2, 1, 3} (as in Figure 5A ); 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0155] A "PRS resource set" is a set of PRS resources used to send a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in the PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in the PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity can have a length selected from: 2^μ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where μ=0, 1, 2, 3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0156] The PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where one TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") may also be referred to as a "beam". Note that this does not have any implication on whether the UE knows the TRP and beam on which the PRS is transmitted.

[0157] A "PRS instance" or "PRS opportunity" is an instance of a periodically repeated time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity", "PRS positioning instance", "positioning opportunity", "positioning instance", "positioning repetition", or simply "opportunity", "instance", or "repetition".

[0158] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set of one or more PRS resource sets with the same values ​​for certain parameters across one or more TRPs. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the physical downlink shared channel (PDSCH) are also supported by PRS), the same point A, the same value of the downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio frequency channel number") and is an identifier / code that specifies a pair of physical radio channels for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs and the maximum value is 272 PRBs. Currently, the UE can support up to four frequency layers across all positioning methods across all frequency bands, and up to two PRS resource sets can be configured per frequency layer per TRP.

[0159] The concept of frequency layer is somewhat similar to the concept of component carrier and bandwidth part (BWP), but the difference is that component carrier and BWP are used by one base station (or macro cell base station and small cell base station) to send data channels, while frequency layer is used by several (usually three or more) base stations to send PRS. The UE can indicate the number of frequency layers that the UE can support when the UE transmits its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, the UE can indicate whether it can support one or four positioning frequency layers.

[0160] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. If further distinction is needed between the types of PRS, the downlink positioning reference signal may be referred to as "DL-PRS", while the uplink positioning reference signal (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS". In addition, for signals that may be sent in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prepended with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS".

[0161] Figure 5B is a diagram of an example PRS configuration 500 for PRS transmission for a given base station in accordance with aspects of the present disclosure. Figure 5B In , time is represented horizontally, increasing from left to right. Each long rectangle represents a time slot, and each short (shaded) rectangle represents an OFDM symbol. Figure 5B In the example of FIG. 5 , a PRS resource set 510 (labeled as “PRS resource set 1”) includes two PRS resources, a first PRS resource 512 (labeled as “PRS resource 1”) and a second PRS resource 514 (labeled as “PRS resource 2”). The base station transmits PRS on PRS resources 512 and 514 of PRS resource set 510 .

[0162] PRS resource set 510 has an opportunity length (N_PRS) of two slots and a periodicity (T_PRS) of, for example (for 15 kHz subcarrier spacing) 160 slots or 160 milliseconds (ms). Thus, both PRS resources 512 and 514 are two consecutive slots in length and repeat every T_PRS slots starting from the slot in which the first symbol of the corresponding PRS resource appears. Figure 5B In the example of , PRS resource 512 has a symbol length (N_symb) of two symbols, and PRS resource 514 has a symbol length (N_symb) of four symbols. PRS resource 512 and PRS resource 514 may be transmitted on separate beams of the same base station.

[0163] Each instance of the PRS resource set 510 (illustrated as instances 520a, 520b, and 520c) includes a length of "2" opportunities (i.e., N_PRS=2) for each PRS resource 512, 514 in the PRS resource set. The PRS resources 512 and 514 repeat once every T_PRS time slot up to a muting sequence periodicity of T_REP. Therefore, a bitmap of length T_REP will be needed to indicate which opportunities of the instances 520a, 520b, and 520c of the PRS resource set 510 are muted (i.e., not transmitted).

[0164] In one aspect, there may be additional constraints on the PRS configuration 500. For example, for all PRS resources (e.g., PRS resources 512, 514) of a PRS resource set (e.g., PRS resource set 510), the base station may configure the following parameters to be the same: (a) opportunity length (N_PRS), (b) number of symbols (N_symb), (c) comb type, and / or (d) bandwidth. In addition, for all PRS resources in all PRS resource sets, the subcarrier spacing and cyclic prefix may be configured to be the same for one base station or for all base stations. Whether for one base station or for all base stations may depend on the ability of the UE to support the first and / or second options.

[0165] In some designs, the LMF provides the complete PRS configuration to the gNB as auxiliary information, and the gNB determines the pre-configuration of the measurement gap (MG). Category 1 procedures associated with the UE can be used to provide the complete PRS configuration to the gNB as pre-configured auxiliary information for the MG. In some designs, the MG activation request can be initiated by the LMF. In some designs, the signaling procedure for the MG activation request uses the category 2 signaling procedure associated with the UE. In some designs, the MG activation request message may include information similar to the RRC LocationMeasurementIndication message. In some designs, the LMF may provide auxiliary information to help the gNB determine the PRS processing window (described in more detail below). In some designs, for activation request procedures initiated by non-LMF, a unified signaling procedure on NRPPa may be used to deliver pre-configured MG and PRS processing window configuration information.

[0166] Figure 6 600 is a diagram illustrating various downlink channels within an example downlink time slot. Figure 6 In , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top. Figure 6 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0167] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a set of contiguous RBs selected from a contiguous subset of common RBs for a given parameter set on a given carrier. In general, a maximum of four BWPs can be specified in the downlink and uplink. That is, the UE can be configured to have up to four BWPs on the downlink and up to four BWPs on the uplink. Only one BWP (uplink or downlink) can be active at a given time, which means that the UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0168] refer to Figure 6 , the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form an SSB (also referred to as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent via the PBCH (such as the system information block (SIB)), and paging messages.

[0169] The physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), each CCE includes one or more RE group (REG) bundles (which can span multiple symbols in the time domain), each REG bundle includes one or more REGs, each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for PDCCH.

[0170] exist Figure 6 In the example of , there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be just one symbol or two symbols). Unlike LTE control channels that occupy the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region (i.e., CORESET) in the frequency domain. Thus, Figure 6 The frequency components of the PDCCH shown in FIG are illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESETs are continuous in the frequency domain, the CORESETs do not need to be continuous. Furthermore, the CORESETs may span less than three symbols in the time domain.

[0171] The DCI within the PDCCH carries information about uplink resource allocations (persistent and non-persistent) and descriptions of downlink data sent to the UE (referred to as uplink grants and downlink grants, respectively). More specifically, the DCI indicates resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of a variety of formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or decoding rates.

[0172] The following are the currently supported DCI formats. Format 0-0: Fallback for PUSCH scheduling; Format 0-1: Non-fallback for PUSCH scheduling; Format 1-0: Fallback for PDSCH scheduling; Format 1-1: Non-fallback for PDSCH scheduling; Format 2-0: Notify the UE group of the timeslot format; Format 2-1: Notify the UE group of PRBs and OFDM symbols where the UE can assume no transmission for the UE; Format 2-2: Transmission of TPC commands for the Physical Uplink Control Channel (PUCCH) and PUSCH; and Format 2-3: Transmission of a set of SRS requests and TPC commands for SRS transmission. Note that the fallback format is the default scheduling option, which has non-configurable fields and supports basic NR operation. In contrast, the non-fallback format is flexible to accommodate NR features.

[0173] It should be understood that the UE needs to be able to demodulate (also called "decode") the PDCCH in order to read the DCI and thereby obtain the scheduling of resources allocated to the UE on the PDSCH and PUSCH. If the UE fails to demodulate the PDCCH, the UE will not know the location of the PDSCH resources, and it will continue to try to demodulate the PDCCH using different PDCCH candidate sets in subsequent PDCCH monitoring opportunities. If the UE fails to demodulate the PDCCH after a certain number of attempts, the UE declares a radio link failure (RLF). In order to overcome the PDCCH demodulation problem, the search space is configured for efficient PDCCH detection and demodulation.

[0174] Typically, a UE will not attempt to demodulate every PDCCH candidate that may be scheduled in a time slot. In order to reduce the constraints on the PDCCH scheduler and to reduce the number of blind demodulation attempts made by the UE, a search space is configured. The search space is indicated by a set of consecutive CCEs that the UE is expected to monitor for scheduling assignments / grants related to a certain component carrier. There are two types of search spaces used for PDCCH to control each component carrier: Common Search Space (CSS) and UE Specific Search Space (USS).

[0175] The common search space is shared across all UEs, while the UE-specific search space is used for each UE (i.e., the UE-specific search space is specific to a specific UE). For the common search space, the DCI cyclic redundancy check (CRC) is scrambled with the system information radio network temporary identifier (SI-RNTI), random access RNTI (RA-RNTI), temporary cell RNTI (TC-RNTI), paging RNTI (P-RNTI), interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, cell RNTI (C-RNTI), or configured scheduling RNTI (CS-RNTI) for all common procedures. For the UE-specific search space, the DCI CRC is scrambled with the C-RNTI or CS-RNTI because these are specific to an individual UE.

[0176] The UE demodulates the PDCCH using four UE-specific search space aggregation levels (1, 2, 4, and 8) and two common search space aggregation levels (4 and 8). Specifically, for the UE-specific search space, aggregation level "1" has six PDCCH candidates per time slot and is six CCEs in size. Aggregation level "2" has six PDCCH candidates per time slot and is 12 CCEs in size. Aggregation level "4" has two PDCCH candidates per time slot and is eight CCEs in size. Aggregation level "8" has two PDCCH candidates per time slot and is 16 CCEs in size. For the common search space, aggregation level "4" has four PDCCH candidates per time slot and is 16 CCEs in size. Aggregation level "8" has two PDCCH candidates per time slot and is 16 CCEs in size.

[0177] Each search space includes a set of consecutive CCEs that can be allocated to PDCCH (referred to as PDCCH candidates). The UE demodulates all PDCCH candidates in these two search spaces (USS and CSS) to find DCI for the UE. For example, the UE can demodulate the DCI to obtain scheduled uplink grant information on the PUSCH and downlink resources on the PDSCH. It should be noted that the aggregation level is the number of REs of the CORESET that carry the PDCCH DCI message and is expressed in the form of CCEs. There is a one-to-one mapping between the aggregation level and the number of CCEs per aggregation level. That is, for aggregation level "4", there are four CCEs. Therefore, as shown above, if the aggregation level is "4" and the number of PDCCH candidates in a time slot is "2", the size of the search space is "8" (i.e., 4x 2=8).

[0178] Referring back to PRS, the following table provides the current physical layer DL-PRS processing capabilities that a UE can report. These values ​​indicate the amount of time that a UE may need in order to buffer and process DL-PRS at the physical layer.

[0179]

[0180] Table 2

[0181] The measurement window for each positioning frequency layer depends on (1) the reporting capability of the UE (e.g., according to Table 2), (2) the PRS periodicity (denoted as T PRS or T_PRS), (3) measurement gap periodicity (in the absence of measurement gaps, the UE is expected not to measure PRS), and (4) the number of receive beams of the UE (if operating in FR2).

[0182] Figure 7 700 is a diagram illustrating an example DL-PRS measurement scenario according to aspects of the present disclosure. Figure 7 , time is represented horizontally. The arrows represent a PRS periodicity 710 of 20 ms, and the boxes represent PRS resources 720 within the PRS periodicity 710, whose PRS symbols have a duration of 0.5 ms in milliseconds.

[0183] Based on the above considerations related to the length of the measurement window, given the following assumptions, Figure 7The minimum PRS measurement window in the example of will be 88 ms: (1) one PRS frequency layer in FR1, (2) PRS RSTD measurements are performed across four PRS instances (i.e., four repetitions of PRS periodicity 710), (3) both PRS periodicity 710 and measurement gap periodicity (denoted as "measurement gap repetition period" or "MGRP") are equal to 20 ms, and (4) the configured PRS resources are within the PRS processing capability of the UE. For the fourth assumption, parameters (N, T) = (0.5 ms, 8 ms) (from Table 2), where N is the duration in milliseconds of PRS resources 720 that the UE can process every T = 8 ms. Therefore, after the last PRS periodicity 710, there is an 8 ms period (i.e., T) during which the UE processes the PRS resources 720 received during four PRS periodicities 710, resulting in a total latency of 88 ms.

[0184] For positioning procedures where low latency is required (e.g., less than 10 ms at the physical layer), an 88 ms measurement window at the physical layer (e.g., Figure 7 ) will not meet the requirements. Figure 8 Table 800 illustrates different techniques for reducing physical layer PRS processing latency in accordance with aspects of the present disclosure.

[0185] Referring to the enhancement in the first row of Table 800, different UEs may have different time domain processing windows while ensuring that network resources may be used across UEs. Fig. 9 is a diagram 900 of an example DL-PRS transmission, processing, and reporting cycle for multiple UEs in accordance with aspects of the present disclosure. Fig. 9 In the example of FIG. 9 , three UEs have been configured to use a "DDDSU" frame structure 910 in a time division duplex (TDD) 30kHz SCS. As mentioned above, for a 30kHz SCS (μ=1), there are 20 slots per frame and the slot duration is 0.5ms. Therefore, each box of the DDDSU frame structure 910 represents a 0.5ms slot. The DDDSU frame structure 910 includes a repetition of three downlink (D) slots, one special (S) slot, and one uplink (U) slot.

[0186] exist Fig. 9In the example of , PRS is received in the first three downlink time slots of the frame, and SRS is sent in the fourth time slot. PRS and SRS can be received and sent as part of a downlink and uplink based positioning session (such as an RTT positioning session), respectively. The three time slots in which PRS is received (i.e., measured) can correspond to PRS instances. Typically, the PRS instance should be included within a few milliseconds (here, 2ms) of the start of the PRS transmission, processing and reporting cycle. SRS transmission (if necessary, as here, for downlink and uplink based positioning procedures) should be close to the PRS instance (here, in the next time slot).

[0187] like Fig. 9 As shown, a first UE (labeled "UE1") has been configured with a PRS transmission, processing and reporting cycle 920, a second UE (labeled "UE2") has been configured with a PRS transmission, processing and reporting cycle 930, and a third UE (labeled "UE3") has been configured with a PRS transmission, processing and reporting cycle 940. The PRS transmission, processing and reporting cycles 920, 930 and 940 may be repeated periodically (e.g., every 10 ms) for a certain duration. Each UE is expected to transmit a positioning report (e.g., its corresponding Rx-Tx time difference measurement result) at the end of its PRS transmission, processing and reporting cycle (e.g., every 10 ms). Each UE transmits its report on a PUSCH (e.g., a configured uplink grant). Specifically, the first UE transmits its report on PUSCH 924, the second UE transmits its report on PUSCH 934, and the third UE transmits its report on PUSCH 944.

[0188] like Fig. 9 As shown, different UEs have each been configured with their own PRS processing gap (or simply "processing gap") or PRS processing window (or simply "processing window") in which to process the PRS measured in the first three time slots of the frame (e.g., determine the ToA of the PRS and calculate the Rx-Tx time difference measurement result). Specifically, the first UE has been configured with processing gap 922, the second UE has been configured with processing gap 932, and the third UE has been configured with processing gap 942. Fig. 9 In the example shown in FIG. 1 , the length of each processing gap is 4 ms.

[0189] like Fig. 9As shown, the processing gap of each UE is offset from the processing gaps of other UEs, but still within the UE's 10ms PRS transmission, processing and reporting cycle. In addition, there is still a PUSCH opportunity for reporting the UE's measurement results after the processing gap. Even if there is a gap between the PRS instance and the processing gaps of the second UE and the third UE, the timing between measurement and reporting is limited due to the short length of the UE's corresponding PRS transmission, processing and reporting cycles 930 and 940.

[0190] The technical advantage of configuring offset processing gaps for UEs is greater spectrum utilization. Instead of all UEs processing PRS simultaneously after a PRS instance (and SRS transmission) and thus not processing other signals, different UEs can continue to transmit and receive while other UEs do not.

[0191] Refer to Processing Gap in more detail, e.g. Fig. 9 As shown, a processing gap is a time window after the time when the PRS is received and measured. Thus, this is a time period during which the UE processes the PRS (e.g., to determine the ToA of the PRS for Rx-Tx time difference measurement or RSTD measurement) without having to measure any other signal. In other words, a processing gap is a time period during which the UE prioritizes the PRS over other channels, which may include prioritizing over data (e.g., PDSCH), control (e.g., PDCCH), and any other reference signal. However, as Fig. 9 As shown, there may be a gap between the time of measurement and the processing gap. Note that in some cases, depending on the capabilities of the UE, the processing gap may only correspond to the actual PRS symbols being measured.

[0192] A processing gap or processing window is different from a measurement gap. In a processing gap, there is no retuning gap as in a measurement gap - the UE does not change its BWP but continues with the BWP it had before the processing gap. In addition, the location server (e.g., LMF 270) can determine the processing gap and the UE will not need a processing gap to transmit an RRC request to the serving base station and wait for a reply. Thus, the processing gap will reduce signaling overhead and latency.

[0193] Information related to the PRS processing gap may be provided in the unicast assistance data received by the UE. For example, the LPP provides assistance data message may include information for determining the processing gap. Alternatively, the PRS processing gap information may be included in the LPP provides location information message to the UE, or included in the on-demand PRS information (e.g., UE-initiated on-demand PRS and processing gap information). The processing gap may be associated with one or more positioning frequency layers, one or more PRS resource sets, one or more PRS resources, or any combination thereof.

[0194] The UE may include a request for a specific processing gap in the LPP Assistance Data Request message. Alternatively, the UE may include PRS processing gap information in the LPP Provide Capabilities message. For example, the UE may selectively include a processing gap request for a "strict" PRS processing case (e.g., a case where there is a limited time between measuring a PRS instance and reporting the measurement). The request may include how long a PRS processing gap the UE requires for low latency PRS processing applications. For example, for a PRS instance with "X" PRS resource sets, resources, or symbols, the UE may require 4 ms of processing time. The location server may use this recommendation to transmit assistance data associated with a specific PRS processing gap to the UE.

[0195] The processing gap information configured to the UE and / or recommended by the UE may include: (1) offsets relative to: (a) the start or offset of a PRS instance (e.g., Fig. 9 The processing gap of the second UE in the PRS instance is offset by 4 ms from the start of the PRS instance); (b) the end of the PRS instance (e.g., Fig. 9 The processing gap of the third UE in the PRS instance is offset by 3.5 ms from the end of the PRS instance); (c) a PRS resource offset; (d) a PRS resource set offset; or (e) a time slot, subframe, or frame boundary (e.g., Fig. 9 The processing gap for the second UE in the frame is offset by 4.5 ms from the start of the frame); (2) the length and / or end time of the processing gap; (3) whether the processing gap is per UE, per band, per band combination (BC), per frequency range (e.g., FR1 or FR2), whether the processing gap affects LTE; and / or (4) how many PRS resources, resource sets, or instances can be processed within a processing gap of this length. In some cases, the location of the start / offset of the processing gap may depend on the UE ID.

[0196] To configure a processing gap for a UE, a location server (e.g., LMF 270) may first transmit an on-demand PRS configuration and a suggestion or recommendation or a request or request for a processing gap for the UE to a serving base station of the UE. Note that the location server may not need to transmit the requested processing gap at the same time (e.g., in the same message) as the on-demand PRS configuration. Second, the serving base station may transmit a response to the location server. The response may be an acceptance of the requested processing gap or a configuration of a different processing gap. Third, the location server transmits assistance data for the positioning session to the UE. The assistance data includes the PRS configuration and the associated processing gap.

[0197] In some cases, the UE may utilize autonomous processing gaps (i.e., autonomous PRS prioritization). In such cases, after a PRS instance, if no measurement gap is configured, the UE may drop or ignore all other traffic for a certain period of time without notifying the serving base station. In one aspect, there may be a maximum window in which the UE is allowed to perform these autonomous PRS prioritizations. As an example, the UE may expect to complete PRS processing within "X" ms (e.g., 6 ms) after the end of a PRS instance, and within this "X" milliseconds, the UE may select a period of "Y" ms (where "Y" is less than "X", e.g., 4 ms) during which the UE autonomously prioritizes PRS over other channels. During this window, it is up to the UE to decide whether to drop or ignore any other channels and processes (e.g., CSI processes) - the serving base station will not suppress transmission to the UE.

[0198] In one aspect, the processing gap information (e.g., processing gap offset) may be implicitly determined by UE-specific parameters. For example, using a modulo operation with the UE's ID may result in the UEs measuring the same PRS instance and still time-division multiplexing their PRS processing (e.g., Fig. 9 ).

[0199] In one aspect, the serving base station may configure the UE using a MAC control element (MAC-CE) or DCI, rather than the location server configuring the processing gap for the UE via the LPP.

[0200] Typically, DL-PRS has a lower priority than other channels in LTE and NR. This is because when no measurement gaps are configured for the UE, the UE is not expected to process DL-PRS in the same symbol as other downlink signals and channels sent to the UE. However, if a higher priority for DL-PRS than other channels is supported, various factors should be considered.

[0201] Currently, the working assumption for PRS processing without measurement gaps (also referred to as "no measurement gap" PRS processing or "no MG" PRS processing) is that, subject to UE capabilities, PRS measurements should be supported outside of measurement gaps and within the PRS processing window (e.g. Fig. 9 As exemplified and referenced in Fig. 9 In addition, UE measurements within an active downlink BWP whose PRS has the same parameter set as the UE's active downlink BWP should be supported.

[0202] Within the PRS processing window (such as Fig. 9 As exemplified and referenced in Fig. 9As described above, subject to the UE determining DL-PRS as a higher priority, the following UE capabilities are expected to be supported. The first capability (referred to as "capability 1" or "type 1" capability) indicates whether the UE is able or expected to prioritize PRS over all other downlink signals / channels in all symbols within the PRS processing window. This capability includes two sub-capabilities. The first sub-capability (referred to as "capability 1A" or "type 1A" capability) indicates that downlink signals / channels from all downlink component carriers (CCs) (per UE) are affected. The second sub-capability (referred to as "capability 1B" or "type 1B" capability) indicates that only downlink signals / channels from a specific frequency band / CC(s) are affected.

[0203] For Type 1B capabilities, in some cases, the PRS may be in a CC of a first band, and if the UE attempts to perform PRS processing in this first CC / band, the PRS processing in another band may be affected. For example, in FR2, if the UE uses the same beam management across bands, performing PRS processing in one band (and performing beam management on those PRS) may affect the beams used in the data / control / reference signals in the second band. Therefore, additional signaling may be required. Specifically, the UE can report its capabilities regarding whether measurement gap-free PRS processing in one band will affect downlink reception in another band. The report can be per band pair (i.e., which band pairs will be affected) or per band combination (i.e., which band combinations will be affected).

[0204] The second UE capability (referred to as "capability 2" or "type 2" capability) indicates whether the UE is able or expected to prioritize PRS over other downlink signals / channels only in PRS symbols within the PRS processing window. Type 2 capabilities may be per CC or per frequency band and are higher level capabilities than type 1 capabilities. It is expected that the UE can declare the capability for PRS processing outside of measurement gaps.

[0205] In some designs, a PRS processing window is configured for each BWP. In some designs, a processing type (e.g., type 1A, type 1B, or type 2) can be associated with a PRS processing window if and only if multiple processing types per band in UE capability signaling are supported. As described above, the type 1A capability indicates that the UE can discard processing of any DL signal in any DL band and prioritize PRS processing within the PRS processing window. In some designs, it is not necessary to provide a band ID and CC ID associated with the PRS processing window. In some designs, a single priority indicator can be provided for the PRS processing window, which applies to all PRSs within the PRS processing window within the BWP (e.g., PRS processing windows on different BWPs may have different priority indicators). In some designs, the maximum number of PRS processing windows activated per BWP is 1. In some designs, the maximum number of PRS processing windows activated across all active DL BWPs is 4. In some designs, the maximum number of PRS processing windows activated concurrently across all active DL BWPs is 1.

[0206] For the purpose of this feature, it is contemplated to specify PRS related conditions, where the following conditions are selected: (1) only applicable to serving cell PRS, or (2) all PRS under the condition that applies to non-serving cell PRS. It should be noted that when the UE determines that other downlink signals / channels have higher priority than PRS measurement / processing, it is contemplated that the UE does not measure / process DL-PRS, which applies to all the above capability options.

[0207] In view of the above, further details on which downlink signals / channels should be prioritized over PRS would be helpful. In addition, it would be helpful to have further details on how the UE determines the priority of DL-PRS based on one or more of the following: (1) based on indication / configuration from the serving base station, or (2) other options (e.g., implicit, signaling from LMF, etc.).

[0208] FIG. 10A to FIG. 10C Tables 1000, 1030, and 1050, respectively, illustrate various feature groups associated with different types of PRS processing capabilities and corresponding components of these feature groups, according to aspects of the present disclosure. FIG. 10A to FIG. 10C In the acronym "MG" stands for "Measurement Gap".

[0209] In the present disclosure, a UE may declare a PRS processing window capability of type 1A, type 1B, type 2, or a combination thereof for PRS processing outside of a measurement gap. The UE may declare the capability to its serving base station (e.g., via RRC or MAC control element (MAC-CE) signaling) and / or a location server (e.g., via LPP) in one or more capability messages. In subsequent configuration / activation of the PRS processing window, if the UE has declared that it supports multiple PRS processing window types, the serving base station or location server may include explicit signaling indicating whether the type of the PRS processing window is type 1A, type 1B, or type 2. However, if the UE has declared a single type of PRS processing window capability, this field may be optional.

[0210] The signaling of the type of PRS processing window may be from the location server to the serving base station (e.g., via NR Positioning Protocol Type A (NRPPa)) to the UE (e.g., via RRC or MAC-CE), or from the base station to the UE (e.g., via RRC or MAC-CE), or from the location server to the UE (e.g., via LPP). For example, the location server may indicate to the base station that it wants the UE to apply a particular type of PRS processing window based on the UE's PRS processing capabilities, and in response, the base station will configure the UE to use / apply that type of PRS processing window.

[0211] In various aspects, the UE expects to be triggered with a single type of PRS processing window at a certain time. That is, the UE expects not to apply more than one type of PRS processing window at a certain time. The triggered PRS processing window type (Type 1A, Type 1B, or Type 2) can be applied (1) across all CCs, (2) in a single CC, or (3) in a single frequency band (or simply "band").

[0212] In various aspects, within the same type of PRS processing windows, the UE expects that the PRS processing windows do not overlap (1) across all CCs (e.g., more applicable to Type 1A), (2) within a CC (e.g., more applicable to Type 2), or (3) within a frequency band (e.g., more applicable to Type 1B).

[0213] In the event that the UE has declared a PRS processing window capability of type 1A, type 1B, type 2, or a combination thereof, the UE may also report its capability of the maximum number of positioning frequency layers (PFLs) that it can process for the declared type of PRS processing window. If the UE declares type 1A PRS processing window capability, then (1) a single PFL is assumed to be processed across all frequency bands, or (2) the UE separately reports the number of PFLs that the UE can process and the maximum number of PFLs that the UE can process (currently up to 4 PFLs), or (3) the maximum number of PFLs currently supported (4 PFLs) is applicable to PRS processing without measurement gaps. If the UE declares type 1B capability, then (1) the UE may be able to process a single PFL in each frequency band, or (2) the UE separately reports the number of PFLs that the UE can process and the maximum number of PFLs that the UE can process (currently up to 4 PFLs), or (3) the maximum number of PFLs currently supported (4 PFLs) is applicable to PRS processing without measurement gaps. If the UE declares Type 2 capability, then (1) the UE may be able to process a single PFL in each CC, or (2) the UE separately reports the number of PFLs that the UE can process and the maximum number of PFLs that the UE can process (currently up to 4 PFLs), or (3) the maximum number of PFLs currently supported (4 PFLs) applies to PRS processing without measurement gaps.

[0214] In some cases, even for Type 2 UEs (which typically have higher capabilities than Type 1A UEs or Type 1B UEs), the UE may support X CCs for downlink carrier aggregation (CA), but may only support up to Y PFLs for PRS processing without measurement gaps, where Y is less than X. For example, for the purpose of PRS processing, the UE may support only one PFL in each CC. As a more detailed example, the same UE may declare the following PFL-related capabilities: (1) four PFLs for both PRS processing based on measurement gaps and PRS processing without measurement gaps, (2) two PFLs for PRS processing window Type 1A, and (3) one PFL for PRS processing window Type 1B. Note that the legacy capability (i.e., up to four PFLs across all positioning methods across all frequency bands) may be interpreted as an upper limit across all types of PRS processing (i.e., Type 1A, Type 1B, and Type 2 based on measurement gaps and without measurement gaps).

[0215] In some aspects, the UE may send one or more capability messages to the first network entity, the one or more capability messages indicating one or more types of PRS processing windows that the UE can apply for PRS processing without measurement gaps, wherein each type of PRS processing window in the one or more types of PRS processing windows indicates a different capability of the UE to prioritize PRS processing over processing of other channels. On the other hand, the UE may receive a configuration message from the second network entity, the configuration message indicating one type of PRS processing window of the one or more types of PRS processing windows that the UE intends to use for processing PRS.

[0216] Fig.11 1 is a diagram 1100 illustrating an example PRS configuration for two TRPs (labeled “TRP1” and “TRP2”) operating in the same positioning frequency layer (labeled “positioning frequency layer 1”) in accordance with aspects of the present disclosure. For a positioning session, assistance data indicating the illustrated PRS configuration may be provided to the UE. Fig.11 In the example of , a first TRP ("TRP1") is associated with (e.g., transmits) two PRS resource sets labeled "PRS resource set 1" and "PRS resource set 2", and a second TRP ("TRP2") is associated with one PRS resource set labeled "PRS resource set 3". Each PRS resource set includes at least two PRS resources. Specifically, the first PRS resource set ("PRS resource set 1") includes PRS resources labeled "PRS resource 1" and "PRS resource 2", the second PRS resource set ("PRS resource set 2") includes PRS resources labeled "PRS resource 3" and "PRS resource 4", and the third PRS resource set ("PRS resource set 3") includes PRS resources labeled "PRS resource 5" and "PRS resource 6".

[0217] In some designs, for MG-free measurements within the active BW and PRS processing window (PPW) within the same parameter set, PRS may be measured if PRS is considered to have higher priority than other DL signals / channels under some conditions. These conditions include at least that the Rx timing difference between the PRS from the non-serving cell and the PRS from the serving cell is within a threshold. The LMF may transmit a request for specific PPW parameters to the serving gNB. In some designs, the UE may not be able to recommend / request a PPW. In some designs, multiple PPWs may be preconfigured and a single PPW may be activated using DL-MAC-CE.

[0218] In some designs, the main differences of MG-free measurements within PPW compared to MG-based PRS processing are: (i) UL signals / channels are not affected / interrupted during PPW, (ii) no RF retuning is required since the UE does not change the active BWP, (iii) better multiplexing of PRS with other channels / better interruption of DL traffic (at least for Type 1B / 2), and / or (iv) PRS is processed only within PPW and the UE is expected to be able to report at the end of the PPW.

[0219] The above Type 1A, Type 1B and Type 2 capabilities can be characterized as PPW types as follows:

[0220] Table 3: PPW types

[0221] In some designs as described above, the gNB uses RRC configuration to indicate PPW priority (e.g., providing a single priority indicator for the PPW that applies to all PRSs within the PPW). In one example, the UE may indicate support for two priority states, including state 1 and state 2, in which state 1, the PRS has a higher priority than DL channels, and in state 2, the PRS has a lower priority than DL channels. In another example, the UE may indicate support for three priority states, including state 1, state 2, and state 3, in which state 1, the PRS has a higher priority than DL channels, in state 2, the PRS has a lower priority than PDCCH and URLLC PDSCH and higher than other PDSCH / CSI-RS (e.g., the URLLC channel corresponds to a dynamically scheduled PDSCH whose PUCCH resources for carrying ACK / NAK are marked as high priority), and in state 3, the PRS has a lower priority than DL channels. In another example, the UE may indicate support for a single priority state; i.e., state 1 in which the PRS has a higher priority than all DL channels. In the various examples above, the relative priority between PRS and SSB is flexible and may vary.

[0222] In some designs, the UE may indicate support for more than one processing type and corresponding PRS processing capabilities on a frequency band. In some designs, the gNB may decide which processing type to use. In some designs described above, a PPW is configured for each DLBWP. In some designs, the PPW configuration includes a starting slot, periodicity, duration / length, SCS information, priority, and processing type. In some designs described above, for example:

[0223] • Configure PPW for each DL BWP.

[0224] • If and only if multiple processing types per frequency band in the UE capability signaling is supported, the processing type (to be selected from 1A, 1B or 2) will be provided to be associated with the PPW.

[0225] • There is no need to provide the band ID and CC ID associated with the PPW.

[0226] • A single priority indicator is provided for a PPW, which applies to all PRSs within the PPW of the corresponding DL BWP.

[0227] The maximum number of PPWs preconfigured per DL BWP is 4.

[0228] The maximum number of PPWs that can be activated / deactivated by a DL MAC CE is 1.

[0229] • At each single instance of a PPW, a single PFL can be measured.

[0230] • The maximum number of PPWs activated per DL BWP is 1, and the maximum number across all active DL BWPs is 4.

[0231] • The maximum number of activated PPWs that overlap in time across all active DL BWPs is one.

[0232] An example of MG mode configuration is as follows:

[0233] <![CDATA[ Gap Mode ID ]]> <![CDATA[ MG length (ms) ]]> <![CDATA[ MG repetition period (ms) ]]> 0 6 40 1 6 80 2 3 40 3 3 80 4 6 20 5 6 160 6 4 20 7 4 40 8 4 80 9 4 160 10 3 20 11 3 160 12 5.5 20 13 5.5 40 14 5.5 80 15 5.5 160 16 3.5 20 17 3.5 40 18 3.5 80 19 3.5 160 20 1.5 20 21 1.5 40 22 1.5 80 23 1.5 160 24 10 80 25 20 160

[0234] Table 4: MG mode configuration

[0235] In one aspect, the MG mode configuration may be pre-configured via RRC. Each MG mode configuration may be associated with a specific gap pattern ID. For example, with respect to the MG mode configurations described in Table 4, gap pattern IDs 24 and 25 are specifically defined for NR positioning. In one aspect, information in the UL MAC CE for an MG activation request by a UE may include a gap pattern ID associated with the MG. In one aspect, the MG activation request may be sent by the UE (e.g., via UCI or UL MAC CE) or via an LMF (e.g., via an NRPPa message, which may be transparent to the UE). In one aspect, the UE may be pre-configured with multiple MG IDs, and the UE may use the UL MAC CE to activate or deactivate any particular configured MG. In some designs, the IE PosMeasGapPreConfig may provide the MG mode configuration. The IEPosMeasGapPreConfig may include a preConfigGapID field indicating a preconfigured MG configuration ID and a measGapConfig field indicating a preconfigured MG configuration.

[0236] Fig.12 The PPW activation / deactivation procedure 1200 according to various aspects of the present disclosure is illustrated. In one aspect, the PPW activation / deactivation procedure 1200 is used by the network to provide the UE with a PRS processing window for NR DL-PRS measurement without a measurement gap. The gNB may activate the pre-configured PRS processing window upon receiving a request from the LMF. Fig.12 :

[0237] 1. The LMF provides the serving gNB 304 with the PRS information of the neighboring TRPs and requests the serving gNB 304 to pre-configure the PRS processing window configuration via the NRPPa Measurement Pre-Configuration Required message.

[0238] 2a-2b. Based on UE capabilities, the serving gNB provides the UE with a pre-configured PRS processing window configuration with an associated ID by transmitting an RRC reconfiguration.

[0239] 3. The gNB transmits a confirmation message indicating the success of the pre-configuration to the LMF via the NRPPa Measurement Pre-configuration Confirm message.

[0240] 4. The LMF transmits the NRPPa Measurement Activation message to request the gNB to (de)activate the pre-configured PRS processing window.

[0241] 5. Based on the request from the LMF in step 4, the gNB transmits a DL MAC CE PPW Activate / Deactivate Command containing the ID for (de)activating the associated PRS processing window.

[0242] In some designs, the procedures for pre-configuration and activation / deactivation of MG and PPW for positioning can be unified (e.g., a procedure similar to PPW activation / deactivation procedure 1200 can be used as MG activation / deactivation procedure). In some designs, UE DL-PRS processing capabilities outside of the MG can be included in the NRPPa measurement pre-configuration requirement message. In some designs, information about what has been pre-configured in the target device (MG and / or PPW) can be included in the NRPPa measurement activation message to activate / deactivate the pre-configured PPW. In some designs, the NRPPa measurement activation message can be used to activate / deactivate the pre-configured PPW. In some designs, a UL MAC-CE for PPW activation / deactivation request can be defined. In some designs, UE capabilities for UL / DL MAC-CE-based PPW activation can be defined (e.g., by analogy to similar aspects for UL / DL MAC-CE-based MG activation).

[0243] In some designs, the PPW configuration may be provided in IEBWP-DownlinkDedicated. More specifically, IEDL-PRS-ProcessingWindowPreConfig specifies a measurement window in which the UE may receive data (e.g., PDCCH / PDSCH) and CSI-RS while also performing DL-PRS measurements in the configured window. In some designs, the fields of IEDL-PRS-ProcessingWindowPreConfig are as follows:

[0244]

[0245] Table 5: DL-PRS-ProcessingWindowConfig field description

[0246] In some designs, a first set of PRS processing capabilities of the UE may be defined within the MG (e.g., via IENNR-DLPRS-ProcessingCapability-r16 and PRS-ProcessingCapabilityPerBand-r16), and a second set of PRS processing capabilities may be defined outside the MG or for the PPW. For example, the second set of PRS processing capabilities may include DL PRS buffering capabilities (e.g., type 1 - sub-slot / symbol level buffering or type 2 - slot level buffering), a maximum duration N of DL PRS symbols that the UE can process in the first part of the PPW in ms (assuming a maximum DL PRS bandwidth in MHz, such that the UE can report measurements T-Nms after the last PRS symbol), and a maximum number of DL PRS resources that the UE can process in a slot. In some designs, N may be selected from {0.125, 0.25, 0.5, 1, 2, 3, 4, 5, 6, 8, 12} ms, and T may be selected from {N+4, N+5, N+6, N+8} ms. In some designs, where a UE supports multiple types in a frequency band, the UE may declare a PRS processing capability for each supported Type 1A, Type 1B, or Type 2 capability.

[0247] With respect to UE capabilities, a particular UE may have the option to measure PRS resources within the MG as well as outside the MG (eg, in the PPW), such as Fig.13 As depicted in . Fig.13 1 illustrates a BWP configuration 1300 according to aspects of the present disclosure. Fig.131, the BWP configuration 1300 includes a PFL (PFL1) having one or more PRS resources to be measured by the UE. The UE is configured with both a MG (MG1) and a PPW (PPW1) which overlaps with PFL1 in time. In this case, either the configured MG1 or the configured PPW1 may be activated to perform PRS measurements of the PRS resources of PFL1 in the active BWP.

[0248]

[00136] In some designs, to improve latency, the network may preconfigure a set of MG IDs per PFL. The UE may select a specific MG ID to handle PRS processing in the MG. The UE may activate or deactivate the MG ID via UL MAC CE. To measure PRS outside the MG, the network may preconfigure a set of PPW IDs per PFL. The UE may select a specific PPW ID to handle PRS processing outside the MG. The UE may activate or deactivate the PPW ID via UL MAC CE.

[0249] In some designs, a PPW may be associated with a restricted number. For example, in some designs, for PPW-based processing, the UE is only allowed to measure the PFL within the active BWP. In some designs, for PPW-based processing, if another channel has a higher priority than the PRS signal (e.g., SSB processing, etc.), the UE may need to measure other channels within the PPW. In some designs, for PPW-based processing, if another channel has a lower priority than the PRS signal, the UE will not measure other channels within the PPW. In some designs, the priority of the PRS signal may be conveyed to the UE by the LMF / gNB.

[0250] Various aspects of the present disclosure are directed to selecting a measurement window type (e.g., MG or PPW) for performing measurement processing on each instance of a PFL for a positioning session for a UE based on one or more selection criteria. Such aspects can provide various technical advantages, such as improved position estimation accuracy, reduced position estimation latency, etc. (e.g., via selecting a more appropriate measurement window type for a particular positioning session).

[0251] Fig.14 An exemplary process 1400 of communicating according to one aspect of the present disclosure is illustrated. Fig.14 Process 1400 is performed by a UE such as UE 302.

[0252] refer to Fig.14At 1410, UE 302 (e.g., receiver 312 or 322, etc.) receives a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP). In one aspect, the configuration of the PPW for the active BWP may be received via L3 signaling (such as RRC signaling). In one aspect, means for performing the reception of 1410 may include Figure 3A The receiver 312 or 322 of the UE 302 .

[0253] refer to Fig.14 At 1420, UE 302 (e.g., receiver 312 or 322, etc.) receives a configuration of a measurement gap (MG). In one aspect, the PPW and the MG include an overlapping time domain portion that includes an instance of a positioning frequency layer (PFL) for a positioning session of the UE (e.g., as illustrated in FIG. Fig.13 In one aspect, the configuration of the MG may be received via L3 signaling (such as RRC signaling). In one aspect, the means for performing the receiving of 1420 may include Figure 3A Receiver 312 or 322 of UE 302.

[0254] refer to Fig.14 At 1430, the UE 302 (e.g., the processor 332, the positioning component 342, etc.) selects a measurement window type corresponding to the PPW or MG for performing measurement processing for each instance of the PFL for the positioning session of the UE based on one or more selection criteria. In one aspect, the means for performing the selection of 1430 may include Figure 3A The processor 332, positioning component 342, etc. of the UE 302.

[0255] refer to Fig.14 At 1440, the UE 302 (e.g., the receiver 312 or 322, the processor 332, the positioning component 342, etc.) performs a measurement process for each instance of the PFL for the positioning session via the selected measurement window type. In one aspect, the component for performing the measurement process of 1440 may include Figure 3A The receiver 312 or 322, processor 332, positioning component 342, etc. of the UE 302.

[0256] Fig.15 An exemplary process 1500 of communicating according to one aspect of the present disclosure is illustrated. Fig.15 The process 1500 is performed by a network component (e.g., BS 304 or a network entity 306 such as LMF or an O-RAN component such as RU / CU / DU, etc.).

[0257] refer to Fig.15At 1510, a network component (e.g., a transmitter 354 or 364, a network interface 380 or 390, etc.) transmits a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP). In one aspect, the configuration of the PPW of the active BWP may be transmitted via L3 signaling (such as RRC signaling). In one aspect, means for performing the transmitting of 1510 may include a transmitter 354 or 364, a network interface 380 or 390, etc. of a network component (e.g., in an example where the network component corresponds to BS 304).

[0258] refer to Fig.15 At 1520, a network component (e.g., a transmitter 354 or 364, a network interface 380 or 390, etc.) transmits a configuration of a measurement gap (MG). In one aspect, the PPW and the MG include an overlapping time domain portion that includes an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE). In one aspect, the configuration of the MG may be transmitted via L3 signaling (such as RRC signaling). In one aspect, the means for performing the transmission of 1520 may include a transmitter 354 or 364, a network interface 380 or 390, etc. of a network component (e.g., in an example where the network component corresponds to BS 304).

[0259] refer to Fig.15 At 1530, a network component (e.g., processor 384 or 394, positioning component 388 or 398, etc.) selects a measurement window type corresponding to a PPW or MG for performing measurement processing for each instance of a PFL for a positioning session for the UE based on one or more selection criteria. In one aspect, means for performing the selection of 1530 may include processor 384 or 394, positioning component 388 or 398, etc. of the network component (e.g., in an example where the network component corresponds to BS 304).

[0260] refer to Fig.15 At 1540, the network component (e.g., transmitter 354 or 364, network interface 380 or 390, etc.) sends to the UE an activation of the selected measurement window type for performing measurement processing on each instance of the PFL for the positioning session. In one aspect, the configuration of the MG may be sent via L1 signaling (e.g., DCI, etc.), L2 signaling (e.g., MAC CE, etc.), or L3 signaling (e.g., RRC, etc.). In one aspect, the means for performing the sending of 1540 may include the transmitter 354 or 364, the network interface 380 or 390, etc. of the network component (e.g., in an example where the network component corresponds to BS 304).

[0261] refer to Figure 14 to Figure 15In some designs, one or more selection criteria include a first measurement period for PPW-based processing of a PPW of an instance of the PFL, and a second measurement period for MG-based processing of an MG of an instance of the PFL. In one aspect, the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period. For example, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period may be selected for the selected measurement window type based on network requirements. Alternatively, the selected measurement window type is associated with the longer of the first measurement period and the second measurement period. In this case, as an example, a corresponding measurement window type associated with the longer of the first measurement period and the second measurement period may be selected for the selected measurement window type based on decision logic (e.g., UE or network component decision logic) without a network requirement requiring the UE or network component to select the selected measurement window type based on the measurement period duration.

[0262] refer to Figure 14 to Figure 15 In some designs, the one or more selection criteria include a first measurement result latency of the PPW based on the processing of the PPW via the measurement of the PFL, and a second measurement result latency of the MG based on the processing of the MG via the measurement of the PFL. In one aspect, Fig.14 1430 or Fig.15 The selection of 1530 may select, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement result delay and the second measurement result delay.

[0263] In a specific example, it is assumed that each PFL of a positioning session is associated with a single measurement period (P_i). When the UE is associated with multiple PFLs, the measurement period is sum(P_i), assuming TDM of the PFLs. It is further assumed that the MG or PPW is used to measure a single PFL, and a single PFL is configured. Now, it is further assumed that the UE is configured with both the MG and the PPW to measure the PFL. In one aspect, if the UE measures based on the MG, a first measurement period (P11) may be used because the measurement period depends on the periodicity of the MG. In one aspect, if the UE measures based on the PPW, a second measurement period may be defined because the measurement period depends on the periodicity of the PPW. In some designs, it is expected that the UE utilizes the MG or PPW for all PRS measurements associated with the positioning session (e.g., the UE cannot pick and choose). In some designs, the selected measurement window type (e.g., MG or PPW) may be selected as min(P11, P12) or max(P11, P12). In other words, in one aspect, depending on which of the MG or PPW is fastest (e.g., min(P11, P12)), the UE is expected to make measurements based on the MG or PPW, or is allowed to make one or the other (e.g., max(P11, P12), etc.). In one aspect, the UE decision logic for selection can be generalized as a function of P11, P12, i.e., F(P11, P12). In one aspect, both the selection of the MG or PPW and the measurement period can be jointly determined as a function of P11 and P12. For example, in special cases, the UE can first decide between the MG and the PPW, and then follow the measurement period rules of whatever is decided. Although the above is relative to such Fig.14 1430 is described based on the UE selection, but it should be understood that similar decision logic can be implemented at the network component for Fig.15 The 1530 selections.

[0264] refer to Figure 14 to Figure 15 In some designs, the one or more selection criteria include a first priority level for PPW-based processing of the PPW via measurements of the PFL, or a second priority level for MG-based processing of the MG via measurements of the PFL, or a combination thereof. In some designs, the first priority level, the second priority level, or both are indicated to the UE by a network component. For example, in some designs, the LMF may indicate the priority to the UE. In one aspect, if the MG has a higher priority, the UE (e.g., in Fig.14 ) or network components (e.g. Fig.15 In the case of MG, the UE will first seek the MG, and if the MG is not pre-configured, the UE or network component will select the PPW. In one aspect, if the PPW has a higher priority, the UE (e.g., Fig.14 ) or network components (e.g. Fig.15 In another example, the first priority level for PPW-based processing may be based on the priority of PRS resources within the PPW (outside the MG). For example, there may be situations where other DL channels may be of higher priority than PRS within the PPW. In this case, the UE or network component will prioritize the selection of MG over PPW in this case. Alternatively, there may be situations where PRS is of higher priority than other DL channels within the PPW. In this case, the UE or network component will prioritize the selection of PPW over MG.

[0265] refer to Figure 14 to Figure 15 In some designs, one or more selection criteria include a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof. In another aspect, one or more selection criteria include a radio frequency (RF) tuning budget. For example, in the case of the MG, the UE can perform RF tuning in and out. In the case of the PPW, there is no RF tuning in and out time, and the full PPW can be used for PRS processing. Therefore, the RF tuning budget and / or PRS processing capability can be taken into account in the selection of the PPW by the MG. In addition, the PPW and MG IDs can be configured with different lengths, and the corresponding lengths can be taken into account in the selection of the PPW by the MG.

[0266] refer to Figure 14 to Figure 15 In some designs, the one or more selection criteria include an available bandwidth (BW) to be measured. In some designs, the one or more selection criteria include a first power consumption level associated with PPW-based processing of the PPW of the measurements via the PFL, and a second power consumption level associated with MG-based processing of the MG of the measurements via the PFL. For example, the corresponding power consumption level may be based in part on resynchronization associated with the MG-based processing. In one aspect, the UE may select (e.g., based on battery power, etc.) a corresponding measurement window type associated with more power consumption or less power consumption.

[0267] refer to Figure 14 to Figure 15In some designs, one or more selection criteria include a radio resource management (RRM) state associated with the MG. For example, the MG may already be configured / activated for RRM measurements. In this case, the same MG may also be used to measure PRS resources for the PFL. The UE may also be pre-configured with a PPW for the PFL. In this case, in one aspect, the UE or network component may avoid configuring / activating the PPW and may instead use the already configured / activated MG for processing. Note that the MG may or may not be in the pre-configured gap list for the PFL.

[0268] refer to Figure 14 to Figure 15 In some designs, one or more selection criteria include a first periodicity of the PPW and a second periodicity of the MG. For example, the PPW and the MG may be configured with different periodicities. In one aspect, the UE or network component may select the PPW or MG that is more aligned with the PRS periodicity (e.g., one that overlaps with more PRS resources associated with the positioning session).

[0269] refer to Figure 14 to Figure 15 In some designs, one or more selection criteria include a service level outside the MG and within the PPW. For example, Fig.16 A BWP configuration 1600 is illustrated in accordance with aspects of the present disclosure. Fig.16 Similar to Fig.16 , except that high priority traffic communication 1602 is scheduled to be outside of MG1 and within PPW1. Assume that the UE or network component selects between MG1 and PPW1 before MG1 starts. In this case, the UE or network component can determine that if PPW1 is selected, the UE will drop the PRS due to the presence of high priority traffic communication 1602. However, if MG1 is selected, there is no such conflict. Therefore, in this case, the UE or network component can be manipulated to select MG1 instead of PPW1.

[0270] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each subordinate clause can refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to specific combinations. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is explicitly expressed or can be easily inferred that a specific combination is not intended (for example, contradictory aspects, such as defining an element as an insulator and a conductor). In addition, it is also expected that various aspects of the clause can be included in any other independent clause, even if the clause is not directly subordinate to the independent clause.

[0271] Specific implementation examples are described in the following numbered clauses:

[0272] Clause 1. A method of operating a user equipment (UE), the method comprising: receiving a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); receiving a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and performing the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0273] Clause 2. The method of clause 1, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0274] Clause 3. The method of clause 2, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0275] Clause 4. The method of clause 3, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0276] Clause 5. The method of any of clauses 2 to 4, wherein the selected measurement window type is associated with the longer of the first measurement period and the second measurement period.

[0277] Clause 6. A method according to clause 5, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement cycle and the second measurement cycle for the selected measurement window type based on UE decision logic in the absence of a network requirement requiring the UE to select the selected measurement window type based on the measurement cycle duration.

[0278] Clause 7. A method according to any one of clauses 1 to 6, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0279] Clause 8. The method of clause 7, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement latency and the second measurement latency.

[0280] Clause 9. A method according to any one of clauses 1 to 8, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0281] Clause 10. The method of clause 9, wherein the first priority level, the second priority level, or both are indicated to the UE by a network component.

[0282] Clause 11. A method according to any one of clauses 1 to 10, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0283] Clause 12. The method of any one of clauses 1 to 11, wherein the one or more selection criteria comprises: a radio frequency (RF) tuning budget.

[0284] Clause 13. The method of any one of clauses 1 to 12, wherein the one or more selection criteria include: available bandwidth (BW) to be measured.

[0285] Clause 14. A method according to any one of clauses 1 to 13, wherein the one or more selection criteria include: a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL.

[0286] Clause 15. The method of any of clauses 1 to 14, wherein the one or more selection criteria comprises a radio resource management (RRM) state associated with the MG.

[0287] Clause 16. The method of any of clauses 1 to 15, wherein the one or more selection criteria include: a first periodicity of the PPW, and a second periodicity of the MG.

[0288] Clause 17. The method of any of clauses 1 to 16, wherein the one or more selection criteria include: a traffic level outside the MG and within the PPW.

[0289] Clause 18. A method of operating a network component, the method comprising: sending a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); sending a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and sending to the UE an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0290] Clause 19. The method of clause 18, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0291] Clause 20. The method of Clause 19, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0292] Clause 21. The method of clause 20, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0293] Clause 22. The method of any of clauses 19 to 21, wherein the selected measurement window type is associated with the longer of the first measurement period and the second measurement period.

[0294] Clause 23. A method according to clause 22, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement cycle and the second measurement cycle for the selected measurement window type based on network component decision logic in the absence of a network requirement requiring the network component to select the selected measurement window type based on the measurement cycle duration.

[0295] Clause 24. A method according to any one of clauses 18 to 23, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0296] Clause 25. The method of clause 24, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement latency and the second measurement latency.

[0297] Clause 26. A method according to any one of clauses 19 to 25, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0298] Clause 27. A method according to any one of clauses 19 to 26, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0299] Clause 28. A method according to any one of clauses 19 to 27, wherein the one or more selection criteria include: an available bandwidth (BW) to be measured, or a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL, or a radio resource management (RRM) state associated with the MG, or a first periodicity of the PPW and a second periodicity of the MG, or a traffic level outside the MG and within the PPW, or any combination thereof.

[0300] Clause 29. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); receive, via the at least one transceiver, a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; select, based on one or more selection criteria, a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE; and perform the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0301] Clause 30. A UE according to clause 29, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW via the instance of the PFL, and a second measurement period of MG-based processing of the MG via the instance of the PFL.

[0302] Clause 31. The UE of clause 30, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0303] Clause 32. The UE of clause 31, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0304] Clause 33. A UE as set forth in any of clauses 30 to 32, wherein the selected measurement window type is associated with the longer of the first measurement period and the second measurement period.

[0305] Clause 34. A UE according to clause 33, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement cycle and the second measurement cycle for the selected measurement window type based on UE decision logic in the absence of a network requirement requiring the UE to select the selected measurement window type based on the measurement cycle duration.

[0306] Clause 35. A UE according to any one of clauses 29 to 34, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0307] Clause 36. The UE of clause 35, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement result latency and the second measurement result latency.

[0308] Clause 37. A UE according to any one of clauses 29 to 36, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0309] Clause 38. The UE of clause 37, wherein the first priority level, the second priority level, or both are indicated to the UE by a network component.

[0310] Clause 39. A UE according to any one of clauses 29 to 38, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0311] Clause 40. A UE as set forth in any of clauses 29 to 39, wherein the one or more selection criteria comprises: a radio frequency (RF) tuning budget.

[0312] Clause 41. A UE as set forth in any of clauses 29 to 40, wherein the one or more selection criteria comprises: an available bandwidth (BW) to be measured.

[0313] Clause 42. A UE according to any one of clauses 29 to 41, wherein the one or more selection criteria include: a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL.

[0314] Clause 43. A UE as set forth in any of clauses 29 to 42, wherein the one or more selection criteria comprises a radio resource management (RRM) state associated with the MG.

[0315] Clause 44. A UE as set forth in any of clauses 29 to 43, wherein the one or more selection criteria comprise: a first periodicity of the PPW, and a second periodicity of the MG.

[0316] Clause 45. A UE as set forth in any of clauses 29 to 44, wherein the one or more selection criteria comprise: a traffic level outside the MG and within the PPW.

[0317] Clause 46. A network component, the network component comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send, via the at least one transceiver, a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); send, via the at least one transceiver, a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); select, based on one or more selection criteria, a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE; and send, via the at least one transceiver, to the UE, an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0318] Clause 47. A network component according to clause 46, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0319] Clause 48. The network component of Clause 47, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0320] Clause 49. The network component of Clause 48, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0321] Clause 50. A network component as recited in any of Clauses 47 to 49, wherein the selected measurement window type is associated with the longer of the first measurement period and the second measurement period.

[0322] Clause 51. A network component according to clause 50, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement period and the second measurement period for the selected measurement window type based on network component decision logic in the absence of a network requirement requiring the network component to select the selected measurement window type based on the measurement period duration.

[0323] Clause 52. A network component according to any one of clauses 46 to 51, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0324] Clause 53. The network component of Clause 52, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with a shorter of the first measurement latency and the second measurement latency.

[0325] Clause 54. A network component according to any one of clauses 47 to 53, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0326] Clause 55. A network component according to any one of clauses 47 to 54, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0327] Clause 56. A network component according to any one of clauses 47 to 55, wherein the one or more selection criteria include: available bandwidth (BW) to be measured, or a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL, or a radio resource management (RRM) state associated with the MG, or a first periodicity of the PPW and a second periodicity of the MG, or a traffic level outside the MG and within the PPW, or any combination thereof.

[0328] Clause 57. A user equipment (UE), comprising: a component for receiving a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); a component for receiving a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; a component for selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and a component for performing the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0329] Clause 58. A UE according to clause 57, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0330] Clause 59. The UE of clause 58, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0331] Clause 60. The UE of clause 59, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0332] Clause 61. A UE as set forth in any of clauses 58 to 60, wherein the selected measurement window type is associated with the longer of the first measurement period and the second measurement period.

[0333] Clause 62. A UE according to clause 61, wherein the selection selects the corresponding measurement window type associated with the longer of the first measurement cycle and the second measurement cycle for the selected measurement window type based on UE decision logic in the absence of a network requirement requiring the UE to select the selected measurement window type based on the measurement cycle duration.

[0334] Clause 63. A UE according to any one of clauses 57 to 62, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0335] Clause 64. The UE of clause 63, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement result latency and the second measurement result latency.

[0336] Clause 65. A UE according to any one of clauses 57 to 64, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0337] Clause 66. The UE of clause 65, wherein the first priority level, the second priority level, or both are indicated to the UE by a network component.

[0338] Clause 67. A UE according to any of clauses 57 to 66, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0339] Clause 68. A UE as set forth in any of clauses 57 to 67, wherein the one or more selection criteria comprises: a radio frequency (RF) tuning budget.

[0340] Clause 69. A UE as set forth in any of clauses 57 to 68, wherein the one or more selection criteria comprises: an available bandwidth (BW) to be measured.

[0341] Clause 70. A UE according to any one of clauses 57 to 69, wherein the one or more selection criteria include: a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL.

[0342] Clause 71. A UE as set forth in any of clauses 57 to 70, wherein the one or more selection criteria comprises: a radio resource management (RRM) state associated with the MG.

[0343] Clause 72. A UE as set forth in any of clauses 57 to 71, wherein the one or more selection criteria comprise: a first periodicity of the PPW, and a second periodicity of the MG.

[0344] Clause 73. A UE as set forth in any of clauses 57 to 72, wherein the one or more selection criteria comprise: a traffic level outside the MG and within the PPW.

[0345] Clause 74. A network component comprising: means for sending a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); means for sending a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); means for selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and means for sending to the UE an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0346] Clause 75. A network component according to clause 74, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0347] Clause 76. The network component of Clause 75, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0348] Clause 77. The network component of Clause 76, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0349] Clause 78. A network component as recited in any of Clauses 75 to 77, wherein the selected measurement window type is associated with the longer of the first measurement period and the second measurement period.

[0350] Clause 79. A network component according to clause 78, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement cycle and the second measurement cycle for the selected measurement window type based on network component decision logic in the absence of a network requirement requiring the network component to select the selected measurement window type based on the measurement cycle duration.

[0351] Clause 80. A network component according to any one of clauses 74 to 79, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0352] Clause 81. The network component of clause 80, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with a shorter of the first measurement latency and the second measurement latency.

[0353] Clause 82. A network component according to any one of clauses 75 to 81, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0354] Clause 83. A network component according to any one of clauses 75 to 82, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0355] Clause 84. A network component according to any one of clauses 75 to 83, wherein the one or more selection criteria include: available bandwidth (BW) to be measured, or a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL, or a radio resource management (RRM) state associated with the MG, or a first periodicity of the PPW and a second periodicity of the MG, or a traffic level outside the MG and within the PPW, or any combination thereof.

[0356] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); receive a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; select a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and perform the measurement processing on each instance of the PFL for the positioning session via the selected measurement window type.

[0357] Clause 86. A non-transitory computer-readable medium as described in clause 85, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0358] Clause 87. The non-transitory computer-readable medium of Clause 86, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

[0359] Clause 88. The non-transitory computer-readable medium of Clause 87, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0360] Clause 89. The non-transitory computer-readable medium of any one of Clauses 86 to 88, wherein the selected measurement window type is associated with a longer of the first measurement period and the second measurement period.

[0361] Clause 90. A non-transitory computer-readable medium according to clause 89, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement period and the second measurement period for the selected measurement window type based on UE decision logic in the absence of a network requirement requiring the UE to select the selected measurement window type based on a measurement period duration.

[0362] Clause 91. A non-transitory computer-readable medium according to any one of clauses 85 to 90, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0363] Clause 92. The non-transitory computer-readable medium of Clause 91, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with a shorter of the first measurement latency and the second measurement latency.

[0364] Clause 93. A non-transitory computer-readable medium as described in any of clauses 85 to 92, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0365] Clause 94. The non-transitory computer-readable medium of clause 93, wherein the first priority level, the second priority level, or both are indicated to the UE by a network component.

[0366] Clause 95. A non-transitory computer-readable medium according to any one of clauses 85 to 94, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0367] Clause 96. The non-transitory computer-readable medium of any one of clauses 85 to 95, wherein the one or more selection criteria comprises: a radio frequency (RF) tuning budget.

[0368] Clause 97. The non-transitory computer-readable medium of any one of clauses 85 to 96, wherein the one or more selection criteria include: an available bandwidth (BW) to be measured.

[0369] Clause 98. A non-transitory computer-readable medium as described in any of clauses 85 to 97, wherein the one or more selection criteria include: a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL.

[0370] Clause 99. The non-transitory computer-readable medium of any of clauses 85 to 98, wherein the one or more selection criteria comprises: a radio resource management (RRM) state associated with the MG.

[0371] Clause 100. The non-transitory computer-readable medium of any one of clauses 85 to 99, wherein the one or more selection criteria include: a first periodicity of the PPW, and a second periodicity of the MG.

[0372] Clause 10 1. The non-transitory computer-readable medium of any of clauses 85 to 100, wherein the one or more selection criteria comprises: a traffic level external to the MG and within the PPW.

[0373] Clause 102. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: send a configuration of a positioning reference signal (PRS) processing window (PPW) for an active bandwidth part (BWP); send a configuration of a measurement gap (MG), wherein the PPW and the MG include overlapping time domain portions, the overlapping time domain portions including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); select a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; and send to the UE an activation of the selected measurement window type for performing the measurement processing on each instance of the PFL for the positioning session.

[0374] Clause 103. A non-transitory computer-readable medium as described in clause 102, wherein the one or more selection criteria include: a first measurement period of PPW-based processing of the PPW of the instance of the PFL, and a second measurement period of MG-based processing of the MG of the instance of the PFL.

[0375] Clause 104. The non-transitory computer-readable medium of Clause 103, wherein the selected measurement window type is associated with a shorter of the first measurement period and the second measurement period.

[0376] Clause 105. The non-transitory computer-readable medium of clause 104, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

[0377] Clause 106. The non-transitory computer-readable medium of any one of Clauses 103 to 105, wherein the selected measurement window type is associated with a longer of the first measurement period and the second measurement period.

[0378] Clause 107. A non-transitory computer-readable medium according to clause 106, wherein the selection selects a corresponding measurement window type associated with the longer of the first measurement period and the second measurement period for the selected measurement window type based on network component decision logic in the absence of a network requirement requiring the network component to select the selected measurement window type based on the measurement period duration.

[0379] Clause 108. A non-transitory computer-readable medium according to any one of clauses 102 to 107, wherein the one or more selection criteria include: a first measurement result latency of PPW-based processing of the PPW measured via the PFL, and a second measurement result latency of MG-based processing of the MG measured via the PFL.

[0380] Clause 109. The non-transitory computer-readable medium of Clause 108, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with a shorter of the first measurement latency and the second measurement latency.

[0381] Clause 110. A non-transitory computer-readable medium as described in any of clauses 103 to 109, wherein the one or more selection criteria include: a first priority level for PPW-based processing of the PPW via the measurement of the PFL, or a second priority level for MG-based processing of the MG via the measurement of the PFL, or a combination thereof.

[0382] Clause 111. A non-transitory computer-readable medium as described in any of clauses 103 to 110, wherein the one or more selection criteria include: a first PRS processing capability of the UE within the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or a combination thereof.

[0383] Clause 112. A non-transitory computer-readable medium as described in any of clauses 103 to 111, wherein the one or more selection criteria include: an available bandwidth (BW) to be measured, or a first power consumption level associated with PPW-based processing of the PPW of the measurement via the PFL, and a second power consumption level associated with MG-based processing of the MG of the measurement via the PFL, or a radio resource management (RRM) state associated with the MG, or a first periodicity of the PPW and a second periodicity of the MG, or a traffic level outside the MG and within the PPW, or any combination thereof.

[0384] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0385] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0386] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0387] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0388] In one or more example aspects, the described functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, and the communication media include any media that facilitates the transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other media that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server, or other remote sources using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.

[0389] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure as described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method of operating a user equipment (UE), the method comprising: Configuration of the Positioning Reference Signal (PRS) Processing Window (PPW) for the receive active bandwidth part (BWP); receiving a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, the overlapping time domain portion including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; as well as The measurement process of each instance of the PFL for the positioning session is performed via the selected measurement window type.

2. The method of claim 1, wherein the one or more selection criteria include: a first measurement cycle of a PPW-based process of the PPW via the instance of the PFL, and A second measurement period of MG-based processing of the MG via the instance of the PFL. 3 . The method of claim 2 , wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period. 4 . The method of claim 3 , wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements. 5 . The method of claim 2 , wherein the selected measurement window type is associated with a longer of the first measurement period and the second measurement period.

6. The method of claim 5, wherein the selecting selects a corresponding measurement window type associated with the longer of the first measurement cycle and the second measurement cycle for the selected measurement window type based on UE decision logic in the absence of a network requirement requiring the UE to select the selected measurement window type based on a measurement cycle duration.

7. The method of claim 1, wherein the one or more selection criteria include: a first measurement result time delay of the PPW based on the processing of the PPW via the measurement of the PFL, and A second measurement result time delay of the MG based on MG processing of the measurement of the PFL.

8. The method of claim 7, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement delay and the second measurement delay.

9. The method of claim 1, wherein the one or more selection criteria include: a first priority level for PPW-based processing of said PPW via said measurement of said PFL, or a second priority level for MG-based processing of said MG via said measurement of said PFL, or A combination of them.

10. The method of claim 9, wherein the first priority level, the second priority level, or both are indicated to the UE by a network component.

11. The method of claim 1 , wherein the one or more selection criteria include: a first PRS processing capability of the UE in the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or A combination of them.

12. The method of claim 1, wherein the one or more selection criteria include: Radio frequency (RF) tuning budget.

13. The method of claim 1, wherein the one or more selection criteria include: The available bandwidth (BW) to be measured.

14. The method of claim 1, wherein the one or more selection criteria include: a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and A second power consumption level associated with MG-based processing of the MG via the measurement of the PFL.

15. The method of claim 1, wherein the one or more selection criteria include: A radio resource management (RRM) state associated with the MG.

16. The method of claim 1, wherein the one or more selection criteria include: a first periodicity of the PPW, and The second periodicity of the MG.

17. The method of claim 1, wherein the one or more selection criteria include: Traffic level outside the MG and within the PPW.

18. A method of operating a network component, the method comprising: Configuration of the Positioning Reference Signal (PRS) Processing Window (PPW) for transmitting the active bandwidth part (BWP); sending a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, the overlapping time domain portion including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; as well as An activation of the selected measurement window type for performing the measurement process for each instance of the PFL for the positioning session is sent to the UE.

19. The method of claim 18, wherein the one or more selection criteria include: a first measurement cycle of a PPW-based process of the PPW via the instance of the PFL, and A second measurement period of MG-based processing of the MG via the instance of the PFL.

20. The method of claim 19, wherein the selected measurement window type is associated with the shorter of the first measurement period and the second measurement period.

21. The method of claim 20, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement period and the second measurement period based on network requirements.

22. The method of claim 19, wherein the selected measurement window type is associated with a longer of the first measurement period and the second measurement period.

23. The method of claim 22, wherein the selecting selects a corresponding measurement window type associated with the longer of the first measurement period and the second measurement period for the selected measurement window type based on network component decision logic in the absence of a network requirement requiring the network component to select the selected measurement window type based on a measurement period duration.

24. The method of claim 18, wherein the one or more selection criteria include: a first measurement result time delay of the PPW based on the processing of the PPW via the measurement of the PFL, and A second measurement result time delay of the MG based on MG processing of the measurement of the PFL.

25. The method of claim 24, wherein the selecting selects, for the selected measurement window type, a corresponding measurement window type associated with the shorter of the first measurement latency and the second measurement latency.

26. The method of claim 19, wherein the one or more selection criteria include: a first priority level for PPW-based processing of said PPW via said measurement of said PFL, or a second priority level for MG-based processing of said MG via said measurement of said PFL, or A combination of them.

27. The method of claim 19, wherein the one or more selection criteria include: a first PRS processing capability of the UE in the MG, or a second PRS processing capability of the UE outside the MG and within the PPW, or A combination of them.

28. The method of claim 19, wherein the one or more selection criteria include: The available bandwidth (BW) to be measured, or a first power consumption level associated with PPW-based processing of the PPW via the measurement of the PFL, and a second power consumption level associated with MG-based processing of the MG via the measurement of the PFL, or the Radio Resource Management (RRM) state associated with the MG, or a first periodicity of the PPW and a second periodicity of the MG, or A service level outside the MG and within the PPW, or Any combination of them.

29. A user equipment (UE), the user equipment (UE) comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); receiving, via the at least one transceiver, a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, the overlapping time domain portion including an instance of a positioning frequency layer (PFL) for a positioning session of the UE; selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; as well as The measurement process of each instance of the PFL for the positioning session is performed via the selected measurement window type.

30. A network component, the network component comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmitting, via the at least one transceiver, a configuration of a positioning reference signal (PRS) processing window (PPW) of an active bandwidth part (BWP); transmitting, via the at least one transceiver, a configuration of a measurement gap (MG), wherein the PPW and the MG include an overlapping time domain portion, the overlapping time domain portion including an instance of a positioning frequency layer (PFL) for a positioning session of a user equipment (UE); selecting a measurement window type corresponding to the PPW or the MG for performing measurement processing on each instance of the PFL for the positioning session of the UE based on one or more selection criteria; as well as Activation of the selected measurement window type for performing the measurement process for each instance of the PFL for the positioning session is sent to the UE via the at least one transceiver.

Images