CN117157608A

CN117157608A - User-defined scene space

Info

Publication number: CN117157608A
Application number: CN202280025811.XA
Authority: CN
Inventors: 埃德蒙·格雷夫斯·布朗
Original assignee: Snap Inc
Current assignee: Snap Inc
Priority date: 2021-03-31
Filing date: 2022-03-23
Publication date: 2023-12-01

Abstract

Systems and methods herein describe generating a user-defined contextual space, receiving an image of a view of a physical space from an imaging device, receiving a virtual boundary of a first portion of the physical space, determining a virtual volume of the first portion of the physical space based on a first input, receiving data associated with the first portion of the physical space, and storing the virtual volume in association with the received data.

Description

User-defined scene space

Cross Reference to Related Applications

The present application claims the benefit of priority from U.S. provisional application Ser. No. 63/168,435, filed on 3 months 31 in 2021, and U.S. patent application Ser. No. 17/697,425, filed on 3 months 17 in 2022, each of which are incorporated herein by reference in their entirety.

Technical Field

Embodiments herein generally relate to specific computing. More particularly, but not by way of limitation, embodiments herein describe a system for creating a user-defined contextual space.

Background

Spatial computing has transformed the way people interact with the real world. Computers may interact with three-dimensional physical space using Augmented Reality (AR) and Virtual Reality (VR) and provide a real and immersive digital experience to a user.

Drawings

In the drawings (which are not necessarily drawn to scale), like numerals may describe similar components in different views. For ease of identifying a discussion of any particular element or act, one or more of the highest digits in a reference number refer to the figure number in which that element was first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

FIG. 1 is a diagrammatic representation of a networking environment in which the present disclosure may be deployed, according to some examples.

Fig. 2 is a diagrammatic representation of a messaging system having both client-side and server-side functions in accordance with some examples.

FIG. 3 is a diagrammatic representation of a data structure as maintained in a database in accordance with some examples.

Fig. 4 is a diagrammatic representation of a message according to some examples.

Fig. 5 illustrates a head wearable device according to an example embodiment.

FIG. 6 is a flowchart of an example method for generating a user-defined contextual space according to some example embodiments.

FIG. 7 is a flowchart of an example method for automatically populating virtual content in semantically annotated virtual objects, according to some example embodiments.

FIG. 8 is a flowchart of an example method for generating a user-aligned spatial volume according to an example embodiment.

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

Fig. 10 is a block diagram illustrating a software architecture in which an example may be implemented.

Fig. 11 illustrates a system 1100 in which a head wearable device 500 with a selector input device 706 (deleted) may be implemented, according to an example embodiment.

Detailed Description

Embodiments of the present disclosure improve the functionality of a messaging system by facilitating sharing of media content items (e.g., pictures, videos, etc.) exchanged between two people on the messaging system. Further, one embodiment of the present disclosure is a method for creating a user-defined scene space using a scene space generator. The contextual space customizer accesses a view of the physical space from the head wearable device. In one example, a user defines a virtual boundary within a physical space by providing two boundary points, and a contextual space customizer generates a virtual volume based on the two boundary points. The user also provides data about the virtual boundary via the head wearable device. For example, the user may provide data such as room identification corresponding to the virtual boundary, a set of room sizes, and user room preferences. The user-provided data is stored in one or more databases in association with the virtual volumes.

Networked computing environment

Fig. 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each instance hosting several applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of messaging clients 104 (e.g., hosted on respective other client devices 102), messaging server systems 108, and third party servers 110 via a network 112 (e.g., the internet). The messaging client 104 may also communicate with locally hosted applications 106 using an Application Program Interface (API).

The messaging client 104 is capable of communicating and exchanging data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and the messaging server system 108 includes functions (e.g., commands to activate the functions) as well as payload data (e.g., text, audio, video, or other multimedia data).

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

The messaging server system 108 supports various services and operations provided to the messaging client 104. Such operations include sending data to the messaging client 104, receiving data from the messaging client 104, and processing data generated by the messaging client 104. As examples, the data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The exchange of data within the messaging system 100 is activated and controlled by functions available via a User Interface (UI) of the messaging client 104.

Turning now specifically to messaging server system 108, an Application Program Interface (API) server 116 is coupled to application server 114 and provides a programming interface to application server 112. The application server 114 is communicatively coupled to a database server 120, the database server 120 facilitating access to a database 126, the database 126 storing data associated with messages processed by the application server 114. Similarly, web server 128 is coupled to application server 114 and provides a web-based interface to application server 114. To this end, web server 128 processes incoming network requests through the hypertext transfer protocol (HTTP) and several other related protocols.

An Application Program Interface (API) server 116 receives and transmits message data (e.g., command and message payloads) between the client device 102 and the application server 114. In particular, an Application Program Interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that may be invoked or queried by the messaging client 104 to activate functions of the application server 114. An Application Program Interface (API) server 116 exposes various functions supported by the application server 114, including: registering an account; a login function; sending a message from a particular messaging client 104 to another messaging client 104 via the application server 114, sending a media file (e.g., an image or video) from the messaging client 104 to the messaging server 118, and for possible access by the other messaging client 104; setting a collection of media data (e.g., a story); retrieving a friends list of the user of the client device 102; retrieving such a collection; retrieving the message and the content; adding and deleting entities (e.g., friends) to an entity graph (e.g., social graph); locating friends within the social graph; and open application (e.g., related to messaging client 104) events.

Application server 114 hosts a plurality of server applications and subsystems including, for example, messaging server 118, image processing server 122, social networking server 124, and contextual space customizer 130. The messaging server 118 implements a number of message processing techniques and functions, particularly related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources may be aggregated into a collection of content (e.g., referred to as a story or gallery). These sets are then made available to the messaging client 104. Such processing may also be performed by the messaging server 118 on the server side in view of hardware requirements for other processors and memory intensive processing of data.

The application server 114 also includes an image processing server 122, the image processing server 122 being dedicated to performing various image processing operations generally for images or videos within the payload of messages sent from the messaging server 118 or received at the messaging server 118.

The social networking server 124 supports various social networking functions and services and makes these functions and services available to the messaging server 118. To this end, the social networking server 124 maintains and accesses an entity graph 308 (shown in FIG. 3) within the database 126. Examples of functions and services supported by the social networking server 124 include identifying other users in the messaging system 100 that have a relationship with or are "focused on" by a particular user, and also identifying interests and other entities of the particular user.

The contextual space customizer 130 allows the user of the head wearable device 500 to define and customize virtual spaces. For example, the contextual space customizer 130 uses spatial computation to reconstruct the physical space of the user in real-time.

Returning to the messaging client 104, features and functions of external resources (e.g., applications 106 or applets) are available to the user via the interface of the messaging client 104. In this scenario, "external" refers to the fact that the application 106 or applet is external to the messaging client 104. The external resources are typically provided by a third party, but may also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option to initiate or access a feature of such an external resource. The external resource may be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version (e.g., an "applet") of an application hosted on the client device 102 or located remotely from the client device 102 (e.g., on the third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., full-scale, native version of the application) and is implemented using a markup language document. In one example, a small-scale version of an application (e.g., an "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (e.g., a..ml file), applets may include scripting languages (e.g., a..js file or a. Json file) and style sheets (e.g., a..ss file).

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

In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 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 messaging client 104 communicates with, for example, the third party server 110 to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to render the web-based external resource within the user interface of the messaging client 104.

The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") related to such users of the activity occurring in one or more external resources. For example, the messaging client 104 may provide notifications to participants in a conversation (e.g., chat session) in the messaging client 104 regarding the current or recent use of external resources by one or more members of a group of users. One or more users may be invited to join an active external resource or to initiate (among the set of friends) a recently used but currently inactive external resource. The external resources may provide participants in the conversation each using a respective messaging client 104 with the ability to share items, states, conditions, or locations in the external resources with one or more members of a group of users into a chat session. The shared items may be interactive chat cards with which members of the chat may interact, for example, to initiate a corresponding external resource, to view specific information within the external resource, or to bring members of the chat to a specific location or state within the external resource. Within a given external resource, a response message may be sent to the user on the messaging client 104. The external resource may selectively include different media items in the response based on a current context of the external resource.

The messaging client 104 may 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 may be presented in a context sensitive menu. For example, icons representing different applications 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

System architecture

Fig. 2 is a block diagram illustrating additional details regarding the messaging system 100 according to some examples. In particular, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains a number of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an augmentation system 208, a map system 210, a game system 212, and an external resource system 214.

The ephemeral timer system 202 is responsible for enforcing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The ephemeral timer system 202 incorporates a plurality of timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the messaging client 104 based on a duration and display parameters associated with the message or collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.

The collection management system 204 is responsible for managing collections of media and collections (e.g., collections of text, image video, and audio data). A collection of content (e.g., messages, including images, video, text, and audio) may be organized into an "event gallery" or "event story. Such a collection may be made available for a specified period of time, for example, for the duration of a content-related event. For example, content related to a concert may be made available as a "story" for the duration of the concert. The collection management system 204 may also be responsible for publishing icons that provide notifications to the user interface of the messaging client 104 that a particular collection exists.

In addition, the collection management system 204 includes a curation interface 206 that enables the collection manager to manage and curate a particular collection of content. For example, curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., delete inappropriate content or redundant messages). In addition, the collection management system 204 employs machine vision (or image recognition techniques) and content rules to automatically curate the collection of content. In some examples, compensation may be paid to the user for including the user-generated content into the collection. In such a case, the collection management system 204 operates to automatically pay such users for use of their content.

Enhancement system 208 provides various functionality that enables a user to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functionality related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlay or enhancement (e.g., image filters) to the messaging client 104 based on the geolocation of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information, such as social network information of the user of the client device 102. The media overlay 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) at the client device 102. For example, the media overlay may include text or images that may be overlaid on top of a photograph taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., a Venice beach), a live event name, or a merchant name overlay (e.g., a beach cafe). In another example, the enhancement system 208 uses the geolocation of the client device 102 to identify a media overlay that includes the merchant name at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlay may be stored in database 126 and accessed through database server 120.

In some examples, the enhancement system 208 provides a user-based distribution platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user may also specify the environment in which the particular media overlay should be provided to other users. Enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

In other examples, the enhancement system 208 provides a merchant-based distribution platform that enables merchants to select particular media overlays associated with geographic locations via a bidding process. For example, the enhancement system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time.

The map system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the map system 210 enables display of user icons or avatars (e.g., stored in the profile data 316) on a map to indicate the current or past locations of a user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by such friends in the context of the map. For example, a message posted by a user from a particular geographic location to the messaging system 100 may be displayed to a "friend" of a particular user within the context of that particular location of the map on the map interface of the messaging client 104. The user may also share his or her location and status information with other users of the messaging system 100 (e.g., using an appropriate status avatar) via the messaging client 104, where the location and status information is similarly displayed to the selected user within the context of the messaging client 104's map interface.

The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a game interface that provides a list of available games that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to play a particular game by issuing an invitation from the messaging client 104 to such other users. Messaging client 104 also supports messaging (e.g., chat) of both speech and text within a play scenario, provides a leaderboard for a game, and also supports in-game rewards (e.g., money and items)

The external resource system 214 provides an interface for the messaging client 104 to communicate with a remote server (e.g., the third party server 110) to launch or access external resources (i.e., applications or applets). Each third party server 110 hosts, for example, a markup language (e.g., HTML 5) based application or a small-scale version of an application (e.g., a gaming application, a utility application, a payment application, or a ride share application). The messaging client 104 may launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third party server 110 associated with the web-based resource. In some examples, the application hosted by the third party server 110 is programmed in JavaScript with a Software Development Kit (SDK) provided by the messaging server 118. The SDK includes an Application Program Interface (API) having functions that can be invoked or activated by web-based applications. In some examples, the messaging server 118 includes a javascript library that provides given external resource access to certain user data of the messaging client 104. HTML5 is used as an example technique for programming games, but applications and resources programmed based on other techniques may be used.

To integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the messaging server 118 by the third party server 110 or otherwise received by the third party server 110. 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 may then call or activate certain functions of the SDK to integrate features of the messaging client 104 into the web-based resource.

The SDK stored on the messaging server 118 effectively provides bridging between external resources (e.g., applications 106 or applets) and the messaging client 104. This provides a seamless experience for a user to communicate with other users on the messaging client 104 while also preserving the look and feel of the messaging client 104. To bridge communications between external resources and the messaging client 104, in some examples, the SDK facilitates communications between the third party server 110 and the messaging client 104. In some examples, webviewjavascript bridge running on the client device 102 establishes two unidirectional communication channels between the external resource and the messaging client 104. Messages are sent asynchronously between the external resources and the messaging client 104 via these communication channels. Each SDK function call is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

By using the SDK, not all information from the messaging client 104 is shared with the third party server 110. The SDK limits which information to share based on the needs of external resources. In some examples, each third party server 110 provides an HTML5 file corresponding to the web-based external resource to the messaging server 118. The messaging server 118 may add a visual representation (such as a box design or other graphic) of the web-based external resource in the messaging client 104. Once the user selects a visual representation or instructs the messaging client 104, through the GUI of the messaging client 104, to access the features of the web-based external resource, the messaging client 104 obtains the HTML5 file and instantiates the resources needed to access the features of the web-based external resource.

The messaging client 104 presents a graphical user interface (e.g., a landing page or a banner screen) for the external resource. During, before, or after presentation of the landing page or the banner screen, the messaging client 104 determines whether the initiated external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the initiated external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource that includes functionality and features of the external resource. In response to determining that the initiated external resource was not previously authorized to access the user data of messaging client 104, messaging client 104 slides up a menu (e.g., animations the menu as floating from the bottom of the picture to the middle or other portion of the picture) for authorizing the external resource to access the user data after a threshold period of time (e.g., 3 seconds) of displaying a landing page or title screen of the external resource. The menu identifies the type of user data that the external resource is to be authorized to use. In response to receiving the user selection of the receipt option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access user data from the messaging client 104. In some examples, the external resource is authorized by the messaging client 104 to access the user data in accordance with the OAuth 2 framework.

The messaging 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, external resources including full-scale applications (e.g., application 106) are provided access to a first type of user data (e.g., a two-dimensional-only avatar of a user with or without different body characteristics). As another example, 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 avatars having various avatar characteristics) is provided to an external resource that includes a small scale version of the application (e.g., a web-based version of the application). Avatar characteristics include different ways of customizing the look and feel (e.g., different gestures, facial features, clothing, etc.) of the avatar.

Data architecture

Fig. 3 is a schematic diagram illustrating a data structure 300 that may be stored in the database 126 of the messaging server system 108, according to some examples. While the contents of database 126 are shown as including multiple tables, it will be appreciated that data may be stored in other types of data structures (e.g., as an object-oriented database).

Database 126 includes message data stored within message table 302. For any particular message, the message data includes at least message sender data, message recipient (or recipient) data, and a payload. Additional details regarding information that may be included in a message and within message data stored in message table 302 are described below with reference to fig. 4.

The entity table 306 stores entity data and is linked (e.g., referenced to ground) to the entity graph 308 and profile data 316. The entities for which records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, and the like. Regardless of the entity type, any entity about which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

The entity diagram 308 stores information about relationships and associations between entities. By way of example only, such relationships may be interest-based or activity-based social relationships, professional relationships (e.g., working at a common company or organization).

The profile data 316 stores various types of profile data regarding a particular entity. The profile data 316 may be selectively used and presented to other users of the messaging system 100 based on privacy settings specified by a particular entity. In the case where the entity is a person, the profile data 316 includes, for example, a user name, a telephone number, an address, settings (e.g., notification and privacy settings), and user-selected avatar representations (or a set of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages transmitted via messaging system 100 and on map interfaces displayed to other users by messaging client 104. The set of avatar representations may include a "status avatar" that presents graphical representations of status or activities that the user may select to transmit at a particular time.

In the case where the entity is a community, the profile data 316 for the community may similarly include one or more avatar representations associated with the community in addition to the community name, the member, and various settings (e.g., notifications) for the relevant community.

Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to video (data of the video is stored in video table 304) and images (data of the images is stored in image table 312).

In one example, the filter is an overlay that is displayed as an overlay over the image or video during presentation to the recipient user. The filters may be of various types, including user-selected filters from a set of filters presented to the sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geo-filters), which may be presented to a sending user based on geolocation. For example, a nearby or special location-specific geolocation filter may be presented by the messaging client 104 within the user interface based on geolocation information determined by the Global Positioning System (GPS) unit of the client device 102.

Another type of filter is a data filter that may be selectively presented to the sending user by the messaging client 104 based on other inputs or information collected by the client device 102 during the message creation process. Examples of data filters include a current temperature at a particular location, a current speed at which a sending user travels, a battery life of the client device 102, or a current time.

Other augmentation data that may be stored within the image table 312 includes augmented reality content items (e.g., corresponding to application lenses or augmented reality experiences). The augmented reality content item may be real-time special effects and sounds that may be added to an image or video. The augmented reality content item may also include a Virtual Reality (VR) experience.

As described above, the augmentation data includes augmented reality content items, overlays, image transforms, AR images, and similar terms that refer to modifications that may be applied to image data (e.g., video or images). This includes real-time modifications that modify the image as it is captured using the device sensor (e.g., one or more cameras) of the client device 102 and then displayed on the screen of the client device 102 in the case of modifications. This also includes modifications to the stored content (e.g., video clips in the gallery that may be modified). For example, in a client device 102 accessing multiple augmented reality content items, a user may use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify stored clips. For example, multiple augmented reality content items to which different pseudo-random motion models are applied may be applied to the same content by selecting different augmented reality content items for the same content. Similarly, real-time video capture may be used with the illustrated modifications to illustrate how the video image currently being captured by the sensor of the client device 102 will modify the captured data. Such data may be displayed on the screen only and not stored in memory, or content captured by the device sensor may be recorded and stored in memory with or without modification (or both). In some systems, the preview feature may simultaneously display how different augmented reality content items will look within different windows in the display. For example, this may enable multiple windows with different pseudo-random animations to be viewed simultaneously on a display.

Thus, using data of an augmented reality content item and various systems or other such transformation systems that use such data to modify content may involve: detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in a video frame, tracking of such objects as they leave the field of view, enter the field of view, and move around the field of view, and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve generating a three-dimensional mesh model of one or more objects, and implementing the transformation within the video using a transformation of the model and an animated texture. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In further examples, neural network analysis of video frames may be used to place images, models, or textures in content (e.g., images or video frames). Thus, augmented reality content items relate to both images, models, and textures used to create transformations in the content, and to additional modeling and analysis information required to implement such transformations with object detection, tracking, and placement.

Real-time video processing may be performed with any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user may load a video file and save it in the memory of the device, or may generate a video stream using a sensor of the device. In addition, computer animation models may be used to process any object, such as the human face and parts of the human body, animals, or inanimate objects (e.g., chairs, automobiles, or other objects).

In some examples, when a particular modification is selected along with the content to be transformed, the element to be transformed is identified by the computing device and then detected and tracked if the element to be transformed is in a frame of the video. The elements of the object are modified according to the modification request, thus transforming the frames of the video stream. For different kinds of transformations, the transformation of frames of the video stream may be performed by different methods. For example, for frame transforms that primarily involve changing the form of an element of the object, characteristic points of each element of the object are computed (e.g., using an active shape model (Active Shape Model, ASM) or other known methods). Then, a grid based on the characteristic points is generated for each of the at least one element of the object. The grid is used for tracking the subsequent stages of the elements of the object in the video stream. During the tracking process, the mentioned grid for each element is aligned with the position of each element. Additional points are then generated on the grid. A first set of first points is generated for each element based on the modification request and a second set of points is generated for each element based on the first set of points and the modification request. The frames of the video stream may then be transformed by modifying the elements of the object based on the set of first points, the set of second points, and the grid. In such a method, the background of the modified object may also be changed or distorted by tracking and modifying the background.

In some examples, transforming using elements of the object to change certain regions of the object may be performed by calculating characteristic points of each element of the object and generating a grid based on the calculated characteristic points. Points are generated on the grid, and then various regions based on the points are generated. The elements of the object are then tracked by aligning the region of each element with the location of each of the at least one element, and the properties of the region may be modified based on the modification request, thus transforming the frames of the video stream. The properties of the mentioned regions may be transformed in different ways depending on the specific modification request. Such modifications may involve: changing the color of the region; removing at least a portion of the region from a frame of the video stream; including one or more new objects in the modification request-based region; and modifying or distorting the elements of the region or object. In various examples, any combination of such modifications or other similar modifications may be used. For some models to be animated, some characteristic points may be selected as control points for determining the entire state space for the options for model animation.

In some examples of computer-animated models that use face detection to transform image data, a particular face detection algorithm (e.g., viola-Jones) is utilized to detect faces on the image. An Active Shape Model (ASM) algorithm is then applied to the facial regions of the image to detect facial feature reference points.

Other methods and algorithms suitable for face detection may be used. For example, in some examples, landmarks are used to locate features, the landmarks representing distinguishable points present in most of the images considered. For example, for facial landmarks, the localization of the left eye pupil may be used. If the initial landmark is not identifiable (e.g., if the person has eye-masks), a secondary landmark may be used. Such landmark identification procedures may be used for any such object. In some examples, a set of landmarks form a shape. The coordinates of points in the shape may be used to represent the shape as a vector. One shape is aligned with another shape using a similar transformation (allowing translation, scaling, and rotation) that minimizes the average euclidean distance between shape points. The mean shape (mean shape) is the mean of the aligned training shapes.

In some examples, the landmarks are searched starting from a mean shape aligned with the position and size of the face determined by the global face detector. Such a search then repeats the steps of: the tentative shape is suggested by adjusting the positioning of the shape points by template matching of the image texture around each point, and then conforming the tentative shape to the global shape model until convergence occurs. In some systems, individual template matching is unreliable, and shape models pool the results of weak template matching to form a stronger overall classifier. The entire search repeats at each level of the image pyramid from coarse resolution to fine resolution.

The transformation system may capture images or video streams on a client device (e.g., client device 102) and perform complex image manipulation locally on the client device 102 while maintaining an appropriate user experience, computation time, and power consumption. Complex image manipulation may include size and shape changes, mood transformations (e.g., changing a face from frowning to smiling), state transformations (e.g., aging a subject, reducing apparent age, changing gender), style transformations, graphical element applications, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to be efficiently performed on the client device 102.

In some examples, a computer animation model for transforming image data may be used by the following system: in this system, a user may capture an image or video stream (e.g., self-timer) of the user using a client device 102 having a neural network operating as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of faces within an image or video stream and provides a modification icon associated with a computer animation model to transform the data image, or the computer animation model may be present in association with the interface described herein. The modify icon includes the following changes: the change may be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of converting the image of the user to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream may be presented in a graphical user interface displayed on the client device 102. The transformation system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modifications. That is, the user may capture an image or video stream and once the modification icon is selected, the modification results are presented to the user in real-time or near real-time. Further, the modification may be persistent while the video stream is being captured, and the selected modification icon remains switched. A neural network of machine teachings may be used to implement such modifications.

Presenting a modified graphical user interface performed by the transformation system may provide additional interaction options to the user. Such options may be based on an interface (e.g., initiated from a content creator user interface) for initiating selection of a particular computer animation model and content capture. In various examples, the modification may be persistent after an initial selection of the modification icon. The user may turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system and store it for later viewing or browsing to other areas of the imaging application. In the case of multiple faces modified by a transformation system, the user may globally turn the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a set of multiple faces may be modified individually, or such modification may be switched individually by tapping or selecting each face or a series of each faces displayed within the graphical user interface.

Story table 314 stores data about a collection of messages and associated image, video, or audio data assembled into a collection (e.g., a story or gallery). Creation of a particular collection may be initiated by a particular user (e.g., each user for which records are maintained in the entity table 306). The user may create a "personal story" in the form of a collection of content that has been created and transmitted/broadcast by the user. To this end, the user interface of the messaging client 104 may include user selectable icons to enable the sending user to add particular content to his or her personal story.

The collection may 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" may constitute a curated stream of user-submitted content from different locations and events. A user whose client device is enabled with a positioning service and at a particular time is at a co-location event may be presented with an option to contribute content to a particular live story, for example, via a user interface of messaging client 104. The live story may be identified to the user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

Another type of collection of content is referred to as a "positioning story" that enables users whose client devices 102 are located within a particular geographic location (e.g., at a college or university campus) to contribute to the particular collection. In some examples, the contribution to the positioning story may require a secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student in a university campus).

As mentioned above, video table 304 stores video data, which in one example is associated with messages for which records are maintained within message table 302. Similarly, the image table 312 stores image data associated with messages whose message data is stored in the entity table 306. Entity table 306 may associate various enhancements from enhancement table 310 with various images and videos stored in image table 312 and video table 304.

Data communication architecture

Fig. 4 is a diagram illustrating the structure of a message 400 generated by a messaging client 104 for transmission to another messaging client 104 or messaging server 118, according to some examples. The contents of a particular message 400 are used to populate the message table 302 stored within the database 126 accessible by the messaging server 118. Similarly, the content of message 400 is stored in memory as "in-transit" or "in-flight" data for client device 102 or application server 114. Message 400 is shown as including the following example components:

message identifier 402: a unique identifier that identifies the message 400.

Message text payload 404: text to be generated by a user via a user interface of the client device 102 and included in the message 400.

Message image payload 406: image data captured by the camera component of the client device 102 or retrieved from the memory component of the client device 102 and included in the message 400. Image data for a transmitted or received message 400 may be stored in the image table 312.

Message video payload 408: video data captured by the camera assembly component or retrieved from the memory component of the client device 102 and included in the message 400. Video data for a transmitted or received message 400 may be stored in video table 304.

Message audio payload 410: audio data captured by the microphone or retrieved from a memory component of the client device 102 and included in the message 400.

Message enhancement data 412: enhancement data (e.g., filters, tags, or other annotations or enhancements) representing enhancements to the message image payload 406, the message video payload 408, or the message audio payload 410 to be applied to the message 400. Enhancement data for a transmitted or received message 400 may be stored in the enhancement table 310.

Message duration parameter 414: the parameter values that indicate, in units of seconds, the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) to be presented to or made accessible to the user via the messaging client 104.

Message geolocation parameters 416: geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. A plurality of message geolocation parameter 416 values may be included in the payload, each of which is associated with a content item included in the content (e.g., a particular image within the message image payload 406 or a particular video within the message video payload 408).

Message story identifier 418: an identifier value that identifies one or more collections of content (e.g., the "story" identified in story table 314) associated with a particular content item in message image payload 406 of message 400. For example, the identifier value may be used to associate each of the plurality of images within the message image payload 406 with a plurality of content sets.

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

Message sender identifier 422: an identifier (e.g., a messaging system identifier, an email address, or a device identifier) indicating the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

Message recipient identifier 424: an identifier (e.g., a messaging system identifier, an email address, or a device identifier) indicating the user of the client device 102 to which the message 400 is addressed.

The contents (e.g., values) of the various components of message 400 may be pointers to locations in a table where the content data values are stored. For example, the image value in the message image payload 406 may be a pointer (or address) to a location within the image table 312. Similarly, values within message video payload 408 may point to data stored within video table 304, values stored within message enhancement 412 may point to data stored within enhancement table 310, values stored within message story identifier 418 may point to data stored within story table 314, and values stored within message sender identifier 422 and message receiver identifier 424 may point to user records stored within entity table 306.

Fig. 5 illustrates a head wearable device 500 according to an example embodiment. Fig. 5 shows a perspective view of a head wearable device 500 according to an example embodiment. In fig. 5, the head wearable device 500 is a pair of eyeglasses. In some embodiments, the head wearable device 500 may be sunglasses or goggles. Some implementations may include one or more wearable devices (such as a pendant with an integrated camera device that is integrated with, in communication with, or coupled to the head wearable device 500 or the client device 102). Any desired wearable device may be used in connection with embodiments of the present disclosure, such as a watch, earphone, wristband, earbud earphone, garment (such as a hat or jacket with integrated electronics), clip-on electronic device, or any other wearable device. It is understood that, although not shown, one or more portions of the system included in the head wearable apparatus 500 may be included in a client device 102 (e.g., machine 900 in fig. 9) that may be used in conjunction with the head wearable apparatus 500.

In fig. 5, the head wearable device 500 is a pair of eyeglasses comprising a frame 506, the frame 506 comprising a frame (or rim) coupled to two handles (or temples) via hinges and/or end pieces, respectively. The frame of the frame 506 carries or accommodates a pair of lenses (e.g., lens 508a and lens 508 b). The frame 506 includes a first (e.g., right) side coupled to the first handle and a second (e.g., left) side coupled to the second handle. The first side of the frame 506 is opposite the second side.

The head wearable device 500 also includes a camera module (not shown) including a camera lens (e.g., camera lens 504a, camera lens 504 b) and at least one image sensor. The camera lens 504a and the camera lens 504b may be a perspective camera lens or a non-perspective camera lens. The non-see-through camera lens may be, for example, a fisheye lens, a wide angle lens, an omnidirectional lens, or the like. The image sensor captures digital video through camera lens 504a and camera lens 504 b. The image may also be a still image frame or a video comprising a plurality of still image frames. The camera module may be coupled to the frame 506. As shown in fig. 5, the frame 506 is coupled to the image pickup device lens 504a and the image pickup device lens 504b such that the image pickup device lenses (e.g., the image pickup device lens 504a, the image pickup device lens 504 b) face forward. The camera lens 504a and the camera lens 504b may be perpendicular to the mirror 508a and the mirror 508 b. The camera module may include a dual front camera that is spaced apart by the width of the frame 506 or the width of the head of the user of the head wearable device 500.

In fig. 5, two handles (or temples) are coupled to microphone housing 502a and microphone housing 502b, respectively. The first and second handles are coupled to opposite sides of the frame 506 of the head wearable device 500. The first handle is coupled to the first microphone housing 502a and the second handle is coupled to the second microphone housing 502b. Microphone housing 502a and microphone housing 502b may be coupled to the stem between the frame 506 and the position of the temple tip. Microphone housing 502a and microphone housing 502b may be located on either side of a user's temple when the user wears head wearable device 500.

As shown in fig. 5, microphone housing 502a and microphone housing 502b enclose a plurality of microphones (not shown). Microphones are air interface sound collection devices that convert sound into an electrical signal. More specifically, a microphone is a transducer that converts sound pressure into an electrical signal (e.g., an acoustic signal). The microphone may be a digital or analog microelectromechanical system (MEMS) microphone. The acoustic signal generated by the microphone may be a Pulse Density Modulated (PDM) signal.

Although a flowchart described below may show the operations as a sequential process, many of the operations can be performed in parallel or concurrently. Further, the order of the operations may be rearranged. The process is terminated when the operation of the process is completed. The process may correspond to a method, a program, an algorithm, etc. The operations of a method may be performed in whole or in part, may be performed in combination with some or all of the operations in other methods, and may be performed by any number of different systems, such as the systems described herein, or any portion thereof, such as a processor included in any of the systems.

User-defined scene space

FIG. 6 is a flowchart of an example method for generating a user-defined contextual space according to some example embodiments. In some examples, the method 600 may be implemented by a user operating the head wearable device 500. In one example, a processor in the contextual space customizer 130, a processor in the client device 102, a processor in the messaging server system 108, or any combination thereof may perform the operations in the method 600.

At operation 602, the scene space customizer 130 receives an image via the camera device. The image includes a view of the physical space. For example, the physical space may be a view of a kitchen and living room. At operation 604, the contextual space customizer 130 receives an input associated with a virtual boundary of a first portion of the physical space. The virtual boundary is defined by two points in the first portion of the physical space. The input may be two points in the first portion. In one example, the first portion of the physical space may represent a kitchen. The first point may be at a wall that serves as the leftmost boundary of the kitchen, and the second point may represent the rightmost boundary of the kitchen. The position of the camera device can be used as additional boundary information. For example, the location of the camera may determine whether the kitchen is in front of the user or behind the user. In some examples, the virtual boundary is displayed on the head wearable device 500 as an augmented reality content item.

At operation 606, based on the first input, the contextual space customizer 130 determines a virtual volume of the first portion of the physical space. For example, the scene space customizer 130 may generate a plurality of vectors based on the two points and calculate the volume of the first portion using the plurality of vectors. The first vector may represent the distance between two points, the second vector represents gravity, and the third vector represents an average of the heights of the two points.

At operation 608, the contextual space customizer 130 receives data corresponding to the first portion of the physical space, the data including a room identity, a set of room sizes, and user room preferences. The room identity may indicate a unique identity of the first part. For example, the room identification may be "kitchen". In some examples, the room identity may be selected by the user through the head wearable device 500 from a list of common room identities (e.g., living room, kitchen, bathroom, etc.). In some examples, the room identification may be a unique identification generated by the user. A set of room sizes may be received from a virtual boundary determined by a user. The user preferences may include augmented reality content items associated with a first portion of the physical space that are frequently used by the user. For example, while in the kitchen, the user may choose to superimpose a virtual timer on the wall near the kitchen range. In another example, the user may superimpose a virtual recipe book on a food preparation table in the kitchen. The augmented reality content items may be retrieved by a user from one or more databases 126 via the network 112.

At operation 610, the scenario space customizer 130 stores the virtual volume in association with the received data. The virtual volumes may be stored in one or more databases 126.

In some examples, the user may define a second virtual boundary within the physical space. For example, the user may define a "living room". The second virtual boundary is defined by a second set of two points in a second portion of the physical space. The second set of two points is received by the user via the head wearable device 500. The scenario space-customizer 130 determines a second virtual volume of the second portion of the physical space and receives second data corresponding to the second portion of the physical space. The second data includes at least a room identification (e.g., "living room"), a second set of room dimensions (e.g., a second virtual boundary), and a second user preference. The second user preference may include an augmented reality content item associated with a second portion of the physical space that is frequently used by the user.

Automatically populating virtual content

FIG. 7 is a flowchart of an example method for populating virtual content in semantically tagged virtual objects, according to some example embodiments. In some examples, method 700 may be implemented by a user operating head wearable device 500. In one example, a processor in the contextual space customizer 130, a processor in the client device 102, a processor in the messaging server system 108, or any combination thereof may perform the operations in the method 700.

At operation 702, the scene space customizer 130 receives an image of a portion of the physical space from the camera device. The camera device may be the camera device of the head wearable device 500. Upon receiving a portion of the physical space, the contextual space customizer 130 may scan the portion to identify objects within the portion. The identification of objects within the portion may include identifying one or more categories associated with the object and a location of each object in the portion of physical space. For example, the contextual space customizer 130 may scan kitchen areas within a residence. At operation 702, the contextual space customizer 130 may identify a coffee pot, a console (counter), and a kitchen range. The scene space customizer 130 may determine that the console is beside the kitchen range and that the coffee maker is in the middle of the console. The object class associated with each item may be a predetermined class. For example, in a kitchen, object categories may include: cookware, tableware, appliances, etc.

At operation 704, the contextual space customizer 130 identifies a portion of the physical space. In some examples, a portion of the physical space is associated with the virtual volume depicted in fig. 6. The identification of a portion of the physical space may involve retrieval of data associated with the portion, such as room identification, a set of room sizes, and user preferences.

At operation 706, the contextual space customizer 130 accesses the augmented reality content item associated with the identified portion of the physical space. The augmented reality content item may comprise a lens or a software application. In one example, the contextual space customizer 130 accesses augmented reality content items stored in the augmentation table 310. In one example, the contextual space customizer 130 generates augmented reality content items. The contextual space customizer 130 may use data stored in the augmented table 310, other tables in the database 126, or any combination thereof to generate augmented reality content items. In some examples, the augmented reality content item includes an internet webpage. For example, where the identified portion of the physical space is a kitchen, the example augmented reality content item may include a virtual kitchen timer. In another example, the augmented reality content item may be a virtual recipe book.

In some examples, a set of augmented reality content items is displayed on a display coupled to a head wearable device. The scene space customizer 130 may receive a selection of one of the augmented reality content items from the set of augmented reality content items and cause the selected augmented reality content item to be displayed.

At operation 708, the contextual space customizer 130 identifies locations within a portion of the physical space. At operation 710, the contextual space customizer 130 causes the augmented reality content item at a location within a portion of the physical space to be displayed on a display coupled to the head wearable device. For example, the contextual space customizer 130 may identify the console and display the virtual recipe book onto the console.

In one embodiment, the location is identified using a machine learning model. The machine learning model may consider a category associated with the augmented reality content item. Based on the category of the augmented reality content item and the location of the object within a portion of the physical space, the machine learning model may determine a location of the augmented reality content item.

In another embodiment, the location is provided by a user of the head wearable device 500. For example, a user may select an arrangement of augmented reality content items using the head wearable apparatus 500 or a client device communicatively coupled to the head wearable apparatus 500.

In another embodiment, the location is determined based on historical user data. The contextual space customizer 130 may store historical user behavior of users comprising particular augmented reality content items within particular portions of physical space in one or more databases 126. For example, if the user repeatedly selects to display a virtual kitchen timer on a wall behind his kitchen range on the display of his head wearable device 500, the situational space customizer 130 may automatically display the virtual kitchen timer on a wall behind his kitchen range based on historical user behavior data.

User-aligned spatial volume

FIG. 8 is a flowchart of an example method for generating a user-aligned spatial volume, according to some example embodiments. In some examples, method 800 may be implemented by a user operating head wearable device 500. In one example, a processor in the contextual space customizer 130, a processor in the client device 102, a processor in the messaging server system 108, or any combination thereof may perform the operations in the method 800.

At operation 802, the contextual space customizer 130 receives an image from a camera device coupled to the head wearable device 500. The image includes a view of the object. For example, the object may be a console in a kitchen that serves as a food preparation station. At operation 804, the contextual space customizer 130 receives a first input associated with a virtual boundary of an object from the head wearable device 500. The virtual boundary is defined by two points on the perimeter of the object. For example, in the case where the kitchen console is a rectangle having four corners, the user may define the bezel by selecting the lower left corner of the console as the first point and the lower right corner as the second point.

At operation 806, the contextual space customizer 130 generates a volume of objects based on the virtual boundaries.

The contextual space customizer 130 may generate a volume using two points received by the user.

At operation 808, the contextual space customizer 130 causes a representation of the volume to be presented on a display device coupled to the head wearable device. The representation of the volume may be displayed as an augmented reality content item. At operation 810, the contextual space customizer 130 receives a second input from the head wearable device 500. The second input is associated with an adjustment to the representation of the volume. The adjustment may be received based on a change in position of a user wearing the head wearable device 500. The user may change his position to align the representation of the volume with the object. The adjustment of the representation of the volume may occur in real time or near real time.

At operation 812, the contextual space customizer 130 causes the adjusted volumetric representation to be presented on a display device coupled to the head wearable device. The adjusted volumetric representation may be stored in one or more databases 126. In some examples, the contextual space customizer 130 receives data corresponding to objects from a user. For example, a user may receive an object identification and an augmented reality content item associated with the object.

Machine architecture

Fig. 9 is a diagrammatic representation of a machine 900 within which instructions 910 (e.g., software, programs, applications, applets, apps, or other executable code) for causing the machine 900 to perform any one or more of the methods discussed herein may be executed. For example, instructions 910 may cause machine 900 to perform any one or more of the methods described herein. Instructions 910 transform a generic, un-programmed machine 900 into a specific machine 900 programmed to perform the described and illustrated functions in the manner described. The machine 900 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 900 may operate in the capacity of a server machine or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 900 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 telephone, a smart phone, 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 910 that specify actions to be taken by machine 900. Furthermore, while only a single machine 900 is illustrated, the term "machine" shall also be taken to include a collection of machines that individually or jointly execute instructions 910 to perform any one or more of the methodologies discussed herein. For example, the machine 900 may include the client device 102 or any one of a plurality of server devices forming part of the messaging server system 108. In some examples, machine 900 may also include both a client system and a server system, where 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.

The machine 900 may include a processor 904, a memory 906, and input/output (I/O) components 902, which may be configured to communicate with each other via a bus 940. In an example, the processor 904 (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, the processor 908 and the processor 912 to execute the instructions 910. The term "processor" is intended to include multi-core processors, which may include two or more separate processors (sometimes referred to as "cores") that may concurrently execute instructions. Although fig. 9 shows multiple processors 904, machine 900 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.

Memory 906 includes a main memory 914, a static memory 916, and a storage unit 918, all accessible by processor 904 via bus 940. Main memory 906, static memory 916, and storage unit 918 store instructions 910 that implement any one or more of the methods or functions described herein. The instructions 910 may also reside, completely or partially, within the main memory 914, within the static memory 916, within the machine-readable medium 920 within the storage unit 918, within at least one processor of the processors 904 (e.g., within the cache memory of the processor), or any suitable combination thereof, during execution thereof by the machine 900.

I/O component 902 can comprise various components for receiving input, providing output, producing output, sending information, exchanging information, capturing measurement results, and the like. The particular I/O component 902 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 would be unlikely to include such a touch input device. It should be appreciated that I/O component 902 may comprise many other components not shown in FIG. 9. In various examples, the I/O components 902 may include a user output component 926 and a user input component 928. The user output component 926 may include a visual component (e.g., a display such as a Plasma Display Panel (PDP), a Light Emitting Diode (LED) display, a Liquid Crystal Display (LCD), a projector, or a Cathode Ray Tube (CRT)), an acoustic component (e.g., a speaker), a haptic component (e.g., a vibration motor, a resistance mechanism), other signal generator, and the like. User input components 928 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), point-based input components (e.g., a mouse, touchpad, trackball, joystick, motion sensor, or other pointing instrument), tactile input components (e.g., physical buttons, a touch screen or other tactile input components that provide location and force of a touch or touch gesture), audio input components (e.g., a microphone), and the like.

In other examples, I/O component 902 can include a biometric component 930, a motion component 932, an environmental component 934, or a positioning component 936, as well as a wide range of other components. For example, the biometric component 930 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), and the like. The motion component 932 includes an acceleration sensor component (e.g., accelerometer), a gravity sensor component, a rotation sensor component (e.g., gyroscope).

Environmental components 934 include, for example, one or more cameras (with still image/photo and video capabilities), illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors for detecting the concentration of hazardous gases for safety or for measuring contaminants in the atmosphere), or other components that may provide an indication, measurement, or signal corresponding to the surrounding physical environment.

Regarding the camera, the client device 102 may have a camera system including, for example, a front camera on the front surface of the client device 102 and a rear camera on the rear surface of the client device 102. The front-facing camera may, for example, be used to capture still images and video (e.g., "self-timer") of the user of the client device 102, which may then be enhanced with the enhancement data (e.g., filters) described above. For example, a rear camera may be used to capture still images and video in a more conventional camera mode, which images are similarly enhanced with enhancement data. In addition to the front-end camera and the rear-end camera, the client device 102 may also include a 360 ° camera for capturing 360 ° photos and videos.

Further, the camera system of the client device 102 may include dual rear-facing cameras (e.g., a main camera and a depth sensing camera), or even triple, quadruple, or quintuple rear-facing camera configurations on the front-to-back side of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a tele camera, a macro camera, and a depth sensor.

The positioning component 936 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects barometric pressure from which altitude may be derived), an orientation sensor component (e.g., a magnetometer), and the like.

Communication may be implemented using a variety of techniques. The I/O component 902 also includes a communications component 938, the communications component 938 operable to couple the machine 900 to the network 922 or device 924 via a corresponding coupling or connection. For example, communications component 938 may include a network interface component or another suitable device to interface with network 922. In other examples, communications component 938 may include a wired communications component, a wireless communications component, a cellular communications component, a Near Field Communications (NFC) component,Parts (example)For example, a->Low energy consumption),>components, and other communication components for providing communication via other forms. Device 924 may be another machine or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

Further, communications component 938 may detect the identifier or include components operable to detect the identifier. For example, communications component 938 may include a Radio Frequency Identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, aztec codes, data matrices, data symbols (Dataglyph), maximum codes (MaxiCode), PDF417, ultra codes (Ultra Code), UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying marked audio signals). In addition, various information may be available via communications component 938, e.g., located via Internet Protocol (IP) geolocation, via Signal triangulation results in location, detection of NFC beacon signals that may indicate a particular location, and so on.

The various memories (e.g., main memory 914, static memory 916, and memory of processor 904) and storage unit 918 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 910), when executed by processor 904, cause various operations to implement the disclosed examples.

The instructions 910 may be transmitted or received over the network 922 via a network interface device (e.g., a network interface component included in the communications component 938) using a transmission medium and using any of a number of well-known transmission protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, instructions 910 may be transmitted or received via a coupling (e.g., peer-to-peer coupling) to device 924 using a transmission medium.

Software architecture

Fig. 10 is a block diagram 1000 illustrating a software architecture 1004 that may be installed on any one or more of the devices described herein. The software architecture 1004 is supported by hardware such as a machine 1002 that includes a processor 1020, memory 1026, and I/O components 1038. In this example, the software architecture 1004 may be conceptualized as a stack of layers, with each layer providing a particular function. The software architecture 1004 includes layers such as an operating system 1012, libraries 1010, frameworks 1008, and applications 1006. In operation, the application 1006 activates the API call 1050 through the software stack and receives the message 1052 in response to the API call 1050.

Operating system 1012 manages hardware resources and provides common services. Operating system 1012 includes, for example, a kernel 1014, services 1016, and drivers 1022. The core 1014 acts as an abstraction layer between the hardware layer and other software layers. For example, core 1014 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functions. Service 1016 may provide other common services for other software layers. The drivers 1022 are responsible for controlling or interfacing with the underlying hardware. For example, the number of the cells to be processed, the drivers 1022 may include display drivers an imaging device driver,Or (b)Low power consumption drive, flash memory drive, serial communication drive (e.g., USB drive),Drivers, audio drivers, power management drivers, etc.

Library 1010 provides the common low-level infrastructure used by applications 1006. The library 1010 may include a system library 1018 (e.g., a C-standard library), the system library 1018 providing functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, libraries 1010 may include API libraries 1024, such as media libraries (e.g., libraries for supporting presentation and manipulation of various media formats, such as moving Picture experts group-4 (MPEG 4), advanced video coding (H.264 or AVC), moving Picture experts group layer-3 (MP 3), advanced Audio Coding (AAC), adaptive Multi-Rate (AMR) audio codec, joint Picture experts group (JPEG or JPG) or Portable Network Graphics (PNG)), graphics libraries (e.g., openGL framework for presentation in two-dimensional (2D) and three-dimensional (3D) in graphical content on a display), database libraries (e.g., SQLite providing various relational database functions), web libraries (e.g., webKit providing web browsing functions), and the like. The library 1010 may also include various other libraries 1028 to provide many other APIs to the application 1006.

Framework 1008 provides a common high-level infrastructure used by applications 1006. For example, framework 1008 provides various Graphical User Interface (GUI) functions, advanced resource management, and advanced location services. Framework 1008 may provide a wide variety of other APIs that may be used by applications 1006, some of which may be specific to a particular operating system or platform.

In an example, the applications 1006 can include a home application 1036, a contact application 1030, a browser application 1032, a book reader application 1034, a location application 1042, a media application 1044, a messaging application 1046, a gaming application 1048, and a variety of other applications such as a third party application 1040. The application 1006 is a program that executes functions defined in the program. One or more of the applications 1006 that are variously structured may be created using a variety of programming languages, such as an object oriented programming language (e.g., objective-C, java or C++) or a procedural programming language (e.g., C-language or assembly language). In a particular example, third party application 1040 (e.g., using ANDROID by an entity other than the vendor of the particular platform) ^TM Or IOS ^TM Applications developed in Software Development Kits (SDKs) may be, for example, in IOS ^TM 、ANDROID ^TM 、The Phone's mobile operating system or another mobile software running on the mobile operating system. In this example, third party application 1040 may activate API call 1050 provided by operating system 1012 to facilitate the functionality described herein.

System with head wearable device

Fig. 11 illustrates a system 1100 in which a head wearable device 500 may be implemented, according to an example embodiment. Fig. 11 is a high-level functional block diagram of an example head wearable apparatus 500 communicatively coupling a mobile client device 102 and a server system 1130 via various networks 1136.

The head wearable device 500 includes an imaging device, such as at least one of a visible light imaging device 1110, an infrared transmitter 1112, and an infrared imaging device 1114. The camera may include the camera module of fig. 5 having camera lens 504a and camera lens 504 b.

The client device 102 may be capable of connecting with the wearable apparatus 500 using a low power wireless connection 1132 and a high speed wireless connection 1134. Client device 102 connects to server system 1130 and network 1136. The network 1136 may include any combination of wired and wireless connections.

The head wearable device 500 also includes two image displays of the image display of the optical component 1102. The two image displays of the optical assembly 1102 include one image display associated with the left lateral side and one image display associated with the right lateral side of the head wearable device 500. The head wearable device 500 also includes an image display driver 1106, an image processor 1108, low power circuitry 1124 and high speed circuitry 1116. The image display of the optical assembly 1102 is used to present images and video to a user of the head wearable device 500, including images that may include a graphical user interface.

The image display driver 1106 commands and controls the image display of the optical component 1102. The image display driver 1106 may deliver image data directly to an image display of the optical assembly 1102 for presentation or must convert the image data into a signal or data format suitable for delivery to an image display device. For example, the image data may 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., and the still image data may be formatted according to a compression format such as Portable Network Group (PNG), joint Photographic Experts Group (JPEG), tagged Image File Format (TIFF), or exchangeable image file format (Exif), etc.

As described above, the head wearable device 500 includes the frame 506 and the stem (or temple) extending from the lateral side of the frame 506. The head wearable device 500 also includes a user input device 1104 (e.g., a touch sensor or button), the user input device 1104 including an input surface on the head wearable device 500. The user input device 1104 (e.g., a touch sensor or button) is a graphical user interface for receiving input selections from a user to manipulate a presented image.

The components shown in fig. 11 for the head wearable device 500 are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the bezel or temple. Alternatively, or in addition, the depicted components may be located in a block, frame, hinge, or beam of the head wearable device 500. Left and right visible light cameras 1110 and 1410 may include digital camera device elements including images of a scene with unknown objects such as Complementary Metal Oxide Semiconductor (CMOS) image sensors, charge coupled devices, camera device lenses 504a and 504b, or any other corresponding visible or light capturing elements that may be used to capture data.

The head wearable device 500 includes a memory 1120, the memory 1120 storing instructions to perform a subset or all of the functions described herein. Memory 1120 may also include storage.

As shown in fig. 11, the high speed circuit 1116 includes a high speed processor 1118, a memory 1120, and a high speed wireless circuit 1122. In an example, the image display driver 1106 is coupled to the high speed circuit 1116 and operated by the high speed processor 1118 to drive the left and right image displays of the image display of the optical assembly 1102. The high speed processor 1118 may be any processor capable of managing high speed communications and operation of any general computing system required by the head wearable device 500. The high speed processor 1118 includes processing resources that are required to manage high speed data transmissions over a high speed radio connection 1134 to a Wireless Local Area Network (WLAN) using high speed radio circuitry 1122. In some examples, the high-speed processor 1118 executes an operating system (such as the LINUX operating system or other such operating system of the head wearable device 500) and the operating system is stored in the memory 1120 for execution. The high speed processor 1118 executing the software architecture of the head wearable device 500 is used to manage data transfer with the high speed wireless circuit 1122, among any other responsibilities. In some examples, the high-speed wireless circuitry 1122 is configured to implement an Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard (also referred to herein as Wi-Fi). In other examples, other high-speed communication standards may be implemented by the high-speed wireless circuit 1122.

The low power wireless circuit 1128 and the high speed wireless circuit 1122 of the head wearable device 500 may include a short range transceiver (bluetooth ^TM ) And wireless wide-area, local, or wide-area network transceivers (e.g., cellular or WiFi). The client device 102 (including transceivers that communicate via a low power radio connection 1132 and a high speed radio connection 1134) may be implemented using details of the architecture of the head wearable apparatus 500, which may be other elements of the network 1136, for example.

The memory 1120 includes any storage device capable of storing various data and applications including, among other things, camera data generated by the left and right visible light cameras 1110, the infrared camera 1114, and the image processor 1108, and images for display generated by the image display driver 1106 on the image display of the optical assembly 1102. Although the memory 1120 is shown as being integrated with the high-speed circuitry 1116, in other examples, the memory 1120 may be a separate, stand-alone element of the head wearable device 500. In some such examples, the circuit by wires may provide a connection from the image processor 1108 or the low power processor 1126 to the memory 1120 through a chip including the high speed processor 1118. In other examples, the high-speed processor 1118 may manage the addressing of the memory 1120 such that the low-power processor 1126 will boot the high-speed processor 1118 at any time that a read or write operation involving the memory 1120 is required.

As shown in fig. 11, the low power processor 1126 or the high speed processor 1118 of the head wearable device 500 may be coupled to a camera device (a visible light camera device 1110; an infrared transmitter 1112, or an infrared camera device 1114), an image display driver 1106, a user input device 1104 (e.g., a touch sensor or button), and a memory 1120.

The head wearable device 500 is connected with a host. For example, the head wearable apparatus 500 is paired with the client device 102 via a high-speed wireless connection 1134 or connected to the server system 1130 via a network 1136. The server system 1130 may be one or more computing devices that are part of a service or network computing system, e.g., including a processor, memory, and a network communication interface to communicate with the client device 102 and the head wearable 500 over the network 1136.

The client device 102 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication through a network 1136, a low power radio connection 1132, or a high speed radio connection 1134. The client device 102 may also store at least some of the instructions for generating the binaural audio content in a memory of the client device 102 to implement the functionality described herein.

The output components of the head wearable device 500 include visual components such as a display (such as 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 an image display driver 1106. The output components of the head wearable device 500 also include acoustic components (e.g., speakers), haptic components (e.g., vibration motors), other signal generators, and the like. Input components of the head wearable apparatus 500, client device 102, and server system 1130, such as user input device 1104, may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optoelectronic keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, touchpad, trackball, joystick, motion sensor, or other pointing instrument), tactile input components (e.g., physical buttons, a touch screen providing the location and force of a touch or touch gesture, or other tactile input components), audio input components (e.g., a microphone), and the like.

The head wearable apparatus 500 may optionally include additional peripheral elements. Such peripheral elements may include biometric sensors, additional sensors, or display elements integrated with the head wearable device 500. For example, a peripheral element may include any I/O component including an output component, a motion component, a positioning component, or any other such element described herein.

For example, the biometric means includes means for detecting an expression (e.g., hand expression, face expression, voice expression, body posture, or eye tracking), measuring a biological signal (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), and the like. The motion components include acceleration sensor components (e.g., accelerometers), gravity sensor components, rotation sensor components (e.g., gyroscopes), and the like. The positioning component includes a position sensor component (e.g., a Global Positioning System (GPS) receiver component) that generates position coordinates, wiFi or bluetooth that generates positioning system coordinates ^TM Transceivers, altitude sensor components (e.g., altimeters or barometers that detect barometric pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and so forth. Such positioning system coordinates may also be received from client device 102 via low power wireless circuit 1128 or high speed wireless circuit 1122 via low power wireless connection 1132 and high speed wireless connection 1134.

Where phrases similar to "at least one of A, B or C", "at least one of A, B and C", "one or more A, B or C", or "one or more of A, B and C" are used, the phrase is intended to be construed to mean that a may be present alone in an embodiment, B may be present alone in an embodiment, C may be present alone in an embodiment, or any combination of elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the following claims.

Glossary of terms

"carrier wave signal" refers to any intangible medium capable of storing, encoding or carrying instructions for execution by a machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. The instructions may be transmitted or received over a network using a transmission medium via a network interface device.

"client device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. The client device may be, but is not limited to, a mobile phone, desktop computer, laptop computer, portable Digital Assistant (PDA), smart phone, tablet computer, super book, netbook, laptop computer, multiprocessor system, microprocessor-based or programmable consumer electronics, game console, set top box, or any other communication device that a user can use to access a network.

"communication network" refers to one or more portions of a network, the network 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 Virtual Private Network (VPN) Metropolitan Area Networks (MANs), the Internet, portions of the Public Switched Telephone Network (PSTN), plain Old Telephone Service (POTS) networks, cellular telephone networks, wireless networks, A network, another type of network, or a combination of two or more such networks. For example, the network or portion of the network may comprise a wireless network or 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 (1 xRTT), evolution data optimized (EVDO) technology, general Packet Radio Service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, third generation partnership project (3 GPP) including 3G, fourth generation wireless (4G) networks, universal Mobile Telecommunications System (UMTS), high Speed Packet Access (HSPA), worldwide 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.

"component" refers to a device, physical entity, or logic having the following boundaries: the boundaries are defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of particular processing or control functions. The components may be combined with other components via their interfaces to perform machine processes. A component may be a packaged functional hardware unit designed for use with other components and may be part of a program that typically performs certain of the relevant functions. The components may constitute software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., processors or groups of processors) may be configured by software (e.g., an application or application part) as hardware components that operate to perform certain operations as described herein. The hardware components may also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include specialized circuitry or logic permanently configured to perform certain operations. The hardware component may be a special purpose processor such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). The hardware components may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, the hardware components may include software that is executed by a general purpose processor or other programmable processor. Once configured by such software, the hardware components become the specific machine (or specific component of the machine) uniquely tailored to perform the configured functions and are no longer general purpose processors. It should be appreciated that it may be decided, for cost and time considerations, to implement a hardware component mechanically in dedicated and permanently configured circuitry or in temporarily configured (e.g., by software configuration) circuitry. Thus, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, i.e., an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in some manner or perform certain operations described herein. Considering the example where hardware components are temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to be a special-purpose processor, the general-purpose processor may be configured at different times as respective different special-purpose processors (e.g., including different hardware components). The software configures the particular processor or processors accordingly, for example, to constitute a particular hardware component at one time and to constitute a different hardware component at a different time. A hardware component may provide information to and receive information from other hardware components. Thus, the described hardware components may be considered to be communicatively coupled. Where multiple hardware components are present at the same time, communication may be achieved by signaling (e.g., through appropriate circuitry and buses) between or among two or more of the hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components may be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving the information in the memory structure. For example, one hardware component may perform an operation and store an output of the operation in a memory device communicatively coupled thereto. Additional hardware components may then access the memory device at a later time to retrieve and process the stored output. The hardware component may also initiate communication with an input device or an output device, and may operate on a resource (e.g., a collection of information). Various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., via software) or permanently configured to perform the relevant operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refers to hardware components implemented using one or more processors. Similarly, the methods described herein may be implemented, at least in part, by processors, where a particular processor or processors are examples of hardware. For example, at least some operations of the method may be performed by one or more processors or processor-implemented components. In addition, one or more processors may also operate to support execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS) operations. For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), where the operations are accessible via a network (e.g., the internet) and via one or more suitable interfaces (e.g., APIs). The performance of certain operations may be distributed among processors, not only residing within a single machine, but also deployed across multiple machines. In some examples, the processor or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other examples, the processor or processor-implemented components may be distributed across multiple geolocations.

"computer-readable storage medium" refers to both machine storage media and transmission media. Accordingly, these terms include both storage/media and carrier/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.

"ephemeral message" refers to a message that can be accessed for a limited duration of time. The transient message may be text, images, video, etc. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. The message is temporary regardless of the setup technique.

"machine storage media" refers to single or multiple storage devices and media (e.g., centralized or distributed databases, as well as associated caches and servers) that store the executable instructions, routines, and data. Thus, the term should be taken to include, but is not limited to, solid-state memory as well as 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: nonvolatile memory including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disk; CD-ROM and DVD-ROM discs. The terms "machine storage medium," "device storage medium," "computer storage medium" mean the same and may be used interchangeably in this disclosure. The terms "machine storage medium," computer storage medium, "and" device storage medium "expressly exclude carrier waves, modulated data signals, and other such media, and at least some of the carrier waves, modulated data signals, and other such media are encompassed by the term" signal medium.

"non-transitory computer-readable storage medium" refers to a tangible medium capable of storing, encoding or carrying instructions for execution by a machine.

"signal medium" refers to any intangible medium capable of storing, encoding or carrying instructions for execution by a machine and including digital or analog communications signals, or other intangible medium to facilitate communication of software or data. The term "signal medium" shall be taken to include any form of modulated data signal, carrier wave, and the like. 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 and may be used interchangeably throughout this disclosure.

Claims

1. A method, comprising:

receiving, by one or more processors, an image from a camera device, the image comprising a view of a physical space;

receiving an input associated with a virtual boundary of a first portion of the physical space, the virtual boundary defined by two points in the first portion of the physical space, the first input including the two points in the first portion;

Determining a virtual volume of the first portion of the physical space based on the first input;

receiving data associated with the first portion of the physical space, the data including a room identification, a set of room dimensions, and user room preferences; and

the virtual volume is stored in association with the received data.

2. The method of claim 1, wherein the camera device is coupled to a head wearable device.

3. The method of claim 1, wherein determining the virtual volume further comprises:

generating a first vector representing a distance between the two points;

generating a second vector representing gravity;

generating a third vector based on an average of the heights of the two points; and

the virtual volume is determined using the first vector, the second vector, and the third vector.

4. The method of claim 2, wherein the virtual boundary is displayed as an augmented reality content item on a display coupled to the head wearable device.

5. The method of claim 2, wherein receiving data associated with a portion of the physical space comprises:

user input is received, the user input comprising data from the head wearable device.

6. The method of claim 1 further comprising:

receiving a second input associated with a second virtual boundary of a second portion of the physical space, the second virtual boundary defined by two points in the second portion of the physical space;

determining a second virtual volume of the second portion of the physical space based on the second input; and

second data associated with the second portion of the physical space is received, the second data including a second room identification, a second set of room dimensions, and a second user room preference.

7. The method of claim 1, wherein the user room preference comprises:

a first set of augmented reality content items associated with the first portion.

8. A system, comprising:

a processor; and a memory storing instructions that, when executed by the processor, configure the system to perform operations comprising:

the virtual volume is stored in association with the received data.

9. The system of claim 8, wherein the camera device is coupled to a head wearable device.

10. The system of claim 8, wherein determining the virtual volume further comprises:

generating a first vector representing a distance between the two points;

generating a second vector representing gravity;

11. The system of claim 9, wherein the virtual boundary is displayed as an augmented reality content item on a display coupled to the head wearable device.

12. The system of claim 9, wherein receiving data associated with a portion of the physical space comprises:

13. The system of claim 8 further comprising:

14. The system of claim 8, wherein the user room preference comprises:

15. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations comprising:

the virtual volume is stored in association with the received data.

16. The non-transitory computer readable storage medium of claim 15, wherein the camera device is coupled to a head wearable device.

17. The non-transitory computer-readable storage medium of claim 15, wherein determining the virtual volume further comprises:

generating a first vector representing a distance between the two points;

generating a second vector representing gravity;

18. The non-transitory computer-readable storage medium of claim 16, wherein the virtual boundary is displayed as an augmented reality content item on a display coupled to the head wearable device.

19. The non-transitory computer-readable storage medium of claim 16, wherein receiving data associated with a portion of the physical space comprises:

20. The non-transitory computer-readable storage medium of claim 15, further comprising: