Patent Description:
In a Fifth Generation (<NUM>) New Radio (NR) mobile communication network, a UE may transmit an uplink (UL) Sounding Reference Signal (SRS) that can be received by base stations and/or other Transmission/Reception Points (TRPs) to make angle and/or distance measurements to determine the location of the UE using any of a variety of network-based positioning methods. An increase in a bandwidth of reference signals transmitted by the UE can result in an increase in accuracy of the determined position for the UE. A network may obtain the capabilities of the UE related to bandwidth to help ensure efficient bandwidth usage.

<CIT> discloses a method for signal transmission, a terminal and a network device which relate to a wireless communication field to realize efficient SRS transmission. The method including sending, by a terminal, first indication information to a network device which is used by the network device to determine the second indication information which is used to instruct the terminal to send an SRS signal; receiving, by the terminal, the second indication information sent by the network device; and sending the SRS signal by the terminal according to the second indication information.

<CIT> discloses a system and method for SRS switching in order to transmit SRS symbols over all component carriers,.

A mobile device can report its capabilities to a network node regarding one or more phase characteristics between Sounding Resource Signal (SRS) resources transmitted by the mobile device under one or more circumstances, enabling the network to configure the mobile device accordingly. Such reporting can enable the network to coherently process multiple SRS resources, effectively increasing the bandwidth of the SRS resources and, ultimately, the accuracy of a position determination for the mobile device. Various techniques are provided for reporting capabilities and determining applicable conditions.

Optional features are defined in the dependent claims.

The foregoing, together with other features and examples, will be described in more detail below in the following specification, claims, and accompanying drawings.

Several illustrative embodiments will now be described with respect to the accompanying drawings, which form a part hereof. While some embodiments in which one or more aspects of the disclosure may be implemented as described below, other embodiments may be used, and various modifications may be made.

The following description is directed to certain implementations for the purposes of describing innovative aspects of various embodiments. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations may be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency (RF) signals according to any communication standard, such as any of the Institute of Electrical and Electronics Engineers (IEEE) IEEE <NUM> standards (including those identified as Wi-Fi® technologies), the Bluetooth® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High Rate Packet Data (HRPD), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals that are used to communicate within a wireless, cellular or internet of things (IoT) network, such as a system utilizing <NUM>, <NUM>, <NUM>, <NUM>, or further implementations thereof, technology.

A UE may have certain capabilities with regard to being able to transmit reference signals two one or more Transmission/Reception Point (TRPs) using multiple component carriers (CCs). The use of multiple reference signals in multiple CCs can effectively increase the bandwidth of the reference signals for a measurement taken to determine the location of the UE. More particularly, this increase in bandwidth comes by aggregating the reference signals (e.g., processing the reference signals jointly in the signal domain). The UE's ability to transmit reference signals that may be aggregated (e.g., by a TRP) may be limited by channel spacing, timing offset, phase offset (or phase misalignment), frequency error, power imbalance, and other such factors between reference signals of different CCs. Embodiments provided herein provide for a way in which a UE can provide a report to the network (e.g., a network node) with an indication of its capabilities with respect maintaining one or more phase characteristics (e.g., phase offset, phase ramp, phase slope, and/or phase time drift) between reference signals of different between reference signals of different CCs. The network can respond by configuring the UE accordingly. Additional details are provided herein.

As used herein, an "RF signal" comprises an electromagnetic wave that transports information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a "multipath" RF signal.

Additionally, unless otherwise specified, references to "reference signals," "positioning reference signals," "reference signals for positioning," and the like may be used to refer to signals used for positioning of a user equipment (UE). As described in more detail herein, such signals may comprise any of a variety of signal types but may not necessarily be limited to a Positioning Reference Signal (PRS) as defined in relevant wireless standards.

<FIG> is a simplified illustration of a positioning system <NUM> in which a UE <NUM>, location server <NUM>, and/or other components of the positioning system <NUM> can use the techniques provided herein for providing phase characteristic capability reporting for SRS stitching, according to an embodiment. The techniques described herein may be implemented by one or more components of the positioning system <NUM>. The positioning system <NUM> can include: a UE <NUM>; one or more satellites <NUM> (also referred to as space vehicles (SVs)) for a Global Navigation Satellite System (GNSS) such as the Global Positioning System (GPS), GLONASS, Galileo or Beidou; base stations <NUM>; access points (APs) <NUM>; location server <NUM>; network <NUM>; and external client <NUM>. Generally put, the positioning system <NUM> can estimate a location of the UE <NUM> based on RF signals received by and/or sent from the UE <NUM> and known locations of other components (e.g., GNSS satellites <NUM>, base stations <NUM>, APs <NUM>) transmitting and/or receiving the RF signals. Additional details regarding particular location estimation techniques are discussed in more detail with regard to <FIG>.

It should be noted that <FIG> provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated as necessary. Specifically, although only one UE <NUM> is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system <NUM>. Similarly, the positioning system <NUM> may include a larger or smaller number of base stations <NUM> and/or APs <NUM> than illustrated in <FIG>. The illustrated connections that connect the various components in the positioning system <NUM> comprise data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality. In some embodiments, for example, the external client <NUM> may be directly connected to location server <NUM>. A person of ordinary skill in the art will recognize many modifications to the components illustrated.

Depending on desired functionality, the network <NUM> may comprise any of a variety of wireless and/or wireline networks. The network <NUM> can, for example, comprise any combination of public and/or private networks, local and/or wide-area networks, and the like. Furthermore, the network <NUM> may utilize one or more wired and/or wireless communication technologies. In some embodiments, the network <NUM> may comprise a cellular or other mobile network, a wireless local area network (WLAN), a wireless wide-area network (WWAN), and/or the Internet, for example. Examples of network <NUM> include a Long-Term Evolution (LTE) wireless network, a Fifth Generation (<NUM>) wireless network (also referred to as New Radio (NR) wireless network or <NUM> NR wireless network), a Wi-Fi WLAN, and the Internet. LTE, <NUM> and NR are wireless technologies defined, or being defined, by the 3rd Generation Partnership Project (3GPP). Network <NUM> may also include more than one network and/or more than one type of network.

The base stations <NUM> and access points (APs) <NUM> may be communicatively coupled to the network <NUM>. In some embodiments, the base station <NUM> may be owned, maintained, and/or operated by a cellular network provider, and may employ any of a variety of wireless technologies, as described herein below. Depending on the technology of the network <NUM>, a base station <NUM> may comprise a node B, an Evolved Node B (eNodeB or eNB), a base transceiver station (BTS), a radio base station (RBS), an NR NodeB (gNB), a Next Generation eNB (ng-eNB), or the like. A base station <NUM> that is a gNB or ng-eNB may be part of a Next Generation Radio Access Network (NG-RAN) which may connect to a <NUM> Core Network (5GC) in the case that Network <NUM> is a <NUM> network. An AP <NUM> may comprise a Wi-Fi AP or a Bluetooth® AP or an AP having cellular capabilities (e.g., <NUM> LTE and/or <NUM> NR), for example. Thus, UE <NUM> can send and receive information with network-connected devices, such as location server <NUM>, by accessing the network <NUM> via a base station <NUM> using a first communication link <NUM>. Additionally or alternatively, because APs <NUM> also may be communicatively coupled with the network <NUM>, UE <NUM> may communicate with network-connected and Internet-connected devices, including location server <NUM>, using a second communication link <NUM>, or via one or more other UEs <NUM>.

As used herein, the term "base station" may generically refer to a single physical transmission point, or multiple co-located physical transmission points, which may be located at a base station <NUM>. A Transmission Reception Point (TRP) (also known as transmit/receive point) corresponds to this type of transmission point, and the term "TRP" may be used interchangeably herein with the terms "gNB," "ng-eNB," and "base station. " In some cases, a base station <NUM> may comprise multiple TRPs - e.g. with each TRP associated with a different antenna or a different antenna array for the base station <NUM>. Physical transmission points may comprise an array of antennas of a base station <NUM> (e.g., as in a Multiple Input-Multiple Output (MIMO) system and/or where the base station employs beamforming). The term "base station" may additionally refer to multiple non-co-located physical transmission points, the physical transmission points may be a Distributed Antenna System (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a Remote Radio Head (RRH) (a remote base station connected to a serving base station).

As used herein, the term "cell" may generically refer to a logical communication entity used for communication with a base station <NUM>, and may be associated with an identifier for distinguishing neighboring cells (e.g., a Physical Cell Identifier (PCID), a Virtual Cell Identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine-Type Communication (MTC), Narrowband Internet-of-Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others) that may provide access for different types of devices. In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) over which the logical entity operates.

The location server <NUM> may comprise a server and/or other computing device configured to determine an estimated location of UE <NUM> and/or provide data (e.g., "assistance data") to UE <NUM> to facilitate location measurement and/or location determination by UE <NUM>. According to some embodiments, location server <NUM> may comprise a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support the SUPL user plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for UE <NUM> based on subscription information for UE <NUM> stored in location server <NUM>. In some embodiments, the location server <NUM> may comprise, a Discovered SLP (D-SLP) or an Emergency SLP (E-SLP). The location server <NUM> may also comprise an Enhanced Serving Mobile Location Center (E-SMLC) that supports location of UE <NUM> using a control plane (CP) location solution for LTE radio access by UE <NUM>. The location server <NUM> may further comprise a Location Management Function (LMF) that supports location of UE <NUM> using a control plane (CP) location solution for NR or LTE radio access by UE <NUM>.

In a CP location solution, signaling to control and manage the location of UE <NUM> may be exchanged between elements of network <NUM> and with UE <NUM> using existing network interfaces and protocols and as signaling from the perspective of network <NUM>. In a UP location solution, signaling to control and manage the location of UE <NUM> may be exchanged between location server <NUM> and UE <NUM> as data (e.g. data transported using the Internet Protocol (IP) and/or Transmission Control Protocol (TCP)) from the perspective of network <NUM>.

As previously noted (and discussed in more detail below), the estimated location of UE <NUM> may be based on measurements of RF signals sent from and/or received by the UE <NUM>. In particular, these measurements can provide information regarding the relative distance and/or angle of the UE <NUM> from one or more components in the positioning system <NUM> (e.g., GNSS satellites <NUM>, APs <NUM>, base stations <NUM>). The estimated location of the UE <NUM> can be estimated geometrically (e.g., using multiangulation and/or multilateration), based on the distance and/or angle measurements, along with known position of the one or more components.

Although terrestrial components such as APs <NUM> and base stations <NUM> may be fixed, embodiments are not so limited. Mobile components may be used. For example, in some embodiments, a location of the UE <NUM> may be estimated at least in part based on measurements of RF signals <NUM> communicated between the UE <NUM> and one or more other UEs <NUM>, which may be mobile or fixed. When or more other UEs <NUM> are used in the position determination of a particular UE <NUM>, the UE <NUM> for which the position is to be determined may be referred to as the "target UE," and each of the one or more other UEs <NUM> used may be referred to as an "anchor UE. " For position determination of a target UE, the respective positions of the one or more anchor UEs may be known and/or jointly determined with the target UE. Direct communication between the one or more other UEs <NUM> and UE <NUM> may comprise sidelink and/or similar Device-to-Device (D2D) communication technologies. Sidelink, which is defined by 3GPP, is a form of D2D communication under the cellular-based LTE and NR standards.

An estimated location of UE <NUM> can be used in a variety of applications - e.g. to assist direction finding or navigation for a user of UE <NUM> or to assist another user (e.g. associated with external client <NUM>) to locate UE <NUM>. A "location" is also referred to herein as a "location estimate", "estimated location", "location", "position", "position estimate", "position fix", "estimated position", "location fix" or "fix". The process of determining a location may be referred to as "positioning," "position determination," "location determination," or the like. A location of UE <NUM> may comprise an absolute location of UE <NUM> (e.g. a latitude and longitude and possibly altitude) or a relative location of UE <NUM> (e.g. a location expressed as distances north or south, east or west and possibly above or below some other known fixed location (including, e.g., the location of a base station <NUM> or AP <NUM>) or some other location such as a location for UE <NUM> at some known previous time, or a location of another UE <NUM> at some known previous time). A location may be specified as a geodetic location comprising coordinates which may be absolute (e.g. latitude, longitude and optionally altitude), relative (e.g. relative to some known absolute location) or local (e.g. X, Y and optionally Z coordinates according to a coordinate system defined relative to a local area such a factory, warehouse, college campus, shopping mall, sports stadium or convention center). A location may instead be a civic location and may then comprise one or more of a street address (e.g. including names or labels for a country, state, county, city, road and/or street, and/or a road or street number), and/or a label or name for a place, building, portion of a building, floor of a building, and/or room inside a building etc. A location may further include an uncertainty or error indication, such as a horizontal and possibly vertical distance by which the location is expected to be in error or an indication of an area or volume (e.g. a circle or ellipse) within which UE <NUM> is expected to be located with some level of confidence (e.g. <NUM>% confidence).

The external client <NUM> may be a web server or remote application that may have some association with UE <NUM> (e.g. may be accessed by a user of UE <NUM>) or may be a server, application, or computer system providing a location service to some other user or users which may include obtaining and providing the location of UE <NUM> (e.g. to enable a service such as friend or relative finder, asset tracking or child or pet location). Additionally or alternatively, the external client <NUM> may obtain and provide the location of UE <NUM> to an emergency services provider, government agency, etc..

As previously noted, the example positioning system <NUM> can be implemented using a wireless communication network, such as an LTE-based or <NUM> NR-based network. <FIG> shows a diagram of a <NUM> NR positioning system <NUM>, illustrating an embodiment of a positioning system (e.g., positioning system <NUM>) implementing 5GNR. The <NUM> NR positioning system <NUM> may be configured to determine the location of a UE <NUM> by using access nodes, which may include NR NodeB (gNB) <NUM>-<NUM> and <NUM>-<NUM> (collectively and generically referred to herein as gNBs <NUM>), ng-eNB <NUM>, and/or WLAN <NUM> to implement one or more positioning methods. The gNBs <NUM> and/or the ng-eNB <NUM> may correspond with base stations <NUM> of <FIG>, and the WLAN <NUM> may correspond with one or more access points <NUM> of <FIG>. Optionally, the <NUM> NR positioning system <NUM> additionally may be configured to determine the location of a UE <NUM> by using an LMF <NUM> (which may correspond with location server <NUM>) to implement the one or more positioning methods. Here, the <NUM> NR positioning system <NUM> comprises a UE <NUM>, and components of a <NUM> NR network comprising a Next Generation (NG) Radio Access Network (RAN) (NG-RAN) <NUM> and a <NUM> Core Network (<NUM> CN) <NUM>. A <NUM> network may also be referred to as an NR network; NG-RAN <NUM> may be referred to as a <NUM> RAN or as an NR RAN; and <NUM> CN <NUM> may be referred to as an NG Core network. The <NUM> NR positioning system <NUM> may further utilize information from GNSS satellites <NUM> from a GNSS system like Global Positioning System (GPS) or similar system (e.g. GLONASS, Galileo, Beidou, Indian Regional Navigational Satellite System (IRNSS)). Additional components of the <NUM> NR positioning system <NUM> are described below. The <NUM> NR positioning system <NUM> may include additional or alternative components.

It should be noted that <FIG> provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as necessary. Specifically, although only one UE <NUM> is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the <NUM> NR positioning system <NUM>. Similarly, the <NUM> NR positioning system <NUM> may include a larger (or smaller) number of GNSS satellites <NUM>, gNBs <NUM>, ng-eNBs <NUM>, Wireless Local Area Networks (WLANs) <NUM>, Access and mobility Management Functions (AMF)s <NUM>, external clients <NUM>, and/or other components. The illustrated connections that connect the various components in the <NUM> NR positioning system <NUM> include data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality.

The UE <NUM> may comprise and/or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a Secure User Plane Location (SUPL)-Enabled Terminal (SET), or by some other name. Moreover, UE <NUM> may correspond to a cellphone, smartphone, laptop, tablet, personal data assistant (PDA), navigation device, Internet of Things (IoT) device, or some other portable or moveable device. Typically, though not necessarily, the UE <NUM> may support wireless communication using one or more Radio Access Technologies (RATs) such as using GSM, CDMA, W-CDMA, LTE, High Rate Packet Data (HRPD), IEEE <NUM> Wi-Fi®, Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX™), 5GNR (e.g., using the NG-RAN <NUM> and <NUM> CN <NUM>), etc. The UE <NUM> may also support wireless communication using a WLAN <NUM> which (like the one or more RATs, and as previously noted with respect to <FIG>) may connect to other networks, such as the Internet. The use of one or more of these RATs may allow the UE <NUM> to communicate with an external client <NUM> (e.g., via elements of <NUM> CN <NUM> not shown in <FIG>, or possibly via a Gateway Mobile Location Center (GMLC) <NUM>) and/or allow the external client <NUM> to receive location information regarding the UE <NUM> (e.g., via the GMI,C <NUM>). The external client <NUM> of <FIG> may correspond to external client <NUM> of <FIG>, as implemented in or communicatively coupled with a <NUM> NR network.

The UE <NUM> may include a single entity or may include multiple entities, such as in a personal area network where a user may employ audio, video and/or data I/O devices, and/or body sensors and a separate wireline or wireless modem. An estimate of a location of the UE <NUM> may be referred to as a location, location estimate, location fix, fix, position, position estimate, or position fix, and may be geodetic, thus providing location coordinates for the UE <NUM> (e.g., latitude and longitude), which may or may not include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of the UE <NUM> may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor). A location of the UE <NUM> may also be expressed as an area or volume (defined either geodetically or in civic form) within which the UE <NUM> is expected to be located with some probability or confidence level (e.g., <NUM>%, <NUM>%, etc.). A location of the UE <NUM> may further be a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location which may be defined geodetically, in civic terms, or by reference to a point, area, or volume indicated on a map, floor plan or building plan. In the description contained herein, the use of the term location may comprise any of these variants unless indicated otherwise. When computing the location of a UE, it is common to solve for local X, Y, and possibly Z coordinates and then, if needed, convert the local coordinates into absolute ones (e.g. for latitude, longitude and altitude above or below mean sea level).

Base stations in the NG-RAN <NUM> shown in <FIG> may correspond to base stations <NUM> in <FIG> and may include gNBs <NUM>. Pairs of gNBs <NUM> in NG-RAN <NUM> may be connected to one another (e.g., directly as shown in <FIG> or indirectly via other gNBs <NUM>). The communication interface between base stations (gNBs <NUM> and/or ng-eNB <NUM>) may be referred to as an Xn interface <NUM>. Access to the <NUM> network is provided to UE <NUM> via wireless communication between the UE <NUM> and one or more of the gNBs <NUM>, which may provide wireless communications access to the <NUM> CN <NUM> on behalf of the UE <NUM> using <NUM> NR. The wireless interface between base stations (gNBs <NUM> and/or ng-eNB <NUM>) and the UE <NUM> may be referred to as a Uu interface <NUM>. <NUM> NR radio access may also be referred to as NR radio access or as <NUM> radio access. In <FIG>, the serving gNB for UE <NUM> is assumed to be gNB <NUM>-<NUM>, although other gNBs (e.g. gNB <NUM>-<NUM>) may act as a serving gNB if UE <NUM> moves to another location or may act as a secondary gNB to provide additional throughput and bandwidth to UE <NUM>.

Base stations in the NG-RAN <NUM> shown in <FIG> may also or instead include a next generation evolved Node B, also referred to as an ng-eNB, <NUM>. Ng-eNB <NUM> may be connected to one or more gNBs <NUM> in NG-RAN <NUM>-e.g. directly or indirectly via other gNBs <NUM> and/or other ng-eNBs. An ng-eNB <NUM> may provide LTE wireless access and/or evolved LTE (eLTE) wireless access to UE <NUM>. Some gNBs <NUM> (e.g. gNB <NUM>-<NUM>) and/or ng-eNB <NUM> in <FIG> may be configured to function as positioning-only beacons which may transmit signals (e.g., Positioning Reference Signal (PRS)) and/or may broadcast assistance data to assist positioning of UE <NUM> but may not receive signals from UE <NUM> or from other UEs. Some gNBs <NUM> (e.g., gNB <NUM>-<NUM> and/or another gNB not shown) and/or ng-eNB <NUM> may be configured to function as detecting-only nodes may scan for signals containing, e.g., PRS data, assistance data, or other location data. Such detecting-only nodes may not transmit signals or data to UEs but may transmit signals or data (relating to, e.g., PRS, assistance data, or other location data) to other network entities (e.g., one or more components of <NUM> CN <NUM>, external client <NUM>, or a controller) which may receive and store or use the data for positioning of at least UE <NUM>. It is noted that while only one ng-eNB <NUM> is shown in <FIG>, some embodiments may include multiple ng-eNBs <NUM>. Base stations (e.g., gNBs <NUM> and/or ng-eNB <NUM>) may communicate directly with one another via an Xn communication interface. Additionally or alternatively, base stations may communicate directly or indirectly with other components of the <NUM> NR positioning system <NUM>, such as the LMF <NUM> and AMF <NUM>.

<NUM> NR positioning system <NUM> may also include one or more WLANs <NUM> which may connect to a Non-3GPP InterWorking Function (N3IWF) <NUM> in the <NUM> CN <NUM> (e.g., in the case of an untrusted WLAN <NUM>). For example, the WLAN <NUM> may support IEEE <NUM> Wi-Fi access for UE <NUM> and may comprise one or more Wi-Fi APs (e.g., APs <NUM> of <FIG>). Here, the N3IWF <NUM> may connect to other elements in the <NUM> CN <NUM> such as AMF <NUM>. In some embodiments, WLAN <NUM> may support another RAT such as Bluetooth. The N3IWF <NUM> may provide support for secure access by UE <NUM> to other elements in <NUM> CN <NUM> and/or may support interworking of one or more protocols used by WLAN <NUM> and UE <NUM> to one or more protocols used by other elements of <NUM> CN <NUM> such as AMF <NUM>. For example, N3IWF <NUM> may support IPSec tunnel establishment with UE <NUM>, termination of IKEv2/IPSec protocols with UE <NUM>, termination of N2 and N3 interfaces to <NUM> CN <NUM> for control plane and user plane, respectively, relaying of uplink (UL) and downlink (DL) control plane Non-Access Stratum (NAS) signaling between UE <NUM> and AMF <NUM> across an N1 interface. In some other embodiments, WLAN <NUM> may connect directly to elements in <NUM> CN <NUM> (e.g. AMF <NUM> as shown by the dashed line in <FIG>) and not via N3IWF <NUM>. For example, direct connection of WLAN <NUM> to 5GCN <NUM> may occur if WLAN <NUM> is a trusted WLAN for 5GCN <NUM> and may be enabled using a Trusted WLAN Interworking Function (TWIF) (not shown in <FIG>) which may be an element inside WLAN <NUM>. It is noted that while only one WLAN <NUM> is shown in <FIG>, some embodiments may include multiple WLANs <NUM>.

Access nodes may comprise any of a variety of network entities enabling communication between the UE <NUM> and the AMF <NUM>. As noted, this can include gNBs <NUM>, ng-eNB <NUM>, WLAN <NUM>, and/or other types of cellular base stations. However, access nodes providing the functionality described herein may additionally or alternatively include entities enabling communications to any of a variety of RATs not illustrated in <FIG>, which may include non-cellular technologies. Thus, the term "access node," as used in the embodiments described herein below, may include but is not necessarily limited to a gNB <NUM>, ng-eNB <NUM> or WLAN <NUM>.

In some embodiments, an access node, such as a gNB <NUM>, ng-eNB <NUM>, and/or WLAN <NUM> (alone or in combination with other components of the <NUM> NR positioning system <NUM>), may be configured to, in response to receiving a request for location information from the LMF <NUM>, obtain location measurements of uplink (UL) signals received from the UE <NUM>) and/or obtain downlink (DL) location measurements from the UE <NUM> that were obtained by UE <NUM> for DL signals received by UE <NUM> from one or more access nodes. As noted, while <FIG> depicts access nodes (gNB <NUM>, ng-eNB <NUM>, and WLAN <NUM>) configured to communicate according to <NUM> NR, LTE, and Wi-Fi communication protocols, respectively, access nodes configured to communicate according to other communication protocols may be used, such as, for example, a Node B using a Wideband Code Division Multiple Access (WCDMA) protocol for a Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using an LTE protocol for an Evolved UTRAN (E-UTRAN), or a Bluetooth® beacon using a Bluetooth protocol for a WLAN. For example, in a <NUM> Evolved Packet System (EPS) providing LTE wireless access to UE <NUM>, a RAN may comprise an E-UTRAN, which may comprise base stations comprising eNBs supporting LTE wireless access. A core network for EPS may comprise an Evolved Packet Core (EPC). An EPS may then comprise an E-UTRAN plus an EPC, where the E-UTRAN corresponds to NG-RAN <NUM> and the EPC corresponds to 5GCN <NUM> in <FIG>. The methods and techniques described herein for obtaining a civic location for UE <NUM> may be applicable to such other networks.

The gNBs <NUM> and ng-eNB <NUM> can communicate with an AMF <NUM>, which, for positioning functionality, communicates with an LMF <NUM>. The AMF <NUM> may support mobility of the UE <NUM>, including cell change and handover of UE <NUM> from an access node (e.g., gNB <NUM>, ng-eNB <NUM>, or WLAN <NUM>)of a first RAT to an access node of a second RAT. The AMF <NUM> may also participate in supporting a signaling connection to the UE <NUM> and possibly data and voice bearers for the UE <NUM>. The LMF <NUM> may support positioning of the UE <NUM> using a CP location solution when UE <NUM> accesses the NG-RAN <NUM> or WLAN <NUM> and may support position procedures and methods, including UE assisted/UE based and/or network based procedures/methods, such as Assisted GNSS (A-GNSS), Observed Time Difference Of Arrival (OTDOA) (which may be referred to in NR as Time Difference Of Arrival (TDOA)), Real Time Kinematic (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhance Cell ID (ECID), angle of arrival (AoA), angle of departure (AoD), WLAN positioning, round trip signal propagation delay (RTT), multi-cell RTT, and/or other positioning procedures and methods. The LMF <NUM> may also process location service requests for the UE <NUM>, e.g., received from the AMF <NUM> or from the GMI,C <NUM>. The LMF <NUM> may be connected to AMF <NUM> and/or to GMI,C <NUM>. In some embodiments, a network such as 5GCN <NUM> may additionally or alternatively implement other types of location-support modules, such as an Evolved Serving Mobile Location Center (E-SMLC) or a SUPL Location Platform (SLP). It is noted that in some embodiments, at least part of the positioning functionality (including determination of a UE <NUM>'s location) may be performed at the UE <NUM> (e.g., by measuring downlink PRS (DL-PRS) signals transmitted by wireless nodes such as gNBs <NUM>, ng-eNB <NUM> and/or WLAN <NUM>, and/or using assistance data provided to the UE <NUM>, e.g., by LMF <NUM>).

The Gateway Mobile Location Center (GMLC) <NUM> may support a location request for the UE <NUM> received from an external client <NUM> and may forward such a location request to the AMF <NUM> for forwarding by the AMF <NUM> to the LMF <NUM>. A location response from the LMF <NUM> (e.g., containing a location estimate for the UE <NUM>) may be similarly returned to the GMLC <NUM> either directly or via the AMF <NUM>, and the GMLC <NUM> may then return the location response (e.g., containing the location estimate) to the external client <NUM>.

A Network Exposure Function (NEF) <NUM> may be included in 5GCN <NUM>. The NEF <NUM> may support secure exposure of capabilities and events concerning 5GCN <NUM> and UE <NUM> to the external client <NUM>, which may then be referred to as an Access Function (AF) and may enable secure provision of information from external client <NUM> to 5GCN <NUM>. NEF <NUM> may be connected to AMF <NUM> and/or to GMLC <NUM> for the purposes of obtaining a location (e.g. a civic location) of UE <NUM> and providing the location to external client <NUM>.

As further illustrated in <FIG>, the LMF <NUM> may communicate with the gNBs <NUM> and/or with the ng-eNB <NUM> using an NR Positioning Protocol annex (NRPPa) as defined in 3GPP Technical Specification (TS) <NUM>. NRPPa messages may be transferred between a gNB <NUM> and the LMF <NUM>, and/or between an ng-eNB <NUM> and the LMF <NUM>, via the AMF <NUM>. As further illustrated in <FIG>, LMF <NUM> and UE <NUM> may communicate using an LTE Positioning Protocol (LPP) as defined in 3GPP TS <NUM>. Here, LPP messages may be transferred between the UE <NUM> and the LMF <NUM> via the AMF <NUM> and a serving gNB <NUM>-<NUM> or serving ng-eNB <NUM> for UE <NUM>. For example, LPP messages may be transferred between the LMF <NUM> and the AMF <NUM> using messages for service-based operations (e.g., based on the Hypertext Transfer Protocol (HTTP)) and may be transferred between the AMF <NUM> and the UE <NUM> using a <NUM> NAS protocol. The LPP protocol may be used to support positioning of UE <NUM> using UE assisted and/or UE based position methods such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and/or ECID. The NRPPa protocol may be used to support positioning of UE <NUM> using network based position methods such as ECID, AoA, uplink TDOA (UL-TDOA) and/or may be used by LMF <NUM> to obtain location related information from gNBs <NUM> and/or ng-eNB <NUM>, such as parameters defining DL-PRS transmission from gNBs <NUM> and/or ng-eNB <NUM>.

In the case of UE <NUM> access to WLAN <NUM>, LMF <NUM> may use NRPPa and/or LPP to obtain a location of UE <NUM> in a similar manner to that just described for UE <NUM> access to a gNB <NUM> or ng-eNB <NUM>. Thus, NRPPa messages may be transferred between a WLAN <NUM> and the LMF <NUM>, via the AMF <NUM> and N3IWF <NUM> to support network-based positioning of UE <NUM> and/or transfer of other location information from WLAN <NUM> to LMF <NUM>. Alternatively, NRPPa messages may be transferred between N3IWF <NUM> and the LMF <NUM>, via the AMF <NUM>, to support network-based positioning of UE <NUM> based on location related information and/or location measurements known to or accessible to N3IWF <NUM> and transferred from N3IWF <NUM> to LMF <NUM> using NRPPa. Similarly, LPP and/or LPP messages may be transferred between the UE <NUM> and the LMF <NUM> via the AMF <NUM>, N3IWF <NUM>, and serving WLAN <NUM> for UE <NUM> to support UE assisted or UE based positioning of UE <NUM> by LMF <NUM>.

In a <NUM> NR positioning system <NUM>, positioning methods can be categorized as being "UE assisted" or "UE based. " This may depend on where the request for determining the position of the UE <NUM> originated. If, for example, the request originated at the UE (e.g., from an application, or "app," executed by the UE), the positioning method may be categorized as being UE based. If, on the other hand, the request originates from an external client or AF <NUM>, LMF <NUM>, or other device or service within the <NUM> network, the positioning method may be categorized as being UE assisted (or "network-based").

With a UE-assisted position method, UE <NUM> may obtain location measurements and send the measurements to a location server (e.g., LMF <NUM>) for computation of a location estimate for UE <NUM>. For RAT-dependent position methods location measurements may include one or more of a Received Signal Strength Indicator (RSSI), Round Trip signal propagation Time (RTT), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Time Difference (RSTD), Time of Arrival (TOA), AoA, Receive Time-Transmission Time Difference (Rx-Tx), Differential AoA (DAoA), AoD, or Timing Advance (TA) for gNBs <NUM>, ng-eNB <NUM>, and/or one or more access points for WLAN <NUM>. Additionally or alternatively, similar measurements may be made of sidelink signals transmitted by other UEs, which may serve as anchor points for positioning of the UE <NUM> if the positions of the other UEs are known. The location measurements may also or instead include measurements for RAT-independent positioning methods such as GNSS (e.g., GNSS pseudorange, GNSS code phase, and/or GNSS carrier phase for GNSS satellites <NUM>), WLAN, etc..

With a UE-based position method, UE <NUM> may obtain location measurements (e.g., which may be the same as or similar to location measurements for a UE assisted position method) and may further compute a location of UE <NUM> (e.g., with the help of assistance data received from a location server such as LMF <NUM>, an SLP, or broadcast by gNBs <NUM>, ng-eNB <NUM>, or WLAN <NUM>).

With a network based position method, one or more base stations (e.g., gNBs <NUM> and/or ng-eNB <NUM>), one or more APs (e.g., in WLAN <NUM>), or N3IWF <NUM> may obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AoA, or TOA) for signals transmitted by UE <NUM>, and/or may receive measurements obtained by UE <NUM> or by an AP in WLAN <NUM> in the case of N3IWF <NUM>, and may send the measurements to a location server (e.g., LMF <NUM>) for computation of a location estimate for UE <NUM>.

Positioning of the UE <NUM> also may be categorized as UL, DL, or DL-UL based, depending on the types of signals used for positioning. If, for example, positioning is based solely on signals received at the UE <NUM> (e.g., from a base station or other UE), the positioning may be categorized as DL based. On the other hand, if positioning is based solely on signals transmitted by the UE <NUM> (which may be received by a base station or other UE, for example), the positioning may be categorized as UL based. Positioning that is DL-UL based includes positioning, such as RTT-based positioning, that is based on signals that are both transmitted and received by the UE <NUM>. Sidelink (SL)-assisted positioning comprises signals communicated between the UE <NUM> and one or more other UEs. According to some embodiments, UL, DL, or DL-UL positioning as described herein may be capable of using SL signaling as a complement or replacement of SL, DL, or DL-UL signaling.

Depending on the type of positioning (e.g., UL, DL, or DL-UL based) the types of reference signals used can vary. For DL-based positioning, for example, these signals may comprise PRS (e.g., DL-PRS transmitted by base stations or SL-PRS transmitted by other UEs), which can be used for TDOA, AoD, and RTT measurements. Other reference signals that can be used for positioning (UL, DL, or DL-UL) may include Sounding Reference Signal (SRS), Channel State Information Reference Signal (CSI-RS), synchronization signals (e.g., synchronization signal block (SSB) Synchronizations Signal (SS)), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Shared Channel (PSSCH), Demodulation Reference Signal (DMRS), etc. Moreover, reference signals may be transmitted in a Tx beam and/or received in an Rx beam (e.g., using beamforming techniques), which may impact angular measurements, such as AoD and/or AoA.

<FIG> is a diagram showing an example of a frame structure for NR and associated terminology, which can serve as the basis for physical layer communication between the UE <NUM> and base stations/TRPs. A mini slot may comprise a sub slot structure (e.g., <NUM>, <NUM>, or <NUM> symbols). Additionally shown in <FIG> is the complete Orthogonal Frequency-Division Multiplexing (OFDM) of a subframe, showing how a subframe can be divided across both time and frequency into a plurality of Resource Blocks (RBs). A single RB can comprise a grid of Resource Elements (REs) spanning <NUM> symbols and <NUM> subcarriers.

Each symbol in a slot may indicate a link direction (e.g., downlink (DL), uplink (UL), or flexible) or data transmission and the link direction for each subframe may be dynamically switched. The SS block includes a primary SS (PSS), a secondary SS (SSS), and a two symbol Physical Broadcast Channel (PBCH). The PSS may provide half-frame timing, the SS may provide the cyclic prefix (CP) length and frame timing. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc..

<FIG> are provided to offer some background regarding PRS transmission for positioning within a wireless communication network. It can be noted that, although embodiments described with regard to <FIG> frequently refer to DL-PRS, aspects such as comb type, resource repetition, and the like similarly apply to uplink reference signals (e.g., SRS/UL-PRS).

<FIG> is a diagram showing an example of a radio frame sequence <NUM> with PRS positioning occasions. A "PRS instance" or "PRS occasion" is one instance of a periodically repeated time window (e.g., a group of one or more consecutive slots) where PRS resources (explained in more detail below) are expected to be transmitted. A PRS occasion may also be referred to as a "PRS positioning occasion," a "PRS positioning instance, a "positioning occasion," "a positioning instance," or simply an "occasion" or "instance. " Subframe sequence <NUM> may be applicable to broadcast of PRS signals (DL-PRS signals) from base stations <NUM> in positioning system <NUM>. The radio frame sequence <NUM> may be used in <NUM> NR (e.g., in <NUM> NR positioning system <NUM>) and/or in LTE. Similar to <FIG>, time is represented horizontally (e.g., on an X axis) in <FIG>, with time increasing from left to right. Frequency is represented vertically (e.g., on a Y axis) with frequency increasing (or decreasing) from bottom to top.

<FIG> shows how PRS positioning occasions <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> (collectively and generically referred to herein as positioning occasions <NUM>) are determined by a System Frame Number (SFN), a cell-specific subframe offset (ΔPRS) <NUM>, a length or span of LPRS subframes, and the PRS Periodicity (TPRS) <NUM>. The cell-specific PRS subframe configuration may be defined by a "PRS Configuration Index," IPRS, included in assistance data (e.g., TDOA assistance data), which may be defined by governing 3GPP standards. The cell-specific subframe offset (ΔPRS) <NUM> may be defined in terms of the number of subframes transmitted starting from System Frame Number (SFN) <NUM> to the start of the first (subsequent) PRS positioning occasion.

A PRS may be transmitted by wireless nodes (e.g., base stations <NUM> or other UEs) after appropriate configuration (e.g., by an Operations and Maintenance (O&M) server). A PRS may be transmitted in special positioning subframes or slots that are grouped into positioning occasions <NUM>. For example, a PRS positioning occasion <NUM>-<NUM> can comprise a number NPRS of consecutive positioning subframes where the number NPRS may be between <NUM> and <NUM> (e.g., may include the values <NUM>, <NUM>, <NUM> and <NUM> as well as other values). PRS occasions <NUM> may be grouped into one or more PRS occasion groups. As noted, PRS positioning occasions <NUM> may occur periodically at intervals, denoted by a number TPRS, of millisecond (or subframe) intervals where TPRS may equal <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> (or any other appropriate value). In some embodiments, TPRS may be measured in terms of the number of subframes between the start of consecutive positioning occasions.

In some embodiments, when a UE <NUM> receives a PRS configuration index IPRS in the assistance data for a particular cell (e.g., base station), the UE <NUM> may determine the PRS periodicity TPRS <NUM> and cell-specific subframe offset (ΔPRS) <NUM> using stored indexed data. The UE <NUM> may then determine the radio frame, subframe, and slot when a PRS is scheduled in the cell. The assistance data may be determined by, for example, a location server (e.g., location server <NUM> in <FIG> and/or LMF <NUM> in <FIG>), and includes assistance data for a reference cell, and a number of neighbor cells supported by various wireless nodes.

Typically, PRS occasions from all cells in a network that use the same frequency are aligned in time and may have a fixed known time offset (e.g., cell-specific subframe offset (ΔPRS) <NUM>) relative to other cells in the network that use a different frequency. In SFN-synchronous networks all wireless nodes (e.g., base stations <NUM>) may be aligned on both frame boundary and system frame number. Therefore, in SFN-synchronous networks all cells supported by the various wireless nodes may use the same PRS configuration index for any particular frequency of PRS transmission. On the other hand, in SFN-asynchronous networks, the various wireless nodes may be aligned on a frame boundary, but not system frame number. Thus, in SFN-asynchronous networks the PRS configuration index for each cell may be configured separately by the network so that PRS occasions align in time. A UE <NUM> may determine the timing of the PRS occasions <NUM> of the reference and neighbor cells for TDOA positioning, if the UE <NUM> can obtain the cell timing (e.g., SFN or Frame Number) of at least one of the cells, e.g., the reference cell or a serving cell. The timing of the other cells may then be derived by the UE <NUM> based, for example, on the assumption that PRS occasions from different cells overlap.

With reference to the frame structure in <FIG>, a collection of REs that are used for transmission of PRS is referred to as a "PRS resource. " The collection of resource elements can span multiple RBs in the frequency domain and one or more consecutive symbols within a slot in the time domain, inside which pseudo-random Quadrature Phase Shift Keying (QPSK) sequences are transmitted from an antenna port of a TRP. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive RBs in the frequency domain. The transmission of a PRS resource within a given RB has a particular combination, or "comb," size. (Comb size also may be referred to as the "comb density. ") A comb size "N" represents the subcarrier spacing (or frequency/tone spacing) within each symbol of a PRS resource configuration, where the configuration uses every Nth subcarrier of certain symbols of an RB. For example, for comb-<NUM>, for each of the four symbols of the PRS resource configuration, REs corresponding to every fourth subcarrier (e.g., subcarriers <NUM>, <NUM>, <NUM>) are used to transmit PRS of the PRS resource. Comb sizes of comb-<NUM>, comb-<NUM>, comb-<NUM>, and comb-<NUM>, for example, may be used in PRS. Examples of different comb sizes using with different numbers of symbols are provided in <FIG>.

A "PRS resource set" comprises a group of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. In addition, 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 cell ID). A "PRS resource repetition" is a repetition of a PRS resource during a PRS occasion/instance. The number of repetitions of a PRS resource may be defined by a "repetition factor" for the PRS resource. In addition, the PRS resources in a PRS resource set may have the same periodicity, a common muting pattern configuration, and the same repetition factor across slots. The periodicity may have a length selected from <NUM>m·{<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} slots, with µ = <NUM>, <NUM>, <NUM>, <NUM>. The repetition factor may have a length selected from {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} slots.

A PRS resource ID in a PRS resource set may be associated with a single beam (and/or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource of a PRS resource set may be transmitted on a different beam, and as such, 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 TRPs and the beams on which PRS are transmitted are known to the UE.

In the <NUM> NR positioning system <NUM> illustrated in <FIG>, a TRP (gNB <NUM>, ng-eNB <NUM>, and/or WLAN <NUM>)may transmit frames, or other physical layer signaling sequences, supporting PRS signals (i.e. a DL-PRS) according to frame configurations as previously described, which may be measured and used for position determination of the UE <NUM>. As noted, other types of wireless network nodes, including other UEs, may also be configured to transmit PRS signals configured in a manner similar to (or the same as) that described above. Because transmission of a PRS by a wireless network node may be directed to all UEs within radio range, the wireless network node may be considered to transmit (or broadcast) a PRS.

<FIG> is a diagram of a hierarchical structure of how PRS resources and PRS resource sets may be used by different TRPs of a given position frequency layer (PFL), as defined in <NUM> NR. With respect to a network (Uu) interface, a UE <NUM> can be configured with one or more DL-PRS resource sets from each of one or more TRPs. Each DL-PRS resource set includes K ≥ <NUM> DL-PRS resource(s), which, as previously noted, may correspond to a Tx beam of the TRP. A DL-PRS PFL is defined as a collection of DL-PRS resource sets which have the same subcarrier spacing (SCS) and cyclic prefix (CP) type, the same value of DL-PRS bandwidth, the same center frequency, and the same value of comb size. In current iterations of the NR standard, a UE <NUM> can be configured with up to four DL-PRS PFLs.

NR has multiple frequency bands across different frequency ranges (e.g., Frequency Range <NUM> (FR1) and Frequency Range <NUM> (FR2)). PFLs may be on the same band or different bands. In some embodiments, they may even be in different frequency ranges. Additionally, as illustrated in <FIG>, multiple TRPs (e.g., TRP1 and TR2) may be on the same PFL. Currently under NR, each TRP can have up to two PRS resource sets, each with one or more PRS resources, as previously described.

Different PRS resource sets may have different periodicity. For example, one PRS resource set may be used for tracking, and another PRS resource that could be used for acquisition. Additionally or alternatively, one PRS resource set may have more beams, and another may have fewer beams. Accordingly, different resource sets may be used by a wireless network for different purposes. Example repetition and beam sweeping options for resource sets are illustrated in <FIG>.

<FIG> is a time diagram illustrating two different options for slot usage of a resource set, according to an embodiment. Because each example repeats each resource four times, the resource set is said to have a repetition factor of four. Successive sweeping <NUM> comprises repeating a single resource (resource <NUM>, resource <NUM>, etc.) four times before proceeding to a subsequent resource. In this example, if each resource corresponds to a different beam of a TRP, the TRP repeats a beam for four slots in a row before moving to the next beam. Because each resource is repeated in successive slots (e.g., resource <NUM> is repeated in slots n, n+<NUM>, n+<NUM>, etc.), the time gap is said to be one slot. On the other hand, for interleaved sweeping <NUM>, the TRP may move from one beam to the next for each subsequent slot, rotating through four beams for four rounds. Because each resource is repeated every four slots (e.g., resource <NUM> is repeated in slots n, n+<NUM>, n+<NUM>, etc.), the time gap is said to be one slot. Of course, embodiments are not so limited. Resource sets may comprise a different amount of resources and/or repetitions. Moreover, as noted above, each TRP may have multiple resource sets, multiple TRPs may utilize a single PFL, and a UE may be capable of taking measurements of PRS resources transmitted via multiple FLs.

Thus, to obtain PRS measurements from PRS signals sent by TRPs and/or UEs in a network, the UE can be configured to observe PRS resources during a period of time called a measurement period. That is, to determine a position of the UE using PRS signals, a UE and a location server (e.g., LMF <NUM> of <FIG>) may initiate a location session in which the UE is given a period of time to observe PRS resources and report resulting PRS measurements to the location server. As described in more detail below, this measurement period may be determined based on the capabilities of the UE.

Similar functionality can be implemented to obtain SRS-based measurements. That is, for a network to obtain SRS measurements using one or more TRPs (and/or other UEs) from SRS resources transmitted by a UE <NUM>, the network can configure the UE <NUM> to transmit the SRS resources at a certain period of time. Just as a UE <NUM> may be configured to measure DL-PRS resources of multiple PFLs, a UE <NUM> can be configured to transmit multiple SRS resources using multiple CCs. Accordingly, the network may configure the UE <NUM> to use certain CCs to transmit multiple SRS resources. As previously noted, although SRS resources may be separated in frequency and/or time, TRPs may aggregate multiple SRS resources in certain conditions (e.g., when SRS resources are related through a phase offset and phase slope), processing them jointly rather than independently. This can effectively increase the bandwidth of the SRS resources and increase the accuracy of the measurement (e.g., a TOA measurement) taken by the TRP. This can ultimately increase the accuracy of the determined position of the UE <NUM> based on the measurement because the resolution of the position determination scales inversely with the increase in bandwidth.

The aggregation of SRS resources in different CCs (also referred to herein as "reference signal aggregation" and "SRS aggregation") can be done, for example, by jointly processing the resources by combining them in the signal domain. As used herein, this type of SRS aggregation is referred to as "coherent" processing, or "stitching" together of SRS resources/reference signals. Conversely, where SRS resources are not combined in this manner, it is referred to as "incoherent" processing. Again, coherent processing of SRS resources can take place where SRS resources are separated in frequency and/or time, related through a phase offset and phase slope. As described in more detail below, not only may SRS resources from different CCs be stitched together, but the CCs may be in different frequency bands and/or frequency ranges (FRs).

Because coherent processing of SRS resources from different CCs may be dependent on a phase relationship, or characteristic, between SRS resources, embodiments herein provide for the reporting of the UEs capabilities for maintaining a phase characteristic between SRS resources. That is, according to some embodiments, the UE <NUM> can report its capabilities to a network node regarding the UE's ability to maintaining a phase characteristic between SRS resources under one or more circumstances, enabling the network to configure the UE <NUM> accordingly. According to some embodiments, the UE <NUM> may report its capabilities with regard to an exhaustive set of conditions, and the network can determine the set of conditions that apply, or will apply, to a certain scenario in which SRS resources are transmitted. Alternatively, according to some embodiments, the UE may report its capabilities with regard to a default set of conditions, and at the network can interpret how these report capabilities apply to additional sets of conditions based on a governing standard or other agreed-upon protocol.

<FIG> is a signal flow diagram illustrating how a mobile device <NUM> may communicate capabilities related to a phase characteristic between SRS resources to the network, according to an embodiment. <FIG> illustrates a communication exchange between the mobile device <NUM> and a network node <NUM>. Here, the mobile device <NUM> may correspond to a UE <NUM> as previously described with regard to <FIG>. The network node <NUM> may comprise, for example, a TRP (e.g., serving gNB <NUM>-<NUM> of <FIG>) or location server (e.g., LMF <NUM> of <FIG>). As such, in some embodiments, there may be intervening components that serve to relay the communication (illustrated as arrows in <FIG>) between the mobile device <NUM> and network node <NUM>.

The communication exchange in <FIG> may take place using different protocols and/or within different communication sessions, depending on the type of network node <NUM>. For example, for a network node <NUM> comprising an LMF <NUM>, the communication exchange in <FIG> may take place using LPP protocol, during or before a positioning session between the mobile device <NUM> and LMF <NUM>. Alternatively, if the network node <NUM> comprises a serving gNB <NUM>-<NUM>, the communication exchange in <FIG> may occur during an RRC connection over RRC protocol.

The process may begin at arrow <NUM> and <FIG>, where the network node <NUM> sends a capability request to the mobile device <NUM>. The dashed line in <FIG> indicates optional functionality. In other words, some embodiments may not include the network node <NUM> explicitly providing a capability request to the mobile device <NUM>.

The content of the capability request may vary, depending on desired functionality. According to some embodiments, for example, the capability request <NUM> may solicit the capabilities of the mobile device <NUM> with regard to maintaining a phase characteristic between SRS resources under all conditions. Alternatively, the capability request <NUM> may solicit capabilities under a limited number of conditions, based on different options (e.g., CCs, frequency bands, time slots, etc.) available for transmittal of the SRS resources.

At action <NUM>, the mobile device provides capability reporting to the network node <NUM>. As noted, this may be in response to a capability request <NUM> or may be provided to the network node <NUM> without a request. In short, the capability reporting <NUM> gives the network an indication of the mobile device's capabilities for maintaining a phase relationship between a first SRS and a second SRS. This can enable the network to determine whether to stitch the first and second SRS resources together. The phase relationship may be described as a phase characteristic, such as phase offset, phase ramp, phase slope, or phase time drift.

With regard to phase ramp, the phase ramp can be a phase ramp across time, across frequency, or both. A phase ramp across frequency corresponds, for example, to a case in which the first and second CCs corresponding to the first and second SRS resources have a time drift. A phase ramp across time corresponds, for example, to a case in which there is a Carrier Frequency Offset (CFO) or different doppler shifts between the CCs.

The mobile device's capabilities for maintaining a phase relationship between a first and second SRS may be conveyed in any of a variety of ways. Three such capabilities will be discussed in the examples that follow:.

Given these capabilities the network node <NUM> can, at arrow <NUM>, provide and SRS configuration to the mobile device <NUM>. The SRS configuration may be made to accommodate the mobile devices capabilities in view of available network resources. Additionally or alternatively, the network node <NUM> can similarly configure TRPs to receive SRS transmissions from the mobile device <NUM> in view of the mobile device's capabilities (e.g., indicating to TRP is whether to coherently process SRS resources).

At block <NUM>, the mobile device <NUM> then sends the SRS transmissions in accordance with the SRS configuration received at arrow <NUM>. Because the network node <NUM> may comprise a TRP, the network node <NUM> may receive SRS transmissions from the mobile device <NUM>, as indicated by arrow <NUM>. As noted, the SRS transmissions <NUM> may be received by additional or alternative TRPs. In embodiments where the network node <NUM> comprises an LMF <NUM>, measurements of the SRS transmissions <NUM> taken by one or more TRPs may be forwarded to the LMF <NUM> to determine the position of the mobile device <NUM>.

As noted, the capabilities of the mobile device <NUM> (e.g., capabilities #<NUM> to #<NUM> above) may vary, depending on various conditions. These conditions may include, for example, whether CCs are in the same or different band, whether there is full/partial/no temporal overlap between the SRS resources, whether SRS resources have the same or different bandwidth, and/or whether the comb type of the SRS resources is the same or different. Capabilities additionally may be impacted by a time mask (also known as a "transient period" or "guard period") between one or both SRS resources and a neighboring channel in one of the CCs. Examples of various conditions are provided in <FIG>.

<FIG> is a diagram <NUM> illustrating an example of a first set of conditions, according to an embodiment. The diagram <NUM> plots SRS resources, SRS1 and SRS2, in frequency (e.g., a block of subcarriers) over time, illustrating the relationship in time and frequency one another. Similar to the PRS resources previously described, and SRS resource may occupy different symbols within a slot (e.g., according to a comb structure as illustrated in <FIG>), may span one or more slots, and may be repeated (e.g., as illustrated in <FIG>).

The set of conditions in <FIG> may represent a set of conditions most favorable to maintaining a phase characteristic between SRS1 and SRS2. Specifically, there is full temporal overlap between SRS1 and SRS2 (i.e., they start and end at the same time). Furthermore, there is no overlap between either SRS resource and a time and mask <NUM> resulting from a neighboring channel transmission <NUM>. Additionally, the bandwidth <NUM> of SRS1 is the same as the bandwidth <NUM> of SRS2. Although not shown, the comb type between SRS <NUM> and SRS <NUM> may be the same as well.

As noted, according to some embodiments, the mobile device <NUM> may report capabilities with regard to a default set of conditions, such as the conditions illustrated in <FIG>. In such cases, the network node <NUM> may be able to determine the mobile device's capability under other conditions. For example, capability #<NUM> may represent the mobile device's capability under favorable conditions, capability #<NUM> may represent the mobile device's capability under less favorable conditions, and capability #<NUM> may represent the mobile device's capability under the least favorable conditions. If that is the case, and the mobile device <NUM> reports capability #<NUM> under default (favorable) conditions such as those illustrated in <FIG>, the network node <NUM> can then determine that the mobile device <NUM> has capability #<NUM> under all other conditions. Alternatively, if the mobile device <NUM> reports capability #<NUM> or capability #<NUM> under default conditions, the network node <NUM> may use a set of rules (e.g., as set forth by a governing standard or protocol) to determine which capabilities the mobile device <NUM> has under a different set of conditions, based on the capability reported by the mobile device <NUM>. According to other embodiments, the mobile device <NUM> may provide capabilities under different sets of conditions.

<FIG> is a diagram <NUM> illustrating another set of conditions, according to an embodiment. Here, CC1 and CC2 are located in different frequency bands: Band <NUM> and Band <NUM>, respectively. Additionally, a time mask <NUM> from a neighboring channel transmission <NUM> overlaps with SRS1 and SRS2 for an overlap period <NUM>. Furthermore, the bandwidth <NUM> of SRS1 is different than the bandwidth <NUM> of SRS2. Each of these differences from the conditions in <FIG> may impact the capability of the mobile device <NUM> for maintaining a phase characteristic between SRS1 and SRS2. For example, a mobile device <NUM> having capability #<NUM> under the conditions illustrated in <FIG> may have capabilities #<NUM> and/or #<NUM> for different sets of conditions within a <FIG>.

A time mask <NUM> is a designated period of time for allowing a mobile device to transition from transmitting something on a neighboring channel to transmitting the SRS. The length of time mask <NUM> may be defined (e.g., by a governing standard or protocol) in terms of microseconds. Moreover, the length may vary, depending on the frequency band or frequency range. , time mask <NUM> may be set as <NUM> in FR1 and <NUM> in FR2. ) Further, as illustrated, the neighboring channel transmission <NUM> may comprise a Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), or another SRS resource.

A time mask <NUM> may apply to an SRS on the same CC (e.g., SRS1) as the neighboring channel transmission <NUM>, as well as other CCs in the same frequency band. This is because CCs of the same frequency band often use the same power amplifier (PA), and the neighboring channel transmission <NUM> can result in a frequency-selective phase disruption on SRS within the same frequency band for the length of the time mask <NUM>. That said, as illustrated in <FIG>, a time mask <NUM> may also apply to an SRS in a different band (e.g., SRS2) in cases where the same PA is used for both frequency bands.

The impact of the overlap period <NUM> may vary. For example, according to some embodiments, the mobile device <NUM> may have a first capability during the overlap period <NUM> and a second capability during the non-overlap period <NUM>. These capabilities may be assumed by the network (based on default capabilities reported by the UE <NUM> and applicable set of rules for applying the default capabilities to a time mask overlap) or may be explicitly provided by the mobile device <NUM>. Alternatively, the mobile device <NUM> may have a single capability for the entire duration of SRS1 and SRS2, which may be based in part on the overlap with the time mask <NUM>. For example, where the mobile device <NUM> may otherwise have capability #<NUM> for the duration of SRS1 and SRS2, because of the overlap with time mask <NUM>, it may instead have capability #<NUM> for the entire duration of SRS1 and SRS2.

<FIG> is a diagram <NUM> illustrating yet another set of conditions, according to an embodiment. Here, the diagram <NUM> shows three neighboring CCs in the same band. SRS1 and SRS2 are transmitted in CC1 and CC3, respectively, and a neighboring CC transmission <NUM> (a PUSCH) occurs in CC2 during SRS1 and SRS2. This results in an overlap period <NUM> sandwiched between a first non-overlap period <NUM> and a second non-overlap period <NUM>. According to some embodiments, this may result in a different phase offset between SRS1 and SRS2 for each of these periods. However, if the phase offset remains below a threshold, capability #<NUM> would still apply for the entire duration of SRS1 and SRS2. Alternatively, the neighboring CC transmission <NUM> may result in different capabilities for different periods.

It can be noted that different capabilities may apply to a mobile device <NUM> with respect to different phase characteristics. For example, as noted above, a UE may be able to maintain a phase offset of less than a threshold for each of the periods <NUM>, <NUM>, and <NUM>. Thus the UE may have capability #<NUM> with respect to phase offset for each of these periods <NUM>, <NUM>, and <NUM>. However, the conditions in <FIG> may affect phase offset or phase ramp differently. For example, the neighboring CC transmission <NUM> may cause the UE to have capability #<NUM> and/or #<NUM> for one or more of the periods <NUM>, <NUM>, and <NUM>. With this in mind, according to some embodiments, the UE <NUM> may report (and/or the network node <NUM> may determine) different capabilities with respect to different phase characteristics.

<FIG> is a diagram <NUM> illustrating yet another set of conditions, according to an embodiment. Here, SRS1 and SRS2 only partially overlap in time. The overlapping portion <NUM> may span a set of symbols or one or more slots. Under other conditions (not illustrated) SRS1 and SRS2 may not overlap at all. In the example in <FIG>, however, there is an overlapping portion <NUM> and two nonoverlapping portions <NUM> and <NUM>. Depending on the functionality of the UE <NUM>, there may be differences between the capability of the UE <NUM> during the overlapping portion <NUM> with one or both of the non-overlapping portions <NUM> and <NUM>. Again, depending on desired functionality, these capabilities may be determined by the network via explicit reporting from the UE <NUM> or derivation from a governing specification in view of default capabilities. For example, the UE <NUM> may report a capability with respect to a default condition in which SRS1 and SRS2 fully overlap. The network node <NUM> may apply this capability to the overlapping portion <NUM>, and further extrapolate capabilities for the non-overlapping portions <NUM> and <NUM> based on the reported capability by the UE <NUM> and rules for determining non-overlapping portions as defined in a governing specification or protocol.

<FIG> is a diagram <NUM> illustrating yet another set of conditions, according to an embodiment. The diagram <NUM> and <FIG> illustrates an extreme case with multiple sets of conditions for different periods of time. These periods include <NUM> (a period in which SRS1 overlaps with a time mask), <NUM> (a period in which only SRS1 is being transmitted), <NUM> (periods in which SRS1 and SRS2 overlap), <NUM> (periods in which both SRS1 and SRS2 overlap with a time mask), <NUM> (periods in which both SRS1 and SRS2 overlap with a time mask and PUSCH), <NUM> (a period in which both SRS1 and SRS2 overlap with a PUSCH), and <NUM> (a period in which only SRS2 is being transmitted). The conditions in each of these periods may be considered to determine the capabilities of the mobile device <NUM> with respect to maintaining a phase characteristic between SRS1 and SRS2.

It can further be noted that, according to some embodiments, temporal considerations may also be taken into account. As previously noted, an overlap between an SRS with a time mask may impact the capability not only for the period of overlap between the SRS and time mask, but for the entire duration of the SRS. More generally, different capabilities may apply to a given set of conditions, based on one or more sets of conditions that precede the given set of conditions.

<FIG> is a flow diagram of a method <NUM> of wireless communication at a mobile device, according to an embodiment. The method <NUM> provides for particular reporting of phase characteristic capabilities of the mobile device in the manner indicated in the previously-described embodiments. Means for performing the functionality illustrated in the blocks shown in <FIG> may be performed by hardware and/or software components of a UE. Example components of a UE are illustrated in <FIG>, which are described in more detail below.

At block <NUM>, the functionality comprises sending to a network node, an indication of a capability of the mobile device for maintaining a phase relationship between a first SRS using a first CC and a second SRS using a second CC. The capability comprises an ability to maintain a phase characteristic below a threshold value, an ability to maintain the phase characteristic at a constant value, or an inability to maintain the phase characteristic, or any combination thereof. As discussed in the embodiments above, the phase characteristic may comprise a phase offset; a phase ramp across time, frequency, or both; a phase slope; or a phase time drift; or any combination thereof. Moreover, the capabilities of a UE for maintaining a phase characteristic between the first and second SRS a variety of conditions. As such, the capability of block <NUM> may be dependent on a condition, where the condition comprises whether the first CC and the second CC are in a same or different frequency band, whether the first SRS and the second SRS fully or partially overlap in time, whether the first SRS and the second SRS have a same or different bandwidth, or whether the first SRS and the second SRS have a same or different comb type, or any combination thereof. According to some embodiments, the method <NUM> may further comprise sending an indication of the condition to the network node.

According to some embodiments, additional conditions may apply. For example, the capability may be dependent on whether the first SRS overlaps with a time mask between a channel in the first CC and the first SRS. The channel may comprise a Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), or another SRS resource.

Means for performing functionality at block <NUM> may comprise a wireless communication interface <NUM>, bus <NUM>, digital signal processor (DSP) <NUM>, processor(s) <NUM>, memory <NUM>, and/or other components of a UE <NUM>, as illustrated in <NUM>.

The functionality at block <NUM> comprises transmitting the first SRS and the second SRS. As previously indicated, the network node may comprise a TRP (e.g., serving gNB) or location server (LMF). According to some embodiments, the indication of the capability is sent via Radio Resource Control (RRC) protocol. Means for performing functionality at block <NUM> may comprise a wireless communication interface <NUM>, bus <NUM>, digital signal processor (DSP) <NUM>, processor(s) <NUM>, memory <NUM>, and/or other components of a UE <NUM>, as illustrated in <NUM>.

As previously described and illustrated in <FIG>, sending the indication of the capability of the mobile device and transmitting the first SRS and second SRS may be part of a larger communication exchange with a network node and/or TRPs. For example, the indication of the capability may be sent in response to a capability request from the network node. Additionally or alternatively, the method <NUM> may include, subsequent to sending the indication of the capability, receiving a configuration from the network node for transmitting the first SRS and the second SRS. Transmitting the first SRS and the second SRS may then comprise transmitting the first SRS and the second SRS in accordance with the configuration.

<FIG> is a flow diagram of a method <NUM> of wireless communication at a network node, according to an embodiment. The method <NUM> provides for receiving capability reporting from the mobile device for maintaining a phase relationship in the manner indicated in the previously-described embodiments. Means for performing the functionality illustrated in the blocks shown in <FIG> may be performed by hardware and/or software components of a TRP (e.g., serving gNB) or location server (e.g., LMF). Example components of a TRP and server are illustrated in <FIG> and <FIG>, respectively, which are described in more detail below.

The functionality at block <NUM> comprises, receiving, from a mobile device, an indication of a capability of the mobile device for maintaining a phase relationship between a first SRS transmitted by the mobile device using a first CC and a second SRS transmitted by the mobile device using a second CC. The capability comprises an ability to maintain a phase characteristic below a threshold value, an ability to maintain the phase characteristic at a constant value, or an inability to maintain the phase characteristic, or any combination thereof. Again, the phase characteristic may comprise a phase offset; a phase ramp across time, frequency, or both; a phase slope; or a phase time drift; or any combination thereof. The indication of the capability a be received via RRC protocol.

As noted in the above-described embodiments, a network node may further determine the capabilities of a mobile device based on additional considerations, in addition to the indication of the capability provided by the mobile device. As such, according to some embodiments, the method <NUM> may further comprise determining a second capability, based on the received capability and a determination that the first SRS overlaps with a time mask between a channel in the first CC and the first SRS. The second capability may be determined for an entire duration of the first SRS. Alternatively, the second capability may be determined only for a duration of time during which the first SRS overlaps with the time mask. According to some embodiments, the method <NUM> may further comprising determining a condition related to the transmitting of the first SRS and the second SRS. As noted, an indication of this condition may be explicitly provided to the network node by the mobile device, or otherwise obtained by the network node. The configuration may be further based on the condition. According to some embodiments, the condition can comprise whether the first CC and the second CC are in a same or different frequency band, whether the first SRS and the second SRS fully or partially overlap in time, whether the first SRS and the second SRS have a same or different bandwidth, or whether the first SRS and the second SRS have a same or different comb type, or any combination thereof.

Means for performing functionality at block <NUM> may comprise a wireless communication interface <NUM>, bus <NUM>, digital signal processor (DSP) <NUM>, processor(s) <NUM>, memory <NUM>, and/or other components of a TRP <NUM>, as illustrated in <FIG>; or a wireless communications interface <NUM>, bus <NUM>, processor(s) <NUM>, memory <NUM>, and/or other components of a computer system <NUM>, as illustrated in <FIG>.

The functionality at block <NUM> comprises, sending, to the mobile device, a configuration for transmitting the first SRS and the second SRS, wherein the configuration is based at least in part on the capability. Means for performing functionality at block <NUM> may comprise a wireless communication interface <NUM>, bus <NUM>, digital signal processor (DSP) <NUM>, processor(s) <NUM>, memory <NUM>, and/or other components of a TRP <NUM>, as illustrated in <FIG>; or a wireless communications interface <NUM>, bus <NUM>, processor(s) <NUM>, memory <NUM>, and/or other components of a computer <NUM> system, as illustrated in <FIG>.

<FIG> illustrates an embodiment of a UE <NUM>, which can be utilized as described herein above (e.g., in association with <FIG>). For example, the UE <NUM> can perform one or more of the functions of the method shown in <FIG>. It should be noted that <FIG> is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It can be noted that, in some instances, components illustrated by <FIG> can be localized to a single physical device and/or distributed among various networked devices, which may be disposed at different physical locations. Furthermore, as previously noted, the functionality of the UE discussed in the previously described embodiments may be executed by one or more of the hardware and/or software components illustrated in <FIG>.

The UE <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include a processor(s) <NUM> which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structures or means. As shown in <FIG>, some embodiments may have a separate DSP <NUM>, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processor(s) <NUM> and/or wireless communication interface <NUM> (discussed below). The UE <NUM> also can include one or more input devices <NUM>, which can include without limitation one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, and/or the like; and one or more output devices <NUM>, which can include without limitation one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, and/or the like.

The UE <NUM> may also include a wireless communication interface <NUM>, which may comprise without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth® device, an IEEE <NUM> device, an IEEE <NUM>. <NUM> device, a Wi-Fi device, a WiMAX device, a WAN device, and/or various cellular devices, etc.), and/or the like, which may enable the UE <NUM> to communicate with other devices as described in the embodiments above. As such, the wireless communication interface <NUM> can include RF circuitry capable of being tuned between an active BWP and one or additional bands having one or more FLs used for PRS signals, as described herein. The wireless communication interface <NUM> may permit data and signaling to be communicated (e.g., transmitted and received) with TRPs of a network, for example, via eNBs, gNBs, ng-eNBs, access points, various base stations and/or other access node types, and/or other network components, computer systems, and/or any other electronic devices communicatively coupled with TRPs, as described herein. The communication can be carried out via one or more wireless communication antenna(s) <NUM> that send and/or receive wireless signals <NUM>. According to some embodiments, the wireless communication antenna(s) <NUM> may comprise a plurality of discrete antennas, antenna arrays, or any combination thereof.

Depending on desired functionality, the wireless communication interface <NUM> may comprise a separate receiver and transmitter, or any combination of transceivers, transmitters, and/or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers, such as wireless devices and access points. The UE <NUM> may communicate with different data networks that may comprise various network types. For example, a Wireless Wide Area Network (WWAN) may be a CDMA network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, a WiMAX (IEEE <NUM>) network, and so on. A CDMA network may implement one or more RATs such as CDMA2000, WCDMA, and so on. CDMA2000 includes IS-<NUM>, IS-<NUM> and/or IS-<NUM> standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ LTE, LTE Advanced, <NUM> NR, and so on. <NUM> NR, LTE, LTE Advanced, GSM, and WCDMA are described in documents from 3GPP. Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project <NUM>" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A WLAN may also be an IEEE <NUM>. 11x network, and a wireless personal area network (WPAN) may be a Bluetooth network, an IEEE <NUM>. 15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.

The UE <NUM> can further include sensor(s) <NUM>. Sensors <NUM> may comprise, without limitation, one or more inertial sensors and/or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), and the like), some of which may be used to obtain position-related measurements and/or other information.

Embodiments of the UE <NUM> may also include a Global Navigation Satellite System (GNSS) receiver <NUM> capable of receiving signals <NUM> from one or more GNSS satellites using an antenna <NUM> (which could be the same as antenna <NUM>). Positioning based on GNSS signal measurement can be utilized to complement and/or incorporate the techniques described herein. The GNSS receiver <NUM> can extract a position of the UE <NUM>, using conventional techniques, from GNSS satellites <NUM> of a GNSS system, such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, BeiDou Navigation Satellite System (BDS) over China, and/or the like. Moreover, the GNSS receiver <NUM> can be used with various augmentation systems (e.g., a Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems, such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), and Geo Augmented Navigation system (GAGAN), and/or the like.

It can be noted that, although GNSS receiver <NUM> is illustrated in <FIG> as a distinct component, embodiments are not so limited. As used herein, the term "GNSS receiver" may comprise hardware and/or software components configured to obtain GNSS measurements (measurements from GNSS satellites). In some embodiments, therefore, the GNSS receiver may comprise a measurement engine executed (as software) by one or more processors, such as processor(s) <NUM>, DSP <NUM>, and/or a processor within the wireless communication interface <NUM> (e.g., in a modem). A GNSS receiver may optionally also include a positioning engine, which can use GNSS measurements from the measurement engine to determine a position of the GNSS receiver using an Extended Kalman Filter (EKF), Weighted Least Squares (WLS), a hatch filter, particle filter, or the like. The positioning engine may also be executed by one or more processors, such as processor(s) <NUM> or DSP <NUM>.

The UE <NUM> may further include and/or be in communication with a memory <NUM>. The memory <NUM> can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (RAM), and/or a read-only memory (ROM), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

The memory <NUM> of the UE <NUM> also can comprise software elements (not shown in <FIG>), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions in memory <NUM> that are executable by the UE <NUM> (and/or processor(s) <NUM> or DSP <NUM> within UE <NUM>). In an aspect, then such code and/or instructions can be used to configure and/or adapt a general-purpose computer (or other device) to perform one or more operations in accordance with the described methods.

<FIG> illustrates an embodiment of a TRP <NUM>, which can be utilized as described herein above (e.g., in association with <FIG>), and may further perform the functions of one or more of the blocks shown in <FIG>. It should be noted that <FIG> is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate.

The TRP <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include a processor(s) <NUM> which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics acceleration processors, ASICs, and/or the like), and/or other processing structure or means. As shown in <FIG>, some embodiments may have a separate DSP <NUM>, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processor(s) <NUM> and/or wireless communication interface <NUM> (discussed below), according to some embodiments. The TRP <NUM> also can include one or more input devices, which can include without limitation a keyboard, display, mouse, microphone, button(s), dial(s), switch(es), and/or the like; and one or more output devices, which can include without limitation a display, light emitting diode (LED), speakers, and/or the like.

The TRP <NUM> might also include a wireless communication interface <NUM>, which may comprise without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth® device, an IEEE <NUM> device, an IEEE <NUM>. <NUM> device, a Wi-Fi device, a WiMAX device, cellular communication facilities, etc.), and/or the like, which may enable the TRP <NUM> to communicate as described herein. The wireless communication interface <NUM> may permit data and signaling to be communicated (e.g., transmitted and received) to UEs, other base stations/TRPs (e.g., eNBs, gNBs, and ng-eNBs), and/or other network components, computer systems, and/or any other electronic devices described herein. The communication can be carried out via one or more wireless communication antenna(s) <NUM> that send and/or receive wireless signals <NUM>.

The TRP <NUM> may also include a network interface <NUM>, which can include support of wireline communication technologies. The network interface <NUM> may include a modem, network card, chipset, and/or the like. The network interface <NUM> may include one or more input and/or output communication interfaces to permit data to be exchanged with a network, communication network servers, computer systems, and/or any other electronic devices described herein.

In many embodiments, the TRP <NUM> may further comprise a memory <NUM>. The memory <NUM> can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a RAM, and/or a ROM, which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

The memory <NUM> of the TRP <NUM> also may comprise software elements (not shown in <FIG>), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions in memory <NUM> that are executable by the TRP <NUM> (and/or processor(s) <NUM> or DSP <NUM> within TRP <NUM>). In an aspect, then such code and/or instructions can be used to configure and/or adapt a general-purpose computer (or other device) to perform one or more operations in accordance with the described methods.

<FIG> is a block diagram of an embodiment of a computer system <NUM>, which may be used, in whole or in part, to provide the functions of one or more network components as described in the embodiments herein (e.g., location server <NUM> of <FIG>, LMF <NUM> of <FIG>, etc.). It should be noted that <FIG> is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. <FIG>, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner. In addition, it can be noted that components illustrated by <FIG> can be localized to a single device and/or distributed among various networked devices, which may be disposed at different geographical locations.

The computer system <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include processor(s) <NUM>, which may comprise without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like), and/or other processing structure, which can be configured to perform one or more of the methods described herein. The computer system <NUM> also may comprise one or more input devices <NUM>, which may comprise without limitation a mouse, a keyboard, a camera, a microphone, and/or the like; and one or more output devices <NUM>, which may comprise without limitation a display device, a printer, and/or the like.

The computer system <NUM> may further include (and/or be in communication with) one or more non-transitory storage devices <NUM>, which can comprise, without limitation, local and/or network accessible storage, and/or may comprise, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a RAM and/or ROM, which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like. Such data stores may include database(s) and/or other data structures used store and administer messages and/or other information to be sent to one or more devices via hubs, as described herein.

The computer system <NUM> may also include a communications subsystem <NUM>, which may comprise wireless communication technologies managed and controlled by a wireless communication interface <NUM>, as well as wired technologies (such as Ethernet, coaxial communications, universal serial bus (USB), and the like). The wireless communication interface <NUM> may send and receive wireless signals <NUM> (e.g., signals according to <NUM> NR or LTE) via wireless antenna(s) <NUM>. Thus the communications subsystem <NUM> may comprise a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset, and/or the like, which may enable the computer system <NUM> to communicate on any or all of the communication networks described herein to any device on the respective network, including a User Equipment (UE), base stations and/or other TRPs, and/or any other electronic devices described herein. Hence, the communications subsystem <NUM> may be used to receive and send data as described in the embodiments herein.

In many embodiments, the computer system <NUM> will further comprise a working memory <NUM>, which may comprise a RAM or ROM device, as described above. Software elements, shown as being located within the working memory <NUM>, may comprise an operating system <NUM>, device drivers, executable libraries, and/or other code, such as one or more applications <NUM>, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.

A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) <NUM> described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system <NUM>. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as an optical disc), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system <NUM> and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system <NUM> (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.

For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both.

With reference to the appended figures, components that can include memory can include non-transitory machine-readable media. The term "machine-readable medium" and "computer-readable medium" as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion. In embodiments provided hereinabove, various machine-readable media might be involved in providing instructions/code to processors and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Common forms of computer-readable media include, for example, magnetic and/or optical media, any other physical medium with patterns of holes, a RAM, a programmable ROM (PROM), erasable PROM (EPROM), a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read instructions and/or code.

The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the figures provided herein can be embodied in hardware and/or software. Also, technology evolves and, thus many of the elements are examples.

It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, numerals, or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as is apparent from the discussion above, it is appreciated that throughout this Specification discussion utilizing terms such as "processing," "computing," "calculating," "determining," "ascertaining," "identifying," "associating," "measuring," "performing," or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this Specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.

Terms, "and" and "or" as used herein, may include a variety of meanings that also is expected to depend, at least in part, upon the context in which such terms are used. Typically, "or" if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B, or C, here used in the exclusive sense. In addition, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in the singular or may be used to describe some combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example and claimed subject matter is not limited to this example. Furthermore, the term "at least one of" if used to associate a list, such as A, B, or C, can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc..

Claim 1:
A method (<NUM>) of wireless communication at a mobile device, the method comprising :
sending (<NUM>), to a network node, an indication of a capability of the mobile device for maintaining a phase relationship between a first Sounding Reference Signal, SRS, using a first Component Carrier, CC, and a second SRS using a second CC, wherein the capability comprises:
an ability to maintain a phase characteristic below a threshold value,
an ability to maintain the phase characteristic at a constant value, or
an inability to maintain the phase characteristic, or
any combination thereof; and
transmitting (<NUM>) the first SRS and the second SRS.