Relationship-agnostic messaging system
By introducing relationship-agnostic message sending and receiving functions and a recommendation engine into the interactive system, the problem of limited interaction caused by the lack of existing relationships between users is solved, improving system efficiency and user experience while ensuring privacy and security.
Patent Information
- Application Number
- CN202380030052.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-25
- Filing Date
- 2023-03-23
- Publication Date
- 2024-11-08
AI Technical Summary
In existing interactive systems, when users lack existing relationships, electronic interaction is impossible or limited, leading to inefficiency and a poor user experience.
By introducing relationship-agnostic message sending and receiving functionality into the interactive system, users are allowed to interact with other users with whom they have not established direct relationships. A matching system is used to generate a composite list of contacts, and a recommendation engine is used to recommend potential interaction targets. Visual differentiation and privacy controls are provided to ensure that receiving users can easily accept or reject messages.
It improves the efficiency and user experience of the interactive system, enabling users to interact with recommended users more easily without waiting for friends' requests for approval, and ensuring the privacy and security of receiving users.
Smart Images

Figure CN118922808A_ABST
Abstract
Description
[0001] Priority claim
[0002] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 323,905, filed on March 25, 2022, the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to interactive systems and, more particularly, to relationship agnostic messaging in interactive systems. Background Art
[0004] Electronic messaging continues to grow in popularity. Users increasingly share messages with each other that include text and / or media content items (e.g., electronic images and videos). Users also increasingly utilize mobile devices to communicate with each other using various interactive systems that include messaging functions (also referred to as chat functions) suitable for sharing such messages.
[0005] A first user of an interactive system may wish to interact with a second user, but the interactive system may prevent the first user from interacting with the second user due to the lack of an existing two-way relationship (also referred to as a friend relationship in some examples) between the two users. For example, the first user may not be able to send a message to the second user or share certain content with the second user unless the friend relationship is established in the records of the interactive system. A friend relationship may be established by the first user proposing a friend relationship to the second user and the second user accepting the friend relationship proposal (or vice versa, the second user proposing a friend relationship to the first user and the first user accepting the friend relationship proposal). Restrictions of this nature may create technical barriers that prevent certain electronic interactions between users. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] In the accompanying drawings (which are not necessarily drawn to scale), similar reference numerals may describe similar components in different views. To more 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:
[0007] Figure 1 is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, according to some examples.
[0008] Figure 2 is a diagrammatic representation of an interactive system having both client-side and server-side functionality according to some examples.
[0009] Figure 3is a diagrammatic representation of data structures maintained in a database according to some examples.
[0010] Figure 4 is a relationship diagram according to some examples, which shows details about various data structures and interactions in and with the interactive system.
[0011] Figure 5 is a flow diagram illustrating a method of facilitating messaging or other interactions between entities of an interactive system according to some examples.
[0012] Figure 6 is a set of user interface diagrams illustrating messaging user interfaces in the form of sender and recipient user interfaces according to some examples.
[0013] Figure 7 is a user interface diagram illustrating a header area of a messaging user interface according to some examples.
[0014] Figure 8 is a user interface diagram illustrating a header area of a messaging user interface according to some examples.
[0015] Fig. 9 is a user interface sequence diagram illustrating a search interface and a messaging user interface according to some examples, wherein the search interface is partially displayed.
[0016] Fig.10 is a user interface diagram illustrating an alert notification according to some examples.
[0017] Fig.11 is a user interface sequence diagram, which respectively shows a message sending and receiving interface, a view in which an action page is superimposed on the message sending and receiving interface, and a view in which a confirmation page is superimposed on the message sending and receiving interface.
[0018] Fig.12 is a user interface diagram showing a portion of a user profile interface according to some examples.
[0019] Fig.13 is a user interface diagram showing a portion of a user profile interface according to some examples.
[0020] Fig.14 is a user interface diagram showing an action page superimposed on a user profile interface according to some examples.
[0021] Fig.15 is a user interface sequence diagram illustrating a message feed interface and an alert notification superimposed on the message feed interface according to some examples.
[0022] Fig.16is a user interface diagram illustrating a recipient user interface according to some examples.
[0023] Fig.17 is a user interface diagram illustrating a contact settings interface according to some examples.
[0024] Fig.18 is a user interface diagram illustrating a user profile interface according to some examples.
[0025] Fig.19 is a user interface diagram illustrating a conversation creation interface according to some examples.
[0026] Fig. 20 is a user interface diagram illustrating a message feed interface including recommendations according to some examples.
[0027] Fig.21 is a user interface diagram illustrating a message feed interface including recommendations according to some examples.
[0028] Fig. 22 is a user interface diagram illustrating a sender user interface according to some examples.
[0029] Fig.23 is a graphical representation of messages according to some examples.
[0030] Fig.24 is a flow chart of an access restriction process according to some examples.
[0031] Fig.25 A head mounted device according to some examples is shown.
[0032] Fig.26 is a block diagram illustrating a software architecture within which examples may be implemented.
[0033] Fig. 27 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein. DETAILED DESCRIPTION
[0034] The example interactive system enables users to interact with others without waiting for friend request approval. In some examples, existing users of the interactive system can interact with people in their electronic address book (e.g., provided by a contact management application on a mobile device) without prior commitment to establish a two-way relationship (e.g., a "friend relationship"). Interacting with a user may involve sharing messages or other content (e.g., a map location).
[0035] The user profile interface may be modified or supplemented to provide details of the association between two users, for example, indicating to the active user that the other user is in their electronic address book, even if the other user is not recorded as a friend in the interactive system. Thus, the example technical problem of users being unable to interact or being limited to certain interactions due to a lack of existing (direct) relationships in the interactive system may be solved or alleviated by the relationship-agnostic messaging functionality.
[0036] The example interactive system performs a matching operation between a user relationship record in the interactive system and other user relationship records (such as a user's electronic address book record). A composite list of contacts may be generated for a subject user, the composite list of contacts including users who have a direct (such as a two-way) relationship with the subject user in the interactive system and users who do not have such a (direct) relationship. The composite list of contact identifiers may then be presented to the subject user. In some examples, the subject user's feed interface is automatically updated to surface contact information and / or messages from other users who do not maintain a two-way relationship with the subject user. The contact presentation process may include visually distinguishing and presenting the electronic contact identifiers of users who maintain a two-way relationship with an active user and users who do not maintain a two-way relationship with the active user. Therefore, the example technical problem of improving the efficiency or intuitiveness of the interactive system may be solved or alleviated.
[0037] In some examples, the technical problem of improving the efficiency or intuitiveness of the interactive system can be further solved or alleviated by a recommendation engine that identifies users to be presented to the active user as "recommended friends." Such recommendations can be surfaced in the feed interface to enable the active user to more easily interact with the recommended user without having to wait for the friend request to be approved. These recommendations can be dynamically generated so that the feed interface is automatically updated.
[0038] In addition, the example methods and systems described herein provide various technical functions and safeguards that allow relationship-agnostic messaging on a limited basis while ensuring that receiving users can easily accept or reject messages from sending users and specify protection and privacy.
[0039] When the effects of the present disclosure are considered together, one or more methods described herein can improve known systems, provide additional functionality (such as but not limited to the above), make them easier, faster, or more intuitive to operate, and / or eliminate the need for certain work or resources that would otherwise be involved in the electronic interaction process. As a result, computing resources used by one or more machines, databases, or networks can be more efficiently utilized or even reduced.
[0040] Networked computing environment
[0041] Figure 11 is a block diagram illustrating an example interactive system 100 for facilitating interactions over a network (e.g., exchanging text messages, conducting text audio and video calls, or playing games). The interactive system 100 includes multiple user systems 102, each of which hosts multiple applications including an interactive client 104 and other applications 106. Each interactive client 104 is communicatively coupled to other instances of the interactive client 104 (e.g., hosted on respective other user systems 102), an interactive server system 108, and a third-party server 110 via one or more communication networks including a network 112 (e.g., the Internet). The interactive client 104 can also communicate with the locally hosted application 106 using an application program interface (API).
[0042] Each user system 102 may include multiple user devices, such as mobile devices 128, head mounted devices 126, and computer client devices 130, which are communicatively connected to exchange data and messages. The interactive clients 104 interact with other interactive clients 104 and with the interactive server system 108 via the network 112. The data exchanged between the interactive clients 104 (e.g., interactions 124) and between the interactive clients 104 and the interactive server system 108 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).
[0043] The interactive server system 108 provides server-side functions to the interactive clients 104 via the network 112. 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 108, it may be a design choice whether certain functions are located within the interactive clients 104 or within the interactive server system 108. For example, it may be technically preferred to initially deploy certain technologies and functions within the interactive server system 108, but later migrate the technologies and functions to the interactive clients 104 where the user system 102 has sufficient processing power.
[0044] The interactive server system 108 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, entity relationship 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.
[0045] Turning now specifically to the interaction server system 108, the API server 114 is coupled to and provides a programming interface to the interaction server 118, making the functionality of the interaction server 118 accessible to the interaction clients 104, other applications 106, and third-party servers 110. The interaction server 118 is communicatively coupled to the database server 116, thereby facilitating access to a database 120 that stores data associated with interactions processed by the interaction server 118. Similarly, a web server 122 is coupled to the interaction server 118 and provides a web-based interface to the interaction server 118. To this end, the web server 122 handles incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.
[0046] The API server 114 receives and sends interaction data (e.g., commands and message payloads) between the interaction server 118 and the user system 102 (and, for example, the interaction client 104 and other applications 106) and the third-party server 110. Specifically, the API server 114 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 118. The API server 114 exposes various functions supported by the interaction server 118, including account registration; login function; sending interaction data from a particular interaction client 104 to another interaction client 104 via the interaction server 118; transferring media files (e.g., images or videos) from the interaction client 104 to the interaction server 118; setting up a collection of media data (e.g., a story); retrieving a list of friends (or other related users) of a user of the user system 102; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends in a social graph; and opening application events (e.g., related to the interaction client 104). The interactive server 118 hosts multiple systems and subsystems, as described below. Figure 2 Give a description.
[0047] Linked Applications
[0048] 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 user system 102, or a small-scale version of the application (e.g., a "mini program") hosted on the user system 102 or located at the remote end of the user system 102 (e.g., on a third-party server 110). 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).
[0049] 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 user 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 user system 102. Small-scale versions of such applications 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 110 and processing such a document.
[0050] In response to determining that the external resource is a locally installed application 106, the interactive client 104 instructs the user system 102 to launch the external resource by executing 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 110 (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.
[0051] The interactive client 104 can notify the user of the user 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 notifications related to external resources currently or recently used by one or more members in the user group to participants in a conversation (e.g., a chat conversation) in the interactive client 104. One or more users can be invited to join an active external resource or start an external resource that was recently used but is currently inactive (in a friend group). The external resource can provide the 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 the chat conversation. 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. In 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.
[0052] 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).
[0053] System Architecture
[0054] Figure 2 1 is a block diagram showing further 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 118. The interactive system 100 includes a plurality of subsystems supported on the client side by the interactive client 104 and on the server side by the interactive server 118.
[0055] The image processing system 202 provides various functions that enable a user to capture and enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. The camera system 204 includes control software (e.g., in a camera application) that interacts with and controls the camera hardware of the user 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.
[0056] 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 user system 102 or retrieved from the memory of the user system 102. For example, the enhancement system 206 is operable to select, present, and display media overlays (e.g., image filters or image lenses) to the interactive client 104 for enhancing real-time images received via the camera system 204 or stored images retrieved from the memory 2524 of the user system 102. These enhancements are selected and presented to the user of the interactive client 104 by the enhancement system 206 based on some input and data, such as:
[0057] The geolocation of the user system 102; and
[0058] Entity relationship information of users of the user system 102 .
[0059] 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 user 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 various subsystems of communication system 210, and supports various subsystems of communication system 210, such as messaging system 212 and video communication system 216.
[0060] Media overlays may include text or image data that can be superimposed on a photo taken by the user system 102 or a video stream produced by the user 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, the image processing system 202 uses the geolocation of the user system 102 to identify a media overlay that includes the name of a business at the geolocation of the user system 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 120 and accessed by the database server 116.
[0061] 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.
[0062] The augmented creation system 208 supports an augmented reality (AR) developer platform and includes applications for content creators (e.g., artists and developers) to create and publish augmentations (e.g., augmented reality experiences) for interactive clients 104. The augmented creation system 208 provides content creators with a library of built-in features and tools, including, for example, custom shaders, tracking techniques, templates.
[0063] In some examples, the enhancement creation system 208 provides a merchant-based publishing platform that enables merchants to select specific enhancements associated with geographic locations via a bidding process. For example, the enhancement creation system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time.
[0064] The communication system 210 is responsible for enabling and processing various forms of communication and interaction within the interactive system 100, and includes a messaging system 212, an audio communication system 214, and a video communication system 216. The messaging system 212 is responsible for implementing temporary or time-limited access to content by the interactive clients 104. The messaging system 212 includes multiple timers (e.g., in a transient timer system 232) that selectively enable access (e.g., for presentation and display) of messages and associated content via the interactive clients 104 based on durations 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 232 are provided below. The audio communication system 214 enables and supports audio communication (e.g., real-time audio chat) between multiple interactive clients 104. Similarly, the video communication system 216 enables and supports video communication (e.g., real-time video chat) between multiple interactive clients 104.
[0065] The user management system 218 is operationally responsible for managing user data and profiles, and includes an entity relationship system 220 that maintains information about relationships between users of the interactive system 100. The user management system 218 may be responsible for recording relationship data, performing matching operations described herein (e.g., using the matching system 234), generating combined contact data and hybrid contact lists described herein, and / or generating "friends" or "contacts" identification and recommendations for presentation to active users. The user management system 218 may also include a recommendation engine 236 that is configured to recommend other users of the interactive system 100 to a particular user for interaction and / or connection with the other user. For example, the recommendation engine 236 may be configured to detect for a particular user that the particular user has more than a predetermined number of common "friends" with another user. Based on such a determination, the user management system 218 may send or present a recommendation to the particular user to suggest that the particular user add the other user as a friend, etc., and / or suggest that the particular user interact with the other user (e.g., send a message to the other user) without first requesting to establish a "friend" relationship (as described below).
[0066] The collection management system 222 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 222 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 222 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 222 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 222 operates to automatically pay such users to use their content.
[0067] The mapping system 224 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 224 enables the display of a user icon or avatar (e.g., stored in the profile data 316) 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.
[0068] The gaming system 226 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).
[0069] The external resource system 228 provides an interface for the interactive client 104 to communicate with a remote server (e.g., a third-party server 110) to launch or access an external resource (i.e., an application or applet). Each third-party server 110 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 110 associated with a web-based resource. The application hosted by the third-party server 110 is programmed in JavaScript using a software development kit (SDK) provided by the interactive server 118. The SDK includes an application program interface (API) with functions that can be called or activated by a web-based application. The interactive server 118 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.
[0070] In order to integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the interactive server 118 by the third-party server 110, or the SDK is received by the third-party server 110 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.
[0071] The SDK stored on the interactive server system 108 effectively provides a bridge between external resources (e.g., applications 106 or applets) and the interactive client 104. This gives the user a seamless experience of communicating with other users on the interactive client 104 while also preserving the appearance of the interactive client 104. In order to bridge the communication between the external resources and the interactive client 104, the SDK facilitates the communication between the third-party server 110 and the interactive client 104. The WebViewJavaScriptBridge running on the user system 102 establishes two one-way communication channels between the external resources and the interactive client 104. Messages are sent asynchronously between the external resources and the interactive client 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.
[0072] By using the SDK, not all information from the interactive client 104 is shared with the third-party server 110. The SDK limits which information is shared based on the needs of the external resource. Each third-party server 110 provides an HTML5 file corresponding to a web-based external resource to the interactive server 118. The interactive server 118 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.
[0073] 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.
[0074] The interactive client 104 controls the type of user data shared with the external resource based on the type of external resource 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.). The advertising system 230 is operative to enable third parties to purchase advertisements to be presented to end users via the interactive client 104, and also handles the delivery and presentation of these advertisements.
[0075] Data Architecture
[0076] Figure 3 is a diagram illustrating a data structure 300 that may be stored in a database 318 of an interactive server system 108 according to some examples. Although the contents of the database 318 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).
[0077] Database 318 includes message data stored in message table 302. 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 302 are described.
[0078] The entity table 306 stores entity data and is linked (e.g., referenced) to the entity graph 308 and profile data 316. The entity for which records are maintained within the entity table 306 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 108 stores data may be an identified entity. Each entity is provided with a unique identifier and an entity type identifier (not shown).
[0079] The entity graph 308 stores information about relationships and associations between entities. For example, such relationships can be interest-based or activity-based social relationships, professional relationships (e.g., working in a common company or organization). One type of social relationship is a friend relationship, which is established through a mutual agreement between two entities. Such a mutual agreement can be established by sending an offer to establish a friend relationship from a first entity to a second entity, and accepting the offer to establish a friend relationship by the second entity.
[0080] The profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, the profile data 316 can be selectively used and presented to other users of the interactive system 100. In the case where the entity is a person, the profile data 316 includes, for example, the 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.
[0081] Where the entity is a group, profile data 316 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).
[0082] Database 318 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (data for videos is stored in video table 304) and images (data for images is stored in image table 312).
[0083] In some examples, the filter is displayed as an overlay on an image or video during presentation to the recipient user. The filter can be of various types, including a user-selected filter from a set of filters presented to the sending user by the interactive client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to the sending user based on geolocation. For example, a geolocation filter specific to a nearby or special location can be presented by the interactive client 104 within the user interface based on geolocation information determined by a global positioning system (GPS) unit of the user system 102.
[0084] Another type of filter is a data filter, which can be selectively presented to the sending user by the interactive client 104 based on other input or information collected by the user system 102 during the message creation process. Examples of data filters include the current temperature at a particular location, the current speed at which the sending user is traveling, the battery life of the user system 102, or the current time. Other augmented data that can be stored in the image table 312 include augmented reality content items (e.g., corresponding to an application "lens" or augmented reality experience). Augmented reality content items can be real-time special effects and sounds that can be added to an image or video.
[0085] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar items involving 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 the device sensor (e.g., one or more cameras) of the user system 102 and then display the modified images on the screen of the user system 102. This also includes modifications to stored content (such as video clips that can be modified in a collection or group). For example, in a user system 102 that can access 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 user 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 look in different windows in the display. For example, this may enable multiple windows with different pseudo-random animations to be viewed simultaneously on the display.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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.
[0091] 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.
[0092] The transformation system can capture an image or video stream on a client device (e.g., user system 102) and perform complex image manipulations locally on the user 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 implemented by a convolutional neural network that has been configured to execute efficiently on the user system 102.
[0093] 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 user system 102 having a neural network operating as part of an interactive client 104 operating on the user 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 user 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.
[0094] 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.
[0095] The story table 314 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 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by that user. To this end, the user interface of the interactive client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.
[0096] 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.
[0097] Another type of content collection is called a "location story" that enables users whose user system 102 is 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).
[0098] As mentioned above, video table 304 stores video data that, in some examples, is associated with messages for which records are maintained within message table 302. Similarly, image table 312 stores image data associated with messages whose message data is stored in entity table 306. Entity table 306 may associate various enhancements from enhancement table 310 with various images and videos stored in image table 312 and video table 304.
[0099] Figure 4 is a relationship diagram according to some examples, which shows Figure 1 The various data structures and interactions in the interactive system 100 shown in FIG. 1 and additional details of the interactions with the interactive system 100 are described in detail below. Figure 3 As described, the interactive system 100 maintains an entity table 306 of data or records of entities (eg, registered users) of the interactive system 100, and an entity graph 308 in which details of the relationships between these different entities are stored. Figure 4Further details of the relationships between example entities in the form of users of the interactive system 100 are shown. These relationships are recorded as relationship data stored within the database 120 of the interactive server system 108.
[0100] Entity graph 308 shows that user 402 has a bidirectional relationship 414 with user 404, a unidirectional relationship 416 with user 406, and no direct relationship 418 with user 408. Various other bidirectional and unidirectional relationships between users 402, 404, 406, 408, 410, and 412 are also reflected to illustrate entity graph 308, according to some examples.
[0101] A one-way relationship, such as one-way relationship 416 between user 402 and user 406, may result from user 406 sending a relationship request to user 402 (e.g., a request to add user 406 as a friend). Since user 402 may not have accepted the relationship request, in some examples, the relationship is considered to be one-way relationship 416. On the other hand, user 402 has a two-way relationship with user 404 because, in some examples, one party sent an invitation to establish a relationship to the other party, and the other party accepted the invitation, thereby establishing a two-way relationship 414.
[0102] Due to the establishment of relationships, such as unidirectional or bidirectional relationships recorded by the entity graph 308, as a result of the establishment of the relationship, certain automatic information sharing can occur in the context of the interactive system 100. For example, where the interactive system 100 includes an entity relationship system (such as a social media system), information, data, and / or content related to an entity (such as user 402) can be shared according to the direction of the relationship. In the case of a unidirectional relationship, the information, data, and / or content can be shared along the direction of the relationship. In the case of a bidirectional relationship, the information, data, and / or content sharing can be mutual and bidirectional between entities. In the case of the interactive system 100 including an entity relationship system (such as a social media system), the shared information can include, for example, content generated or shared by the user, geographic location information about the user, and certain profile or personal information. Therefore, as part of a bidirectional relationship, the interactive system 100 can automatically share user-generated content and / or other data between two users in the relationship, which would not be shared if there was no such relationship.
[0103] The privacy settings and systems provided by the interactive system 100 and any particular entity (such as user 402) can specify what information is shared in a one-way relationship or a two-way relationship with other entities. The privacy settings can also determine the type and scope of shared information based on the classification of the relationship type with other entities by the relevant entity.
[0104] Although in the context of the interactive system 100, it is the entity (such as user 402) who grants permissions in terms of communication, systems and methods are described herein that enable a user to initiate communication with another user. For example, in the case where there is no one-way or two-way relationship established between these entities (which can be considered as the lack of a direct relationship), the described methods and systems enable user 402 who does not have an established relationship with user 408 to send a message to user 408. In addition, the methods and systems provide various technical functions and safeguards to ensure that the receiving user (such as user 408) can easily accept or reject the message while allowing the sending and receiving of messages on a limited basis, and also provide for protection and privacy. The described methods and systems also enable the sending user 402 to easily locate the desired receiving user 408 and to easily issue an invitation for a two-way relationship 414 (such as a "friend" relationship) in the context of the interactive system 100.
[0105] It is understood that the user system 102 may host many additional applications 106 in addition to the interactive client 104. For example, Fig.26 Examples of such applications are described, such as application 2606. One such application may be a contact management application in the form of a contacts application 420 (other examples may include third-party communication applications, such as third-party messaging applications or third-party email applications, and third-party social media platform applications). The contacts application 420 maintains a set of electronic contact data 422 that may be accessed by a matching system associated with or forming part of the interactive system. Figure 4 A matching system is shown in the example form of a matching system 234 , which forms part of the interaction system 100 .
[0106] The interactive system 100 maintains its own set of contact information, which is stored in the entity table 306 and the entity graph 308. Therefore, the entity data stored in the entity table 306 and the entity graph 308 can be regarded as a first set of electronic contact data or a collection of electronic contact data, and the contact data stored by the external application (e.g., the contact data 422 maintained by the contact application 420) can be regarded as a second set of electronic contact data. Figure 4 It is shown that the matching system 234 can access both the first set of electronic contact data and the second set of electronic contact data because the matching system 234 can access the entity table 306, the entity graph 308, and the contact data 422 of the external contact application 420. The matching system 234 is operable to access both the first set of contact data and the second set of contact data to generate combined contact data 424 and make the combined contact data 424 available to the interactive system 100. The interactive system 100 can then display the combined contact data 424 in various user interfaces (e.g., Figure 4 As shown in Figure 1 The combined contact data 424 is supplemented and presented in a user interface 426 presented on the mobile device 128 of the mobile device 128. As described herein, the combined contact data 424 or an identifier linked to the combined contact data 424 can be presented in the example form of a mixed list.
[0107] Figure 5 is a flow diagram illustrating a method 500 for facilitating messaging or other interactions between entities of an interactive system 100, according to some examples. For example, the method 500 may be used to enable a user 402 to perform an interaction with a user 408 (e.g., receive a message from and / or send a message to the user 408) despite not having a direct relationship 418 with the user 408.
[0108] The method 500 begins at block 502 and proceeds to block 504, where the matching system 234 accesses a third-party application in the example form of a contacts application 420 of a particular user (referred to as a subject user) and associated contact data 422 (e.g., within an address book) maintained by the contacts application 420. The interactive system 100 may also access the contacts applications 420 and contact data 422 of multiple additional users of the interactive system 100. To this end, the interactive system 100 may request access and access the third-party application and associated contact data 422 of multiple devices of multiple users of the interactive system 100, through appropriate permissions and in accordance with the privacy settings of such multiple additional users.
[0109] At block 506, the matching system 234 performs a matching operation between the contact data 422 and the user of the interactive system 100. For example, the matching system 234 may perform a matching operation between the records within the contact data 422 and the records within the entity table 306 to identify corresponding records. To perform the matching, the matching system 234 may examine and compare various types of information included in the contact data 422, including email addresses, phone numbers, names, geographic location information, etc. In addition to identifying the matched entities, the matching system 234 also retrieves relationship data associated with the matched entities at block 506, for example, indicating whether the other user has no direct relationship with the subject user, has a one-way relationship, or has a two-way relationship.
[0110] At block 508, the matching system 234 then generates a combined list of contacts (combined contact data 424) for the subject user, which includes additional users who have a relationship (a bidirectional relationship, optionally also a unidirectional relationship) with the subject user, and additional users of the interactive system 100 for which matching records exist in the contact data 422 (e.g., contact application 420) of the subject user. The existence of matching records may be because these additional users are included in the contact data 422 of the subject user, or the subject user is included in the contact data 422 of the additional users, or a combination of both. In addition to generating a combined list of contacts including friends of the subject user and registered users of the interactive system 100 for which matching records exist, the method 500 may also include, at block 508: obtaining details of "non-users" of the interactive system 100, for example, "non-users" are users identified by contact information that is not used to register with the interactive system 100 but is found in the contact application 420 of the subject user. For example, by allowing the subject user (using details found in the contact management application) to invite non-users to register and participate in the interactive system 100, this group of "non-users" can be added to the contact identification mixed list (as described in more detail below) to facilitate the connection of non-users to the interactive system 100.
[0111] The matching system 234 passes the combined contact data 424 to the interactive system 100, which then causes the combined contact data 424 to be presented in a user interface 426, such as within the search user interface 902 or the new chat interface 1902, as a mixed list of contact identifiers (e.g., names and digital avatars) at block 510. As described above, in some examples, details of non-users may be added to the mixed list to provide the subject user with a convenient option to invite these non-users to visit the interactive system 100. These may be considered "friend recommendations" because the subject user can invite one or more non-users to join the interactive system 100 using the presented details of the non-users (e.g., phone numbers from an address book).
[0112] At box 512, as reflected by the entity graph 308, users with whom the subject user has a relationship (e.g., "friends" of the subject user) are visually distinguished from users with whom the subject user has no relationship within the presented combined contact data 424. This visual distinction may include presenting text identifying whether the user has a relationship with the subject user (e.g., is a "friend" of the subject user). As previously described, non-users may also be presented as "friend recommendations", and these non-users may be visually distinguished from other users (e.g., by an "invite" button or presented in an "invite" portion of a user interface). In addition, the combined contact data 424 may include other users with whom the subject user has a relationship, or may even include other users that are located by a particular search query but with whom the subject user has no relationship and that do not appear in the contact data (e.g., address book) of the subject user (or vice versa). Similarly, users or identifiers in the presented list may be visually distinguished from one another based on the type of relationship (or lack of relationship) with the subject user, or in the case of non-users, based on whether the identifier corresponds to a registered user of the interactive system 100.
[0113] At block 514, the interactive system 100 enables the subject user, via the interactive client 104, to initiate an interaction with another user of the interactive system 100, for example, to interact with a matched registered user of the interactive system 100, the matched registered user appearing in the contact application 420 of the subject user, but having no direct relationship with the subject user in the interactive system 100. The additional user may appear in the contact data 422 of a third-party application (e.g., the contact application 420), or may be a user of the interactive system 100 located by search but having no existing relationship with the subject user and whose information does not appear in the contact data 422. The interactive client 104 may also enable the additional user to initiate an interaction. In this way, the method 500 promotes the convenience of communication between users who may not have established and recorded relationships in the context of the interactive system 100.
[0114] The subject user initiating an interaction with another user with whom there is no relationship (or enabling another user to initiate an interaction) can be facilitated and implemented in various ways described herein. For example, various user-selectable identifiers can be presented in a message sending and receiving interface, which enable the subject user to send a message and at the same time conveniently send a request to another user to establish a two-way relationship with the subject user. Establishing such a two-way relationship in the interactive system 100 may include: soliciting and receiving permission from another user to establish such a relationship. As described herein, establishing such a two-way relationship enables specific or predetermined data or information to be automatically shared between users based on the relationship type and the privacy / authority settings of each user. The method 500 terminates at box 516.
[0115] Examples seek to address technical barriers to interaction between users of the interactive system 100 by enabling messaging and / or other interactions between users without requiring a prior establishment of a two-way relationship (eg, a friendship) between the relevant users.
[0116] Figure 6 6 is a diagram of a user interface presented by the interactive client 104 to a user of the interactive system 100 according to some examples, showing a messaging user interface in the form of example sender and receiver user interfaces (sender user interface 602 and receiver user interface 604). Figure 6 , a sender sends a message to a non-friend using a sender user interface 602, and a recipient receives the message, as shown in a recipient user interface 604. The sender user interface 602 and the recipient user interface 604 illustrate a conversation view presented by the interaction client 104.
[0117] When the user uses the interactive client 104 to open a conversation with a non-friend in the sender user interface 602 or the recipient user interface 604, the add button 606 is presented in the header portion of the relevant user interface, and a description bar 608 is attached to the header, and the text in the description bar 608 explains why the user wants to add the friend, such as "Add [last name] so they can see your stories, etc.!". The add button 606 is an example of a relationship establishment graphical element that can be selected by a specific user to invite a second user to establish a two-way relationship with the specific user in the context of the interactive system 100.
[0118] like Figure 7 As shown, once a user initiates the establishment of a two-way social relationship (e.g., requesting a friend relationship), the text in the description bar 608 is removed to make room for any related friend activity sub-text, and a friend added indicator 702 is displayed in the header to indicate that the subject user has "added" the other user (establishing a one-way relationship).
[0119] In some examples, a user can send messages that appear to be delivered on the sender's message feed, but sending a message does not guarantee that the conversation will appear on the recipient's feed. For example, privacy on the recipient's side may be subject to the recipient's privacy settings (such as the "Who can contact me?" setting, which will be described below with reference to examples). Once the other user accepts the request and a two-way relationship is established, the friend add indicator 702 is removed and a set of call buttons 802 (such as the "Friends" button 802) are presented in the header. Figure 8 ). These call buttons 802 represent calling options that were not previously available but have become available due to the establishment of a two-way relationship between the users.
[0120] Return to Figure 6And referring to the recipient user interface 604, when receiving a message from another user of the interactive system 100 with whom the recipient has not established a two-way or accepting relationship (e.g., a friend relationship), the "non-friend" conversation view header is displayed again, as is the case with the sender user interface 602. Specifically, the conversation view header also includes an add button 606 that is user-selectable for the recipient user to add the sender user as a friend and accordingly establish a friend relationship between the sender user and the recipient user.
[0121] like Figure 6 As shown, the receiving user interface 604 also displays a set of privacy control graphical elements upon receiving a message from a non-friend, including an explanatory text 610 with a user-selectable hide or block button 612 and a user-selectable agree button 614. The explanatory text 610 provides the receiving user with an explanation of the relationship (or lack of relationship) with the sending user, and provides a highly visible way for the receiving user to easily block the sending user (e.g., prohibit receiving any additional communications from the sending user). In the example shown, the explanatory text 610 identifies the sending user as a non-friend, but still invites the receiving user to communicate with the sending user by selecting an "OK" button 614 (if the receiving user chooses to do so), or to block the sender by selecting the hide or block button 612. If the "OK" button 614 is selected, the set of privacy control graphical elements can disappear and no longer be presented in the communication between the two users in question.
[0122] Thus, a subject user can send an electronic message to a recipient user, and a set of privacy control graphic elements can be presented to the recipient user in the messaging user interface, which provides a mechanism for allowing or prohibiting further communication with the subject user (in other words, one or more privacy control graphic elements can be selected by the user to allow or prohibit communication with a particular user).
[0123] Example implementations enable users to start a "non-friend" conversation with anyone by providing or enabling several technical functions or features within the interactive system 100 (particularly the interactive client 104). For example, an active (sending) user can attempt to start a conversation with any other registered user located during the user's search in the interactive system 100, and then attempt to send a message to the located user (or view messages received from the located user, if any). If the sending user does not have a two-way (e.g., friend) relationship with the other user, then when starting a conversation, a user interface is presented to the sending user, such as the sender user interface 602 (or the messaging user interface 912 described below). The sending user can start such a "non-friend" conversation through the search function, and then use the "add friend" function or context function.
[0124] Fig. 9 An example search user interface 902 is shown having a search bar 904 in which an active user of an interactive client 104 can enter a textual search query. The search results are displayed in a first list of search results from contacts (e.g., results located in a contact management application of the active user), and then in a second section, an additional list of search results that do not match any records in the active user's contact list are displayed.
[0125] To this end, in some examples, the interaction client 104 may access a set of electronic contact data associated with a third-party application (e.g., a contact application or other messaging application, such as email or other third-party messaging application) and perform a matching operation between the third-party electronic contact data and registered users of the interaction system 100 to identify entities (e.g., people) that are both in the search user's third-party application contact list and are registered users of the interaction system 100. Fig. 9 As shown, where such a match is located (eg, by matching an email address or mobile phone number), information about the related entity is displayed in a "From Contacts" section.
[0126] For entities whose contact data exists in the electronic contact data from the third-party application (e.g., user) but who are not registered users of the interactive system 100, these entities are also included in the "From Contacts" section, but an invite button 906 is displayed next to the contact identifier (e.g., name) of the entity. Accordingly, the search may return details of "non-platform" entities (non-users). These non-platform entities can be, for example, Fig. 9 The invite button 906 and text 910 ("Invite to Platform") shown in the figure are visually distinguishable from registered users of the platform. Thus, a mechanism is provided for active users to easily invite non-users to register with the interactive system 100, for example, by selecting a user-selectable invitation graphical element presented in the example form of the invite button 906, so that a registration invitation is sent to the device of the non-user (e.g., using the phone number located during the search for the user "AB deVilliers").
[0127] For entities for which a match occurs between electronic contact data associated with a third-party application and a registered user of the interactive system 100, an add button 606 is displayed adjacent to a contact identifier (e.g., name) of the matched entity within the search user interface 902. The matched entity is further identified by the term "in my contacts" (e.g., see text 914 included in the cell representing the matched user "Abel Samson").
[0128] Other registered users returned by the search, i.e., users for which no matches were found in the search user's contacts and who have no direct relationship with the search user, are displayed in the "Add Friends" section. Within the search user interface 902, user selection of a registered user's graphical identifier (e.g., avatar 908) activates a conversation view by displaying a messaging user interface 912. Fig. 9 A transition 916 from the search user interface 902 to the messaging user interface 912 is shown according to some examples. The messaging user interface 912 enables a sending user to send a message directly to a receiving user, even though these users may not have established a one-way or two-way social relationship. Thus, the selection of the avatar 908 may activate an interaction with a non-friend. As described above, the messaging user interface 912 also includes an add button 606.
[0129] In addition, as described above, the sending user's user selection of the add button 606 activates the relationship establishment procedure, establishing a one-way relationship between the sending user and the receiving user (e.g., see Figure 7 ), and an invitation to accept the relationship request is sent from the sending user to the receiving user, thereby establishing a two-way relationship. In some examples, the two-way relationship may include the permission to share certain information (such as a collection of media content and location information) between the two-way related users, and the ability of the two users to call each other, for example, via the call button 802. Similarly, in the case where only a one-way relationship is established (for example, an invitation is sent by the first user to the second user), the establishment of such a relationship may include the permission to share certain information of the first user with the second user. For example, when establishing a one-way relationship, the interactive system 100 can be operated to automatically share certain media content, media content collections, personal information or location information of the first user with the second user. In the case where the invitation is accepted and a two-way relationship is established, similar information of the second user can also be shared with the first user.
[0130] Fig.10 1 is a user interface diagram according to some examples, showing an alert notification 1002 that may be presented to a user. If the conversation that the user is attempting to open has certain input or viewing interactions (e.g., messages), then the alert notification 1002 is presented to the user. For example, this may apply to messages sent by user "Abraham Cook", such as Fig. 9 The messaging user interface 912 is shown.
[0131] The user of the interactive client 104 is presented with an alert notification 1002 before being presented with further information and content of the relevant conversation. The alert notification 1002 enables the user to make an informed choice about opening a conversation with a non-friend, wherein the interactive system 100 can, for example, record certain content (e.g., message content) as "viewed" and communicate it to other users. For example, the alert notification 1002 includes text identifying the sending user and the type of interaction of the sending user, together with text reminding the receiving user that the sending user will be notified when the receiving user accesses a message sent by the sending user. The alert notification 1002 then presents two options to the receiving user: a first action option to participate in the interaction, for example, to view the message content and further continue the conversation (e.g., the start chat button 1004) and a second option to cancel the interaction (e.g., the cancel button 1006).
[0132] Fig.11 1 is a user interface diagram showing an interaction or message feed interface 1102 according to some examples. The message feed interface 1102 displays several interactions in the form of examples of messages or "chats" in which users participate, with the chat exchanges displayed in reverse chronological order (with the most recent interactions displayed at the top).
[0133] When the interaction includes sending a message to a user with whom the sending user has not established a two-way relationship (e.g., a non-friend recipient), the feed cell corresponding to the sent message is marked or visually distinguished, such as with an X that serves as a non-friend indicator. For example, feed cell 1110 is marked with indicator 1104. Indicator 1104 remains presented within message feed interface 1102 until the interaction system 100 identifies that the related entity (e.g., "Abraham Cook") has established a two-way relationship with the sending user. In addition, indicator 1104 can be selected by the user to hide or prevent further communication with the related entity. For example, when the feed cell is a message sent from a non-friend user to a viewing user, the viewing user can click on indicator 1104 to prevent any further communication from the sending user. Specifically, by clicking on indicator 1104, the viewing user activates action page 1106 (superimposed on message feed interface 1102), using which the viewing user can report, block or clear related conversations from the interaction feed and accordingly from the viewing user's message feed interface 1102.
[0134] The user selection of the clear conversation option within the action page 1106 activates a confirmation page 1108, which is displayed superimposed on the message feed interface 1102. The confirmation page 1108 communicates to the viewing user the action taken as a result of selecting the clear conversation option. For example, the user selection of the clear conversation option may result in the viewing user being informed that the non-friend user "Abraham Cook" may still be able to send messages to the sending user at a later time, and that the clear conversation action is operated to delete the relevant conversation from the viewing user's device.
[0135] Fig.12 1 is a user interface diagram illustrating a portion of a user profile interface 1202 according to some examples. For example, in response to a user selection of an appropriate cell within the user interface 902, the user profile interface 1202 is displayed to the viewing user in the context of the interactive client 104. The user profile interface 1202 for a user of the interactive system 100 (with whom the viewing user does not have an established relationship (one-way or two-way)) may provide a profile view that includes certain information and functionality that is in addition to the profile view presented for users with whom the viewing user has a relationship, or that is not available in the profile view of users with whom the viewing user has a relationship. Fig.12 In the example shown, an add button 606 and a report indicia in the form of a report icon 1204 are displayed within the user profile interface 1202 .
[0136] In addition, if Fig.13 As shown, in the case where a non-friend user sends a relationship request to a viewing user, an accept button 1302 is displayed in the user profile interface 1202 instead of the add button 606. A report icon 1204 is also displayed next to the accept button 1302.
[0137] In some examples, in addition to presenting Fig.12 and Fig.13 In addition to the user-selectable indicators described in , for non-friend users, the user profile interface can also omit displaying specific information associated with the user of the displayed user profile, such as the current geographic location, shared content, or other interactive information published via the interactive system 100.
[0138] Fig.14 1 is a user interface diagram showing an action page 1402 according to some examples, which is superimposed on the user profile interface 1202 and presents several actions that a viewing user can take with respect to a user profile of another user of the interactive system 100. These actions include reporting the other user, blocking the other user, editing the other user's name in the viewing user's interactive client 104, chat settings, etc.
[0139] Example implementations enable “non-friend” messages (also referred to as “pre-friend” messages) to surface in a user's message feed (also referred to as a chat feed) by providing or enabling several technical functions or features within the interactive system 100 , and in particular the interactive client 104 .
[0140] Fig.15 1 is a user interface sequence diagram according to some examples, showing a message feed interface 1502 and an alert notification 1504 superimposed on the message feed interface. The message feed interface 1502 displays several interactions in the form of examples of messages or "chats" in which the user is already a participant. Each chat is identified by a dedicated, user-selectable cell, and the cells are displayed in reverse chronological order (the cells for the most recent interactions are displayed at the top).
[0141] exist Fig.15 In the example above, the active user (in this case, the receiving user or recipient) receives a message from another user (“David”, e.g. Fig.15 The receiving user does not have a two-way relationship record established with the other user in the interactive system 100, but the other user is associated with a record in the contact management application of the receiving user. Therefore, the interactive system 100 allows the other user to interact with the receiving user through messages, which are presented to the receiving user in the message feed interface 1502 and are visually distinguished from other messages originating from entities that do have a two-way relationship established with the receiving user.
[0142] "Non-Friend" messages can be identified or marked in the message feed interface 1502 by text 1506, which is located in the message cell 1508 identifying the interaction, indicating to the receiving user that a message has been received from an entity that is not a "friend" of the active user, but is linked to a record in the receiving user's contact management application (displayed as "In My Contacts" in the message cell 1508, rather than "New Chat" displayed for messages received from "Friends", for example). Thus, the text 1506 serves as the first non-friend indicator of the incoming message in the form of a feed cell child text element. Once the receiving user opens the associated message, the text 1506 can disappear from the message feed interface 1502.
[0143] The "non-friend" message is further marked or visually distinguished using an X, which serves as a second non-friend indicator 1510. The non-friend indicator 1510 can remain present within the messaging interface 1502 until the interactive system 100 recognizes that the related entity has established a two-way relationship with the receiving user. In addition, as described above, the indicator 1104 is user-selectable for the receiving user to hide or prevent further communications with the related entity.
[0144] If the receiving user selects the message cell 1508, the interactive client 104 may transition 1516 to a state where the alert notification 1504 is presented before the conversation is initiated. The alert notification 1504 is presented to the receiving user to enable the receiving user to make an informed decision as to whether to proceed with the “non-friend” messaging activity. The receiving user may then decide whether to continue by selecting the turn on chat button 1512 or to adjust their privacy settings by selecting the privacy settings button 1514. In some examples, the alert notification 1504 may only be displayed once or a predetermined number of times to new users of the interactive system 100. If the receiving user decides to interact with other users and selects the turn on chat button 1512 (thereby opting into the “non-friend” messaging functionality), the interactive client 104 may present a notification such as Fig.16 The recipient user interface is shown.
[0145] Fig.16 1 is a diagram showing a user interface according to some examples, illustrating a recipient user interface 1602 that the interactive client 104 may present to a user of the interactive system 100. Fig.16 , based on the interactive system 100 determining that although the two users do not have a two-way relationship, the sender (“David”) is associated with a contact record in the recipient's contact management application (a linked third-party application), the sender (“David”) sends a message to the non-friend user, and the recipient receives the message (as shown in the recipient user interface 1602).
[0146] When the recipient opens a conversation with a non-friend, an add button 606 is presented within the header of the associated user interface, and a description bar 608 is appended to the header, with text in the description bar 608 explaining why the user wants to add the entity as a friend, for example, "Add [last name] so they can see your stories, etc!".
[0147] The add button 606 is user-selectable for the recipient to add the sender as a friend and accordingly initiate the establishment of a friend relationship between the users. Upon receiving a message from a non-friend, the recipient user interface 1602 also displays a set of privacy graphical elements, including explanatory text 1604 along with a hide or block button 1606 and a privacy settings button 1608. The explanatory text 1604 provides the recipient with an explanation of the relationship (or lack of relationship) with the sender and provides a highly visible way for the recipient to easily block the sender (e.g., disabling or hiding any further communication with the recipient).
[0148] In some examples, particular users of the interactive system 100 may interact with each other only if the privacy settings of another non-friend user of the interactive system 100 permit such interactions. For example, in response to the interactive system 100 checking the privacy settings of other users stored within the interactive system 100 and determining that the privacy settings permit electronic interactions with users with whom the user has no relationship as reflected in the relevant relationship data, the particular user may send a message to the other (non-friend) user. If the interactive system 100 detects that the privacy settings permit such interactions (e.g., interactions with “contacts” who are not “friends”), the interactive system 100 may cause an indication to be presented at the other user's device (e.g., in a messaging user interface) that the electronic interaction was initiated by the particular user. For example, such an indication may be as follows: Fig.15 The indication shown, when selected, initiates an interaction, e.g. Fig.16 The message dialogue in the example form is shown in .
[0149] Thus, privacy on the recipient side may be managed by the recipient's privacy settings stored within the interactive system 100. For example, if the recipient selects the privacy settings button 1514 or the privacy settings button 1608, the interactive client 104 presents the contact settings interface 1702, which allows user selection of specific settings (e.g., Fig.17 shown).
[0150] The contact setup interface 1702 includes instruction text 1704 for indicating to the subject user that the contact setup interface 1702 can be used to select a method of directly contacting a user (in Fig.17 In the example, this specifically refers to other user categories of the interactive system 100 for messaging and call interactions).
[0151] The subject user may select a friend option element 1706. If the friend option element 1706 is selected, the interactive system 100 enables the friend option for the subject user to allow friends (users with whom the subject user has a two-way relationship reflected in the relationship data) to directly call the subject user and send messages to the subject user. The subject user may select a contact option element 1708. If the contact option element 1708 is selected, the interactive system 100 enables the contact option to allow non-friends that appear in the user's contact management application (e.g., the contacts application 420) to send messages to the user and call the user. This may be referred to as "contact messaging" or "contact calling" rather than "friend messaging" or "friend calling," respectively.
[0152] The user may select the everyone option element 1710. If the everyone option element 1710 is selected, the interactive system 100 enables the "Everyone can contact me" option for the subject user to allow any registered user of the interactive system 100 to interact directly with the subject user, regardless of their relationship with the user (e.g., even if the other user is not a friend or contact of the subject user). If the "Everyone can contact me" option is selected, the other two options in the contact settings interface 1702 are frozen and cannot be adjusted (because the "Everyone can contact me" option already covers the friends option element 1706 and the contacts option element 1708).
[0153] If the user does not select the contacts option element 1708 or the everyone option element 1710, the interactive system 100 will not allow the subject user to send and receive "non-friend" messages. In some examples, if the subject user interacts with a "non-friend" and then adjusts its privacy settings at a later stage to no longer allow such interactions, the existing conversation associated with the "non-friend" will be automatically removed from the subject user's message feed by the interactive system 100.
[0154] It is understandable that, referring to Fig.17 The privacy setting examples described are only examples, and alternative or additional privacy settings can be applied. For example, the interactive system 100 can automatically apply certain restrictions based on the age of the user. For example, users under the age of 18 can be locked to the friends-only option, which means that the subject user (under the age of 18) can only directly receive messages and calls from other users when the subject user has a two-way relationship with the relevant other users. Even if the contact details of other users are located in the address book of the subject user and matched during the matching operation, this setting can also be applicable. In other words, the subject user can be prevented from selecting options such as contact option element 1708 or each person option element 1710. As mentioned above, the sending user can still send a message to the subject user (under the age of 18), but the interactive system 100 can be configured to, for example, not make the subject user know the message by not surfacing the message in the message feed interface, unless the two users subsequently establish a two-way relationship. In some examples, this function can enhance the privacy of the user profile by not enabling the sending user to infer the sensitive personal information of the (proposed) recipient.
[0155] Within a conversation view such as recipient user interface 1602 , the recipient may select a graphical identification (eg, avatar 1610 ) to activate presentation of a user profile interface of the user associated with avatar 1610 . Fig.18 A user profile interface 1802 is shown according to some examples.
[0156] The user profile interface 1802 displays to the viewing user an avatar or user image 1804 of the viewed user, the viewed user's username 1806, and an add button 606 and a report icon 1204. The add button 606 is displayed based on the lack of a bidirectional relationship between the viewing user and the viewed user. The user profile interface 1802 further presents an association portion 1808 that provides a non-friend indicator in the form of a contact card cell 1810. The contact card cell 1810 indicates to the viewing user that the viewed user is not a friend of the viewing user, but that the viewed user's phone number was found in the viewing user's contact management application, for example, during the matching operation described above (hence the display of the "in my contacts" descriptor).
[0157] The association portion 1808 may essentially provide the viewing user with a reason or explanation as to why the viewing user is able to interact with the viewed user (or vice versa, why the viewed user is able to interact with the viewing user) even though the two users do not have a two-way relationship established within the interaction system 100. In some examples, in response to detecting that the viewing user has deleted the contact details of the viewed user from the contact management application, the interaction system 100 causes the contact card cell 1810 to be automatically deleted from the user profile interface 1802.
[0158] Fig.19 1 is a user interface diagram illustrating a conversation creation interface or new chat interface 1902 according to some examples. The new chat interface 1902 enables an active user to add one or more users of the interactive system 100 to a new chat. The chat may be a private communication between only two users, or may be a group conversation (e.g., if the active user decides to add multiple users to the new chat).
[0159] In the new chat interface 1902, a list of available users is presented for the active user. The list is presented in the example form of a mixed list of contact identifiers, which includes contact identifiers of friends of the active user (there is a two-way relationship) and contact identifiers of users who are not friends of the active user but are associated with the record discovered during the matching operation. As described above, the interactive client 104 can access a set of electronic contact data associated with a third-party application (such as a contact application or other messaging application, such as email or other third-party messaging application), and perform a matching operation between the third-party electronic contact data and registered users of the interactive system 100 to identify entities (such as people) that are both in the third-party application contact list of the active user and are registered users of the interactive system 100. Fig.19 As shown, where such a match is located (eg, by matching an email address or mobile phone number), the identities of the related entities may be displayed in a mixed list.
[0160] The icons of the active user's friends are visually distinguished from the icons of the active user's "non-friends". Fig.19 In the example of FIG. 1902, this distinction is made by including subtext below the name of the relevant "non-friend" user (in the same cell of the new chat interface 1902). For example, the first contact identifier 1904 is a cell that identifies a user ("Samantha") with whom the active user has a two-way relationship; the second contact identifier 1906 is a cell that identifies a user with whom the active user does not have a two-way relationship but for whom a matching record was found in the matching operation. Therefore, the subtext 1908 ("In My Contacts") is included in the cell representing the second contact identifier 1906, but not in the cell representing the first contact identifier 1904.
[0161] This can allow the active user to find someone they have contacted but is not in the interactive system 100 in a third party application (e.g., a contact management application or an email application) and initiate an interaction with them in an intuitive and easy manner, while still providing a visible distinction between that person and the active user's "friends." If the active user does decide to initiate a conversation with, for example, the user identified by the second contact identification 1906 ("Sam"), a dialog similar to Figure 6 The interface shown initiates message sending and receiving.
[0162] In some examples, as part of the conversation creation process facilitated by the new chat interface 1902, the interactive system 100 can prevent active users from adding both "friends" and "non-friends" to the same new chat. In addition, as described above, the new chat interface 1902 can be adjusted or restricted based on user privacy settings, user age, etc. For example, a user who has selected the friend-only contact option may not be presented with any "non-friends" in the new chat interface 1902. Similarly, users under the age of 18 may be presented with only a list of users with whom they have a two-way relationship, thereby automatically preventing the user from adding "non-friends" to the new chat.
[0163] Fig. 20 and Fig.21 2 is a user interface diagram illustrating a message feed interface including friend recommendations according to some examples. As described above, the recommendation engine 236 can generate recommendations for a particular user, and such recommendations can be surfaced in a user interface presented to the particular user, thereby allowing the user to request to establish a relationship with the suggested user in a convenient manner (e.g., without having to perform a search for the suggested user), or simply interact with the suggested user without requesting to establish a relationship.
[0164] In some examples, generating composite electronic contact data as described above (e.g., combined contact data including "friends" and "contacts" of a user) includes: using output from recommendation engine 236 (e.g., generated by output of recommendation engine 236) to determine that electronic contact records associated with the suggested user are to be included in the composite electronic contact data. In this way, a mixed list of contact identifiers can be presented to the active user, the mixed list of contact identifiers including at least one first contact identifier associated with one or more "friends" and at least one second contact identifier associated with one or more other users of the interactive system 100, these other users are not "friends" of the active user, but the interactive system 100 will recommend these users to the active user based on the matching operation.
[0165] Now more specifically turn to Fig. 20 and Fig.21 , both the message feed interface 2002 and the message feed interface 2102 present the first suggested user 2004 and the second suggested user 2006 to the active user. The first suggested user 2004 and the second suggested user 2006 do not have a two-way relationship with the active user within the interactive system 100, but are matched with the active user during the matching operation. Specifically, the interactive system 100 determines using the matching system 234 that each of the first suggested user 2004 and the second suggested user 2006 is associated with a contact in the contact application of the active user. Therefore, the recommendation engine 236 presents the identification of the two suggested users to the active user together with the explanatory text 2008 ("In my contacts" or "Join from contacts") and the recommendation text 2012 ("Say hello!"). In this way, based on the interactive system 100 determining that the recommended user is a contact of the active user in the linked third-party application, the recommended users of the interactive system 100 are presented to the active user to interact with and / or add as friends.
[0166] exist Fig. 20 , a cell including the identification of the first suggested user 2004 and the second suggested user 2006 is presented above the "Quick Add" portion of the messaging interface 2002. The "Quick Add" portion presents a list of other suggested users 2010 generated by the recommendation engine 236, but does not include matching operation results. For example, the other suggested users 2010 may include users who have common friends (common friends) with the active user but are not identified in the active user's contact book application. Fig.21 , a cell including the identification of the first suggested user 2004 and the second suggested user 2006 is presented in the message feed interface 2102 above a group of regular message feed cells, each cell identifying a conversation with a user (or group) within the interactive system 100.
[0167] As described above, while the text 2008 acts as a non-friend indicator, the feed cell corresponding to each suggested user may be further marked or visually distinguished, for example, using an X, which also acts as a non-friend indicator 1104. The presentation of the indicator 1104 is maintained until the interactive system 100 identifies that the related entity has established a two-way relationship with the active user. In addition, the indicator 1104 is user-selectable for the viewing user to hide or block the related entity from further communications. In this case, the active user can click on the indicator 1104 to remove the suggestion from the message feed interface 2002 and / or block / hide any communications from the suggested user.
[0168] The identities of suggested users may be surfaced and / or positioned relative to other contact identities in the user interface (e.g., in a mixed list) based on output received from the recommendation engine 236. For example, the order of suggested users in the message feed may be determined based on the time when each suggestion was generated, and the order may be dynamically updated over time as suggestions change or new suggestions are generated.
[0169] In some examples, "N" "non-friend messaging suggestions" may be presented to a user of the interactive system 100, which are determined by the recommendation engine 236 based on a predefined algorithm. Included below is pseudocode illustrating the processing logic for implementing recommendations of this nature according to some examples. It should be understood that the pseudocode included below includes ordinary / simple language descriptions of certain steps in algorithms, logic, and / or other processes. Although the pseudocode uses structural conventions similar to programming languages, it is intended to be read by humans rather than machines. Therefore, it may omit details that are critical to machine understanding, such as variable declarations and specific language codes.
[0170] Example generation logic for users (pseudocode):
[0171] [start]
[0172] Input:FindFriendsRegSortedSuggestions:OrderedList
[0173] output:NonFriendMessagingResult:OrderedList
[0174] params:PositiveNoiseRate; NegativeNoiseRate; PositiveNoiseCap; NegativeNoiseCap; SuggestionCap
[0175] init:SuggestListAfterNoise / / Skip through rate limiting and privacy filtering steps
[0176] setting bidirectionalList,inMyContactsOnlyList=splitByInMyContacts(findFriendsRegSortedSuggestions)
[0177] var NonFriendMessagingResult <suggestion>
[0178] foreach sug in inMyContactsOnlyList:
[0179] if(randomByWeek <PositiveNoiseRate):
[0180] NonFriendMessagingResult.add(sug)
[0181] foreach sug in bidirectionalList:
[0182] if(randomByWeek>=NegativeNoise):
[0183] NonFriendMessagingResult.add(sug)
[0184] sort(NonFriendMessagingResult)
[0185] result=NonFriendMessagingResult.sublist(0,SuggestionCap)
[0186] [Finish]
[0187] According to some examples, the above process splits the input "findFriendsRegSortedSuggestions" into two lists: "bidirectionalList" and "inMyContactsOnlyList" using a function named "splitByInMyContacts". The process loops through each suggestion in "inMyContactsOnlyList" and adds it to the "NonFriendMessagingResult" list with a probability determined by "PositiveNoiseRate". The process also loops through each suggestion in "bidirectionalList" and adds it to the "NonFriendMessagingResult" list with a probability determined by "NegativeNoiseRate". The process includes sorting the "NonFriendMessagingResult" list and returning the final result based on "SuggestionCap".
[0188] Fig. 22 2 is a user interface diagram illustrating a sender user interface 2202 according to some examples. The sender user interface 2202 may be responsive to an active user selection. Fig.21 , and is presented to the active user with the identification of the first suggested user 2004 shown in , so that the active user can initiate a "non-friend message".
[0189] Sender user interface 2202 includes a graphical identifier (e.g., avatar 2206) that can be selected to activate presentation of a user profile interface of the user associated with avatar 2206. Add button 606 is presented within the header of the associated user interface, and description bar 608 is attached to the header with text explaining why the user should add the friend, e.g., "Add this friend to view their stories, call them, and more!"
[0190] The add button 606 is user-selectable for the active user to add the suggested user as a friend and accordingly establish a friend relationship (or initiate a friend request) between the users. The sender user interface 2202 also displays a set of privacy graphical elements, including explanatory text 1604 along with a hide or block button 1606 and an OK button 2204. The explanatory text 1604 provides an explanation of the user relationship to the active user and provides a highly visible way for the active user to easily block (e.g., prohibit receiving any communications or hide further communications) the suggested user. User selection of the OK button 2204 can cause the privacy graphical element to disappear from the sender user interface 2202.
[0191] Data communication architecture
[0192] Fig.23 is a schematic diagram illustrating the structure of a message 2300 according to some examples, the message 2300 being generated by an interactive client 104 for transmission to another interactive client 104 via an interactive server 118. The content of a particular message 2300 is used to populate a message table 302 stored in a database 120 accessible by an interactive server 118. Similarly, the content of the message 2300 is stored in memory as "in-transit" or "in-flight" data of a user system 102 or an interactive server 118. The message 2300 is shown to include the following example components:
[0193] Message ID 2302: a unique ID that identifies the message 2300 .
[0194] Message text payload 2304 : Text to be generated by the user via the user interface of the user system 102 and included in the message 2300 .
[0195] Message image payload 2308: Image data captured by the camera component of the user system 102 or retrieved from the memory component of the user system 102 and included in the message 2300. The image data for the message 2300 sent or received may be stored in the image table 2320.
[0196] Message video payload 2312: Video data captured by the camera component or retrieved from the memory component of the user system 102 and included in the message 2300. The video data for the message 2300 sent or received may be stored in the video table 2306.
[0197] Message audio payload 2314 : Audio data captured by a microphone or retrieved from a memory component of the user system 102 and included in the message 2300 .
[0198] Message enhancement data 2318: Enhancement data (e.g., filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 2308, message video payload 2312, or message audio payload 2314 of the message 2300. The enhancement data for a sent or received message 2300 may be stored in an enhancement table 2316.
[0199] · Message duration parameter 2322: A parameter value indicating the amount of time in seconds that the content of the message (e.g., message image payload 2308, message video payload 2312, message audio payload 2314) is to be presented to the user via the interactive client 104 or made accessible to the user.
[0200] Message geolocation parameters 2328: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 2328 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 2308 or a specific video in a message video payload 2312).
[0201] Message story identification 2330: An identification value that identifies one or more content collections (e.g., "story" identified in collection table 2324) associated with a particular content item in message image payload 2308 of message 2300. For example, identification values may be used to associate multiple images within message image payload 2308 with multiple content collections, respectively.
[0202] Message tags 2332: Each message 2300 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 2308 depicts an animal (e.g., a lion), a tag value may be included within the message tags 2332 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.
[0203] Message sender identification 2334: Indicates the identification of the user of the user system 102 on which the message 2300 was generated and from which the message 2300 was sent (eg, a messaging system identification, an email address, or a device identification).
[0204] Message recipient identification 2326: Indicates the identification of the user of the user system 102 to which the message 2300 is addressed (eg, a messaging system identification, an email address, or a device identification).
[0205] The content (e.g., value) of each component of message 2300 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 2308 may be a pointer (or address) to a location within image table 2320. Similarly, the value within message video payload 2312 may point to data stored within video table 2306, the value stored within message enhancement 2318 may point to data stored within enhancement table 2316, the value stored within message story identifier 2330 may point to data stored within story table 2324, and the values stored within message sender identifier 2334 and message recipient identifier 2326 may point to user records stored within entity table 2310.
[0206] Time-based access restriction architecture
[0207] Fig.24 is a schematic diagram illustrating access restriction processing 2400, according to which access to content (e.g., a multimedia payload of ephemeral message 2402 and associated data) or a collection of content (e.g., ephemeral message group 2406) can be time-restricted (e.g., ephemeral).
[0208] The ephemeral message 2402 is shown to be associated with a message duration parameter 2408, the value of which determines the amount of time that the ephemeral message 2402 will be displayed by the interactive client 104 to the receiving user of the ephemeral message 2402. In some examples, the receiving user may view the ephemeral message 2402 for up to 10 seconds, depending on the amount of time specified by the sending user using the message duration parameter 2408.
[0209] The message duration parameter 2408 and the message recipient identification 2418 are shown as inputs to a message timer 2412, which is responsible for determining the amount of time that the ephemeral message 2402 is shown to the particular receiving user identified by the message recipient identification 2418. In particular, the ephemeral message 2402 is shown to the associated receiving user for a period of time determined by the value of the message duration parameter 2408. The message timer 2412 is shown as providing an output to a more generalized messaging system 2404, which is responsible for the overall timing of displaying content (e.g., the ephemeral message 2402) to the receiving user.
[0210] exist Fig.24 2402 is shown as being included within an ephemeral message group 2406 (e.g., a collection of messages in a personal story or event story). The ephemeral message group 2406 has an associated group duration parameter 2410, the value of which determines the duration for which the ephemeral message group 2406 is presented and accessible by users of the interactive system 100. For example, the group duration parameter 2410 may be the duration of a concert, wherein the ephemeral message group 2406 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 2410 when performing setup and creation of the ephemeral message group 2406.
[0211] In addition, each ephemeral message 2402 within an ephemeral message group 2406 has an associated group participation parameter 2414, the value of which determines the duration for which the ephemeral message 2402 will be accessible within the context of the ephemeral message group 2406. Thus, a particular ephemeral message group 2406 may "expire" and become inaccessible within the context of the ephemeral message group 2406 before the ephemeral message group 2406 itself expires according to the group duration parameter 2410. The group duration parameter 2410, the group participation parameter 2414, and the message recipient identification 2418 each provide inputs to a group timer 2416, which first operatively determines whether a particular ephemeral message 2402 of the ephemeral message group 2406 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 2406 due to the message recipient identification 2418.
[0212] Thus, the group timer 2416 operatively controls the total lifespan of the associated ephemeral message group 2406 and the individual ephemeral messages 2402 included in the ephemeral message group 2406. In some examples, each ephemeral message 2402 within the ephemeral message group 2406 remains viewable and accessible for a period of time specified by the group duration parameter 2410. In another example, within the context of the ephemeral message group 2406, a particular ephemeral message 2402 may expire based on the group participation parameter 2414. Note that even within the context of the ephemeral message group 2406, the message duration parameter 2408 may still determine the duration for which a particular ephemeral message 2402 is displayed to a receiving user. Thus, the message duration parameter 2408 determines the duration for which a particular ephemeral message 2402 is displayed to a receiving user, regardless of whether the receiving user views the ephemeral message 2402 within or outside the context of the ephemeral message group 2406.
[0213] In addition, the messaging system 2404 may be operative to remove a particular ephemeral message 2402 from the ephemeral message group 2406 based on a determination that the particular ephemeral message 2402 has exceeded the associated group participation parameter 2414. For example, when the sending user has established a group participation parameter 2414 of 24 hours from posting, the messaging system 2404 will remove the associated ephemeral message 2402 from the ephemeral message group 2406 after the specified 24 hours. The messaging system 2404 is also operative to remove an ephemeral message group 2406 when the group participation parameter 2414 for each ephemeral message 2402 within the ephemeral message group 2406 has expired, or when the ephemeral message group 2406 itself has expired according to the group duration parameter 2410.
[0214] In some use cases, the creator of a particular ephemeral message group 2406 may specify an indefinite group duration parameter 2410. In this case, the expiration of the group participation parameter 2414 of the last remaining ephemeral message 2402 within the ephemeral message group 2406 will determine when the ephemeral message group 2406 itself expires. In this case, a new ephemeral message 2402 with a new group participation parameter 2414 added to the ephemeral message group 2406 effectively extends the life of the ephemeral message group 2406 to a value equal to the group participation parameter 2414.
[0215] In response to the messaging system 2404 determining that the ephemeral message group 2406 has expired (e.g., is no longer accessible), the messaging system 2404 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 2406 to no longer be displayed within the user interface of the interactive client 104. Similarly, when the messaging system 2404 determines that the message duration parameter 2408 of a particular ephemeral message 2402 has expired, the messaging system 2404 causes the interactive client 104 to no longer display the indicia (e.g., icon or text identification) associated with the ephemeral message 2402.
[0216] System with head wearable device
[0217] Fig.25 System 2500 is shown, which includes a head wearable device 2502 with a selector input device according to some examples. Fig.25 is a high-level functional block diagram of an exemplary head wearable device 2502 communicatively coupled to a mobile client device 2506 and a server system 2534 via various networks 2540.
[0218] The head wearable device 2502 includes a camera device, such as at least one of a visible light camera 2514, an infrared transmitter 2516, and an infrared camera 2518.
[0219] The client device 2506 can connect to the head wearable device 2502 using a low power wireless connection 2536 and a high speed wireless connection 2538. The client device 2506 connects to the server system 2534 and the network 2540. The network 2540 can include any combination of wired and wireless connections.
[0220] The head wearable device 2502 also includes two image displays of the optical assembly's image displays 2504. The two optical assembly's image displays 2504 include an image display associated with a left lateral side of the head wearable device 2502 and an image display associated with a right lateral side of the head wearable device 2502. The head wearable device 2502 also includes an image display driver 2510, an image processor 2512, low power circuits 2528 for low power consumption, and high speed circuits 2520. The optical assembly's image displays 2504 are used to present images and videos to a user of the head wearable device 2502, including images that may include a graphical user interface.
[0221] The image display driver 2510 commands and controls the image display 2504 of the optical assembly. The image display driver 2510 can deliver the image data directly to the image display 2504 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.
[0222] The head wearable device 2502 includes a frame and stems (or temples) extending from lateral sides of the frame. The head wearable device 2502 also includes a user input device 2508 (e.g., a touch sensor or a push button), including an input surface on the head wearable device 2502. The user input device 2508 (e.g., a touch sensor or a push button) is used to receive input selections from a user for manipulating a graphical user interface of a presented image.
[0223] Fig.25 The components of the head wearable device 2502 shown in 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 nose bridges of the head wearable device 2502. The left visible light camera and the right visible light camera 2514 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).
[0224] The head wearable device 2502 includes a memory 2524 that stores instructions for performing a subset or all of the functions described herein. The memory 2524 may also include a storage device. Fig.25 As shown, the high-speed circuit 2520 includes a high-speed processor 2522, a memory 2524, and a high-speed wireless circuit 2526. In this example, the image display driver 2510 is coupled to the high-speed circuit 2520 and is operated by the high-speed processor 2522 to drive the left image display and the right image display in the image display 2504 of the optical assembly. The high-speed processor 2522 can be any processor capable of managing high-speed communications and operations of any general computing system required by the head wearable device 2502. The high-speed processor 2522 includes the processing resources required to manage high-speed data transmission to a wireless local area network (WLAN) on the high-speed wireless connection 2538 using the high-speed wireless circuit 2526. In some examples, the high-speed processor 2522 executes an operating system (e.g., a LINUX operating system) or other such operating system of the head wearable device 2502, and the operating system is stored in the memory 2524 for execution. In addition to any other duties, the high-speed processor 2522 that executes the software architecture of the head wearable device 2502 is used to manage data transmission with the high-speed wireless circuit 2526. In some examples, high-speed wireless circuit 2526 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 2526 can implement other high-speed communication standards.
[0225] The low power wireless circuitry 2532 and high speed wireless circuitry 2526 of the head wearable device 2502 may include a short range transceiver (Bluetooth) and a wireless wide area network transceiver, a wireless local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). The client device 2506, including a transceiver that communicates via the low power wireless connection 2536 and the high speed wireless connection 2538, may be implemented using details of the architecture of the head wearable device 2502, as may other elements of the network 2540.
[0226] The memory 2524 includes any storage device capable of storing various data and applications, including camera data generated by the left and right visible light cameras 2514, the infrared camera 2518, and the image processor 2512, and the image generated to be displayed on the image display in the image display 2504 of the optical assembly through the image display driver 2510. Although the memory 2524 is shown as being integrated with the high-speed circuit 2520, in some examples, the memory 2524 can be a separate independent element of the head wearable device 2502. In some such examples, electrical wiring can provide a connection from the image processor 2512 or the low-power processor 2530 to the memory 2524 through a chip including the high-speed processor 2522. In some examples, the high-speed processor 2522 can manage the addressing of the memory 2524 so that the low-power processor 2530 will start the high-speed processor 2522 at any time when a read or write operation involving the memory 2524 is required.
[0227] like Fig.25 As shown, the low-power processor 2530 or the high-speed processor 2522 of the head wearable device 2502 can be coupled to a camera device (a visible light camera device 2514, an infrared emitter 2516 or an infrared camera device 2518), an image display driver 2510, a user input device 2508 (for example, a touch sensor or a push button), and a memory 2524.
[0228] The head wearable device 2502 is connected to a host computer. For example, the head wearable device 2502 is paired with a client device 2506 via a high-speed wireless connection 2538 or connected to a server system 2534 via a network 2540. The server system 2534 can be one or more computing devices as part of a service or network computing system, for example, including a processor, a memory, and a network communication interface to communicate with the client device 2506 and the head wearable device 2502 through the network 2540.
[0229] The client device 2506 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication via a network 2540, a low-power wireless connection 2536, or a high-speed wireless connection 2538. The client device 2506 may further store at least a portion of the instructions for generating binaural audio content in a memory of the client device 2506 to implement the functions described herein.
[0230] The output components of the head wearable device 2502 include visual components, such as a display (e.g., a liquid crystal display (LCD), a plasma display panel (PDP), a light emitting diode (LED) display, a projector, or a waveguide). The image display of the optical assembly is driven by the image display driver 2510. The output components of the head wearable device 2502 also include acoustic components (e.g., speakers), tactile components (e.g., vibration motors), other signal generators, etc. The input components (e.g., user input devices 2508) of the head wearable device 2502, the client device 2506, and the server system 2534 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.
[0231] The head wearable device 2502 may optionally include additional peripheral elements. Such peripheral elements may include biometric sensors, additional sensors, or display elements integrated with the head wearable device 2502. 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.
[0232] For example, the biometric component includes a component for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, 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 obtained), orientation sensor component (e.g., a magnetometer), etc. Such positioning system coordinates can also be received from the client device 2506 via the low power wireless connection 2532 and the high speed wireless connection 2526 via the low power wireless circuit 2536 or the high speed wireless circuit 2538.
[0233] When phrases similar to "at least one of A, B, or C," "at least one of A, B, and C," "one or more A, B, or C," or "one or more of A, B, and C" are used, it is intended that the phrase be interpreted to mean that A can exist alone in an example, B can exist alone in an example, C can exist alone in an example, or any combination of elements A, B, and C can exist in a single example; for example, A and B, A and C, B and C, or A and B and C.
[0234] 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.
[0235] Software Architecture
[0236] Fig.26 2600 is a block diagram illustrating a software architecture 2604 that can be installed on any one or more of the devices described herein. The software architecture 2604 is supported by hardware, such as a machine 2602 including a processor 2620, a memory 2626, and an I / O component 2636. In this example, the software architecture 2604 can be conceptualized as a stack of layers, each of which provides specific functionality. The software architecture 2604 includes layers such as an operating system 2612, a library 2610, a framework 2608, and an application 2606. In operation, the application 2606 calls an API call 2648 through the software stack and receives a message 2650 in response to the API call 2648.
[0237] The operating system 2612 manages hardware resources and provides public services. The operating system 2612 includes, for example, a kernel 2614, a service 2616, and a driver 2622. The kernel 2614 acts as an abstraction layer between the hardware and other software layers. For example, the kernel 2614 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. The service 2616 can provide other public services to other software layers. The driver 2622 is responsible for controlling or interfacing with the underlying hardware. For example, the driver 2622 may include a display driver, a camera driver, a Bluetooth or Bluetooth low energy driver, a flash driver, a serial communication driver (e.g., a USB driver), Drivers, audio drivers, power management drivers, etc.
[0238] The library 2610 provides a common low-level infrastructure used by the application 2606. The library 2610 may include a system library 2618 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 2610 may include an API library 2624, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for rendering 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 2610 may also include various other libraries 2628 to provide many other APIs to the application 2606 .
[0239] The framework 2608 provides a common high-level infrastructure used by the applications 2606. For example, the framework 2608 provides various graphical user interface (GUI) functions, advanced resource management, and advanced positioning services. The framework 2608 can provide a wide range of other APIs that can be used by the applications 2606, some of which can be specific to a particular operating system or platform.
[0240] In the example, the application 2606 may include a home application 2636, a contact application 420, a browser application 2630, a book reader application 2632, a positioning application 2640, a media application 2642, a messaging application 2644, a game application 2646, and a variety of other applications such as third-party applications 2638. Application 2606 is a program that executes the functions defined in the program. Various programming languages can be used to create one or more of the applications 2606 constructed in various ways, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C language or assembly language). In a specific example, a third-party application 2636 (e.g., an application developed by an entity other than a supplier of a specific platform using an ANDROID or IOS software development kit (SDK)) can be a mobile software running on a mobile operating system such as IOS, ANDROID, WINDOWS phone, or another mobile operating system. In this example, third party application 2638 can activate API calls 2648 provided by operating system 2612 to facilitate the functionality described herein.
[0241] Machine Architecture
[0242] Fig. 27 2700 within which instructions 2710 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 2700 to perform any one or more of the methods discussed herein. For example, the instructions 2710 may cause the machine 2700 to perform any one or more of the methods described herein. The instructions 2710 convert a general purpose, unprogrammed machine 2700 into a specific machine 2700 that is programmed to perform the functions described and illustrated in the manner described. The machine 2700 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 2700 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 2700 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 2710 specifying actions to be taken by the machine 2700. In addition, although only a single machine 2700 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 2710 to perform any one or more of the methods discussed herein. For example, the machine 2700 may include any of the plurality of server devices that form part of the interactive server system 108 or the user system 102. In some examples, the machine 2700 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.
[0243] The machine 2700 may include a processor 2704, a memory 2706, and an input / output (I / O) component 2702 that may be configured to communicate with each other via a bus 2740. In an example, the processor 2704 (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 2708 that executes instructions 2710 and a processor 2712. 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. 27 Multiple processors 2704 are shown, but the machine 2700 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.
[0244] The memory 2706 includes a main memory 2714, a static memory 2716, and a storage unit 2718, which can be accessed by the processor 2704 via the bus 2740. The main memory 2706, the static memory 2716, and the storage unit 2718 store instructions 2710 that implement any one or more of the methods or functions described herein. The instructions 2710 may also reside, completely or partially, within the main memory 2714, within the static memory 2716, within the machine-readable medium 2720 within the storage unit 2718, within at least one of the processors 2704 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 2700.
[0245] I / O components 2702 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 2702 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 2702 may include Fig. 27 2702. In various examples, the I / O components 2702 may include a user output component 2726 and a user input component 2728. The user output component 2726 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 2728 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.
[0246] In other examples, the I / O component 2702 may include a biometric component 2730, a motion component 2732, an environmental component 2734, or a position component 2736, as well as a wide range of other components. For example, the biometric component 2730 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 2732 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope). Any biometric data collected by the biometric component is captured and stored only with the user's consent and deleted when the user requests it. In addition, such biometric data can be used for very limited purposes, such as identity verification. To ensure limited and authorized use of biometric information and other personally identifiable information (PII), access to this data is limited to authorized personnel. Any use of biometric data may be strictly limited to identity verification purposes and may not be shared with any third party or sold without the user's explicit consent. In addition, appropriate technical and organizational measures are implemented to ensure the security and confidentiality of this sensitive information.
[0247] Environmental components 2734 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor for detecting concentrations of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.
[0248] With respect to cameras, user system 102 may have a camera system including, for example, a front-facing camera on a front surface of user system 102 and a rear-facing camera on a rear surface of user system 102. The front-facing camera may, for example, be used to capture still images and videos of a user of user system 102 (e.g., "selfies"), which may then be enhanced with the enhancement data (e.g., filters) described above. For example, the rear-facing camera may be used to capture still images and videos in a more conventional camera mode, which images are similarly enhanced with the enhancement data. In addition to the front-facing camera and the rear-facing camera, user system 102 may also include a 360° camera for capturing 360° photos and videos.
[0249] Additionally, the camera system of the user system 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the user system 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.
[0250] The location component 2736 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.
[0251] Various technologies can be used to achieve communication. The I / O component 2702 also includes a communication component 2738, which is operable to couple the machine 2700 to the network 2722 or the device 2724 via a corresponding coupling or connection. For example, the communication component 2738 may include a network interface component or another suitable device that interfaces with the network 2722. In other examples, the communication component 2738 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, a Bluetooth component (e.g., Bluetooth low energy), a Wi-Fi component, and other communication components for providing communication via other forms. The device 2724 can be any peripheral device of another machine or a variety of peripheral devices (e.g., a peripheral device coupled via USB).
[0252] In addition, the communication component 2738 can detect the identification, or include a component that can be operated to detect the identification. For example, the communication component 2738 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting a one-dimensional barcode such as a universal product code (UPC) barcode, a multi-dimensional barcode such as a quick response (QR) code, an Aztec code, a data matrix, a data symbol (Dataglyph), a maximum code (MaxiCode), PDF417, UltraCode, UCC RSS-2D barcode, 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 2738, such as obtaining a location via Internet Protocol (IP) geolocation, obtaining a location via Wi-Fi signal triangulation, obtaining a location via detecting an NFC beacon signal that can indicate a specific location, etc.
[0253] Various memories (e.g., main memory 2714, static memory 2716, and memory of processor 2704) and storage unit 2718 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 2710) when executed by processor 2704 cause various operations to implement the disclosed examples.
[0254] The instructions 2710 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 2738) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 2722. Similarly, the instructions 2710 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with the device 2724 using a transmission medium.
[0255] Example
[0256] In view of the implementation of the above-mentioned subject matter, the present application discloses the following list of examples, in which one feature of a separate example or more than one feature of an example is combined together, and optionally, combined with one or more features of one or more additional examples, is an additional example that also falls within the disclosure of the present application.
[0257] Example 1 is a method, comprising: maintaining for an interactive system: first electronic contact data of multiple users of the interactive system, and relationship data related to the relationships between the multiple users of the interactive system; using the first electronic contact data and the relationship data, automatically generating composite electronic contact data, the composite electronic contact data comprising: a first electronic contact record of a first user of the interactive system, as reflected in the relationship data, a specific user of the interactive system has a relationship with the first user, and a second electronic contact record of a second user of the interactive system, as reflected in the relationship data, the specific user has no relationship with the second user; causing the composite electronic contact data to be presented within the interactive system, wherein presenting the composite electronic contact data comprises: visually distinguishing the presentation of the first electronic contact record from the presentation of the second electronic contact record; and enabling the specific user of the interactive system to use the second electronic contact record to initiate an electronic interaction with the second user.
[0258] In Example 2, the subject matter of Example 1 includes, wherein generating the composite electronic contact data includes: accessing second electronic contact data, the second electronic contact data being associated with a third-party application; performing a matching operation between the first electronic contact data and the second electronic contact data; and including the second electronic contact data in the composite electronic contact data based on determining a match between an electronic data record in the second electronic contact data and the second electronic contact record.
[0259] In Example 3, the subject matter of Examples 1-2 includes, wherein causing the composite electronic contact data to be presented within the interactive system includes causing a mixed list of contact identifiers to be presented in a user interface, the contact identifiers including a first contact identifier of the first user and a second contact identifier of the second user.
[0260] In Example 4, the subject matter of Example 3 includes, wherein presenting the mixed list includes: visually distinguishing the first contact identifier from the second contact identifier within the mixed list.
[0261] In Example 5, the subject matter of Example 4 includes, wherein the second contact identification includes a not-friend indicator and the first contact identification does not include the not-friend indicator.
[0262] In Example 6, the subject matter of Examples 1-5 includes, wherein the relationship data records a bidirectional relationship between the specific user and the first user within the interactive system.
[0263] In Example 7, the subject matter of Examples 1-6 includes, wherein enabling the particular user to initiate an electronic interaction with the second user comprises enabling the particular user to send an electronic message to a second user of the interaction system associated with the second electronic contact record.
[0264] In Example 8, the subject matter of Example 7 includes, wherein the electronic message is an electronic message presented to the second user in a messaging user interface, the messaging user interface including a set of privacy control graphical elements, one or more of the privacy control graphical elements being user selectable to allow or prohibit communication with the particular user.
[0265] In Example 9, the subject matter of Examples 7-8 includes, wherein enabling the particular user to send the electronic message to the second user includes: causing a messaging user interface to be presented that includes a relationship establishment graphical element, wherein the relationship establishment graphical element is user-selectable to invite the second user to establish a two-way relationship with the particular user in the context of the interactive system.
[0266] In Example 10, the subject matter of Example 9 includes, wherein establishing the bidirectional relationship includes enabling automatic sharing of predetermined data between the specific user and the second user within the interactive system.
[0267] In Example 11, the subject matter of Examples 9-10 includes, wherein inviting the second user to establish a two-way relationship with the specific user in the context of the interactive system includes: inviting the second user to establish a two-way relationship, and the interactive system automatically shares user-generated content between the specific user and the second user based on the two-way relationship.
[0268] In Example 12, the subject matter of Examples 2-11 includes: accessing third electronic contact data, the third electronic contact data being associated with the third-party application, and the third electronic contact data including a third electronic contact record of a non-user of the interactive system; causing the third electronic contact record to be presented within the interactive system together with the composite electronic contact data, wherein presenting the third electronic contact record includes: visually distinguishing the presentation of the third electronic contact record from both the first electronic contact record and the second electronic contact record; and enabling a specific user of the interactive system to invite the non-user to register with the interactive system using the third electronic contact record.
[0269] In Example 13, the subject matter of Example 12 includes, wherein enabling a particular user of the interactive system to invite the non-user to register with the interactive system includes: causing a user-selectable invitation graphical element to be presented in a user interface in association with the third electronic contact record, user selection of the invitation graphical element causing a registration invitation to be sent to a device of the non-user.
[0270] In Example 14, the subject matter of Examples 2-13 includes, wherein the third party application is a contact management application.
[0271] In Example 15, the subject matter of Examples 2-14 includes, wherein the third party application is a third party communication application.
[0272] In Example 16, the subject matter of Examples 2-15 includes, wherein the third-party application is an application hosted on a device of at least one of the particular user, the first user, or the second user.
[0273] In Example 17, the subject matter of Examples 1-16 includes, wherein enabling a particular user of the interactive system to initiate an electronic interaction with the second user includes: checking the privacy settings of the second user stored within the interactive system; and in response to determining that the privacy settings of the second user allow electronic interaction with a user who has no relationship with the second user reflected in the relationship data, automatically causing an indication of the electronic interaction initiated by the particular user to be presented at the second user's device and within a messaging user interface.
[0274] In Example 18, the subject matter of Examples 1-17 includes, wherein generating the composite electronic contact data includes: using output generated by a recommendation engine of the interactive system to determine that the second electronic contact record is to be included in the composite electronic contact data, and wherein causing presentation of the composite electronic contact data within the interactive system includes: automatically causing presentation in a user interface of a blended list of contact identifiers including a first contact identifier of the first user and a second contact identifier of the second user, the second contact identifier being positioned relative to other contact identifiers in the blended list based on the output generated by the recommendation engine.
[0275] Example 19 is a computing device comprising at least one processor and a memory storing instructions, wherein the instructions are configured such that when executed in cooperation with controlling the at least one processor, the instructions operate the device to perform operations, the operations comprising: maintaining for an interactive system: first electronic contact data of multiple users of the interactive system, and relationship data related to the relationships between the multiple users of the interactive system; using the first electronic contact data and the relationship data, automatically generating composite electronic contact data, the composite electronic contact data comprising: a first electronic contact record of a first user of the interactive system, as reflected in the relationship data, a specific user of the interactive system has a relationship with the first user, and a second electronic contact record of a second user of the interactive system, as reflected in the relationship data, the specific user does not have a relationship with the second user; causing the composite electronic contact data to be presented within the interactive system, wherein presenting the composite electronic contact data comprises: visually distinguishing the presentation of the first electronic contact record from the presentation of the second electronic contact record; and enabling the specific user of the interactive system to use the second electronic contact record to initiate an electronic interaction with the second user.
[0276] Example 20 is a non-transitory computer-readable storage medium, which includes instructions that, when executed by at least one computer, cause the at least one computer to perform operations, the operations including: maintaining for an interactive system: first electronic contact data of multiple users of the interactive system, and relationship data related to the relationships between the multiple users of the interactive system; using the first electronic contact data and the relationship data, automatically generating composite electronic contact data, the composite electronic contact data including: a first electronic contact record of a first user of the interactive system, as reflected in the relationship data, a specific user of the interactive system has a relationship with the first user, and a second electronic contact record of a second user of the interactive system, as reflected in the relationship data, the specific user does not have a relationship with the second user; causing the composite electronic contact data to be presented within the interactive system, wherein presenting the composite electronic contact data includes: visually distinguishing the presentation of the first electronic contact record from the presentation of the second electronic contact record; and enabling the specific user of the interactive system to use the second electronic contact record to initiate an electronic interaction with the second user.
[0277] Example 21 is at least one machine-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any of Examples 1-20. Example 22 is an apparatus comprising an apparatus that implements any of Examples 1-20. Example 23 is a system that implements any of Examples 1-20. Example 24 is a method that implements any of Examples 1-20.
[0278] in conclusion
[0279] In some examples, first electronic contact data for a plurality of users of the interactive system and relationship data relating to relationships between the plurality of users of the interactive system are maintained within or by the interactive system. Composite electronic contact data may be automatically generated using the first electronic contact data and the relationship data. The composite electronic contact data may include a first electronic contact record for a first user of the interactive system, with the particular user having a relationship with the first user as reflected in the relationship data, and a second electronic contact record for a second user of the interactive system, with the particular user not having a relationship with the second user as reflected in the relationship data. The composite electronic contact data is caused to be presented within the interactive system. The composite electronic contact data may be presented in a manner that visually distinguishes the presentation of the first electronic contact record from the presentation of the second electronic contact record. The particular user of the interactive system is enabled to use the second electronic contact record to initiate an electronic interaction with the second user.
[0280] The interactive system can access second electronic contact data associated with the third-party application and perform a matching operation between the first electronic contact data and the second electronic contact data. Based on determining a match between an electronic data record in the second electronic contact data and the second electronic contact record, the interactive system can automatically include the second electronic contact data in the composite electronic contact data.
[0281] The interactive system may access third electronic contact data that is associated with a third-party application and includes a third electronic contact record of a non-user of the interactive system. The third electronic contact record may be caused to be presented within the interactive system along with the composite electronic contact data. The process may include visually distinguishing the presentation of the third electronic contact record from both the first electronic contact record and the second electronic contact record. For example, by presenting a user-selectable invitation graphical element in association with the third electronic contact record, providing a mechanism for sending a registration invitation to a device of the non-user, a particular user of the interactive system may be enabled to invite the non-user to register with the interactive system (in other words, a user selection of the invitation graphical element may cause a registration invitation to be sent to a device of the non-user).
[0282] Thus, the examples described herein may solve or mitigate example technical problems where users are unable to interact or are limited in their interaction due to a lack of an existing (direct) relationship within an interactive system. Example technical problems of improving the efficiency or intuitiveness of an interactive system may also be solved or mitigated. The example methods and systems described herein provide various technical features and safeguards that may enhance user protection and privacy.
[0283] As used in this disclosure, phrases of the form "at least one of one A, one B, or one C", "at least one of A, B, or C", "at least one of A, B, and C", etc. should be interpreted as selecting at least one from the group including "A, B, and C". In this disclosure, unless otherwise explicitly stated in conjunction with a specific example, this wording does not mean "at least one of A, at least one of B, and at least one of C". As used in this disclosure, the example "at least one of one A, one B, or one C" will cover any of the following selections: {A}, {B}, {C}, {A, B}, {A, C}, {B, C}, and {A, B, C}.
[0284] Unless the context clearly requires otherwise, throughout the specification and claims, the words "include", "comprises", etc. should be interpreted as inclusive rather than exclusive or exhaustive; that is, "including but not limited to". As used herein, the term "connect", "couple", or any variation thereof means any direct or indirect connection or connection between two or more elements; the connection or connection between elements can be physical, logical, or a combination thereof. In addition, when used in this application, the words "herein", "above", "below" and words of similar meaning refer to this application as a whole, rather than to any particular part of this application. Where the context permits, words used in the singular or plural may also include the plural or singular, respectively. When referencing a list of two or more items, the word "or" covers all interpretations of the word as follows: any item in the list, all items in the list, and any combination of items in the list. Similarly, when referencing a list of two or more items, the term "and / or" covers all interpretations of the word as follows: any item in the list, all items in the list, and any combination of items in the list.
[0285] Although some examples (such as the examples depicted in the accompanying drawings) include a specific order of operations, the order may be changed without departing from the scope of the present disclosure. For example, some of the operations depicted may be performed in parallel or in a different order that does not substantially affect the functions described in the examples. In other examples, different components of the example devices or systems that implement the example methods may perform functions substantially simultaneously or in a specific order.
[0286] Glossary
[0287] "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.
[0288] A "client device" or "user device" refers to a machine that interfaces with a 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 product, a game console, a set-top box, or any other communication device that a user may use to access a network.
[0289] "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 portion of the Internet, a portion 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.
[0290] "Component" refers to a logic or device, a physical entity with the following boundaries, which is defined by function or subroutine calls, branch points, APIs, or other technical definitions that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be encapsulated functional hardware units designed for use with other components, and part of a program that generally performs specific functions of related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units 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., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) 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 for cost and time considerations 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 to implement the hardware component. 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 herein 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 group). In other examples, a processor or a part implemented by a processor can be distributed across multiple geographic locations.
[0291] "Computer-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 "machine-readable medium", "computer-readable medium" and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.
[0292] "Ephemeral messages" are messages that are accessible for a time-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.
[0293] "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" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term "signal media".
[0294] “Non-transitory computer-readable storage medium” refers to a tangible medium capable of storing, encoding or carrying instructions for execution by a machine.
[0295] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions to be executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.< / suggestion>
Claims
1. A method comprising: For interactive system maintenance: first electronic contact data of a plurality of users of the interactive system, and relationship data relating to relationships between the plurality of users of the interactive system; Using the first electronic contact data and the relationship data, composite electronic contact data is automatically generated, the composite electronic contact data comprising: a first electronic contact record of a first user of the interactive system, the particular user of the interactive system having a relationship with the first user as reflected in the relationship data, and a second electronic contact record of a second user of the interactive system, the particular user having no relationship with the second user as reflected in the relationship data; causing presentation of the composite electronic contact data within the interactive system, wherein presenting the composite electronic contact data comprises: visually distinguishing presentation of the first electronic contact record from presentation of the second electronic contact record; and The particular user of the interactive system is enabled to use the second electronic contact record to initiate an electronic interaction with the second user.
2. The method according to claim 1, wherein: Generating the composite electronic contact data includes: accessing second electronic contact data, the second electronic contact data being associated with a third-party application; performing a matching operation between the first electronic contact data and the second electronic contact data; and Based on determining a match between an electronic data record in the second electronic contact data and the second electronic contact record, the second electronic contact data is included in the composite electronic contact data.
3. The method according to claim 1, wherein: Causing presentation of the composite electronic contact data within the interactive system includes causing presentation of a mixed list of contact identifiers in a user interface, the contact identifiers including a first contact identifier for the first user and a second contact identifier for the second user.
4. The method according to claim 3, wherein: Presenting the mixed list includes visually distinguishing the first contact identifier from the second contact identifier in the mixed list.
5. The method according to claim 4, wherein: The second contact identification includes a non-friend indicator and the first contact identification does not include the non-friend indicator.
6. The method according to claim 1, wherein: The relationship data records the bidirectional relationship between the specific user and the first user within the interactive system.
7. The method according to claim 1, wherein: Enabling the particular user to initiate an electronic interaction with the second user includes enabling the particular user to send an electronic message to a second user of the interaction system associated with the second electronic contact record.
8. The method according to claim 7, wherein: The electronic message is an electronic message presented to the second user in a messaging user interface, the messaging user interface including a set of privacy control graphical elements, one or more of the privacy control graphical elements being user selectable to allow or prohibit communication with the particular user.
9. The method according to claim 7, wherein: Enabling the specific user to send the electronic message to the second user includes: causing a messaging user interface including a relationship establishment graphical element to be presented, wherein the relationship establishment graphical element is user-selectable to invite the second user to establish a two-way relationship with the specific user in the context of the interactive system.
10. The method according to claim 9, wherein: Establishing the bidirectional relationship includes enabling automatic sharing of predetermined data between the specific user and the second user within the interactive system.
11. The method according to claim 9, wherein: Inviting the second user to establish a two-way relationship with the specific user in the context of the interactive system includes: inviting the second user to establish a two-way relationship, and the interactive system automatically shares user-generated content between the specific user and the second user according to the two-way relationship.
12. The method according to claim 2, further comprising: accessing third electronic contact data, the third electronic contact data being associated with the third-party application and comprising a third electronic contact record for a non-user of the interactive system; causing the third electronic contact record to be presented within the interactive system along with the composite electronic contact data, wherein presenting the third electronic contact record comprises: visually distinguishing presentation of the third electronic contact record from both the first electronic contact record and the second electronic contact record; and The particular user of the interactive system is enabled to invite the non-user to register with the interactive system using the third electronic contact record.
13. The method according to claim 12, wherein: Enabling the particular user of the interactive system to invite the non-user to register with the interactive system comprises causing a user-selectable invitation graphical element to be presented in association with the third electronic contact record in a user interface, user selection of the invitation graphical element causing a registration invitation to be sent to a device of the non-user.
14. The method according to claim 2, wherein: The third-party application is a contact management application.
15. The method according to claim 2, wherein: The third-party application is a third-party communication application.
16. The method according to claim 2, wherein: The third-party application is an application hosted on a device of at least one of: the particular user, the first user, or the second user.
17. The method according to claim 1, wherein: Enabling the specific user of the interactive system to initiate an electronic interaction with the second user comprises: checking the privacy settings of the second user stored in the interactive system; and In response to determining that the privacy settings of the second user allow electronic interactions with users with whom the second user has no relationship as reflected in the relationship data, automatically causing an indication to be presented at a device of the second user and within a messaging user interface that an electronic interaction was initiated by the particular user.
18. The method according to claim 1, wherein: Generating the composite electronic contact data comprises: using output generated by a recommendation engine of the interactive system to determine that the second electronic contact record is to be included in the composite electronic contact data, and wherein causing presentation of the composite electronic contact data within the interactive system comprises: automatically causing presentation in a user interface of a blended list of contact identifiers comprising a first contact identifier of the first user and a second contact identifier of the second user, the second contact identifier being positioned relative to other contact identifiers in the blended list based on the output generated by the recommendation engine.
19. A computing device comprising at least one processor and a memory storing instructions, the instructions being configured such that when executed in cooperation with controlling the at least one processor, the instructions operate the device to perform operations comprising: For interactive system maintenance: first electronic contact data of a plurality of users of the interactive system, and relationship data relating to relationships between the plurality of users of the interactive system; Using the first electronic contact data and the relationship data, composite electronic contact data is automatically generated, the composite electronic contact data comprising: a first electronic contact record of a first user of the interactive system, the particular user of the interactive system having a relationship with the first user as reflected in the relationship data, and a second electronic contact record of a second user of the interactive system, the particular user having no relationship with the second user as reflected in the relationship data; causing presentation of the composite electronic contact data within the interactive system, wherein presenting the composite electronic contact data comprises: visually distinguishing presentation of the first electronic contact record from presentation of the second electronic contact record; and The particular user of the interactive system is enabled to use the second electronic contact record to initiate an electronic interaction with the second user.
20. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one computer, cause the at least one computer to perform operations comprising: For interactive system maintenance: first electronic contact data of a plurality of users of the interactive system, and relationship data relating to relationships between the plurality of users of the interactive system; Using the first electronic contact data and the relationship data, composite electronic contact data is automatically generated, the composite electronic contact data comprising: a first electronic contact record of a first user of the interactive system, the particular user of the interactive system having a relationship with the first user as reflected in the relationship data, and a second electronic contact record of a second user of the interactive system, the particular user having no relationship with the second user as reflected in the relationship data; causing presentation of the composite electronic contact data within the interactive system, wherein presenting the composite electronic contact data comprises: visually distinguishing presentation of the first electronic contact record from presentation of the second electronic contact record; and The particular user of the interactive system is enabled to use the second electronic contact record to initiate an electronic interaction with the second user.
Citation Information
Cited By
External messaging function for an interaction system
US12335211B2
