Patent Description:
Obtaining the location of a mobile device that is accessing a wireless network may be useful for many applications including, for example, emergency calls, personal navigation, asset tracking, locating a friend or family member, etc. Existing location methods include methods based on measuring the timing of radio signals received from a variety of devices including, for example, satellite vehicles (SVs), terrestrial radio sources (e.g., a base station), etc. in a multiple-access wireless network. Examples of such multiple-access networks include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, etc. A FDMA network may include, for example, Orthogonal FDMA (OFDMA) networks, Single-Carrier FDMA (SC-FDMA) networks, etc. It is expected that standardization for new fifth-generation (<NUM>) wireless networks will include support for various positioning methods, both new and existing, such as Observed Time Difference Of Arrival (OTDOA), Enhanced Cell ID (E-CID), among others.

A base station in a <NUM> network can transmit signals to support various positioning methods using multiple directional radio beams. Various attributes of the radio beams, such as beam widths, can affect the accuracy of the positioning operations. Embodiments disclosed herein enable positioning operations to be adapted according to the attributes of the radio beams transmitted by different base stations, to improve the accuracy of positioning operations in <NUM> wireless networks.

<CIT> discloses mechanisms for providing location information in a communications network. A method is performed by a first device. The first device supports positioning of other devices in the communications network. The method comprises acquiring positioning reference signal configuration from a radio network node in the communications network. The method comprises acquiring location information from a local positioning entity. The method comprises providing the location information to at least one of a radio network node and a second device in the communications network. The method comprises transmitting a positioning reference signal according to the positioning reference signal configuration.

<CIT> discloses a composite measurement used to determine a position of a target wireless device. The composite measurement may include a result of at least two measurement components. The two measurement components may be measurements performed on physical signal and/or channels transmitted from a same transmitting node and measured by a measuring node. Each measurement component includes one or more measurement configurations, where each configuration is of a resource, signal, transmitter, and receiver configuration types. The two measurement components have configurations of at least one common configuration type in which the configurations of the common type are different for the two measurement components.

Any reference to "embodiment(s)", "example(s)" or "aspect(s)" in this description not falling under the scope of the claims should be interpreted as illustrative example(s) for understanding the invention".

The present disclosure provides a method for wireless communication, the method being performed by a location server and comprising: obtaining beam support information of a plurality of cells; configuring a location determination operation for a mobile device based on the beam support information of the plurality of cells, the location determination operation comprising measurements of one or more signals to be performed by at least one of the mobile device or one or more cells of the plurality of cells; receiving results of the measurements of the one or more signals; and determining a location of the mobile device based on the results of the measurements of the one or more signals.

In some aspects, the beam support information comprises at least one of: a number of beams supported at each cell of the plurality of cells, information to identify each beam of the number of beams supported at the each cell, beam width information of the each beam, or Positioning reference Signals (PRS) codebook information which encapsulates the beams which are enabled along various elevation and azimuth angles.

In some aspects, the information to identify each beam of the number of beams supported at the each cell comprises a bitmap. Each bit of the bitmap corresponds to a beam, and a value of the each bit indicates whether the beam is supported at the each cell.

In some aspects, the method further comprises transmitting a query to each base station of each cell of the plurality of cells to request the beam support information. The beam support information is obtained after the query is transmitted. In some examples, the query is transmitted under New Radio Location Protocol A (NRPPa) protocol.

In some aspects, the method further comprises transmitting an information request to each base station of each cell of the plurality of cells, the information request including a list of information items, one of the list of information items including the beam support information. The beam support information is obtained after the information request is transmitted. The information request may be included in at least one of: an Enhanced Cell ID (E-CID) measurement initiation request message, or an Observed Time Difference Of Arrival (OTDOA) information request message. The information request can be transmitted under NRPPa protocol.

In some aspects, the beam support information is not obtained from base stations of the plurality of cells. Instead, the beam support information is obtained from at least one of: a maintenance operation of the location server, or a programming operation of the location server.

In some aspects, configuring the location determination operation for the mobile device comprises: generating configuration data based on the beam support information; and transmitting the configuration data to the mobile device, to enable the mobile device to perform the measurements of one or more signals with a subset of cells of the plurality of cells for the location determination operation. The configuration data may include Assistance Data.

In some aspects, the method further comprises: ranking the subset of cells based on number of beams supported at the each cell included in the beam support information. The subset of cells supports highest numbers of beams among the plurality of cells.

In some aspects, the method further comprises ranking the subset of cells based on beam width of the beams supported at the each cell included in the beam support information. The subset of cells supports narrowest beams among the plurality of cells.

In some aspects, the configuration data includes information of the subset of cells. In some examples, the configuration data includes the beam support information of each cell of the plurality of cells. In some examples, the measurements of one or more signals comprise at least one of: measurements of Positioning Reference Signals (PRS), measurements of Reference Signal Received Power (RSRP), measurements of Reference Signal Received Quality (RSRQ), Timing Advance, or Angle of Arrival (AoA).

In some aspects, configuring the location determination operation for the mobile device comprises: selecting, based on the beam support information, a subset of cells of the plurality of cells; and transmitting a signal measurement request to the subset of cells to initiate the location determination operation at the subset of cells. The signal measurement request comprises at least one of: an E-CID measurement initiation request message, or an OTDOA information request message.

In some aspects, configuring the location determination operation for the mobile device comprises: selecting, based on the beam support information, a subset of cells of the plurality of cells; and updating a schedule of PRS transmission at the subset of cells. Updating a schedule of PRS transmission at the subset of cells comprises at least one of: updating a duration of each PRS signal, updating a period between the each PRS signal, or updating a bandwidth allocated for the each PRS signal.

The present disclosure also provides a location server configured to perform the method for the wireless communication as described above. The location server may include a processor to execute a set of instructions stored in a non-transitory computer readable medium to perform the method for the wireless communication as described above.

The present disclosure also provides a method for wireless communication, the method being performed by a mobile device, the method comprising: obtaining beam support information of a plurality of cells; performing measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells to support a location determination operation for the mobile device; and transmitting results of the measurements of the one or more signals to at least one of a location server or a base station to support the location determination operation.

In some aspects, the information to identify each beam of the number of beams supported at the each cell comprises a bitmap. Each bit of the bitmap corresponds to a beam. A value of the each bit indicates whether the beam is supported at the each cell.

In some aspects, the beam support information is obtained from configuration data provided from a location server. The configuration data may include a subset of the plurality of cells which support beams that are targeted at a location of the mobile device. In some examples, the beam support information is obtained from base stations of the plurality of cells. The beam support information is obtained via at least one of: Radio Resource Control (RRC) Reconfiguration messages from the plurality of cells, or System Information Block Type <NUM> (SIB1) messages from the plurality of cells.

In some aspects, performing measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells comprises: selecting, based on the beam support information, a subset of cells of the plurality of cells; and performing the measurements with the subset of cells. The measurements of the one or more signals comprise at least one of: measurements of Positioning Reference Signals (PRS), measurements of Reference Signal Received Power (RSRP), or measurements of Reference Signal Received Quality (RSRQ).

In some aspects, performing measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells comprises: selecting, based on the beam support information, a subset of cells of the plurality of cells; and transmitting a request to the subset of cells to update a schedule of PRS transmission at the subset of cells. In some examples, updating a schedule of PRS transmission at the subset of cells comprises at least one of: updating a duration of each PRS signal, updating a period between the each PRS signal, or updating a bandwidth allocated for the each PRS signal.

The present disclosure also provides a mobile device, such as a User Equipment (UE), configured to perform the method for the wireless communication as described above. The UE may include a processor to execute a set of instructions stored in a non-transitory computer readable medium to: obtain beam support information of a plurality of cells; perform measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells to support a location determination operation for the mobile device; and transmit results of the measurements of the one or more signals to at least one of a location server or to a base station to support the location determination operation.

In some aspects, the beam support information is obtained from configuration data provided from the location server.

In some aspects, the configuration data identifies a subset of cells of the plurality of cells which support beams that are targeted at a location of the mobile device. The configuration data further includes information of the subset of cells.

In some aspects, the configuration data includes the beam support information of each cell of the plurality of cells. The configuration data may include Assistance Data.

In some aspects, the beam support information is obtained from base stations of the plurality of cells. The beam support information can be obtained by the location server from the base stations based on a query transmitted under New Radio Location Protocol A (NRPPa) protocol. The beam support information can be obtained by the location server from the base stations based on an information request.

In some aspects, the information request includes a list of information items, one of the list of information items including the beam support information.

In some aspects, the beam support information is obtained from at least one of: a maintenance operation of the location server, or a programming operation of the location server.

In some aspects, the beam support information is obtained via at least one of: Radio Resource Control (RRC) Reconfiguration messages from the plurality of cells, or System Information Block Type <NUM> (SIB1) messages from the plurality of cells.

In some aspects, the hardware processor is configured to execute the set of instructions to: select, based on the beam support information, a subset of cells of the plurality of cells; and perform the measurements of the one or more signals with the subset of cells.

In some aspects, the measurements of the one or more signals comprise at least one of: measurements of Positioning Reference Signals (PRS), measurements of Reference Signal Received Power (RSRP), measurements of Reference Signal Received Quality (RSRQ), Timing Advance, or Angle of Arrival (AoA).

In some aspects, the hardware processor is configured to execute the set of instructions to: select, based on the beam support information, a subset of cells of the plurality of cells; and transmit a request to the subset of cells to update a schedule of PRS transmission at the subset of cells. The updating a schedule of PRS transmission at the subset of cells comprises at least one of: updating a duration of each PRS signal, updating a period between the each PRS signal, or updating a bandwidth allocated for the each PRS signal. In some aspects, the subset of cells supports a highest number of beams among the plurality of cells. In some aspects, the subset of cells supports narrowest beams among the plurality of cells.

The present disclosure also provides a method of wireless communication. The method comprises: obtaining, by a mobile device, beam support information of a plurality of cells; performing, by the mobile device, measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells to support a location determination operation for the mobile device; and transmitting, by the mobile device, results of the measurements of the one or more signals to at least one of a location server or to a base station to support the location determination operation.

In some aspects, the beam support information comprises at least one of: a number of beams supported at each cell of the plurality of cells, information to identify each beam of the number of beams supported at the each cell, beam width information of the each beam, or Positioning reference Signals (PRS) codebook information which encapsulates the beams which are enabled along various elevation and azimuth angles. In some aspects, the information to identify each beam of the number of beams supported at the each cell comprises a bitmap. Each bit of the bitmap corresponds to a beam. A value of the each bit indicates whether the beam is supported at the each cell.

In some aspects, the configuration data identifies a subset of cells of the plurality of cells which support beams that are targeted at a location of the mobile device. In some aspects, the subset of cells supports a highest number of beams among the plurality of cells. In some aspects, the subset of cells supports narrowest beams among the plurality of cells.

In some aspects, the method further comprises: selecting, by the mobile device and based on the beam support information, a subset of cells of the plurality of cells; and transmitting, by the mobile device, a request to the subset of cells to update a schedule of PRS transmission at the subset of cells. The updating a schedule of PRS transmission at the subset of cells comprises at least one of: updating a duration of each PRS signal, updating a period between the each PRS signal, or updating a bandwidth allocated for the each PRS signal.

The present disclosure also provides a non-transitory computer-readable medium storing instructions that, when executed by a hardware processor of a mobile device, cause the mobile device to: obtain beam support information of a plurality of cells, perform measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells to support a location determination operation for the mobile device, and transmit results of the measurements of the one or more signals to at least one of a location server or to a base station to support the location determination operation.

In some aspects, the beam support information comprises at least one of: a number of beams supported at each cell of the plurality of cells, information to identify each beam of the number of beams supported at the each cell, beam width information of the each beam, or Positioning reference Signals (PRS) codebook information which encapsulates the beams which are enabled along various elevation and azimuth angles. The information to identify each beam of the number of beams supported at the each cell comprises a bitmap. Each bit of the bitmap corresponds to a beam. A value of the each bit indicates whether the beam is supported at the each cell.

In some aspects, the beam support information is obtained from configuration data provided from the location server. The beam support information can be obtained via at least one of: Radio Resource Control (RRC) Reconfiguration messages from the plurality of cells, or System Information Block Type <NUM> (SIB1) messages from the plurality of cells.

In some aspects, the non-transitory computer readable medium further comprises instructions that, when executed by the hardware processor, cause the mobile device to: select, based on the beam support information, a subset of cells of the plurality of cells; and perform the measurements of the one or more signals with the subset of cells. The subset of cells supports a highest number of beams or narrowest beams among the plurality of cells.

In some aspects, the non-transitory computer readable medium further comprises instructions that, when executed by the hardware processor, causes the mobile device to: select, and based on the beam support information, a subset of cells of the plurality of cells; and transmit a request to the subset of cells to update a schedule of PRS transmission at the subset of cells. The updating a schedule of PRS transmission at the subset of cells comprises at least one of: updating a duration of each PRS signal, updating a period between the each PRS signal, or updating a bandwidth allocated for the each PRS signal.

The present disclosure also provides an apparatus. The apparatus comprises: means for obtaining beam support information of a plurality of cells; means for performing measurements of one or more signals at the apparatus based on the beam support information of the plurality of cells to support a location determination operation for the apparatus; and means for transmitting results of the measurements of the one or more signals to at least one of a location server or to a base station to support the location determination operation.

Non-limiting and non-exhaustive aspects are described with reference to the following figures.

Like reference numbers and symbols in the various figures indicate like elements, in accordance with certain example implementations. In addition, multiple instances of an element may be indicated by following a first number for the element with a hyphen and a second number. For example, multiple instances of an element <NUM> may be indicated as <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> etc. When referring to such an element using only the first number, any instance of the element is to be understood (e.g., elements <NUM> in the previous example would refer to elements <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM>).

Some example techniques for determining the location of a user equipment (UE) are presented herein, which may be implemented at the UE (e.g., a mobile device or mobile station), a location server (LS), a base station, and/or other devices. These techniques can be utilized in a variety of applications utilizing various technologies and/or standards, including 3rd Generation Partnership Project (3GPP), Open Mobile Alliance (OMA) Long Term Evolution (LTE) Positioning Protocol (LPP) and/or LPP Extensions (LPPe), Wi-Fi®, Global Navigation Satellite System (GNSS), and the like.

A UE may comprise a mobile device such as, for example, a mobile phone, smartphone, tablet or other mobile computer, a portable gaming device, a personal media player, a personal navigation device, a wearable device, an in-vehicle device, or other electronic device. Location determination of a UE can be useful to the UE and/or other entities in a wide variety of scenarios. There are many methods already known to determine an estimated location of the UE, including methods that involve communicating measurement and/or other information between the UE and an LS.

It is expected that fifth-generation (<NUM>) standardization will include support for positioning methods. One example of positioning method that may be supported in a <NUM> network is Observed Time Difference Of Arrival (OTDOA), which is used in LTE network. With OTDOA, a UE measures time differences, referred to as Reference Signal Time Differences (RSTDs), between reference signals transmitted by one or more pairs of base stations. In LTE, the reference signals used for OTDOA may include signals that are intended only for navigation and positioning which may be referred to as Positioning Reference Signals (PRS). To perform a location measurement, a base station may be scheduled to transmit PRS signals at certain time periods using frequency resources (e.g., a pre-determined carrier frequency or a set of sub-carrier frequencies to perform the transmission). With OTDOA, a UE can measure time differences of receiving PRS signals from multiple base stations relative to a reference base station. Each time difference can correspond to a hyperbola, and the point at which these hyperbolas intersect can correspond to the UE position.

Another example of positioning method that may be supported in a <NUM> network is Enhanced Cell ID (E-CID), which is also used in LTE network. With E-CID, the location of the UE can be estimated using the knowledge of the geographical coordinates of its serving base station, and based on performing measurements on cell-specific reference signals received by the UE from the serving base station and from other base stations. Various measurements on the reference signals can be performed including, for example, Timing Advance, Angle-of-Arrival (AoA) measurement, Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), etc. Based on the measurements, a location of the UE relative to the serving base station can be determined. The relative location can be combined with the geographical coordinates of the serving base station to estimate the location of the UE.

A base station in a <NUM> network can transmit signals to support the aforementioned positioning methods using multiple directional radio beams. For example, a base station can transmit PRS signals using the directional radio beams towards different areas within a cell, and a UE can perform RSTD measurements on the PRS signals received via the directional radio beams to support OTDOA operations. Moreover, the directional radio beams can also carry other reference signals to support measurements for E-CID operations. For example, for AoA measurement, a base station can estimate the angle of an uplink transmission to a UE on a directional radio beam. The UE can also perform Timing Advance, RSRP, and RSRQ measurements based on measuring the timing and power of the reference signals carried by the directional radio beams.

There are various advantages of using directional radio beams to perform positioning operations as well as other aspects of wireless communications, such as reduced interference, more efficient use of spectrum and power, etc. However, various attributes of the radio beams, such as beam widths, can affect the accuracy of the positioning operations. For example, in a case where relatively wide radio beams are used to carry reference signals, including PRS signals, the radio beams can cover a relatively large area. As a result, a UE can obtain the same measurement result (e.g., RSTD, RSRP, RSRQ, etc.) from the signals carried by the radio beam within the area, which adds uncertainty to the location determination of the UE. To reduce uncertainty to the location determination, it is desirable for a UE to perform measurements on radio signals carried by the relatively narrow radio beams.

Moreover, in a <NUM> network, the number of radio beams transmitted by a base station may vary between different cells, and a cell that supports a higher number of radio beams typically deploys radio beams with narrower beam widths than a cell that supports a smaller number of radio beams. For example, the <NUM> specification allows support of up to four radio beams for a carrier frequency range below <NUM>, eight radio beams for a carrier frequency range between <NUM> and <NUM>, and <NUM> radio beams for a carrier frequency range exceeding <NUM>. But currently a UE cannot obtain information about the number of radio beams and/or the beam widths of the radio beams supported by a particular cell, and the UE cannot choose which cell to perform the measurements based on the number and beam widths of the radio beams supported by the cell.

Techniques described herein below can address these issues to improve positioning methods in <NUM> network. Specifically, a location server, which can coordinate a positioning operation for a UE, can obtain beam support information of a plurality of cells. The location server can configure a location determination operation for a UE based on the beam support information of the plurality of cells, the location determination operation comprising measurements of one or more signals by at least one of the mobile devices or one or more cells of the plurality of cells. The location server can then determine a location of the mobile device based on results of the measurements of the one or more signals.

The beam support information can include information that can reflect the beam widths of the radio beams supported at each cell. For example, the beam support information can indicate a number of radio beams supported by each of the cells. In some examples, the beam support information can include a bitmap to indicate which of a group of radio beams are transmitted by a base station that serves each of the cells, with each bit of the bitmap being configured to identify a radio beam within the group. The bitmap can also indicate a number of radio beams supported by each of the cells. As discussed above, a cell that supports a higher number of radio beams typically deploys radio beams with narrower beam widths than a cell that supports a smaller number of radio beams. The plurality of cells can be ranked based on the number of radio beams supported, and signal measurements with cells that support a higher number of radio beams can be prioritized based on an expectation that the beam widths of the radio beams deployed at these cells are likely to be narrower. In some examples, the beam support information can also include beam widths information, which allows signal measurements to be prioritized with cells that support radio beams with narrower beam widths.

There are various ways by which the location server can obtain the beam support information. In some examples, the location server can transmit a query to the base station of each cell to request for the beam support information. In some examples, the beam support information can be provided by the base station to the location server to initialize a location information transfer transaction, e.g., as part of OTDOA Information Transfer or E-CID Location Information transfer operations. In some examples, the location server can also receive the beam support information from a third party other than the base station (e.g., via a management/maintenance operation).

There are various ways by which the location server can configure the location determination operation. In some examples, the location server can generate configuration data (e.g., Assistance Data) based on the beam support information, and send the configuration data to the UE, to enable the UE to select a subset of the cells to perform signal measurements (e.g., PRS signal measurements for OTDOA operations). In some examples, the configuration data may include the number of radio beams supported at each cell, the beam widths of the radio beams supported at each cell, etc., and the UE can select the subset of the cells supporting the highest number of beams among the cells based on the configuration data to perform the signal measurements. In some examples, the location server can also select the subset of the cells based on the beam support information and include the subset of the cells in the configuration data. The location server can also request the subset of cells to perform signal measurements with the UE (e.g., RSRP/RSRQ measurement, Timing Advance measurements, etc., for E-CID operations), to increase the frequency and/or duration of PRS signals transmission to facilitate the signal measurement at the UE, etc..

Techniques described herein can also be implemented at the UE. For example, the UE can receive the beam support information as part of configuration data (e.g., Assistance Data) from the location server, cache the beam support information, and use the beam support information to prioritize signal measurements with cells that support higher number of radio beams and/or radio beams with narrower beam widths, as described above. In some examples, the UE can also receive the beam support information via broadcast signals from neighboring cells (e.g., SIB1 (System Information Block Type <NUM>) broadcasts). In some examples, the UE can also request the base stations of cells that support higher number of radio beams to increase the frequency and/or duration of PRS signals transmission, to improve the likelihood that the UE can perform sufficient number of PRS signals measurements for location determination within a time window.

With such arrangements, the location determination operation can be adapted based on, for example, the number of radio beams supported at the cells, the beam width of the radio beams supported at the cells, etc. Priority can be given to signal measurements with cells that support higher number of radio beams and/or narrower radio beams, which can improve the efficiency and accuracy of location determination operation.

<FIG> is a diagram of a communication system <NUM> that may utilize a <NUM> network to determine a location of a UE <NUM>, according to some embodiments. Here, the communication system <NUM> comprises a UE <NUM> and a <NUM> network comprising a Next Generation (NG) Radio Access Network (RAN) (NG-RAN ) <NUM> and a <NUM> Core Network (5GC) <NUM>, which, along with providing OTDOA-based positioning, may provide data and voice communication to the UE <NUM>. A <NUM> network may also be referred to as a New Radio (NR) network; NG-RAN <NUM> may be referred to as a <NUM> RAN or as an NR RAN; and 5GC <NUM> may be referred to as an NG Core network (NGC). Standardization of an NG-RAN and 5GC is ongoing in 3GPP. Accordingly, NG-RAN <NUM> and 5GC <NUM> may conform to current or future standards for <NUM> support from 3GPP. The communication system <NUM> may further utilize information from GNSS satellite vehicles (SVs) <NUM>. Additional components of the communication system <NUM> are described below. It will be understood that a communication 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 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 communication system <NUM>. Similarly, the communication system <NUM> may include a larger (or smaller) number of SVs <NUM>, gNBs <NUM>, ng-eNBs <NUM>, AMFs <NUM>, external clients <NUM>, and/or other components. The illustrated connections that connect the various components in the communication 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.

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, as noted above, UE <NUM> may correspond to any of a variety of devices, including a cellphone, smartphone, laptop, tablet, PDA, tracking device, 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 Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Long Term Evolution (LTE), High Rate Packet Data (HRPD), IEEE <NUM> WiFi (also referred to as Wi-Fi), Bluetooth® (BT), Worldwide Interoperability for Microwave Access (WiMAX), <NUM> new radio (NR) (e.g., using the NG-RAN <NUM> and 5GC <NUM>), etc. The UE <NUM> may also support wireless communication using a Wireless Local Area Network (WLAN) which may connect to other networks (e.g., the Internet) using a Digital Subscriber Line (DSL) or packet cable for example. The use of one or more of these RATs may enable the UE <NUM> to communicate with an external client <NUM> (e.g., via elements of 5GC <NUM> not shown in <FIG> or possibly via Gateway Mobile Location Center (GMLC) <NUM>) and/or enable the external client <NUM> to receive location information regarding the UE <NUM> (e.g., via GMLC <NUM>).

The UE <NUM> may comprise a single entity or may comprise 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, location estimate or location fix, and may be geographic, 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 geographically 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 geographically, 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.

Base stations in the NG-RAN <NUM> may comprise NR Node Bs which are more typically referred to as gNBs. In <FIG>, three gNBs are shown - gNBs <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM>, which are collectively and generically referred to herein as gNBs <NUM>. However, a typical NG RAN <NUM> could comprise dozens, hundreds or even thousands of gNBs <NUM>. Pairs of gNBs <NUM> in NG-RAN <NUM> may be connected to one another (not shown in <FIG>). 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 5GC <NUM> on behalf of the UE <NUM> using <NUM> (also referred as NR). In <FIG>, the serving gNB for UE <NUM> is assumed to be gNB <NUM>-<NUM>, although other gNBs (e.g., gNB <NUM>-<NUM> and/or 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 throughout and bandwidth to UE <NUM>.

Base stations (BSs) 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> (not shown in <FIG>) - 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., a set of pre-determined location measurement signals) and/or may broadcast assistance data to assist positioning of UE <NUM> but may not receive signals from UE <NUM> or from other UEs. It is noted that while only one ng-eNB <NUM> is shown in <FIG>, the description below sometimes assumes the presence of multiple ng-eNBs <NUM>.

As noted, while <FIG> depicts nodes configured to communicate according to <NUM> communication protocols, nodes configured to communicate according to other communication protocols, such as, for example, an LPP protocol or IEEE <NUM>. 11x protocol, may be used. For example, in an Evolved Packet System (EPS) providing LTE wireless access to UE <NUM>, a RAN may comprise an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) which may comprise base stations comprising evolved Node Bs (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 EPC, where the E-UTRAN corresponds to NG-RAN <NUM> and the EPC corresponds to 5GC <NUM> in <FIG>. The methods and techniques described herein for support of UE <NUM> positioning may be applicable to such other networks.

The gNBs <NUM> and ng-eNB <NUM> can communicate with an Access and Mobility Management Function (AMF) <NUM>, which, for positioning functionality, communicates with a Location Management Function (LMF) <NUM>. The AMF <NUM> may support mobility of the UE <NUM>, including cell change and handover and may 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> when UE <NUM> accesses the NG-RAN <NUM> and may support location methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), angle of arrival (AoA), angle of departure (AoD), and/or other location methods. The LMF <NUM> may also process location services requests for the UE <NUM>, e.g., received from the AMF <NUM> or from the GMLC <NUM>. The LMF <NUM> may be connected to AMF <NUM> and/or to GMLC <NUM>. The LMF <NUM> may be referred to by other names such as a Location Server (LS), Location Manager (LM), Location Management Function (LMF), Location Function (LF), commercial LMF (CLMF), value added LMF (VLMF), etc. A description of some of the protocols supported at LMF <NUM> can be found at, for example, https://www. org/deliver/etsi_ts/138400_138499/<NUM>/ <NUM>. 00_60/ts_138455v150000p. In some embodiments, a node / system that implements the LMF <NUM> may additionally or alternatively implement other types of location-support modules, such as an Enhanced Serving Mobile Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). It is noted that in some embodiments, at least part of the positioning functionality (including derivation of a UE <NUM>'s location) may be performed at the UE <NUM> (e.g., using signal measurements obtained by UE <NUM> for signals transmitted by wireless nodes such as gNBs <NUM> and ng-eNB <NUM>, and 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> or may forward the location request directly 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>. The GMLC <NUM> is shown connected to both the AMF <NUM> and LMF <NUM> in <FIG> though only one of these connections may be supported by 5GC <NUM> in some implementations.

As further illustrated in <FIG>, the LMF <NUM> may communicate with the gNBs <NUM> and/or with the ng-eNB <NUM> using a New Radio Location Protocol A (which may be referred to as NPPa or NRPPa), which may be defined in 3GPP Technical Specification (TS) <NUM>. NRPPa may be the same as, similar to, or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS <NUM>, with NRPPa messages being 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), which may be defined in 3GPP TS <NUM>. LMF <NUM> and UE <NUM> may also or instead communicate using a New Radio Positioning Protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of LPP. Here, LPP and/or NPP 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 and/or NPP messages may be transferred between the LMF <NUM> and the AMF <NUM> using a <NUM> Location Services Application Protocol (LCS AP) and may be transferred between the AMF <NUM> and the UE <NUM> using a <NUM> Non-Access Stratum (NAS) protocol. The LPP and/or NPP protocol may be used to support positioning of UE <NUM> using UE assisted and/or UE based location methods such as A-GNSS, RTK, OTDOA and/or E-CID. The NRPPa protocol may be used to support positioning of UE <NUM> using network based location methods such as E-CID (e.g., when used with measurements obtained by a gNB <NUM> or ng-eNB <NUM>) and/or may be used by LMF <NUM> to obtain location related information from gNBs <NUM> and/or ng-eNBs <NUM>, such as parameters defining PRS transmission from gNBs <NUM> and/or ng-eNB <NUM>.

With a UE assisted location 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 example, the location measurements may include techniques based on antenna beam angle of direction (AoD) to be described below. The location measurements may also include one or more of a Received Signal Strength Indication (RSSI), Round Trip signal propagation Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ) for gNBs <NUM>, ng-eNB <NUM> and/or a WLAN access point (AP). The location measurements may also or instead include measurements of GNSS pseudorange, code phase and/or carrier phase for SVs <NUM>. With a UE based location method, UE <NUM> may obtain location measurements (e.g., which may be the same as or similar to location measurements for a UE assisted location method) and may compute a location of UE <NUM> (e.g., with the help of assistance data received from a location server such as LMF <NUM> or broadcast by gNBs <NUM>, ng-eNB <NUM> or other base stations or APs). With a network based location method, one or more base stations (e.g., gNBs <NUM> and/or ng-eNB <NUM>) or APs may obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, Timing Advance, etc.) for signals transmitted by UE <NUM>, and/or may receive measurements obtained by UE <NUM>, and may send the measurements to a location server (e.g., LMF <NUM>) for computation of a location estimate for UE <NUM>.

Information provided by a gNB <NUM> and/or ng-eNB <NUM> to the LMF <NUM> using NRPPa may include timing and configuration information for transmission of location measurement signals from the gNB <NUM> and/or location coordinates for the gNB <NUM>. The LMF <NUM> can then provide some or all of this information to the UE <NUM> as assistance data in an LPP and/or NPP message via the NG-RAN <NUM> and the 5GC <NUM>.

An LPP or NPP message sent from the LMF <NUM> to the UE <NUM> may instruct the UE <NUM> to do any of a variety of things, depending on desired functionality. For example, the LPP or NPP message could contain an instruction for the UE <NUM> to obtain measurements for GNSS (or A-GNSS), WLAN, OTDOA, E-CID, etc. The UE <NUM> may send the measurements back to the LMF <NUM> in an LPP or NPP message (e.g., inside a <NUM> NAS message) via the serving gNB <NUM>-<NUM> (or serving ng-eNB <NUM>) and the AMF <NUM>.

As noted, while the communication system <NUM> is described in relation to <NUM> technology, the communication system <NUM> may be implemented to support other communication technologies, such as GSM, WCDMA, LTE, etc., that are used for supporting and interacting with mobile devices such as the UE <NUM> (e.g., to implement voice, data, positioning, and other functionalities). In some such embodiments, the 5GC <NUM> may be configured to control different air interfaces. For example, in some embodiments, 5GC <NUM> may be connected to a WLAN using a Non-3GPP InterWorking Function (N3IWF, not shown <FIG>) in the 5GC <NUM>. For example, the WLAN may support IEEE <NUM> WiFi access for UE <NUM> and may comprise one or more WiFi APs.

Here, the N3IWF may connect to the WLAN and to other elements in the 5GC <NUM> such as AMF <NUM>. In some other embodiments, both the NG-RAN <NUM> and the 5GC <NUM> may be replaced by other RANs and other core networks. For example, in an EPS, the NG-RAN <NUM> may be replaced by an E-UTRAN containing eNBs and the 5GC <NUM> may be replaced by an EPC containing a Mobility Management Entity (MME) in place of the AMF <NUM>, an E-SMLC in place of the LMF <NUM> and a GMLC that may be similar to the GMLC <NUM>. In such an EPS, the E-SMLC may use LPPa in place of NRPPa to send and receive location information to and from the eNBs in the E-UTRAN and may use LPP to support positioning of UE <NUM>. In these other embodiments, positioning of a UE <NUM> may be supported in an analogous manner to that described herein for a <NUM> network with the difference that functions and procedures described herein for gNBs <NUM>, ng-eNB <NUM>, AMF <NUM> and LMF <NUM> may, in some cases, apply instead to other network elements such eNBs, WiFi APs, an MME and an E-SMLC.

<FIG> is an example of a radio beam (hereinafter, "beam") <NUM> that can be used for location measurement. Beam <NUM> may generated by an antenna <NUM> which can be part of, for example, gNB <NUM>. Beam <NUM> may be generated based on an antenna pattern which defines a pattern of radiation of energy as a function of space. The pattern of radiation can be defined based on one or more beam widths (e.g., beam width <NUM>) along different dimensions and a corresponding beam center (e.g., beam center <NUM>) along a propagation path (e.g., propagation path <NUM>) of the beam. Propagation path <NUM> can be associated with an angle of departure (AoD) from antenna <NUM> and with respect to a reference plane and/or axis. In the example of <FIG>, propagation path <NUM> may be associated with an AoD <NUM> with respect to an X-axis which is parallel with the horizon. The beam width may define a distance (from a corresponding beam center) where the power level of the beam drops by a pre-determined percentage (e.g., <NUM>% or 3dB) compared with the power level at the corresponding beam center. In some examples, antenna <NUM> may include a number of antenna elements each of which can transmit radio signals, and antenna <NUM> can set an angle of departure of a beam by setting phase differences of transmissions by each antenna elements. The phase differences can lead to constructive (or destructive) interferences among the transmitted radio signals, to form a beam along a pre-determined propagation path based on the preset angle of departure.

Although <FIG> illustrates beam <NUM> as a two-dimensional beam, it is understood that beam <NUM> can be a three-dimensional beam, and the antenna pattern that defines beam <NUM> can be a three-dimensional antenna pattern. <FIG> illustrates an example of beam <NUM> as a three-dimensional beam. In the example of <FIG>, beam <NUM> may be defined by a combination of two two-dimensional antenna patterns. A first two-dimensional antenna pattern, and a first beam width <NUM>, can be defined on an elevation plane <NUM>. Elevation plane <NUM> can be defined by the X-axis and a Z-axis and is perpendicular to the horizon. A second two-dimensional antenna pattern, and a second beam width <NUM>, can be defined on an azimuth plane <NUM>. Azimuth plane <NUM> can be defined by the Y-axis and the Z-axis and can be perpendicular to elevation plane <NUM>. Beam <NUM> can also be associated with a first angle of departure (denoted as θ) on elevation plane <NUM> and with reference to, for example, the Y-axis (or the Z-axis). Beam <NUM> can also be associated with a second angle of departure (denoted as ϕ) on azimuth plane <NUM> and with reference to, for example, the Y-axis (or the X-axis).

In a <NUM> network, antenna <NUM> may be configured to transmit a number of beams, with each beam having a different angle of departure (e.g., different angles on the elevation plane and/or on the azimuth plane) and targeted at a pre-determined geographical region. <FIG> illustrates an example of a beam transmission scheme by antenna <NUM> in a <NUM> network. In the example of <FIG>, antenna <NUM> may transmit beams 230a, 230b, 230c, 230d, 230e, 230f, <NUM>, and <NUM> to, respectively, one of regions 240a, 240b, 240c, 240d, 240e, 240f, <NUM>, and <NUM>. To avoid interference between the beams, the beam width of each beam can be adapted based on the total number of beams transmitted. For example, the beam width of beams 230a-<NUM> is typically smaller than a case where antenna <NUM> only transmits beams 230a-230d to the cell area covering regions 240a-<NUM>. The beam width of beams 230a-<NUM> can be further reduced if additional beams are also transmitted by antenna <NUM> to the cell area covering regions 240a-<NUM>. With such arrangements, a mobile device located in one of the regions 240a-<NUM> may receive only one of beams 230a-<NUM> as a direct line-of-sight beam. For example, mobile device <NUM>, located in region 240a may receive radio beam 230a as a direct line-of-sight beam (versus as a reflected or deflected beam) from antenna <NUM>. However, mobile device <NUM> is unlikely to receive radio beam 230b as a direct line-of-sight beam. Moreover, mobile device <NUM>, located in region 240d and also camping in the cell, may receive radio beam 230d as a direct line-of-sight beam from antenna <NUM>.

Each of beams 230a-<NUM> may carry various information. For example, each of beams 230a-<NUM> may carry data representing a beam identifier associated with the respective beam. Moreover, the beams may carry signals used for radio frame synchronization and beam tracking, such as Primary Synchronization Sequences (PSS), Secondary Synchronization Sequences (SSS), Physical Broadcast Channel (PBCH) signals, Tracking Reference Signals (TRS), etc. Each beam may also be used to carry reference signals for location determination, such as PRS signals for OTDOA operations, other reference signals to support Timing Advance, RSRP, and RSRQ measurements for E-CID operations, etc. Each beam can include a sequence of radio frames to transmit PSS, SSS, PBCH, TRS signals. Each radio frame may be associated with a period of transmission, and can be organized into a number of subframes. Each subframe may be further divided into a number of symbol periods, with each symbol period being used for transmission of a symbol. Each symbol can be transmitted by modulating a set of subcarriers allocated as resource elements, with each subcarrier occupying a different frequency band. Each of PSS, SSS, PBCH, and TRS signals can include a sequence of symbols formed by modulating a set of subcarriers in a set of symbol periods.

As described above, the directional radio beams transmitted by base stations can be used to support various positioning operations, such as OTDOA and E-CID. <FIG> illustrates an example of an OTDOA operation. As shown in <FIG>, a UE <NUM> (represented by a star in <FIG>) can receive beam <NUM> carrying a reference signal from gNB <NUM>, a beam <NUM> carrying a reference signal from gNB <NUM>, and a beam <NUM> carrying a reference signal from gNB <NUM>. The reference signals carried by the beams can include position measurement signals, such as PRS signals. UE <NUM> can measure three time-of-arrivals (TOA) τ<NUM>, τ<NUM>, and τ<NUM> of the reference signals received from, respectively, beams <NUM>, <NUM>, and <NUM> to perform RSTD measurement. To perform RSTD measurement, one of the TOA (e.g., τ<NUM>) can be selected as a reference, and two time differences t<NUM>,<NUM> (which represents τ<NUM> - τ<NUM>) and t<NUM>,<NUM> (which represents τ<NUM> - τ<NUM>) can be determined. Each time difference can represent a hyperbola, and the point at which the two hyperbolas (e.g., of t<NUM>,<NUM> and t<NUM>,<NUM>) intersects can represent an estimated location of UE <NUM>.

Each time difference measurement can have certain uncertainty, which is represented by the dotted lines in <FIG>. One potential source of uncertainty can come from the finite beam width. For example, due to finite beam width of beam <NUM>, UE <NUM> can detect the same TOA τ<NUM> at locations <NUM> and <NUM>, which contribute to the uncertainty in the estimation of location of UE <NUM>. By reducing the beam width of beam <NUM>, the distance between locations <NUM> and <NUM> can shrink, and the uncertainty of location estimation of UE <NUM> can be reduced. As to be described in more details below, PRS measurements can be prioritized for cells that support radio beams with narrower beam widths to improve the accuracy of location determination operations.

<FIG> is an example of the structure of a LTE subframe sequence of position measurement signals (e.g., PRS). A similar subframe sequence structure can also be used in the system of <FIG> and can be transmitted using the radio beams of <FIG> and of <FIG>. In <FIG>, time is represented horizontally (e.g., on an X axis) with time increasing from left to right, while frequency is represented vertically (e.g., on a Y axis) with frequency increasing (or decreasing) from bottom to top, as illustrated. As shown in <FIG>, downlink and uplink LTE Radio Frames <NUM> can be <NUM> duration each. For downlink Frequency Division Duplex (FDD) mode, Radio Frames <NUM> are organized into ten subframes <NUM> of <NUM> duration each. Each subframe <NUM> comprises two slots <NUM>, each of <NUM> duration. Each slot of slots <NUM> may include seven symbol periods (in the case of normal cyclic prefix (NCP) as shown in <FIG>) or six symbol periods (in the case of extended cyclic prefix (ECP)), with each symbol period for transmission of a symbol. Up to <NUM> symbols (in the case of ECP) or <NUM> symbols (in the case of NCP) can be transmitted within subframe <NUM>. It is understood that in a <NUM> network, the number of symbols in one slot can include a different number (other than six or seven) of symbol periods, and a pre-determined pattern of the symbols transmitted in the symbol periods can represent a position measurement signal in the <NUM> network.

In the frequency domain, the available bandwidth may be divided into uniformly spaced orthogonal subcarriers <NUM>. For example, for a normal length cyclic prefix using <NUM> spacing, subcarriers <NUM> may be grouped into a group of <NUM> subcarriers. Each grouping, which comprises <NUM> subcarriers <NUM>, in <FIG>, is termed a resource block and, in the example above, the number of subcarriers in the resource block may be written as <MAT>. For a given channel bandwidth, the number of available resource blocks on each channel <NUM>, which is also called the transmission bandwidth configuration, is indicated as <MAT> <NUM>. For example, for a <NUM> channel bandwidth in the above example, the number of available resource blocks on each channel <NUM> is given by <MAT>. It is understood that in a <NUM> network, a resource block can include a different number (other than <NUM> or <NUM>) of subcarriers, and the subcarriers can occur a different channel bandwidth than, for example, the <NUM> channel bandwidth discussed above.

A position reference signal (PRS), which has been defined in 3GPP LTE Release-<NUM> and later releases, may be transmitted by an eNB after appropriate configuration (e.g., by an Operations and Maintenance (O&M) server). A PRS may be transmitted in downlink transmissions as a broadcast signal directed to all UEs within a radio range from the eNB, and the PRS can be used by the UEs as a position measurement signal for position determination. A PRS can be transmitted in special positioning subframes that are grouped into positioning occasions. For example, in LTE, a PRS positioning occasion can comprise positioning subframes <NUM>, which can include 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). The time of arrival (TOA) can be determined based on, for example, when the UE receives the start of a PRS subframe.

The PRS positioning occasions may occur periodically at intervals <NUM>, denoted by a number TPRS, of millisecond (or subframe) intervals where TPRS may equal <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>. As an example, <FIG> illustrates a periodicity of positioning occasions where NPRS equals <NUM> and TPRS is greater than or equal to <NUM>. In some embodiments, TPRS may be measured in terms of the number of subframes between the start of consecutive positioning occasions. UE can receive PRS scheduling information from a location server as part of Assistance Data, which indicates the times when the PRS positioning occasions are scheduled to occur, and the durations of the PRS positioning occasions. The UE can perform TOA measurement on one or more positioning occasions at the scheduled times.

In <NUM> network, the duration of a PRS positioning occasion (represented by NPRS) and the period between each PRS positioning occasion (represented by TPRS) can be adjusted dynamically (e.g., based on a request of a location server, a UE, etc.) to implement an "On Demand PRS" scheme. Transmitting PRS through static scheduling (e.g., having a fixed TPRS and NPRS) can lead to inefficient usage of resource blocks. For example, PRS might be used for positioning during emergency calls, asset tracking and other applications which might not need PRS for a significant portion of time. For those applications, it is advantageous to dynamically alter the PRS scheduling. For example, for applications that do not need PRS for a significant portion of time (e.g., emergency calls), the duration of a PRS positioning occasion can be reduced, the period between PRS positioning occasions can be increased, etc., to free up the resource blocks for other applications. Moreover, as to be described in more details below, base stations that transmitted radio beams of narrower beam widths can be controlled to increase the duration of PRS positioning occasions, reduce the period between PRS positioning occasions, allocate more bandwidth (e.g., by allocating more resource blocks) for the PRS symbol transmission, etc. Such arrangements can improve the likelihood that the UE can perform a sufficient number of PRS signal measurements with base stations that support more accurate measurements (by supporting narrower radio beams), which can improve the efficiency and accuracy of the location determination operation.

<FIG> illustrates an example of E-CID operation, which can also be supported by directional radio beams transmitted by a base station. As shown in <FIG>, UE <NUM> is in a cell <NUM> served by a base station <NUM>. As part of E-CID operation, signal measurements can be made by base station <NUM> and/or by UE <NUM> to determine a distance d between UE <NUM> and base station <NUM>, and an angle of arrival (AoA) of the radio beam at UE <NUM> on a horizontal plane.

There are different ways by which the distance d can be measured, such as by measuring the power of a signal received at the UE from the base station, to determine a degree of attenuation (e.g., due to path loss, signal fading, etc.) of the signal power. The degree of attenuation can be used to determine the distance d. Alternatively, a propagation delay between the UE and the base station can also be measured, and the propagation delay can also be used to determine the distance d. For example, UE <NUM> can measure Reference Signal Received Power (RSRP), which is the average power of a resource element that carries a cell specific Reference Signal (RS) received at the UE. Another measurement that UE <NUM> can perform is Reference Signal Received Quality (RSRQ), which can be based on a ratio between RSRP and average total received power (e.g., based on Received Signal Strength Indicator (RSSI)). UE <NUM> can perform the RSRP and/or RSRQ measurements and report the measurements results back to a base station <NUM>. As another example, to measure propagation delay, base station <NUM> can measure a time difference in the transmission and reception of a subframe as part of Timing Advance measurement. Base station <NUM> may transmit a signal to UE <NUM> which includes a time of transmission of the signal. UE <NUM>, upon receiving the signal from base station <NUM>, can also determine a time of reception of the signal, and report the time of reception back to base station <NUM>. Base station <NUM> can determine the time difference between the time of transmission of the signal and the time of reception of the signal. The time difference can represent the Timing Advance measurement. Base station <NUM> can transmit the timing Advance measurement in a Timing Advance (TA) command to UE <NUM> to synchronize uplink timing with downlink transmission from base station <NUM>.

In addition, base station <NUM> can also measure AoA with based on the angle of departure (AoD) of a directional radio beam transmitted to UE <NUM>. For example, base station <NUM> determines that a radio beam of certain AoD is transmitted to UE <NUM> as part of uplink transmission, and receives a report back from UE <NUM> that the UE has received the radio beam, base station <NUM> can determine the AoA of the radio beam at the UE as identical to the AoD of the same radio beam at base station <NUM>.

In some examples, base station <NUM> can transmit the RSRP, RSRQ, and Timing Advance measurements, as well as the AoA measurement results, to a location server in an E-CID Measurement Initiation Response which can be part of LPPa and/or NRPPa procedure. In some examples, UE <NUM> can also report some the measurements results (e.g., RSRP, RSRQ, and receive-transmit time difference) directly to the location server in an E-CID-SignalMeasurementInformation message which can be part of LPP and/or NRPP procedure. The location server can then estimate a location of UE <NUM> based on a relative location of UE <NUM> with respect to base station <NUM> (e.g., based on AoA and distance estimated from RSRP, RSRQ, and/or Timing Advance measurements), as well as the known location of base station <NUM>.

Similar to OTDOA operation, the accuracy of E-CID operation can also be affected by the beam width of the radio beams used for the measurement. For example, as shown in <FIG>, instead of receiving the central part <NUM> of the radio beam, UE <NUM> receives the edge part <NUM> of the radio beam. Due to the finite beam width, the actual angle of arrival is AoA' is different from AoA as well as AoD. Using AoD to estimate the direction of UE <NUM> with respect to base station <NUM> can lead to error. Moreover, due to the finite beam width, UE <NUM> may also obtain similar RSRP, RSRQ, and/or Timing Advance measurement results at different locations with the cell. By reducing the beam width, the uncertainties in the location determination using E-CID operations can be reduced. As to be described in more details below, E-CID operation can also be prioritized for cells that support radio beams with narrower beam widths to improve the accuracy of location determination operations.

In addition to beam width and/or number of radio beams information, it can also be advantageous for a UE to have other information about the radio beams transmitted by a base station, such as the direction, the target area, etc. Such information can be useful for the UE to determine whether it is likely to receive a radio beam from the base station. If the UE determines that it is unlikely to receive a radio beam from the base station, the UE can skip the signal measurement operations (for OTDOA, for E-CID, etc.) with that base station and perform the signal measurement operations with other base stations instead. With such arrangements, the efficiency of location determination operation can be improved.

<FIG> illustrates an example of UE skipping signal measurement operations with a base station based on the information of the radio beams transmitted by the base station. As shown in <FIG>, base station <NUM> transmits four radio beams 502a, 502b, 502c, and 502d at AoDs of, respectively, <NUM>°, <NUM>°, <NUM>°, and <NUM>° (e.g., in a counter-clockwise direction with respect to axis <NUM>). UE <NUM> may store information <NUM> that maps the beam IDs of radio beams transmitted by base station <NUM> (502a, 502b, 502c, and 502d) to the AoDs <NUM>°, <NUM>°, <NUM>°, and <NUM>°. Information <NUM> also includes the location of base station <NUM>. UE <NUM> may obtain a coarse measurement of its own location (e.g., based on GPS, WiFi, etc.). Based on the coarse measurement, as well as the location of base station <NUM> and the AoDs of the radio beams from information <NUM>, UE <NUM> can determine whether it is likely to receive any of radio beams 502a, 502b, 502c, or 502d. In the example of <FIG>, based on the coarse measurement of its location, UE <NUM> may determine that it is unlikely to receive any of radio beams 502a, 502b, 502c, or 502d, and skip the signal measurement operations with base station <NUM>.

<FIG> is a diagram of communication system <NUM> may utilize radio beam support according to some embodiments. information to support location determination operation in a <NUM> network, according to some embodiments. As shown in <FIG>, a location server <NUM> (e.g., which can include or be part of LMF <NUM> of <FIG>) can obtain beam support information <NUM> from gNBs <NUM> and/or from maintenance operations <NUM> (e.g., programming operations). As to be discussed in more details below, location server <NUM> can configure a location determination operation for a UE <NUM> based on beam support information <NUM>. For example, location server <NUM> can select, based on beam support information <NUM>, a subset of gNBs <NUM> to perform the location determination operation with UE <NUM>. As another example, location server <NUM> can also transmit beam support information <NUM> (and/or derived information) to UE <NUM> as part of Assistance Data <NUM> to enable or control UE <NUM> to perform the location determination operation with the subset of gNBs <NUM>. In some examples, UE <NUM> can also receive beam support information <NUM> directly from gNBs <NUM>.

Beam support information <NUM> can come in various forms. In some examples, beam support information <NUM> for a cell can include a number that indicates a number of radio beams supported in that cell, which enables location server <NUM> and/or UE <NUM> to determine, for example, the relative beam width of radio beams at different cells. In some examples, beam support information <NUM> can include information to identify each radio beam supported at the cell. For example, beam support information <NUM> can include a bitmap, with each bit corresponding to a particular radio beam, and the value of each bit can indicate whether the radio beam is supported in that cell. In some examples, beam support information <NUM> can include beam width information (e.g., a first beam width measured in the elevation plane and a second beam width measured in the azimuth plane), which can directly provide the beam width information of each cell to location server <NUM> and/or UE <NUM>.

There are different ways by which location server <NUM> can obtain beam support information <NUM> from gNBs <NUM>. In some examples, location server <NUM> can transmit a query to gNBs <NUM> using NRPPa procedures to request beam support information <NUM>. In some examples, as part of E-CID Location Information Transfer under the NRPPa procedures, location server <NUM> can transmit a message for an E-CID measurement initiation request to each of gNBs <NUM> to initiate E-CID operations with the gNBs, and the message may include an information element (IE) for beam support information. An excerpt of an example E-CID measurement initiation request message <NUM> is shown in <FIG>. As shown in <FIG>, E-CID measurement initiation request message <NUM> includes an IE <NUM> labelled "Actual Beam Support. " IE <NUM> can be a <NUM>-bit number that ranges between <NUM>-<NUM> and can indicate a number of radio beams supported by a cell, with the range being set based on, for example, the <NUM> specification. In addition, E-CID measurement initiation request message <NUM> also includes an IE <NUM> labelled "Measurement Quantities Item. " IEE <NUM> can include a set of measurements which location server <NUM> has selected and to be performed by the recipient gNB. The measurements may include, for example, reporting of a cell identifier of the cell, a set of identifiers of the radio beams supported by the cell, Angle of Arrival (AoA), Timing Advance, RSRP, RSRQ, etc. for each beam identified by the set of identifiers. As part of the E-CID Location Information Transfer, gNB may receive E-CID measurement initiation request message <NUM>, parse the message to identify the IE requested by location server <NUM>, and provide the data for the requested IE (e.g., the number of radio beams supported by the cell, and the results of the requested measurements) in an E-CID measurement initiation response message back to location server <NUM>.

In some examples, as part of OTDOA Information Transfer under the NRPPa procedures, location server <NUM> can transmit a message for an OTDOA information request to each of gNBs <NUM> to initiate OTDOA operations with the gNBs, and the message may also include an information element (IE) for beam support information. An excerpt of an example OTDOA information request message <NUM> is shown in <FIG>. As shown in <FIG>, OTDOA information request message <NUM> includes an IE <NUM> labelled "Actual Beam Support. " IE <NUM> can be a <NUM>-bit number that ranges between <NUM>-<NUM> and can indicate a number of radio beams supported by a cell, with the range being set based on, for example, the <NUM> specification. As part of the OTDOA Information Transfer, gNB may receive OTDOA information request message <NUM>, parse the message to identify IE <NUM>, and provide the number of radio beams information to location server <NUM> in an OTDOA information response message.

In addition, as described above, UE <NUM> can also receive beam support information <NUM> directly from gNBs <NUM> in various ways. In some examples, UE <NUM> may receive beam support information <NUM> while establishing or reconfiguring a Radio Resource Control (RRC) connection with one of gNBs <NUM>. In some examples, UE <NUM> may also receive broadcast messages (e.g., System Information Block Type <NUM> (SIB1) messages) from gNBs <NUM>. <FIG> illustrates an excerpt of an example SIB1/RRC Reconfig message <NUM>. As shown in <FIG>, SIB <NUM>/RRC Reconfig message <NUM> includes an IE <NUM> labelled "PositionInBurstLongBitmap. " IE <NUM> can be in the form of a <NUM>-bit bitmap, with each bit representing/identifying a radio beam. A bit value of "<NUM>" can indicate that the radio beam represented by the bit is transmitted in the cell, whereas a bit value of "<NUM>" can indicate that the radio beam represented by it is not transmitted in the cell. The bitmap information can be combined with additional information including, for example, the angle of arrival (AoA) of each beam represented in the bitmap, a coarse estimate of the present location of the UE, known location of the base station that serve the cell, etc., to determine whether a UE is likely to receive some or all of the radio beams transmitted in the cell, as described above. In the example of <FIG>, the cell transmits all <NUM> radio beams allowed under the <NUM> specification. In some examples, the "PositionInBurstLongBitmap" bitmap can be included in E-CID measurement initiation request/response message and in OTDOA information request/response message in lieu of or in addition to the <NUM>-bit "Actual Beam Support" number.

In some examples (not shown in <FIG>), E-CID measurement initiation request/response messages, OTDOA information request/response messages, SIB1/RRC Reconfig messages, or other messages sent by gNBs <NUM> to the location server may also include other forms of beam support information <NUM>. For example, beam support information <NUM> may include beam width information. For example, these messages can include a first beam width (measured in the elevation plane) and a second beam width (measured in the azimuth plane) of each of the beams supported in a cell. In some examples, gNBs <NUM> may also transmit PRS codebook information (which can be part of beam support information <NUM>) which encapsulates specifically the beams which are enabled along specific elevation and azimuth angles.

After receiving beam support information <NUM> from each of gNBs <NUM>, location server <NUM> and/or UE <NUM> can store a data structure (e.g., a mapping table) that maps each cell served by gNBs <NUM> to the corresponding beam support information <NUM>. In some examples, the cells in the data structure can be ranked based on, for example, the number of beams supported in each cell, the beam width of the beams in each cell, the number of beams a UE is likely to receive, etc. For example, the top ranked cells can have the highest number of beams and/or narrowest beam width among the cells in the data structure. Location server <NUM> and/or UE <NUM> can configure a location determination operation (e.g., OTDOA operation, E-CID operation, etc.) based on a result of the ranking.

<FIG> illustrate examples of location determination operations adapted based on support information <NUM>. In <FIG>, location server <NUM> can transmit Assistance Data <NUM> to UE <NUM>. Assuming that UE <NUM> has a limited time allocated for performing OTDOA operations and can perform measurements with no more than three base stations within the allocated time, location server <NUM> can rank the beam support information and select the top three cells (e.g., served by gNBs 608a, 608b, and 608c) having the highest number of beams (or narrowest beam width) among gNB <NUM>, and include the three cells in Assistance Data <NUM>, which enables UE <NUM> to only perform RSTD measurements with gNBs 608a, 608b, and 608c, and not to perform RSTD measurements with other gNBs <NUM> (e.g., gNBs 608d and 608e), for better localization and to reduce position uncertainty as explained above. In some examples, location server <NUM> may also determine an approximate location of UE <NUM> with respect to the base stations of the cells. Based on the beam support information which indicate the beams supported at each cell, and based on the approximate location of UE <NUM> with respect to the base stations of these cells, location server <NUM> can select a set of cells for which beams are enabled at the approximate direction/location of UE <NUM>, such that UE <NUM> only performs signals measurements with these cells. In some examples, UE <NUM> can also include beam support information <NUM> of all of the cells served by gNBs <NUM> in Assistance Data <NUM>, and UE <NUM> can perform the ranking and select the top three cells to perform the RSTD measurements. After performing the RSTD measurements, UE <NUM> can include the RSTD measurement results in an OTDOA-SignalMeasurementInformation message <NUM> back to location server <NUM>, which can then determine a location of UE <NUM> based on the RSTD measurement results.

<FIG> illustrates another example of location determination operations adapted based on support information <NUM>. As shown in <FIG>, location server <NUM> can select a subset of gNBs <NUM> based on the ranking, and request the subset of gNBs <NUM> to perform E-CID operations with UE <NUM>. For example, based on the ranking, location server <NUM> can transmit E-CID measurement initiation request messages <NUM> to gNBs 608a, 608b, and 608c, with each message including the item to be measured (e.g., Angle of Arrival (AoA), Timing Advance, RSRP, RSRQ, etc.). Location server <NUM> also does not transmit E-CID measurement initiation request messages <NUM> to other gNBs <NUM> (e.g., gNBs 608d and 608e). Subsequently, gNBs 608a, 608b, and 608c can perform the requested measurements with UE <NUM>, receive measurement reports <NUM> from UE <NUM>, and include the measurement results in E-CID measurement initiation response messages <NUM> back to location server <NUM>, which can then determine a location of UE <NUM> based on the E-CID measurement results.

<FIG> illustrates another example of location determination operations adapted based on support information <NUM>. As shown in <FIG>, at least one of location server <NUM> or UE <NUM> can select a cell (e.g., served by gNB 608a) that supports a relatively high number of radio beams (or supports radio beams of relatively narrow beam width) and, as part of "On Demand PRS" operation, request the selected cell to update scheduling of PRS transmission. The updating can be targeted at maximizing the quality of RSTD measurements performed by UE <NUM> within an allocated time for the measurements, to improve the efficiency and accuracy of the OTDOA operation. The updating to the scheduling of PRS transmission can include, for example, increasing the duration of PRS positioning occasions, reducing the period between PRS positioning occasions, allocating more bandwidth (e.g., by allocating more resource blocks) for the PRS symbol transmission, etc. Location server <NUM> can configure the PRS scheduling at gNB 608a via PRS scheduling configuration <NUM>, whereas UE <NUM> can transmit a PRS scheduling update request <NUM> to gNB 608a, to update the PRS scheduling.

In some examples, UE <NUM> can cache the beam support information of the cells (e.g., serving cells, neighboring cells, etc.) it has measured in the past and can adapt the location determination operations without further assistance from, for example, location server <NUM>. For example, UE <NUM> may have received the beam support information from location server <NUM> and/or SIB <NUM> broadcast from gNBs <NUM> in the past and cache the beam support information. UE <NUM> can adapt the location determination operations (e.g., E-CID operations, OTDOA operations, etc.) based on the cached beam support information. For example, as shown in <FIG>, based on the cached beam support information, UE <NUM> can rank the top three cells that support the highest number of radio beams, narrowest radio beams, etc., and select gNBs 608a, 608b, and 608c to perform RSTD and/or ECID measurements, while skipping the measurements with gNBs 608d and 608e.

<FIG> is a flow diagram illustrating a method <NUM> of performing a location measurement at a location server, according to some embodiments. <FIG> illustrates the functionality of a location server according to aspects of embodiments described above. According to some embodiments, functionality of one or more blocks illustrated in <FIG> may be performed by a location server (e.g., location server <NUM>). Means for performing these functions may include software and/or hardware components of location server <NUM>, as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes obtaining beam support information of a plurality of cells. There are various ways of obtaining beam support information. For example, the location server can transmit a query to each of a set of base stations (e.g., gNBs <NUM>) using NRPPa procedures to request for the beam support information. In some examples, as part of E-CID Location Information Transfer under the NRPPa procedures, the location server can transmit a message for an E-CID measurement initiation request to each base station to initiate E-CID operations with the base stations, and the message may include an information element (IE) for the beam support information. In some examples, as part of OTDOA Information Transfer under the NRPPa procedures, the location server can transmit a message for an OTDOA information request to the base stations to initiate OTDOA operations with the base stations, and the message may also include an information element (IE) for the beam support information. Means for performing the functions at block <NUM> may comprise a bus <NUM>, processing unit(s) <NUM>, wireless communication interface <NUM>, memory <NUM>, and/or other hardware and/or software components of location server <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes configuring a location determination operation for a mobile device based on the beam support information, the location determination operation comprising measurements of one or more signals to be performed by at least one of the mobile device or one or more cells of the plurality of cells and may include, for example, an OTDOA operation, an E-CID operation, etc..

There are various ways by which the location server can configure the location determination operation. In some examples, the location server can generate configuration data (e.g., Assistance Data) based on the beam support information at sub-block 804a. The configuration data may include the number of radio beams supported at each cell, the beam widths of the radio beams supported at each cell, identification of the radio beams supported at each cell, etc. The UE can select the subset of the cells supporting the highest number of beams the UE is likely to receive (e.g., based on the AoAs of the beams, a coarse estimate of the UE's present location, known location of the base station, etc.) among the cells based on the configuration data to perform the signal measurements. The UE may also select the subset of the cells supporting beams with the narrowest beam widths among the cells based on the configuration data to perform the signal measurements. In some examples, the location server can also select the subset of the cells based on the beam support information and include the subset of the cells in the configuration data. The location server can send the configuration data to the mobile device at sub-block 804b, to enable the mobile device to perform signal measurements (e.g., PRS signal measurements, E-CID measurements, etc.) with a subset of cells.

In some examples, the location server can select a subset of the cells to perform location measurements with a UE based on the beam support information of the cells, at sub-block 804c. In some examples, the location server can transmit a signal measurement request (e.g., an E-CID measurement initiation response message) to the subset of the cells to initiate signal measurements (e.g., RSRP/RSRQ measurement, Timing Advance measurements, etc.) at the subset of cells, at sub-block 804d. In some examples, the location server can also configure the subset of the cells to update the transmission schedules of positioning reference signals (PRS) (e.g., by increasing the duration of the signals, reducing the periods between the signals, allocating additional carrier bandwidths to transmit the signals, etc.), as part of "On-Demand PRS" operation, at sub-block 804e.

Means for performing the functions at block <NUM>, including sub-blocks 804a-804e, may comprise bus <NUM>, processing unit(s) <NUM>, wireless communication interface <NUM>, memory <NUM>, and/or other hardware and/or software components of location server <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes receiving results of the measurements of the one or more signals. The results can be received from, for example, the mobile device (e.g., RSTD measurements) and/or the base stations of the one or more cells (e.g., AoA measurements, RSRP/RSRQ measurement, Timing Advance measurements, etc.). Means for performing the functions at block <NUM> may comprise bus <NUM>, processing unit(s) <NUM>, wireless communication interface <NUM>, memory <NUM>, and/or other hardware and/or software components of location server <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes determining a location of the mobile device based on the results of the measurements of the one or more signals, based on the techniques described above in. Means for performing the functionsFIG. 5B at block <NUM> may comprise a bus <NUM>, processing unit(s) <NUM>, memory <NUM>, and/or other hardware and/or software components of location server <NUM> as illustrated in <FIG> and described in more detail below.

<FIG> is a flow diagram illustrating a method <NUM> of performing a location measurement at a mobile device (e.g., UE <NUM>), according to some embodiments. <FIG> illustrates the functionality of a mobile device according to aspects of embodiments described above. According to some embodiments, functionality of one or more blocks illustrated in <FIG> may be performed by a mobile device (e.g., UE <NUM>). Means for performing these functions may include software and/or hardware components of UE <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes obtaining beam support information of a plurality of cells. The mobile device may receive the beam support information may via, for example, configuration data (e.g., Assistance Data) from a location server, SIB1 broadcast and/or RRC Reconfig message from a base station, etc. Means for performing the functions at block <NUM> may comprise a bus <NUM>, processing unit(s) <NUM>, wireless communication interface <NUM>, memory <NUM>, and/or other hardware and/or software components of UE <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes performing measurements of one or more signals at the mobile device based on the beam support information of the plurality of cells to support a location determination operation for the mobile device. There are various ways by which the mobile device can perform the measurements based on the beam support information. For example, the mobile device can select a subset of cells to perform the measurements of the one or more signals for the location determination operation, at sub-block 904a. Specifically, the mobile device can select the subset of the cells supporting the highest number of beams the mobile device is likely to receive (e.g., based on the AoAs of the beams, a coarse estimate of the mobile device's present location from GPS signals, known location of the base station, etc.) among the cells based on the configuration data to perform the signal measurements. The mobile device may also select the subset of the cells supporting beams with the narrowest beam widths among the cells based on the configuration data to perform the signal measurements. As another example, the mobile device can transmit, based on the beam support information of the cells, a request to the subset of the cells to update the transmission schedule of PRS (e.g., by increasing the duration of the signals, reducing the periods between the signals, allocating additional carrier bandwidths to transmit the signals, etc.), as part of "On-Demand PRS" operation, at sub-block 904b. Means for performing the functions at block <NUM> may comprise bus <NUM>, processing unit(s) <NUM>, wireless communication interface <NUM>, memory <NUM>, GNSS receiver <NUM>, and/or other hardware and/or software components of UE <NUM> as illustrated in <FIG> and described in more detail below.

At block <NUM>, the functionality includes transmitting results of the measurements to support the location determination operation. The mobile device may transmit the results to a location server (e.g., OTDOA operation) or to the base station it operates with (e.g., RSRQ and/or RSRP measurements for E-CID operation). Means for performing the functions at block <NUM> may comprise bus <NUM>, processing unit(s) <NUM>, wireless communication interface <NUM>, memory <NUM>, GNSS receiver <NUM>, and/or other hardware and/or software components of UE <NUM> as illustrated in <FIG> and described in more detail below.

<FIG> illustrates an embodiment of UE <NUM> (and UE <NUM> of <FIG>), which can be utilized as described herein above (e.g., in association with <FIG>). For example, UE <NUM> can perform one or more of the functions of method <NUM> of <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 (e.g., located at different parts of a user's body, in which case the components may be communicatively connected via a Personal Area Network (PAN) and/or other means).

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 processing unit(s) <NUM> which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing (DSP) chips, graphics acceleration processors, application specific integrated circuits (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 processing unit(s) <NUM> and/or wireless communication interface <NUM> (discussed below). UE <NUM> also can include one or more input devices <NUM>, which can include without limitation a touch screen, a touch pad, microphone, button(s), dial(s), switch(es), and/or the like; and one or more output devices <NUM>, which can include without limitation a display, light emitting diode (LED), speakers, and/or the like.

UE <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 to the UE <NUM>/UE <NUM> to communicate via the networks described above with regard to <FIG>. The wireless communication interface <NUM> may permit data to be communicated with a network, eNBs, gNBs, 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>.

Depending on desired functionality, the wireless communication interface <NUM> may comprise separate transceivers to communicate with base stations (e.g., eNBs and gNBs) and other terrestrial transceivers, such as wireless devices and access points. 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 Code Division Multiple Access (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>), and so on. A CDMA network may implement one or more radio access technologies (RATs) such as cdma2000, Wideband-CDMA (W-CDMA), and so on. Cdma2000 includes IS-<NUM>, IS-<NUM>, and/or IS-<NUM> standards. A TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ LTE, LTE Advanced, and so on. <NUM>, LTE, LTE Advanced, GSM, and W-CDMA 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 wireless local area network (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.

UE <NUM> can further include sensor(s) <NUM>. Such sensors may comprise, without limitation, one or more inertial sensors (e.g., accelerometer(s), gyroscope(s), and or other IMUs), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), and the like, some of which may be used to complement and/or facilitate the location determination described herein.

Embodiments of UE <NUM> may also include a GNSS receiver <NUM> capable of receiving signals <NUM> from one or more GNSS satellites (e.g., SVs <NUM>) using an GNSS antenna <NUM>. Such positioning can be utilized to complement and/or incorporate the techniques described herein. The GNSS receiver <NUM> can extract a location of UE <NUM>, using conventional techniques, from GNSS SVs of a GNSS system, such as Global Positioning System (GPS), Galileo, Glonass, Compass, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, Beidou over China, and/or the like. Moreover, the GNSS receiver <NUM> can be used 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. By way of example but not limitation, an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like. Thus, as used herein a GNSS may include any combination of one or more global and/or regional navigation satellite systems and/or augmentation systems, and GNSS signals may include GNSS, GNSS -like, and/or other signals associated with such one or more GNSS.

UE <NUM> may further include and/or be in communication with a memory <NUM>. 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.

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 executable by UE <NUM> (and/or processing unit(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 computer system <NUM>, which may be utilized and/or incorporated into one or more components of a communication system (e.g., communication system <NUM> of <FIG>), including various components a <NUM> network, including the <NUM> RAN and 5GC, and/or similar components of other network types, and may include location server <NUM>. <FIG> provides a schematic illustration of one embodiment of a computer system <NUM> that can perform the methods provided by various other embodiments, such as the method described in relation to <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. <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 physical or geographical locations. In some embodiments, computer system <NUM> may correspond to an LMF <NUM>, a gNB <NUM> (e.g., gNB <NUM>-<NUM>), an eNB, an E-SMLC, a SUPL SLP and/or some other type of location-capable device.

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 processing unit(s) <NUM>, which can include 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, including the method described in relation to <FIG>. The computer system <NUM> also can include one or more input devices <NUM>, which can include without limitation a mouse, a keyboard, a camera, a microphone, and/or the like; and one or more output devices <NUM>, which can include without limitation a display device, a printer, and/or the like.

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 can include, without limitation, 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.

Computer system <NUM> may also include a communications subsystem <NUM>, which can include support of wireline communication technologies and/or wireless communication technologies (in some embodiments) managed and controlled by a wireless communication interface <NUM>. The communications subsystem <NUM> may include a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset, and/or the like. The communications subsystem <NUM> may include one or more input and/or output communication interfaces, such as the wireless communication interface <NUM>, to permit data to be exchanged with a network, mobile devices, other computer systems, and/or any other electronic devices described herein. Note that the terms "mobile device" and "UE" are used interchangeably herein to refer to any mobile communications device such as, but not limited to, mobile phones, smartphones, wearable devices, mobile computing devices (e.g., laptops, PDAs, tablets), embedded modems, and automotive and other vehicular computing devices.

In many embodiments, computer system <NUM> will further comprise a working memory <NUM>, which can include a RAM and/or or ROM device. Software elements, shown as being located within the working memory <NUM>, can include an operating system <NUM>, device drivers, executable libraries, and/or other code, such as application(s) <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, such as the method described in relation to <FIG>, may be implemented as code and/or instructions executable by a computer (and/or a processing unit 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 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.

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 processing units 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, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a 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 that do not limit the scope of the disclosure to those specific 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 discussions 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 mobile device (<NUM>), comprising:
a wireless communication interface (<NUM>) and one or more wireless communication antennas (<NUM>);
memory (<NUM>); and
a processor (<NUM>), communicatively coupled to the wireless communication interface (<NUM>) and the memory (<NUM>), the mobile device (<NUM>) configured to:
receive beam support information of a plurality of cells, wherein the beam support information comprises a number of beams supported by each cell of the plurality of cells;
perform measurements of one or more signals at the mobile device (<NUM>), the one or more signals selected, at least in part, based on the beam support information of the plurality of cells to support a location determination operation of the mobile device; and
transmit results of the measurements of the one or more signals to a location server or to a base station to support the location determination operation.