High precision positioning for mobile devices

Abstract

The mobile device (102) performs a satellite positioning fixed solution operation using information from another mobile device (902). This information enables the mobile device to perform satellite positioning fixed solution operations with less power. An example method includes receiving, via a wireless communication protocol, an indication of a spacecraft identification (SVID) and an indication of a frequency error of the spacecraft indicated by the SVID, and performing an acquisition process for the spacecraft using the frequency error as a starting frequency. The method may further include receiving a ratio of carrier power to noise power (C / N) per unit bandwidth, determining an integration time based on the C / N, and performing an acquisition process for the spacecraft using the frequency error as a starting frequency error and using the integration time.

Description

Priority Statement

[0001] This application claims the benefit of U.S. Patent Application Serial No. 18 / 379,268, filed on October 12, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0002] Examples of this disclosure generally relate to high-precision positioning for mobile devices. More specifically, but without limitation, examples of this disclosure relate to a first mobile device performing a satellite fix operation and providing information to a second mobile device so that the second mobile device can perform a satellite fix operation based on the information provided by the first mobile device. Background Technology

[0003] Mobile devices have become ubiquitous. Many apps used on mobile devices require location information. However, location information can be inaccurate and may require significant amounts of energy. Attached Figure Description

[0004] In the accompanying drawings (which are not necessarily drawn to scale), similar reference numerals may describe similar parts in different views. To facilitate identification of any discussion of a particular element or action, one or more of the highest-order digits in the reference numerals indicate the drawing number in which the element was first introduced. Some non-limiting examples are shown in the accompanying drawings:

[0005] Figure 1 It is a diagrammatic representation of a networked environment in which the content of this disclosure can be deployed, based on some examples.

[0006] Figure 2 It is a graphical representation of a messaging system with both client-side and server-side functionalities, based on some examples.

[0007] Figure 3 It is a graphical representation of the data structures maintained in the database based on some examples.

[0008] Figure 4 It is a graphical representation based on some example messages.

[0009] Figure 5 A system with wearable devices is shown based on some examples.

[0010] Figure 6 It is a graphical representation of a machine in the form of a computer system, based on some examples, within which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein.

[0011] Figure 7It is a block diagram showing the software architecture in which examples can be implemented.

[0012] Figure 8 These are perspective views of wearable devices in the form of glasses, based on some examples.

[0013] Figure 9 A system for high-precision positioning of mobile devices is shown, based on some examples.

[0014] Figure 10 A system for high-precision positioning of mobile devices is shown, based on some examples.

[0015] Figure 11 The method for high-precision positioning of mobile devices is illustrated with some examples.

[0016] Figure 12 The method for high-precision positioning of mobile devices is illustrated with some examples. Detailed Implementation

[0017] The following description includes illustrative examples of systems, methods, techniques, instruction sequences, and computer program products that implement the present disclosure. In this description, numerous specific details are set forth for illustrative purposes to provide an understanding of various examples of the subject matter of the invention. However, it will be apparent to those skilled in the art that examples of the subject matter of the invention can be practiced without these specific details. Generally, well-known examples of instructions, protocols, structures, and techniques are not necessarily shown in detail.

[0018] Many applications running on mobile devices require location information from the mobile device to provide many of the application's features. For example, many applications that provide augmented reality (AR), mixed reality (MR), virtual reality (VR), and / or extended reality (XR) require location information from the mobile device to provide many of the application's features.

[0019] One technical challenge is determining the location information of a mobile device. In some examples, this is addressed by having a housing with a large battery to determine the housing's location and then providing that information to the mobile device so that the device can determine its location. The information from the housing allows the mobile device to use less energy, saving battery power and enabling more accurate location determination. For example, the housing could have a GNSS receiver component covering multiple frequency bands. The housing downloads almanac and ephemeris information from GNSS satellites. The housing then transmits this information to the mobile device using a low-power communication protocol such as Bluetooth Low Energy® (BLE). The housing identifies the satellites from which the mobile device is most likely to acquire and track signals. Because the housing is close to the mobile device, it can determine this information.

[0020] The housing can then transmit information such as spacecraft identification number (SVID), frequency error, carrier power to noise power ratio per unit bandwidth (C / N), SVID of satellites to be avoided, atmospheric delay, clock error, frequency Doppler shift, and other information. Mobile devices use this information to simplify determining their location using spacecraft or satellites. Additionally, mobile devices may be able to use clock errors, which can reduce the number of satellites the device must use from four to three. Furthermore, the information can include the housing's assumed location near the mobile device. The mobile device can use the housing's location to improve the estimation of its position and reduce the complexity of determining its location.

[0021] In addition, because mobile devices simplify positioning operations, GNSS receiver components can remain in standby or off mode for longer periods of time, which saves battery power and reduces the user's exposure to electromagnetic radiation.

[0022] Another technical challenge is providing privacy for mobile device users. This challenge is addressed by including a housing that can perform positioning fixation operations using GNSS satellites. Because the housing is close to the mobile device, it can provide information to assist the mobile device in acquiring and tracking satellites. Furthermore, the mobile device does not need to share any positioning information with the outside of the housing, which is controlled by the same user. Additionally, because the housing is close to the mobile device, the housing and the mobile device can exchange information using low-power communication protocols.

[0023] Networked computing environment

[0024] Figure 1 This is a block diagram illustrating an example interactive system 100 for facilitating interactions on a network, such as exchanging text messages, making text audio and video calls, or playing games. Interactive system 100 includes multiple client systems, each hosting multiple applications including interactive client 104 and other applications 106. Each interactive client 104 is communicatively coupled to other instances of interactive client 104 (e.g., hosted on corresponding other user systems), interactive server system 110, and third-party server 112 via one or more communication networks including network 108 (e.g., the Internet). Interactive client 104 can also communicate with locally hosted applications 106 using application programming interfaces (APIs).

[0025] Each user system 102 may include multiple user devices, such as computing device 114, wearable device 116, and computer client device 118, which are communicatively connected to exchange data and messages. Wearable device 116 may be a wearable device 116.

[0026] Interactive client 104 interacts with other interactive clients 104 and with interactive server system 110 via network 108. The data exchanged between interactive clients 104 (e.g., interaction 120) and between interactive client 104 and interactive server system 110 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0027] Interactive server system 110 provides server-side functionality to interactive client 104 via network 108. While some functions of interactive system 100 are described herein as being performed by interactive client 104 or interactive server system 110, the location of certain functions within interactive client 104 or interactive server system 110 may be a design choice. For example, it may be technically preferred that specific technologies and functions are initially deployed within interactive server system 110, but later migrated to interactive client 104 of user system 102 with sufficient processing power.

[0028] The interactive server system 110 supports various services and operations provided to the interactive client 104. Such operations include sending data to and receiving data from the interactive client 104, and processing data generated by the interactive client 104. This data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. Data exchange within the interactive system 100 is activated and controlled via functions available through the user interface (UI) of the interactive client 104.

[0029] Specifically, the focus now shifts to interactive server system 110. Application Programming Interface (API) server 122 is coupled to interactive server 124 and provides it with a programming interface, making the functionality of interactive server 124 accessible to interactive client 104, other applications 106, and third-party server 112. Interactive server 124 is communicatively coupled to database server 126, thereby facilitating access to database 128, which stores data associated with the interactions processed by interactive server 124. Similarly, web server 130 is coupled to interactive server 124 and provides a web-based interface to interactive server 124. For this purpose, web server 130 handles incoming network requests via Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0030] Application Programming Interface (API) server 122 receives and sends interactive data (e.g., command and message payloads) between interactive server 124 and client systems (such as interactive client 104 and other applications 106) and third-party server 112. Specifically, API server 122 provides a set of interfaces (e.g., routines and protocols) that interactive client 104 and other applications 106 can invoke or query to activate the functionality of interactive server 124. API server 122 exposes various functions supported by interactive server 124, including account registration; login functionality; sending interactive data from one interactive client 104 to another interactive client 104 via interactive server 124; transferring media files (e.g., images or videos) from interactive client 104 to interactive server 124; setting media data sets (e.g., stories); retrieving the friend list of users of user system 102; retrieving messages and content; adding and deleting entities (e.g., friends) against an entity graph (e.g., a social graph); locating friends in the social graph; and opening (e.g., application events associated with interactive client 104). Interactive server 124 hosts multiple systems and subsystems, as shown below. Figure 2 Describe it.

[0031] Linked applications

[0032] Returning to interactive client 104, the features and functionalities of the external resource (e.g., a linked application 106 or applet) are available to the user via the interface of interactive client 104. In this context, "external" refers to the fact that application 106 or applet is outside of interactive client 104. External resources are typically provided by third parties, but may also be provided by the creator or provider of interactive client 104. Interactive client 104 receives user selections regarding options for launching or accessing the features of such external resources. External resources may be application 106 installed on user system 102 (e.g., a "local app"), or a smaller version (e.g., a "app") of an application hosted on user system 102 or located remotely on user system 102 (e.g., on a third-party server 112). A smaller version of an application includes a subset of the features and functionalities of the application (e.g., a full-scale local version of the application) and is implemented using markup language documentation. In some examples, a smaller version of an application (e.g., an "app") is a web-based markup language version of the application and is embedded in interactive client 104. In addition to using markup language documentation (e.g., In addition to files, mini-programs can include scripting languages ​​(e.g., (files or .json files) and stylesheets (e.g., document).

[0033] In response to receiving a user selection of an option for launching or accessing an external resource, interactive client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, application 106, locally installed on user system 102, can be launched independently of and separately from interactive client 104, for example, by selecting the icon corresponding to application 106 on the home screen of user system 102. A smaller version of such an application can be launched or accessed via interactive client 104, and in some examples, no part of the smaller application can be accessed outside of interactive client 104, or only a limited portion of the smaller application can be accessed outside of interactive client 104. A smaller application can be launched by receiving, for example, markup language documents associated with the smaller application from third-party server 112 and processing such documents via interactive client 104.

[0034] In response to determining that the external resource is a locally installed application 106, the interactive client 104 instructs the user system 102 to launch the external resource by executing locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the interactive client 104 communicates with a third-party server 112 (e.g.) to obtain a markup language document corresponding to the selected external resource. The interactive client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the interactive client 104.

[0035] Interactive client 104 can notify users of user system 102 or other users (e.g., "friends") associated with such users of one or more external resources of ongoing activity. For example, interactive client 104 can provide participants in a conversation (e.g., a chat conversation) within interactive client 104 with notifications related to external resources currently or recently used by one or more members of a user group. One or more users can be invited to join an active external resource or to activate a recently used but currently inactive external resource (in a friend group). External resources can provide participants in the conversation, each using their respective interactive client 104, with the ability to share items, conditions, states, or locations within the external resource with one or more members of the user group during the chat session. Shared items can be interactive chat cards that chat members can use to interact, for example, activate the corresponding external resource, view specific information within the external resource, or take chat members to a specific location or state within the external resource. Within a given external resource, response messages can be sent to users on interactive client 104. External resources can selectively include different media items in the response based on the current context of the external resource.

[0036] Interactive client 104 can present a list of available external resources (e.g., application 106 or mini-program) to the user to launch or access a given external resource. This list can be presented as a context-sensitive menu. For example, the icons representing different applications (or mini-programs) of application 106 (or mini-program) can change based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0037] System Architecture

[0038] Figure 2 This is a block diagram illustrating further details of the interactive system 100 according to some examples. Specifically, the interactive system 100 is shown as including an interactive client 104 and an interactive server 124. The interactive system 100 includes multiple subsystems, which are supported on the client side by the interactive client 104 and on the server side by the interactive server 124. Example subsystems are discussed below.

[0039] The image processing system 202 provides various functions that enable users to acquire and enhance (e.g., annotate or otherwise modify or edit) media content associated with the message.

[0040] The camera device system 204 includes (e.g., in a camera device application) control software that (e.g., directly or via operating system controls) interacts with and controls the hardware camera device of the user system 102 to modify and enhance real-time images acquired and displayed via the interactive client 104.

[0041] Enhancement system 206 provides functionality related to the generation and distribution of enhancements (e.g., media overlays) for images acquired in real-time by the camera device of user system 102 or retrieved from the memory of user system 102. For example, enhancement system 206 is operable to select, present, and display media overlays (e.g., image filters or image lenses) for interactive client 104 to enhance real-time images received via camera device system 204 or stored images retrieved from memory 502 of user system 102. These enhancements are selected and presented to the user of interactive client 104 by enhancement system 206 based on some inputs and data, such as: The geographical location of user system 102; and Social network information of users in user system 102.

[0042] Enhancements may include audio and visual content and visual effects. Examples of audio and visual content include images, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects may be applied to media content items (e.g., photos or videos) at user system 102 for transmission in messages, or to video content such as video content streams or feeds sent from interactive client 104. Therefore, image processing system 202 can interact with and support various subsystems of communication system 208, such as messaging system 210 and video communication system 212.

[0043] Media overlays may include text or image data that can be superimposed on photographs taken by user system 102 or video streams produced by user system 102. In some examples, media overlays may be location overlays (e.g., Venice Beach), names of live events, or names of businesses (e.g., beach cafes). In other examples, image processing system 202 uses the geographic location of user system 102 to identify media overlays that include the names of businesses located at the geographic location of user system 102. Media overlays may include additional tags associated with businesses. Media overlays may be stored in database 128 and accessed through database server 126.

[0044] Image processing system 202 provides a user-based publishing platform that allows users to select geographic locations on a map and upload content associated with those locations. Users can also specify which media overlays should be provided to other users. Image processing system 202 generates a media overlay that includes the uploaded content and associates it with the selected geographic location.

[0045] The augmented reality creation system 214 supports augmented reality developer platforms and includes applications for content creators (e.g., artists and developers) to create and publish interactive clients 104, such as augmented reality experiences. The augmented reality creation system 214 provides content creators with a library of built-in features and tools, including, for example, custom shaders, tracking technologies, and templates.

[0046] In some examples, enhancement creation system 214 provides a merchant-based publishing platform that allows merchants to select specific enhancements associated with geographic locations via a bidding process. For example, enhancement creation system 214 associates the media overlay of the highest-bidding merchant with a corresponding geographic location for a predefined amount of time.

[0047] Communication system 208 is responsible for enabling and processing various forms of communication and interaction within interactive system 100, and includes messaging system 210, audio communication system 216, and video communication system 212. Messaging system 210 is responsible for enabling temporary or time-limited access to content by interactive client 104. Messaging system 210 includes (e.g., in short-lived timer system 218) multiple timers that selectively enable access (e.g., for presentation and display) of messages and associated content via interactive client 104 based on duration and display parameters associated with a message or set of messages (e.g., a story). Further details regarding the operation of short-lived timer system 218 are provided below. Audio communication system 216 enables and supports audio communication (e.g., real-time audio chat) between multiple interactive clients 104. Similarly, video communication system 212 enables and supports video communication (e.g., real-time video chat) between multiple interactive clients 104.

[0048] The user management system 220 is operationally responsible for managing user data and profiles, and includes an interactive platform 222, which maintains information about the relationships between users of the interactive system 100.

[0049] The collection management system 224 is operationally responsible for managing collections or sets of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into “event libraries” or “event stories.” Such collections can be made available for a specified time period (e.g., the duration of the event to which the content relates). For example, content related to a concert can be available as a “story” for the duration of the concert. The collection management system 224 can also be responsible for publishing icons that notify the user interface of the interactive client 104 of the availability of specific collections. The collection management system 224 includes curatorial functions that enable collection managers to manage and curate specific content collections. For example, a curation interface enables event organizers to curate collections of content related to a specific event (e.g., removing inappropriate content or redundant messages). Additionally, the collection management system 224 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, users may be compensated for including user-generated content in a collection. In such cases, the collection management system 224 operates to automatically pay such users for using their content.

[0050] Map system 226 provides various geolocation functions and supports the presentation of map-based media content and messages by interactive client 104. For example, map system 226 enables the display (e.g., stored in profile data 302) of user icons or avatars on a map to indicate the current or past locations of the user's "friends" within the context of the map, as well as media content generated by these friends (e.g., a collection of messages including photos and videos). For example, on the map interface of interactive client 104, messages posted by a user from a specific geographic location to interactive system 100 can be displayed to the specific user's "friends" within the context of that specific location on the map. Users can also share their location and status information with other users of interactive system 100 via interactive client 104 (e.g., using an appropriate status avatar), where the location and status information is similarly displayed to selected users within the context of the map interface of interactive client 104.

[0051] Game system 228 provides various game functions within the context of interactive client 104. Interactive client 104 provides a game interface that offers a list of available games that can be launched by a user within the context of interactive client 104 and played with other users of interactive system 100. Interactive system 100 also enables specific users to invite other users to participate in specific games by sending invitations from interactive client 104. Interactive client 104 also supports sending and receiving voice, video, and text messages (e.g., chat) within the context of playing the game, provides leaderboards for the game, and also supports providing in-game rewards (e.g., game currency and items).

[0052] External resource system 230 provides interactive client 104 with an interface to communicate with remote servers (e.g., third-party server 112) to launch or access external resources (i.e., applications or applets). Each third-party server 112 hosts applications or smaller versions of applications (e.g., game applications, utility applications, payment applications, or ride-sharing applications) based on markup languages ​​(e.g., HTML5). Interactive client 104 can launch web-based resources (e.g., applications) by accessing HTML5 files from the third-party server 112 associated with the web-based resource. The application hosted by the third-party server 112 is programmed in JavaScript using a software development kit (SDK) provided by interactive server 124. The SDK includes application programming interfaces (APIs) with functions that can be called or activated by the web-based application. Interactive server 124 hosts a JavaScript library that provides access to a given external resource for specific user data of interactive client 104. HTML5 is an example of a technology for programming games, but applications and resources programmed using other technologies can be used.

[0053] To integrate the SDK's functionality into the web-based resource, the third-party server 112 downloads the SDK from the interactive server 124, or the third-party server 112 otherwise receives the SDK. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the interactive client 104 into the web-based resource.

[0054] The SDK stored on the interactive server system 110 effectively bridges the gap between external resources (e.g., application 106 or applet) and the interactive client 104. This provides users with a seamless experience communicating with other users on the interactive client 104 while preserving the appearance of the interactive client 104. To bridge communication between the external resources and the interactive client 104, the SDK facilitates communication between the third-party server 112 and the interactive client 104. The WebViewJavaScriptBridge running on the user system 102 establishes two unidirectional communication channels between the external resources and the interactive client 104. Messages are sent asynchronously between the external resources and the interactive client 104 via these communication channels. Each SDK function activation is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.

[0055] By using the SDK, not all information from the interactive client 104 is shared with the third-party server 112. The SDK limits which information is shared based on the needs of the external resources. Each third-party server 112 provides the interactive server 124 with an HTML5 file corresponding to the web-based external resource. The interactive server 124 can add a visual representation (e.g., box design or other graphics) of the web-based external resource to the interactive client 104. Once the user selects the visual representation or instructs the interactive client 104 to access the features of the web-based external resource through the interactive client 104's GUI, the interactive client 104 obtains the HTML5 file and instantiates the resource for accessing the features of the web-based external resource.

[0056] Interactive client 104 presents a graphical user interface (GUI) for an external resource (e.g., a login page or title screen). During, before, or after presenting the login page or title screen, interactive client 104 determines whether the initiated external resource has previously been authorized to access user data of interactive client 104. In response to determining that the initiated external resource has previously been authorized to access user data of interactive client 104, interactive client 104 presents another GUI of the external resource, including its functionality and characteristics. In response to determining that the initiated external resource has not previously been authorized to access user data of interactive client 104, after displaying the login page or title screen of the external resource for a threshold time period (e.g., 3 seconds), interactive client 104 slides up a menu (e.g., animates the menu to appear from the bottom of the screen to the middle of the screen or other parts) to authorize the external resource to access user data. This menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of the accept option, interactive client 104 adds the external resource to the list of authorized external resources and allows the external resource to access user data from interactive client 104. External resources are authorized by the interactive client 104 to access user data under the OAuth 2 framework.

[0057] Interactive client 104 controls the type of user data shared with external resources based on the type of authorized external resource. For example, it provides access to a first type of user data (e.g., two-dimensional avatars of users with or without different avatar characteristics) to external resources including full-scale applications (e.g., application 106). As another example, it provides access to a second type of user data (e.g., payment information, two-dimensional avatars of users, three-dimensional avatars of users, and avatars with various avatar characteristics) to external resources including smaller versions of applications (e.g., web-based versions of applications). Avatar characteristics include different ways of customizing the appearance of an avatar (e.g., different poses, facial features, clothing, etc.).

[0058] The advertising system 232 is operationally designed to enable third parties to purchase advertisements to be presented to end users via the interactive client 104, and also handles the delivery and presentation of these advertisements.

[0059] Reference Figure 9 and Figure 10The high-precision positioning system 234 supports the positioning of components 932 and 1032. In some examples, the high-precision positioning system 234 performs one or more functions for positioning components 932 and 1032, such as solving equations for acquiring components 935 and 1035 or tracking components 933 and 1033. Additionally, the high-precision positioning system 234 can provide almanac and ephemeris information 926 to the housing 902 and / or the user system 102. Furthermore, the high-precision positioning system 234 can provide updates and / or applications to the housing 902 and / or the user system 102, such as providing positioning information for components 932 and 1032.

[0060] Data Architecture

[0061] Figure 3 This is a schematic diagram illustrating a data structure 300 that can be stored in a database 304 of an interactive server system 110, according to certain examples. Although the contents of the database 304 are shown as including multiple tables, it should be understood that data can be stored in other types of data structures, such as object-oriented databases.

[0062] Database 304 includes message data stored in message table 306. For any given message, this message data includes at least message sender data, message receiver (or recipient) data, and payload. See below for reference. Figure 3 Further details are provided regarding information that can be included in the message and is contained within the message data stored in message table 306.

[0063] Entity table 308 stores entity data and (for example, links to entity diagram 310 and profile data 302). Entities for which records are maintained in entity table 308 can include individuals, company entities, organizations, objects, locations, events, etc. Regardless of the entity type, any entity for which the interactive server system 110 stores data can be an identifiable entity. Each entity is assigned a unique identifier and an entity type identifier (not shown).

[0064] Entity graph 310 stores information about the relationships and associations between entities. As an example only, such relationships can be social, professional (e.g., working in a common company or organization), interest-based, or activity-based. Some relationships between entities can be one-way, such as an individual user subscribing to digital content from a business or publishing user (e.g., a newspaper or other digital media channel or brand). Other relationships can be two-way, such as the "friendship" relationships between the various users of interactive system 100.

[0065] Certain licenses and relationships can be attached to each relationship, and also to each direction of the relationship. For example, a two-way relationship (e.g., a friendship between individual users) can include authorization for the posting of digital content items between the individual users, but certain restrictions or filters can be imposed on the posting of such digital content items (e.g., based on content characteristics, location data, or time of day data). Similarly, a subscription relationship between an individual user and a business user can impose varying degrees of restrictions on the posting of digital content from the business user to the individual user, and can significantly restrict or prevent the posting of digital content from the individual user to the business user. As an example of an entity, a specific user can (e.g., through privacy settings) record certain restrictions in the records for that entity within entity table 308. Such privacy settings can be applied to all types of relationships in the context of interaction system 100, or selectively applied to certain types of relationships.

[0066] Profile data 302 stores various types of profile data about a specific entity. Based on privacy settings specified by the specific entity, profile data 302 can be selectively used and presented to other users of the interaction system 100. In the case of an individual, profile data 302 includes, for example, the user's name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a set of such avatar representations) selected by the user. A specific user can then selectively include one or more of these avatar representations within the content of messages transmitted via the interaction system 100 and on a map interface displayed to other users by the interaction client 104. The set of avatar representations may include "status avatars," which present a graphical representation of a status or activity that the user can choose to transmit at a specific time.

[0067] In the case that the entity is a group, in addition to the group name, members and various settings for the relevant group (e.g., notifications), the profile data 302 for the group may similarly include one or more avatars associated with the group.

[0068] Database 304 also stores enhancement data, such as overlays or filters, in enhancement table 312. Enhancement data is associated with and applied to videos (video data is stored in video table 314) and images (image data is stored in image table 316).

[0069] In some examples, filters are displayed as overlays on images or videos during presentation to the recipient user. Filters can be of various types, including user-selected filters from a set of filters presented to the sending user by the interactive client 104 while the sending user is composing a message. Other types of filters include geolocation filters (also known as geographic filters), which can be presented to the sending user based on geographic location. For example, geolocation filters specific to nearby or particular locations can be presented by the interactive client 104 within the user interface based on geographic location information determined by the user system 102's Global Positioning System (GPS) unit.

[0070] Another type of filter is a data filter, which can be selectively presented to the sending user by the interactive client 104 based on other inputs or information collected by the user system 102 during the message creation process. Examples of data filters include the current temperature at a specific location, the sending user's current speed, the battery life of the user system 102, or the current time.

[0071] Other augmented data that can be stored in image table 316 includes augmented reality content items (e.g., corresponding to an application "lens" or augmented reality experience). Augmented reality content items can be real-time special effects and sounds that can be added to images or videos.

[0072] Story table 318 stores data about collections of messages and associated image, video, or audio data, compiled into collections (e.g., stories or galleries). The creation of a specific collection can be initiated by a specific user (e.g., each user for whom records are maintained in entity table 308). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcast by that user. For this purpose, the user interface of interactive client 104 can include user-selectable icons to allow the sending user to add specific content to his or her personal story.

[0073] The collection can also constitute a "live story," which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" can constitute a curated stream of user-submitted content from different locations and events. Users whose client devices have location services enabled and who are at a shared location event at a specific time can be presented with the option to contribute content to a specific live story, for example, via the user interface of interactive client 104. Live stories can be identified to a user by interactive client 104 based on their location. The end result is a "live story" told from a collective perspective.

[0074] Another type of content collection is called a "location story," which enables users of user system 102 located in a specific geographic location (e.g., on a college or university campus) to contribute to a specific collection. In some examples, contributions to a location story may employ two-level authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on a university campus).

[0075] As mentioned above, video table 314 stores video data, which in some examples is associated with messages for which records are maintained within message table 306. Similarly, image table 316 stores image data associated with messages whose message data is stored in entity table 308. Entity table 308 can associate various enhancements from enhancement table 312 with various images and videos stored in image table 316 and video table 314.

[0076] Database 304 also includes location table 319. (See reference...) Figure 9 and Figure 10 Positioning table 319 includes almanac and ephemeris information 926, 1026, user system positioning 1029, shell positioning 929, 1028, etc.

[0077] Data communication architecture

[0078] Figure 4 This is a schematic diagram illustrating the structure of message 400 according to some examples, generated by interactive client 104 for transmission to another interactive client 104 via interactive server 124. The content of a particular message 400 is used to populate message table 306 within database 304 accessible by interactive server 124. Similarly, the content of message 400 is stored in memory as "in-transit" or "in-flight" data for user system 102 or interactive server 124. Message 400 is shown to include the following example components: Message identifier 402 is a unique identifier that identifies message 400. The message text payload 404 is the text to be generated by the user through the user interface of the user system 102 and included in message 400. The message image payload 406 is image data acquired by the camera device component of the user system 102 or retrieved from the memory component of the user system 102 and included in the message 400. The image data for the sent or received message 400 can be stored in the image table 316. Message video payload 408: Video data acquired by the camera device component or retrieved from the memory component of the user system 102 and included in message 400. The video data for the sent or received message 400 may be stored in image table 316. Message audio payload 410: Audio data acquired by the microphone or retrieved from the memory component of the user system 102 and included in message 400. Message enhancement data 412: This represents enhancement data (e.g., filters, labels, or other annotations or enhancements) to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of message 400. Enhancement data for the sent or received message 400 can be stored in enhancement table 312. The message duration parameter 414 is a parameter value that indicates, in seconds, the amount of time that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) will be presented to the user via the interactive client 104 or made accessible to the user. Message geolocation parameter 416: Geographic location data (e.g., latitude and longitude coordinates) associated with the message's content payload. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within the message image payload 406 or a specific video within the message video payload 408). Message Story Identifier 418: An identifier value that identifies one or more sets of content (e.g., "Stories" identified in Story Table 318) associated with a specific content item in Message Image Payload 406 of Message 400. For example, the identifier value can be used to associate multiple images within Message Image Payload 406 with multiple sets of content, respectively. Message Tag 420: Each message 400 can be labeled with multiple tags, each of which indicates the subject of the content included in the message payload. For example, in the case where a specific image depicts an animal (e.g., a lion) is included in the message image payload 406, the tag value can be included within the message tag 420 indicating the relevant animal. The tag value can be manually generated based on user input, or it can be automatically generated using, for example, image recognition. Message sender identifier 422: An identifier (e.g., message sending system identifier, email address, or device identifier) ​​indicating the user of the user system 102 on which message 400 is generated and from which message 400 is sent. Message receiver identifier 424: An identifier (e.g., message sending and receiving system identifier, email address, or device identifier) ​​indicating the user of the user system 102 to which message 400 is addressed.

[0079] The content (e.g., values) of each component of message 400 can be pointers to locations in tables where content data values ​​are stored. For example, image values ​​in message image payload 406 can be pointers (or addresses) to locations within image table 316. Similarly, values ​​in message video payload 408 can point to data stored in image table 316, values ​​in message enhancement data 412 can point to data stored in enhancement table 312, values ​​in message story identifier 418 can point to data stored in story table 318, and values ​​in message sender identifier 422 and message receiver identifier 424 can point to user records stored in entity table 308.

[0080] Systems with wearable devices

[0081] Figure 5 A system 500 including a wearable device 116 with a selector input device is shown according to some examples. Figure 5 This is a high-level functional block diagram of an example wearable device 116 that is communicatively coupled to computing devices 114 and various server systems 504 (e.g., interactive server system 110) via various networks 108.

[0082] The wearable device 116 includes one or more camera devices, each of which may be, for example, a visible light camera 506, an infrared emitter 508, and an infrared camera 510.

[0083] Computing device 114 connects to wearable device 116 using both low-power wireless connection 512 and high-speed wireless connection 514. According to some examples, computing device 114 also connects to server system 504 and network 516. Computing device 114 can be a portable computing device, such as a smartphone, tablet computer, laptop computer, or other type of computing device 114, such as a desktop computer or other type of computing device 114.

[0084] The wearable device 116 also includes two image displays of the optical component's image display 518. The two image displays 518 of the optical component include one image display associated with the left lateral side of the wearable device 116 and one image display associated with the right lateral side of the wearable device 116. The wearable device 116 also includes an image display driver 520, an image processor 522, a low-power circuitry system 524, and a high-speed circuitry system 526. The image displays 518 of the optical component are used to present images and videos to the user of the wearable device 116, including images that may include a graphical user interface.

[0085] The image display driver 520 commands and controls the image display 518 of the optical components. The image display driver 520 can directly deliver image data to the image display 518 of the optical components for presentation, or it can convert image data into a signal or data format suitable for delivery to the image display device. For example, the image data can be video data formatted according to compression formats such as H.264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideo RV40, VP8, VP9, ​​etc., while still image data can be formatted according to compression formats such as Portable Network Group (PNG), Joint Photo Experts Group (JPEG), Tagged Image File Format (TIFF), or Exchangeable Image File Format (EXIF), etc.

[0086] Wearable device 116 includes a frame and a pole (or temple) extending laterally from the frame. Wearable device 116 also includes a user input device 528 (e.g., a touch sensor or button) including an input surface on wearable device 116. User input device 528 (e.g., a touch sensor or button) is used to receive input selections from a user for manipulating a graphical user interface of a presented image.

[0087] Figure 5 The components shown for wearable device 116 are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the frame or temples. Alternatively or additionally, the depicted components may be located in modules, frames, hinges, or nose bridges of wearable device 116. The left and right visible light camera devices 506 may include digital camera elements, such as complementary metal-oxide-semiconductor (CMOS) image sensors, charge-coupled devices, camera lenses, or any other corresponding visible light or light-acquiring elements that can be used to acquire data, including images of scenes with unknown objects.

[0088] The wearable device 116 includes a memory 502 that stores instructions for performing a subset or all of the functions described herein. The memory 502 may also include a storage device.

[0089] like Figure 5 As shown, the high-speed circuit system 526 includes a high-speed processor 530, a memory 502, and a high-speed wireless circuit system 532. In some examples, an image display driver 520 is coupled to the high-speed circuit system 526 and operated by the high-speed processor 530 to drive the left and right image displays of the image display 518 of the optical components. The high-speed processor 530 can be any processor capable of managing the high-speed communication and operation of any general-purpose computing system required by the wearable device 116. The high-speed processor 530 includes the processing resources required to manage high-speed data transmission over the high-speed wireless connection 514 to a wireless local area network (WLAN) using the high-speed wireless circuit system 532. In some examples, the high-speed processor 530 executes the operating system of the wearable device 116 (e.g., a LINUX operating system) or other such operating system, and the operating system is stored in the memory 502 for execution. Among other duties, the high-speed processor 530, which executes the software architecture of the wearable device 116, manages data transmission with the high-speed wireless circuit system 532. In some examples, the high-speed wireless circuit system 532 is configured to implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, also referred to herein as WiFi. In some examples, the high-speed wireless circuit system 532 may implement other high-speed communication standards.

[0090] The low-power wireless circuit system 534 and high-speed wireless circuit system 532 of wearable device 116 may include a short-range transceiver (Bluetooth™) and a wireless wide area network transceiver, a wireless local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). Computing device 114—including transceivers communicating via low-power wireless connection 512 and high-speed wireless connection 514—can be implemented using the details of the architecture of wearable device 116, as can other components of network 516.

[0091] Memory 502 includes any storage device capable of storing various data and applications, including, in particular, camera data generated by the left and right visible light cameras 506, the infrared camera 510, and the image processor 522, as well as images generated for display on an image display 518 in the optical components via the image display driver 520. While memory 502 is shown as integrated with the high-speed circuitry 526, in some examples, memory 502 may be a separate, independent component of the wearable device 116. In some such examples, electrical wiring may provide a connection from the image processor 522 or the low-power processor 536 to memory 502 via a chip including the high-speed processor 530. In some examples, the high-speed processor 530 may manage addressing of memory 502 such that the low-power processor 536 will activate the high-speed processor 530 whenever a read or write operation involving memory 502 is required.

[0092] like Figure 5 As shown, the low-power processor 536 or high-speed processor 530 of the wearable device 116 may be coupled to a camera device (visible light camera 506, infrared emitter 508 or infrared camera 510), an image display driver 520, a user input device 528 (e.g., a touch sensor or button) and a memory 502.

[0093] Wearable device 116 is connected to a host computer. For example, wearable device 116 is paired with computing device 114 via high-speed wireless connection 514 or connected to server system 504 via network 516. Server system 504 may be one or more computing devices as part of a service or network computing system, for example, it includes a processor, memory and network communication interface to communicate with computing device 114 and wearable device 116 via network 516.

[0094] The computing device 114 includes a processor and a network communication interface coupled to the processor. The network communication interface enables communication via a network 516, a low-power wireless connection 512, or a high-speed wireless connection 514. The computing device 114 can also store at least a portion of the instructions for generating binaural audio content in its memory to implement the functions described herein.

[0095] The output components of wearable device 116 include visual components such as a display, which may be, for example, a liquid crystal display (LCD), a plasma display panel (PDP), a light-emitting diode (LED) display, a projector, or a waveguide. The image display of the optical components is driven by an image display driver 520. The output components of wearable device 116 also include acoustic components (e.g., a speaker), haptic components (e.g., a vibration motor), other signal generators, etc. The input components (e.g., user input device 528) of wearable device 116, computing device 114, and server system 504 may include alphanumeric input components (e.g., a keyboard, a touchscreen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), pointing-based input components (e.g., a mouse, touchpad, trackball, joystick, motion sensor, or other pointing instruments), haptic input components (e.g., physical buttons, a touchscreen that provides the position and force of a touch or touch gesture, or other haptic input components), audio input components (e.g., a microphone), etc.

[0096] The wearable device 116 may also include additional peripheral device elements. Such peripheral device elements may include biometric sensors, additional sensors, or display elements integrated with the wearable device 116. For example, peripheral device elements may include any I / O components, including output components, motion components, positioning components, or any other such elements described herein.

[0097] For example, biometric components include those for detecting expressions (e.g., hand gestures, facial expressions, voice expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Motion components include accelerometer components (e.g., accelerometers), gravity sensor components, rotation sensor components (e.g., gyroscopes), etc. Positioning components include position sensor components (e.g., GPS receiver components) for generating location coordinates, Wi-Fi or Bluetooth™ transceivers for generating positioning system coordinates, altitude sensor components (e.g., altimeters or barometers that detect air pressure, from which altitude can be obtained), orientation sensor components (e.g., magnetometers), etc. Such positioning system coordinates can also be received from computing device 114 via low-power wireless connection 512 and high-speed wireless connection 514 through low-power wireless circuit system 534 or high-speed wireless circuit system 532.

[0098] Machine architecture

[0099] Figure 6This is a schematic representation of machine 600, within which instructions 602 (e.g., software, programs, applications, applets, or other executable code) can be executed to cause machine 600 to perform any or more of the methods discussed herein. For example, instructions 602 can cause machine 600 to perform any or more of the methods described herein. Instructions 602 transform the general, unprogrammed machine 600 into a specific machine 600 programmed to perform the described and illustrated functions in the described manner. Machine 600 can operate as a standalone device or can be coupled (e.g., networked) to other machines. In a networked deployment, machine 600 can operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 600 may include, but is not limited to, server computers, client computers, personal computers (PCs), tablet computers, laptop computers, netbooks, set-top boxes (STBs), personal digital assistants (PDAs), entertainment media systems, cellular phones, smartphones, mobile devices, wearable devices (e.g., smartwatches), smart home devices (e.g., smart appliances), other smart devices, web devices, network routers, network switches, network bridges, or any machine capable of sequentially or otherwise executing instructions 602 specifying actions to be taken by machine 600. Furthermore, although only a single machine 600 is shown, the term "machine" should also be considered as a collection of machines that individually or jointly execute instructions 602 to perform any or more of the methods discussed herein. For example, machine 600 may include user system 102 or any of a plurality of server devices forming part of interactive server system 110. In some examples, machine 600 may also include both client and server systems, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of said particular method or algorithm are performed on the client side.

[0100] Machine 600 may include a processor 604, a memory 606, and an input / output (I / O) unit 608 that can be configured to communicate with each other via a bus 610. In the example, processor 604 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processors 612 and 614 that execute instruction 602. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") capable of executing instructions simultaneously. Although Figure 6Multiple processors 604 are shown, but machine 600 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0101] Memory 606 includes main memory 616, static memory 618, and memory cells 620, all of which are accessible by processor 604 via bus 610. Main memory 606, static memory 618, and memory cells 620 store instructions 602 that implement any one or more of the methods or functions described herein. Instructions 602 may also reside wholly or partially within main memory 616, static memory 618, machine-readable medium 622 within memory cell 620, at least one processor of processor 604 (e.g., within the processor's cache memory), or any suitable combination thereof during execution by machine 600.

[0102] I / O component 608 may include various components for receiving input, providing output, generating output, sending information, exchanging information, acquiring measurement results, etc. The specific I / O component 608 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine is unlikely to include such a touch input device. It should be recognized that I / O component 608 may include... Figure 6 Many other components are not shown. In various examples, I / O component 608 may include user output component 624 and user input component 626. User output component 624 may include visual components (e.g., displays such as plasma display panels (PDPs), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tube (CRT) displays), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. User input component 626 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), pointing-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing instruments), haptic input components (e.g., physical buttons, touchscreens or other haptic input components that provide the position and force of a touch or touch gesture), audio input components (e.g., microphones), etc.

[0103] In other examples, I / O component 608 may include biometric component 628, motion component 630, environmental component 632, or positioning component 634, as well as a wide range of other components. For example, biometric component 628 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Motion component 630 includes accelerometer components (e.g., accelerometers), gravity sensor components, and rotation sensor components (e.g., gyroscopes).

[0104] The environmental component 632 includes, for example, one or more camera devices (with still image / photograph and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers for detecting ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones for detecting background noise), proximity sensor components (e.g., infrared sensors for detecting nearby objects), gas sensors (e.g., gas detection sensors for detecting the concentration of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0105] Regarding the camera device, user system 102 may have a camera device system including, for example, a front-facing camera on the front surface of user system 102 and a rear-facing camera on the rear surface of user system 102. The front-facing camera may be used, for example, to acquire still images and videos (e.g., “selfies”) of the user of user system 102, which can then be enhanced with the aforementioned enhancement data (e.g., filters). For example, the rear-facing camera may be used to acquire still images and videos in a more conventional camera device mode, which are similarly enhanced with the enhancement data. In addition to the front-facing and rear-facing cameras, user system 102 may also include a 360° camera for acquiring 360° photos and videos.

[0106] Furthermore, the camera system of user system 102 may include dual rear cameras (e.g., a main camera and a depth-sensing camera), or even triple, quadruple, or quintuple rear camera configurations on the front and rear sides of user system 102. For example, these multi-camera systems may include wide-angle cameras, ultra-wide-angle cameras, telephoto cameras, macro cameras, and depth sensors.

[0107] The positioning component 634 includes a location sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure and from which altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0108] Various technologies can be used to achieve communication. I / O component 608 also includes communication component 636, which is operable to couple machine 600 to network 638 or device 640 via a suitable coupling or connection. For example, communication component 636 may include a network interface component or another suitable device that interfaces with network 638. In other examples, communication component 636 may include wired communication component, wireless communication component, cellular communication component, near field communication (NFC) component, Bluetooth component, etc. ® Components (e.g., Bluetooth) ® Low energy consumption), Wi-Fi ® Components and other communication components for providing communication via other means. Device 640 can be any peripheral device from another machine or various peripheral devices (e.g., a peripheral device coupled via USB).

[0109] Furthermore, the communication component 636 can detect identifiers, or include components operable to detect identifiers. For example, the communication component 636 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, UltraCode, UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying audio signals from the tag). Additionally, various information can be obtained via the communication component 636, such as location via Internet Protocol (IP) geographic location, location via Wi-Fi® signal triangulation, location via detecting NFC beacon signals that can indicate a specific location, etc.

[0110] Various memories (e.g., main memory 616, static memory 618, and the memory of processor 604) and storage unit 620 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instruction 602) cause various operations to implement the disclosed examples when executed by processor 604.

[0111] Instruction 602 can be sent or received over network 638 via a transmission medium using a network interface device (e.g., a network interface component included in communication component 636) and using any of several known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instruction 602 can be sent or received via a transmission medium coupled to device 640 (e.g., peer-to-peer coupling).

[0112] Software Architecture

[0113] Figure 7 This is a block diagram 700 illustrating a software architecture 702 that can be installed on any or more devices described herein. The software architecture 702 is supported by hardware, such as a machine 704 including a processor 706, memory 708, and I / O components 710. In this example, the software architecture 702 can be conceptualized as a stack of layers, where each layer provides a specific function. The software architecture 702 includes layers such as an operating system 712, libraries 714, frameworks 716, and applications 718. Operationally, application 718 activates API calls 720 through the software stack and receives messages 722 in response to API calls 720.

[0114] Operating system 712 manages hardware resources and provides public services. Operating system 712 includes, for example, a kernel 724, services 726, and drivers 728. Kernel 724 acts as an abstraction layer between hardware and other software layers. For example, kernel 724 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 726 can provide other public services to other software layers. Drivers 728 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 728 may include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® low-power drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), Wi-Fi® drivers, audio drivers, power management drivers, etc.

[0115] Library 714 provides common low-level infrastructure used by application 718. Library 714 may include system libraries 730 (e.g., the C standard library), which provide functions such as memory allocation, string manipulation, and mathematical functions. Furthermore, library 714 may include API libraries 732, such as media libraries (e.g., libraries for supporting the rendering and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codecs, Joint Picture Experts Group (JPEG or JPG), or Portable Web Graphics (PNG)), graphics libraries (e.g., an OpenGL framework for rendering graphic content on a display in two-dimensional (2D) and three-dimensional (3D) formats), database libraries (e.g., SQLite, which provides various relational database functions), web libraries (e.g., WebKit, which provides web browsing capabilities), etc. Library 714 may also include a wide variety of other libraries 734 to provide many other APIs to application 718.

[0116] Framework 716 provides common high-level infrastructure for use by application 718. For example, framework 716 provides various graphical user interface (GUI) functions, high-level resource management, and high-level location services. Framework 716 can provide a wide range of other APIs that can be used by application 718, some of which may be specific to a particular operating system or platform.

[0117] In the example, application 718 may include home application 736, contact application 738, browser application 740, book reader application 742, location application 744, media application 746, messaging application 748, game application 750, and a wide variety of other applications such as third-party application 752. Application 718 is a program that performs the functions defined in the program. Various programming languages ​​can be used to create one or more applications 718 constructed in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a particular example, third-party application 752 (e.g., an application developed by an entity other than a platform-specific vendor using the Android™ or iOS™ Software Development Kit (SDK)) may be on platforms such as iOS™, Android… TM Mobile software running on the Windows® Phone mobile operating system or other mobile operating systems. In this example, third-party application 752 can activate API call 720 provided by the operating system 712 to facilitate the functionality described herein.

[0118] Figure 8 This is a perspective view of a wearable device in the form of glasses 800, based on some examples. Glasses 800 is an eye-wearable article that includes electronic components that operate within a network system for transmitting image and video content. Figure 8 An example of wearable device 116 is shown. In some examples, wearable electronic devices are referred to as augmented reality (AR), mixed reality (MR), virtual reality (VR), and / or extended reality (XR) glasses. Glasses 800 may include a frame 832 made of any suitable material, such as plastic or metal, including any suitable shape memory alloy. Frame 832 may have a front element 833, which may include a first or left lens, a display or optical element holder 836, and a second lens or right lens, a display or optical element holder 837 connected by a bridge 838. The front element 833 further includes a left end portion 841 and a right end portion 842. A first optical element or left optical element 844 and a second optical element or right optical element 843 may be disposed within the respective left optical element 836 and right optical element holder 837. Each of the optical elements 843, 844 may be a lens, a display, a display assembly, or a combination thereof. In some examples, for instance, the glasses 800 are provided with an integrated near-eye display mechanism that enables, for example, to display to a user a preview image of the visual media acquired by the camera device 869 of the glasses 800.

[0119] Frame 832 further includes a left or temple piece 846 and a right or temple piece 847, which are coupled to corresponding left and right end portions 841 and 842 of the front piece 833 via any suitable means such as hinges (not shown) to either be rigidly or fixably attached to the front piece 833, thereby becoming integral with it. Each of the temple pieces 846 and 847 may include: a first portion 851 coupled to the corresponding end portion 841 or 842 of the front piece 833; and any suitable second portion 852, such as a curved or arched member, for coupling to the user's ear. In one example, the front piece 833 may be formed from a single piece of material to have a monolithic or integrated construction. In one example, the entire frame 832 may be formed from a single piece of material to have a monolithic or integrated construction.

[0120] The eyeglasses 800 include a computing device such as a computer 861, which can be of any suitable type to be carried by the frame 832, and in one example, the computing device has a suitable size and shape to be at least partially disposed in one or more of the temple members 846 and 847. In one example, the computer 861 has a size and shape similar to that of one of the temple members 846 and 847, and is therefore disposed, if not completely, almost completely within the structure and boundaries of such temple members 846 and 847.

[0121] In one example, computer 861 may be disposed in both temple piece 846 and temple piece 847. Computer 861 may include one or more processors having memory, wireless communication circuitry, and a power supply. Computer 861 includes low-power circuitry, high-speed circuitry, position circuitry, and a display processor. Various other examples may include these elements in different configurations or integrated together in different ways. Additional details of various aspects of computer 861 may be implemented as described below with reference to the description.

[0122] The computer 861 also includes a battery 862 or other suitable portable power source. In one example, the battery 862 is disposed in one of the temple pieces 846 or 847. Figure 8 In the illustrated eyeglasses 800, a battery 862 is shown disposed in the left temple 846 and electrically coupled via a connector 874 to the remainder of a computer 861 disposed in the right temple 847. One or more input and output devices may include connectors or ports (not shown) suitable for charging the battery 862 and accessible from the outside of the frame 832, wireless receivers, transmitters or transceivers (not shown), or combinations of such devices.

[0123] The glasses 800 include a digital camera device 869. Although two camera devices 869 are depicted, other examples contemplate the use of a single or additional (i.e., more than two) camera devices 869. For ease of description, the various features associated with the camera device 869 will be further described with reference only to a single camera device 869, but it will be understood that, in suitable examples, these features may apply to two camera devices 869.

[0124] In various examples, in addition to the camera device 869, the glasses 800 may include any number of input sensors or peripheral devices. The front element 833 is provided with: a front-facing, forward-facing, front or outer surface 866 facing forward or away from the user when the glasses 800 is mounted on the user's face; and a relatively inward-facing, rear-facing, rear or inner surface 867 facing the user's face when the glasses 800 is mounted on the user's face. Such sensors may include: an inward-facing video sensor or digital imaging module, for example, which may be mounted on the inner surface 867 of the front element 833 or disposed elsewhere on the inner surface 867 of the front element 833 or on the frame 832 to face the camera device 869 of the user; and an outward-facing video sensor or digital imaging module, for example, which may be mounted on the outer surface 866 of the front element 833 or disposed elsewhere on the outer surface 866 of the front element 833 or on the frame 832 to face away from the camera device 869 of the user. Such sensors, peripheral devices, or peripheral equipment may additionally include biometric sensors, position sensors, accelerometers, or any other such sensors. In some examples, a projector (not shown) is used to project images onto the inner surface of optical elements 843, 844 (or lenses) to provide a mixed reality or augmented reality experience for the user of glasses 800.

[0125] The glasses 800 also include an example of a camera device control mechanism or user input mechanism, which includes a camera device control button mounted on the frame 832 for tactile or manual engagement by the user. The camera device control button provides a bimodal or single-action mechanism, meaning the user can only set it between two states: engaged and disengaged. In this example, the camera device control button is in the disengaged state by default, and can be pressed by the user to set it to the engaged state. When the pressed camera device control button is released, it automatically returns to the disengaged state.

[0126] In other examples, the single-action input mechanism may alternatively be provided by, for example, a touch-sensitive button including a capacitive sensor mounted adjacent to the surface of the frame 832 to detect the presence of a user's finger, so that the touch-sensitive button is engaged when the user touches a corresponding point on the outer surface 866 of the frame 832. It will be understood that the camera device control buttons and capacitive touch buttons described above are merely two examples of tactile input mechanisms for single-action control of the camera device 869, and other examples may employ different single-action tactile control arrangements.

[0127] Computer 861 is configured to perform the methods described herein. In some examples, computer 861 is coupled to one or more antennas for receiving signals from GNSS and to a circuitry for processing the signals, wherein the antennas and circuitry are housed in glasses 800. In some examples, computer 861 is coupled to one or more wireless antennas and circuitry for transmitting and receiving wireless signals, wherein the antennas and circuitry are housed in glasses 800. In some examples, glasses 800 houses multiple sets of antennas and circuitry. In some examples, the antennas and circuitry are configured to operate according to communication protocols such as Bluetooth™, Bluetooth Low Energy™, IEEE 802, IEEE 802.11az / be, Wi-Fi®, etc. In some examples, a PDR sensor is housed in glasses 800 and coupled to computer 861. In some examples, glasses 800 is a VR headset, wherein optics 843 and optics 844 are opaque screens for displaying images to a user of the VR headset. In some examples, computer 861 is coupled to user interface elements such as sliders or touchpads 876 and buttons 878. A long press of button 878 resets glasses 800. Slider or touchpad 876 and button 878 are used by the user to provide input to computer 861 and / or other electronic components of glasses 800. Glasses 800 includes one or more microphones 882 coupled to computer 861. Glasses 800 includes one or more gyroscopes 880.

[0128] High-precision positioning for mobile devices

[0129] Figure 9 A system 900 for high-precision positioning of mobile devices is shown, based on some examples. Figure 10 A system 1000 for high-precision positioning of mobile devices is shown, based on some examples. Figure 9 and Figure 10The components are disclosed in combination. Global Navigation Satellite System (GNSS) satellite 904 provides signals received by GNSS receiver component 906 of housing 902 and GNSS receiver component 1006 of user system 102. GNSS satellite 904 provides autonomous geolocation information. Examples of GNSS satellites 904 include the US Global Positioning System (GPS), the European Union's Galileo system, etc. Signal 903 of GNSS satellite 904 includes information that can be used to determine the distance to GNSS satellite 904. This information may include SVIDs 914 and 1014 of GNSS satellite 904, clock time indication, almanac and ephemeris information 926 and 1026, etc. Positioning components 932 and 1032 can determine housing positioning 929 and user system positioning 1029 respectively by acquiring signals 903 from multiple GNSS satellites 904 and determining the distance to and position of GNSS satellite 904 based on the information encoded in the signals 903.

[0130] In some examples, three GNSS satellites 904 are used for triangulation housing positioning 929 or user system positioning 1029, and a fourth GNSS satellite 904 is used to determine clock errors 937. Almanac and ephemeris information 926, 1026 includes information for calculating the position of each GNSS satellite 904 in orbit, as well as information about the time and status of the entire satellite constellation. According to some examples, housing 902 and user system 102 can select different constellations or groups of GNSS satellites 904 to determine housing positioning 929 and user system positioning 1029, respectively.

[0131] In some examples, GNSS receiver components 906 and 1006 include processing circuitry, transceiver circuitry, memory, and one or more antennas. In some examples, GNSS receiver component 906 includes dual-band L1 and L5 GNSS receivers. The dual-band L1 and L5 GNSS receivers are configured to resolve multipath effects, atmospheric transmission effects that distort GNSS position calculations, etc. In some examples, GNSS receiver component 1006 is a single-band L1 GNSS receiver, which may require less power 1008 than a dual-band L1 and L5 GNSS receiver.

[0132] Wireless components 922 and 1022 include a processing circuit system, a transceiver circuit system, a memory, and one or more antennas. Wireless components 922 and 1022 are configured to communicate with each other using communication protocols such as Bluetooth®, Bluetooth Low Energy® (BLE), another IEEE 802.11 communication protocol, or another communication protocol.

[0133] In some examples, GNSS receiver component 906 and wireless component 922 are configured to communicate with each other using a Serial Peripheral Interface (SPI) and / or an Internal Integrated Circuit (I2C). In some examples, GNSS receiver component 1006 and wireless component 1022 are configured to communicate with each other using SPI and / or I2C.

[0134] The functions described herein as being performed by housing 902 and user system 102 can be performed by one or more of GNSS receiver components 906, 1006, radio components 922, 1022, or positioning components 932, 1032, respectively. For example, the acquisition process can be performed by GNSS receiver components 906, 1006, or positioning components 932, 1032.

[0135] User system 102 can be combined as follows: Figure 1 Public user system 102, such as in combination Figure 5 The disclosed wearable device 116 and / or as combined Figure 8 The publicly disclosed glasses 800. The housing 902 can be integrated with, for example, a user system 102, in which a wearable device 116 is located. Figure 5 Public communication with user system 102. Users of user system 102 may want to use applications that frequently request user system location 1029.

[0136] Housing 902 performs a position-fixing operation and transmits information such as tracked satellite information 912, almanac and ephemeris information 926, housing positioning 929, and / or clock error 937 to user system 102. Housing 902 uses wireless component 922 to transmit information to user system 102, and is designed to reduce the power and / or time required for user system 102 to determine user system positioning 1029. Furthermore, the information transmitted by housing 902 to user system 102 enables user system 102 to determine user system positioning 1029 more accurately.

[0137] The tracked satellite information 912 includes a spacecraft identification number (SVID) 914, frequency error 916, a carrier power to noise power ratio (C / N) 918 per unit bandwidth, other information 921, and SVIDs to be avoided indicating one or more satellites to be avoided 920. Other information 921 includes atmospheric delay, frequency Doppler, etc. For example, the housing 902 can determine the optimal SVID 914, frequency error 916, C / N 918, SVIDs to be avoided 918, clock error 937, housing positioning 929, and / or almanac and ephemeris information 926, and transmit the information to the user system 102 via a wireless component 922. The tracked satellite information 912 can be for each GNSS satellite 904 indicated by the SVID 914. For example, each GNSS satellite 904 may have a clock error 937.

[0138] The housing 902 periodically updates information and transmits it to the user system 102 when the user system 102 is used. The housing 902 can determine when to transmit information based on changes in housing positioning 929 exceeding or surpassing a threshold distance. The battery 924 of the housing 902 is larger than the battery 1024 of the user system 102, enabling the housing 902 to perform more positioning fixation operations. Additionally, the user system 102 can be glasses 800 positioned close to the user's head, allowing for better energy and power reduction to minimize heat exposure to the user's head.

[0139] A positioning component 932, which can be implemented in the GNSS receiver component 906, determines the tracked satellite information 912, hull positioning 929, almanac and ephemeris information 926, hull positioning 928, and clock error 937. For example, the positioning component 932 can perform a fixed-resolution operation, which includes an acquisition component 935 and a tracking component 933 to determine the hull positioning 929 and other information. Parameter 931 is a parameter used by the acquisition component 935 and the tracking component 933. The positioning component 932 determines the SVID 914 of the GNSS satellite 904 (which may also be referred to as a spacecraft) for determining the hull positioning 929. In some examples, the positioning component 932 determines the SVID 914 and other information that would be better used by the user system 102 rather than the hull 902.

[0140] For example, positioning component 932 can use the strongest signal 903 to determine housing positioning 929 for dual-band L1 and L5 GNSS receivers, and determine the optimal SVID 914 and other information for the L1 GNSS receiver used by user system 102. According to some examples, positioning components 932 and 1032 control GNSS receiver components 906 and 1006, respectively.

[0141] User system 102 receives information from housing 902 via wireless component 1022, such as tracked satellite information 1012, SVID 1014, frequency error 1016, C / N 1018, SVID to be avoided 1020, almanac and ephemeris information 1026, housing positioning 1028, other information 1021, and clock error 1037. Other information 921 may include atmospheric delay, frequency Doppler, etc. User system 102 avoids acquiring signals from GNSS satellite 904 corresponding to the SVID to be avoided 1020.

[0142] User system 102 uses signal 903 and this information to determine user system location 1029. This information makes it easier for user system 102 to determine user system location 1029. In some examples, positioning unit 1032 initiates positioning fixed solution operation to determine user system location 1029 by acquiring signal 903 of GNSS satellite 904 corresponding to SVID 1014 through an acquisition process performed by acquisition unit 1035.

[0143] Parameter 1031 is a parameter used by the acquisition unit 1035 and the tracking unit 1033. Parameter 1031 includes information received from the housing 902. The acquisition unit 1035 performs an acquisition process to acquire the signal 903 of the GNSS satellite 904. The tracking unit 1033 tracks the acquired GNSS satellite 904. To determine the user system positioning 1029, it is necessary to acquire and track three or four GNSS satellites 904.

[0144] Different constellations of GNSS satellites 904 may exist from which user system 102 can select. SVID 1014 indicates GNSS satellite 904 and therefore indicates the constellation that user system 102 should use.

[0145] The clock error 1037 allows the user system 102 to reduce the number of GNSS satellites 904 that must be acquired and tracked. The clock error 1037 enables the user system 102 to determine the time of the atomic clocks used by the GNSS satellites 904, and this clock error 1037 is encoded in signal 903. Fewer GNSS satellites 904 that must be acquired and tracked allow the user system 102 to determine user system positioning 1029 more quickly and with less energy. Compared to using a separate L1 receiver, the clock error 1037 and frequency error 1016 from housing 902 enable positioning unit 1032 to determine user positioning 1029 more accurately.

[0146] Acquisition component 1035 begins acquiring the corresponding GNSS satellite 904 indicated by SVID 1014 by using the frequency error 1016 provided by housing 902 as a starting point. Using the frequency error 1016 reduces the frequency search window used by acquisition component 1035 for the acquisition process. Frequency error 1016 is parameter 1031 used by acquisition component 1035.

[0147] Additionally, the acquisition unit 1035 can use the C / N 1018 provided by the housing 902. For example, if the value of SVID 1014 is "2" indicating a specific GNSS satellite 904, and the corresponding C / N 1018 value of the GNSS satellite 904 indicated by SVID 1014 is a higher value, then the acquisition unit 1035 updates the parameters 1031 for the acquisition process, which may be referred to as the acquisition loop, and uses a small integration time, such as 250 μS, to obtain frequency lock on the signal 903 of the GNSS satellite 904, and then obtains code lock on the coded signal 903 of the GNSS satellite 904. Frequency lock and code lock indicate that the acquisition unit 1035 has the frequency of the GNSS satellite 904 and is capable of decoding the signal encoded in the signal 903, such as the transmission time of the signal 903.

[0148] In another example, if the value of SVID 1014 is "5" and the corresponding value of C / N 1018 is a low value, then the acquisition component 1035 updates the parameter 1031 used for the acquisition process and uses a longer integration time, such as 1 ms, to obtain frequency lock and code lock on signal 903. In some examples, the integration time can vary from 100 microseconds to 3 milliseconds, or it can be other durations.

[0149] The search time for GNSS satellite 904 with SVID 1014 value "2" will be one-quarter of the time for GNSS satellite 904 with SVID 1014 value "5". This time saving is due to the C / N 1018 value of GNSS satellite 904 being provided by the housing 902, which is assumed to be close to the user system 102.

[0150] Before the acquisition process performed by the acquisition unit 1035 begins, the almanac and ephemeris information 1026 of the GNSS satellite 904, which may be needed to perform the acquisition and tracking processes, can be transmitted to the user system 102 via the wireless unit 905. The user system 102 then does not need to use the GNSS receiver unit 1006 to download the almanac and ephemeris information 1026. Additionally, according to some examples, this can reduce the time required to determine the user system's location 1029 and save energy, since the GNSS receiver unit 1006 uses more energy than the wireless unit 1022.

[0151] In some examples, information from housing 902 enables tracking component 1033 to reduce bandwidth 1010 to 0.05 Hz or another value between 0.01 Hz and 0.10 Hz. Higher accuracy of user acquisition component 1035, using information such as frequency error 1016 and C / N 1018 of GNSS satellite 904, results in reduced bandwidth 1010. The reduced bandwidth 1010, which can instruct tuning or focusing of GNSS receiver component 1006, reduces the power 1008 required by GNSS receiver component 1006. Using lower power 1008 extends the lifespan of battery 1024 before it needs to be recharged.

[0152] The SVID to be avoided is 1020, which is the ID of GNSS satellite 904, which has a stronger multipath effect. Acquiring GNSS satellite 904, which has a stronger multipath effect, takes longer and requires more energy. Additionally, since hull 902 is near user system 102, the tracked satellite information 1012 will be similar for both user system 102 and hull 902.

[0153] Information from housing 902 enables user system 102 to determine user system location 1029 more quickly, so user system 102 can reduce or turn off power to GNSS receiver component 1006, which saves battery 1024.

[0154] User system 102 can securely communicate with housing 902 and exchange information about its location with housing 902 without sharing user system location 1029 outside of housing 902. Using housing 902 to assist user system 102 in determining user system location 1029 does not expose user system 102 to tracking of user system location 1029. Typically, services assisting user system 102 in determining user system location 1029 require at least a general location of user system 102.

[0155] User system 102 can send a request message to housing 902, and housing 902 can actively send information to user system 102. In some examples, housing 902 and / or user system 102 include inertial measurement units (IMUs) 925 and 1025, respectively. When housing 902 or user system 102 moves a small distance, such as one meter or less, positioning components 932 and 1032 can use IMUs 925 and 1025 to adjust housing positioning 929 or user system positioning 1029, respectively. Additionally, positioning components 932 and 1023 can use IMUs 925 and 1025 to determine whether to execute a new positioning fixation solution to determine a new housing positioning 929 or a new user system positioning, and / or to determine whether to activate GNSS receiver components 906 and 1006. For example, user system 102 can turn off the power 1008 of GNSS receiver component 1006 and turn on the power 1008 if the output of IMU 1025 indicates that user system 102 has moved beyond or exceeded a threshold distance.

[0156] Figure 11 A method 1100 for high-precision positioning of a mobile device is illustrated according to some examples. Method 1100 begins at operation 1102 with the housing closed. For example, housing 902 is in a closed state. Method 1100 continues at operation 1104 with the question, "Is the mobile device in the housing?" For example, user system 102 may be inside or outside its housing 902. According to some examples, housing 902 remains closed as long as user system 102 is inside housing 902.

[0157] If the user system 102 is removed from the housing 902, method 1100 continues to operation 1106, which involves connecting the user system using non-GNSS communication. For example, the housing 902 may automatically open when opened. The user system 102 can be removed by the user, and the wireless component 922 of the housing 902 can connect to the wireless component 1022 of the user system 102 via signal 905 using Bluetooth Low Energy® (BLE).

[0158] Method 1100 continues at operation 1108 with the question, "Is the user system outdoors?". For example, user system 102 can determine whether it is outdoors based on reception from GNSS receiver component 1006. If sufficient reception exists, user system 102 can determine that it is outdoors.

[0159] Method 1100 continues at operation 1112 with "Turn on housing GPS". For example, housing 902 turns on its GNSS receiver component 906. Method 1100 continues at operation 1114 with "Does the user system request GNSS information?". If the user system does not request GNSS information, method 1100 continues to operation 1116 to check again whether the user system is outdoors. If the user system is not outdoors, method 1100 continues at operation 1110 to determine whether the mobile device is inside the housing.

[0160] If the user system does request GNSS information, method 1100 continues to operation 1118, which transmits GNSS information to the user system via non-GNSS communication. For example, housing 902 determines housing positioning 929, tracked satellite information 912, almanac and ephemeris information 926, and SVIDs to be avoided 920. The information is transmitted to user system 102 via wireless component 922, which may use Bluetooth Low Energy®. Housing 902 may additionally transmit information to user system 102 without requiring a request from user system 102 to receive the information. For example, housing 902 may query user system 102 to determine whether user system 102 wants to transmit information to user system 102.

[0161] Figure 12 A method 1200 for high-precision positioning of a mobile device is illustrated according to some examples. Method 1200 begins at operation 1202 with receiving an indication of a spacecraft identifier (SVID) and an indication of the frequency error of the spacecraft indicated by the SVID via a wireless communication protocol. For example, housing 902 uses BLE to transmit information such as SVID 914 and frequency error 916 to user system 102 via wireless component 922. Method 1200 then performs an acquisition process for a signal from the spacecraft at operation 1204, using the frequency error as a starting frequency. For example, acquisition component 1035 can use the frequency error 1016 as a starting point to perform the acquisition process for a GNSS satellite 904 indicated by SVID 1014 received from housing 902 to obtain the GNSS satellite 904 indicated by SVID 1014.

[0162] Additional information from the housing enables the mobile receiver to achieve significantly better positional accuracy than a standalone single-band receiver. Power consumption remains lower than that of a standalone single-band receiver.

[0163] Method 1200 may optionally include one or more additional operations, the operations of method 1200 may be performed in different orders, or one or more operations of method 1200 may be optional. Method 1200 may be performed wholly or partially by one or more computing devices or means of one or more computing devices disclosed herein, such as user system 102, glasses 800, or wearable device 116. The function of a component, such as positioning component 932, may be performed or operated by one or more computing devices configured to perform or execute the function of that component.

[0164] Glossary

[0165] "Carrier signal" refers to any intangible medium, such as a medium capable of storing, encoding, or carrying instructions to be executed by a machine and including digital or analog communication signals, or other intangible medium that facilitates the communication of such instructions. Instructions can be sent or received over a network using a transmission medium via a network interface device.

[0166] "Client device" means any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. Client devices can be, but are not limited to, mobile phones, desktop computers, laptop computers, portable digital assistants (PDAs), smartphones, tablet computers, ultrabooks, netbooks, laptop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user can use to access the network.

[0167] "Communication network" means, for example, one or more parts of a network, which can be an ad hoc network, intranet, extranet, virtual private network (VPN), local area network (LAN), wireless LAN (WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a Common Old-Style Telephone Service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, other types of networks, or a combination of two or more such networks. For example, a network or part of a network may include a wireless network or a cellular network, and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, or other types of cellular or wireless coupling. In this example, coupling can enable any data transmission technology of various types, such as single-carrier radio transmission technology (1xRTT), evolved data optimization (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate GSM evolution (EDGE) technology, the 3rd Generation Partnership Project (3GPP) including 3G, fourth-generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA), Global Microwave Access Interoperability (WiMAX), Long Term Evolution (LTE) standards, other data transmission technologies defined by various standards setting organizations, other long-distance protocols, or other data transmission technologies.

[0168] A “component” or “module” refers to a logical or physical entity having boundaries defined by functional or subroutine calls, branch points, APIs, or other technical definitions that partition or modularize a particular processing or control function. A component or module can be combined with other components via its interface to perform machine processing. A component or module can be an encapsulated functional hardware unit designed for use with other components, and part of a program that typically performs a related function. A component or module can constitute a software component (e.g., code implemented on a machine-readable medium) or a hardware component. A “hardware component” or “hardware module” is a tangible unit capable of performing certain operations and can be configured or arranged in some physical manner. In various examples, one or more hardware components (e.g., processors or processor groups) or software components of a computer system (e.g., a standalone computer system, a client computer system, or a server computer system) or a computer system can be configured by software (e.g., an application or application portion) to operate to perform certain operations as described herein. Hardware components or hardware modules can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component or hardware module may include dedicated circuitry or logic permanently configured to perform certain operations. The hardware component or hardware module may be a dedicated processor, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A hardware component or hardware module may also include programmable logic or circuitry temporarily configured by software to perform certain operations. For example, a hardware component or hardware module may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a particular machine (or a specific part of a machine) uniquely tailored to perform the configured function and is no longer a general-purpose processor. It will be appreciated that a decision may be made, for cost and time considerations, whether to implement the hardware component or hardware module mechanically in a dedicated and permanently configured circuit or in a temporarily configured (e.g., software-configured) circuit. Therefore, the phrase “hardware component” (or “hardware-implemented component”) should be understood to include tangible entities, i.e., entities physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate or perform certain operations described herein. Consider an example where hardware components are temporarily configured (e.g., programmed), without requiring each hardware component to be configured or instantiated at any given time. For instance, in a case where the hardware components include a general-purpose processor that is configured by software to become a dedicated processor, the general-purpose processor can be configured at different times as its own distinct dedicated processor (e.g., including different hardware components).The software accordingly configures one or more specific processors to constitute a particular hardware component at one time and different hardware components at different times. Hardware components or modules can provide information to and receive information from other hardware components. Therefore, the described hardware components or modules can be considered communicatively coupled. In the case of multiple hardware components present simultaneously, communication can be achieved through signal transmission between or among two or more hardware components (e.g., via appropriate circuitry and buses). In examples where multiple hardware components are configured or instantiated at different times, such communication between hardware components can be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving information from the memory structure. For example, a hardware component can perform an operation and store the output of that operation in a memory device communicatively coupled to it. Another hardware component or module can then access the memory device at a subsequent time to retrieve and process the stored output. Hardware components can also initiate communication with input or output devices and can operate on resources (e.g., collections of information). The various operations of the example methods described herein can be performed, at least in part, by one or more processors configured temporarily (e.g., by software) or permanently to perform the relevant operations. Whether temporarily or permanently configured, such processors can constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the methods described herein can be implemented at least in part by processors, where a particular processor or one or more processors are examples of hardware. For example, at least some of the various operations of the methods can be performed by one or more processors or processor-implemented components. Furthermore, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "Software as a Service" (SaaS) operation. For example, at least some of the operations can be performed by a group of computers (as an example of a machine including processors), where these operations are accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The execution of some operations can be distributed among processors, not residing within a single machine, but deployed across multiple machines. In some examples, processors or processor-implemented components can be located in a single geographic location (e.g., within a home environment, an office environment, or a server cluster). In other examples, the processor or processor-implemented components can be distributed across multiple geographical locations.

[0169] "Computer-readable storage medium" refers to both, for example, machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" refer to the same thing and can be used interchangeably in this disclosure.

[0170] A "brief message" is a message that is accessible for a limited time, such as a short period of time. Brief messages can be text, images, videos, etc. The access time for a brief message can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting method, the message is temporary.

[0171] "Machine storage medium" refers to one or more storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Therefore, this term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium," "device storage medium," and "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium," "computer storage medium," and "device storage medium" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered by the term "signal medium."

[0172] "Non-transitory computer-readable storage medium" means, for example, a tangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine.

[0173] "Signal medium" means any intangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal whose characteristics are set or altered in a manner that encodes information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

[0174] "User equipment" means, for example, a device that is accessed, controlled, or owned by a user, and that the user interacts with to perform actions or interact with other users or computer systems. Other claimable topics include the following:

[0175] Example 1 is a computing device comprising: one or more processors; and one or more memories storing instructions that, when executed by one or more processors, configure one or more processors to perform operations including: receiving an indication of a spacecraft identifier (SVID) and an indication of a frequency error of the spacecraft indicated by the SVID via a wireless communication protocol; and acquiring a signal from the spacecraft using the frequency error as a starting frequency.

[0176] In Example 2, the subject of Example 1 includes, where the wireless communication protocol is Bluetooth Low Energy®.

[0177] In Example 3, the subject matter of any one of Examples 1 to 2 includes, wherein receiving further includes: receiving a ratio (C / N) of carrier power to noise power per unit bandwidth; and wherein acquiring further includes: determining the integration time based on C / N, and acquiring the signal from the spacecraft using the frequency error as the starting frequency error and the integration time.

[0178] In Example 4, the subject of Example 3 includes, where the integration time is from 100 microseconds to 3 milliseconds.

[0179] In Example 5, the subject matter of any one of Examples 1 to 4 includes, wherein the operation further includes: receiving almanac and ephemeris data of a spacecraft indicated by SVID via a wireless communication protocol; and using the frequency error as a starting frequency error and using the almanac and ephemeris data to acquire signals from the spacecraft.

[0180] In Example 6, the subject of any of Examples 1 through 5 includes an L1 Global Navigation Satellite System (GNSS) receiver coupled to one or more memories, wherein signals received from the GNSS receiver are acquired using data.

[0181] In Example 7, the subject matter of any one of Examples 1 to 6 includes, wherein the operation further includes: acquiring signals from one or more additional spacecraft; and tracking the spacecraft and one or more additional spacecraft to determine the location of the computing device.

[0182] In Example 8, the subject of Example 7 includes, wherein the computing device is a first computing device and the position is a first position, and wherein receiving further includes: receiving SVID and an indication of the spacecraft’s frequency error indicated by SVID from a second computing device via a wireless communication protocol, and wherein operation further includes: adjusting the first position based on the second position.

[0183] In Example 9, the subject matter of any one of Examples 7 to 8 includes, wherein the SVID is a first SVID, the spacecraft is a first spacecraft, and wherein receiving further includes: receiving a second SVID, the second SVID indicating a second spacecraft; and wherein the operation further includes: avoiding acquiring signals from the second spacecraft.

[0184] In Example 10, the subject of any of Examples 1 through 9 includes, wherein the operation further includes: performing a tracking process on the spacecraft using a lower power mode.

[0185] In Example 11, the subject of Example 10 includes a lower power mode between 0.01 Hz and 0.1 Hz.

[0186] In Example 12, the subject matter of any one of Examples 1 to 11 includes, wherein receiving further includes: receiving clock errors; and performing a position-fixing solution by using clock errors to reduce the number of spacecraft.

[0187] In Example 13, the subject matter of any one of Examples 1 to 12 includes, wherein receiving further includes: receiving information from the housing, the information including at least one of the following: clock error, indication of one or more additional SVIDs, indication of one or more additional spacecraft frequency errors indicated by one or more additional SVIDs, a ratio (C / N) of one or more unit bandwidth carrier power to noise power, indication of one or more SVIDs to be avoided, one or more atmospheric delays, one or more frequency errors, one or more Doppler shifts, almanac and ephemeris information, and clock error; and using the information to perform a positioning fixed solution for the computing device.

[0188] In Example 14, the subject of any of Examples 1 through 13 includes, wherein, acquiring code locking and frequency locking of signals from a spacecraft is achieved.

[0189] In Example 15, the subject of Example 14 includes the following: the acquisition is performed without directly downloading almanacs and ephemeris information from satellites.

[0190] In Example 16, the subject of any one of Examples 1 to 15 includes, wherein the computing device is a wearable electronic device configured for one or more of the following: augmented reality (AR), mixed reality (MR), virtual reality (VR), or extended reality (XR).

[0191] In Example 17, the subject of any of Examples 15 to 16 includes, wherein the indication of SVID is received from the housing of the computing device.

[0192] Example 18 is a non-transitory computer-readable storage medium including instructions that, when processed by one or more processors, configure one or more processors to perform operations including: receiving an indication of a spacecraft identifier (SVID) and an indication of a frequency error of the spacecraft indicated by the SVID via a wireless communication protocol; and acquiring a signal from the spacecraft using the frequency error as a starting frequency.

[0193] In Example 19, the subject matter of Example 18 includes, wherein receiving further includes: receiving a ratio (C / N) of carrier power to noise power per unit bandwidth; and wherein acquiring further includes: determining an integration time based on C / N, and acquiring a signal from the spacecraft using a frequency error as a starting frequency error and using the integration time.

[0194] Example 20 is a method executed by at least one processor, the method comprising: receiving an indication of a spacecraft identifier (SVID) and an indication of a frequency error of the spacecraft indicated by the SVID via a wireless communication protocol; and acquiring a signal from the spacecraft using the frequency error as a starting frequency.

[0195] Example 21 is at least one machine-readable medium including instructions that, when executed by a processing circuitry system, cause the processing circuitry to perform operations for implementing any one of Examples 1 to 20.

[0196] Example 22 is an apparatus that includes means for implementing any one of Examples 1 to 20.

[0197] Example 23 is a system for implementing any one of Examples 1 through 20.

Claims

1. A computing device, comprising: One or more processors; as well as One or more memories storing instructions that, when executed by the one or more processors, configure the one or more processors to perform operations, the operations including: The spacecraft identification number (SVID) and the frequency error of the spacecraft indicated by the SVID are received via a wireless communication protocol. as well as The frequency error is used as the starting frequency to acquire signals from the spacecraft.

2. The computing device according to claim 1, wherein, The wireless communication protocol is Bluetooth Low Energy®.

3. The computing device according to claim 1, wherein, The receiving also includes: The ratio of carrier power to noise power per unit bandwidth (C / N); wherein, the acquisition further includes: The integration time is determined based on the C / N ratio, and The frequency error is used as the starting frequency error, and the integration time is used to acquire the signal from the spacecraft.

4. The computing device according to claim 3, wherein, The integration time is from 100 microseconds to 3 milliseconds.

5. The computing device according to claim 1, wherein, The operation also includes: Receive, via the wireless communication protocol, the almanac and ephemeris data of the spacecraft indicated by the SVID; and The frequency error is used as the starting frequency error, and the signals from the spacecraft are obtained using the almanac and ephemeris data.

6. The computing device according to any one of claims 1 to 5, further comprising: An L1 Global Navigation Satellite System (GNSS) receiver coupled to one or more of the memories, wherein the acquisition uses signals received from the GNSS receiver.

7. The computing device according to any one of claims 1 to 5, wherein, The operation also includes: Acquiring signals from one or more additional spacecraft; and Track the spacecraft and the one or more attached spacecraft to determine the location of the computing device.

8. The computing device according to claim 7, wherein, The computing device is a first computing device, and the location is a first location, wherein the receiving further includes: Receiving the SVID and an indication of the spacecraft's frequency error indicated by the SVID from a second computing device via the wireless communication protocol, wherein the operation further includes: Adjust the first position based on the second position.

9. The computing device according to claim 7, wherein, The SVID is a first SVID, the spacecraft is a first spacecraft, and the receiving further includes: Receive a second SVID, which indicates a second spacecraft; and wherein the operation further includes: Avoid receiving signals from the second spacecraft.

10. The computing device according to any one of claims 1 to 5, wherein, The operation also includes: The spacecraft was tracked using a lower power mode.

11. The computing device according to claim 10, wherein, The lower power mode is between 0.01 Hz and 0.1 Hz.

12. The computing device according to any one of claims 1 to 5, wherein, The receiving also includes: Receive clock error; and The position-fixed solution is performed by using the clock error to reduce the spacecraft's position.

13. The computing device according to any one of claims 1 to 5, wherein, The receiving also includes: Information received from the housing includes at least one of the following: clock error, indication of one or more additional SVIDs, indication of one or more frequency errors of one or more additional spacecraft indicated by the one or more additional SVIDs, one or more carrier power to noise power ratios (C / N) per unit bandwidth, indication of one or more SVIDs to be avoided, one or more atmospheric delays, one or more frequency errors, one or more Doppler shifts, and clock error; and Use information to perform a location fixation solution for the computing device.

14. The computing device according to any one of claims 1 to 5, wherein, The acquisition achieves code locking and frequency locking of signals from the spacecraft.

15. The computing device according to claim 14, wherein, The acquisition, tracking, and location fixing solution is performed without directly downloading almanacs and ephemeris information from satellites.

16. The computing device according to any one of claims 1 to 5, wherein, The computing device is a wearable electronic device configured for one or more of the following: augmented reality (AR), mixed reality (MR), virtual reality (VR), or extended reality (XR).

17. The computing device according to claim 15, wherein, The SVID indication is received from the housing of the computing device.

18. A non-transitory computer-readable storage medium comprising instructions that, when processed by one or more processors, configure the one or more processors to perform operations, the operations including: The spacecraft identification number (SVID) and the frequency error of the spacecraft indicated by the SVID are received via a wireless communication protocol. as well as The frequency error is used as the starting frequency to acquire signals from the spacecraft.

19. The non-transitory computer-readable storage medium according to claim 18, wherein, The receiving further includes: receiving the ratio of carrier power to noise power per unit bandwidth (C / N); and wherein the acquiring further includes: The integration time is determined based on the C / N ratio, and The frequency error is used as the starting frequency error, and the integration time is used to acquire the signal from the spacecraft.

20. A method executed by at least one processor, the method comprising: The spacecraft identification number (SVID) and the frequency error of the spacecraft indicated by the SVID are received via a wireless communication protocol. as well as The frequency error is used as the starting frequency to acquire signals from the spacecraft.

Images