Recreating peripheral vision on wearable device

Abstract

A head wearable device includes a frame having a front piece configured to receive a left lens and a right lens. The left temple is coupled to the front piece, and the right temple is coupled to the front piece. The camera system includes one or more cameras coupled to the front piece, one or more left peripheral cameras coupled to the outer surface of the frame, and one or more right peripheral cameras coupled to the outer surface of the frame. The left peripheral display is coupled to an inner surface of the frame. The left peripheral display is configured to receive and display input from the one or more left peripheral camera devices. The right peripheral display is coupled to an inner surface of the frame. The right peripheral display is configured to receive and display input from one or more right peripheral camera devices.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. patent application serial number 18 / 111,782, filed on February 20, 2023, which is incorporated herein by reference in its entirety.

[0003] BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0004] In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest-order digit or digits in a reference numeral refer to the figure in which the element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0005] Figure 1 is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, according to some examples.

[0006] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality, according to some examples.

[0007] Figure 3 is a diagrammatic representation of data structures maintained in a database according to some examples.

[0008] Figure 4 is a diagrammatic representation of messages according to some examples.

[0009] Figure 5 A system including a head wearable device according to some examples is shown.

[0010] Figure 6 An example of an AR wearable device with a pass-through peripheral camera and display is shown, according to some examples.

[0011] Figure 7 A process for displaying content to a user's peripheral vision is shown, according to some examples.

[0012] Figure 8 is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions may be executed, causing the machine to perform any one or more of the methodologies discussed herein, according to some examples.

[0013] Figure 9 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0014] Augmented reality (AR) wearables such as AR glasses may place most of their components inside the temples, resulting in bulky temples that may reduce the user's peripheral vision. This can be particularly annoying while driving.

[0015] Embodiments of the present disclosure improve upon the functionality of current AR glasses by including peripheral vision cameras and pass-through displays, projectors, or a combination thereof to recreate the user's peripheral vision. For example, the AR system described herein may use outward-facing cameras and displays inside the temples to recreate peripheral vision. The displays and cameras may have low resolutions and high refresh rates to maintain power efficiency when compared to traditional forward-facing cameras. In one example, the display in the AR system may be manually activated by the user via a button or voice. Alternatively, the display in the AR system may be automatically activated when the wearable device detects a driving mode or other mode that can utilize peripheral vision enhancement. The terms "display" and "projector" may be used interchangeably herein. It should be understood that any reference to a display or projector may refer to a display, a projector, or any combination thereof.

[0016] In some examples, the image fed into the display may also be the result of an image created using machine learning techniques. A machine learning algorithm may be used to adjust the image fed into the display (or camera feed) to reflect what the user should see on the other side of the temple of the system. For example, the adjusted camera feed may be adjusted based on camera positioning and adjustment, actual eyeglass adjustment, user eye measurements, or any combination thereof.

[0017] Thus, the system's peripheral display can provide a higher field of view while wearing AR glasses with, for example, thick temples by creating the illusion that the temples are not present. By providing the user with a clearer vision unobstructed by the AR system's temples, the AR system addresses a potential safety issue for the user while driving.

[0018] Networked computing environment

[0019] Figure 11 is a block diagram illustrating an example interactive system 100 for facilitating interactions over a network (e.g., exchanging text messages, conducting text, audio, and video calls, or playing games). The interactive system 100 includes multiple client systems 102, each of which hosts multiple applications including an interactive client 104 and other applications 106. Each interactive client 104 is communicatively coupled to other instances of the interactive client 104 (e.g., hosted on respective other user systems 102), an interactive server system 110, and third-party servers 112 via one or more communication networks including a network 108 (e.g., the Internet). The interactive client 104 can also communicate with the locally hosted applications 106 using an application programming interface (API).

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

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

[0022] The interactive server system 110 provides server-side functionality to the interactive clients 104 via the network 108. Although certain functions of the interactive system 100 are described herein as being performed by either the interactive client 104 or the interactive server system 110, the location of certain functions within the interactive client 104 or within the interactive server system 110 may be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the interactive server system 110, but later migrate the technologies and functions to the interactive client 104 where the user system 102 has sufficient processing power.

[0023] The interactive server system 110 supports various services and operations provided to the interactive clients 104. Such operations include sending data to the interactive clients 104, receiving data from the interactive clients 104, and processing data generated by the interactive clients 104. The 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. The data exchange within the interactive system 100 is activated and controlled by functions available through the user interface (UI) of the interactive client 104.

[0024] Turning now specifically to the interaction server system 110, an application program interface (API) server 122 is coupled to the interaction server 124 and provides a programming interface thereto, making the functionality of the interaction server 124 accessible to the interaction clients 104, other applications 106, and third-party servers 112. The interaction server 124 is communicatively coupled to a database server 126, thereby facilitating access to a database 128 that stores data associated with interactions processed by the interaction server 124. Similarly, a web server 130 is coupled to the interaction server 124 and provides a web-based interface to the interaction server 124. To this end, the web server 130 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0025] The application program interface (API) server 122 receives and sends interaction data (e.g., commands and message payloads) between the interaction server 124 and the client system 102 (and, for example, the interaction client 104 and other applications 106), as well as the third-party server 112. Specifically, the application program interface (API) server 122 provides a set of interfaces (e.g., routines and protocols) that the interaction client 104 and other applications 106 can call or query to activate the functionality of the interaction server 124. The application program interface (API) server 122 exposes various functions supported by the interaction server 124, including account registration; login functionality; sending interaction data from a particular interaction client 104 to another interaction client 104 via the interaction server 124; transferring media files (e.g., images or videos) from the interaction client 104 to the interaction server 124; setting up a collection of media data (e.g., a story); retrieving a friend list of a user of the user system 102; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to the interaction client 104).

[0026] Interactive server 124 hosts multiple systems and subsystems, see below Figure 2 Provide a description.

[0027] Linked application

[0028] Returning to the interactive client 104, the features and functionality of the external resource (e.g., the linked application 106 or applet) are made available to the user via the interface of the interactive client 104. In this context, "external" refers to the fact that the application 106 or applet is external to the interactive client 104. External resources are typically provided by a third party, but may also be provided by the creator or provider of the interactive client 104. The interactive client 104 receives a user selection of an option to launch or access features of such an external resource. The external resource can be an application 106 installed on the user system 102 (e.g., a "local app"), or a small-scale version of an application (e.g., a "mini-program") hosted on the user system 102 or located remotely from the user system 102 (e.g., on a third-party server 112). The small-scale version of an application includes a subset of the features and functionality of the application (e.g., the full-scale, local version of the application) and is implemented using a markup language document. In some examples, the small-scale version of an application (e.g., a "mini-program") is a web-based markup language version of the application and is embedded in the interactive client 104. In addition to using markup language documents (eg, .*ml files), applet may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

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

[0030] 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 (for example) a third-party server 112 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.

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

[0032] The interactive client 104 can present a list of available external resources (e.g., applications 106 or applets) to the user to launch or access a given external resource. The list can be presented in the form of a context-sensitive menu. For example, the icons representing different applications (or applets) of the application 106 (or applets) can change based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0033] System Architecture

[0034] Figure 2 1 is a block diagram illustrating additional details regarding 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 a plurality of subsystems that 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.

[0035] Image processing system 202 provides various functions that enable a user to capture and enhance (eg, annotate or otherwise modify or edit) media content associated with a message.

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

[0037] The enhancement system 206 provides functionality related to the generation and publication of enhancements (e.g., media overlays) for images captured in real time by the camera of the user system 102 or retrieved from the memory of the user system 102. For example, the enhancement system 206 is operable to select, present, and display media overlays (e.g., image filters or image lenses) for the interactive client 104 for enhancing the real-time imagery received via the camera system 204 or the stored imagery retrieved from the memory 502 of the user system 102. These enhancements are selected and presented to the user of the interactive client 104 by the enhancement system 206 based on inputs and data, such as:

[0038] The geographic location of the user system 102; and

[0039] Social network information of users of the user system 102 .

[0040] The enhancement may include audio and visual content and visual effects. Examples of audio and visual content include pictures, 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 systems 102 for transmitting in messages, or may be applied to video content such as video content streams or feeds sent from interactive clients 104. Therefore, image processing system 202 may interact with and support various subsystems of communication system 208, such as messaging system 210 and video communication system 212.

[0041] Media overlays can include text or image data that can be superimposed on a photo taken by user system 102 or a video stream produced by user system 102. In some examples, the media overlay can be a location overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, image processing system 202 uses the geographic location of user system 102 to identify a media overlay that includes the name of a business at the geographic location of user system 102. The media overlay may include other tags associated with the business. The media overlay may be stored in database 128 and accessed by database server 126.

[0042] Image processing system 202 provides a user-based publishing platform that enables users to select a geographic location on a map and upload content associated with the selected geographic location. Users can also specify situations in which specific 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.

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

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

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

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

[0047] The collection management system 224 is operationally responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, video, 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 made available as a "story" for the duration of the concert. The collection management system 224 is also responsible for publishing an icon to the user interface of the interactive client 104 that provides notification of a particular collection. The collection management system 224 includes curation functionality that enables 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). In addition, the collection management system 224 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, users can 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 use of their content.

[0048] The mapping system 226 provides various geolocation capabilities and supports the presentation of map-based media content and messages by the interactive client 104. For example, the mapping system 226 enables the display of user icons or avatars (e.g., stored in the profile data 302) 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, a message posted by a user to the interactive system 100 from a particular geographic location can be displayed to a particular user's "friends" within the context of that particular location on the map on the map interface of the interactive client 104. A user can also share his or her location and status information with other users of the interactive system 100 via the 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 the interactive client 104.

[0049] The gaming system 228 provides various gaming functions within the context of the interactive client 104. The interactive client 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the interactive client 104 and played with other users of the interactive system 100. The interactive system 100 also enables a particular user to invite other users to play a particular game by sending an invitation to such other users from the interactive client 104. The interactive client 104 also supports voice, video, and text messaging (e.g., chat) within the context of game play, provides leaderboards for games, and also supports the provision of in-game rewards (e.g., game coins and items).

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

[0051] To integrate the SDK's functionality into a web-based resource, the third-party server 112 downloads the SDK from the interaction server 124, or the third-party server 112 receives the SDK in some other manner. 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 interaction client 104 into the web-based resource.

[0052] The SDK stored on the interactive server system 110 effectively provides a bridge between external resources (e.g., applications 106 or applet) and the interactive client 104. This gives the user a seamless experience of communicating with other users on the interactive client 104 while also preserving the look and feel of the interactive client 104. In order to bridge the 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 one-way 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 a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0053] 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 resource. Each third-party server 112 provides an HTML5 file corresponding to the web-based external resource to the interactive server 124. The interactive server 124 can add a visual representation of the web-based external resource (e.g., a box design or other graphics) in the interactive client 104. Once the user selects the visual representation or instructs the interactive client 104 to access a feature of the web-based external resource through the GUI of the interactive client 104, the interactive client 104 obtains the HTML5 file and instantiates the resource for accessing the feature of the web-based external resource.

[0054] The interactive client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the interactive client 104 determines whether the launched external resource has previously been authorized to access the user data of the interactive client 104. In response to determining that the launched external resource has previously been authorized to access the user data of the interactive client 104, the interactive client 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not previously been authorized to access the user data of the interactive client 104, after displaying the login page or title screen of the external resource for a threshold period of time (e.g., 3 seconds), the interactive client 104 slides up a menu (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen) for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource is authorized to use. In response to receiving a user selection of the accept option, the interactive client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the interactive client 104. External resources are authorized by the interactive client 104 to access user data under the OAuth 2 framework.

[0055] The interaction client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, an external resource comprising a full-scale application (e.g., application 106) is provided with access to a first type of user data (e.g., a two-dimensional avatar of the user with or without different avatar characteristics). As another example, an external resource comprising a small-scale version of an application (e.g., a web-based version of the application) is provided with access to a second type of user data (e.g., payment information, a two-dimensional avatar of the user, a three-dimensional avatar of the user, and an avatar with various avatar characteristics). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0056] The advertising system 232 operatively enables third parties to purchase advertisements for presentation to end users via the interactive clients 104 and also handles the delivery and presentation of these advertisements.

[0057] The recovery system 234 monitors that all systems are running correctly after the OTA update and initiates the recovery process described herein if the systems are not running correctly.

[0058] Data Architecture

[0059] Figure 3is a diagram illustrating a data structure 300 that may be stored in a database 304 of the interactive server system 110 according to certain examples. Although the contents of the database 304 are shown as including a plurality of tables, it should be understood that data may be stored in other types of data structures (e.g., an object-oriented database).

[0060] The database 304 includes message data stored in the message table 306. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data and payload. Figure 3 Additional details regarding information that may be included in a message and included within the message data stored in message table 306 are described.

[0061] The entity table 308 stores entity data and is linked (e.g., by reference) to the entity graph 310 and the profile data 302. Entities for which records are maintained within the entity table 308 may include individuals, corporate entities, organizations, objects, places, events, and the like. Regardless of the entity type, any entity for which the interactive server system 110 stores data may be an identified entity. Each entity is provided with a unique identifier and an entity type identifier (not shown).

[0062] The entity graph 310 stores information related to relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working at a common company or organization), interest-based, or activity-based. Some relationships between entities may be unidirectional, such as a subscription by an individual user to digital content from a business or publication (e.g., a newspaper or other digital media channel or brand). Other relationships may be bidirectional, such as a "friend" relationship between various users of the interactive system 100.

[0063] Certain permissions and relationships can be attached to each relationship, and can also be attached to each direction of the relationship. For example, a two-way relationship (e.g., a friend relationship between individual users) can include authorization to publish digital content items between the individual users, but can impose certain restrictions or filters on the publication 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 publication of digital content from the business user to the individual user, and can significantly limit or prevent the publication of digital content from the individual user to the business user. As an example of an entity, a particular user can record certain restrictions in the record for that entity within the entity table 308 (e.g., through privacy settings). Such privacy settings can apply to all types of relationships in the context of the interactive system 100, or can be selectively applied to certain types of relationships.

[0064] Profile data 302 stores various types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 302 can be selectively used and presented to other users of the interactive system 100. In the case where the entity is a person, 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 collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the interactive system 100 and on a map interface displayed to other users by the interactive client 104. The collection of avatar representations can include a "status avatar," which presents a graphical representation of the user's status or activity that they may choose to transmit at a particular time.

[0065] Where the entity is a group, the profile data 302 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings for the relevant group (eg, notifications).

[0066] 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).

[0067] In some examples, filters are displayed as overlays on an image or video during presentation to a recipient user. Filters can be of various types, including filters selected by a user from a set of filters presented to a sending user by the interactive client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also known as geofilters), which can be presented to a sending user based on a geographic location. For example, a geolocation filter specific to a nearby or special location can be presented within a user interface by the interactive client 104 based on geographic location information determined by a global positioning system (GPS) unit of the user system 102.

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

[0069] Other augmented data that can be stored in the image table 316 include augmented reality content items (e.g., corresponding to application "lenses" or augmented reality experiences). Augmented reality content items can be real-time special effects and sounds that can be added to images or videos.

[0070] The story table 318 stores data about a collection of messages and associated images, video, or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user for whom a record is maintained in the entity table 308). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by that user. To this end, the user interface of the interactive client 104 can include a user-selectable icon that enables the sending user to add specific content to his or her personal story.

[0071] 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 common location event at a particular time can be presented with the option to contribute content to a particular live story, for example, via the user interface of the interactive client 104. Live stories can be identified to the user by the interactive client 104 based on his or her location. The end result is a "live story" told from the perspective of the group.

[0072] Another type of content collection is called a "location story," which enables users whose user systems 102 are located in a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some examples, contributions to location stories may employ secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).

[0073] As mentioned above, video table 314 stores video data that, in some examples, is associated with messages whose 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 the various images and videos stored in image table 316 and video table 314.

[0074] Data communication architecture

[0075] Figure 4is a schematic diagram illustrating the structure of a message 400 according to some examples, the message 400 being generated by an interaction client 104 for transmission to another interaction client 104 via an interaction server 124. The content of a particular message 400 is used to populate a message table 306 stored within a database 304 accessible by the interaction server 124. Similarly, the content of the message 400 is stored in memory as "in-transit" or "in-flight" data of the user system 102 or the interaction server 124. The message 400 is shown as including the following example components:

[0076] Message identifier 402 : A unique identifier that identifies the message 400 .

[0077] Message text payload 404 : Text to be generated by the user via the user interface of the user system 102 and included in the message 400 .

[0078] • Message image payload 406: Image data captured by the camera 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 a message 400 sent or received may be stored in the image table 316.

[0079] • Message video payload 408: Video data captured by the camera component or retrieved from the memory component of the user system 102 and included in the message 400. The video data for a message 400 sent or received may be stored in the image table 316.

[0080] • Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the user system 102 and included in the message 400 .

[0081] Message enhancement data 412: Enhancement data (e.g., filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of the message 400. Enhancement data for a sent or received message 400 may be stored in the enhancement table 312.

[0082] • Message duration parameter 414: A parameter value indicating the amount of time, in seconds, that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) is to be presented to or made accessible to the user via the interactive client 104.

[0083] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​may be included in the payload, with each of these parameter values ​​being 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).

[0084] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in stories table 318) associated with a particular 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 content collections.

[0085] Message tags 420: Each message 400 can be tagged with a plurality of tags, each of which indicates the subject matter of the content included in the message payload. For example, if a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value can be included within the message tags 420 indicating the relevant animal. The tag value can be manually generated based on user input, or can be automatically generated using, for example, image recognition.

[0086] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the user system 102 on which the message 400 was generated and from which the message 400 was sent.

[0087] • Message recipient identifier 424: Indicates an identifier (eg, a messaging system identifier, email address, or device identifier) ​​of the user of user system 102 to which message 400 is addressed.

[0088] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table where the content data value is stored. For example, the image value in message image payload 406 may be a pointer to a location in image table 316 (or the address of a location in image table 316). Similarly, the value in message video payload 408 may point to data stored in image table 316, the value stored in message enhancement data 412 may point to data stored in enhancement table 312, the value stored in message story identifier 418 may point to data stored in story table 318, and the values ​​stored in message sender identifier 422 and message recipient identifier 424 may point to user records stored in entity table 308.

[0089] System with head wearable device

[0090] Figure 5 A system 500 including a head wearable device 116 is shown according to some examples. Figure 5 is a high-level functional block diagram of an example head wearable device 116 communicatively coupled to a mobile device 114 and various server systems 504 (eg, interactive server system 110 ) via various networks 108 .

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

[0092] The mobile device 114 is connected to the head wearable device 116 using both a low power wireless connection 512 and a high speed wireless connection 514. The mobile device 114 is also connected to the server system 504 and the network 516.

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

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

[0095] The head-wearable device 116 includes a frame and temples extending from lateral sides of the frame. The head-wearable device 116 also includes a user input device 528 (e.g., a touch sensor or a push button), comprising an input surface on the head-wearable device 116. The user input device 528 (e.g., a touch sensor or a push button) is used to receive input selections from the user for manipulating the graphical user interface of the presented image.

[0096] Figure 5 The components of the head wearable device 116 shown in FIG are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the bezel or temples. Alternatively or additionally, the depicted components may be located in a block, frame, hinge, or nosepiece of the head wearable device 116. The left and right visible light cameras 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 capturing elements that can be used to capture data, including images of a scene with an unknown object.

[0097] The head 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.

[0098] like Figure 5 As shown, high-speed circuitry 526 includes a high-speed processor 530, memory 502, and high-speed wireless circuitry 532. In some examples, image display driver 520 is coupled to high-speed circuitry 526 and operated by high-speed processor 530 to drive the left and right image displays of image display 518 of the optical assembly. High-speed processor 530 can be any processor capable of managing high-speed communications and operations required by any general-purpose computing system for head wearable device 116. High-speed processor 530 includes the processing resources required to manage high-speed data transmission over high-speed wireless connection 514 to a wireless local area network (WLAN) using high-speed wireless circuitry 532. In some examples, high-speed processor 530 executes an operating system (e.g., a Linux operating system) or other such operating system for head wearable device 116, and the operating system is stored in memory 502 for execution. In addition to any other responsibilities, high-speed processor 530, which executes the software architecture of head wearable device 116, manages data transmission with high-speed wireless circuitry 532. In some examples, high-speed wireless circuitry 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, high-speed wireless circuitry 532 can implement other high-speed communication standards.

[0099] The low-power wireless circuitry 534 and high-speed wireless circuitry 532 of the head wearable device 116 may include a short-range transceiver (Bluetooth TM ) and a wireless wide area network transceiver, a wireless local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). Mobile device 114, including transceivers for communicating via low-power wireless connection 512 and high-speed wireless connection 514, can be implemented using details of the architecture of head wearable device 116, as can other elements of network 516.

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

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

[0102] The head-worn device 116 is connected to a host computer. For example, the head-worn device 116 is paired with the mobile device 114 via a high-speed wireless connection 514 or is connected to a server system 504 via a network 516. The server system 504 can be one or more computing devices that are part of a service or network computing system, for example, including a processor, memory, and a network communication interface to communicate with the mobile device 114 and the head-worn device 116 via the network 516.

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

[0104] The output components of the head wearable device 116 include visual components, such as a display (e.g., 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 assembly is driven by the image display driver 520. The output components of the head wearable device 116 also include acoustic components (e.g., a speaker), tactile components (e.g., a vibration motor), other signal generators, etc. The input components of the head wearable device 116, the mobile device 114, and the server system 504 (e.g., the user input device 528) may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), a point-based input component (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

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

[0106] For example, the biometric component includes a component for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), etc. The motion component includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The positioning component includes a position sensor component for generating position coordinates (e.g., a global positioning system (GPS) receiver component), a Wi-Fi or Bluetooth receiver for generating positioning system coordinates, etc. TMtransceiver, altitude sensor components (e.g., an altimeter or barometer that detects air pressure, from which altitude can be derived), orientation sensor components (e.g., a magnetometer), etc. Such positioning system coordinates can also be received from the mobile device 114 via the low-power wireless connection 512 and the high-speed wireless connection 514 via the low-power wireless circuitry 534 or the high-speed wireless circuitry 532.

[0107] Figure 6 is a perspective view of an example of a head wearable device 116 in the form of glasses 600 according to some examples. Figure 6 As shown, glasses 600 are eyewear that include electronics that operate within a network system to transmit image and video content. In some examples, glasses 600 are configured to provide augmented reality (AR) capabilities and are referred to as AR glasses. Glasses 600 may include a frame 632 made of any suitable material, such as plastic or metal, including any suitable shape memory alloy. Frame 632 may have a front member 633 that may accommodate a first or left lens, a display or optical element holder 636, and a second or right lens, a display or optical element holder 637, connected by a bridge 638. Front member 633 further includes a left end portion 641 and a right end portion 642. A first or left optical element 644 and a second or right optical element 643 may be disposed within respective left and right optical element holders 636 and 637. Each of optical elements 643 and 644 may be a lens, a display assembly, or a combination thereof. In some examples, for example, the glasses 600 are provided with an integrated near-eye display mechanism that enables, for example, a preview image of visual media captured by the camera 669 of the glasses 600 to be displayed to the user.

[0108] The frame 632 further includes a temple piece 646 and a right temple piece 647, which are coupled to the corresponding left end portion 641 and right end portion 642 of the front piece 633 by any suitable means, such as a hinge (not shown). In another example, the frame 632 can be rigidly or fixedly fixed to the front piece 633, thereby being integral with the front piece 633. Each of the temple piece 646 and the temple piece 647 can include: a first portion 651 coupled to the corresponding end portion 641 or 642 of the front piece 633; ​​and any suitable second portion 652 for coupling to the user's ear, such as a curved or bowed piece. In one example, the front piece 633 can be formed from a single piece of material to have an integrated or integrated construction. In one example, the entire frame 632 can be formed from a single piece of material to have an integrated or integrated construction.

[0109] Eyeglasses 600, for example, include a computing device, such as image processor 522, high-speed processor 530, or low-power processor 536. The computing device can be of any suitable type to be carried by frame 632, and in some examples, the computing device can be of a suitable size and shape to be at least partially disposed within one or more of temple pieces 646, 647. In one example, the computing device has a size and shape similar to the size and shape of one of temple pieces 646, 647, and is thus disposed nearly entirely, if not entirely, within the structure and confines of such temple piece 646, 647.

[0110] In one example, a computing device can be provided in both temple piece 646 and temple piece 647. The computing device can include one or more processors as well as memory, wireless communication circuitry, and a power supply. The computing device includes low-power circuitry, high-speed circuitry, position circuitry, and a display processor. Various other examples can include these elements in different configurations or integrated together in different ways. Additional details of aspects of the computing device can be implemented as described with reference to the description below.

[0111] The computing device further includes a battery 662 or other suitable portable power source. In one example, the battery 662 is disposed in one of the temple piece 646 or the temple piece 647. Figure 6 In the illustrated glasses 600, a battery 662 is shown disposed in the left temple piece 646 and electrically coupled to the remainder of the computing device disposed in the right temple piece 647 using a connector 674. The one or more input and output devices may include a connector or port (not shown) accessible from the exterior of the frame 632 suitable for charging the battery 662, a wireless receiver, transmitter, or transceiver (not shown), or a combination of such devices.

[0112] The glasses 600 include a digital camera 669. Although two cameras 669 are depicted, other examples contemplate the use of a single or additional (i.e., more than two) cameras 669. For ease of description, various features related to the camera 669 will be further described with reference only to a single camera 669, but it will be understood that, in suitable examples, these features may apply to both cameras 669. In some examples, the peripheral camera 669 may include a fisheye camera, depending on the design, camera positioning, and form of the glasses.

[0113] In various examples, the glasses 600 can include any number of input sensors or peripherals in addition to the camera 669. The front piece 633 is provided with an outward-facing, front-facing, front or outer surface 666 that faces forward or away from the user when the glasses 600 are mounted on the user's face, and an opposing inward-facing, rear-facing, rear or inner surface 667 that faces toward the user's face when the glasses 600 are mounted on the user's face. Such sensors can include an inward-facing video sensor or digital imaging module, such as the camera 669, which can be mounted on or disposed within the inner surface 667 of the front piece 633 or elsewhere on the frame 632 to face the user, and an outward-facing video sensor or digital imaging module, such as the camera 669, which can be mounted on or disposed within the outer surface 666 of the front piece 633 or elsewhere on the frame 632 to face away from the user. Such sensors, peripherals, or peripheral devices may additionally include biometric sensors, position sensors, accelerometers, user eye positioning sensors, or any other such sensors. In some examples, a projector or display (not shown) is used to project images on the inner surfaces of optical elements 643, 644 (or lenses) to provide a mixed reality experience or an augmented reality experience for the user of glasses 600.

[0114] Glasses 600 also include an example of a camera control mechanism or user input mechanism, including a camera control button mounted on frame 632 for tactile or manual engagement by the user. The camera control button provides a dual-mode or single-action mechanism, meaning that the user can only set the camera control button between two states: an engaged state and a disengaged state. In this example, the camera control button is a button that defaults to the disengaged state and can be pressed by the user to set the camera control button to the engaged state. When the camera control button is released from the press, it automatically returns to the disengaged state.

[0115] In other examples, the single-action input mechanism may instead be provided by, for example, a touch-sensitive button comprising a capacitive sensor mounted adjacent to a surface of frame 632 for detecting the presence of a user's finger, such that the touch-sensitive button is set to an engaged state when the user touches the finger to a corresponding point on outer surface 666 of frame 632. It will be appreciated that the camera control button and the capacitive touch button described above are merely two examples of tactile input mechanisms for single-action control of camera 669, and that other examples may employ different single-action tactile control arrangements.

[0116] The computing device is configured to perform the methods described herein. In some examples, the computing device is coupled to one or more antennas for receiving signals from a GNSS and circuitry for processing the signals, wherein the antennas and circuitry are housed in the glasses 600. In some examples, the computing device is coupled to one or more wireless antennas and circuitry for transmitting and receiving wireless signals, wherein the antennas and circuitry are housed in the glasses 600. In some examples, multiple sets of antennas and circuitry are housed in the glasses 600. In some examples, the antennas and circuitry are configured to process signals according to, for example, Bluetooth. TM , Bluetooth Low Energy TM , IEEE 902, IEEE 902.11az / be, LTE, proprietary communication standards, 3GPP, and the like. In some examples, the PDR sensor is housed in the glasses 600 and coupled to a computing device. In some examples, the glasses 600 are a VR headset, wherein the optical elements 643 and 644 are opaque screens for displaying images to a user of the VR headset. In some examples, the computing device is coupled to user interface elements, such as a slider or touchpad 676 and a button 678. Long pressing the button 678 resets the glasses 600. The slider or touchpad 676 and button 678 are used by the user to provide input to the computing device and / or other electronic components of the glasses 600. The glasses 600 include one or more microphones 682 coupled to the computing device. The glasses 600 include one or more gyroscopes.

[0117] In addition to the camera 669 provided on the front of the glasses 600, a peripheral camera 690 and a peripheral display 692 are provided to address the peripheral field of view. Figure 6 The peripheral camera devices 690 are shown disposed on the right temple piece 646 and the left temple piece 647 , but it should be understood that more than one camera device 690 may be disposed on one or both of the temple pieces 646 , 647 .

[0118] The peripheral camera device 690 can be disposed on an outer surface 694 of the temple pieces 646, 647 so that the peripheral camera device 690 faces outward from the glasses 600. For example, the peripheral camera device 690 can face away from the user to capture images that mimic the user's peripheral vision.

[0119] Each of the peripheral camera devices 690 can have an associated peripheral display 692, which is disposed on the relative inner surface 696 of the corresponding temple piece 646, temple piece 647. The peripheral display 692 is disposed on the associated inner surface 696 of the temple piece 646, temple piece 647 and is used to project an image into the peripheral field of view of the user of the glasses 600. Providing a peripheral view helps the user of the glasses 600 to obtain a more immersive mixed reality experience or augmented reality experience. According to various examples, the glasses 600 can be configured to activate the peripheral camera device 690 and the peripheral display 692 when a control mechanism is activated. For example, the control mechanism can be tactile and located on the frame (for example, on one or both of the temple piece 646, temple piece 647). In some examples, the control mechanism can be voice-activated. The peripheral camera device 690 and / or the peripheral display 692 can be automatically activated upon a triggering event. For example, they can be activated when it is determined that the user is driving. Any combination of the sensors and camera devices described herein can be used to determine a triggering event. For example, one or more of an accelerometer, a gyroscope, a magnetometer, a GPS, and at least one camera may be used to determine a triggering event.

[0120] When compared to the forward-pointing camera 669, the peripheral camera 690 and / or the associated peripheral display 692 can be of low resolution. The resolution and camera type can be based on a combination of power budget, equipment budget, available physical space, and other factors. According to various implementations, the peripheral camera 690 and the peripheral display 692 have different resolutions. For example, the peripheral display 692 can be configured to zoom in or out of the camera feed. The relatively low resolution of the peripheral camera 690 when compared to the forward-pointing camera 669 contributes to the lower power consumption of the peripheral camera 690. To compensate for the relatively low resolution, the peripheral camera 690 and / or the peripheral display 692 can have a high refresh rate. For example, the refresh rate can be in the range of about 60 Hz to about 240 Hz or in the range of about 100 Hz to about 120 Hz.

[0121] Methods for displaying content to the peripheral vision

[0122] Although the described flowcharts may illustrate the operations as a sequential process, many of the operations may be performed in parallel or simultaneously. Furthermore, the order of the operations may be rearranged. A process is terminated when its operations are completed. A process may correspond to a method, procedure, algorithm, or the like. The operations of a method may be performed in whole or in part, may be performed in conjunction with some or all of the operations in other methods, and may be performed by any number of different systems (e.g., the systems described herein) or any portion thereof (e.g., a processor included in any of the systems).

[0123] Figure 7 A process 700 is shown for displaying content to a user's peripheral vision according to some examples. In one example, a processor in the head wearable device 116, a processor in the user system 102, a processor in the interactive server system 110, or any combination thereof can perform the operations in process 800.

[0124] In operation 702, the processor activates one or more peripheral cameras on the head wearable device based on a triggering event. According to some examples, the peripheral cameras are manually activated. For example, the triggering event can be pressing a tactile button on the head-mounted device. In some examples, the peripheral cameras can be voice-activated. In other cases, the peripheral cameras can be automatically activated upon a triggering event (e.g., determining that the user is driving), for example. According to various examples, the triggering event can be based on the positioning of one or both eyes of the user. As described above, the eye positioning sensor can be provided on the inner surface of the glasses 600 and can be used to track eye positioning. For example, the eye positioning sensor can detect the direction in which the user is looking at the peripheral vision display 692. In some implementations, the triggering event can be, for example, detecting that the user is engaging in a sporting activity such as golf.

[0125] It should be understood that in some examples, activation of the peripheral camera 690 may be accomplished in response to a combination of manual triggering events and automatic triggering events.

[0126] In operation 704, the processor receives input from one or more peripheral cameras 690 of the head wearable device. For example, the one or more peripheral cameras 690 can be disposed on the frame 632 of the head wearable device at a location on the frame in the user's peripheral field of view. Input received from the one or more peripheral vision cameras 690 can be at least partially transmitted to a display 692 in the user's peripheral field of view. According to various examples, the one or more peripheral cameras 690 include at least a left peripheral camera and a right peripheral camera. The left peripheral display is configured to display input received from the left peripheral camera, and the right peripheral camera is configured to display input received from the right peripheral camera.

[0127] In operation 706, the processor adjusts the input received at the display. For example, the controller (e.g., processor 904) can be configured to control the input displayed on one or both of the left peripheral display and the right peripheral display. The controller can adjust the input based on the actual vision of the user of the head wearable device. For example, the actual vision of the user of the head wearable device can include the user's vision if the user is not wearing the head wearable device, such that the user is given the illusion that the temple piece is not present.

[0128] According to various examples, the controller uses machine learning and / or computer vision to adjust the input (e.g., camera feed) based on at least one of the positioning of one or more peripheral cameras 690 or eye measurements of a user of the head-worn device. The goal of the machine learning can be to recreate an image that matches a human perspective as accurately as possible. Because the technology uses machine learning, the accuracy of the input can increase over time to provide a more realistic experience for the user. To recreate the image, the controller can compensate for the distance between one or more peripheral cameras 690 and the user's eyes so that the image fed to the peripheral display 692 shows the perspective that would be observed from the eyes as accurately as possible. For example, if the peripheral vision camera 690 is set 20 mm from the user's eyes and the peripheral display 692 is set 10 mm from the eyes, the controller compensates for the difference in distance. This compensation may become more complex if the camera 690 is located above, below, or to the side of the eye. In this case, the machine learning model may use one or more of: camera calibration information, display calibration information, one or more sensor inputs from the different sensors discussed herein, the pupil distance of the user of the glasses 600, the optical distance of the user's eyes, the shape of the user's head, the positioning of the peripheral camera 690 and peripheral display 692 relative to the user, or other factors.

[0129] The user's eye measurements and other measurable parameters can be measured directly by the head wearable device. In some examples, the eye measurements are measured once upon device initialization. The eye measurements can be updated based on user requests. In some examples, the eye measurements are automatically updated at predefined intervals. According to various examples, the controller is configured to control at least one of the resolution or refresh rate of the left and right peripheral cameras.

[0130] In operation 708, the processor displays the adjusted input fed to the display to the peripheral vision of the user of the head wearable device. For example, the adjusted input can be displayed via the display 692 on the inner surface of the head wearable device disposed in the user's peripheral vision.

[0131] In some examples, the adjusted input is enhanced with one or more augmented content items.For example, the adjusted input can provide at least one of an AR experience and / or a mixed reality experience.

[0132] In operation 710, the processor determines whether a triggering event exists. For example, for an automatic triggering event such as driving, the processor may determine whether the user is still driving. If the processor determines that the user is still driving, the processor may continue to activate the peripheral camera 690 at operation 702. If the triggering event no longer exists, the processor may deactivate the peripheral camera 690 at operation 712.

[0133] In operation 710, the processor may determine whether the user has manually deactivated the peripheral camera 690. If the processor determines that the user has not manually deactivated the peripheral camera 690, the processor determines that the triggering event still exists and continues to activate the peripheral camera 690 at operation 702. Manual deactivation of the peripheral camera 690 causes the triggering event to no longer exist, and the processor deactivates the peripheral camera 690 at operation 712.

[0134] Machine Architecture

[0135] Figure 8800 is a diagrammatic representation of a machine 800 within which instructions 802 (e.g., software, programs, applications, applet, apps, or other executable code) may be executed for causing the machine 800 to perform any one or more of the methodologies discussed herein. For example, the instructions 802 may cause the machine 800 to perform any one or more of the methodologies described herein. The instructions 802 transform a general-purpose, unprogrammed machine 800 into a specialized machine 800 that is programmed to perform the functions described and illustrated in the manner described. The machine 800 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 800 may operate as a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 800 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smartphone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web device, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 802 specifying actions to be taken by the machine 800. In addition, although only a single machine 800 is shown, the term "machine" should also be construed to include a collection of machines that individually or jointly execute instructions 802 to perform any one or more of the methods discussed herein. For example, the machine 800 may include the user system 102 or any of a plurality of server devices forming part of the interactive server system 110. In some examples, the machine 800 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of the particular method or algorithm are performed on the client side.

[0136] The machine 800 may include a processor 804, a memory 806, and input / output I / O components 808 that may be configured to communicate with each other via a bus 810. In an example, the processor 804 (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, a processor 812 that executes instructions 802 and a processor 814. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions concurrently. Although Figure 8 Multiple processors 804 are shown, but the machine 800 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.

[0137] The memory 806 includes a main memory 816, a static memory 818, and a storage unit 820, all of which are accessible by the processor 804 via the bus 810. The main memory 806, the static memory 818, and the storage unit 820 store instructions 802 for implementing any one or more of the methodologies or functions described herein. The instructions 802 may also reside, completely or partially, within the main memory 816, within the static memory 818, within the machine-readable medium 822 within the storage unit 820, within at least one of the processors 804 (e.g., within a cache memory of a processor), or any suitable combination thereof during execution thereof by the machine 800.

[0138] The I / O components 808 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 808 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 will be less likely to include such a touch input device. It will be appreciated that the I / O components 808 may include Figure 8 Many other components are not shown in the drawings. In various examples, the I / O components 808 may include user output components 824 and user input components 826. The user output components 824 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 tubes (CRTs)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. The user input components 826 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens or other tactile input components that provide location and force of touches or touch gestures), audio input components (e.g., microphones), etc.

[0139] In another example, the I / O component 808 may include a biometric component 828, a motion component 830, an environmental component 832, or a positioning component 834, as well as various other components. For example, the biometric component 828 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), etc. The motion component 830 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0140] The environmental components 832 include, for example, one or more cameras (with still image / photo and video capabilities), an illumination sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor for detecting concentrations 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.

[0141] With respect to cameras, user system 102 can have a camera system that includes, 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 can, for example, be used to capture still images and videos of the user of user system 102 (e.g., "selfies"), which can then be enhanced with the enhancement data (e.g., filters) described above. For example, the rear-facing camera can be used to capture still images and videos in a more conventional camera mode, which are similarly enhanced with the enhancement data. In addition to the front-facing camera and the rear-facing camera, user system 102 can also include a 360° camera for capturing 360° photos and videos.

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

[0143] The positioning component 834 includes a position sensor component (for example, a GPS receiver component), an altitude sensor component (for example, an altimeter or barometer that detects air pressure, and the altitude can be obtained according to the air pressure), an orientation sensor component (for example, a magnetometer), etc.

[0144] Various technologies can be used to achieve communication. The I / O components 808 also include a communication component 836 that is operable to couple the machine 800 to a network 838 or device 840 via corresponding couplings or connections. For example, the communication component 836 may include a network interface component or another suitable device that interfaces with the network 838. In other examples, the communication component 836 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Components (e.g. Low energy consumption), Device 840 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0145] In addition, the communication component 836 can detect an identifier, or include a component operable to detect an identifier. For example, the communication component 836 can 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 bar codes such as Universal Product Code (UPC) bar codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 836, such as location via Internet Protocol (IP), geolocation via Internet Protocol (IP), location information ... Signal triangulation to obtain location, location obtained by detecting NFC beacon signals that can indicate a specific location, etc.

[0146] Various memories (e.g., main memory 816, static memory 818, and memory of processor 804) and storage unit 820 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., instructions 802) when executed by processor 804 cause various operations to implement the disclosed examples.

[0147] Instructions 802 may be sent or received over network 838 using a transmission medium via a network interface device (e.g., a network interface component included in communications component 836) and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 802 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with device 840 using a transmission medium.

[0148] Software Architecture

[0149] Figure 9 9 is a block diagram 900 illustrating a software architecture 902 that can be installed on any one or more of the devices described herein. The software architecture 902 is supported by hardware, such as a machine 904 including a processor 906, memory 908, and I / O components 910. In this example, the software architecture 902 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 902 includes layers such as an operating system 912, libraries 914, frameworks 916, and applications 918. In operation, the applications 918 invoke API calls 920 through the software stack and receive messages 922 in response to the API calls 920.

[0150] The operating system 912 manages hardware resources and provides public services. The operating system 912 includes, for example, a kernel 924, services 926, and drivers 928. The kernel 924 serves as an abstraction layer between the hardware and other software layers. For example, the kernel 924 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 926 can provide other public services to other software layers. Drivers 928 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 928 may include display drivers, camera drivers, or Low-power drivers, Flash drivers, serial communication drivers (e.g., USB drivers), drivers, audio drivers, power management drivers, etc.

[0151] The libraries 914 provide a common low-level infrastructure used by the applications 918. The libraries 914 may include system libraries 930 (e.g., C standard libraries) that provide functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 914 may include API libraries 932, such as media libraries (e.g., libraries for supporting the presentation 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 codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries (e.g., the OpenGL framework for rendering graphical content on a display in two dimensions (2D) and three dimensions (3D), database libraries (e.g., SQLite providing various relational database functions), web libraries (e.g., WebKit providing web browsing functions), etc. The libraries 914 may also include a variety of other libraries 934 to provide many other APIs to the applications 918.

[0152] The framework 916 provides a common high-level infrastructure used by applications 918. For example, the framework 916 provides various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The framework 916 can provide a wide range of other APIs that can be used by applications 918, some of which may be specific to a particular operating system or platform.

[0153] In an example, applications 918 may include a home application 936, a contacts application 938, a browser application 940, a book reader application 942, a location application 944, a media application 946, a messaging application 948, a game application 950, and a variety of other applications such as third-party applications 952. Applications 918 are programs that perform functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 918 structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C language or assembly language). In a specific example, third-party applications 952 (e.g., those written by entities other than the vendor of a particular platform using ANDROID) may be used. TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM 、 Mobile software running on the mobile operating system of the phone or other mobile operating system. In this example, third-party applications 952 can activate API calls 920 provided by the operating system 912 to facilitate the functions described in this article.

[0154] Glossary

[0155] "Carrier signal" refers to any intangible medium, such as a digital or analog communication signal, that is capable of storing, encoding, or carrying instructions for execution by a machine, or other intangible medium that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0156] "Client device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices, for example. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smartphone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0157] "Communications network" refers to, for example, one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a Plain Old Telephone Service (POTS) network, a cellular telephone network, a wireless network, The coupling may be a network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the 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 type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (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.

[0158] "Component" refers to a logic or device, a physical entity, for example, having the following boundaries, which are defined by function or subroutine calls, branch points, APIs, or other technical definitions that provide partitioning or modularization of specific processing or control functions. A component can be combined with other components via its interface to perform machine processing. A component can be a packaged functional hardware unit designed for use with other components, and a part of a program that generally performs a specific function of a related function. A component can constitute a software component (for example, a code implemented on a machine-readable medium) or a hardware component. A "hardware component" is a tangible unit that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (for example, a stand-alone computer system, a client computer system, or a server computer system) or one or more hardware components (for example, a processor or a processor group) of a computer system can be configured by software (for example, an application or an application part) to operate to perform certain operations as described herein. Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component can include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component can be a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). The hardware component can also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component can include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine), which is uniquely customized to perform the configured function and is no longer a general-purpose processor. It will be appreciated that it can be decided whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include tangible entities, i.e., entities that are physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware component in the hardware component at any one time. For example, where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as different special-purpose processors (e.g., including different hardware components) at different times. The software configures a specific processor or processors accordingly, such as to constitute a specific hardware component at one time and to constitute a different hardware component at a different time. A hardware component can provide information to other hardware components and receive information from other hardware components.Therefore, the hardware components described can be considered to be coupled in communication. In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission between or among two or more hardware components (for example, by appropriate circuits and buses). In the example where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled in communication with it. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (for example, a collection of information). The various operations of the example methods described herein can be performed at least in part by temporarily configuring (for example, by software) or permanently configuring one or more processors to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein specific one or more processors are examples of hardware. For example, at least some of the various operations of the method can be performed by one or more processors or the parts implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or operate as "software as a service" (SaaS). For example, at least some operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (for example, the Internet) and via one or more appropriate interfaces (for example, API). The execution of some operations can be distributed between processors, is not only resident in a single machine, but deployed across multiple machines. In some examples, a processor or the parts implemented by the processor can be located in a single geographical location (for example, in a home environment, an office environment or a server farm). In other examples, a processor or the parts implemented by the processor can be distributed across multiple geographical locations.

[0159] "Computer-readable storage media" refers to, for example, both machine storage media and transmission media. Thus, these terms encompass both storage devices / media and carrier waves / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0160] A "transient message" is a message that is accessible for a limited duration, for example. Transient messages can be text, images, videos, and the like. The access period for a transient message can be set by the message sender. Alternatively, the access period can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0161] “Machine storage media” refers to, for example, a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be taken 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; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms “machine storage media,” “device storage media,” and “computer storage media” mean the same thing and may be used interchangeably in this disclosure. The terms “machine storage media,” “computer storage media,” and “device storage media” expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term “signal media.”

[0162] “Non-transitory computer-readable storage medium” refers to a tangible medium that is capable of storing, encoding, or carrying instructions for execution by a machine, for example.

[0163] "Signal medium" refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution 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 taken to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

[0164] "User device" refers to a device that is, for example, accessed, controlled, or owned by a user and with which the user interacts to perform actions on the user device or to interact with other users or computer systems.

Claims

1. A head wearable device comprising: a frame comprising a front piece configured to receive a left lens and a right lens, a left temple coupled to the front piece, and a right temple coupled to the front piece; a camera system comprising one or more cameras coupled to the front piece, one or more left peripheral cameras coupled to an exterior surface of the frame, and one or more right peripheral cameras coupled to an exterior surface of the frame; a left peripheral display coupled to an inner surface of the frame, the left peripheral display configured to receive and display input from the one or more left peripheral camera devices; as well as A right peripheral display is coupled to an inner surface of the frame, the right peripheral display being configured to receive and display input from the one or more right peripheral cameras.

2. The head wearable device according to claim 1 further includes a right lens display coupled to the inner surface of the right lens and a left lens display coupled to the inner surface of the left lens.

3. The head wearable device according to claim 1, wherein: One or both of the left peripheral display and the right peripheral display is a projector.

4. The head wearable device of claim 3, further comprising a controller configured to control the input displayed by the left peripheral display and the right peripheral display.

5. The head wearable device according to claim 4, wherein: The controller is configured to adjust the input displayed by the left peripheral display and the right peripheral display based on an actual vision of a user of the head wearable device.

6. The head wearable device according to claim 4, wherein: The controller is configured to adjust the input based on a distance between at least one of the left peripheral camera and the right peripheral camera and a corresponding eye of a user of the head wearable device.

7. The head wearable device of claim 4, further comprising an eye positioning sensor configured to detect the positioning of one or both eyes of a user of the head wearable device, and wherein The controller is configured to activate one or both of the peripheral displays based on the detected positioning.

8. The head wearable device according to claim 4, wherein: The controller is configured to adjust the displayed input based on at least one of the positioning of the one or more left peripheral cameras, the one or more right peripheral cameras, or eye measurements of a user of the head wearable device.

9. The head wearable device according to claim 8, wherein: The controller is configured to adjust the input using machine learning.

10. The head wearable device according to claim 4, wherein: The controller is configured to control at least one of a resolution or a refresh rate of the left peripheral camera and the right peripheral camera.

11. The head wearable device according to claim 4, wherein: The controller is configured to cause the left peripheral display and the right peripheral display to display at least one of mixed reality input or augmented reality input to a user of the head wearable device.

12. A method comprising: receiving input from one or more peripheral camera devices of the head wearable device; using machine learning to adjust the input based on at least one of positioning of the one or more peripheral cameras or eye measurements of a user of the head wearable device; as well as The adjusted input is displayed to the peripheral vision of a user of the head wearable device.

13. The method according to claim 12, wherein: Adjusting the input includes adjusting the input based on an actual field of view of a user of the head wearable device.

14. The method according to claim 12, wherein: Displaying the adjusted input includes displaying at least one of a mixed reality input or an augmented reality input to a user of the head wearable device.

15. The method of claim 12, further comprising controlling at least one of a resolution or a refresh rate of the received input.

16. The method according to claim 12, wherein: The input is adjusted based on a distance between the one or more peripheral cameras and corresponding eyes of a user of the head wearable device.

17. The method according to claim 12, further comprising: detecting the positioning of one or both eyes of a user of the head wearable device; as well as One or both of the peripheral displays are activated based on the detected positioning.

18. A non-transitory computer-readable storage medium comprising instructions that, when executed by a controller of a head wearable device, cause the controller to perform operations comprising: receiving input from one or more peripheral camera devices of the head wearable device; using machine learning to adjust the input based on at least one of positioning of the one or more peripheral cameras or eye measurements of a user of the head wearable device; as well as The adjusted input is displayed to the peripheral vision of a user of the head wearable device.

19. The non-transitory computer-readable storage medium of claim 18, wherein: Adjusting the input includes adjusting the input based on an actual field of view of a user of the head wearable device.

20. The non-transitory computer-readable storage medium of claim 18, wherein: Displaying the adjusted input includes displaying at least one of a mixed reality input or an augmented reality input to a user of the head wearable device.

Images