Precision-based GNSS frequency band selection

Abstract

In some embodiments, a device may receive a request for global navigation satellite system (GNSS) location positioning information. The request may include a precision requirement. The apparatus may determine a set of GNSS frequency bands to be used to determine GNSS position positioning information. The set of GNSS frequency bands may include one or more frequency bands from a plurality of available GNSS frequency bands, and determining the set of GNSS frequency bands to use may be based at least in part on accuracy requirements. The apparatus may determine GNSS position positioning information based at least in part on the GNSS signals received via the selected set of GNSS frequency bands. The apparatus may provide GNSS location positioning information (e.g., to an application processor). The GNSS position positioning information may include GNSS position positioning, pseudo-range information, or both.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Application No. 17 / 811,850, filed on July 11, 2022, entitled “ACCURACY-BASED GNSS BAND SELECTION,” which application is assigned to the assignee of the present application, and the entire contents of which are incorporated herein by reference. Background Art

[0003] Modern electronic devices often include systems that can receive signals from at least one satellite navigation system, often referred to as a Global Navigation Satellite System (GNSS), and use these signals to determine the device's location as well as other information such as speed, heading, altitude, etc. Such GNSS receivers can be integrated into consumer electronic devices such as smartphones or smart watches, as well as into navigation systems in different types of vehicles, including cars, trucks, ships, and airplanes. Signals are received by a GNSS receiver from a plurality of satellites orbiting the Earth and are processed to determine the location of the GNSS receiver and, by proxy, the location of the device, vehicle, etc. However, GNSS receivers can often use a relatively large amount of power to make position determinations. Summary of the invention

[0004] Embodiments disclosed herein provide adaptive GNSS band selection based on desired accuracy. Specifically, an application processor may include accuracy requirements in a GNSS position fix information request to a GNSS receiver. The GNSS receiver may use the accuracy requirements to determine which GNSS band(s) to use when determining GNSS position fix information. The GNSS receiver may also power down or power off RF components associated with unused GNSS bands, thereby allowing power savings.

[0005] According to the present disclosure, an example method for providing global navigation satellite system (GNSS) position fix information may include receiving a request for GNSS position fix information, wherein the request includes an accuracy requirement. The method may also include determining a GNSS band set to be used for determining GNSS position fix information from a plurality of GNSS bands available to a GNSS receiver based at least in part on the accuracy requirement. The method may also include determining GNSS position fix information based at least in part on GNSS signals received via the GNSS band set. The method may also include providing GNSS position fix information, wherein the GNSS position fix information includes GNSS position fix, pseudorange information, or both.

[0006] According to the present disclosure, an example device for providing global navigation satellite system (GNSS) position location information may include a data communication interface, a memory, and one or more processors communicatively coupled to the data communication interface and the memory, wherein the one or more processors are configured to receive a request for GNSS position location information via the data communication interface, wherein the request includes an accuracy requirement. The one or more processors may also be configured to determine a GNSS band set to be used for determining GNSS position location information from a plurality of GNSS bands available to a GNSS receiver based at least in part on the accuracy requirement. The one or more processors may also be configured to determine the GNSS position location information based at least in part on GNSS signals received via the GNSS band set. The one or more processors may also be configured to provide GNSS position location information using the data communication interface, wherein the GNSS position location information includes GNSS position location, pseudorange information, or both.

[0007] According to the present disclosure, an example apparatus for providing global navigation satellite system (GNSS) position fix information may include a component for receiving a request for GNSS position fix information at the apparatus, wherein the request includes an accuracy requirement. The apparatus may also include a component for determining a set of GNSS bands to be used for determining GNSS position fix information from a plurality of GNSS bands available to the apparatus based at least in part on the accuracy requirement. The apparatus may also include a component for determining GNSS position fix information based at least in part on GNSS signals received via the set of GNSS bands. The device may also include a device for providing GNSS position fix information, wherein the GNSS position fix information includes GNSS position fix, pseudorange information, or both.

[0008] According to the present disclosure, an example non-transitory computer-readable medium stores instructions for providing global navigation satellite system (GNSS) position location information, the instructions including code for receiving a request for GNSS position location information, wherein the request includes an accuracy requirement. The instructions may also include code for determining a set of GNSS bands to be used for determining GNSS position location information from a plurality of GNSS bands available to a GNSS receiver based at least in part on the accuracy requirement. The instructions may also include code for determining GNSS position location information based at least in part on GNSS signals received via the GNSS band set. The instructions may also include code for providing GNSS position location information, wherein the GNSS position location information includes GNSS position location, pseudorange information, or both.

[0009] The present disclosure is neither intended to identify the key or essential features of the claimed subject matter nor is it intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood by reference to the appropriate portions of the entire specification of the present disclosure, any or all of the drawings, and each claim. The foregoing and other features and examples will be described in more detail below in the following specification, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram of a positioning system according to an embodiment.

[0011] Figure 2 is a simplified diagram of a GNSS system according to an embodiment.

[0012] Figure 3 It is the frequency band diagram of satellite signals and the frequency of satellite signals.

[0013] Figure 4 A simplified block diagram of an example GNSS receiver is shown in accordance with an embodiment.

[0014] Figure 5 is a call flow diagram illustrating an example exchange between an application processor and a GNSS receiver according to an embodiment.

[0015] Figure 6 is a flow chart of a first process that a GNSS receiver may perform to determine which GNSS frequency bands to use to determine GNSS position location information according to an embodiment.

[0016] Figure 7 is a flow chart of a second process that a GNSS receiver may perform to determine which GNSS frequency bands to use to determine GNSS position fix information according to an embodiment.

[0017] Figure 8 is a flow chart of a third process that a GNSS receiver may perform to determine which GNSS frequency bands to use to determine GNSS position fix information according to an embodiment.

[0018] Fig. 9 is a flowchart of a method for providing GNSS position positioning information according to an embodiment.

[0019] Fig.10 is a block diagram of an embodiment of a mobile device that can be used in the embodiments described herein.

[0020] According to certain exemplary embodiments, the same reference numerals represent the same elements in each of the accompanying drawings. In addition, multiple examples of an element can be indicated by following a letter or hyphen and a second numeral after the first numeral of the element. For example, multiple examples of element 110 can be represented as 110-1, 110-2, 110-3, etc., or as 110a, 110b, 110c, etc. When only the first numeral is used to refer to such an element, any example of the element will be understood (for example, the element 110 in the previous example will refer to element 110-1, 110-2 and 110-3 or to element 110a, 110b and 110c). DETAILED DESCRIPTION

[0021] Several illustrative examples will now be described with reference to the accompanying drawings, which form a part of the present disclosure. Although specific examples in which one or more aspects of the present disclosure may be implemented are described below, other examples may be used and various modifications may be made without departing from the scope of the present disclosure or the spirit of the appended claims.

[0022] Reference throughout this specification to "one example" or "an example" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one example of the claimed subject matter. Thus, the appearances of the phrase "in one example" or "an example" in various places throughout this specification are not necessarily all referring to the same example. Furthermore, the particular features, structures, or characteristics may be combined in one or more examples.

[0023] The methods described herein may be implemented by various components depending on the application according to a specific example. For example, such methods may be implemented in hardware, firmware, software and / or a combination thereof. In a hardware embodiment, for example, a processing unit may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other equipment units designed to perform the functions described herein, and / or combinations thereof.

[0024] As used herein, the terms "mobile device" and "user equipment" (UE) are used interchangeably and are not intended to be specific to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a mobile device and / or UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headsets, etc.), a vehicle (e.g., a car, a ship, an airplane motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.), or other electronic devices that may be used for global navigation satellite system (GNSS) positioning as described herein. According to some embodiments, a mobile device and / or UE may be used to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term UE may be interchangeably referred to as an access terminal (AT), a client device, a wireless device, a subscriber device, a subscriber terminal, a subscriber station, a user terminal (UT), a mobile device, a mobile terminal, a mobile station, or variations thereof. Typically, the UE can communicate with the core network via the RAN, and through the core network, the UE can be connected to an external network (such as the Internet) and to other UEs. Other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.), etc.

[0025] "Spacecraft" (SV) as referred to herein refers to an object capable of transmitting signals to a receiver on the surface of the Earth. In one particular example, such an SV may include a geostationary satellite. Alternatively, an SV may include a satellite that travels in an orbit and moves relative to a stationary position on the Earth. However, these are merely examples of SVs, and the claimed subject matter is not limited in these respects. SVs may also be referred to herein simply as "satellites."

[0026] As described herein, a GNSS receiver may include an electronic device and / or be incorporated into an electronic device. This may include a single entity or may include multiple entities, such as in a personal area network, where a user may employ audio, video and / or data I / O devices and / or body sensors and a separate wired or wireless modem. As described herein, an estimate of the position of a global positioning system (GPS) receiver may be referred to as a location, location estimate, location fix, fix, position, location estimate, or location fix, and may be geodetic, thereby providing location coordinates (e.g., latitude and longitude) of a GPS receiver, which may or may not include an altitude component (e.g., height above sea level, height above ground level, or depth below ground level, floor level, or basement level). In some embodiments, the location of a GPS receiver and / or an electronic device including a GPS receiver may also be expressed as an area or volume (defined geographically or in terms of a city) in which the GPS receiver is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). In the description contained herein, unless otherwise specified, the use of the term location may include any of these variations. When calculating the position of a GPS receiver, this calculation can solve for the local X, Y, and possibly Z coordinates and then, if necessary, transform the coordinates from one coordinate system to another.

[0027] As described above, GNSS positioning typically consumes a relatively large amount of power. This can be particularly burdensome for devices with tight power budgets, such as battery-powered mobile devices. To address these and other issues, embodiments herein provide accuracy-specific positioning, whereby a GNSS receiver can use accuracy requirements (e.g., as provided in a request from an application processor) to determine which GNSS band(s) to use when determining GNSS positioning location information. In this way, embodiments enable a GNSS receiver to use a single GNSS band when accuracy requirements permit, thereby providing power savings that would otherwise not be achieved. Additional details will follow after an initial description of the relevant systems and techniques.

[0028] Figure 1is a simplified illustration of a positioning system 100 according to an embodiment, in which a mobile device 105, a location server 160, and / or other components of the positioning system 100 can use the techniques provided herein to perform precision-based GNSS band selection for positioning of the mobile device 105. The techniques described herein can be implemented by one or more components of the positioning system 100. The positioning system 100 can include: a mobile device 105; one or more satellites 110 (also referred to as space vehicles (SVs)) for GNSS, such as China's GPS, GLONASS (GLO), Galileo (GAL), or BeiDou Navigation Satellite System (BDS); a base station 120; an access point (AP) 130; a location server 160; a network 170; and an external client 180. In general, the positioning system 100 can estimate the location of the mobile device 105 based on radio frequency (RF) signals received and / or transmitted by the mobile device 105 and the known locations of other components (e.g., GNSS satellites 110, base stations 120, APs 130) that transmit and / or receive RF signals. Additional details about specific location estimation techniques Figure 2 Discuss in more detail.

[0029] In this example, Figure 1 The mobile device 105 is illustrated as a smart phone device, however, the mobile device may be any suitable device including GNSS capabilities or may be a device or machine that integrates such GNSS capabilities. Thus, the mobile device 105 may include personal devices such as smart phones, smart watches, tablet computers, laptop computers, etc. However, the mobile device may also include a larger class of devices and may include vehicles with integrated GNSS receivers and positioning systems, such as boats or ships, cars, trucks, airplanes, shipping containers, etc. As described above, in some contexts, such as with respect to cellular networks, the mobile device 105 may be referred to as a UE.

[0030] It should be noted that Figure 1 Only a generalized description of the various components is provided, any or all of which may be used as appropriate, and each of which may be replicated as needed. In particular, although only one mobile device 105 is shown, it will be understood that many mobile devices (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system 100. Similarly, the positioning system 100 may include more than one mobile device 105. Figure 1A greater or lesser number of base stations 120 and / or APs 130 are shown. The illustrated connections connecting the various components in the positioning system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, components may be rearranged, combined, separated, replaced, and / or omitted, depending on the desired functionality. In some embodiments, for example, the external client 180 may be directly connected to the location server 160. Those of ordinary skill in the art will recognize many modifications to the illustrated components.

[0031] Depending on the desired functionality, network 170 may include any of a variety of wireless and / or wired networks. Network 170 may, for example, include any combination of public and / or private networks, local area networks, and / or wide area networks, etc. In addition, network 170 may utilize one or more wired and / or wireless communication technologies. In some embodiments, network 170 may include, for example, cellular or other mobile networks, wireless local area networks (WLANs), wireless wide area networks (WWANs), and / or the Internet. Examples of network 170 include long-term evolution (LTE) wireless networks, fifth-generation (5G) wireless networks (also referred to as new radio (NR) wireless networks or 5G NR wireless networks), Wi-Fi WLANs, and the Internet. LTE, 5G, and NR are wireless technologies defined or being defined by the Third Generation Partnership Project (3GPP). Network 170 may also include more than one network and / or more than one type of network.

[0032] The base station 120 and the access point 130 may be communicatively coupled to the network 170. In some embodiments, the base station 1205 may be owned, maintained and / or operated by a cellular network provider and may employ any of a variety of wireless technologies, as described below. Depending on the technology of the network 170, the base station 120 may include a Node B, an evolved Node B (eNodeB or eNB), a base transceiver station (BTS), a radio base station (RBS), an NR Node B (gNB), a next generation eNB (ng-eNB), etc. The base station 120 as a gNB or ng-eNB may be part of a next generation radio access network (NG-RAN), which may be connected to a 5G core network (5GC) in the case where the network 170 is a 5G network. In view of the open radio access network (O-RAN) and / or virtualized radio access network (V-RAN or vRAN) in 5G or later networks, the functions performed by the base station 120 in earlier generation networks (e.g., 3G and 4G) may be divided into different functional components (e.g., radio unit (RU), distributed unit (DU), central unit (CU)) and layers (e.g., L1 / L2 / L3), which may be performed on different devices at different locations connected, for example, via fronthaul, midhaul, and backhaul connections. As described herein, a "base station" (or ng-eNB, gNB, etc.) may include any or all of these functional components. For example, AP 130 may include a Wi-Fi AP or AP or an AP with cellular capabilities (e.g., 4G LTE and / or 5G NR). Thus, mobile device 105 can send and receive information with networked devices (such as location server 160) by accessing network 170 via base station 120 using first communication link 133. Additionally or alternatively, because AP 130 can also be communicatively coupled with network 170, mobile device 105 can communicate with network-connected and Internet-connected devices (including location server 160) using second communication link 135 or via one or more other mobile devices 145.

[0033] As used herein, the term "base station" may generally refer to a single physical transmission point, or to multiple co-located physical transmission points that may be located at a base station 120. A transmit receive point (TRP) (also referred to as a transmit / receive point) corresponds to this type of transmission point, and the term "TRP" may be used interchangeably herein with the terms "gNB," "ng-eNB," and "base station." In some cases, a base station 120 may include multiple TRPs—e.g., each TRP is associated with a different antenna or a different antenna array of the base station 120. A physical transmission point may include an antenna array of the base station 120 (e.g., as in a multiple-input multiple-output (MIMO) system and / or where the base station employs beamforming). The term "base station" may additionally refer to multiple non-co-located physical transmission points, which may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station).

[0034] As used herein, the term "cell" may generally refer to a logical communication entity for communicating with base station 120, and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) for distinguishing adjacent cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of devices. In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) on which a logical entity operates.

[0035] The location server 160 may include a server and / or other computing device configured to determine an estimated location of the mobile device 105 and / or provide data (e.g., “assistance data”) to the mobile device 105 to facilitate location measurement and / or location determination of the mobile device 105. According to some embodiments, the location server 160 may include a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support a SUPL User Plane (UP) location solution defined by the Open Mobile Alliance (OMA), and may support location services for the mobile device 105 based on subscription information of the mobile device 105 stored in the location server 160. In some embodiments, the location server 160 may include a Discovery SLP (D-SLP) or an Emergency SLP (E-SLP). The location server 160 may also include an Enhanced Serving Mobile Location Center (E-SMLC) that supports positioning of the mobile device 105 using a Control Plane (CP) location solution for LTE radio access of the mobile device 105. The location server 160 may also include a location management function (LMF) that supports positioning of the mobile device 105 using a control plane (CP) positioning solution for NR or LTE radio access of the mobile device 105 .

[0036] In the CP positioning solution, signaling for controlling and managing the location of the mobile device 105 can be exchanged between elements of the network 170 and exchanged with the mobile device 105 using existing network interfaces and protocols and as signaling from the perspective of the network 170. In the UP positioning solution, signaling for controlling and managing the location of the mobile device 105 can be exchanged between the positioning server 160 and the mobile device 105 from the perspective of the network 170 as data (e.g., data transmitted using the Internet Protocol (IP) and / or the Transmission Control Protocol (TCP)).

[0037] As previously mentioned (and discussed in more detail below), the estimated position of the mobile device 105 can be based on measurements of RF signals transmitted from and / or received by the mobile device 105. In particular, these measurements can provide information about the relative distances and / or angles of the mobile device 105 to one or more components in the positioning system 100 (e.g., GNSS satellites 110, APs 130, base stations 120). The estimated position of the mobile device 105 can be estimated geometrically (e.g., using multi-angle measurements and / or multilateration) based on the distance and / or angle measurements along with the known positions of the one or more components.

[0038] Although ground components such as AP 130 and base station 120 may be fixed, embodiments are not limited thereto. Mobile components may be used. For example, in some embodiments, the location of mobile device 105 may be estimated based at least in part on measurements of RF signals 140 communicated between mobile device 105 and one or more other mobile devices 145 (which may be mobile or fixed). As shown, other mobile devices may include, for example, mobile phones 145-1, vehicles 145-2, and / or static communication / positioning devices 145-3. When one or more other mobile devices 145 are used for location determination of a specific mobile device 105, the mobile device 105 to be located may be referred to as a "target mobile device", and each of the one or more other mobile devices 145 used may be referred to as an "anchor mobile device". For location determination of the target mobile device, the corresponding locations of one or more anchor mobile devices may be known and / or determined jointly with the target mobile device. Direct communication between one or more other mobile devices 145 and mobile device 105 may include side links and / or similar device-to-device (D2D) communication technologies. The side link defined by 3GPP is a form of D2D communication under cellular-based LTE and NR standards.

[0039] According to some embodiments, such as when the mobile device 105 includes a vehicle and / or is incorporated into a vehicle, the form of D2D communication used by the mobile device 105 may include vehicle-to-everything (V2X) communication. V2X is a communication standard for vehicles and related entities to exchange information about the traffic environment. V2X may include vehicle-to-vehicle (V2V) communication between vehicles with V2X capabilities, vehicle-to-infrastructure (V2I) communication between vehicles and infrastructure-based equipment (commonly referred to as roadside units (RSUs)), vehicle-to-person (V2P) communication between vehicles and nearby personnel (pedestrians, cyclists, and other road users), etc. In addition, V2X may use any of a variety of wireless RF communication technologies. For example, cellular V2X (CV2X) is a form of V2X that uses cellular-based communications, such as LTE (4G), NR (5G), and / or other cellular technologies in a direct communication mode defined by 3GPP. Figure 1The mobile device 105 shown in the figure may correspond to a component or device on a vehicle, RSU, or other V2X entity for communicating V2X messages. Thus, the static communication / positioning device 145-3 (which may correspond to an RSU) and / or the vehicle 145-2 may communicate with the mobile device 105 and may be used to determine the location of the mobile device 105 using techniques similar to those used by the base station 120 and / or the AP 130 (e.g., using multi-angle measurements and / or multi-point positioning). It may also be noted that, according to some embodiments, the mobile device 145 (which may include a V2X device), the base station 120, and / or the AP 130 may be used together (e.g., in a WWAN positioning solution) to determine the location of the mobile device 105.

[0040] The estimated location of the mobile device 105 can be used in a variety of applications, for example, to assist the user of the mobile device 105 in direction finding or navigation, or to assist another user (e.g., associated with an external client 180) in locating the mobile device 105. "Location" is also referred to herein as "location estimate", "estimated location", "location", "position", "location estimation", "location fix", "estimated location", "location fix", or "positioning". The process of determining a location may be referred to as "positioning", "position determination", "location determination", etc. The location of the mobile device 105 may include an absolute location of the mobile device 105 (e.g., latitude and longitude and possibly altitude) or a relative location of the mobile device 105 (e.g., a location expressed as a distance north or south, east or west and possibly above or below some other known fixed location (including, for example, the location of a base station 120 or AP 130) or some other location, such as the location of the mobile device 105 at some known previous time, or the location of another mobile device 145 at some known previous time). As described elsewhere herein, a location may be specified as a geodetic location including coordinates that may be absolute (e.g., latitude, longitude, and optionally altitude), relative (e.g., relative to some known absolute location), or local (e.g., X, Y, and optionally Z coordinates according to a coordinate system defined relative to a local area, such as a factory, warehouse, college campus, shopping mall, stadium, or convention center). The location may alternatively be a city location, and may then include a street address (e.g., including a country, state, county, city, road, and / or street name or label, and / or road or street number) and / or one or more of a place, a building, a portion of a building, a floor of a building, and / or a room within a building, etc. The location may also include an uncertainty or error indication, such as a level of expected position error and a likely vertical distance or an indication of an area or volume (e.g., a circle or ellipse) within which the mobile device 105 is expected to be located with a certain confidence level (e.g., 95% confidence).

[0041] The external client 180 may be a network server or remote application that may have some association with the mobile device 105 (e.g., accessible by a user of the mobile device 105), or may be a server, application, or computer system that provides location services to some other user or users, which may include obtaining and providing the location of the mobile device 105 (e.g., to enable services such as a friend or relative finder or a child or pet location). Additionally or alternatively, the external client 180 may obtain the location of the mobile device 105 and provide it to emergency service providers, government agencies, etc.

[0042] As mentioned above, Figure 1 The mobile device 105 is capable of GNSS positioning. Figure 2 Provides details about the GNSS position of the mobile device 105 or any device including a GNSS receiver.

[0043] Figure 2 2 is a simplified diagram of a GNSS system 200 that is provided to illustrate how GNSS is typically used to determine an accurate position of a GNSS receiver 210 on Earth 220. In general, the GNSS system 200 enables accurate GNSS position fixes for a GNSS receiver 210 that receives RF signals from GNSS satellites 230 from one or more GNSS constellations. The type of GNSS receiver 210 used may vary depending on the application. In some embodiments, for example, the GNSS receiver 210 may include a standalone device or may be incorporated into another device (e.g., Figure 1 In some embodiments, the GNSS receiver 210 may be integrated into industrial or commercial equipment, such as surveying equipment, Internet of Things (IoT) devices, etc.

[0044] It should be understood that Figure 2 The diagram provided in is greatly simplified. In practice, there may be dozens of satellites 230 and a given GNSS constellation, and there are many different types of GNSS systems. As described above, GNSS systems include GPS, Galileo, GLONASS or BDS. Other GNSS systems include, for example, Japan's Quasi-Zenith Satellite System (QZSS), India's Indian Regional Navigation Satellite System (IRNSS), etc. In addition to the basic positioning functions described later, GNSS enhancements (e.g., satellite-based augmentation systems (SBAS)) can be used to provide higher accuracy. This enhancement can be associated with one or more global and / or regional navigation satellite systems or otherwise enabled for use with one or more global and / or regional navigation satellite systems, such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-Function Satellite Augmentation System (MSAS) and / or Geographic Augmentation Navigation System (GAGAN), etc.

[0045] GNSS positioning is based on trilateration / multilateration, which is a method of determining a position by measuring the distance to a point at known coordinates. In general, the determination of the position of a GNSS receiver 210 in three dimensions can rely on the determination of the distance between the GNSS receiver 210 and four or more satellites 230. As shown, the 3D coordinates can be based on a coordinate system centered on the center of mass of the earth (e.g., XYZ coordinates, latitude, longitude, and altitude, etc.). The distance between each satellite 230 and the GNSS receiver 210 can be determined using an accurate measurement by the GNSS receiver 210 of the time difference from when the RF signal is sent from the corresponding satellite 230 to when the RF signal is received at the GNSS receiver 210. To help ensure accuracy, the GNSS receiver 210 not only needs to accurately determine when the corresponding signal from each satellite 230 is received, but also needs to consider and take into account many additional factors. These factors include, for example, clock differences at the GNSS receiver 210 and the satellites 230 (e.g., clock bias), the precise position of each satellite 230 at the time of transmission (e.g., determined by the broadcast ephemeris), the effects of atmospheric distortions (e.g., ionospheric and tropospheric delays), etc.

[0046] To perform a conventional GNSS position fix, the GNSS receiver 210 may use code-based positioning to determine its distance to each satellite 230 based on the delay determined in the generated pseudo-random binary sequence received in the RF signal received from each satellite, taking into account the additional factors and error sources mentioned above. Using the distance and position information of the satellites 230, the GNSS receiver 210 may then determine a position fix of its position. The position fix may be determined, for example, by a separate positioning engine (SPE) executed by one or more processors of the GNSS receiver 210. However, code-based positioning is relatively inaccurate and, without error correction, is subject to many of the errors described previously. Even so, code-based GNSS positioning may provide the GNSS receiver 210 with a positioning accuracy of approximately several meters.

[0047] More accurate carrier-based ranging is based on the carrier of the RF signal received from each satellite, and error correction can be performed using measurements at a base station or reference station (not shown) to help reduce errors from the aforementioned error sources. More specifically, errors in carrier-based ranging of satellites 230 observed by GNSS receiver 210 (e.g., atmospheric error sources) can be mitigated or eliminated using highly accurate GNSS receivers at base stations at known locations based on similar carrier-based ranging of satellites 230. These measurements and the locations of the base stations can be provided to GNSS receiver 210 for error correction. This position fix can be determined, for example, by a precise positioning engine (PPE) executed by one or more processors of GNSS receiver 210. More specifically, in addition to the information provided to the SPE, the PPE can also use base station GNSS measurement information and additional correction information (such as troposphere and ionosphere) to provide a high-precision carrier-based position fix. Several GNSS technologies may be employed in the PPE, such as differential GNSS (DGNSS), real-time kinematics (RTK), and precise point positioning (PPP), and may provide sub-meter accuracy (e.g., centimeter level). (The SPE and / or PPE may be referred to herein as a GNSS positioning engine, and may be incorporated into a broader positioning engine that uses other (non-GNSS) positioning sources.)

[0048] A multi-frequency GNSS receiver uses satellite signals from different GNSS frequency bands (also referred to herein simply as "GNSS bands") to determine desired information, such as pseudoranges, position estimates, and / or time. Under many conditions, the use of multi-frequency GNSS can provide better performance (e.g., position estimate speed and / or accuracy) than single-frequency GNSS. However, as discussed in more detail below, the use of multi-frequency GNSS generally uses more power than single-frequency GNSS, such as processing power and battery power (e.g., to power a processor (e.g., for determining measurements), baseband processing, and / or RF processing).

[0049] Reference again Figure 2, satellites 230 may be members of a single satellite constellation, i.e., a group of satellites that are part of a GNSS system, e.g., controlled by a public entity such as a government, and orbiting in complementary orbits to help determine the location of entities around the world. One or more of satellites 230 may transmit multiple satellite signals in different GNSS frequency bands, such as L1, L2, and / or L5 bands. The terms L1 band, L2 band, and L5 band are used here because these terms are used in GPS to refer to corresponding frequency ranges. Various receiver configurations may be used to receive satellite signals. For example, a receiver may use separate receive chains for different frequency bands. As another example, a receiver may use a common receive chain for multiple frequency bands that are close in frequency, e.g., L2 and L5 bands. As another example, a receiver may use separate receive chains for different signals in the same frequency band (e.g., GPS L1 and GLONASS L1 sub-bands). A single receiver may use a combination of two or more of these examples. These configurations are examples, and other configurations are possible.

[0050] Multiple satellite frequency bands are allocated for satellite use. These bands include the L-band for GNSS satellite communications, the C-band for communications satellites such as television broadcast satellites, the X-band used by military and RADAR applications, and the Ku-band (mainly downlink communications) and the Ka-band (mainly uplink communications), the Ku and Ka-bands for communications satellites. The L-band is defined by IEEE as a frequency range from 1 to 2 GHz. The L-band is utilized by GNSS satellite constellations (such as GPS, Galileo, GLONASS, and BDS) and is divided into various bands, including L1, L2, and L5. For positioning purposes, the L1 band has historically been used by commercial GNSS receivers. However, measuring GNSS signals across more than one band can provide improved accuracy and availability.

[0051] Figure 3 is a diagram of GNSS frequency bands 300 that may be used in a GNSS receiver according to embodiments herein. (With other attached Figure 1 Sample, Figure 3300 shows that the GNSS constellation operates on several frequencies in the L-band. The L1 band generally covers frequencies from 1559 MHz to 1606 MHz and includes L1 signals from GPS, Galileo, BDS, GLONASS, and QZSS GNSS constellations. The frequency bands within this spectrum may be referred to herein as "upper bands" 310. The same constellation using these upper bands 310 may also transmit concurrently using one or more other bands in the spectrum generally from 1164 MHz to 1246 MHz (which may be referred to herein as "lower bands" 320). Example frequency bands within the lower band 320 include the L2 band and the L5 band. Satellites may transmit, for example, L2 and / or L5 signals as well as the L1 signal. The L2 and L5 signals may supplement the L1 signal that has been in use for many years. For example, the L5 signal has a wider signal bandwidth than the L1 signal, which helps improve positioning performance in a multipath environment. Furthermore, using an L5 signal in addition to an L1 signal can allow for frequency diversity. The L2 and L5 signals are sufficiently distant in frequency from the L1 signal, for example, so that different processing paths are typically used to measure the L2 and L5 signals versus the L1 signal. Although the discussion herein focuses on the L1 and L5 frequency bands, the discussion (including the claims) is not limited to these frequency bands, nor is it limited to using satellite signals in two or three frequency bands.

[0052] Figure 4 A simplified block diagram of an example signal processing architecture 400 that can be used in a GNSS receiver to implement GNSS signal acquisition and tracking using multiple GNSS frequency bands is shown. The signal processing architecture 400 can be implemented in hardware and / or software components of a GNSS receiver, such as described elsewhere herein (e.g., with respect to Figure 1-Figure 10 ) discussed above, including the GNSS receiver 1080 of FIG. 12 , which is described in more detail below.

[0053] It can be noted that alternative embodiments may implement Figure 4 4. A variation of the signal processing architecture 400 shown in FIG. 4 is shown. For example, the signal processing architecture 400 shows two RF chains (a first RF chain represented by components 402-1 to 414-1, and a second RF chain represented by components 402-2 to 414-2), however embodiments are not limited thereto. Alternative embodiments may have any number of RF chains, including only one. As described below, different RF chains may be used to receive and process different frequency bands or groups of frequency bands. In some embodiments, for example, the first RF chain represented by components 402-1 to 414-1 may receive and process ( Figure 3) one or more upper frequency bands 310, and a second RF chain represented by components 402-2 to 414-2 receives and processes one or more lower frequency bands 320. In addition, components such as antennas, filters, amplifiers, or any combination thereof may be shared by different RF chains. Different RF chains may employ different architectures. That is, some RF chains may employ the same architecture. Figure 4 As shown, the architecture of the second RF chain mirrors the architecture of the first RF chain. As such, the following description of components 402-1 through 414-1 may be applied to components 402-2 through 414-2 (eg, for different GNSS signal pairs).

[0054] A single RF chain is capable of receiving and processing multiple GNSS signals. For example, the first RF chain represented by components 402-1 to 414-1 can be used to receive and process multiple GNSS signals by combining the received signal with a frequency F LO The local oscillator (LO) signal is mixed to process the two GNSS signals GNSS1 and GNSS2. The frequency F LO The determination is based at least in part on the first carrier frequency f1 and the second carrier frequency f2. Figure 4 As shown, according to certain embodiments, the signal processing architecture 400 can receive signals GNSS1 and GNSS2 at a single antenna 402-1, a bandpass RF filter 404-1 such as a surface acoustic wave (SAW) filter, and a low noise amplifier (LNA) 406-1. Then, as shown, the received GNSS signals can be complex down-converted to an intermediate frequency by mixing the received signals with a LO signal.

[0055] As used herein, "down conversion" may involve transforming an input signal having a first frequency characteristic into an output signal having a second frequency characteristic. In a particular embodiment, although the claimed subject matter is not limited in this respect, such down conversion may include transforming a first signal into a second signal, wherein the second signal has a frequency characteristic lower than the frequency of the first signal. Here, in particular examples, such down conversion may include transforming a radio frequency (RF) signal into an intermediate frequency (IF) signal, or transforming an IF signal into a baseband signal and / or baseband information. However, these are merely examples of down conversion, and the claimed subject matter is not limited in this respect.

[0056] Returning to the example in which the first RF chain represented by components 402-1 to 414-1 is used to process two GNSS signals, by selecting F at approximately the midpoint between f1 and f2 LO , the portion of the down-converted signal can be substantially covered by the bandpass filters (BPF) 408-1 and 410-1. Here, for example, F is selected LOThe particular frequency of F may result in an image frequency component of one down-converted GNSS signal that may substantially overlap with a desired signal component of another down-converted GNSS signal. In certain embodiments, the effects of such overlap may be avoided by not attenuating the image frequency component prior to mixing with the LO. However, it should be appreciated that in other embodiments, F LO can be chosen to be somewhere other than approximately midway between f1 and f2.

[0057] The in-phase (I) and quadrature (Q) components filtered by the associated BPFs 408-1 and 410-1 may then be digitally sampled at analog-to-digital conversion circuits 412 and 414 to provide digitally sampled in-phase and quadrature components for further processing, including complex down-conversion (e.g., to baseband) and digital baseband processing 416. Here, the ADCs 412-1 and 414-1 may be adapted to sample the output signals of the BPFs 408-1 and 410-1 at or above the Nyquist rate of the combined signal.

[0058] In addition, the presently illustrated embodiment includes ADCs 412-1 and 414-1 between the first and second down-conversion stages (e.g., within IF down-conversion and processing block 418-1). However, it should be appreciated that other architectures may be implemented without departing from the claimed subject matter. In other embodiments, for example, the analog-to-digital conversion may occur after the second down-conversion. Again, these are merely example embodiments, and the claimed subject matter is not limited in these respects.

[0059] Furthermore, in alternative implementations, ADCs 412-1 and 414-1 may be replaced with a single composite ADC or with a single time-shared and / or multiplexed ADC with appropriate delays shared between the in-phase and quadrature signal paths.

[0060] In certain embodiments, GNSS1 and / or GNSS2 may include any of a number of different GNSS signal pairs. In a certain embodiment, although the claimed subject matter is not limited in this respect, GNSS1 and GNSS2 may be selected such that f1 and f2 are close in frequency to enable low-cost manufacturing of SAW 404-1 and / or LNA 406-1 by limiting the operating frequency band. Here, for example, GNSS land GNSS2 may include any of several pairs, such as GPS L1 and GLONASS L1 (where f1=1575MHz and f2=1602MHz), GPS L1 and Compass L1 (where f1=1575MHz and f2=1590 or 1561MHz), Galileo L1 and GLONASS L1 (where f1=1575MHz and f2=1602MHz), GPS L2 and GLONASS L2 (where f1=1228MHz and f2=1246MHz), and GPS L2 and Compass L2 (where f1=1228MHz and f2=1269MHz or 1207MHz). However, it should be understood that these are merely specific examples of GNSS pairs that may be selected in particular embodiments, and the claimed subject matter is not limited to any particular GNSS pair.

[0061] In certain embodiments, the bandwidth of BPFs 408-1 and 410-1 may be centered around a common intermediate frequency IFo to process portions of the GNSS signals received from both GNSS1 and GNSS2. Additionally, the bandwidth of BPFs 408 and 410 may be implemented to be wide enough to capture sufficient information GNSS signals received from both GNSS1 and GNSS2 without introducing significant noise outside the frequency band of components 402 and 404. Additionally, BPFs 408-1 and 410-1 may be selected to be narrow enough to enable ADCs 412-1 and 414-1 to sample at a given sampling rate (e.g., at approximately the Nyquist rate) without significant distortion.

[0062] According to certain embodiments, the sampled in-phase and quadrature components provided by ADCs 412-1 and 414-1 may be further processed according to complex down-conversion and digital baseband 416, which may be used to generate in-phase and quadrature components and output pseudoranges derived from the GNSS signals. According to some embodiments, the output of complex down-conversion and digital baseband 416 may be more broadly referred to as a measurement, where a measurement may include a pseudorange or a pseudorange and carrier phase.

[0063] As described above, the signal processing architecture 400 can have many RF chains to be able to receive and process many GNSS signals. As previously described, each RF chain can receive and process one or more GNSS signals (e.g., in pairs). In some embodiments, the RF chain can receive and process a single GNSS signal, in which case a first RF chain similar to that represented by components 402-1 to 414-1 can be used, but it can be modified (e.g., the components can be tuned for the frequency of the single GNSS signal).

[0064] exist Figure 4 In the example provided in FIG. 4 , the components of the signal processing architecture 400 included in block 418 may be integrated into a single IC, while other components such as antenna 402, RF filter 404, and LNA 406 may be included in separate circuits. Even so, if the RF chain is not in use, the on-chip components of the RF chain (such as IF down-conversion and processing block 418) may be powered down, resulting in overall power savings. Thus, according to some embodiments, the GNSS receiver is capable of powering down at least a portion of the RF chain when not in use, including corresponding on-chip components within block 420 and / or components external to block 420. For example, if the GNSS receiver is using one or more GNSS signals received and processed by the first RF chain represented by components 402-1 through 414-1, but is not using any GNSS signals received and processed by the second RF chain represented by components 402-2 through 414-2, the GNSS receiver may keep components 402-1 through 414-1 powered on (e.g., operating the first RF chain to receive and process one or more GNSS signals used by the GNSS receiver) and power down or remove power from one or more of components 402-2 through 414-2.

[0065] Generally speaking, the more GNSS signals or bands a GNSS receiver uses to determine position / pseudorange, the more accurate the final position determination. However, as previously mentioned, this additional accuracy comes at the expense of additional power usage. With this in mind, embodiments provided herein utilize the ability of a GNSS receiver to power down individual RF chains to enable GNSS band selection based on application requirements specific to position determination.

[0066] As a specific example, Figure 3As shown, GPS L1 and L5 bands are spaced farther apart in frequency relative to other GNSS bands. Therefore, in an embodiment, a GNSS receiver typically utilizes different RF chains and circuits to receive and process GNSS signals on these bands separately, which can be combined at a digital level later. If two bands are used, this results in more power usage. That is, using L5 can increase the accuracy of the pseudorange output by the GNSS receiver, which in turn increases the accuracy of position determination. This is partly due to the use of two bands L1 and L5 that enable the GNSS receiver to determine and reduce / eliminate ionospheric errors. In addition, as previously described, a GNSS receiver can use a single RF chain to receive and process signals from L2 and L5 GPS bands. Therefore, using L2 and L5 bands (in addition to L1) may cost a relatively small amount of additional power compared to using L5 alone. According to some embodiments, if using L1 band alone is insufficient, the GNSS receiver may therefore use both L2 and L5 bands to increase accuracy. Even so, this accuracy may not be required in all cases. According to some embodiments, an accuracy indication may be provided to a GNSS receiver to enable the GNSS receiver to determine whether to use one or more additional frequency bands. The application processor may provide the indication. Figure 5 Provides an example of an exchange between an application processor and a GNSS receiver.

[0067] Figure 5 is a call flow diagram of an example of an exchange between an application processor 505 and a GNSS receiver 510, according to an embodiment, wherein the GNSS receiver performs accuracy-based band selection. As described elsewhere herein, the GNSS receiver may include circuitry (e.g., an integrated circuit (IC)) and / or software modules capable of receiving GNSS signals and determining pseudoranges and / or GNSS position fixes. Thus, the GNSS receiver may include a processor (e.g., an application processor with an integrated modem or GNSS module, or a dedicated processor in a discrete GNSS chipset (e.g., and ARM 7)). According to some embodiments, both the processor 505 and the GNSS receiver 510 may be integrated into a single mobile device. Communication between the processor 505 and the GNSS receiver 510 may be performed, for example, via an application programming interface (API) of the GNSS receiver 510. In Fig.10 An example of such a mobile device is provided in , which is described below.

[0068] The process may begin with the functionality shown at block 515, where the application processor receives a location request. The location request may be received from an application executed by the application processor 505, another device (e.g., another mobile device or a server via a wireless message), and / or through input from another component (e.g., of the mobile device), such as firmware, user input at a user interface (UI), etc.).

[0069] In addition, the application processor can determine the level of accuracy required for location determination. The level of accuracy can be application specific. For example, for a mobile device including a smart phone executing an Internet browser, a website of a retail chain can request a rough approximation (e.g., about tens of meters) of where the mobile device is located via an Internet browser to provide an indication of which stores are nearby. The Internet browser can pass the request to the application processor 505, which can then be used to determine that the required level of accuracy is relatively low. On the other hand, for a mobile device including a vehicle that performs a navigation or self-driving function that requires a relatively high level of accuracy (e.g., about five meters or less), the navigation or self-driving function can indicate this to the application processor 505, which can then be used to determine that the required level of accuracy is relatively high.

[0070] According to some embodiments, the application processor 505 may execute a positioning engine capable of determining the location of the mobile device based at least in part on the pseudoranges output by the GNSS receiver 510. Optionally, the positioning engine may determine the location of the mobile device based on one or more additional positioning sources, such as ground RF positioning systems (e.g., cellular-based positioning, WiFi-based positioning, UWB-based positioning, etc.), mobile sensors (e.g., accelerometers, gyroscopes, magnetometers, etc.), device-specific systems (e.g., for vehicles, this may include speedometers, odometers, radars, lidars, etc.), and historical movement / positioning information of the mobile device. When determining the required accuracy from the GNSS receiver 510, the application processor 505 may take into account the positioning accuracy of these additional positioning sources. For example, if the application processor 505 is able to determine the relatively accurate location of the mobile device using the positioning engine and the additional positioning sources, accurate GNSS position fix information from the GNSS receiver 510 may not be required. On the other hand, if an accurate location is required and the positioning engine is unable to provide an accurate location of the mobile device from the additional positioning sources, accurate GNSS position fix information from the GNSS receiver 510 may be required.

[0071] The application processor 505 may then send an initial GNSS position fix information request to the GNSS receiver 510, as indicated at arrow 520, wherein the determined level of accuracy is provided as an accuracy requirement. Here, "GNSS position fix information" includes a request for a GNSS position fix from a GNSS receiver (and / or a device into which a GNSS receiver may be integrated) and / or pseudorange information from which a GNSS position fix may be obtained. The type of GNSS position fix information requested may vary based on the application processor's ability to utilize the GNSS position fix and / or pseudorange information (e.g., when the information is fused with other positioning information).

[0072] According to some embodiments, the accuracy requirement may be provided in the form of an error estimate. For example, if a position fix and / or pseudorange with an accuracy of 5 m or less is desired from the GNSS receiver 510, the application processor 505 may include in the initial GNSS position fix information request an indication that the initial GNSS position fix and / or pseudorange will have an error estimate of no greater than 5 m. The initial GNSS position fix information request may include, for example, a request for non-periodic position fix information, on-demand position fix information, or a request for position fix information at a future time. (The initial GNSS position fix information may also include periodic position fix information, however, the following description of the position fix information is not provided herein.) Figure 8 Provides procedures specific to periodic location fixes).

[0073] According to some embodiments, the accuracy requirement can be provided by the application processor 505 in one of three ways. The first type of accuracy requirement includes a "maximum accuracy" requirement. In this case, the application processor 505 basically requests the GNSS receiver 510 to provide a GNSS position fix and / or pseudorange with the highest accuracy that the GNSS receiver 510 can provide. For example, this may be the case when positioning from other positioning sources is unreliable and / or a specific application executed by the application processor 505 requires high-precision position determination. In such cases, if possible, the GNSS receiver 510 can (for example, in addition to using multiple GNSS bands) perform additional techniques to obtain a high-precision GNSS-based position fix and / or pseudorange. This can include, for example, using techniques such as DGNSS, RTK, PPP, etc. or a combination thereof.

[0074] The second type of accuracy requirement includes an accuracy requirement without a minimum accuracy. This type of accuracy requirement may be used by the application processor 505 if only a rough approximation of the location of the mobile device is needed. Again, this may be useful in situations where an application may only require an indication of the geographic area in which the mobile device is located, for example, to provide information relative to the geographic area to a user of the mobile device. In such cases, as described in more detail below, the GNSS receiver 510 may simply use a single frequency band or a minimum number of frequency bands to determine the GNSS position fix / pseudorange.

[0075] The third type of accuracy requirement may include a specified accuracy. As described above, this may include a maximum value for an error estimate of the GNSS position fix information. According to some embodiments, the specified accuracy may be adaptive based on the accuracy requirement of the application processor 505, the accuracy of the position determination provided by the positioning engine executed by the application processor 505 (e.g., which may be based on the accuracy obtained from other positioning sources), the accuracy of the most recent GNSS position fix, and / or other factors.

[0076] The GNSS receiver 510 may respond to the GNSS position fix information request by performing the functions indicated at block 525, which includes determining a GNSS frequency band to be used for a GNSS position fix. This determination may be based in part on the accuracy requirement of the GNSS position fix information request as well as other factors, such as whether a recent GNSS position fix / pseudorange determination has been made (e.g., within a threshold amount of time and / or within a threshold amount of detected movement). Furthermore, as described elsewhere herein, this determination may involve an iterative process to satisfy the accuracy requirement. Figure 6-Figure 8 Additional details are provided regarding how the GNSS receiver 510 may determine which frequency bands to use for GNSS position fix / pseudorange determination.

[0077] At block 530, the GNSS receiver 510 may then obtain GNSS position fix information and provide the GNSS position fix information and error estimates to the application processor 505, as indicated at arrow 535. As previously indicated, the GNSS receiver 510 may be configured to provide the GNSS position fix information and error estimates to the application processor 505, as indicated at arrow 535. Figure 4 GNSS signals (of the GNSS frequency band selected at block 525) are received and processed in the manner described to determine GNSS position fix information. As previously described, the GNSS position fix information may include the GNSS position fix itself and / or pseudoranges of satellites from which the GNSS signals are received. Optionally, the GNSS position fix information may also include carrier phase. In some embodiments, the GNSS receiver 510 may indicate to the application processor 505 (e.g., when providing GNSS position fix information) whether the GNSS position fix information (e.g., GNSS position fix and / or pseudorange) meets the accuracy requirements of the initial GNSS position fix information request.

[0078] As indicated at block 540, the application processor may then determine a location based at least in part on the GNSS position fix information. As described above, this may include using a positioning engine to determine the location of the mobile device. In some embodiments, the positioning engine may use other information from additional positioning sources, in which case the positioning engine may "fuse" the data to determine the final location of the mobile device.

[0079] As previously described, the application processor 505 may perform adaptive positioning. In this case, the application processor 505 may perform the functions indicated at box 545 and arrow 550, where the application processor determines whether the accuracy of the determined position is sufficient and sends a subsequent GNSS position fix information request with another accuracy requirement, as shown by arrow 550. For example, if the application processor 505 determines at box 545 that the accuracy is insufficient, it may include an accuracy requirement in the subsequent GNSS position fix information (of arrow 550) that is higher than the accuracy requirement of the initial GNSS position fix information (of arrow 520), and / or an indication that the GNSS position fix information provided at arrow 535 does not meet the accuracy requirement. Alternatively, if the accuracy is insufficient (e.g., in the case of requesting maximum accuracy but still not sufficient to meet the accuracy requirement), the application processor may no longer request anything (e.g., under the assumption that the GNSS receiver is not able to provide sufficiently accurate GNSS position fix information - at least currently). On the other hand, if the application processor 505 determines at block 545 that the accuracy is greater than the required accuracy (e.g., exceeds a threshold of the required accuracy requirement), it may include an accuracy requirement in a subsequent GNSS position fix (of arrow 550) that is lower than the accuracy requirement of the initial GNSS position fix (of arrow 520). The GNSS receiver 510 may respond to the subsequent GNSS position fix in a manner similar to the initial GNSS position fix, and may repeat the Figure 5 Additional GNSS position requests may be made, for example, until the application processor 505 no longer requires a position determination for the mobile device.

[0080] Figure 6-Figure 8 is a flow chart illustrating a process that a GNSS receiver may perform to determine which GNSS frequency bands to use for determining GNSS position fix information. Figure 5 In the process shown in FIG. , for example, the GNSS receiver 510 may perform Figure 6-Figure 8 One of the processes shown at box 525 in .

[0081] Figure 6is a flow chart of a first process 600 that a GNSS receiver may perform to determine which GNSS frequency bands to use for determining GNSS position fix information according to an embodiment. Figure 6 The functional components shown in FIG. 1 may include processing and / or other logic circuitry that may be integrated with GNSS signal receiving and processing circuitry (e.g., Figure 4 The GNSS signal processing architecture 400 is communicatively coupled to the GNSS receiver IC / chip, module, package or subassembly, or a combination thereof, and is also capable of switching the RF chain on or off as previously described, depending on which GNSS frequency bands are selected to determine GNSS position fix information. Such processing / logic circuitry, along with the GNSS signal reception and processing circuitry, may be included in a single GNSS receiver IC / chip, module, package or subassembly, or a combination thereof, which may be incorporated into a processor that also includes an application processor (e.g., Figure 5 It can be noted that, unlike other appendixes provided herein, Figure 1 Sample, Figure 6 Alternative embodiments may alter and / or rearrange the functionality of the first process 600 to provide similar emotion functionality.

[0082] Process 600 may include a series of checks, as shown in boxes 610, 615 and 620 (which may be performed in a different order in alternative embodiments), which are used to determine the type of accuracy requirement included in the GNSS position location information request received from the application processor, thereby enabling the GNSS receiver to respond accordingly using process 600.

[0083] At box 610, a first check includes determining whether maximum accuracy has been requested by the application processor. As previously described, an accuracy requirement including a maximum accuracy request by the application processor can cause the GNSS receiver to provide the most accurate GNSS position fix information possible. Therefore, if the accuracy requirement includes a maximum accuracy request, process 600 can then proceed to the function at box 625, where a baseline GNSS band and one or more additional GNSS bands are used. Here, a "baseline" GNSS band can include a GNSS band determined by the GNSS receiver for all GNSS position fix information. In the example previously described, for example, the baseline GNSS band can include GPS L1. In this case, the additional bands can include the use of GNSS bands L5, L2, or both (if available).

[0084] If the accuracy requirement does not include a maximum accuracy request, process 600 may perform a function at block 615 where it is determined whether the accuracy requirement includes a minimum accuracy. If not, the GNSS receiver can use a baseline GNSS frequency band, as shown at block 630. In many GPS applications, this may include GPS L1, given that use of GPS L1 is most common among manufacturers and may provide high accuracy for a single frequency band. That is, alternative embodiments may use other frequency bands as the baseline frequency band for GNSS position fix information determination.

[0085] If there is a minimum accuracy requirement, process 600 may proceed to functionality at block 620 where a determination is made as to whether there has been a recent GNSS position fix (e.g., a recent GNSS position fix and / or a determination of a GNSS pseudorange). This determination is made because the recent GNSS position fix may be used as a reference point for how accurate the position fix information may be using one or more GNSS bands, as described in more detail below with respect to the functionality at block 640. As previously indicated, GNSS position fix may be determined as “recent” if the GNSS position fix has been determined within a threshold amount of time and / or if the mobile device has moved less than a threshold amount of distance since the previous GNSS position fix determination. For example, a GNSS position fix determination that is 10 seconds old may still be relevant to a stationary or slow mobile device, but it may not be relevant to a device in a vehicle moving at highway speeds.

[0086] If the most recent GNSS positioning information is not available, process 600 may move to block 635, where the GNSS receiver uses one or more default frequency bands to determine the requested GNSS positioning positioning information. Here, the default frequency band may include the baseline GNSS frequency band used to provide relatively low-precision positioning information at block 630, the GNSS frequency band used to provide relatively high-precision positioning information at block 625, or something in between (e.g., if three frequency bands are used at block 625 and a single frequency band is used at block 630, two frequency bands may be used at block 635).

[0087] The default frequency bands at block 635 may vary depending on the desired functionality. For embodiments where power savings are preferred over accuracy, the default frequency band(s) used at block 635 may include only the baseline frequency band used at block 630. On the other hand, for embodiments where accuracy is preferred over power savings, the default frequency bands used at block 635 may include the baseline and additional frequency bands used at block 625. Alternatively, the balancing method may include a subset of the baseline, and the additional frequency band(s) may be used where the subset includes more than the baseline frequency band.

[0088] In addition, according to some embodiments, (multiple) default frequency bands may be determined based on input from an application processor. For example, the application processor may send a command to the GNSS receiver to operate in a power saving mode. When operating in the power saving mode, the GNSS receiver may use only the baseline frequency band as the default frequency band at box 635. Additionally or alternatively, the application processor may send a command to the GNSS receiver to operate in a high precision mode. When operating in the high precision mode, the GNSS receiver may use the baseline and (multiple) additional frequency bands as the default frequency bands at box 635. In addition, according to some embodiments, the application processor may utilize machine learning to determine the relationship between accuracy and power saving (e.g., in terms of results from power saving and / or high precision modes, as well as other factors such as mobile device movement, recent location fix information determination, location, etc.).

[0089] According to some embodiments, the power saving mode may include occasionally using one or more additional GNSS bands to obtain error corrections for single-band GNSS determinations. For example, in addition to the baseline GNSS band, the GNSS receiver may occasionally use the additional GNSS band to obtain ionospheric and / or tropospheric errors. This error may remain valid for a period of time (the length of which may depend on the accuracy requirements of the position fix), during which the GNSS receiver may perform single-band position information determination using the baseline GNSS band. Due to the error correction based on the ionospheric and / or tropospheric errors, the accuracy of such single-band position fix information determination may be increased. After the validity of the ionospheric and / or tropospheric errors disappears, the GNSS receiver may again use one or more additional GNSS bands to obtain new ionospheric and / or tropospheric errors. Therefore, according to some embodiments, process 600 may include determining whether the ionospheric and / or tropospheric errors are still valid before determining the (multiple) default bands at box 635.

[0090] If the most recent GNSS positioning information is determined to be available, process 600 can proceed to the function at box 640, where the most recent GNSS positioning information can be used to determine the (multiple) GNSS bands to be used to meet the accuracy requirement. Because the accuracy of using the baseline GNSS band may change over time (e.g., based on signal quality, the number of visible satellites, etc.), there may be situations where using only the GNSS baseline band may be sufficient to meet the accuracy requirement at one point in time but insufficient to meet the same accuracy requirement at another point in time. However, these changes can be gradual, so the most recent GNSS positioning information using the baseline band and one or more additional bands can be used as a data point to determine whether the accuracy requirement can be met. For example, if the most recent GNSS positioning using only the baseline GNSS band produces an error estimate that will meet the subsequently received accuracy requirement, the GNSS receiver can determine to use only the baseline GNSS band given the possibility that it will produce an accuracy similar to the most recent GNSS positioning. On the other hand, if the most recent GNSS positioning using only the baseline GNSS band results in an accuracy lower than the subsequently received accuracy requirement, the GNSS receiver can choose to use one or more additional GNSS bands to meet the accuracy requirement. In addition to the baseline GNSS band, the most recent position fix using one or more GNSS bands may similarly be utilized.At block 645 , process 600 includes using the GNSS band(s) selected at block 640 .

[0091] Figure 6 The process 600 shown in FIG. 1 shows an example process that a GNSS receiver may perform when providing GNSS position information in a single instance. However, as previously described, the process may be adaptive. That is, based on the accuracy of the initial position fix information, subsequent position fix information determinations may be adapted accordingly to meet the accuracy requirements. The adaptation may be performed at the GNSS receiver and / or at the application processor.

[0092] Figure 7 FIG. 7 is a second process 700 that a GNSS receiver according to an embodiment may perform to determine which GNSS frequency bands to use to determine GNSS position location information. Here, process 700 is Figure 6 The functions at blocks 710-745 may correspond to the previously described Figure 6735 or 745, the GNSS receiver may perform an initial position fix information determination using the selected (multiple) GNSS bands, and then determine whether to increase the accuracy using the functions at blocks 750 to 760. At block 750, a determination is made as to whether the baseline GNSS band and (multiple) additional GNSS bands are used, indicating whether additional accuracy is available. If they are used, the additional accuracy is not available, and the GNSS receiver may return the position fix information. However, if not, the GNSS receiver may determine whether the GNSS position fix information meets the accuracy requirement, as indicated at block 755. If yes, the GNSS receiver may return the GNSS position fix information. However, if not, process 700 may proceed to block 760, in which case the baseline GNSS band and the additional one or more GNSS bands may be used to provide more accurate position fix information, which may then be provided by the GNSS receiver to the application processor. Therefore, the GNSS receiver can perform a preliminary check before providing the GNSS position information to determine whether the GNSS position information meets the accuracy requirements. If not, the GNSS receiver can increase the number of GNSS frequency bands used to provide more accurate position information and then provide the application processor with more accurate GNSS position information.

[0093] However, it may be noted that additional variations may be made to process 700. For example, if the GNSS receiver is capable of using three or more GNSS frequency bands, process 700 may be modified to accommodate an incremental increase or decrease in the number of frequency bands to accommodate an incremental increase or decrease in accuracy. Alternative embodiments may include additional or alternative functionality for increasing or decreasing accuracy based on a preliminary accuracy check of the GNSS position fix information by the GNSS receiver prior to providing the GNSS position fix information to the application processor.

[0094] Figure 8 8 is a flow chart illustrating a third process 800 that a GNSS receiver may perform to determine which GNSS frequency bands to use when determining GNSS position fix information according to an embodiment. The process 800 may be used in situations where an application processor requests a GNSS processor to provide position fix information at one or more times after providing initial GNSS position fix information. Such a request may be included in an initial GNSS position fix information request (e.g., as Figure 5520) and may indicate the number of times the GNSS location information will be provided, as well as the timing (e.g., periodicity) for providing the GNSS location information. In situations where continuous positioning of the mobile device within a time window may be desired, the application processor may provide such a request. Similar to Figure 7 In process 700 , providing GNSS position fix information at multiple times may enable a GNSS processor to perform adaptive selection of a GNSS frequency band based on previous position fix information.

[0095] Process 800 may begin at the functionality of block 805, where the GNSS receiver determines whether the number of times N that position fix information will be provided is greater than one for a position fix information request received by the application processor. If not, the GNSS receiver may perform a single position fix process, as indicated at block 810. In this case, the single position fix information process may include a process similar to Figure 6 Course 600 or Figure 7 The process of process 700 of , wherein GNSS position fix information is provided to the application processor a single time after the GNSS receiver determines which GNSS frequency bands to use. (Although the GNSS receiver may determine GNSS position fix information more than once in process 700, it may ultimately provide a GNSS position fix (e.g., to the application processor) a single time, and thus may be referred to as a "single position fix information process" in this context). If N is greater than one, the process may proceed to the functionality at block 815, where the GNSS receiver determines initial GNSS position fix information using the baseline GNSS frequency band and one or more additional GNSS frequency bands. The initial GNSS position fix information may then be provided to the application processor, as shown in block 820. This reduces the remaining number of times N to provide position fix information by one.

[0096] The remainder of process 800 may be informed by whether the initial GNSS position fix information meets the required accuracy. At box 825, a determination is made whether the accuracy is met. This may be accomplished by determining at the GNSS receiver whether the error estimate of the GNSS position fix information meets the accuracy requirement (as described above). Additionally or alternatively, the application processor may provide feedback on whether the accuracy is satisfactory after using the position fix information. That is, after making a final position determination (e.g., using a positioning engine to fuse multiple positioning sources), the application processor may send a message to the GNSS receiver to indicate whether the accuracy is satisfactory or insufficient. If the accuracy is satisfactory, the application processor may indicate whether a lower accuracy may be allowed.

[0097] If the accuracy is not met, process 800 may proceed to functionality at block 830 where the GNSS receiver uses the baseline and one or more additional GNSS bands to provide the remaining N position fixes.

[0098] If the accuracy is met, the GNSS receiver may attempt to determine a second GNSS position fix using only the baseline GNSS frequency band to see if the GNSS position fix using only the baseline GNSS frequency band provides sufficient accuracy, as indicated at block 835. This may ultimately allow the GNSS receiver to determine whether it can meet the accuracy requirements using fewer frequency bands (and lower power) to provide the remaining position fix information.

[0099] At box 840, a determination is made as to whether the accuracy of the second GNSS position fix information is met. Here, the GNSS position fix information is based on the baseline frequency band used at box 835. Similar to box 825, the determination at box 840 can be performed by the GNSS receiver and / or the application processor. In some embodiments, the GNSS receiver can make a determination without providing the second GNSS position fix information. In some embodiments, the GNSS receiver can provide the second GNSS position fix information to the application processor, which can then provide feedback to the GNSS receiver as to whether the accuracy is satisfactory or insufficient. (If the GNSS receiver provides the second GNSS position fix information to the application processor, the value of N can be decremented by one again). In either case, if the accuracy is insufficient, the GNSS receiver can then perform the function of using the baseline and one or more additional GNSS frequency bands at box 830 to provide the remaining N position fix information. If the accuracy is met, the GNSS receiver can perform the function at box 845, where the baseline frequency band is used to provide the remaining N position fix information.

[0100] Depending on the desired functionality, alternative embodiments may employ any number of variations to process 800. For example, rather than starting with a baseline and one or more additional frequency bands at block 815, process 800 may start with a baseline frequency band and, if necessary, increase the number of frequency bands based on whether accuracy is met. Additionally or alternatively, according to some embodiments, rather than using a set number of frequency bands at blocks 830 or 845 to provide a remaining number of position fixes, the GNSS receiver may re-evaluate whether an increased or decreased number of GNSS frequency bands should be used after each position fix is ​​provided.

[0101] It can be noted that, as regards Figure 7 As mentioned, it can be expanded Figure 8The functionality shown can accommodate GNSS receivers that use any number of GNSS bands. That is, instead of two options ((i) use only the baseline GNSS band, or (ii) use the baseline GNSS band with one or more additional GNSS bands), there may be three or more options of GNSS bands that the GNSS can use (e.g., based on the GNSS receiver's ability to turn on / off different RF chains). Such an embodiment may be implemented similar to Figure 8 In the process 800 , the number of used GNSS frequency bands is increased or decreased based on whether the GNSS position positioning information meets the accuracy requirement.

[0102] It may also be noted that, according to some embodiments, the application processor may adjust the accuracy requirements of subsequent GNSS position location information based on whether the accuracy is met. That is, if the GNSS receiver is unable to provide GNSS position location information that meets the accuracy requirements requested by the application processor, the application processor may be able to reduce the accuracy requirements. For example, the application processor may indicate to an application executed by the application processor that high accuracy is not currently feasible, in which case the application requesting the positioning of the mobile device may reduce its accuracy expectations (e.g., operate in a reduced accuracy mode), which in turn may allow the application processor to reduce the accuracy requirements in subsequent GNSS position location information requests. The application processor may continue to include the reduced accuracy requirements in subsequent GNSS position location information requests for a predetermined period of time until it is determined that the mobile device has moved a threshold distance, and / or a similar event occurs in which conditions may have changed sufficiently to allow higher accuracy GNSS position location information. During this time, the application processor may seek to obtain positioning information from other positioning sources (e.g., cellular-based positioning, motion sensors, etc.) to achieve a position determination with relatively high accuracy, regardless of the reduced accuracy GNSS position location information from the GNSS receiver.

[0103] Fig. 9 is a flow chart of a method 900 for providing GNSS position location information according to an embodiment. Fig. 9 The components of the functions shown in one or more of the blocks shown in the figure may be performed by hardware and / or software components of a device including a GNSS receiver. In some embodiments, the functions may be performed by a GNSS receiver, an application processor in communication with the GNSS receiver (e.g., executing a positioning engine), a separate electrical component of the device, or any combination thereof. Specifically, in some embodiments, the functions may be performed by a GNSS receiver. As described above, the application processor and the GNSS receiver may be integrated into a mobile device. Example components of a mobile device are shown in FIG. Fig.10 , which is described in more detail below.

[0104] At block 910, the functionality includes receiving a request for GNSS position fix information, wherein the request includes an accuracy requirement. Figure 5 As discussed, a request for a GNSS position fix may be received from an application processor (e.g., by a GNSS receiver). The request may be triggered, for example, by an application executed by the application processor, a positioning request from a remote device, user input, or any combination thereof. Means for performing the functions at block 910 may include bus 1005, GNSS receiver 1080, and / or other components of mobile device 1000, such as Fig.10 As shown in and described below.

[0105] At box 920, the function includes determining a set of GNSS frequency bands to be used for GNSS position fix from a plurality of GNSS frequency bands available to the GNSS receiver based at least in part on the accuracy requirement. According to some embodiments, the determination may include selecting the set of GNSS frequency bands from a plurality of GNSS frequency bands available to the GNSS receiver in a manner that satisfies the accuracy requirement. As indicated elsewhere herein, the GNSS receiver is capable of performing GNSS position fix using a plurality of frequency bands, including frequency bands from GNSS constellations such as GPS, BDS, GAL, GLO, etc. Each of these constellations may have a plurality of frequency bands that the GNSS receiver may utilize to determine a GNSS position fix. At a given time, such as when the GNSS receiver receives a GNSS position fix request, the GNSS receiver is capable of receiving signals transmitted via various GNSS frequency bands from various satellites visible to the GNSS receiver (i.e., satellites transmitting GNSS signals that can be received and used by the GNSS receiver). In addition, as previously described, the GNSS receiver is capable of turning on / off RF chains that are capable of receiving GNSS signals via multiple GNSS bands, thereby enabling unused RF chains corresponding to unselected GNSS bands to be powered off, ultimately saving power (e.g., relative to using all GNSS as bands). Therefore, according to some embodiments of method 900, the GNSS receiver has multiple receiver chains, each receiver chain is used to receive one or more GNSS bands among the multiple GNSS bands, and each receiver chain is selectively activated or deactivated based on a set of GNSS bands so that the receiver can receive the set of GNSS bands.

[0106] like Figure 6 and Figure 7As shown, different types of accuracy requirements may cause different GNSS band selections by the GNSS receiver. For example, if the accuracy requirement includes an indication requesting maximum accuracy, the GNSS band set may include two or more (e.g., all) GNSS bands of a plurality of GNSS bands available to the GNSS receiver. For example, if the accuracy requirement includes an indication that minimum accuracy is not required, the GNSS band set may include a single GNSS band. As described above, a baseline GNSS band may be selected for all GNSS position fixes performed by the GNSS receiver (e.g., if available). If the GNSS receiver determines that an additional GNSS may need to be used as a band, the GNSS receiver may then determine one or more bands to be used in addition to the baseline GNSS band. Therefore, according to some embodiments of method 900, the GNSS band set includes at least a baseline GNSS band. According to some embodiments, the baseline band includes a GPS L1 band. Additionally or alternatively, the GNSS band set includes one or more additional GNSS bands. One or more additional GNSS bands may include, for example, a GPS L5 band, a GPS L2 band, or both. For unselected GNSS bands, the GNSS receiver may power down or shut down corresponding circuits (eg, RF chains) to save power.

[0107] The means for performing the functions at block 920 may include the GNSS receiver 1080 and / or other components of the mobile device 1000, such as Fig.10 Additionally or alternatively, the means for performing the functions at block 920 may include one or more components of a GNSS receiver, such as Figure 4 Components shown in .

[0108] At block 930, the functions include obtaining a GNSS position fix based at least in part on GNSS signals received via the set of GNSS frequency bands (e.g., using a GNSS receiver). As previously described, this may include using one or more antennas and circuits to receive and process incoming GNSS signals corresponding to each frequency band in the set of GNSS frequency bands. Figure 7As indicated, for example, the GNSS receiver may make a preliminary or initial GNSS position fix to determine whether the set of GNSS bands results in a GNSS position fix that meets the accuracy requirement. This may include testing whether a single baseline GNSS band is sufficient, and if not, increasing the number of GNSS used for the GNSS position fix. Thus, for some embodiments of method 900, determining which GNSS bands to use to determine GNSS position fix information includes obtaining an initial GNSS position fix using a single GNSS band, determining that the accuracy of the initial GNSS position fix is ​​insufficient to meet the accuracy requirement, and in response to determining that the accuracy of the initial GNSS position fix is ​​insufficient to meet the accuracy requirement, determining two or more GNSS bands as the set of bands used to determine the GNSS position fix.

[0109] Additionally or alternatively, GNSS position information may be determined and provided multiple times (eg, periodically), such as Figure 8 In this case, the request for GNSS position fix information may include multiple requests for GNSS position fix information, and determining the set of GNSS frequency bands for the GNSS position fix information may include selecting two or more GNSS frequency bands from a plurality of GNSS frequency bands available to a GNSS receiver for the first GNSS position fix information. In addition, determining the GNSS position fix information may include determining the first GNSS position fix information, and providing the GNSS position fix information may include providing the first GNSS position fix information. For example, the first GNSS position fix information may be Figure 8 The initial GNSS position positioning information mentioned in process 800. According to some embodiments, method 900 may also include: in response to determining that the first GNSS position positioning information meets the accuracy requirement for the first time in the multiple times, using a single GNSS frequency band to obtain second GNSS position positioning information for the second time in the multiple times. According to some embodiments, method 900 may also include: in response to determining that the second GNSS position positioning information meets the accuracy requirement, using a single GNSS frequency band to obtain third GNSS position positioning information for the third time in the multiple times. In response to determining that the second GNSS position positioning information does not meet the accuracy requirement, the method may include: using two or more GNSS frequency bands used to determine the first GNSS position positioning information to obtain third GNSS position positioning information for the third time in the multiple times.

[0110] Means for performing the functions at block 930 may include bus 1005, GNSS receiver 1080, GNSS antenna 1082, and / or other components of mobile device 1000, such as Fig.10Additionally or alternatively, the means for performing the functions at block 930 may include one or more components of a GNSS receiver, such as Figure 4 Components shown in .

[0111] At block 940, the function includes providing a GNSS position fix, wherein the GNSS position fix information includes a GNSS position fix, pseudorange information, or both. Again, the function may be performed, for example, with a GNSS receiver. As described above, this may be accomplished in an exchange between a GNSS receiver and an application processor. Specifically, according to some embodiments of method 900, receiving a request for a GNSS position fix may include receiving a request for a GNSS position fix from an application processor, and providing a GNSS position fix may include providing the GNSS position fix to the application processor.

[0112] Means for performing the functions at block 940 may include bus 1005, GNSS receiver 1080, and / or other components of mobile device 1000, such as Fig.10 As shown in and described below.

[0113] Fig.10 is a block diagram of an embodiment of a mobile device 1000 that can be used as described above (e.g., with Figure 1-Figure 9 For example, the mobile device 1000 may correspond to Figure 1 The mobile device 105 may include a GNSS receiver and an application processor as described herein. Fig.10 It is intended only to provide a generalized description of the various components, any or all of which may be utilized as appropriate. In other words, because mobile devices may vary widely in functionality, they may include only Fig.10 It can be noted that in some cases, Fig.10 The components shown may be localized to a single physical device and / or distributed among various networked devices that may be located at different physical locations.

[0114] The mobile device 1000 is shown as including hardware elements that may be electrically coupled via a bus 1005 (or may communicate in other ways as appropriate). The hardware elements may include processor(s) 1010, which may include (but are not limited to) one or more general purpose processors (e.g., application processors), one or more special purpose processors (such as digital signal processor (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), etc.), and / or other processing structures or components. Processor(s) 1010 may include one or more processing units, which may be housed in a single integrated circuit (IC) or multiple ICs. Processor 1010 may also include an application processor 1012, which may execute a positioning engine 1014, as described in the above embodiments. As described above, the positioning engine 1014 may determine the location of the mobile device 1000 using GNSS position fixes from the GNSS receiver 1080 and / or information from other positioning sources (e.g., sensor 1040). As shown in FIG. Fig.10 As shown, some embodiments may have a separate DSP 1020, depending on the desired functionality. Position determination and / or other determinations based on wireless communications may be provided in the processor(s) 1010 and / or the wireless communication interface 1030 (discussed below). The mobile device 1000 may also include one or more input devices 1070, which may include (but are not limited to) one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, etc.; and one or more output devices 1015, which may include (but are not limited to) one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, etc.

[0115] The mobile device 1000 may also include a wireless communication interface 1030, which may include (but is not limited to) a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (such as a Devices, IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX TMDevices, WAN devices and / or various cellular devices, etc.), etc., which can enable the mobile device 1000 to communicate with other devices as described in the above embodiments. The wireless communication interface 1030 can allow communication (e.g., sending and receiving) data and signaling with, for example, base stations, access points and / or other access node types and / or other network components, computer systems and / or any other electronic devices communicatively coupled to the wireless communication network. Communication can be performed via one or more wireless communication antennas 1032 that send and / or receive wireless signals 1034. According to some embodiments, (multiple) wireless communication antennas 1032 may include multiple discrete antennas, antenna arrays or any combination thereof. (Multiple) antennas 1032 are capable of using beams (e.g., Tx beams and Rx beams) to send and receive wireless signals. Beamforming can be performed using digital and / or analog beamforming techniques and corresponding digital and / or analog circuits. The wireless communication interface 1030 may include such circuits.

[0116] Depending on the desired functionality, the wireless communication interface 1030 may include separate receivers and transmitters, or any combination of transceivers, transmitters, and / or receivers to communicate with base stations and other terrestrial transceivers (such as wireless devices and access points). The mobile device 1000 can communicate with different data networks, which may include various network types. For example, a wireless wide area network (WWAN) may be a CDMA network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, a WiMAX (IEEE 802.16) network, and the like. A CDMA network may implement one or more RATs, such as CDMA. WCDMA, etc. CDMA Includes IS-95, IS-2000, and / or IS-856 standards. TDMA networks may implement GSM, Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. OFDMA networks may employ LTE, Advanced LTE, 5G NR, etc. 5G NR, LTE, Advanced LTE, GSM, and WCDMA are described in documents from 3GPP. CDMA Described in documents from a consortium named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE 802.11x network, and a wireless personal area network (WPAN) may be a Bluetooth network, IEEE 802.15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN, and / or WPAN.

[0117] The mobile device 1000 may also include sensor(s) 1040. The sensor(s) 1040 may include, but are not limited to, one or more inertial sensors and / or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), etc.), some of which may be used as a source of positioning data and / or for obtaining other location-related measurements and / or other information.

[0118] Embodiments of mobile device 1000 may also include a GNSS receiver 1080 capable of receiving signals 1084 from one or more GNSS satellites via one or more GNSS frequency bands using a device GNSS antenna 1082 . Fig.10 The GNSS receiver 1080 may correspond to the GNSS receiver described in the previous embodiment, including Figure 4 GNSS receiver 400. And therefore, Fig.10 The GNSS receiver 1080 may include Figure 4 Thus, the GNSS receiver 1080 may be used to use, for example, Figure 4 The signal processing architecture 400 and / or similar processing components of the GNSS receiver 1080 provide a GNSS position fix based on the received GNSS signal 1084. The GNSS receiver 1080 is capable of processing signals received via many GNSS bands / constellations. In some embodiments, the GNSS receiver 1080 may include front-end analog components for each GNSS band (or for a pair of GNSS bands with similar baseband frequencies), and digital circuits may be shared between multiple GNSS bands (e.g., Figure 4 1004). Additionally or alternatively, the digital circuitry may be separate for each GNSS frequency band. The GNSS receiver 1080 may communicate with other components of the mobile device 1000 (e.g., processor(s) 1010, including application processor 1012 and / or positioning engine 1014) via a data interface with bus 1005.

[0119] The GNSS receiver 1080 may extract the location of the mobile device 1000 from the GNSS satellites 110 of a GNSS system such as GPS, Galileo, GLONASS, Japan's Quasi-Zenith Satellite System (QZSS), India's IRNSS, China's BeiDou Navigation Satellite System (BDS), etc. using conventional techniques. In addition, the GNSS receiver 1080 may be used with various augmentation systems (e.g., satellite-based augmentation systems (SBAS)), which may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. By way of example and not limitation, the SBAS may include augmentation system(s) that provide integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-Function Satellite Augmentation System (MSAS), GPS-Assisted Geographic Augmentation Navigation or GPS and Geographic Augmentation Navigation System (GAGAN), etc. Thus, as used herein, 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.

[0120] It can be noted that although the GNSS receiver 1080 Fig.10 1010, DSP 1020, and / or a processor within the wireless communication interface 1030 (e.g., in a modem)). The GNSS receiver may also optionally include a GNSS positioning engine that may use the GNSS measurements from the measurement engine to determine the position (e.g., position fix) of the GNSS receiver using an extended Kalman filter (EKF), a weighted least squares (WLS), a shadow filter, a particle filter, and the like. The GNSS positioning engine may also be executed as part of a larger processing engine (e.g., a positioning engine 1014 executed by the application processor 1012).

[0121] The mobile device 1000 may also include and / or be in communication with memory 1060. The memory 1060 may include, but is not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices, such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including, but not limited to, various file systems, database structures, etc.

[0122] The memory 1060 of the mobile device 1000 may also include software elements ( Fig.10 1010), including an operating system, device drivers, executable libraries, and / or other code, such as one or more applications, which may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more programs described with respect to the functionality discussed above may be implemented as code and / or instructions executable by the mobile device 1000 (e.g., using (multiple) processors 1010). In some embodiments, such code and / or instructions may then be used to configure and / or adapt a general purpose computer (or other device) to perform one or more operations according to the described methods.

[0123] It will be apparent to those skilled in the art that substantial variations may be made depending on specific requirements. For example, custom hardware may also be used and / or specific elements may be implemented in hardware, software (including portable software, such as applets, etc.), or both. In addition, connections to other computing devices such as network input / output devices may be employed.

[0124] With reference to the accompanying drawings, the components that may include memory may include non-transitory machine-readable media. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any storage medium that participates in providing data that enables a machine to operate in a particular manner. In the embodiments provided above, various machine-readable media may involve providing instructions / codes to a processor and / or (multiple) other devices for execution. Additionally or alternatively, machine-readable media may be used to store and / or carry such instructions / codes. In many embodiments, computer-readable media are physical and / or tangible storage media. Such media may take many forms, including but not limited to non-volatile media and volatile media. Common forms of computer-readable media include, for example, magnetic and / or optical media, any other physical media with hole patterns, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or box, or any other medium from which a computer can read instructions and / or codes.

[0125] The methods, systems and devices discussed herein are examples. Various embodiments may appropriately omit, replace or add various processes or components. For example, 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 accompanying drawings provided herein may be embodied in hardware and / or software. In addition, technological developments, and therefore many elements are examples that do not limit the scope of the present disclosure to those specific examples.

[0126] It has proven convenient at times, primarily for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numerical values, numbers, and the like. It will be understood, however, that all of these or similar terms are associated with the appropriate physical quantities and are merely convenient labels. Unless otherwise specifically stated, as will be apparent from the above discussion, it will be understood that throughout this specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," "ascertaining," "identifying," "correlating," "measuring," "performing," and the like refer to the actions or processes of a specific apparatus, such as a special purpose computer or similar special purpose electronic computing device. Thus, in the context of this specification, a special purpose computer or similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within a memory, register, or other information storage device, transmission device, or display device of the special purpose computer or similar special purpose electronic computing device.

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

[0128] Several embodiments have been described, and various modifications, alternative configurations, and equivalents may be used without departing from the scope of the present disclosure. For example, the above elements may be merely components of a larger system, where other rules may take precedence over or otherwise modify the application of the various embodiments. In addition, multiple steps may be performed before, during, or after considering the above elements. Therefore, the above description does not limit the scope of the present disclosure.

[0129] In view of this description, embodiments may include different combinations of features. Implementation examples are described in the following numbered clauses:

[0130] Clause 1. A method for providing global navigation satellite system (GNSS) position fix information, the method comprising: receiving a request for GNSS position fix information, wherein the request includes an accuracy requirement; determining a set of GNSS frequency bands to be used for determining GNSS position fix information from a plurality of GNSS frequency bands available to a GNSS receiver based at least in part on the accuracy requirement; and determining the GNSS position fix information based at least in part on GNSS signals received via the set of GNSS frequency bands; and providing GNSS position fix information, wherein the GNSS position fix information includes GNSS position fix, pseudorange information, or both.

[0131] Clause 2. The method of clause 1, wherein: the accuracy requirement comprises an indication requesting maximum accuracy; and the set of GNSS frequency bands comprises two or more GNSS frequency bands of a plurality of GNSS frequency bands available to the GNSS receiver.

[0132] Clause 3. The method of clause 1, wherein the accuracy requirement comprises an indication that no minimum accuracy is required; and the set of GNSS frequency bands comprises a single GNSS frequency band.

[0133] Clause 4. The method of clause 1, wherein the accuracy requirement comprises a maximum allowable error estimate of the GNSS position location information.

[0134] Clause 5. A method according to any one of clauses 1 or 3-4, wherein determining a set of GNSS frequency bands to be used to determine GNSS position positioning information comprises: obtaining initial GNSS position positioning information using a single GNSS frequency band; determining that the accuracy of the initial GNSS position positioning information is insufficient to meet accuracy requirements; and in response to determining that the accuracy of the initial GNSS position positioning information is insufficient to meet accuracy requirements, determining two or more GNSS frequency bands as the GNSS frequency band set.

[0135] Clause 6. A method according to any one of clauses 1-5, wherein the request for GNSS position positioning information includes multiple requests for GNSS position positioning information; determining a set of GNSS frequency bands for GNSS position positioning information includes: determining two or more GNSS frequency bands for first GNSS position positioning information from multiple GNSS frequency bands available to the GNSS receiver; determining the GNSS position positioning information includes determining the first GNSS position positioning information; and providing the GNSS position positioning information includes providing the first GNSS position positioning information; wherein the method further includes: in response to determining that the first GNSS position positioning information meets the accuracy requirement for the first time in the multiple times, obtaining second GNSS position positioning information using a single GNSS frequency band for the second time in the multiple times.

[0136] Clause 7. A method according to any one of clauses 1-6, wherein the method further comprises: in response to determining that the second GNSS position positioning information meets the accuracy requirement, obtaining third GNSS position positioning information using a single GNSS frequency band for a third time in the multiple times.

[0137] Clause 8. A method according to any one of clauses 1-7, wherein the method further comprises: in response to determining that the second GNSS position positioning information does not meet the accuracy requirement, obtaining a third GNSS position positioning information using two or more GNSS frequency bands used to determine the first GNSS position positioning information for the third time in the multiple times.

[0138] Clause 9. The method of any one of clauses 1-8, wherein receiving the request for GNSS position location information comprises: receiving the request for GNSS position location information from an application processor; and providing the GNSS position location information comprises providing the GNSS position location information to the application processor.

[0139] Clause 10. The method of any one of clauses 1-9, wherein the set of GNSS frequency bands comprises at least a baseline GNSS frequency band.

[0140] Clause 11. The method of clause 10, wherein the baseline GNSS frequency band comprises a Global Positioning System (GPS) L1 frequency band.

[0141] Clause 12. The method of any of clauses 10-11, wherein the set of GNSS frequency bands comprises one or more additional GNSS frequency bands.

[0142] Clause 13. The method of clause 12, wherein the one or more additional GNSS frequency bands include a GPS L5 band, a GPS L2 band, or both.

[0143] Clause 14. The method of any of clauses 1-13, wherein determining a set of GNSS frequency bands to be used for determining GNSS position location information based at least in part on the accuracy requirement comprises selecting the set of GNSS frequency bands from a plurality of GNSS frequency bands available to a GNSS receiver.

[0144] Clause 15. The method of any of clauses 1-14, wherein the GNSS receiver determines a GNSS position fix information and provides the GNSS position fix information.

[0145] Clause 16. A method according to any one of clauses 1-15, wherein the GNSS receiver has multiple receiver chains, each receiver chain is used to receive one or more GNSS bands among a plurality of GNSS bands, and wherein each receiver chain is selectively activated or deactivated based on the GNSS band set so that the receiver can receive the GNSS band set.

[0146] Clause 17. A device for providing global navigation satellite system (GNSS) position information, the device comprising: a data communication interface; a memory; and one or more processors communicatively coupled to the data communication interface and the memory, wherein the one or more processors are configured to: receive a request for GNSS position information via the data communication interface, wherein the request includes an accuracy requirement; determine a set of GNSS frequency bands to be used for determining GNSS position information from a plurality of GNSS frequency bands available to a GNSS receiver based at least in part on the accuracy requirement; determine the GNSS position information based at least in part on GNSS signals received via the GNSS frequency band set; and provide the GNSS position information using the data communication interface, wherein the GNSS position information includes a GNSS position fix, pseudorange information, or both.

[0147] Clause 18. An apparatus according to clause 17, wherein, in order to determine a set of GNSS bands to be used based at least in part on an accuracy requirement, one or more processors are configured to include in the GNSS band set two or more GNSS bands from a plurality of GNSS bands available to the GNSS receiver in response to the accuracy requirement including a request for maximum accuracy.

[0148] Clause 19. An apparatus according to clause 17, wherein, in order to determine a set of GNSS bands to be used based at least in part on an accuracy requirement, one or more processors are configured to include in the GNSS band set a single GNSS band from a plurality of GNSS bands available to the GNSS receiver in response to the accuracy requirement including an indication that no minimum accuracy is required.

[0149] Clause 20. The apparatus of Clause 17, wherein the one or more processors are configured to determine the set of GNSS frequency bands to use based at least in part on a maximum allowable error estimate of the GNSS position fix information.

[0150] Clause 21. An apparatus according to any one of clauses 17 or 19-20, wherein, in order to determine a set of GNSS frequency bands for determining GNSS position positioning information, one or more processors are configured to: obtain initial GNSS position positioning information using a single GNSS frequency band; determine that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement; and in response to determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement, include two or more GNSS frequency bands in the frequency band set.

[0151] Clause 22. An apparatus according to any one of clauses 17-21, wherein, in order to receive a request for a GNSS position fix, one or more processors are configured to receive multiple requests for GNSS position fix information; in order to determine a set of GNSS frequency bands for GNSS position fix information, one or more processors are configured to determine two or more GNSS frequency bands for first GNSS position fix information from multiple GNSS frequency bands available to a GNSS receiver; in order to determine the GNSS position fix information, one or more processors are configured to determine the first GNSS position fix information; in order to provide GNSS position fix information, one or more processors are configured to provide the first GNSS position fix information; and the one or more processors are configured to obtain the second GNSS position fix information using a single GNSS frequency band the second time in response to determining that the first GNSS position fix information meets the accuracy requirement the first time in the multiple times.

[0152] Clause 23. An apparatus according to any one of clauses 17-22, wherein the one or more processors are further configured to obtain third GNSS position fix information using a single GNSS frequency band for a third time in the plurality of times in response to determining that the second GNSS position fix information meets the accuracy requirement.

[0153] Clause 24. An apparatus according to any one of clauses 17-23, wherein the one or more processors are further configured to obtain third GNSS position information using two or more GNSS frequency bands used to determine the first GNSS position information for the third time in a plurality of times in response to determining that the second GNSS position information does not meet accuracy requirements.

[0154] Clause 25. An apparatus according to any one of clauses 17-24, wherein, in order to receive a request for GNSS location information, one or more processors are configured to: receive a request for GNSS location information from an application processor; and the one or more processors are also configured to provide GNSS location information including providing the GNSS location information to the application processor.

[0155] Clause 26. The apparatus of any of clauses 17-25, wherein, to determine the set of GNSS frequency bands to use, the one or more processors are configured to include at least a baseline GNSS frequency band in the set of GNSS frequency bands.

[0156] Clause 27. The apparatus of clause 26, wherein the one or more processors are configured to select a Global Positioning System (GPS) L1 frequency band as the baseline GNSS frequency band.

[0157] Clause 28. The apparatus of any of Clauses 26-27, wherein, to determine the set of GNSS frequency bands to use, the one or more processors are configured to include one or more additional GNSS frequency bands in the set of GNSS frequency bands.

[0158] Clause 29. The apparatus of clause 28, wherein the one or more processors are configured to select the GPS L5 band, the GPS L2 band, or both as the one or more additional GNSS frequency bands.

[0159] Clause 30. The apparatus of any of clauses 17-29, wherein, to determine the set of GNSS frequency bands to use, the one or more processors are configured to select the set of GNSS frequency bands from a plurality of GNSS frequency bands available to a GNSS receiver.

[0160] Clause 31. The apparatus of any of clauses 17-30, wherein the apparatus comprises a GNSS receiver.

[0161] Clause 32. An apparatus according to any one of clauses 17-31, wherein the GNSS receiver has multiple receiver chains, each receiver chain is used to receive one or more GNSS bands among a plurality of GNSS bands, and wherein each receiver chain is selectively activated or deactivated based on the GNSS band set so that the receiver can receive the GNSS band set.

[0162] Clause 33. A device for providing global navigation satellite system (GNSS) position location information, the device comprising: a component for receiving a request for GNSS position location information at the device, wherein the request includes an accuracy requirement; a component for determining a set of GNSS frequency bands to be used for determining GNSS position location information from a plurality of GNSS frequency bands available to the device based at least in part on the accuracy requirement; a component for determining the GNSS position location information based at least in part on GNSS signals received via the set of GNSS frequency bands; and a component for providing GNSS position location information, wherein the GNSS position location information includes GNSS position location, pseudorange information, or both.

[0163] Clause 34. An apparatus according to clause 33, wherein the component for determining the set of GNSS frequency bands to be used includes: a component for including two or more GNSS frequency bands from a plurality of GNSS frequency bands available to the apparatus in the set of GNSS frequency bands in response to the accuracy requirement including an indication requesting maximum accuracy.

[0164] Clause 35. The apparatus of clause 33, wherein the means for determining the set of GNSS frequency bands to use comprises means for including a single GNSS frequency band as the set of GNSS frequency bands in response to the accuracy requirement including an indication that no minimum accuracy is required.

[0165] Clause 36. The apparatus of clause 33, wherein the means for determining the set of GNSS frequency bands to use comprises means for determining the set of GNSS frequency bands in response to an accuracy requirement comprising a maximum allowable error estimate of the GNSS position fix information.

[0166] Clause 37. An apparatus according to any one of clauses 33 or 35-36, wherein the component for determining a set of GNSS frequency bands to be used for determining GNSS position positioning information includes: a component for obtaining initial GNSS position positioning information using a single GNSS frequency band; a component for determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement; and a component for determining two or more GNSS frequency bands as a frequency band set in response to determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement.

[0167] Clause 38. An apparatus according to any one of clauses 33-37, wherein the component for receiving a request for GNSS position positioning information includes: a component for receiving multiple requests for GNSS position positioning information; the component for determining a set of GNSS frequency bands for GNSS position positioning information includes: a component for determining two or more GNSS frequency bands for first GNSS position positioning information from multiple GNSS frequency bands available to the apparatus; the component for determining GNSS position positioning information includes: a component for determining first GNSS position positioning information; and the component for providing GNSS position positioning information includes: a component for providing first GNSS position positioning information; wherein the apparatus also includes a component for obtaining second GNSS position positioning information using a single GNSS frequency band the second time in the multiple times in response to determining that the first GNSS position positioning information meets the accuracy requirement the first time in the multiple times.

[0168] Clause 39. An apparatus according to any one of clauses 33-38, wherein the apparatus further comprises: a component for obtaining a third GNSS position location information using a single GNSS frequency band for a third time in a plurality of times in response to determining that the second GNSS position location information meets the accuracy requirement.

[0169] Clause 40. An apparatus according to any one of clauses 33-39, wherein the apparatus further comprises: a component for obtaining a third GNSS position location information using two or more GNSS frequency bands used to determine the first GNSS position location information for the third time in a plurality of times in response to determining that the second GNSS position location information does not meet accuracy requirements.

[0170] Clause 41. An apparatus according to any one of clauses 33-40, wherein the component for receiving a request for GNSS position positioning information includes: a component for receiving a request for GNSS position positioning information from an application processor; and the component for providing GNSS position positioning information includes: a component for providing the GNSS position positioning information to the application processor.

[0171] Clause 42. The apparatus of any of clauses 33-41, wherein the means for determining a set of GNSS frequency bands comprises means for including at least a baseline GNSS frequency band in the set of GNSS frequency bands.

[0172] Clause 43. The apparatus of any of clauses 33-42, wherein the means for determining the set of GNSS frequency bands comprises means for including one or more additional GNSS frequency bands in the set of GNSS frequency bands.

[0173] Clause 44. An apparatus as described in any of clauses 33-43, wherein the means for determining a set of GNSS frequency bands to be used for determining GNSS position location information based at least in part on the accuracy requirement includes: means for selecting the set of GNSS frequency bands from a plurality of GNSS frequency bands available to the apparatus.

[0174] Clause 45. The apparatus of any of clauses 33-44, wherein the apparatus comprises a GNSS receiver.

[0175] Clause 46. A method according to any one of clauses 33-45, wherein the GNSS receiver has multiple receiver chains, each receiver chain is used to receive one or more GNSS bands among a plurality of GNSS bands, and wherein each receiver chain is selectively activated or deactivated based on the GNSS band set so that the receiver can receive the GNSS band set.

[0176] Clause 47. A non-transitory computer-readable medium storing instructions for providing global navigation satellite system (GNSS) position fix information, the instructions comprising code for: receiving a request for GNSS position fix information, wherein the request includes an accuracy requirement; determining a set of GNSS frequency bands to be used to determine the GNSS position fix information from a plurality of GNSS frequency bands available to a GNSS receiver based at least in part on the accuracy requirement; determining the GNSS position fix information based at least in part on GNSS signals received via the set of GNSS frequency bands; and providing the GNSS position fix information, wherein the GNSS position fix information includes a GNSS position fix, pseudorange information, or both.

[0177] Clause 48. A computer-readable medium according to clause 47, wherein the code for determining a set of GNSS frequency bands to be used to determine GNSS position location information includes code for the following operations: obtaining initial GNSS position location information using a single GNSS frequency band; determining that the accuracy of the initial GNSS position location information is insufficient to meet the accuracy requirement; and in response to determining that the accuracy of the initial GNSS frequency bands is insufficient to meet the accuracy requirement, determining two or more GNSS frequency bands as a frequency band set.

[0178] Clause 49. A computer-readable medium as described in any of Clauses 47-48, wherein the code for receiving a request for GNSS location information includes: code for receiving a request for GNSS location information from an application processor; and the code for providing GNSS location information includes: code for providing GNSS location information to the application processor.

Claims

1. A method for providing global navigation satellite system (GNSS) position positioning information, the method comprising: receiving a request for the GNSS position location information, wherein the request includes an accuracy requirement; determining, based at least in part on the accuracy requirement, a set of GNSS frequency bands from a plurality of GNSS frequency bands available to a GNSS receiver to be used for determining the GNSS position fix information; as well as determining the GNSS position location information based at least in part on GNSS signals received via the set of GNSS frequency bands; as well as The GNSS position fix information is provided, wherein the GNSS position fix information includes a GNSS position fix, pseudorange information, or both.

2. The method according to claim 1, wherein: The accuracy requirement includes an indication that maximum accuracy is requested; and The GNSS frequency band set includes two or more GNSS frequency bands among a plurality of GNSS frequency bands available to the GNSS receiver.

3. The method according to claim 1, wherein: The accuracy requirement includes an indication that no minimum accuracy is required; and The set of GNSS frequency bands includes a single GNSS frequency band.

4. The method according to claim 1, wherein: The accuracy requirement includes a maximum allowable error estimate of the GNSS position positioning information.

5. The method according to claim 1, wherein: Determining the set of GNSS frequency bands to be used for determining the GNSS position location information comprises: Using a single GNSS frequency band to obtain initial GNSS position information; Determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement; and In response to determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement, two or more GNSS frequency bands are determined as the GNSS frequency band set.

6. The method according to claim 1, wherein: The request for the GNSS position location information comprises multiple requests for GNSS position location information; Determining the set of GNSS frequency bands for the GNSS position fix information includes: determining two or more GNSS frequency bands for first GNSS position fix information from among the plurality of GNSS frequency bands available to the GNSS receiver; Determining the GNSS position location information includes determining the first GNSS position location information; and Providing the GNSS position information includes providing the first GNSS position information; The method further includes: in response to determining that the first GNSS position information meets the accuracy requirement for the first time among the multiple times, obtaining second GNSS position information using a single GNSS frequency band for the second time among the multiple times.

7. The method according to claim 6, wherein: The method further includes: in response to determining that the second GNSS position fix information meets the accuracy requirement, obtaining third GNSS position fix information using the single GNSS frequency band during a third of the multiple times.

8. The method according to claim 6, wherein: The method further includes: in response to determining that the second GNSS position fix information does not meet the accuracy requirement, obtaining a third GNSS position fix information using the two or more GNSS frequency bands used to determine the first GNSS position fix information at a third time of the multiple times.

9. The method according to claim 1, wherein: Receiving the request for the GNSS position location information comprises receiving the request for the GNSS position location information from an application processor; and Providing the GNSS position location information includes providing the GNSS position location information to the application processor.

10. The method according to claim 1, wherein: The set of GNSS frequency bands includes at least a baseline GNSS frequency band.

11. The method according to claim 10, wherein: The baseline GNSS frequency band includes a Global Positioning System (GPS) L1 frequency band.

12. The method according to claim 10, wherein: The set of GNSS frequency bands includes one or more additional GNSS frequency bands.

13. The method according to claim 12, wherein: The one or more additional GNSS frequency bands include the GPS L5 frequency band, the GPS L2 frequency band, or both.

14. The method according to claim 1, wherein: Determining the set of GNSS frequency bands to be used for determining the GNSS position fix information based at least in part on the accuracy requirement includes selecting the set of GNSS frequency bands from the plurality of GNSS frequency bands available to the GNSS receiver.

15. The method according to claim 1, wherein: The GNSS receiver determines the GNSS position fix information and provides the GNSS position fix information.

16. The method according to claim 1, wherein: The GNSS receiver has a plurality of receiver chains, each receiver chain being configured to receive one or more of the plurality of GNSS frequency bands, and wherein each receiver chain is selectively activated or deactivated based on the set of GNSS frequency bands so that the receiver is able to receive the set of GNSS frequency bands.

17. An apparatus for providing global navigation satellite system (GNSS) position positioning information, the apparatus comprising: Data communication interface; Memory; as well as one or more processors communicatively coupled to the data communications interface and the memory, wherein the one or more processors are configured to: receiving, via the data communication interface, a request for the GNSS position location information, wherein the request includes an accuracy requirement; determining, based at least in part on the accuracy requirement, a set of GNSS frequency bands from a plurality of GNSS frequency bands available to a GNSS receiver to be used for determining the GNSS position fix information; determining the GNSS position location information based at least in part on GNSS signals received via the set of GNSS frequency bands; and The GNSS position information is provided using the data communication interface, wherein the GNSS position information includes GNSS position information, pseudorange information, or both.

18. The device according to claim 17, wherein: To determine the set of GNSS frequency bands to use based at least in part on the accuracy requirement, the one or more processors are configured to, in response to the accuracy requirement comprising a request for maximum accuracy, include in the set of GNSS frequency bands two or more of the plurality of GNSS frequency bands available to the GNSS receiver.

19. The device according to claim 17, wherein: To determine the set of GNSS frequency bands to use based at least in part on the accuracy requirement, the one or more processors are configured to, in response to the accuracy requirement including an indication that no minimum accuracy is required, include in the set of GNSS frequency bands a single GNSS frequency band from the plurality of GNSS frequency bands available to the GNSS receiver.

20. The device according to claim 17, wherein: The one or more processors are configured to determine the set of GNSS frequency bands to use based at least in part on a maximum allowable error estimate of the GNSS position fix information.

21. The apparatus of claim 17, wherein: To determine the set of GNSS frequency bands to be used for determining the GNSS position fix information, the one or more processors are configured to: Using a single GNSS frequency band to obtain initial GNSS position information; Determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement; as well as In response to determining that the accuracy of the initial GNSS position fix information is insufficient to meet the accuracy requirement, two or more GNSS frequency bands are included in the set of frequency bands.

22. The apparatus of claim 17, wherein: To receive the request for the GNSS position fix, the one or more processors are configured to receive a plurality of requests for GNSS position fix information; To determine the set of GNSS frequency bands for the GNSS position fix information, the one or more processors are configured to determine two or more GNSS frequency bands for first GNSS position fix information from among the plurality of GNSS frequency bands available to the GNSS receiver; To determine the GNSS position fix information, the one or more processors are configured to determine the first GNSS position fix information; To provide the GNSS position fix information, the one or more processors are configured to provide the first GNSS position fix information; as well as The one or more processors are configured to obtain second GNSS position fix information using a single GNSS frequency band at a second one of the plurality of times in response to determining that the first GNSS position fix information satisfies the accuracy requirement at a first one of the plurality of times.

23. The device according to claim 22, wherein: The one or more processors are further configured to obtain third GNSS position fix information using the single GNSS frequency band during a third of the multiple times in response to determining that the second GNSS position fix information meets the accuracy requirement.

24. The device according to claim 22, wherein: The one or more processors are further configured to, in response to determining that the second GNSS position fix information does not meet the accuracy requirement, obtain a third GNSS position fix information using the two or more GNSS frequency bands used to determine the first GNSS position fix information a third time in the plurality of times.

25. The apparatus of claim 17, wherein: To receive the request for the GNSS position location information, the one or more processors are configured to receive the request for the GNSS position location information from an application processor; as well as The one or more processors are further configured to provide the GNSS position fix information including providing the GNSS position fix information to the application processor.

26. The device according to claim 17, wherein: To determine the set of GNSS frequency bands to use, the one or more processors are configured to include at least a baseline GNSS frequency band in the set of GNSS frequency bands.

27. The device according to claim 26, wherein: The one or more processors are configured to select the Global Positioning System (GPS) L1 frequency band as the baseline GNSS frequency band.

28. The device according to claim 26, wherein To determine the set of GNSS frequency bands to use, the one or more processors are configured to include one or more additional GNSS frequency bands in the set of GNSS frequency bands.

29. The device according to claim 28, wherein The one or more processors are configured to select the GPS L5 frequency band, the GPS L2 frequency band, or both as the one or more additional GNSS frequency bands.

30. The apparatus of claim 17, wherein: To determine the set of GNSS frequency bands to use, the one or more processors are configured to select the set of GNSS frequency bands from the plurality of GNSS frequency bands available to the GNSS receiver.

31. The apparatus of claim 17, wherein: The apparatus comprises a GNSS receiver.

32. The device according to claim 31, wherein The GNSS receiver has a plurality of receiver chains, each receiver chain being used to receive one or more GNSS frequency bands among the plurality of GNSS frequency bands, and wherein each receiver chain is selectively activated or deactivated based on the set of GNSS frequency bands so that the receiver can receive the set of GNSS frequency bands.

33. An apparatus for providing global navigation satellite system (GNSS) position positioning information, the apparatus comprising: means for receiving, at the device, a request for the GNSS position fix information, wherein the request includes an accuracy requirement; means for determining a set of GNSS frequency bands to be used for determining the GNSS position fix information from a plurality of GNSS frequency bands available to the apparatus based at least in part on the accuracy requirement; means for determining said GNSS position location information based at least in part on GNSS signals received via said set of GNSS frequency bands; as well as Means for providing the GNSS position fix information, wherein the GNSS position fix information comprises a GNSS position fix, pseudorange information, or both.

34. The device according to claim 33, wherein: The means for determining the set of GNSS frequency bands to use comprises means for including in the set of GNSS frequency bands two or more of the plurality of GNSS frequency bands available to the apparatus in response to the accuracy requirement comprising an indication requesting maximum accuracy.

35. The device according to claim 33, wherein The means for determining the set of GNSS frequency bands to use comprises means for including a single GNSS frequency band as the set of GNSS frequency bands in response to the accuracy requirements comprising an indication that no minimum accuracy is required.

36. The device according to claim 33, wherein The means for determining a set of GNSS frequency bands to be used comprises means for determining the set of GNSS frequency bands in response to the accuracy requirement comprising a maximum allowable error estimate of the GNSS position fix information.

37. The device according to claim 33, wherein: The means for determining the set of GNSS frequency bands to be used for determining the GNSS position location information comprises: A component for obtaining initial GNSS position fix information using a single GNSS frequency band; A component for determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement; and Means for determining two or more GNSS frequency bands as the frequency band set in response to determining that the accuracy of the initial GNSS position fix information is insufficient to meet the accuracy requirement.

38. The apparatus of claim 33, wherein: said means for receiving said request for said GNSS position location information comprises means for receiving a plurality of requests for GNSS position location information; the means for determining the set of GNSS frequency bands for the GNSS position fix information comprises means for determining two or more GNSS frequency bands of the plurality of GNSS frequency bands available to the apparatus for first GNSS position fix information; The means for determining the GNSS position location information comprises means for determining the first GNSS position location information; as well as The means for providing the GNSS position location information comprises means for providing the first GNSS position location information; The apparatus further includes a component for obtaining second GNSS position information using a single GNSS frequency band for a second time among the multiple times in response to determining that the first GNSS position information meets the accuracy requirement for the first time among the multiple times.

39. The device according to claim 38, wherein The apparatus further includes means for obtaining third GNSS position fix information using the single GNSS frequency band at a third time of the plurality of times in response to determining that the second GNSS position fix information meets the accuracy requirement.

40. The apparatus of claim 38, wherein: The apparatus further includes means for obtaining, in response to determining that the second GNSS position fix information does not meet the accuracy requirement, a third GNSS position fix information using the two or more GNSS frequency bands used to determine the first GNSS position fix information at a third time among the multiple times.

41. The apparatus of claim 33, wherein: The means for receiving the request for the GNSS position location information comprises the means for receiving the request for the GNSS position location information from an application processor; as well as The means for providing the GNSS position fix information includes means for providing the GNSS position fix information to the application processor.

42. The apparatus of claim 33, wherein: The means for determining the set of GNSS frequency bands comprises means for including at least a baseline GNSS frequency band in the set of GNSS frequency bands.

43. The device according to claim 42, wherein: The means for determining the set of GNSS frequency bands includes means for including one or more additional GNSS frequency bands in the set of GNSS frequency bands.

44. The apparatus of claim 33, wherein: The means for determining the set of GNSS frequency bands to be used for determining the GNSS position fix information based at least in part on the accuracy requirement includes means for selecting the set of GNSS frequency bands from the plurality of GNSS frequency bands available to the apparatus.

45. The apparatus of claim 33, wherein: The apparatus comprises a GNSS receiver.

46. ​​The device according to claim 45, wherein The GNSS receiver has a plurality of receiver chains, each receiver chain being used to receive one or more GNSS frequency bands among the plurality of GNSS frequency bands, and wherein each receiver chain is selectively activated or deactivated based on the set of GNSS frequency bands so that the receiver can receive the set of GNSS frequency bands.

47. A non-transitory computer-readable medium storing instructions for providing global navigation satellite system (GNSS) position location information, the instructions comprising code for: receiving a request for the GNSS position location information, wherein the request includes an accuracy requirement; determining, based at least in part on the accuracy requirement, a set of GNSS frequency bands from a plurality of GNSS frequency bands available to a GNSS receiver to be used for determining the GNSS position fix information; determining the GNSS position location information based at least in part on GNSS signals received via the set of GNSS frequency bands; as well as The GNSS position fix information is provided, wherein the GNSS position fix information includes a GNSS position fix, pseudorange information, or both.

48. The computer readable medium of claim 47, wherein: The code for determining the set of GNSS frequency bands to be used for determining the GNSS position fix information includes code for: Using a single GNSS frequency band to obtain initial GNSS position information; Determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement; as well as In response to determining that the accuracy of the initial GNSS position positioning information is insufficient to meet the accuracy requirement, two or more GNSS frequency bands are determined as the frequency band set.

49. The computer readable medium of claim 47, wherein: The code for receiving the request for the GNSS position location information includes code for receiving the request for the GNSS position location information from an application processor; as well as The code for providing the GNSS position fix information includes code for providing the GNSS position fix information to the application processor.

Images