Mutual affinity widgets

Abstract

An interaction system provides a transmit message to a user in a mutual affinity relationship. An interactive application of two or more users receives a notification of a mutual affinity relationship between a first user and a second user. The interactive application configures the respective intercompatible widgets by associating the intercompatible widgets with the respective other users. Icons of intercompatible widgets are provided on the user's respective home screen. Upon detection of a selection of the intercompatible widget by the first user, a message creation interface is provided to the first user, and a message is generated based on an image captured by the first user using the message creation interface. The message is then sent to the second user. The second user accesses the message using its own intercompatible widget.

Description

[0001] Priority declaration

[0002] This application claims the benefit of priority to U.S. application serial number 18 / 050,869, filed on October 28, 2022, which claims the benefit of priority to U.S. provisional application serial number 63 / 369,998, filed on August 1, 2022, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to user interfaces and, more particularly, to user interfaces for social networking. Background Art

[0004] Users like to use mobile devices, such as smart phones, to access social networking content. The use of mobile devices enables users to spontaneously share moments with others while also enjoying life in a community and participating in various activities. Mobile devices use touch screens with limited surface areas as both display devices and input devices, which limits content viewing and user interaction with the content. Therefore, a convenient process for accessing social networking content is desired. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0009] Figure 4 is a graphical representation of messages according to some examples.

[0010] Figure 5 is a flow chart of an access restriction process according to some examples.

[0011] Figure 6 A system of a head mounted device according to some examples is shown.

[0012] Fig. 7A is a flowchart of a widget configuration method according to some examples.

[0013] Figure 7B is a sequence diagram of a widget configuration method according to some examples.

[0014] Fig. 8A , Figure 8B , Figure 8C and Fig.8D is a diagram of a widget configuration method according to some examples.

[0015] Fig. 9A and Fig. 9B is a flow chart of a method of creating a message according to some examples.

[0016] Fig. 9C is a sequence diagram of the Create Message method based on some examples.

[0017] Fig. 10A and Fig. 10B A create message user interface is shown according to some examples.

[0018] Fig.11A is a flowchart of a method of receiving a message according to some examples.

[0019] Fig. 11B is a sequence diagram of a receive message method according to some examples.

[0020] Fig.12 A receiving mutual affinity message user interface is shown according to some examples.

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

[0022] Fig.14 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0023] Users of social networking systems develop relationships with other users. Some of these relationships are casual, and users in these casual relationships may rarely exchange messages. Some relationships are one-sided, where one user may send more messages to another user who rarely replies to messages or sends more information to the other user. However, some users also develop mutually strong relationships, where each user in the relationship primarily sends messages to the other user in the mutual relationship. Some users in these mutual relationships frequently exchange messages and desire a convenient method for sending and receiving messages to another user in the mutual relationship.

[0024] Many software applications have a wide range of functions or features that are accessed by users of the software applications through various user interfaces. The more features a software application has, the more user interfaces are provided to the user. Some user interfaces may have extensive or in-depth dialogs that require several user interactions before the user finds and accesses a particular feature or function. Sometimes, a user may want to use a software application to perform a specific set of operations, but the features of the software application used to perform those operations may be distributed across several user interfaces, or may be in different dialog branches of the same user interface.

[0025] Examples of the present disclosure provide a method for providing a message sender with a quick and simple way to send messages to a message recipient of a social networking system using an interactive client without explicitly invoking the interactive application from the home screen of the client system hosting the interactive application. In addition, the message sender and the message recipient access additional features of the interactive application using a simplified user interface. This reduces the number and complexity of user interactions with the interactive client compared to directly invoking the interactive client and accessing multiple user interfaces and dialog boxes to send and receive messages to and from a unique user.

[0026] In some examples, the mutual affinity widget displayed on the client system of the message sender provides a convenient way to send and receive image-based messages with the message recipient who has mutual affinity with the message sender. Social networking information is used to identify and notify users in mutual affinity relationships. When notified, the user configures its corresponding mutual affinity widget by associating its mutual affinity widget with other users. The mutual affinity widget is configured, and the mutual affinity widget icon is displayed on the home screen of the corresponding client system, such as a smart phone. The user selects the mutual affinity widget icon and is provided with a special user interface that can be used to quickly capture an image, enhance the image, and then send it to other users as a mutual affinity message. The client system of the message recipient of the mutual affinity message receives the mutual affinity message, and displays a portion of the mutual affinity message in the mutual affinity icon on the home screen of the message recipient. The message recipient selects the mutual affinity icon, and the client system provides the mutual affinity message in a user interface that provides options for replying to the sender of the mutual affinity message.

[0027] In some examples, a message recipient of a mutual affinity message responds by sending a mutual affinity message of their own.

[0028] In some examples, a message recipient of a mutual affinity message enters into a conversation with the sender of the mutual affinity message.

[0029] In some examples, a sender of a mutual affinity message enhances an image of the mutual affinity message before sending the mutual affinity message to a message recipient of the mutual affinity message.

[0030] In some examples, the mutual affinity widget includes a status indicator indicating that the message has been sent.

[0031] In some examples, the mutual affinity widget displays a portion of the message to the message recipient, thereby alerting the message recipient that they have a message from the message sender.

[0032] Networked computing environment

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

[0034] Each client system 102 may include multiple user devices, such as mobile devices 114, head mounted devices 116, and computer client devices 118, which may be communicatively connected to exchange data and messages.

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

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

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

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

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

[0040] The interactive server 124 hosts multiple systems and subsystems, as shown below. Figure 2 Give a description.

[0041] Linked Applications

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

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

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

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

[0046] The interactive 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 the form of a context-sensitive menu. For example, icons representing different applications (or applets) of the application 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).

[0047] System Architecture

[0048] Figure 2 1 is a block diagram showing additional details about the interactive system 100 according to some examples. Specifically, the interactive system 100 is shown to include an interactive client 104 and an interactive server 124. The interactive system 100 includes a number of subsystems that are supported on the client side by the interactive client 104 and on the server side by the interactive server 124. Example subsystems are discussed below.

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

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

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

[0052] The geolocation of the client system 102; and

[0053] • Social network information of the user of the client system 102 .

[0054] Enhancement can 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 can be applied to media content items (e.g., photos or videos) at client systems 102 for transmission in messages, or applied to video content such as video content streams or feeds sent from interactive clients 104. Therefore, image processing system 202 can interact with and support various subsystems of communication system 208, such as messaging system 210 and video communication system 212.

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

[0056] The image processing system 202 provides a user-based publishing platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user can also specify situations in which a particular media overlay should be provided to other users. The image processing system 202 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

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

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

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

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

[0061] The collection management system 224 is operationally responsible for managing a collection or collection of media (e.g., a collection of text, image video, and audio data). A collection of content (e.g., messages, including images, videos, text, and audio) can be organized into an "event library" or "event story". Such a collection can be made available within a specified time period (e.g., the duration of the event to which the content relates). For example, content related to a concert can be available as a "story" for the duration of the concert. The collection management system 224 can also be responsible for publishing an icon that provides a notification of a specific collection to the user interface of the interactive client 104. The collection management system 224 includes a curation function that enables collection managers to manage and curate specific content collections. For example, a curation interface enables event organizers to curate a collection of content related to a specific event (e.g., deleting inappropriate content or redundant messages). In addition, the collection management system 224 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users for including user-generated content in a collection. In such a case, the collection management system 224 operates to automatically pay such users to use their content.

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

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

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

[0065] In order to integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the interactive server 124 by the third-party server 112, or the SDK is received by the third-party server 112 in other ways. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the interactive client 104 into the web-based resource.

[0066] The SDK stored on the interactive server system 110 effectively provides a bridge between external resources (e.g., applications 106 or applets) and the interactive client 104. This gives users a seamless experience of communicating with other users on the interactive client 104 while also preserving the appearance of the interactive client 104. In order to bridge the communication between external resources and the interactive client 104, the SDK facilitates communication between the third-party server 112 and the interactive client 104. The WebViewJavaScriptBridge running on the client system 102 establishes two one-way communication channels between the external resources and the interactive client 104. Messages are sent asynchronously between the external resources and the interactive client 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

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

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

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

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

[0071] Data Architecture

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

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

[0074] The entity table 308 stores entity data and is linked (e.g., referenced) to the entity graph 310 and the profile data 302. The entity for which records are maintained within the entity table 308 may include a person, a corporate entity, an organization, an object, a place, an event, etc. Regardless of the entity type, any entity about which the interactive server system 110 stores data may be an identified entity. Each entity is provided with a unique identifier and an entity type identifier (not shown).

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

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

[0077] Profile data 302 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 302 can be selectively used and presented to other users of the interactive system 100. In the case where the entity is a person, profile data 302 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the interactive system 100 and on a map interface displayed to other users by the interactive client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a status or activity that the user can choose to transmit at a particular time.

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

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

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

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

[0082] Other augmented data that may be stored in the image table 316 include augmented reality content items (eg, corresponding to application "lenses" or augmented reality experiences). Augmented reality content items may be real-time special effects and sounds that may be added to an image or video.

[0083] As described above, augmented data includes augmented reality (AR) content items, virtual reality (VR) content items, and mixed reality (MR) content items, overlays, image transformations, images, and modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify images when they are captured using device sensors (e.g., one or more cameras) of the client system 102 and then display the modified images on the screen of the client system 102. This also includes modifications to stored content (such as video clips in a collection or group that can be modified). For example, in a client system 102 that has access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clips. Similarly, real-time video capture can use modifications to show how the video image currently captured by the sensor of the client system 102 will modify the captured data. Such data can be displayed only on the screen without being stored in the memory, or the content captured by the device sensor can be recorded and stored in the memory with or without modification (or both). In some systems, the preview feature can simultaneously show how different augmented reality content items will look in different windows in the display. For example, this can enable multiple windows with different pseudo-random animations to be viewed on the display at the same time.

[0084] Thus, data and various systems using augmented reality content items or other such transformation systems using the data to modify content may involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, 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 using transformations and animated textures of the models within the video. In some examples, tracking of points on the objects may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In further examples, an image, model, or texture may be placed in content (e.g., an image or video frame) using neural network analysis of the video frame. Thus, augmented reality content items involve both: images, models, and textures used to create transformations in the content; and additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0085] Real-time video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and save it in the memory of the device, or a sensor of the device can be used to generate a video stream. Additionally, computer animation models can be used to process any object, such as a human face and parts of a human body, an animal, or a non-living thing such as a chair, a car, or other objects.

[0086] In some examples, when a specific modification is selected together with the content to be transformed, the element to be transformed is identified by a computing device, and then if the element to be transformed is present in a frame of the video, it is detected and tracked. The elements of the object are modified according to the modification request, thereby transforming the frame of the video stream. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for the transformation of the frame that mainly refers to changing the form of the elements of the object, the characteristic points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, a grid based on the characteristic points is generated for each element of the object. The grid is used in a subsequent stage in which the elements of the object in the video stream are tracked. During the tracking process, the grid for each element is aligned with the position of each element. Then, additional points are generated on the grid.

[0087] In some examples, the transformation of some areas of the object using the elements of the object can be performed by calculating the 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 areas based on these points are generated. Then, the elements of the object are tracked by aligning the area of ​​each element with the position of each element of at least one element, and the properties of the area can be modified based on the request for modification, thereby transforming the frame of the video stream. Depending on the specific request for modification, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least part of the area from the frame of the video stream; including new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points can be selected as control points of the entire state space to be used to determine options for model animation.

[0088] In some examples of computer animation models for transforming image data using face detection, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.

[0089] Other methods and algorithms suitable for face detection may be used. For example, in some examples, landmarks are used to locate features, and landmarks represent distinguishable points that are present in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person is wearing an eye patch), secondary landmarks can be used. Such a landmark identification procedure can be used for any such object. In some examples, a set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The average shape is the average of the aligned training shapes.

[0090] The transformation system can capture an image or video stream on a client device (e.g., client system 102) and perform complex image manipulations locally on the client system 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, emotion transformations (e.g., changing a face from a frown to a smile), state transitions (e.g., aging a subject, reducing apparent age, changing gender), style transformations, application of graphical elements, and any other suitable image or video manipulations enabled by a convolutional neural network that has been configured to execute efficiently on the client system 102.

[0091] In some examples, a computer animation model for transforming image data may be used by a system in which a user may capture an image or video stream of the user (e.g., a selfie) using a client system 102 having a neural network operating as part of an interactive client 104 operating on the client system 102. The transformation system operating within the interactive client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the image data, or the computer animation model may exist in association with an interface described herein. The modification icon includes changes as a basis for modifying the user's face 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 transforming the user's image to reflect the selected modification icon (e.g., generating a smile 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 system 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 modification. That is, a user can capture an image or video stream, and once a modification icon is selected, the modified result can be presented to the user in real time or near real time. In addition, the modification can be persistent while the video stream is being captured and the selected modification icon remains toggled. Machine-taught neural networks can be used to implement such modifications.

[0092] The graphical user interface presenting the modifications performed by the transformation system can supply additional interactive options to the user. Such options can be based on an interface for initiating content capture and selection of a particular computer animation model (e.g., initiated from a content creator user interface). In various examples, the modification can persist after the initial selection of the modification icon. The user can turn the modification on or off by tapping or otherwise selecting a face 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 the transformation system, the user can 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, a single face in a group of multiple faces can be individually modified by tapping or selecting a single face or a series of single faces displayed within the graphical user interface, or such modifications can be individually switched.

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

[0094] 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. Users whose client devices have location services enabled and who are at a co-located event at a particular time may be presented with the option of contributing content to a particular live story, for example, via the user interface of the interactive client 104. Live stories may be identified to the user by the interactive client 104 based on his or her location. The end result is a "live story" told from a group perspective.

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

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

[0097] The database 304 also includes social network information collected by the social network system 222. The social network information includes mutual affinity data of users. The mutual affinity data can be used to group two or more users into mutual affinity relationships and provide additional functions of the interactive system 100.

[0098] Data communication architecture

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

[0100] Message identifier 402 : a unique identifier that identifies the message 400 .

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

[0102] Message image payload 404 : Image data captured by a camera component of the client system 102 or retrieved from a memory component of the client system 102 and included in the message 400 . Image data for a sent or received message 400 may be stored in an image table 406 .

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

[0104] Message audio payload 412 : audio data captured by a microphone or retrieved from a memory component of the client system 102 and included in the message 400 .

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

[0106] Message duration parameter 418: A parameter value indicating the amount of time in seconds that the content of a message (eg, message image payload 404, message video payload 408, message audio payload 412) is to be presented to or made accessible to a user via the interactive client 104.

[0107] Message geolocation parameters 420: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 420 values ​​may be included in the payload, with each of these parameter values ​​being associated with a content item included in the content (e.g., a specific image within a message image payload 404 or a specific video in a message video payload 408).

[0108] Message story identifier 422: An identifier value that identifies one or more content collections (e.g., a "story" identified in story table 424) associated with a particular content item in message image payload 404 of message 400. For example, multiple images within message image payload 404 may each be associated with multiple content collections using an identifier value.

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

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

[0111] • Message recipient identifier 430: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client system 102 to which the message 400 is addressed.

[0112] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table where the content data value is stored. For example, the image value in message image payload 404 may be a pointer (or address) to a location within image table 406. Similarly, the value within message video payload 408 may point to data stored within video table 410, the value stored within message enhancement data 418 may point to data stored in enhancement table 416, the value stored within message story identifier 422 may point to data stored in story table 424, and the values ​​stored within message sender identifier 428 and message recipient identifier 430 may point to user records stored within entity table 432.

[0113] Time-based access restriction architecture

[0114] Figure 5 is a schematic diagram illustrating an access restriction process 500 according to which access to content (e.g., a multimedia payload of an ephemeral message 502 and associated data) or a collection of content (e.g., an ephemeral message group 504) can be time-restricted (e.g., ephemeral).

[0115] The ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines the amount of time that the ephemeral message 502 will be displayed by the interactive client 104 to the recipient user of the ephemeral message 502. In some examples, the recipient user may view the ephemeral message 502 for up to 10 seconds, depending on the amount of time specified by the message sender using the message duration parameter 506.

[0116] The message duration parameter 506 and the message recipient identifier 508 are shown as inputs to a message timer 510, which is responsible for determining the amount of time that the ephemeral message 502 is shown to the particular receiving user identified by the message recipient identifier 508. In particular, the ephemeral message 502 is shown to the associated receiving user for a period of time determined by the value of the message duration parameter 506. The message timer 510 is shown as providing an output to a more generalized messaging system 512, which is responsible for the overall timing of displaying content (e.g., the ephemeral message 502) to the receiving user.

[0117] exist Figure 5 1. The ephemeral message 502 is shown as being included in an ephemeral message group 504 (e.g., a collection of messages in a personal story or an event story). The ephemeral message group 504 has an associated group duration parameter 514, the value of which determines the duration for which the ephemeral message group 504 is presented and accessible to users of the interactive system 100. For example, the group duration parameter 514 may be the duration of a concert, wherein the ephemeral message group 504 is a collection of content related to the concert. Alternatively, a user (an owning user or a curator user) may specify the value of the group duration parameter 514 when performing setup and creation of the ephemeral message group 504.

[0118] In addition, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 516, the value of which determines the duration for which the ephemeral message 502 will be accessible within the context of the ephemeral message group 504. Thus, a particular ephemeral message group 504 may "expire" and become inaccessible within the context of the ephemeral message group 504 before the ephemeral message group 504 itself expires according to the group duration parameter 514. The group duration parameter 514, the group participation parameter 516, and the message recipient identifier 508 each provide inputs to a group timer 518, which first operatively determines whether a particular ephemeral message 502 of the ephemeral message group 504 will be displayed to a particular receiving user, and if so, how long to display it. Note that the identity of the particular receiving user is also known to the ephemeral message group 504 due to the message recipient identifier 508.

[0119] Thus, the group timer 518 operatively controls the total lifespan of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In some examples, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 514. In another example, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 516. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration for which a particular ephemeral message 502 is displayed to a receiving user. Thus, the message duration parameter 506 determines the duration for which a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user views the ephemeral message 502 within the context of the ephemeral message group 504 or outside the context of the ephemeral message group 504.

[0120] In addition, the messaging system 512 may be operative to remove a particular ephemeral message 502 from the ephemeral message group 504 based on a determination that the particular ephemeral message 502 has exceeded the associated group participation parameter 516. For example, when the sending user has established a group participation parameter 516 of 24 hours from posting, the messaging system 512 will remove the associated ephemeral message 502 from the ephemeral message group 504 after the specified 24 hours. The messaging system 512 is also operative to remove an ephemeral message group 504 when the group participation parameter 516 for each ephemeral message 502 within the ephemeral message group 504 has expired, or when the ephemeral message group 504 itself has expired according to the group duration parameter 514.

[0121] In some use cases, the creator of a particular ephemeral message group 504 may specify an indefinite group duration parameter 514. In this case, the expiration of the group participation parameter 516 of the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself expires. In this case, a new ephemeral message 502 with a new group participation parameter 516 added to the ephemeral message group 504 effectively extends the life of the ephemeral message group 504 to a value equal to the group participation parameter 516.

[0122] In response to the messaging system 512 determining that the ephemeral message group 504 has expired (e.g., is no longer accessible), the messaging system 512 communicates with the interactive system 100 (and, for example, in particular the interactive client 104) to cause the indicia (e.g., icon) associated with the relevant ephemeral message group 504 to no longer be displayed within the user interface of the interactive client 104. Similarly, when the messaging system 512 determines that the message duration parameter 506 of a particular ephemeral message 502 has expired, the messaging system 512 causes the interactive client 104 to no longer display the indicia (e.g., icon or text identification) associated with the ephemeral message 502.

[0123] System with head mounted device

[0124] Figure 6 System 600 is shown, which includes a head mounted device 116 with a selector input device according to some examples. Figure 6 is a high-level functional block diagram of an example head mounted device 116 communicatively coupled to a mobile device 114 and various server systems 604 (e.g., an interactive server system 110) via various networks 108.

[0125] The head mounted device 116 includes one or more cameras, each of which may be, for example, at least one of a visible light camera 608 , an infrared emitter 610 , and an infrared camera 612 .

[0126] The mobile device 114 is connected to the head mounted device 116 using both a low power wireless connection 614 and a high speed wireless connection 616. The mobile device 114 is also connected to the server system 604 and the network 606.

[0127] The head mounted device 116 also includes two image displays in the optical assembly image displays 618. The two optical assembly image displays 618 include an image display associated with the left lateral side of the head mounted device 116 and an image display associated with the right lateral side of the head mounted device 116. The head mounted device 116 also includes an image display driver 620, an image processor 622, low power circuits 624 for low power consumption, and high speed circuits 626. The optical assembly image displays 618 are used to present images and videos to a user of the head mounted device 116, including images that may include a graphical user interface.

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

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

[0130] Figure 6 The components of the head mounted device 116 shown in the figure are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the frame or temples. Alternatively or additionally, the depicted components may be located in chunks, frames, hinges, or nosepieces of the head mounted device 116. The left and right visible light cameras 608 may include digital camera elements, such as complementary metal oxide semiconductor (CMOS) image sensors, charge coupled devices, camera lenses, or any other corresponding visible light or light capturing elements that can be used to capture data (including images of scenes with unknown objects).

[0131] The head mounted device 116 includes a memory 602 that stores instructions for performing a subset or all of the functions described herein. The memory 602 may also include a storage device.

[0132] like Figure 6 As shown, the high-speed circuit 626 includes a high-speed processor 630, a memory 602, and a high-speed wireless circuit 632. In some examples, the image display driver 620 is coupled to the high-speed circuit 626 and is operated by the high-speed processor 630 to drive the left image display and the right image display in the image display 618 of the optical assembly. The high-speed processor 630 can be any processor capable of managing high-speed communications and operations of any general-purpose computing system required by the head-mounted device 116. The high-speed processor 630 includes the processing resources required to manage high-speed data transmission on the high-speed wireless connection 616 to the wireless local area network (WLAN) using the high-speed wireless circuit 632. In some examples, the high-speed processor 630 executes an operating system (e.g., a LINUX operating system) or other such operating system of the head-mounted device 116, and the operating system is stored in the memory 602 for execution. In addition to any other duties, the high-speed processor 630 that executes the software architecture of the head-mounted device 116 is used to manage data transmission with the high-speed wireless circuit 632. In some examples, high-speed wireless circuit 632 is configured to implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, also referred to herein as WiFi. In some examples, high-speed wireless circuit 632 can implement other high-speed communication standards.

[0133] The low-power wireless circuit 634 and the high-speed wireless circuit 632 of the head mounted device 116 may include a short-range transceiver (Bluetooth TM ) and a wireless wide area network transceiver, a wireless local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). Mobile device 114, including a transceiver that communicates via low power wireless connection 614 and high speed wireless connection 616, can be implemented using details of the architecture of head mounted device 116, as can other elements of network 606.

[0134] The memory 602 includes any storage device capable of storing various data and applications, including camera data generated by the left and right visible light cameras 608, the infrared camera 612, and the image processor 622, as well as images generated to be displayed on the image display 618 of the optical assembly through the image display driver 620. Although the memory 602 is shown as being integrated with the high-speed circuit 626, in some examples, the memory 602 can be a separate independent element of the head mounted device 116. In some such examples, electrical wiring can provide a connection from the image processor 622 or the low-power processor 636 to the memory 602 through a chip including the high-speed processor 630. In some examples, the high-speed processor 630 can manage the addressing of the memory 602 so that the low-power processor 636 will start the high-speed processor 630 whenever a read or write operation involving the memory 602 is required.

[0135] like Figure 6 As shown, the low-power processor 636 or the high-speed processor 630 of the head-mounted device 116 can be coupled to a camera device (a visible light camera device 608, an infrared emitter 610 or an infrared camera device 612), an image display driver 620, a user input device 628 (for example, a touch sensor or a push button), and a memory 602.

[0136] The head mounted device 116 is connected to a host computer. For example, the head mounted device 116 is paired with the mobile device 114 via a high-speed wireless connection 616 or connected to a server system 604 via a network 606. The server system 604 can be one or more computing devices as part of a service or network computing system, for example, including a processor, memory, and a network communication interface to communicate with the mobile device 114 and the head mounted device 116 through the network 606.

[0137] The mobile device 114 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication via a network 606, a low-power wireless connection 614, or a high-speed wireless connection 616. The mobile device 114 may further store at least a portion of the instructions for generating binaural audio content in a memory of the mobile device 114 to implement the functions described herein.

[0138] The output components of the head-mounted device 116 include visual components, such as a display (e.g., a liquid crystal display (LCD), a plasma display panel (PDP), a light-emitting diode (LED) display, a projector, or a waveguide). The image display of the optical component is driven by the image display driver 620. The output components of the head-mounted device 116 also include acoustic components (e.g., speakers), tactile components (e.g., vibration motors), other signal generators, etc. The input components of the head-mounted device 116, the mobile device 114, and the server system 604 (e.g., user input devices 628) may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, tracking balls, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens or other tactile input components that provide the location and force of touch or touch gestures), audio input components (e.g., microphones), etc.

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

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

[0141] Fig. 7A is a flowchart of a mutual affinity widget configuration method, and Figure 7B is a sequence diagram of a mutual affinity widget configuration method, and Fig. 8A , Figure 8B , Figure 8C and Fig.8D A mutual affinity widget configuration user interface according to some examples is shown. An interactive client of the interactive system 100, such as interactive client 1 718 and interactive client 2 724, uses the mutual affinity widget configuration method 700 to configure the mutual affinity widget. The interactive client provides the user with a mutual affinity widget configuration user interface to guide the user during the configuration process. The configuration is performed when an interactive server of the interactive system 100, such as interactive server 712, notifies the interactive client that two users share mutually significant attributes, such as mutual affinity.

[0142] For purposes of example herein, the interaction of two users, a message sender (first user) and a message recipient (second user), is disclosed, although those skilled in the art of interactive systems will understand that the methods disclosed herein may be applied to any number of users.

[0143] The message sender (first user) and the message recipient (second user) are users of the interactive system 100 and maintain user accounts with the interactive system 100. The message sender (first user) uses an interactive client 1 718 hosted by a client system 1 716 to access an interactive server 712 of the interactive system 100, and in a similar manner, the message recipient (second user) uses an interactive client 2 724 hosted by a client system 1 726 to access the interactive server 712. The client systems host the respective interactive clients 718 and 724. The interactive clients include respective mutual affinity widget components 720 and 722 configured based on the mutual affinity notification data 714 received from the interactive server 712.

[0144] In operation 702, the interaction server 712 determines that the message sender (first user) and the message recipient (second user) have reached a mutual affinity relationship based on the interaction between the message sender (first user) and the message recipient (second user) using the interaction system 100. The interaction server 712 uses the Figure 2 The social network system 222 of the embodiment of the present invention collects social network information to determine the mutual affinity between the message sender (first user) and the message recipient (second user). Examples of mutual affinity include, but are not limited to: first best friend mutual affinity, in which two or more users are determined to be mutual best friends based on their frequency of interaction and the fact that they do not communicate with other users as much as they communicate with each other; common interest or activity mutual affinity, in which users have a common interest in a particular topic or activity; organizational mutual affinity, in which users share affiliation through a social club or charitable organization; and the like.

[0145] In some examples, the achievement of a mutual affinity relationship is based on the level of interaction between the message sender (first user) and the message recipient (second user). For example, the achievement of a mutual affinity relationship is determined based on matching or exceeding a threshold frequency of interactions between the message sender (first user) and the message recipient (second user). In another example, the achievement of a mutual affinity relationship is determined based on matching or exceeding a threshold number of interactions between the message sender (first user) and the message recipient (second user). In another example, the achievement of a mutual affinity relationship is determined based on matching or exceeding a threshold duration that the message sender (first user) and the message recipient (second user) have been in a specified mutual affinity relationship.

[0146] In some examples, the determination of the achievement of a mutual affinity relationship is based on a comparison of the interaction level between the message sender (first user) and the message recipient (second user) with the interaction level between the message sender (first user) and the message recipient (second user) and other users. For example, based on the interaction level between the message sender (first user) and the message recipient (second user) matching or exceeding a threshold, the message sender (first user) and the message recipient (second user) may have a "best friend" mutual affinity relationship. Although the message sender (first user) and the message recipient (second user) may have other "best friends", the interaction level between the message sender (first user) and the message recipient (second user) may exceed the interaction level between the message sender (first user) and any other user, and therefore the message sender (first user) is determined to have a mutual affinity relationship with the message recipient (second user) who is the "first best friend" of the message sender (first user). In a similar manner, the level of interaction between the message recipient (second user) and the message sender (first user) may exceed the level of interaction between the message recipient (second user) and any other user, thus determining the message recipient (second user) to have a mutual affinity with the message sender (first user) who is the "first best friend" of the message recipient (second user). In another example, the mutual affinity is determined by the message sender (first user) and the message recipient (second user) having a corresponding mutual affinity, such as but not limited to being each other's first best friend or "mutual first best friend".

[0147] In some examples, the interaction server 712 makes a determination to transmit mutual affinity notification data 714 in response to detecting that the message sender (first user) and the message recipient (second user) have established a mutual affinity relationship.

[0148] In some examples, the interaction server 712 makes a determination to transmit mutual affinity notification data 714 based on an analysis of past interactions between the message sender (first user) and the message recipient (second user) and a determination that the message sender (first user) and the message recipient (second user) have established a mutual affinity relationship.

[0149] The interaction server 712 generates mutual affinity notification data 714 describing the mutual affinity relationship. The mutual affinity notification data 714 includes user identification information identifying the message sender (first user) and the message receiver (second user), and the user identification information is used to configure mutual affinity widget 1 720 and mutual affinity widget 2 722 .

[0150] In operation 704, interactive client 1 718 and interactive client 2 724 receive mutual affinity notification data 714 and provide the corresponding message sender (first user) and message receiver (second user) with the same affinity notification data. Fig. 8A The mutual affinity widget configuration user interface 800 includes an achievement reminder user interface 804 screen or card. The achievement reminder user interface 804 includes a user identification 822 and an affinity level indicator 806, which indicates the mutual affinity level achieved between the message sender (first user) and the message recipient (second user). For example, where the mutual affinity is a mutual best friends affinity, the affinity level indicator 806 includes emojis and hues in the card that reflect the friendship level (a heart emoji with a shade if the message sender (first user) and the message recipient (second user) are each other's #1 best friends - Besties, a heart emoji if the message sender (first user) and the message recipient (second user) have been each other's #1 best friends for two consecutive weeks - BFF, and a double heart emoji if the message sender (first user) and the message recipient (second user) have been each other's #1 best friends for two consecutive months - Super BFF. In some examples, the user can customize the emojis used. The achievement reminder user interface 804 also includes a configuration button 808, which the user selects to configure its corresponding mutual affinity widget.

[0151] In some examples, the interaction server 712 detects that a message sender (first user) and a message recipient (second user) enter into a conversation, wherein the message sender (first user) and the message recipient (second user) exchange information, such as in a chat session, etc. The determination to transmit the mutual affinity notification data 714 to the interaction client 1 718 and the interaction client 2 724 is based on the fact that the message sender (first user) and the message recipient (second user) have a mutual affinity relationship and are currently in a conversation. In operation 704, the interaction client 1 718 and the interaction client 2 724 receive the mutual affinity notification data 714 and provide the message sender (first user) and the message recipient (second user) thereof with the mutual affinity notification data 714. Figure 8B Another part of the mutual affinity widget configuration user interface 800 of the embodiment of the present invention is a configuration button 808 for each user to select to configure their corresponding mutual affinity widget. The mutual affinity widget configuration user interface 800 includes a conversation reminder user interface 810 screen or card. The conversation reminder user interface 810 includes a user identification 820 and an affinity level indicator 806, which indicates the mutual affinity level reached between the message sender (first user) and the message recipient (second user). The conversation reminder user interface 810 also includes a configuration button 808 for each user to select to configure their corresponding mutual affinity widget.

[0152] In some examples, where the friendship profile user interface 812 is provided to the user, the interaction client 1 718 and the interaction client 2 724 provide Figure 8C The friendship profile user interface 812 includes a configuration button 808 that can be selected by a user to configure a mutual affinity widget.

[0153] In operation 706, the interactive client 1 718 and the interactive client 2 724 detect the selection of the configuration button 808 by the corresponding message sender (first user) or the message recipient (second user), and the interactive client 1 718 and the interactive client 2 724 configure their corresponding mutual affinity widgets 1 720 and 2 722 by associating the corresponding other users with their mutual affinity widgets. That is, the interactive client 2 724 associates the mutual affinity widget 2 722 with the message recipient (second user), and the interactive client 1 718 associates the mutual affinity widget 1 720 with the message sender (first user).

[0154] In operation 708, interactive client 1 718 and interactive client 2 724 provide Fig.8DAnother portion of the mutual affinity widget configuration user interface 800 is shown. The user selects a mutual affinity widget icon 816 from the widget selection user interface 814 and places 802 the mutual affinity widget icon 816 on the home screen user interface 818, thereby providing the mutual affinity widget icon 816 to the corresponding message sender (first user) and the message recipient (second user) on their corresponding home screen user interfaces.

[0155] In some examples, the respective client system provides the widget selection user interface 814 as part of the general services of the client system.

[0156] Although the operation of the interacting clients has been disclosed as occurring collaboratively, one or both interacting clients may operate independently.

[0157] Fig. 9A and Fig. 9B is a flowchart of a method for creating a mutual affinity message according to some examples, and Fig. 9C is a sequence diagram of the Create Message method, and Fig. 10A and Fig. 10B The create message user interface is shown. The interaction client 1 718 uses the create mutual affinity message method 900 to provide a create mutual affinity message user interface 1000 to the user so that the user can create a mutual entity message and send it to another user in a mutual affinity relationship.

[0158] In operation 902, the client system 1716 of the message sender (first user) provides a home screen user interface 818 with a mutual affinity widget icon 816. The mutual affinity widget icon 816 includes the identification of the mutual affinity user identified during the configuration of the mutual affinity widget 1720. The message sender (first user) selects the mutual affinity widget icon 816 to directly send a message to the message recipient (second user) or to start a conversation with the message recipient (second user).

[0159] In operation 904 , the client system 1 716 detects that the message sender (first user) selects the mutual affinity widget icon 816 and invokes the interaction client 1 718 .

[0160] In operation 906, interaction client 1 718 responds to being called 1002 by providing the message sender (first user) with a message creation user interface 1006. The message creation user interface 1006 includes selectable icons that the message sender (first user) selects to perform operations of creating and sending a mutual affinity message.

[0161] In operation 908, the interactive client 1 718 detects the message sender (first user)'s selection of the back button icon 1010. In response, in operation 910, the interactive client 1 718 terminates the mutual affinity create mutual affinity message method 900 and provides a user interface including a camera interface and a message feed of other users with whom the message sender (first user) sends and receives messages.

[0162] In operation 912, the interactive client 1 718 detects the selection of the mutual affinity conversation button icon 1012 by the message sender (first user). In response, in operation 914, the interactive client 1 718 terminates the create mutual affinity message method 900 and provides a conversation user interface that the message sender (first user) can use to start or continue a conversation with a mutual affinity user associated with the mutual affinity widget 1 720.

[0163] In operation 916, the interactive client 1 718 detects the selection of the setting selection button icon 1008 by the message sender (first user). In response, in operation 918, the interactive client 1 718 terminates the create mutual affinity message method 900 and provides a setting user interface to the message sender (first user), wherein the message sender (first user) can adjust various settings of the mutual affinity widget 1720.

[0164] In operation 920, the interactive client 1 718 detects the selection of the capture image button icon 1014 by the message sender (first user). In response, in operation 922, the interactive client 1 718 uses the camera system 204 of the client system 1 716 to capture image data of one or more images, such as image 1024. The image data is added to the message image payload (e.g., message image payload 404) of the mutual affinity message 944 (e.g., message 400) sent by the message sender (first user) to the message recipient (second user). In some examples, the image data includes a still image. In other examples, the image data includes video data added to the message video payload (e.g., message video payload 408) of the mutual affinity message 944.

[0165] In operation 924, the interactive client 1 718 provides the message sender (first user) with a message editing user interface 1016. The message sender (first user) may use the message editing user interface 1016 to edit and enhance the image data of the image 1024 before sending the message to the message recipient (second user).

[0166] In operation 926, the interactive client 1 718 detects that the message sender (first user) selects an enhancement icon from the enhancement icons 1022. In response, in operation 928, the interactive client 1 718 enhances the image 1024 by adding message enhancement data (e.g., message enhancement data 414) based on the selected enhancement icon. For example, the message sender (first user) can add text to the image 1024, erase a portion of the image 1024, crop the image 1024, add effects to the image 1024, etc.

[0167] In operation 930, the interactive client 1 718 detects the selection of the save message button icon 1018. In response, in operation 932, the interactive client 1 718 saves the image 1024 as a message.

[0168] In operation 938, the interactive client 1 718 detects the message sender (first user)'s selection of the back button icon 1026. In response, in operation 940, the interactive client 1 718 terminates the create mutual affinity message method 900 and returns to the home screen user interface 818.

[0169] In operation 934, the interactive client 1 718 detects the selection of the send button icon 1020 by the message sender (first user). In response, in operation 936, the interactive client 1 718 transmits the mutual affinity message 944 created according to the image 1024 to the message recipient (second user) via the interactive server 712. The interactive client 1 718 terminates the create mutual affinity message method 900, updates the mutual affinity widget icon 816 to indicate the status of the mutual affinity message 944 as having been sent to the message recipient (second user), and returns 1004 to the home screen user interface 818.

[0170] In operation 942, the interaction server 712 receives a mutual affinity message 944 intended for the message recipient (the second user).

[0171] Fig.11A is a flowchart of a method 1100 for receiving a mutual affinity message according to some examples, Fig. 11B is a sequence diagram of a method 1100 for receiving a mutual affinity message, and Fig.12 A receive mutual affinity message user interface is shown. The receive mutual affinity message method 1100 is used by the interaction client 2724 hosted by the client system 2726 to provide a mutual affinity message 944 to the message recipient (second user).

[0172] In operation 1102 , the interaction client 2 724 receives the mutual affinity message 944 transmitted from the interaction server 712 .

[0173] In operation 1104 , the interaction client 2 724 provides a portion of the mutual affinity message 944 to the message recipient (the second user) as part of the mutual affinity widget icon 1206 provided by the client system 2 726 in the message recipient's home screen user interface 1204 .

[0174] In operation 1106 , the interaction client 2 724 detects the selection of the mutual affinity widget icon 1206 by the message recipient (the second user). In operation 1108 , the interaction client 2 724 responds 1202 by providing a message interaction user interface 1208 . The message interaction user interface 1208 includes: a display of the mutual affinity message 9440 sent by the message sender (first user); a back button icon 1218, which can be selected by the message recipient (second user) to close the message interaction user interface 1208 and return to the message recipient main screen user interface 1204; an affinity message sender icon 1216, which indicates the sender of the mutual affinity message 944; a message reply button icon 1210, which can be selected by the message recipient (second user) to reply with another mutual affinity message of his own; a conversation button icon 1212, which can be selected by the message recipient (second user) to start a conversation between the message sender (first user) and the message recipient (second user); and a save message button icon 1214, which can be selected by the message recipient (second user) to save the mutual affinity message 944.

[0175] In operation 1110, the interactive client 2 724 detects the selection of the message reply button icon 1210 by the message recipient (second user). In operation 1112, the interactive client 2 724 responds 1220 by providing a mutual affinity reply message user interface 1226 used by the message recipient (second user) to send a reply mutual affinity message 1228 to the message sender (first user).

[0176] In operation 1114, the interactive client 2 724 detects the selection of the conversation button icon 1212 by the message recipient (second user). In operation 1116, the interactive client 2 724 responds 1232 by providing a mutual affinity message recipient conversation user interface 1224, which the message recipient (second user) can use to start a conversation with the message sender (first user). To this end, the interactive client 2 724 transmits the mutual affinity conversation message data 1134 to the interactive server 712. In operation 1132, the interactive server 712 receives the mutual affinity conversation message data 1134 and transmits the mutual affinity conversation message data 1134 to the interactive client 1718 of the message sender (first user). In operation 1130, the interactive client 1 718 receives the mutual affinity conversation message data 1134 and provides the mutual affinity message sender conversation user interface 1234 to the message sender (first user). The mutual affinity message sender conversation user interface 1234 includes a preview of the mutual affinity message 944 sent by the message sender (first user).

[0177] In operation 1118, the interaction client 2 724 detects the selection of the save message button icon 1214 by the message recipient (the second user). In response, in operation 1120, the interaction client 2 724 saves the mutual affinity message 944 to the memory of the client system 2 726.

[0178] In operation 1122, the interactive client 2 724 detects the message recipient (second user)'s selection of the replay mutual affinity message button icon 1222 of the mutual affinity reply message user interface 1226. In operation 1124, the interactive client 2 724 responds by replaying the mutual affinity message 944 previously sent.

[0179] In operation 1126, the interaction client 2 724 detects the message recipient (second user) selection of the back button icon 1218. In operation 1128, the interaction client 2 724 responds 1230 by terminating the receive mutual affinity message method 1100 and returning to the message recipient home screen user interface 1204.

[0180] In some examples, the interaction client 2 724 continues to display a portion of the current mutual affinity message 944 in the mutual affinity widget icon 1206 until the message sender (the first user) sends a new mutual affinity message.

[0181] In some examples, the mutual affinity message 944 is a transient message, and the interaction client 2 724 stops making the mutual affinity information 944 available to the message recipient (the second user) after a period of time.

[0182] Machine Architecture

[0183] Fig.13 1300 within which instructions 1302 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1300 to perform any one or more of the methods discussed herein. For example, the instructions 1302 may cause the machine 1300 to perform any one or more of the methods described herein. The instructions 1302 convert a general purpose, unprogrammed machine 1300 into a specific machine 1300 that is programmed to perform the functions described and illustrated in the manner described. The machine 1300 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1300 may operate as a server machine or a client machine in a server-client network environment or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1300 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a 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 1302 specifying actions to be taken by the machine 1300. In addition, although only a single machine 1300 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1302 to perform any one or more of the methods discussed herein. For example, the machine 1300 may include any of the client system 102 or a plurality of server devices forming part of the interactive server system 110. In some examples, the machine 1300 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of the particular method or algorithm are performed on the client side.

[0184] The machine 1300 may include a processor 1304, a memory 1306, and an input / output I / O component 1308 that may be configured to communicate with each other via a bus 1310. In an example, the processor 1304 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1312 that executes instructions 1302 and a processor 1314. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.13 Multiple processors 1304 are shown, but the machine 1300 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.

[0185] The memory 1306 includes a main memory 1316, a static memory 1318, and a storage unit 1320, which are all accessible by the processor 1304 via the bus 1310. The main memory 1306, the static memory 1318, and the storage unit 1320 store instructions 1302 that implement any one or more of the methods or functions described herein. The instructions 1302 may also reside, completely or partially, within the main memory 1316, within the static memory 1318, within the machine-readable medium 1322 within the storage unit 1320, within at least one of the processors 1304 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1300.

[0186] I / O components 1308 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1308 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It should be appreciated that I / O components 1308 may include Fig.131308. In various examples, the I / O components 1308 may include a user output component 1324 and a user input component 1326. The user output component 1324 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 tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1326 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0187] In other examples, the I / O component 1308 may include a biometric component 1328, a motion component 1330, an environmental component 1332, or a position component 1334, as well as a wide range of other components. For example, the biometric component 1328 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1330 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0188] Environmental components 1332 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), 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 concentrations of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

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

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

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

[0192] Various technologies may be used to implement communications. I / O components 1308 also include communications components 1336 that are operable to couple machine 1300 to network 1338 or device 1340 via corresponding couplings or connections. For example, communications components 1336 may include a network interface component or another suitable device that interfaces with network 1338. In other examples, communications components 1336 may include wired communications components, wireless communications components, cellular communications components, near field communications (NFC) components, Parts (e.g. Low energy consumption), Components and other communication components for providing communication via other forms. Device 1340 can be another machine or any peripheral device among various peripheral devices (e.g., a peripheral device coupled via USB).

[0193] In addition, the communication component 1336 can detect the identifier, or include a component that is operable to detect the identifier. For example, the communication component 1336 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 bar codes such as universal product codes (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbols (Dataglyph), MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 1336, such as location via Internet Protocol (IP) geolocation, location via NFC smart tag detection, etc. Signal triangulation to obtain location, location obtained via detection of NFC beacon signals that can indicate a specific location, etc.

[0194] Various memories (e.g., main memory 1316, static memory 1318, and memory of processor 1304) and storage unit 1320 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 1302) when executed by processor 1304 cause various operations to implement the disclosed examples.

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

[0196] Software Architecture

[0197] Fig.141400 is a block diagram illustrating a software architecture 1402 that may be installed on any one or more of the devices described herein. The software architecture 1402 is supported by hardware, such as a machine 1404 including a processor 1406, a memory 1408, and I / O components 1410. In this example, the software architecture 1402 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1402 includes layers such as an operating system 1412, a library 1414, a framework 1416, and an application 1418. In operation, the application 1418 invokes an API call 1420 through the software stack and receives a message 1422 in response to the API call 1420.

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

[0199] The libraries 1414 provide a common low-level infrastructure used by the applications 1418. The libraries 1414 may include a system library 1430 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1414 may include an API library 1432, such as a media library (e.g., a library for supporting presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presentation in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1414 may also include a variety of other libraries 1434 to provide many other APIs to the application 1418 .

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

[0201] In an example, applications 1418 may include a home application 1436, a contacts application 1438, a browser application 1440, a book reader application 1442, a positioning application 1444, a media application 1446, a messaging application 1448, a game application 1450, and a variety of other applications such as third-party applications 1452. Applications 1418 are programs that execute functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1418 constructed in various ways, 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 specific example, third-party applications 1452 (e.g., applications created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM , Mobile software running on the mobile operating system of the phone or other mobile operating systems. In this example, third-party applications 1452 can activate API calls 1420 provided by the operating system 1412 to facilitate the functions described herein.

[0202] in conclusion

[0203] Changes and modifications may be made to the disclosed examples 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 appended claims.

[0204] Glossary

[0205] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

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

[0207] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

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

[0209] "Machine-readable storage media" refers to both machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier waves / modulated data signals. The terms "computer-readable medium," "machine-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0210] "Ephemeral messages" are messages that are accessible for a limited duration. Ephemeral messages can be text, images, videos, etc. The access time for ephemeral messages can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is ephemeral.

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

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

[0213] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. A machine comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations including: receiving a notification of a mutual affinity relationship between the first user and the second user from the server; configuring the mutual affinity widget of the interactive client by associating the mutual affinity widget with the second user; providing the mutual affinity widget to the first user; as well as In response to detecting that the first user selects the mutual affinity widget, performing the following operations: providing, by the one or more processors, a message creation user interface to the first user; generating, by the one or more processors, a first message based on image data captured by the first user using the message creation user interface; as well as The first message is sent, by the one or more processors, to the second user.

2. The machine according to claim 1, wherein: The server determines the notification based on achieving an interaction level between the first user and the second user.

3. The machine according to claim 1, wherein: The server transmits a notification of the mutual affinity in response to detecting a conversation between the first user and the second user.

4. The machine according to claim 1, wherein: When the instructions are executed by the one or more processors, the machine performs an operation of providing the mutual affinity widget to the first user, and further performs the following operations: The mutual affinity widget is provided to the first user on a home screen of a client system of the first user.

5. The machine according to claim 1, wherein: When the instructions are executed by the one or more processors, the machine performs operations of generating the first message, and further performs operations including: The first message is annotated based on an annotation selected by the first user using a message editing user interface.

6. The machine according to claim 1, wherein: The instructions, when executed by the one or more processors, further cause the machine to perform operations including: receiving, via the server, a second message from a second user; as well as The one or more processors display a portion of the second message in an icon of the mutual affinity widget.

7. The machine according to claim 6, wherein: The instructions, when executed by the one or more processors, further cause the machine to perform operations including: In response to detecting a selection of the icon of the mutual affinity widget by the first user, providing the second message to the first user.

8. A method comprising: receiving, by one or more processors, a notification of a mutual affinity relationship between a first user and a second user from a server; configuring, by the one or more processors, the mutual affinity widget of the interactive client by associating the mutual affinity widget with the second user; providing, by the one or more processors, the mutual affinity widget to the first user; as well as In response to the one or more processors detecting that the first user selects the mutual affinity widget, performing operations including the following: providing, by the one or more processors, a message creation user interface to the first user; generating, by the one or more processors, a first message based on image data captured by the first user using the message creation user interface; as well as The first message is sent, by the one or more processors, to the second user.

9. The method according to claim 8, wherein: The server determines the notification based on achieving an interaction level between the first user and the second user.

10. The method according to claim 8, wherein: The server transmits a notification of the mutual affinity in response to detecting a conversation between the first user and the second user.

11. The method according to claim 8, wherein: The mutual affinity widget is provided to the first user on a home screen of a client system of the first user.

12. The method according to claim 8, wherein: Generating the first message further includes: The first message is annotated based on an annotation selected by the first user using a message editing user interface.

13. The method according to claim 8, further comprising: receiving, by the one or more processors via the server, a second message from a second user; as well as The one or more processors display a portion of the second message in an icon of the mutual affinity widget.

14. The method according to claim 13, further comprising: In response to detecting a selection of the icon of the mutual affinity widget by the first user, providing the second message to the first user by the one or more processors.

15. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors, cause a machine to perform operations comprising: receiving, by the one or more processors, a notification of a mutual affinity relationship between a first user and a second user from a server; configuring, by the one or more processors, the mutual affinity widget of the interactive client by associating the mutual affinity widget with the second user; providing, by the one or more processors, the mutual affinity widget to the first user; as well as In response to the one or more processors detecting that the first user selects the mutual affinity widget, performing operations including the following: providing, by the one or more processors, a message creation user interface to the first user; generating, by the one or more processors, a first message based on image data captured by the first user using the message creation user interface; as well as The first message is sent, by the one or more processors, to the second user.

16. The machine-readable storage medium of claim 15, wherein: The server determines the notification based on achieving an interaction level between the first user and the second user.

17. The machine-readable storage medium of claim 15, wherein: The server transmits a notification of the mutual affinity in response to detecting a conversation between the first user and the second user.

18. The machine-readable storage medium of claim 15, wherein: When the instructions are executed by the one or more processors, the machine performs an operation of providing the mutual affinity widget to the first user, and further performs the following operations: The mutual affinity widget is provided to the first user on a home screen of a client system of the first user.

19. The machine-readable storage medium of claim 15, wherein: When the instructions are executed by the one or more processors, the machine performs operations of generating the first message, and further performs operations including: The first message is annotated based on an annotation selected by the first user using a message editing user interface.

20. The machine-readable storage medium of claim 15, wherein: The instructions, when executed by the one or more processors, further cause the machine to perform operations including: receiving, via the server, a second message from a second user; and A portion of the second message is displayed in the icon of the mutual affinity widget.

Images