Capability signaling for positioning reference signal bandwidth aggregation across multiple positioning frequency layers

Abstract

Techniques for wireless communication are disclosed. In an aspect, a user equipment (UE) sends at least one provision capability message to a location server indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities include at least a total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receiving, from a location server, a location information request to report, based on the one or more capabilities, an aggregated measurement of the one or more DL-PRS resources, or positioning assistance data including DL-PRS resources for an aggregated destination link, or any combination thereof.

Description

BACKGROUND 1. TECHNICAL FIELD

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

[0002] 2. Related Art

[0003] Wireless communication systems have developed through various generations, including first-generation analog wireless telephones, second-generation (2G) digital wireless telephones, and third-generation (3G) high speed data modems, with Internet capability. Today's wireless communication systems are currently in a transitional stage, where different technologies coexist. For example, 2G systems such as 2.5G and 2.75G, 3G systems, and pre-5G systems are being used concurrently. The next generation wireless communication systems, referred to as 5G, are now being developed. It is expected that 5G systems will deliver much higher data rates, greater numbers of connected devices, and lower latency relative to current 3G and 4G wireless communications systems.

[0004] The 5th Generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connected devices, and lower latency relative to previous standards. According to the Next Generation Mobile Networks Alliance, 5G technology should provide bitrates on the order of 100 megabits per second (Mbps) to 1 gigabit per second (Gbps) and peak data rates of 10 to 20 Gbps. 5G should also provide system capacity of approximately 50,000 users per square kilometer in a 20 megahertz (MHz) bandwidth, 100 times more connections than current 4G systems, and battery life of at least 10 times current devices. Other goals of 5G include 99th percentile user experience of 1 ms latency, 1% of users experiencing 10 ms latency, and 99% of users experiencing 50 ms latency. SUMMARY

[0005] The following presents a simplified summary related to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any specific aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects disclosed herein in a simplified form to precede the detailed description presented below.

[0006] In an aspect, a method of wireless communication performed by a user equipment (UE), includes transmitting, to a location server, at least one provide capabilities message indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receiving, from the location server, a location information request to report aggregated measurements of one or more DL-PRS resources, or positioning assistance data including DL-PRS resources linked for aggregation purposes, or any combination thereof, based on the one or more capabilities.

[0007] In an aspect, a user equipment (UE) includes at least one memory; at least one transceiver; and at least one processor communicatively coupled to the at least one memory and the at least one transceiver, the at least one processor configured to: transmit, to a location server via the at least one transceiver, at least one provide capabilities message indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receive, from the location server via the at least one transceiver, a location information request to report aggregated measurements of one or more DL-PRS resources, or positioning assistance data including DL-PRS resources linked for aggregation purposes, or any combination thereof, based on the one or more capabilities.

[0008] In an aspect, a user equipment (UE) includes means for transmitting, to a location server, at least one provide capabilities message indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and means for receiving, from the location server, a location information request to report aggregated measurements of one or more DL-PRS resources, or positioning assistance data including DL-PRS resources linked for aggregation purposes, or any combination thereof, based on the one or more capabilities.

[0009] In an aspect, a non-transitory computer-readable medium storing computer- executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit, to a location server, at least one provide capabilities message indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receive, from the location server, a location information request to report one or more of aggregated measurements of one or more DL-PRS resources, or positioning assistance data including DL-PRS resources linked for aggregation purposes, or any combination thereof based on the one or more capabilities.

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

[0011] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects.

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

[0013] Figure 2A , Figure 2B and Figure 2C An example wireless network structure in accordance with aspects of the disclosure is illustrated.

[0014] Figure 3A , Figure 3B and Figure 3C are simplified block diagrams of several example aspects of components that can be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0015] Figure 4 Examples of various positioning methods supported in New Radio (NR) in accordance with aspects of the disclosure are illustrated.

[0016] Figure 5 Example Long Term Evolution (LTE) Positioning Protocol (LPP) capability transfer procedures, assistance data transfer procedures, and location information transfer procedures between a target device and a location server in accordance with aspects of the disclosure are illustrated.

[0017] Figure 6 is a diagram illustrating an example frame structure in accordance with aspects of the disclosure.

[0018] Figure 7is a diagram of an example of downlink positioning reference signal (DL-PRS) bandwidth aggregation according to aspects of the present disclosure.

[0019] Figure 8 is a diagram of an example of DL-PRS bandwidth aggregation across two positioning frequency layers (PFLs) according to aspects of the present disclosure.

[0020] Figure 9 is a diagram of an example of DL-PRS bandwidth aggregation across three PFLs according to aspects of the present disclosure.

[0021] Figure 10 An example method of wireless communication according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0022] Aspects of the present disclosure are provided in the following description and related drawings, which are provided for illustration purposes only and are not intended to be limiting. Alternative aspects can be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the disclosure, or portions thereof, can not be described with full detail to avoid obscuring aspects of the disclosure.

[0023] Various aspects relate generally to downlink positioning reference signal (DL-PRS) bandwidth aggregation. Some aspects more specifically relate to DL-PRS bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs). In some examples, a user equipment (UE) sends at least one provide capabilities message to a location server indicating a capability of the UE to support DL-PRS bandwidth aggregation across multiple aggregated PFLs. The capability can include at least a total maximum DL-PRS bandwidth value across the multiple PFLs and a maximum DL-PRS bandwidth value per aggregated PFL. Based on the reported capability, the location server sends a location information request to the UE to report aggregated measurements of DL-PRS resources.

[0024] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by a UE reporting a particular capability of the UE to support DL-PRS bandwidth aggregation across multiple PFLs, the described techniques can be used to enable a location server to request the UE to report aggregated measurements of DL-PRS resources.

[0025] 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 present disclosure” does not necessarily require all aspects of the disclosure to include the discussed feature, advantage or mode of operation.

[0026] Those skilled in the art will appreciate that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields, or particles, optical fields or particles, or any combination thereof.

[0027] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or direct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure can be embodied in a number 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 aspects described herein, the corresponding form of any such aspects can be described herein in terms such as "logic configured to" perform the actions described.

[0028] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE can be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset-positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary, and can communicate with a radio access network (RAN). As used herein, the term “UE” can be referred to interchangeably 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, UEs can communicate with one another directly, e.g., using a device-to-device (D2D) protocol, or communicate with a core network via a RAN, and through the core network the UEs can communicate with other UEs and with other network nodes, including network servers, etc. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications), etc.

[0029] A base station can operate according to one of several RATs to communicate with UEs depending on the network in which it is deployed, and can be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as gNB, or gNodeB), etc. Base stations can be used for or can primarily support wireless access for UEs, including supporting data, voice, and / or signaling connections for UEs served by the base station. In some systems, base stations can provide only edge node signaling functions, while in other systems they can provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called 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) can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0030] The term “base station” can refer to a single physical transmission reception point (TRP) or multiple physical TRPs that can or can not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP can be an antenna of the base station corresponding to a cell (or cell sector) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs can be an array of antennas 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 TRPs can 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 TRPs can be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP, as used herein, is a point from which a base station sends and receives wireless signals, references to transmissions from or receptions at a base station should be understood to refer to particular TRPs of the base station.

[0031] In some implementations that support positioning of UEs, a base station can not support wireless access by UEs (e.g., can not support data, voice, and / or signaling connections for UEs), but can instead transmit reference signals to UEs to be measured by the UEs and / or can receive and measure signals transmitted by the UEs. Such a base station can be referred to as a positioning beacon (e.g., where signals are transmitted to UEs) and / or as a location measurement unit (e.g., where signals from UEs are received and measured).

[0032] An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter can transmit a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals over multi-path channels, the receiver can receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multi-path” RF signal. As used herein, where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal, an RF signal can also be referred to as a “wireless signal” or simply a “signal.”

[0033] Figure 1An example wireless communications system 100 in accordance with aspects of the present disclosure is illustrated. The wireless communications system 100, which can also be referred to as a wireless wide area network (WW AN), can include various base stations 102, labeled as “BSs,” and various UEs 104. The base stations 102 can include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base station can include eNBs and / or ng-eNBs (where the wireless communications system 100 corresponds to an LTE network), or gNBs (where the wireless communications system 100 corresponds to an NR network), or a combination of both, and the small cell base stations can include femto cells, pico cells, micro cells, and the like.

[0034] The base stations 102 can collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122 (e.g., SI, X2, Xn, etc. interfaces), and with one or more location servers 172 (e.g., location management function (LMF) or secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 can be part of the core network 170 or can be external to the core network 170. The location server 172 can be integrated with the base stations 102. The UEs 104 can communicate directly with the location server 172, either directly or indirectly. For example, a UE 104 can communicate with the location server 172 via a base station 102 that is currently serving the UE 104. The UE 104 can 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., AP 150 described below), and the like. The communication between the UE 104 and the location server 172 can be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128) for signaling purposes, with intermediate nodes (if any) omitted from the signaling diagrams for the sake of clarity.

[0035] The base stations 102 can perform functions such as, but not limited to, orchestrating user data communications, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with one another directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which can be wired or wireless.

[0036] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more of the cells can be supported by the base station 102 in each of the geographic coverage areas 110. A “cell” is a logical communication entity used for communication to a base station, e.g., through a certain frequency bandwidth, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc. and can 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 of the same or different carrier frequencies that are operated by the same or different base stations. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs, such as machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types. Because cells are supported by a particular base station, the term “cell” can refer to either or both of a logical communication entity and a base station supporting a logical communication entity, depending on context. In addition, because a TRP is typically a physical transmission point of a cell, the terms “cell” and “TRP” can be used interchangeably. In some cases, the term “cell” can also refer to a geographic coverage area of a base station (e.g., a sector) as well, as long as a carrier frequency can be detected and used for communication within the geographic coverage area 110.

[0037] While the geographic coverage area 110 of a macro cell base station 102 can overlap with one or more other geographic coverage areas 110 of the same or different macro cell base stations 102 (e.g., in an urban setting), some of the geographic coverage areas 110 can substantially overlap with the geographic coverage area 110 of a small cell base station 102'. For example, a small cell base station 102' with a relatively small geographic coverage area 110' can be deployed in a home (e.g., a residential home, a business office, etc.) or other small geographic area to provide network access to one or more UEs 104, such as UEs 104 that are in or near the home. The small cell base station 102' can be a femto cell, a pico cell, a micro cell, etc. A network that includes both macro cell base stations 102 and small cell base stations 102 can be referred to as a heterogeneous network. A heterogeneous network can also include Home eNBs (HeNBs), which can provide service to a restricted group, such as in a closed subscription group (CSG).

[0038] The communication links 120 between the base stations 102 and the UEs 104 can include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 can use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 can be through one or more carrier frequencies. Allocation of carriers can be asymmetric with respect to downlink and uplink (e.g., more or less carriers can be allocated for downlink than for uplink).

[0039] Wireless communications system 100 can also include a WLAN access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 can perform clear channel assessment (CCA) or listen before talk (LBT) procedures prior to communicating in order to determine whether the channel is available.

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

[0041] Wireless communications system 100 can also include millimeter wave (mmW) base stations 180 that can operate in mmW frequencies and / or near mmW frequencies to communicate with UEs 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and wavelengths less than 1 millimeter to 10 millimeters. Radio waves in this band can be referred to as a millimeter wave. Near mmW can extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends from 3 GHz to 30 GHz, which is also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band have high path loss and a relatively short range. The mmW base stations 180 and the UEs 182 can utilize beamforming (transmit and / or receive) over the mmW communication links 184 to compensate for the extremely high path loss and short range. Further, it should be appreciated that in an alternative configuration one or more base stations 102 can also transmit using mmW or near mmW and beamforming. Thus, it should be appreciated that the foregoing illustrative example is only exemplary and should not be taken as limiting upon the various aspects disclosed herein.

[0042] Transmit beamforming is a technique used to focus the RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts a RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is in relation to the transmitting network node, and projects a stronger downlink RF signal in that specific direction, thereby providing a faster and stronger RF signal (in terms of data rate) for the receiving device. 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”), which in effect moves the beam without moving the actual antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0043] Transmit beams can be quasi co-located, which means that they have the same parameters as seen by the receiver (e.g., a UE), 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 a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, then 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 transmitted on the same channel. If the source reference RF signal is QCL Type B, then the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, then the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, then the receiver can use the source reference RF signal to estimate the spatial receive parameter of the second reference RF signal transmitted on the same channel.

[0044] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver can increase a gain setting and / or adjust a phase setting of an antenna array in a particular direction to amplify (e.g., increase a gain level of) an RF signal received from that direction. Thus, when a receiver is said to beamform in a certain direction, this means that the beam gain in that direction is high relative to the beam gain in 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.

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

[0046] Note that depending on the entity forming the “downlink” beam, the beam can be a transmit beam or a receive beam. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, the downlink beam is a receive beam to receive 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 a base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if a UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0047] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, etc. In 5G NR, 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 a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub- 6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with respect to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is designated as a “millimeter wave” band by the INTERNATIONAL TELECOMMUNICATION

[0048] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Moreover, even higher bands are currently under exploration to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands falls within the EHF band.

[0049] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “Sub-6 GHz” or the like if used herein, can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein, can broadly represent frequencies 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.

[0050] ​In multi-carrier systems 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 the 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 a RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (although this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and can be 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 can contain only necessary signaling information and signals, e.g., those that are UE-specific can not be present in the secondary carrier since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier for any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier through which a certain base station communicates, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc. can be used interchangeably.

[0051] For example, still referring to Figure 1 , one of the frequencies used by the macrocell base station 102 can be an anchor carrier (or “PCell”), and other frequencies used by the macrocell base station 102 and / or the mmW base station 180 can be secondary carriers (“SCells”). The simultaneous transmission and / or reception of multiple carriers enables the 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.

[0052] The wireless communications system 100 can also include UE 164, which can be in communication with macro cell base station 102 through the communication link 120 and / or mmW base station 180 through the mmW communication link 184. For example, macro cell base station 102 can support PCell and one or more SCells for the UE 164, and mmW base station 180 can support one or more SCells for the UE 164.

[0053] In some cases, the UEs 164 and 182 can be capable of sidelink communications. A sidelink-capable UE (SL-UE) can communicate with the base station 102 using the Uu interface (i.e., the air interface between a UE and a base station) through the communication link 120. SL-UEs (e.g., UEs 164, 182) can also communicate with one another directly via wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). The wireless sidelink (or “sidelink” for short) is an adaptation of the core cellular network (e.g., LTE, NR) standard that allows for direct communication between two or more UEs without the need for communication 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-everything (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of the SL-UEs in a group utilizing sidelink communications can be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group can be outside the geographic coverage area 110 of a base station 102, or be otherwise unable to receive transmissions from base station 102. In some cases, groups of SL-UEs communicating via sidelink communications can utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, the base station 102 facilitates scheduling of resources for the sidelink communications. In other cases, the sidelink communications are performed between SL-UEs without the involvement of base station 102.

[0054] In an aspect, the sidelink 160 can operate over a wireless communication medium of interest that can be shared with other wireless communications between other vehicles and / or infrastructure access points and other RATs. A "medium" can include one or more time, frequency, and / or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In an aspect, the medium of interest can correspond to at least a portion of an unlicensed frequency band that is shared between various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC)), these systems, particularly those employing small cell access points, have recently extended operations into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.1 lx WLAN technologies 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, etc.

[0055] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UE 164 and UE 182), but any of the illustrated UEs can be SL-UEs. Further, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs, including UE 164, can be capable of beamforming. Where the SL-UEs are capable of beamforming, they can beamform toward one another (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base station 102, base station 180, small cell 102', access point 150), etc. Thus, in some cases, UE 164 and UE 182 can utilize beamforming over sidelink 160.

[0056] In Figure 1 the illustrated UEs (for simplicity, only UE 164 and UE 182 are Figure 1Any of the UEs 104 (shown as a single UE 104) can receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112, such as satellites. In an aspect, the SVs 112 can be part of a satellite positioning system that UEs 104 can use as a standalone source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned in Earth orbit so that receivers (e.g., UEs 104) can determine their 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 signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters can sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. UEs 104 can include one or more specialized receivers designed specifically for receiving signals 124 in order to derive geographic location information from SVs 112.

[0057] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS), which can be associated with one or more global and / or regional navigation satellite systems or which can otherwise enable the use of one or more global and / or regional navigation satellite systems. For example, an SBAS can include an augmentation system(s) that provides integrity information, differential corrections, etc. to one or more global and / or regional navigation satellite systems, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi

[0058] In an aspect, the SVs 112 additionally or alternatively can be part of one or more non-terrestrial networks (NTNs). In an NTN, the SVs 112 connect to an Earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in the 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately to entities outside the 5G network, such as Internet web servers and other user equipment. In this way, the UEs 104 can receive communication signals (e.g., signals 124) from the SVs 112 as an alternative or supplement to communication signals from terrestrial base stations 102.

[0059] The wireless communications system 100 can also include one or more UEs, such as UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). For example, UEs 104 can indirectly connect to the 5G core network 206 or the LTE core network 206a via D2D P2P links 192 with a network-connected UE, such as a UE 104 connected to base station 102. Figure 1 In an example, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 can indirectly access cellular connectivity), and has a D2D P2P link 194 with a WLAN STA 152 connected to the WLAN AP 150 (through which the UE 190 can indirectly access WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 can be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), Bluetooth®, Zigbee®, Z-Wave®, Wi-Fi, and so on. In an example, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 can indirectly access cellular connectivity), and has a D2D P2P link 194 with a WLAN STA 152 connected to the WLAN AP 150 (through which the UE 190 can indirectly access WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 can be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), Bluetooth®, Zigbee®, Z-Wave®, Wi-Fi, and so on.

[0060] Figure 2A An example wireless network structure 200 is illustrated. For example, a 5GC 210 (also referred to as Next Generation Core (NGC)) can be viewed functionally as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway function, access to data networks, IP

[0061] Another optional aspect can include a location server 230 that can communicate with the 5GC 210 to provide location assistance for UEs 204. The location server 230 can 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 alternately can each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Further, the location server 230 can be integrated into a component of the core network, or alternately 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).

[0062] Figure 2B Another example wireless network structure 240 is illustrated. A 5GC 260 (which can correspond to the 5GC 210) is shown that includes an AMF 262, a UDM 264, and a location management function (LMF) 266. The AMF 262 can communicate with a base station 220 (which can correspond to the base stations 220a, 220b, 220c) over an N2 interface 268. The base station 220 can also Figure 2AThe 5GC 210) can be viewed functionally as control plane functions provided by an access and mobility management function (AMF) 264, user plane function (UPF) 262, that operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for one or more UE 204 (e.g., any of the UEs described herein) session management (SM) messages between a UE 204 and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between a UE 204 and an SMS function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and a UE 204, and receives an intermediate key that was established as a result of the UE 204 authentication process. In the case of universal mobile (Third Generation Partnership Project) access networks.

[0063] Functions of the UPF 262 include acting as an anchor point for intra- / inter-RAT mobility (when applicable), acting as a external protocol data unit (PDU) session point of interconnect 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, quality of service (QoS) handling for user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding of one or more “end markers.” The UPF 262 can also support transfer of location services messages between the UE 204 and a location server, such as the SLP 272, over the user plane.

[0064] Functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 for proper

[0065] Another optional aspect can include an LMF 270, which can be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 can 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 alternately can each correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204, which can connect to the LMF 270 via the core network, 5GC 260, and / or via the Internet (not illustrated). The SLP 272 can support similar functions as the LMF 270, but whereas the LMF 270 can communicate with the AMF 264, NG-RAN 220, and UEs 204 over the control plane (e.g., using interfaces and protocols intended to transfer signaling messages, rather than voice or data), the SLP 272 can communicate with UEs 204 and external clients (e.g., third-party servers 274) over the user plane (e.g., using protocols intended to carry voice and / or data, such as the transmission control protocol (TCP) and / or IP).

[0066] Yet another optional aspect can include a third party server 274 that can communicate with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third party server 274 can be referred to as a Location Services (LCS) client or an external client. The third party server 274 can be implemented as a number 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 alternatively can each correspond to a single server.

[0067] The user plane interface 263 and control plane interface 265 connect the 5GC 260, and in particular the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between gNBs 222 and / or ng-eNBs 224 and AMF 264 is referred to as the “N2” interface, while the interface between gNBs 222 and / or ng-eNBs 224 and UPF 262 is referred to as the “N3” interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 can communicate with one another directly via backhaul connections 223, referred to as the “Xn-C” interface. One or more of the gNBs 222 and / or ng-eNBs 224 can communicate with one or more UEs 204 over a wireless interface referred to as the “Uu” interface.

[0068] The functionality of a gNB 222 is divided among a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. The gNB-CU 226 is a logical node that includes base station functionality other than that specifically allocated to the gNB-DUs 228, including transfer 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-DUs 228 are logical nodes that typically host the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Their 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 the one or more gNB-DUs 228 is referred to as the “Fl” interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more standalone gNB-RUs 229 that 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, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0069] Deployments of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of a network, RAN nodes, core network nodes, network elements, or network equipment, such as a base station or one or more elements (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, etc., can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station.

[0070] A disaggregated base station can be configured to utilize a radio protocol stack integrated physically or logically within a single RAN node. A disaggregated base station can be configured to utilize a protocol stack distributed physically or logically across 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 can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DUs can be implemented to be in communication with one or more RUs. Each of the CU, DU, and RU can also be implemented as virtual units, i.e., a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU).

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

[0072] 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 can include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the 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-RT RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CUs 280 can communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective fronthaul links, such as an Fl interface. The DUs 285 can communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective front-haul links. The RUs 287 can communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be simultaneously served by multiple RUs 287.

[0073] 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) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission mediums. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, can be configured to communicate with one or more of the other units via the transmission mediums. For example, the units can include wired interfaces configured to receive signals from or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units can include wireless interfaces, which can include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals from or transmit signals to one or more of the other units over a wireless transmission medium, or both.

[0074] In some aspects, CU 280 can host one or more higher layer control functions. Such control functions can include RRC, PDCP, Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by CU 280. CU 280 can 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 implementations, CU 280 can 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 units can be in bidirectional communication with the CU-CP units via an interface, such as an El interface. CU 280 can be implemented to communicate with DU 285 as needed for network control and signaling.

[0075] DU 285 can 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 can host one or more of the RLC layer, the MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) in accordance with a functional split, such as the functional split defined by the Third Generation Partnership Project (3GPP) NR standards. In some aspects, DU 285 can also host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280. DU 285 can 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 can host one or more of the RLC layer, the MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) in accordance with a functional split, such as the functional split defined by the Third Generation Partnership Project (3GPP) NR standards. In some aspects, DU 285 can also host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.

[0076] Lower layer functionality can be implemented by one or more RUs 287. In some deployments, RUs 287 controlled by a DU 285 can correspond to logical nodes that host 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, RUs 287 can 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 RUs 287 can be controlled by a corresponding DU 285. In some scenarios, this configuration can enable implementation of DUs 285 and CUs 280 in a cloud-based RAN architecture, such as a vRAN architecture.

[0077] The SMO framework 255 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 255 can 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 to instantiate virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287, and near-RT RICs 259. In some implementations, the SMO framework 255 can communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 261, via an Ol interface. Additionally, in some implementations, the SMO framework 255 can communicate directly with one or more RUs 287 via an Ol interface. The SMO framework 255 can also include a non-RT RIC 257 configured to support functionality of the SMO framework 255.

[0078] The non-RT RIC 257 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including model training and update, application / features in near-RT RIC 259 of artificial intelligence / machine learning (AI / ML) workflow or policy-based steering. The non-RT RIC 257 can be coupled to, or in communication with, the near-RT RIC 259, such as via an Al interface. The near-RT RIC 259 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions by an interface, such as via an E2 interface, connecting one or more CUs 280, one or more DUs 285, or both, and an O-eNB with the near-RT RIC 259.

[0079] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 259, the non-RT RIC 257 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 259 and can be received at the SMO framework 255 or the non-RT RIC 257 from non-network data sources or from network functions. In some examples, the non-RT RIC 257 or the near-RT RIC 259 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions by the SMO framework 255, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.

[0080] Figure 3A , Figure 3B and Figure 3C Several example components are illustrated (represented by corresponding blocks), which can be incorporated into the UE 302 (which can correspond to any of the UEs described herein), the base station 304 (which can correspond to any of the base stations described herein), and the network entity 306 (which can correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively can be independent of those functions). The components can be configured to perform processes for techniques described herein, e.g., as described with regard to the flow charts and example operations below. Figure 2A and Figure 2BThe depicted NG-RAN 220 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, to support operations as described herein. It will be appreciated that these components can be implemented with different implementations in different types of apparatuses (e.g., in ASICs, in System-on-Chips (SoCs), etc.). The illustrated components can also be incorporated into other apparatuses in the communication system. For example, other apparatuses in the system can include components similar to those described as providing similar functionality. Also, a given apparatus can contain one or more of the components. For example, an apparatus can include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

[0081] The UE 302 and the base stations 304 each include one or more wireless wide area network (WWAN) transceiver components 310 and 350, respectively, that provide the means for communicating over one or more wireless communication networks, such as an NR network, an LTE network, a GSM network, and / or the like (not shown). The WWAN transceiver components 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

[0082] At least in some cases, the UE 302 and the base stations 304 each also include one or more short-range wireless transceiver components 320 and 360, respectively. The short-range wireless transceiver components 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide the means for communicating via at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth®, Bluetooth® Low Energy, Near Field Communication, etc.) over a wireless communication medium having a shorter range than a WWAN. In some cases, a WWAN and a short-range wireless communication medium can be the same or different types of communication media. Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communication between PC5, Dedicated Short Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, short-range transceivers 320 and 360 each include: one or more transmitters 324 and 364 for transmitting 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 specific examples, the short-range wireless transceivers 320 and 360 can be Wi-Fi transceivers, transceiver and / or Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

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

[0084] The base stations 304 and network entities 306 each include one or more network transceivers 380 and 390, respectively, which provide means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306) over a network. For example, a base station 304 can employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, a network entity 306 can employ one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

[0085] A transceiver can be configured to communicate over wired or wireless links. A transceiver, whether wired or wireless, includes transmitter circuitry (e.g., transmitter 314, 324, 354, 364) and receiver circuitry (e.g., receiver 312, 322, 352, 362). In some implementations, a transceiver can be an integrated device (e.g., implementing transmitter circuitry and receiver circuitry in a single device), in some implementations can include separate transmitter circuitry and separate receiver circuitry, or can be implemented in other manners in other implementations. The transmitter circuitry and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) can be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitter 314, 324, 354, 364) can include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the respective apparatus (e.g., UE 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) can include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry can share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. The wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) can also include a network listen module (NLM) or the like for performing various measurements.

[0086] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some specific embodiments, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some specific embodiments) may generally be described as "transceiver," "at least one transceiver," or "one or more transceivers." Therefore, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0087] 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 each include one or more processors 332, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, processors 332, 384, and 394 may 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.

[0088] The UE 302, the base stations 304, and the network entity 306 each include memory circuitry implementing memory 340, 386, and 396 (e.g., including at least one memory device each) to maintain information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memory 340, 386, and 396 can thus provide a means for storing, a means for retrieving, a means for maintaining, and so on. In some cases, the UE 302, the base stations 304, and the network entity 306 can each include a positioning component 342, 388, and 398, respectively. The positioning component 342, 388, and 398 can be hardware circuits that are part of, or coupled to, the processors 332, 384, and 394, respectively, which, when executed, cause the UE 302, the base stations 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning component 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning component 342, 388, and 398 can be memory modules stored in the memory 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 stations 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for the positioning component 342 are illustrated, which can be part of, for example, the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or can be a standalone component. Figure 3B Possible locations for the positioning component 388 are illustrated, which can be part of, for example, the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or can be a standalone component. Figure 3C Possible locations for the positioning component 398 are illustrated, which can be part of, for example, the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or can be a standalone component.

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

[0090] Further, the UE 302 includes a user interface 346 that provides means for providing indications (e.g., audible and / or visual indications) to a user and / or for receiving user input (e.g., upon the user actuating a sensing device, such as a keypad, a touch screen, a microphone, etc.). Although not shown, the base station 304 and the network entity 306 can also include user interfaces.

[0091] Referring to the one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 can be provided to the processor 384. The one or more processors 384 can implement functionality for a RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The one or more processors 384 can provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer 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.

[0092] The transmitter 354 and receiver 352 can implement layer 1 (LI) functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the 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 coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to a orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., 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 precoded to produce multiple spatial streams if multiple spatial streams are

[0093] At the UE 302, the receiver 312 receives a signal through its respective antenna 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the 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 multiple spatial streams are destined for the UE 302, they can be combined by the receiver 312 into a single OFDM symbol stream. 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 comprises 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 most likely signal constellation points transmitted by the base station 304. These soft decisions can be based on channel estimates computed by the channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted on the physical channel. The data and control signals are then provided to the one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

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

[0095] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 332 provide RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer 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 transmission channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

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

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

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

[0099] For convenience, the UE 302, base station 304, and / or network entity 306 are referred to as Figure 3A , Figure 3B and Figure 3CThe document is shown as including 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 functionalities in different designs. In particular, Figures 3A-3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or (e.g., cellular only, but without cellular capability), or the short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal receiver 330 can be omitted, or the sensor 344 can be omitted, etc. For example, in... Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0100] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between these different logical entities.

[0101] 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 the network entity 306 can be implemented in one or more circuits, such as for example one or more processors and / or ASICs (which can include one or more processors). Here, each circuit can use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide functionality. For example, some or all of the functionality represented by blocks 350-388 can be implemented by a processor and memory component of the base station 304, e.g., by execution of appropriate code and / or by appropriate configuration of processor components. Also, some or all of the functionality represented by blocks 390-398 can be implemented by a processor and memory component of the network entity 306, e.g., by execution of appropriate code and / or by appropriate configuration of processor components. For simplicity, various operations, acts, and / or functions are described herein as being performed by a UE, a base station, a network entity, and / or the like. However, as will be appreciated, such operations, acts, and / or functions can actually be performed by specific components or combinations of components of the UE 302, the base station 304, the network entity 306, and / or the like, such as the processors 332, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning components 342, 388, and 398, and / or the like.

[0102] In some designs, the network entity 306 can be implemented as a component of a core network. In other designs, the network entity 306 can be distinct from the operation of a network operator or cellular network infrastructure (e.g., the NG RAN 220 and / or the 5GC 210 / 260). For example, the network entity 306 can be a component of a private network that can be configured to communicate with the UE 302 via the base station 304 or independent of the base station 304 (e.g., through a non-cellular communication link such as Wi-Fi).

[0103] NR supports multiple cellular network-based positioning techniques, 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. Figure 4Examples of various positioning methods in accordance with aspects of the present disclosure are illustrated. In the OTDOA or DL-TDOA positioning procedure illustrated in scenario 410, a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., Positioning Reference Signals (PRS)) received from pairs of base stations (referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurements) and reports these differences to a positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in assistance data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the location of the UE.

[0104] For DL-AoD positioning illustrated in scenario 420, a positioning entity determines the angles between a UE and transmitting base stations using signal strength measurements from the UE’s measurement reports on the reception of multiple downlink transmit beams. The positioning entity can then estimate the location of the UE based on the determined angles and the known locations of the transmitting base stations.

[0105] 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 is based on uplink reference signals (e.g., Sounding Reference Signals (SRS)) transmitted by a UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the time of reception (referred to as Relative Time of Arrival (RTOA)) of the reference signal to a positioning entity (e.g., a location server) that knows the locations and relative timings of the involved base stations. Based on the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can estimate the location of the UE using TDOA.

[0106] 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 a UE on one or more uplink receive beams. A positioning entity determines the angles between the UE and the base stations using the signal strength measurements and the angles of the receive beams. Based on the determined angles and the known locations of the base stations, the positioning entity can then estimate the location of the UE.

[0107] Downlink- and uplink-based positioning methods include Enhanced Cell-ID (E-CID) positioning and Multilateration (also referred to as “Multi-Cell RTT” and “Multi-RTT”). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or base station), which transmits 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. This time difference is referred to as the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the closest time slot boundaries of the received and transmitted signals. Both entities can then communicate their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which computes the round trip propagation time (i.e., RTT) between the two entities from these two Rx-Tx time difference measurements (e.g., as the sum of these two Rx-Tx time difference measurements). Alternatively, one entity can communicate its Rx-Tx time difference measurement to the other entity, which then computes the RTT. The distance between the two entities can be determined from the RTT and the known speed of signal (e.g., the speed of light). For Multi-RTT positioning illustrated by scenario 430, 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) to enable determination of the location of the first entity based on distances to the second entities and known locations of the second entities (e.g., using multilateration). RTT and Multi-RTT methods can be combined with other positioning techniques, such as UL-AoA and DL-AoD, to improve location accuracy, as illustrated by scenario 440.

[0108] E-CID positioning methods are based on radio resource management (RRM) measurements. In E-CID, a UE reports the serving cell ID, timing advance (TA), and identifiers of detected neighbor base stations, estimated timing, and signal strength. The UE’s location is then estimated based on this information and known locations of the base stations.

[0109] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) can provide assistance data to a UE. For example, the assistance data can include identifiers of base stations (or cells / TRPs of base stations) from which to measure reference signals, reference signal configuration parameters (e.g., including a number of consecutive time slots comprising a PRS, a periodicity of consecutive time slots comprising a PRS, a muting 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 can originate directly from the base stations themselves (e.g., in periodically broadcasted overhead messages, etc.). In some cases, a UE can be able to detect neighboring network nodes without the use of assistance data.

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

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

[0112] Long Term Evolution (LTE) Positioning Protocol (LPP) is used point-to-point between a location server (e.g., LMF 270) and a target device (e.g., UE) in order to position the target device using positioning-related measurements obtained by one or more reference sources (physical entities or parts of physical entities that provide signals that can be measured by the target device in order to obtain a position of the target device). An LPP session is used between the location server and the target device in order to obtain position-related measurements or a position estimate, or to transfer assistance data. Currently, a single LPP session is used to support a single position request, and multiple LPP sessions can be used between the same endpoints to support multiple different position requests. Each LPP session includes one or more LPP transactions (or procedures), where each LPP transaction performs a single operation (capability exchange, assistance data transfer, or position information transfer). Each LPP transaction involves the exchange of one or more LPP messages between the location server and the target device. The general format of an LPP message consists of a set of common fields followed by a body. The body (which can be empty) contains information specific to the particular message type. Each message type contains information specific to one or more positioning methods and / or information common to all positioning methods.

[0113] An LPP session typically includes at least a capability transfer or indication procedure, an assistance data transfer or delivery procedure, and a position information transfer or delivery procedure. Figure 5 Example LPP capability transfer procedures 510, LPP assistance data transfer procedures 530, and LPP position information transfer procedures 550 between a target device (labeled “Target”) and a location server (labeled “Server”) are illustrated in accordance with aspects of the present disclosure.

[0114] The purpose of the LPP capability transfer procedure 510 is to enable the transfer of capabilities from the target device (e.g., UE 204) to the location server (e.g., LMF 270). In this context, capabilities refer to LPP-related positioning and protocol capabilities and positioning methods supported by LPP. In the LPP capability transfer procedure 510, the location server (e.g., LMF 270) indicates the types of capabilities required from the target device (e.g., UE 204) in an LPP Request Capabilities message. The target device responds with an LPP Provide Capabilities message. The capabilities included in the LPP Provide Capabilities message shall correspond to any capability types specified in the LPP Request Capabilities message. Specifically, for each positioning method for which a request for capabilities is included in the LPP Request Capabilities message, the target device includes the target device’s capabilities for the supported positioning method in the LPP Provide Capabilities message if the target device supports the positioning method. For the LPP capability indication procedure, the target device provides capabilities to the location server in the LPP Provide Capabilities message unsolicited (i.e., without receiving an LPP Request Capabilities message).

[0115] The purpose of the LPP assistance data transfer procedure 530 is to enable a target device to request assistance data from a location server to assist in positioning and for a location server to transfer assistance data to a target device without a request. In the LPP assistance data transfer procedure 530, a target device transmits an LPP Request Assistance Data message to a location server. The location server responds to the target device with an LPP Provide Assistance Data message containing assistance data. The transferred assistance data shall match or be a subset of the assistance data requested in the LPP Request Assistance Data. The location server can also provide any unrequested information that it deems useful to the target device. The location server can also send one or more additional LPP Provide Assistance Data messages to the target device containing further assistance data. For the LPP assistance data delivery procedure, the location server provides unsolicited assistance data necessary for positioning. Assistance data can be provided periodically or aperiodically.

[0116] The purpose of the LPP position information transfer procedure 550 is to enable a location server to request position measurement data and / or a position estimate from a target device and for a target device to transfer position measurement data and / or a position estimate to a location server without a request. In the LPP position information transfer procedure 550, a location server transmits an LPP Request Location Information message to a target device to request position information, indicating the type of position information required and potentially associated QoS. The target device responds to the location server with an LPP Provide Location Information message to transfer position information. Unless the location server explicitly allows additional position information, the transferred position information shall match or be a subset of the position information requested by the LPP Request Location Information. More specifically, the target device includes the requested information in the LPP Provide Location Information message if the requested information is compatible with the capabilities and configuration of the target device. Otherwise, if the target device does not support one or more of the requested positioning methods, the target device continues processing the message as if the message contained only information for the supported positioning methods and handles the signaling content for the unsupported positioning methods through LPP error detection. The target device transmits additional LPP Provide Location Information messages to the location server to transfer additional position information if requested by the LPP Request Location Information message. The LPP position information delivery procedure supports delivery of unsolicited service-based positioning estimates.

[0117] LPP also defines procedures related to error indications when a receiving endpoint (target device or location server) receives erroneous or unexpected data or detects some data loss. Specifically, when a receiving endpoint determines that a received LPP message contains an error, the receiving endpoint can return an error message to the sending endpoint indicating one or more errors and discard the received / erroneous message. If the receiving endpoint is able to determine that the erroneous LPP message is an LPP error or abort message, the receiving endpoint discards the received message without needing to return an error message to the sending endpoint.

[0118] LPP also defines procedures related to abort indications to allow a target device or location server to abort an ongoing procedure due to some unexpected event (e.g., LCS client cancellation of a location request). Abort procedures can also be used to stop an ongoing procedure (e.g., periodic location reporting from a target device). In an abort procedure, a first endpoint determines that a procedure P must be aborted and transmits an abort message to a second endpoint carrying the transaction ID of procedure P. The second endpoint then aborts procedure P.

[0119] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 6 FIG. 600 is a diagram 600 illustrating an example frame structure in accordance with aspects of the present disclosure. The frame structure can be a downlink or uplink frame structure. Other wireless communication technologies can have different frame structures and / or different channels.

[0120] LTE (and in some cases NR) utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Specifically, LTE and NR support a range of subcarrier spacing configurations. For example, NR TDD supports subcarrier spacing of 120 kHz, 240 kHz, 480 kHz, and 960 kHz. 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 often referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing of the adjacent subcarriers can be fixed, and the total number of subcarriers K can be dependent on the system bandwidth. The spacing of the subcarriers can be 15 kHz, and the minimum resource allocation (called a “resource block” (RB)) can be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth can also be partitioned into sub-bands. For example, a sub-band can cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 sub-bands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

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

[0122] In Figure 6 examples, a numerology of 15 kHz is used. Thus, in the time domain, a frame of 10 ms is divided into 10 equal size subframes with each subframe of 1 ms and each subframe including one slot. In Figure 6 time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.

[0123] A resource grid can be used to represent the time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE can correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In Figure 6An RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain for normal cyclic prefix, or six consecutive symbols in the time domain for extended cyclic prefix, for a total of 84 or 72 REs, respectively. The number of bits carried by each RE depends on the modulation scheme.

[0124] Some of the REs can carry reference (pilot) signals (RS). These reference signals can 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 (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communications. Figure 6 Example locations of REs carrying reference signals are illustrated (labeled “R”).

[0125] A set of resource elements (REs) used for the transmission of a PRS is referred to as a “PRS resource.” The set of resource elements can 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.

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

[0127] Currently, DL-PRS resources use a full frequency domain interlaced pattern that can span 2, 4, 6, or 12 consecutive symbols within a slot. A DL-PRS resource can be configured in any downlink or flexible (FL) symbol of a slot that is configured by higher layers. There can be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the per-symbol frequency offsets for comb sizes 2, 4, 6, and 12 over 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, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3} (as in the example of Figure 6 {0, 2, 1, 3} (as in the example of

[0128] A “PRS resource set” is a set of PRS resources used for transmitting PRS signals, where each PRS resource has a PRS resource ID. Further, the PRS resources in a 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 particular TRP (identified by a TRP ID). Further, the PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across slots. The periodicity is the time from a first repetition of a first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of a next PRS instance. The periodicity can have a length selected from {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} slots with μ = 0, 1, 2, 3. The repetition factor can have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0129] A 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 thus a “PRS resource” (or simply “resource”) can also be referred to as a “beam.” Note that this does not have any implications on whether the TRP and beam on which the PRS is transmitted is known to the UE.

[0130] A “PRS instance” or “PRS occasion” is one instance of a periodically repeating time window (such as a set of one or more consecutive slots) in which PRS is expected to be transmitted. A PRS occasion can also be referred to as a “PRS positioning occasion,” “PRS positioning instance,” “positioning occasion,” “positioning instance,” “positioning repetition,” or simply “occasion,” “instance,” or “repetition.”

[0131] A “positioning frequency layer” (also simply referred to as a “frequency layer”) is a set of one or more PRS resource sets across one or more TRPs that have the same values for certain parameters. Specifically, the set of PRS resource sets have the same subcarrier spacing and cyclic prefix (CP) type (meaning that all numerologies supported for physical downlink shared channel (PDSCH) are also supported for PRS), the same point A, the same value of 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, with a minimum value of 24 PRBs and a maximum value of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets per TRP per frequency layer can be configured.

[0132] The concept of a frequency layer is somewhat analogous to the concepts of a component carrier and a bandwidth part (BWP), but with the difference that a component carrier and a BWP are used by one base station (or macrocell base station and small cell base station) to transmit data channels, whereas a frequency layer is used by several (typically three or more) base stations to transmit PRS. A UE can indicate the number of frequency layers that it can support when the UE communicates its positioning capabilities to the network, such as during an LTE Positioning Protocol (LPP) session. For example, a UE can indicate that it can support one or four positioning frequency layers.

[0133] It should be noted that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can 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. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink positioning reference signals, uplink positioning reference signals, or sidelink positioning reference signals, unless otherwise indicated by the context. If further distinction is required regarding the type of PRS, downlink positioning reference signals can be referred to as "DL-PRS," uplink positioning reference signals (e.g., positioning SRS, i.e., PTRS) as "UL-PRS," and sidelink positioning reference signals as "SL-PRS." Furthermore, for signals that can be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), these signals may be preceded by "DL", "UL", or "SL" to distinguish the direction. For example, "UL-DMRS" may be different from "DL-DMRS".

[0134] DL-PRS is typically transmitted over the entire bandwidth supported by the base station. However, a receiver (e.g., a UE) may not be able to measure the PRS transmitted over that entire bandwidth within a single time interval (e.g., one or more symbols or time slots). One technique for increasing the bandwidth of the measured PRS is cross-frequency domain aggregation of PRS (referred to as “bandwidth aggregation” or “frequency domain stitching”) and / or cross-time domain aggregation of PRS (referred to as “time domain stitching”). In frequency domain PRS bandwidth aggregation, the PRS is measured over multiple (preferably consecutive) bandwidth intervals (e.g., Positioning Frequency Layer (PFL), Bandwidth Part (BWP), or groups of consecutive PRBs) within one or more component carriers, frequency bands, or other bandwidth portions. By measuring the PRS over multiple bandwidth intervals, the effective bandwidth of the PRS is increased, leading to increased accuracy in positioning measurements.

[0135] Figure 7 Figure 700 illustrates an example of DL-PRS bandwidth aggregation based on various aspects of this disclosure. (See Figure 700.) Figure 7 As shown, PRS (labeled "PRS1") is measured on the corresponding bandwidth intervals 710-1, 710-2, and 710-3 (labeled "BW1", "BW2", and "BW3", respectively) within a given frequency band (labeled "B1"). Bandwidth intervals 710-1, 710-2, and 710-3 (collectively referred to as bandwidth interval 710) can, for example, be a locating frequency layer. Frequency band "B1" can be a band within FR1 or FR2.

[0136] exist Figure 7In this case, time is represented horizontally, and frequency is represented vertically. Thus, in the example of FIG. 7, the PRS is measured over three bandwidth intervals 710, each of which is a different PFL. In this case, the PRS is measured over a first PFL 712, a second PFL 714, and a third PFL 716. The first PFL 712 is a 24-PRB PFL, the second PFL 714 is a 48-PRB PFL, and the third PFL 716 is a 96-PRB PFL. In this case, the PRS is measured over a first bandwidth interval 710, a second bandwidth interval 710, and a third bandwidth interval 710. Figure 7 In the example of FIG. 7, the three bandwidth intervals 710 are contiguous in the frequency domain. While Figure 7 While a single frequency band “B1” is illustrated, the bandwidth intervals 710 can instead span multiple frequency bands (possibly in both FR1 and FR2), with or without guard bands (not shown) between different frequency bands. Moreover, the bandwidth intervals 710 can span one or more component carriers within one or more frequency bands. Additionally, while Figure 7 While the PRS is illustrated as being measured over three bandwidth intervals 710, it should be understood that the PRS can be measured over only two bandwidth intervals 710 or over more than three bandwidth intervals 710.

[0137] In the time domain, a PRS can be a PRS occasion, a PRS resource, a slot containing a PRS, etc. The PRSs should generally be the same as one another except for being measured over different bandwidth intervals 710. However, while the PRSs in FIG. 7 are illustrated as starting and ending at the same time, this is not always the case, and some PRSs can start or end or have a different length than other PRSs. Figure 7

[0138] To enable DL-PRS bandwidth aggregation between PRS in two or three different PFLs, various conditions should be met for aggregated PRS resources from TRPs across the aggregated PFLs. For example, aggregated PRS resources from TRPs across the aggregated PFLs should be in the same slot, in the same symbol, provided by the same TRP associated with the same allocation and retention priority (ARP), and from the same RF chain (i.e., the same antenna). Additionally, the aggregated PRS resources should have the same QCL, the same number of symbols, symbol location within a slot, and repetition factor, the same numerology (i.e., the same cyclic prefix and SCS), the same or different bandwidth, the same comb size, and the same power per subcarrier. Additionally, the aggregated PFLs should be configured on the same aligned numerology grid, and there should be phase continuity between the aggregated PFLs. Whether the PRS resources have the same gNB transmit timing error group (Tx TEG) and the same UE receive TEG (Rx TEG), maximum transmit timing error margin, the same periodicity and slot offset, the same muting pattern, and / or the same “NR-DL-PRS-SFN0-Offset” parameter currently depends on implementation. Similarly, whether there should be the same number of PRS resource sets and resources for the TRPs or how to maintain contiguous PRS patterns across the aggregated bandwidth even in the presence of guard tones (e.g., PFLs with different RE offset configurations, PFLs with different point A) currently depends on implementation.

[0139] ​For PRS bandwidth aggregation across PFLs, it has been agreed to support certain PRS configuration enhancements for the location server to inform the UE (or for the NG-RAN to inform the location server) of PRS resources for which it links two or three PFLs. It has also been agreed to support joint measurement and reporting of PRS resources aggregated across PFLs for DL-TDOA and Multi-RTT positioning methods. In this case, in the measurement report element, it has been agreed that a single RSTD or a single UE Rx-Tx time difference can be reported for PRS resources across aggregated PFLs. It has also been agreed to support location server initiated and UE initiated on-demand PRS for PRS bandwidth aggregation, and to support preconfigured on-demand PRS across PFLs for PRS bandwidth aggregation. Finally, it has been agreed to support PRS measurements by the UE across multiple aggregated PFLs in RRC CONNECTED, RRC INACTIVE, and RRC IDLE states.

[0140] The present disclosure provides capability signaling enhancements for PRS bandwidth aggregation. Based on a PFL aggregation capability report (provided by the UE in an LPP capability transfer procedure 510), the positioning assistance data (e.g., provided by the location server in an LPP assistance data transfer procedure 530) can include an indication that two or three PFLs can be aggregated. A subsequent location information request (e.g., received from the location server as in an LPP location information transfer procedure 550) can request the UE to report aggregated PRS measurements. The UE can also report legacy measurements (i.e., non-aggregated PRS measurements) in the same measurement report.

[0141] Referring now more specifically to the PFL aggregation capability report, the report can include (N, K, maxBW, Type 1 / Type 2) values for the aggregation type processing for each band. For dual PFL aggregation, the report can include a total maximum bandwidth value, and the UE can also report a maximum bandwidth value per PFL, or the maximum bandwidth per PFL can be inherited from the legacy (i.e., non-aggregated) maximum bandwidth values of the UE’s per PFL capability. For triple PFL aggregation, the report can include a total maximum bandwidth value, and the UE can also report a maximum bandwidth value per PFL, or the maximum bandwidth per PFL can be inherited from the legacy (i.e., non-aggregated) maximum bandwidth values of the UE’s per PFL capability. The UE can also report separate PFL aggregation capabilities for measurement gap based PRS processing and for measurement gap free PRS processing.

[0142] Figure 8 is a diagram 800 of an example of DL-PRS bandwidth aggregation across two PFLs in accordance with aspects of the present disclosure. As Figure 8As shown, the same PRS (labeled “PRS1”) is measured on two PFLs (labeled “PFL1” and “PFL2”). In this scenario, the maximum bandwidth per PFL capability of the UE can be (1) the same as the maximum bandwidth of the PFL when the PFL is processed without aggregation (as can currently be indicated in the capability report), or (2) a new maximum bandwidth of the PFL that is only reported when this PFL is used for aggregated measurements. The maximum bandwidth of the aggregated PFLs can include the total bandwidth span of the PFLs, including the guard bands in between. Alternatively, the maximum bandwidth across the two PFLs can not include the guard bands, and the UE can report a separate capability of the maximum guard band that the UE can tolerate between the two PFLs.

[0143] Figure 9 FIG. 9 is a diagram of an example of DL-PRS bandwidth aggregation across three PFLs in accordance with aspects of the present disclosure. As shown, the same PRS (labeled “PRS1”) is measured on three PFLs (labeled “PFL1,” “PFL2,” “PFL3”). In this scenario, as in the dual-PFL scenario, the maximum bandwidth per PFL capability of the UE can be (1) the same as the maximum bandwidth of the PFL when the PFL is processed without aggregation (as can currently be indicated in the capability report), or (2) a new maximum bandwidth of the PFL that is only reported when this PFL is used for aggregated measurements. Also, the maximum bandwidth of the aggregated PFLs reported by the UE can include the total bandwidth span of the three PFLs, including the two guard bands in between. Alternatively, the maximum bandwidth across the three PFLs can not include the guard bands, and the UE can report a separate capability of the maximum guard band that the UE can tolerate between the two PFLs. Figure 9

[0144] With reference to the specifics of the PFL aggregation capability report, if the UE supports PRS aggregation across two PFLs, the UE can report a “DL-PRS processing capability for dual-PFL aggregation in a frequency band” information element (IE) to the location server (e.g., via the LPP capability transfer procedure 510). This IE can include a parameter / field indicating the maximum DL-PRS bandwidth in MHz per PFL supported and reported by the UE. For FR1 bands, the value can be one of {5, 10, 20, 40, 50, 80, 100}. For FR2 bands, the value can be one of {50, 100, 200, 400}. This IE can also include a parameter indicating the maximum DL-PRS bandwidth in MHz across the two PFLs supported and reported by the UE. For FR1 bands, the value can be one of {10, 20, 40, 50, 80, 100, 200}. For FR2 bands, the value can be one of {100, 200, 400, 800}. ​

[0145] The “DL-PRS processing capability for dual PFL aggregation in a frequency band” IE can also include a parameter indicating the UE’s DL-PRS buffering capability for each PFL as Type 1 or Type 2 (same value applies to both PFLs). Type 1 is sub-slot / symbol level buffering and Type 2 is slot level buffering.

[0146] The “DL-PRS processing capability for dual PFL aggregation in a frequency band” IE can also include a parameter indicating the duration in ms of the number of DL-PRS symbols “N” that the UE is capable of processing every “T” ms (ms) assuming the maximum DL-PRS bandwidth configured per PFL in MHz is configured (same value applies to both PFLs). T can have a reported value as one of {8, 16, 20, 30, 40, 80, 160, 320, 640, 1280} ms and N can have a value as one of {0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50} ms.

[0147] The “DL-PRS processing capability for dual PFL aggregation in a frequency band” IE can also include a parameter indicating the maximum number of DL-PRS resources the UE is capable of processing in a slot for each PFL underneath (again, same value applies to both PFLs). For FR1 bands, for each SCS of 15 kHz, 30 kHz, and 60 kHz, the value can be one of {1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64}. For FR2 bands, for each SCS of 60 kHz and 120 kHz, the value can be one of {1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64}.

[0148] Note that the above parameters can be reported assuming the maximum ratio of configured measurement gap and measurement gap length (MGL) / measurement gap repetition period (MGRP) does not exceed 30%. Also note that if the UE does not indicate this capability for a frequency band (i.e., the “DL-PRS processing capability for dual PFL aggregation in a frequency band” IE), it is assumed that the UE does not support aggregated PRS processing in that frequency band.

[0149] If the UE supports PRS aggregation across three PFLs, the UE can report a “DL-PRS processing capability for three PFL aggregation in a frequency band” IE (e.g., via the LPP capability transfer procedure 510) to the location server. This IE can include a parameter / field indicating the maximum DL-PRS bandwidth in MHz for each PFL supported and reported by the UE. For FR1 bands, the value can be one of {5, 10, 20, 40, 50, 80, 100}. For FR2 bands, the value can be one of {50, 100, 200, 400}. This IE can also include the maximum DL-PRS bandwidth in MHz across all three PFLs supported and reported by the UE. For FR1 bands, the value can be one of {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300}. For FR2 bands, the value can be one of {150, 200, 300, 400, 600, 800, 1200}.

[0150] The “DL-PRS processing capability for three PFL aggregation in a frequency band” IE can also include a parameter indicating the UE’s DL-PRS buffering capability for each PFL as Type 1 or Type 2 (the same value applies to all three PFLs). As noted above, Type 1 is sub-slot / symbol level buffering and Type 2 is slot level buffering.

[0151] The “DL-PRS processing capability for three PFL aggregation in a frequency band” IE can also include a parameter indicating the duration in ms of the number of DL-PRS symbols “N” that the UE is capable of processing every T ms assuming the maximum DL-PRS bandwidth in MHz configured for each PFL supported and reported by the UE (the same value applies to all three PFLs). For dual PFL aggregation, the value of T can be one of {8, 16, 20, 30, 40, 80, 160, 320, 640, 1280} ms and the value of N can be one of {0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50} ms.

[0152] The “DL-PRS processing capability for three PFL aggregation in a band” IE can also include a parameter indicating the maximum number of DL-PRS resources the UE can process per PFL under it in a slot (same value applies to all three PFLs). For FR1 bands, for each SCS of 15 kHz, 30 kHz, and 60 kHz, the value can be one value from {1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64}. For FR2 bands, for each SCS of 60 kHz and 120 kHz, the value can be one value from {1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64}.

[0153] Note that for dual PFL aggregation, the above parameter can be reported under the assumption that the maximum ratio of configured measurement gap and measurement gap length (MGL) / measurement gap repetition period (MGRP) does not exceed 30%. Also, if the UE does not indicate this capability for a band (i.e., the “DL-PRS processing capability for three PFL aggregation in a band” IE), it is assumed that the UE does not support aggregated PRS processing in that band.

[0154] Additionally, if the UE reports that it can aggregate three PFLs, it should also report the capability for dual PFL aggregation. Alternatively, if the UE reports that it can aggregate three PFLs but does not report the capability for dual PFL aggregation, the capability for dual PFL aggregation is considered the same as for three PFL aggregation.

[0155] The UE can also report a buffering capability for DL-PRS processing outside of a measurement gap (MG), referred to as a PRS processing window (PPW). This capability can be reported in a “DL-PRS Processing Capability Outside of MG - Buffering Capability” IE that indicates the type of PRS buffering capability supported, values for N, T, N2, and T2, the maximum number of PRS resources, and the maximum PRS bandwidth. Currently, the “DL-PRS Processing Capability Outside of MG - Buffering Capability” IE can include parameters that indicate the UE’s DL-PRS buffering capability as Type 1 (sub-slot / symbol level buffering) or Type 2 (slot level buffering). The IE can also include a parameter that indicates the duration in ms of the number of DL-PRS symbols “N” that the UE supports and reports that the UE is capable of processing every “T” ms assuming a maximum DL-PRS bandwidth in units of MHz. The IE can further include a parameter that indicates the duration in ms of the number of DL-PRS symbols “N2” that the UE supports and reports that the UE is capable of processing in “T2” ms assuming a maximum DL-PRS bandwidth in units of MHz. The “DL-PRS Processing Capability Outside of MG - Buffering Capability” IE can include a parameter that indicates the maximum number of DL-PRS resources that the UE is capable of processing in a slot. Finally, the “DL-PRS Processing Capability Outside of MG - Buffering Capability” IE can include a parameter that indicates the maximum DL-PRS bandwidth in units of MHz for PRS measurements outside of a MG and within a PRS processing window (PPW) that the UE supports and reports.

[0156] If the UE supports multiple PFL aggregation, the UE can report a separate “DL-PRS Processing Capability Outside of MG - Buffering Capability” IE that indicates its DL-PRS processing capability outside of a MG for aggregated PFLs. In this case, for PRS aggregation PRS buffering type, it can be required that the same buffering type (Type 1 or Type 2) is used for two or three aggregated PFLs. Alternatively, it can be required that the same type is used for two or three aggregated PFLs and legacy (i.e., single PFL / non-aggregated PFL) measured PFLs. For PRS aggregation parameters “T” or “T2”, it can be required that the same values are used for two or three aggregated PFLs and legacy (single PFL / non-aggregated) measured PFLs.

[0157] Further, for dual PFL aggregation, the UE can report (in the “DL-PRS processing capability - buffering capability outside of MG” IE) a total maximum bandwidth value and a maximum bandwidth value per PFL, or the maximum bandwidth per PFL can be inherited from the legacy (i.e., non-aggregated) maximum bandwidth value per PFL capability of the UE. For triple PFL aggregation, the UE can report a total maximum bandwidth value and a maximum bandwidth value per PFL, or the maximum bandwidth per PFL can be inherited from the legacy (i.e., non-aggregated) maximum bandwidth value per PFL capability of the UE.

[0158] The UE can also report (via LPP capability transfer procedure 510) a specific “DL-PRS measurement outside of MG and in PRS processing window” IE that indicates the supported PRS processing type (Type-1A, Type-1B, Type-2) subject to the UE determining that DL-PRS has higher priority for PRS measurement outside of measurement gap and in PRS processing window. There are three options for supporting priority handling options for PRS. The first option is to support “st1” and “st3”, the second option is to support “st1”, “st2” and “st3”, and the third option is to support “st1”. Type-1A refers to determining priority between DL-PRS and other downlink signals / channels in all symbols within the PRS processing window, where downlink signals / channels from all downlink component carriers (per UE) are affected. Type 1B refers to determining priority between DL-PRS and other downlink signals / channels in all symbols within the PRS processing window, where downlink signals / channels from a certain frequency band are affected. Type 2 refers to determining priority between DL-PRS and other downlink signals / channels only in DL-PRS symbols within the PRS processing window. Value “st1” indicates that the priority of DL-PRS is higher than all downlink signals / channels except SSB. Value “st2” indicates that the priority of DL-PRS is lower than physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) scheduled by downlink control information (DCI) format 1_1 or 1_2, where the priority indicator field in the corresponding DCI format is set to “1”, and the priority of DL-PRS is higher than other downlink signals / channels except SSB. Value “st3” indicates that the priority of DL-PRS is lower than all downlink signals / channels except SSB.

[0159] For multi-PFL aggregation, a new DL-PRS processing outside of the MG for supported PRS processing types and priority handling can be defined (e.g., a new “DL-PRS measurement outside of the MG and in the PRS processing window” IE). This capability can be a separate new capability or it can be implicit. Specifically, if the UE reports the currently defined capability (i.e., the “DL-PRS measurement outside of the MG and in the PRS processing window” IE) and it reports a PRS aggregation capability of two or three PFLs, the location server assumes the same value applies for the aggregated PFL processing.

[0160] The UE can also report (via the LPP capability transfer procedure 510) a “DL-PRS processing capability in RRC inactive state” IE. This IE can include a parameter indicating the UE’s DL-PRS buffering capability as Type 1 (sub-slot / symbol level buffering) or Type 2 (slot level buffering), a duration in ms indicating the number of DL-PRS symbols “N” the UE is capable of processing per “T” ms assuming a maximum DL-PRS bandwidth in MHz, and a maximum number of DL-PRS resources the UE is capable of processing in a slot.

[0161] If the UE supports PFL aggregation, the UE can report a similar “DL-PRS processing capability in RRC inactive state” IE indicating the UE’s PRS aggregation PRS processing capability in RRC inactive state. This IE can include the following components. First is a duration in ms of the number of DL-PRS symbols “N” the UE is capable of processing per “T” ms assuming a maximum DL-PRS bandwidth in MHz for each aggregated PFL supported and reported by the UE. Second is a maximum number of DL-PRS resources the UE is capable of processing in a slot for each aggregated PFL.

[0162] The UE can also report (in the “M-sample measurement in RRC CONNECTED” IE) an M-sample measurement capability to support reporting aggregated measurements based on measuring two or three linked aggregated sets of DL-PRS resources / resources for M=1 or M=2 samples (instances). This capability can be a separate new capability for aggregated PFLs or it can be implicit. Specifically, if the UE reports the currently defined M-sample measurement capability and also reports a PRS aggregation capability of two or three PFLs, the location server assumes the UE is capable of processing M=1 or M=2 samples of two or three linked sets of DL-PRS resources / resources (i.e., the number of samples needed across the PFL aggregation).

[0163] Figure 10An example method 1000 of wireless communication is illustrated in accordance with aspects of the present disclosure. In an aspect, method 1000 can be performed by a UE (e.g., any of the UEs described herein).

[0164] At 1010, the UE transmits, to a location server (e.g., LMF 270), at least one provide capabilities message (e.g., LPP Provide Capabilities message) indicating one or more capabilities of the UE to support DL-PRS bandwidth aggregation across multiple aggregated PFLs, where the one or more capabilities include at least a total maximum DL-PRS bandwidth value across multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL. In an aspect, operation 1010 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0165] At 1020, the UE receives, from the location server, a location information request (e.g., LPP Request Location Information message) to report aggregated measurements of one or more DL-PRS resources, or positioning assistance data including DL-PRS resources linked for aggregation purposes (e.g., LPP Provide Assistance Data message), or any combination thereof, based on the one or more capabilities. In an aspect, operation 1020 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0166] As will be appreciated, a technical advantage of method 1000 is enabling the UE to provide a location server with specific capabilities of the UE to support DL-PRS bandwidth aggregation across multiple PFLs.

[0167] In the detailed description above, various features are grouped together in examples. This manner of disclosure should not be understood as an intention that the examples are to be taken in a way that any particular feature is required to be in a particular example. The various aspects of the disclosure can include fewer than all features of an individually disclosed example. Therefore, the following clauses should be taken to be incorporated by reference into the description in which each clause can stand on its own as a separate example. Although each dependent clause can refer to a particular combination of features in a clause, aspects of the dependent clause are not limited to the particular combination. It is understood that other example clauses can also include combinations of aspects of dependent clauses with the subject matter of any other dependent clause or independent clause, or combinations of any features with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations unless it is explicitly expressed or can be readily inferred that a particular combination is not intended (e.g., contradictory aspects such as defining an element as both an electrical insulator and an electrical conductor). Moreover, it is also contemplated that aspects of a clause can be included in any other independent clause even if the clause does not directly depend on the independent clause.

[0168] Various implementation examples are described in the following numbered clauses:

[0169] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: transmitting, to a location server, at least one provide capabilities message indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across a plurality of aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receiving, from the location server, a location information request to report aggregated measurements of one or more DL-PRS resources, or positioning assistance data including linked DL-PRS resources for aggregation purposes, or any combination thereof, based on the one or more capabilities.

[0170] Clause 2. The method of clause 1, wherein: for frequency range 1 (FR1) bands, the maximum DL-PRS bandwidth value per aggregated PFL is selected from {5, 10, 20, 40, 50, 80, 100}, and for frequency range 2 (FR2) bands, the maximum DL-PRS bandwidth value per aggregated PFL is selected from {50, 100, 200, 400}.

[0171] Clause 3. The method of any of clauses 1-2, wherein the maximum DL-PRS bandwidth value per aggregated PFL: is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or is the same as a non-aggregated single PFL maximum DL-PRS bandwidth capability of the UE.

[0172] Clause 4. The method of any of clauses 1-3, wherein: the multiple aggregated PFLs consist of two PFLs, for a FR1 frequency band, the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs is selected from {10, 20, 40, 50, 80, 100, 200}, and for a FR2 frequency band, the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs is selected from {100, 200, 400, 800}.

[0173] Clause 5. The method of any of clauses 1-3, wherein: the multiple aggregated PFLs consist of three PFLs, for a FR1 frequency band, the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs is selected from {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300}, and for a FR2 frequency band, the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs is selected from {150, 200, 300, 400, 600, 800, 1200}.

[0174] Clause 6. The method of any of clauses 1-5, wherein: the one or more capabilities further comprise a DL-PRS buffering capability for each aggregated PFL, and the DL-PRS buffering capability is sub-slot or symbol level buffering, or is slot level buffering.

[0175] Clause 7. The method of clause 6, wherein the DL-PRS buffering capability is the same for each of the multiple aggregated PFLs.

[0176] Clause 8. The method of any of clauses 1-7, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number “N” of DL-PRS symbols that the UE is capable of processing every “T” millisecond (ms) assuming the maximum DL-PRS bandwidth per aggregated PFL.

[0177] Clause 9. The method of clause 8, wherein a value of “T” is the same for each of the multiple aggregated PFLs.

[0178] Clause 10. The method of any of clauses 1-9, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number of DL-PRS symbols “N” that the UE is capable of processing per “T” ms in a radio resource control (RRC) inactive state assuming the maximum DL-PRS bandwidth per aggregation PFL.

[0179] Clause 11. The method of any of clauses 1-10, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources that the UE is capable of processing in a slot per aggregation PFL.

[0180] Clause 12. The method of any of clauses 1-11, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources that the UE is capable of processing in a slot per aggregation PFL in an RRC inactive state.

[0181] Clause 13. The method of any of clauses 1-12, wherein the one or more capabilities further comprise a parameter indicating a capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on “M” samples of the one or more DL-PRS resources.

[0182] Clause 14. The method of clause 13, wherein the parameter indicating the capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on the “M” samples of the one or more DL-PRS resources is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregation PFLs or is the same as a non-aggregated single PFL capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on the “M” samples of the one or more DL-PRS resources of the UE.

[0183] Clause 15. The method of any of clauses 1-14, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement of the one or more DL-PRS resources within a measurement gap.

[0184] Clause 16. The method of any of clauses 1-15, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement of the one or more DL-PRS resources outside of a measurement gap and within a PRS processing window (PPW).

[0185] Clause 17. The method of clause 16, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number of DL-PRS symbols “N2” that the UE is capable of processing per “T2” milliseconds (ms) assuming the maximum DL-PRS bandwidth per aggregate PFL.

[0186] Clause 18. The method of clause 17, wherein a value of “T2” is the same for each of the plurality of aggregate PFLs.

[0187] Clause 19. The method of any of clauses 16 to 18, wherein the one or more capabilities further comprise a parameter indicating a DL-PRS processing type based on a determination that the one or more DL-PRS resources have a higher priority for DL-PRS measurement outside of a measurement gap and within a DL-PRS processing window.

[0188] Clause 20. The method of clause 19, wherein the parameter indicating the DL-PRS processing type is specific to the UE supporting DL-PRS bandwidth aggregation across the plurality of aggregate PFLs or is the same as a non-aggregated single PFL DL-PRS processing type of the UE.

[0189] Clause 21. The method of any of clauses 16 to 20, wherein the one or more capabilities further comprise a parameter indicating a priority handling option for the one or more DL-PRS resources.

[0190] Clause 22. The method of clause 21, wherein the parameter indicating the priority handling option is specific to the UE supporting DL-PRS bandwidth aggregation across the plurality of aggregate PFLs or is the same as a non-aggregated single PFL priority handling option of the UE.

[0191] Clause 23. The method of any of clauses 1 to 22, wherein the at least one provide capabilities message indicates that the one or more capabilities are for three aggregate PFLs.

[0192] Clause 24. The method of clause 23, wherein: the at least one provide capabilities message comprises one or more second capabilities of the UE supporting DL-PRS bandwidth aggregation across two aggregate PFLs, or the one or more capabilities apply to both DL-PRS bandwidth aggregation across two aggregate PFLs and DL-PRS bandwidth aggregation across three aggregate PFLs.

[0193] Clause 25. A user equipment (UE), the UE comprising: at least one memory; at least one transceiver; and at least one processor communicatively coupled to the at least one memory and the at least one transceiver, the at least one processor configured to: send, via the at least one transceiver, to a location server, at least one provide capabilities message indicating that the UE supports one or more capabilities for downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receive, via the at least one transceiver, from the location server, a location information request to report aggregated measurements of one or more DL-PRS resources, or positioning assistance data including linked DL-PRS resources for aggregation purposes, or any combination thereof, based on the one or more capabilities.

[0194] Clause 26. The UE of clause 25, wherein: for frequency range 1 (FR1) bands, the maximum DL-PRS bandwidth value per aggregated PFL is selected from {5, 10, 20, 40, 50, 80, 100}, and for frequency range 2 (FR2) bands, the maximum DL-PRS bandwidth value per aggregated PFL is selected from {50, 100, 200, 400}.

[0195] Clause 27. The UE of any one of clauses 25 to 26, wherein the maximum DL-PRS bandwidth value per aggregated PFL is: specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or the same as a non-aggregated single PFL maximum DL-PRS bandwidth capability of the UE.

[0196] Clause 28. The UE of any one of clauses 25 to 27, wherein: the multiple aggregated PFLs consist of two PFLs, for FR1 bands, the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs is selected from {10, 20, 40, 50, 80, 100, 200}, and for FR2 bands, the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs is selected from {100, 200, 400, 800}.

[0197] Clause 29. The UE of any of Clauses 25 to 27, wherein: the plurality of aggregated PFLs consists of three PFLs, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300} for FR1 bands, and the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {150, 200, 300, 400, 600, 800, 1200} for FR2 bands.

[0198] Clause 30. The UE of any of Clauses 25 to 29, wherein: the one or more capabilities further comprise a DL-PRS buffering capability for each aggregated PFL, and the DL-PRS buffering capability is sub-slot or symbol level buffering, or is slot level buffering.

[0199] Clause 31. The UE of Clause 30, wherein the DL-PRS buffering capability is the same for each of the plurality of aggregated PFLs.

[0200] Clause 32. The UE of any of Clauses 25 to 31, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number “N” of DL-PRS symbols the UE is capable of processing every “T” millisecond (ms) assuming the maximum DL-PRS bandwidth per aggregated PFL.

[0201] Clause 33. The UE of Clause 32, wherein a value of “T” is the same for each of the plurality of aggregated PFLs.

[0202] Clause 34. The UE of any of Clauses 25 to 33, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number “N” of DL-PRS symbols the UE is capable of processing every “T” ms in a radio resource control (RRC) inactive state assuming the maximum DL-PRS bandwidth per aggregated PFL.

[0203] Clause 35. The UE of any of Clauses 25 to 34, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources the UE is capable of processing in a slot for each aggregated PFL.

[0204] Clause 36. The UE of any of Clauses 25 to 35, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources the UE is capable of processing in a slot for each aggregated PFL in an RRC inactive state.

[0205] Clause 37. The UE of any of clauses 25 to 36, wherein the one or more capabilities further comprise a parameter indicating a capability of the UE to report the aggregate measurements of the one or more DL-PRS resources based on ‘M’ samples of the one or more DL-PRS resources.

[0206] Clause 38. The UE of clause 37, wherein the parameter indicating the capability of the UE to report the aggregate measurements of the one or more DL-PRS resources based on the ‘M’ samples of the one or more DL-PRS resources is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs or is the same as a non-aggregated single PFL capability of the UE to report the aggregate measurements of the one or more DL-PRS resources based on the ‘M’ samples of the one or more DL-PRS resources of the UE.

[0207] Clause 39. The UE of any of clauses 25 to 38, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurements of the one or more DL-PRS resources within a measurement gap.

[0208] Clause 40. The UE of any of clauses 25 to 39, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurements of the one or more DL-PRS resources outside of a measurement gap and within a PRS processing window (PPW).

[0209] Clause 41. The UE of clause 40, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number ‘N2’ of DL-PRS symbols per ‘T2’ millisecond (ms) that the UE is capable of processing assuming the maximum DL-PRS bandwidth per aggregated PFL.

[0210] Clause 42. The UE of clause 41, wherein a value of ‘T2’ is the same for each aggregated PFL of the multiple aggregated PFLs.

[0211] Clause 43. The UE of any of clauses 40 to 42, wherein the one or more capabilities further comprise a parameter indicating a DL-PRS processing type based on a determination that the one or more DL-PRS resources have a higher priority for DL-PRS measurements outside of a measurement gap and within a DL-PRS processing window.

[0212] Clause 44. The UE of clause 43, wherein the parameter indicating the DL-PRS processing type: is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or is the same as a non-aggregated single PFL DL-PRS processing type of the UE.

[0213] Clause 45. The UE of any one of clauses 40-44, wherein the one or more capabilities further comprise a parameter indicating a priority handling option for the one or more DL-PRS resources.

[0214] Clause 46. The UE of clause 45, wherein the parameter indicating the priority handling option: is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or is the same as a non-aggregated single PFL priority handling option of the UE.

[0215] Clause 47. The UE of any one of clauses 25-46, wherein the at least one provide capabilities message indicates that the one or more capabilities are for three aggregated PFLs.

[0216] Clause 48. The UE of clause 47, wherein: the at least one provide capabilities message comprises one or more second capabilities that the UE supports DL-PRS bandwidth aggregation across two aggregated PFLs, or the one or more capabilities apply to both DL-PRS bandwidth aggregation across two aggregated PFLs and DL-PRS bandwidth aggregation across three aggregated PFLs.

[0217] Clause 49. A user equipment (UE), comprising: means for sending, to a location server, at least one provide capabilities message indicating one or more capabilities of the UE supporting downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and means for receiving, from the location server, a location information request to report, based on the one or more capabilities, aggregated measurements of one or more DL-PRS resources, or positioning assistance data comprising DL-PRS resources linked for aggregation purposes, or any combination thereof.

[0218] Clause 50. The UE of clause 49, wherein: for frequency range 1 (FR1) bands, the maximum DL-PRS bandwidth value per aggregation PFL is selected from {5, 10, 20, 40, 50, 80, 100} and for frequency range 2 (FR2) bands, the maximum DL-PRS bandwidth value per aggregation PFL is selected from {50, 100, 200, 400}.

[0219] Clause 51. The UE of any of clauses 49 to 50, wherein the maximum DL-PRS bandwidth value per aggregation PFL is: specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregation PFLs, or the same as a non-aggregation single PFL maximum DL-PRS bandwidth capability of the UE.

[0220] Clause 52. The UE of any of clauses 49 to 51, wherein: the multiple aggregation PFLs consist of two PFLs, for FR1 bands, the total maximum DL-PRS bandwidth value across the multiple aggregation PFLs is selected from {10, 20, 40, 50, 80, 100, 200} and for FR2 bands, the total maximum DL-PRS bandwidth value across the multiple aggregation PFLs is selected from {100, 200, 400, 800}.

[0221] Clause 53. The UE of any of clauses 49 to 51, wherein: the multiple aggregation PFLs consist of three PFLs, for FR1 bands, the total maximum DL-PRS bandwidth value across the multiple aggregation PFLs is selected from {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300} and for FR2 bands, the total maximum DL-PRS bandwidth value across the multiple aggregation PFLs is selected from {150, 200, 300, 400, 600, 800, 1200}.

[0222] Clause 54. The UE of any of clauses 49 to 53, wherein: the one or more capabilities further comprise a DL-PRS buffering capability for each aggregation PFL, and the DL-PRS buffering capability is sub-slot or symbol level buffering or is slot level buffering.

[0223] Clause 55. The UE of clause 54, wherein the DL-PRS buffering capability is the same for each of the multiple aggregation PFLs.

[0224] Clause 56. The UE of any of clauses 49 to 55, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number “N” of DL-PRS symbols that the UE is capable of processing per “T” millisecond (ms) assuming the maximum DL-PRS bandwidth per aggregate PFL.

[0225] Clause 57. The UE of clause 56, wherein a value of “T” is the same for each aggregate PFL of the plurality of aggregate PFLs.

[0226] Clause 58. The UE of any of clauses 49 to 57, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number “N” of DL-PRS symbols that the UE is capable of processing per “T” ms in a radio resource control (RRC) inactive state assuming the maximum DL-PRS bandwidth per aggregate PFL.

[0227] Clause 59. The UE of any of clauses 49 to 58, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources that the UE is capable of processing in a slot per aggregate PFL.

[0228] Clause 60. The UE of any of clauses 49 to 59, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources that the UE is capable of processing in a slot in an RRC inactive state per aggregate PFL.

[0229] Clause 61. The UE of any of clauses 49 to 60, wherein the one or more capabilities further comprise a parameter indicating a capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on “M” samples of the one or more DL-PRS resources.

[0230] Clause 62. The UE of clause 61, wherein the parameter indicating the capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on the “M” samples of the one or more DL-PRS resources is specific to the UE supporting DL-PRS bandwidth aggregation across the plurality of aggregate PFLs or is the same as a non-aggregate single PFL capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on the “M” samples of the one or more DL-PRS resources of the UE.

[0231] Clause 63. The UE of any of clauses 49-62, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement on the one or more DL-PRS resources within a measurement gap.

[0232] Clause 64. The UE of any of clauses 49-63, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement on the one or more DL-PRS resources outside of a measurement gap and within a PRS processing window (PPW).

[0233] Clause 65. The UE of clause 64, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number of DL-PRS symbols “N2” that the UE is capable of processing per “T2” milliseconds (ms) assuming the maximum DL-PRS bandwidth per aggregate PFL.

[0234] Clause 66. The UE of clause 65, wherein a value of “T2” is the same for each aggregate PFL of the plurality of aggregate PFLs.

[0235] Clause 67. The UE of any of clauses 64-66, wherein the one or more capabilities further comprise a parameter indicating a DL-PRS processing type based on a determination that the one or more DL-PRS resources have a higher priority for DL-PRS measurement outside of a measurement gap and within a DL-PRS processing window.

[0236] Clause 68. The UE of clause 67, wherein the parameter indicating the DL-PRS processing type: is specific to the UE supporting DL-PRS bandwidth aggregation across the plurality of aggregate PFLs, or is the same as a non-aggregate single PFL DL-PRS processing type of the UE.

[0237] Clause 69. The UE of any of clauses 64-68, wherein the one or more capabilities further comprise a parameter indicating a priority handling option for the one or more DL-PRS resources.

[0238] Clause 70. The UE of clause 69, wherein the parameter indicating the priority handling option: is specific to the UE supporting DL-PRS bandwidth aggregation across the plurality of aggregate PFLs, or is the same as a non-aggregate single PFL priority handling option of the UE.

[0239] Clause 71. The UE of any of clauses 49-70, wherein the at least one provide capabilities message indicates that the one or more capabilities are for three aggregate PFLs.

[0240] Clause 72. The UE of clause 71, wherein: the at least one provide capabilities message includes one or more second capabilities of the UE to support DL-PRS bandwidth aggregation across two aggregated PFLs, or the one or more capabilities apply to both DL-PRS bandwidth aggregation across two aggregated PFLs and DL-PRS bandwidth aggregation across three aggregated PFLs.

[0241] Clause 73. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: send, to a location server, at least one provide capabilities message indicating one or more capabilities of the UE to support downlink positioning reference signal (DL-PRS) bandwidth aggregation across a plurality of aggregated positioning frequency layers (PFLs), wherein the one or more capabilities comprise at least a total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs and a maximum DL-PRS bandwidth value per aggregated PFL; and receive, from the location server, a request for location information to report, based on the one or more capabilities, aggregated measurements of one or more DL-PRS resources, or positioning assistance data including DL-PRS resources linked for aggregation purposes, or any combination thereof.

[0242] Clause 74. The non-transitory computer-readable medium of clause 73, wherein: for frequency range 1 (FR1) bands, the maximum DL-PRS bandwidth value per aggregated PFL is selected from {5, 10, 20, 40, 50, 80, 100}, and for frequency range 2 (FR2) bands, the maximum DL-PRS bandwidth value per aggregated PFL is selected from {50, 100, 200, 400}.

[0243] Clause 75. The non-transitory computer-readable medium of any of clauses 73 to 74, wherein the maximum DL-PRS bandwidth value per aggregated PFL: is specific to the UE supporting DL-PRS bandwidth aggregation across the plurality of aggregated PFLs, or is the same as a non-aggregated single-PFL maximum DL-PRS bandwidth capability of the UE.

[0244] Clause 76. The non-transitory computer-readable medium of any of clauses 73 to 75, wherein: the plurality of aggregated PFLs consists of two PFLs, for FR1 bands, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 20, 40, 50, 80, 100, 200}, and for FR2 bands, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {100, 200, 400, 800}.

[0245] Clause 77. The non-transitory computer-readable medium of any of Clauses 73 to 75, wherein: the plurality of aggregated PFLs consists of three PFLs, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300} for FR1 bands, and the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {150, 200, 300, 400, 600, 800, 1200} for FR2 bands.

[0246] Clause 78. The non-transitory computer-readable medium of any of Clauses 73 to 77, wherein: the one or more capabilities further comprise a DL-PRS buffering capability for each aggregated PFL, and the DL-PRS buffering capability is sub-slot or symbol level buffering, or is slot level buffering.

[0247] Clause 79. The non-transitory computer-readable medium of Clause 78, wherein the DL-PRS buffering capability is the same for each aggregated PFL of the plurality of aggregated PFLs.

[0248] Clause 80. The non-transitory computer-readable medium of any of Clauses 73 to 79, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number of DL-PRS symbols “N” that the UE is capable of processing per “T” ms assuming the maximum DL-PRS bandwidth per aggregated PFL.

[0249] Clause 81. The non-transitory computer-readable medium of Clause 80, wherein a value of “T” is the same for each aggregated PFL of the plurality of aggregated PFLs.

[0250] Clause 82. The non-transitory computer-readable medium of any of Clauses 73 to 81, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number of DL-PRS symbols “N” that the UE is capable of processing per “T” ms in a radio resource control (RRC) inactive state assuming the maximum DL-PRS bandwidth per aggregated PFL.

[0251] Clause 83. The non-transitory computer-readable medium of any of Clauses 73 to 82, wherein the one or more capabilities further comprise a parameter indicating a maximum number of DL-PRS resources that the UE is capable of processing in a slot for each aggregated PFL.

[0252] Clause 84. The non-transitory computer-readable medium of any of clauses 73-83, wherein the one or more capabilities further comprise a parameter indicating that the UE is capable of processing a maximum number of DL-PRS resources per aggregation PFL in a slot in an RRC inactive state.

[0253] Clause 85. The non-transitory computer-readable medium of any of clauses 73-84, wherein the one or more capabilities further comprise a parameter indicating a capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on “M” samples of the one or more DL-PRS resources.

[0254] Clause 86. The non-transitory computer-readable medium of clause 85, wherein the parameter indicating the capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on the “M” samples of the one or more DL-PRS resources is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregation PFLs or is the same as a non-aggregation single PFL capability of the UE to report the aggregate measurement of the one or more DL-PRS resources based on the “M” samples of the one or more DL-PRS resources of the UE.

[0255] Clause 87. The non-transitory computer-readable medium of any of clauses 73-86, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement of the one or more DL-PRS resources within a measurement gap.

[0256] Clause 88. The non-transitory computer-readable medium of any of clauses 73-87, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement of the one or more DL-PRS resources outside of a measurement gap and within a PRS processing window (PPW).

[0257] Clause 89. The non-transitory computer-readable medium of clause 88, wherein the one or more capabilities further comprise a parameter indicating a duration in ms of a number “N2” of DL-PRS symbols that the UE is capable of processing every “T2” millisecond (ms) assuming the maximum DL-PRS bandwidth per aggregation PFL.

[0258] Clause 90. The non-transitory computer-readable medium of clause 89, wherein a value of “T2” is the same for each aggregation PFL of the multiple aggregation PFLs.

[0259] Clause 91. The non-transitory computer-readable medium of any of clauses 88-90, wherein the one or more capabilities further comprise a parameter indicating a DL-PRS processing type based on a determination that the one or more DL-PRS resources have a higher priority for DL-PRS measurement outside of a measurement gap and within a DL-PRS processing window.

[0260] Clause 92. The non-transitory computer-readable medium of clause 91, wherein the parameter indicating the DL-PRS processing type: is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or is the same as a non-aggregated single PFL DL-PRS processing type of the UE.

[0261] Clause 93. The non-transitory computer-readable medium of any of clauses 88-92, wherein the one or more capabilities further comprise a parameter indicating a priority handling option for the one or more DL-PRS resources.

[0262] Clause 94. The non-transitory computer-readable medium of clause 93, wherein the parameter indicating the priority handling option: is specific to the UE supporting DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or is the same as a non-aggregated single PFL priority handling option of the UE.

[0263] Clause 95. The non-transitory computer-readable medium of any of clauses 73-94, wherein the at least one provide capabilities message indicates that the one or more capabilities are for three aggregated PFLs.

[0264] Clause 96. The non-transitory computer-readable medium of clause 95, wherein: the at least one provide capabilities message comprises one or more second capabilities of the UE supporting DL-PRS bandwidth aggregation across two aggregated PFLs, or the one or more capabilities apply to both DL-PRS bandwidth aggregation across two aggregated PFLs and DL-PRS bandwidth aggregation across three aggregated PFLs.

[0265] Those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0266] Moreover, those skilled in the art will appreciate that the functions described herein can be implemented using software functioning in connection with a programmable computer system; programmable logic components, integrated circuit modules, or discrete hardware components; a combination of the foregoing; or any combination thereof. The disclosure includes a computer program product configured to perform the functions described herein. This program product can include instructions that, when executed by a processor, perform the functions described herein, or cause a processor or processors to perform the functions described herein. The instructions can be software readable by a machine or any combination of hardware and software. The disclosure includes a computer program product configured to perform the functions described herein.

[0267] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed 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, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0268] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., an UE). In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

[0269] In one or more example aspects, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A 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 can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, 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.

[0270] While the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications could be made therein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and / or actions of the methods described in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure can be described or claimed in singular form, the plural can also be considered unless expressly stated otherwise.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Send at least one capability provision message to the location server, the at least one capability provision message indicating that the UE supports one or more capabilities of downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities include at least the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and the maximum DL-PRS bandwidth value per aggregated PFL. as well as The location information request is received from the location server, the location information request being used to report aggregated measurements of one or more DL-PRS resources based on the one or more capabilities, or to include location-aided data of DL-PRS resources linked for aggregation purposes, or any combination thereof.

2. The method according to claim 1, wherein: For frequency range 1 (FR1) band, the maximum DL-PRS bandwidth value for each aggregated PFL is selected from {5, 10, 20, 40, 50, 80, 100}, and For the frequency range 2 (FR2) band, the maximum DL-PRS bandwidth value for each aggregated PFL is selected from {50, 100, 200, 400}.

3. The method of claim 1, wherein the maximum DL-PRS bandwidth value for each aggregated PFL is: Specifically for the UE that supports DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or It has the same maximum DL-PRS bandwidth capability as the non-aggregated single PFL of the UE.

4. The method according to claim 1, wherein: The plurality of aggregated PFLs consist of two PFLs. For the FR1 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 20, 40, 50, 80, 100, 200}, and For the FR2 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {100, 200, 400, 800}.

5. The method according to claim 1, wherein: The plurality of aggregated PFLs consist of three PFLs. For the FR1 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300}, and For the FR2 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {150, 200, 300, 400, 600, 800, 1200}.

6. The method according to claim 1, wherein: The one or more capabilities also include DL-PRS buffering capabilities for each aggregated PFL, and The DL-PRS buffering capability is a sub-slot or symbol-level buffer, or a slot-level buffer.

7. The method of claim 6, wherein the DL-PRS buffering capability is the same for each of the plurality of aggregated PFLs.

8. The method of claim 1, wherein the one or more capabilities further include a duration parameter in milliseconds indicating the number of DL-PRS symbols "N" that the UE can process per "T" milliseconds (ms) assuming the maximum DL-PRS bandwidth per aggregated PFL.

9. The method of claim 8, wherein the value of "T" is the same for each of the plurality of aggregated PFLs.

10. The method of claim 1, wherein the one or more capabilities further include a duration parameter in milliseconds indicating the number of DL-PRS symbols "N" that the UE can process per "T" ms in a Radio Resource Control (RRC) inactive state, assuming the maximum DL-PRS bandwidth per aggregated PFL.

11. The method of claim 1, wherein the one or more capabilities further include a parameter indicating the maximum number of DL-PRS resources that the UE can process for each aggregated PFL in a time slot.

12. The method of claim 1, wherein the one or more capabilities further include a parameter indicating the maximum number of DL-PRS resources that the UE can process in a time slot for each aggregated PFL in an RRC inactive state.

13. The method of claim 1, wherein the one or more capabilities further include a parameter instructing the UE to report the aggregated measurement of the one or more DL-PRS resources based on "M" samples of the one or more DL-PRS resources.

14. The method of claim 13, wherein the UE is instructed to report the parameter of the capability of the aggregated measurement of the one or more DL-PRS resources based on the "M" samples of the one or more DL-PRS resources: Specifically for the UE that supports DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or This is the same as the non-aggregated single PFL capability of the UE to report the aggregated measurements of the one or more DL-PRS resources based on the "M" samples of the one or more DL-PRS resources of the UE.

15. The method of claim 1, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement on the one or more DL-PRS resources within a measurement gap.

16. The method of claim 1, wherein the one or more capabilities are reported based on the UE being configured to perform the aggregate measurement on the one or more DL-PRS resources outside of the measurement gap and within the PRS processing window (PPW).

17. The method of claim 16, wherein the one or more capabilities further include a duration parameter in milliseconds indicating the number of DL-PRS symbols "N2" that the UE can process per "T2" milliseconds (ms) assuming the maximum DL-PRS bandwidth per aggregated PFL.

18. The method of claim 17, wherein the value of "T2" is the same for each of the plurality of aggregated PFLs.

19. The method of claim 16, wherein the one or more capabilities further include a parameter indicating the DL-PRS processing type based on determining that the one or more DL-PRS resources have higher priority for DL-PRS measurements outside the measurement gap and within the DL-PRS processing window.

20. The method of claim 19, wherein the parameter indicating the DL-PRS processing type is: Specifically for the UE that supports DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or It is the same as the non-aggregated single PFL DL-PRS processing type of the UE.

21. The method of claim 16, wherein the one or more capabilities further include parameters indicating priority handling options for the one or more DL-PRS resources.

22. The method of claim 21, wherein the parameter indicating the priority handling option: Specifically for the UE that supports DL-PRS bandwidth aggregation across the multiple aggregated PFLs, or The priority handling options are the same as those for the non-aggregated single PFL of the UE.

23. The method of claim 1, wherein the at least one capability provision message indicates that the one or more capabilities are for three aggregated PFLs.

24. The method according to claim 23, wherein: The at least one capability provision message includes one or more second capabilities that the UE supports DL-PRS bandwidth aggregation across two aggregated PFLs, or The one or more capabilities are applied to both DL-PRS bandwidth aggregation across two aggregated PFLs and DL-PRS bandwidth aggregation across three aggregated PFLs.

25. A user equipment (UE), the user equipment (UE) comprising: At least one memory; At least one transceiver; and At least one processor, communicatively coupled to the at least one memory and the at least one transceiver, the at least one processor being configured to: The UE sends at least one capability provision message to the location server via the at least one transceiver, the at least one capability provision message indicating that the UE supports one or more capabilities of downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities include at least the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and the maximum DL-PRS bandwidth value per aggregated PFL. as well as A location information request is received from the location server via the at least one transceiver, the location information request being used to report aggregated measurements of one or more DL-PRS resources based on the one or more capabilities, or to include location-aided data of DL-PRS resources linked for aggregation purposes, or any combination thereof.

26. The UE according to claim 25, wherein: For frequency range 1 (FR1) band, the maximum DL-PRS bandwidth value for each aggregated PFL is selected from {5, 10, 20, 40, 50, 80, 100}, and For the frequency range 2 (FR2) band, the maximum DL-PRS bandwidth value for each aggregated PFL is selected from {50, 100, 200, 400}.

27. The UE according to claim 25, wherein: The plurality of aggregated PFLs consist of two PFLs. For the FR1 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 20, 40, 50, 80, 100, 200}, and For the FR2 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {100, 200, 400, 800}.

28. The UE according to claim 25, wherein: The plurality of aggregated PFLs consist of three PFLs. For the FR1 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 150, 200, 240, 300}, and For the FR2 band, the total maximum DL-PRS bandwidth value across the plurality of aggregated PFLs is selected from {150, 200, 300, 400, 600, 800, 1200}.

29. A user equipment (UE), the user equipment (UE) comprising: A component for sending at least one capability provision message to a location server, the at least one capability provision message indicating that the UE supports one or more capabilities of downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities include at least the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and the maximum DL-PRS bandwidth value per aggregated PFL. and A component for receiving a location information request from the location server, the location information request being used to report aggregated measurements of one or more DL-PRS resources based on the one or more capabilities, or to include location-aided data of DL-PRS resources linked for aggregation purposes, or any combination thereof.

30. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: Sending at least one capability provision message to a location server, the capability provision message indicating that the UE supports one or more capabilities of downlink positioning reference signal (DL-PRS) bandwidth aggregation across multiple aggregated positioning frequency layers (PFLs), wherein the one or more capabilities include at least the total maximum DL-PRS bandwidth value across the multiple aggregated PFLs and the maximum DL-PRS bandwidth value per aggregated PFL; and The location information request is received from the location server, the location information request being used to report aggregated measurements of one or more DL-PRS resources based on the one or more capabilities, or to include location-aided data of DL-PRS resources linked for aggregation purposes, or any combination thereof.

Images