Managing content across multiple windows

Abstract

Aspects of the present disclosure relate to a system for managing conversations across multiple windows or tabs. The system accesses a dialog interface of the messaging application over the first web session and presents the dialog interface in the first web session. The system receives, from a second web session, a request to access the dialog interface. In response to receiving the request, the system transfers the dialog interface from the first web session to the second web session.

Description

[0001] Priority Claim

[0002] This application claims the benefit of priority to U.S. patent application Ser. No. 17 / 810,992, filed on Jul. 6, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to accessing online services using a browser. Background Art

[0004] Messaging applications allow users to communicate with each other in a variety of different ways. Users can send chat messages to one or more other users. Users can also access certain group pages and view and post content to those pages. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0007] Figure 2 is a diagrammatic representation of a messaging client application according to some examples.

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

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

[0010] Figure 5 is a diagrammatic representation of a dialog management system according to some examples.

[0011] Figure 6 , Fig. 7A and Figure 7B is a graphical representation of the output of a dialog management system according to some examples.

[0012] Figure 8 is a flow diagram illustrating example operations of a dialog management system according to some examples.

[0013] Fig. 9is 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.

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

[0015] The following description includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative examples of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth to provide an understanding of various examples. However, it will be apparent to those skilled in the art that examples may be practiced without these specific details. Typically, known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.

[0016] With the widespread use of mobile devices such as smart phones and tablet computers, many online services are provided as independent client-side applications designed for use with mobile devices, rather than as websites accessed using traditional web browsers (such as Chrome). For example, messaging applications are usually implemented as client-side applications executed on mobile devices, so that terminal users can communicate with each other when users move. Although online services can be used from any location to provide flexibility and convenience, in some cases, users may prefer to use traditional web browsers to access services. For example, during traditional working hours, many users use desktop or laptop computers in long time periods. In these cases, it may be more convenient to access online services via a web browser, because users do not have to switch between devices, and may be prohibited from installing client-side applications on their work computers.

[0017] Another reason why users may prefer to use a web browser to access online services is that it allows users to multitask by easily switching between multiple windows and web browser tabs. Due to the limited display size on mobile devices, client-side applications executed on mobile devices can only be presented one at a time. In contrast, multiple windows can be displayed simultaneously when using a desktop or laptop computer. Users can switch between multiple windows by simply selecting a window and making it the focus.

[0018] However, when implementing a web browser-based version of an online service rather than a client-side application version for a mobile device, the flexibility provided by the web browser may present challenges. For example, some online services may present confidential and / or private data that should be protected. When implemented as a client-side application on a mobile device, the display of private data is controlled to a single instance of the client-side application, because the mobile device does not generally allow multiple instances of the application to be executed simultaneously. In contrast, in a web browser-based implementation, multiple instances of an online service may be accessed simultaneously by using different web browser windows or tabs. Multiple instances of an online service may increase the possibility that confidential and / or private data may be accidentally leaked.

[0019] Some online services may implement ephemeral functionality that is triggered when a user views (e.g., sees) content. For example, a messaging service may be designed to automatically delete a message or other shared content after the user views the content or after a threshold period of time after the user views the content. This functionality may be triggered unintentionally in a web browser-based implementation even if the user does not actually view the content. For example, content may appear in an instance of an online service that the user has not viewed or is not even aware of. Therefore, the content may be deleted before it is viewed by the user.

[0020] The disclosed technology solves these technical problems by providing intelligence that ensures that when a web browser is used to access an application on a mobile device, the same level of privacy, security, protection, and functionality provided by accessing the application is maintained across platforms. For example, a web browser-based version of an application can be designed to limit certain features of the application when certain conditions are met. As an example, certain conversation elements presented by a messaging application can be transferred from being viewed or accessed by a first web session (e.g., a first tab or window or a first web browser application) to being viewed or accessed by a second web session (e.g., a second tab or window or a second web browser application). In some examples, when attempting to access features such as conversation features by a second web session, such conversation features are restricted and can only continue to be accessed by the first web session. Limiting the number of windows and / or tabs that provide an instance of an online service, and / or the data presented by the online service reduces the possibility of private data being viewed by another user or captured via a screenshot, and prevents short-term functions from being triggered unintentionally. In this way, a certain level of privacy, security, protection, and functionality that users expect when accessing applications is maintained across platforms.

[0021] In these ways, the techniques described herein improve the efficiency of using an electronic device and the overall experience of a user when using an electronic device.

[0022] Networked computing environment

[0023] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of which hosts several applications, including a messaging client 104 and other external applications 109 (e.g., third-party applications). Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on corresponding other client devices 102), a messaging server system 108, and an external application server 110 via a network 112 (e.g., the Internet). The messaging client 104 can also communicate with locally hosted third-party applications (also referred to as "external applications" and "external apps") 109 using an application programming interface (API).

[0024] In some examples, client device 102 may include AR glasses or AR headsets, where virtual content is displayed within the lenses of the glasses while the user views the real world environment through the lenses. For example, an image may be presented on a transparent display, which allows the user to view content presented on the display and real-world objects simultaneously.

[0025] Messaging clients 104 (sometimes referred to as client applications) are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via network 112. Data exchanged between messaging clients 104 and between messaging clients 104 and messaging server systems 108 includes functions (e.g., commands to activate functions) and payload data (e.g., text, audio, video, or other multimedia data).

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

[0027] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is activated and controlled by functions available via the user interface of the messaging client 104.

[0028] Turning now specifically to the messaging server system 108, an API server 116 is coupled to and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0029] The API server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the API server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 in order to activate the functionality of the application server 114. The API server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from the messaging client 104 to the messaging server 118 and for possible access by another messaging client 104; setting of collections of media data (e.g., stories); retrieving a list of friends of the user of the client device 102; retrieving such collections; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); the position of friends within the social graph; and opening application events (e.g., related to the messaging client 104).

[0030] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social network server 124. The messaging server 118 implements several message processing technologies and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. In view of the hardware requirements of other processor- and memory-intensive data processing, such processing of data can also be performed on the server side by the messaging server 118.

[0031] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from or received at the messaging server 118 .

[0032] The image processing server 122 is used to implement the enhancement system 208 ( Figure 2 The scanning functionality includes activating and providing one or more AR experiences on the client device 102 when an image is captured by the client device 102. Specifically, the messaging client 104 on the client device 102 can be used to activate the camera. The camera displays one or more real-time images or videos and one or more icons or identifiers of one or more AR experiences to the user. The user can select a given identifier in the identifier to launch the corresponding AR experience or perform the desired image modification (e.g., launch an AR experience, as described below in conjunction with Figures 6 to 10 as discussed).

[0033] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3 Examples of functions and services supported by the social networking server 124 include identifying other users of the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also identifying interests and other entities of a particular user.

[0034] Returning to the messaging client 104, the features and functions of the external resource (e.g., a third-party application 109 or an applet) are available to the user via the interface of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing an external resource (e.g., a third-party resource) such as a feature of an external application 109. The external resource can be a third-party application (external application 109) installed on the client device 102 (e.g., a "local application"), or a small-scale version of a third-party application (e.g., a "applet") hosted on the client device 102 or away from the client device 102 (e.g., on an external resource or application server 110). The small-scale version of the third-party application includes a subset of the features and functions of the third-party application (e.g., a full-scale local version of a third-party standalone application) and is implemented using a markup language document. In one example, the small-scale version of the third-party application (e.g., a "applet") is a web-based markup language version of the third-party application and is embedded in the messaging 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).

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

[0036] In response to determining that the external resource is a locally installed external application 109, the messaging client 104 instructs the client device 102 to launch the external application 109 by executing the locally stored code corresponding to the external application 109. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the external application server 110 to obtain a markup language document corresponding to the selected resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

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

[0038] The messaging client 104 may present a list of available external resources (e.g., third-party or external applications 109 or applets) to the user to launch or access a given external resource. The list may be presented in a context-sensitive menu. For example, icons representing different external applications in the external applications 109 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0039] In some examples, the messaging client 104 is accessed on a first web session (e.g., a first window or tab of a first web browser application (e.g., a first type of web browser application implemented on a desktop computer or other client device 102)). The messaging client 104 provides a conversation interface for display on the first web session. In such a case, certain functions and features of the messaging client 104 may be limited or obscured when certain conditions are met by the desktop computer, the client device 102, and / or the web browser application. For example, the messaging client 104 monitors user input received by the client device 102 to determine whether the conversation interface is initiated or accessed by a second web session (e.g., a second window or tab of a second web browser application (e.g., a second type of web browser application implemented on a desktop computer or other client device 102)). Based on the determination, the messaging client 104 transfers the conversation interface to the second web session to prevent updates to the conversation interface on the first web session, or allows the user to continue to access the conversation interface on the first web session and prevents access to the conversation interface on the second web session. In some cases, when the conversation interface is transferred to the second web session, the messaging client 104 obscures the first subset of conversation elements presented by the first web session. In some cases, in response to transferring the conversation interface from the first web session to the second web session, the messaging client 104 modifies one or more display properties of the second subset of conversation elements.

[0040] Next, in conjunction with the dialogue management system 224, Figure 2 and Figure 5 Further details of the functions performed by the messaging client 104 are discussed in . Although the present disclosure describes the concept of adjusting the display of a web browser window or tab associated with a messaging application, this is only an example and is not meant to be limiting. Similar techniques can be used for any type of online service provided through a web browser application, such as financial services, online retail services, etc.

[0041] System Architecture

[0042] Figure 21 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, an external resource system 220, and a conversation management system 224.

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

[0044] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into "event libraries" or "event stories." Such collections can be made available for a specified time period (e.g., the duration of an event related to the content). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

[0045] In addition, the collection management system 204 also includes a curation interface 206, which enables collection managers to manage and curate specific content collections. For example, the curation interface 206 enables event organizers to curate collections of content related to specific events (e.g., deleting inappropriate content or redundant messages). In addition, the collection management system 204 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 the collection. In such a case, the collection management system 204 operates to automatically pay such users for using their content.

[0046] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays (media overlays) for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. Media overlays 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) at the client device 102. For example, media overlays can include text, graphic elements, or images that can be superimposed on the top of photos taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, the augmentation system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of a business at the geographic location of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

[0047] In some examples, the enhancement system 208 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 enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

[0048] In other examples, the augmentation system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the augmentation system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain an AR experience, and presents an identifier of such an experience in one or more user interfaces (e.g., as an icon on a real-time image or video, or as a thumbnail or icon in an interface dedicated to the identifier of the presented AR experience). Once the AR experience is selected, one or more images, videos, or AR graphical elements are retrieved and presented as an overlay on the image or video captured by the client device 102. In some cases, the camera is switched to a front view (e.g., the front camera of the client device 102 is activated in response to the activation of a particular AR experience), and an image from the front camera of the client device 102, rather than the rear camera of the client device 102, begins to be displayed on the client device 102. One or more images, videos, or AR graphical elements are retrieved and presented as an overlay on top of the image captured and displayed by the front-facing camera of the client device 102 .

[0049] In other examples, the augmentation system 208 can communicate and exchange data with another augmentation system 208 on another client device 102 and with a server via the network 112. The exchanged data may include: a session identifier identifying the shared AR session; a transformation between the first client device 102 and the second client device 102 (e.g., the plurality of client devices 102 include the first device and the second device) for aligning the shared AR session to a common origin, a common coordinate system, and functionality (e.g., a command to activate a function) and other payload data (e.g., text, audio, video, or other multimedia data).

[0050] The augmentation system 208 sends the transformation to the second client device 102 so that the second client device 102 can adjust the AR coordinate system based on the transformation. In this way, the first client device and the second client device 102 synchronize their coordinate systems and frames to display the content in the AR session. Specifically, the augmentation system 208 calculates the origin of the second client device 102 in the coordinate system of the first client device 102. The augmentation system 208 can then determine an offset in the coordinate system of the second client device 102 based on the position of the origin in the coordinate system of the second client device 102 from the perspective of the second client device 102. The transformation is generated using the offset so that the second client device 102 generates AR content according to a common coordinate system with the first client device 102.

[0051] The augmentation system 208 can communicate with the client device 102 to establish a separate or shared AR session. The augmentation system 208 can also be coupled to the messaging server 118 to establish an electronic group communication session (e.g., group chat, instant messaging) for the client device 102 in the shared AR session. The electronic group communication session can be associated with a session identifier provided by the client device 102 to obtain access to the electronic group communication session and the shared AR session. In one example, the client device 102 first obtains access to the electronic group communication session, and then obtains a session identifier in the electronic group communication session that allows the client device 102 to access the shared AR session. In some examples, the client device 102 is able to access the shared AR session without the assistance of the augmentation system 208 in the application server 114 or communication with the augmentation system 208 in the application server 114.

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

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

[0054] The external resource system 220 provides an interface to the messaging client 104 for communicating with the external application server 110 to launch or access external resources. Each external resource (application) server 110 hosts, for example, a small-scale version of an application based on a markup language (e.g., HTML5) or an external application (e.g., a game, utility, payment, or ride-sharing application outside the messaging client 104). The messaging client 104 can launch the web-based resource by accessing an HTML5 file from an external resource (application) server 110 associated with a web-based resource (e.g., application). In some examples, the application hosted by the external resource server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes APIs that have functions that can be called or activated by web-based applications. In some examples, the messaging server 118 includes a JavaScript library that provides access to certain user data of the messaging client 104 to a given third-party resource. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0055] In order to integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the messaging server 118 by the external resource (application) server 110 or received by the external resource (application) server 110 in other ways. Once downloaded or received, the SDK will be 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 messaging client 104 into the web-based resource.

[0056] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., third-party or external applications 109 or applets) and the messaging client 104. This provides users with a seamless experience of communicating with other users on the messaging client 104 while retaining the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates the communication between the external resource server 110 and the messaging client 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously via these communication channels between the external resources and the messaging client 104. 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.

[0057] By using the SDK, not all information from the messaging client 104 is shared with the external resource server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each external resource server 110 provides an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., box art or other graphics) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access a feature of a web-based external resource through the graphical user interface (GUI) of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0058] The messaging client 104 presents a GUI (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another GUI 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 messaging client 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the messaging client 104 slides up a menu (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen) for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the messaging client 104 authorizes the external resource to access the user data according to the OAuth 2 framework.

[0059] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, access to a first type of user data (e.g., only a two-dimensional (2D) avatar of a user with or without different avatar characteristics) is provided to an external resource including a full-scale external application (e.g., a third party or external application 109). As another example, access to a second type of user data (e.g., payment information, a 2D avatar of a user, a 3D avatar of a user, and an avatar with various avatar characteristics) is provided to an external resource including a small-scale version of an external application (e.g., a web-based version of a third-party application). Avatar characteristics include different ways to customize the look and feel of an avatar, such as different poses, facial features, clothing, etc.

[0060] The dialog management system 224 monitors the web session used by the client device 102 to access and present the dialog interface of the messaging client 104 displayed on the web browser implemented on a specific type of client device 102 (e.g., a desktop computer). The dialog management system 224 conditionally and intelligently transfers the dialog interface from one web session to another web session in response to determining that a request to access the dialog interface is received from another web session. The dialog elements may include: user identifiers, chat input areas, exchanged messages, presence or user status indicators, phone call status indicators and options for making phone calls, group names, and various other dialog related information. Although the present disclosure describes the concept of adjusting the display of a web browser window or tab associated with a dialog element, this is only an example and is not meant to be limiting. Similar techniques can be used for any kind of online services provided through a web browser application, such as financial services, online retail services, etc. For example, in a financial services application, financial elements such as personal identity information (PII) and other account information can be obscured.

[0061] In some cases, when the conversation interface is transferred to the second web session, the conversation management system 224 blocks, limits, or obscures certain conversation elements of the conversation interface presented by the first web session. In some cases, when the conversation interface is transferred to the second web session, the conversation management system 224 stops receiving or downloading certain conversation elements of the conversation interface presented by the first web session. In this way, the conversation management system 224 maintains the privacy, security, and protection of the messaging client 104 when the messaging client 104 is accessed on different types of devices (e.g., cross-platform).

[0062] Data Architecture

[0063] Figure 3 is a diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including several tables, it should be understood that data may be stored in other types of data structures (eg, object-oriented databases).

[0064] Database 126 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 4 Additional details regarding information that may be included in a message and included within the message data stored in message table 302 are described.

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

[0066] The entity graph 308 stores information about relationships and associations between entities. Such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based, by way of example only.

[0067] 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 messaging system 100. In the case where the entity is a person, the profile data 316 includes, for example, a user name, phone number, address, and settings (e.g., notification and privacy settings), as well as 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 messaging system 100 and on a map interface displayed to other users by the messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a state or activity that a user can select to communicate at a particular time.

[0068] Where the entity is a group, the 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 related to the group (eg, notifications).

[0069] Database 126 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).

[0070] The database 126 may also store data related to individual and shared AR sessions. The data may include data transmitted between an AR session client controller of a first client device 102 and another AR session client controller of a second client device 102, and data transmitted between an AR session client controller and the augmented system 208. The data may include data for establishing a common coordinate system for a shared AR scene, transformations between devices, session identifiers, images depicting the body, skeletal joint positions, wrist joint positions, feet, and the like.

[0071] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a recipient user. Filters can be of various types, including filters selected by a user from a set of filters presented to a sending user by messaging 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 a sending user based on a geographic location. For example, a geolocation filter specific to a nearby or special location can be presented by messaging client 104 within a user interface based on geographic location information determined by a global positioning system (GPS) unit of client device 102.

[0072] Another type of filter is a data filter, which may be selectively presented to the sending user by the messaging client 104 based on other input or information collected by the client device 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 client device 102, or the current time.

[0073] Other augmented data that may be stored in the image table 312 include AR content items (eg, corresponding to an applied AR experience). AR content items or AR items may be real-time special effects and sounds that may be added to an image or video.

[0074] As described above, augmented data includes AR 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 the image when it is captured using the device sensor (e.g., one or more cameras) of the client device 102 and then display the image on the screen of the client device 102 with the modification. This also includes modifications to stored content (e.g., video clips in a library that can be modified). For example, in a client device 102 that can access multiple AR content items, a user can use a single video clip with multiple AR content items to see how different AR content items will modify the stored clips. For example, by selecting different AR content items for the content, multiple AR content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data can be simply displayed 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 AR content items will look in different windows of the display. This can, for example, enable viewing multiple windows with different pseudo-random animations on the display at the same time.

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

[0076] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as human faces and parts of the human body, animals, or non-living things (e.g., chairs, cars, or other objects) can be processed using computer animation models.

[0077] In some examples, in the case where a specific modification is selected together with the content to be transformed, the element to be transformed is identified by the computing device, and then if the element to be transformed is present in the video frame, the element to be transformed is detected and tracked. The elements of the object are modified according to the request for modification, thereby transforming the frame of the video stream. The transformation of the frame of the video stream can be performed by different methods for different types of transformations. For example, for the frame transformation that mainly refers to the variation of the elements of the object, the characteristic points for each element of the object are calculated (for example, using the active shape model (Active Shape Model, ASM) or other known methods). Then, for each element of at least one element of the object, a grid based on the characteristic points is generated. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A set of first points is generated for each element based on the request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object may also be changed or deformed by tracking and modifying the background of the modified object.

[0078] In some examples, a transformation that changes some areas of an object using elements of an object can be performed by calculating characteristic points for 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 the points are generated. Then, the elements of the object are tracked by aligning the area for each element with the position for 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 can involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the request for modification; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications can be used. For certain models to be animated, some characteristic points can be selected as control points for determining the entire state space of options for model animation.

[0079] In some examples of using computer animation models that use face detection to transform image data, faces are detected on images using a specific face detection algorithm (e.g., Viola-Jones). The ASM algorithm is then applied to the face area of ​​the image to detect facial feature reference points.

[0080] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist 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 process can be used for any such object. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. 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.

[0081] In some examples, the landmark search begins with an average shape that aligns with the location and size of the face determined by a global face detector. Such a search then repeats the steps of proposing tentative shapes by adjusting the positions of shape points by template matching of the image texture around each point, and then conforming the tentative shapes to the global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse to fine resolution.

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

[0083] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be presented in association with an interface described herein. The modification icon includes a change in the basis that can modify 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 smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can 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 has been selected, the modified result can be presented in real time or near real time. Furthermore, while the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine-taught neural networks can be used to implement such modifications.

[0084] The GUI presenting the modifications performed by the transformation system can supply additional interactive options for the user. Such options can be based on an interface for initiating content capture and selecting a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modifications can be persistent after the initial selection of the modification icon. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case of multiple faces being modified by the transformation system, the user can globally switch the modification on or off by tapping or selecting a single face modified and displayed in the GUI. In some examples, a single face in a group of multiple faces can be modified individually, or such modifications can be switched individually by tapping or selecting a single face or a series of single faces displayed in the GUI.

[0085] The story table 314 stores data about a collection of messages and associated image, video or audio data that are compiled into a collection (e.g., a story or library). 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 the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0086] A collection may also constitute a "live story" that 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 various locations and events. Users whose client devices have location services enabled and who are at a common location event at a particular time may be presented with the option to contribute content to a particular live story, for example, via the user interface of the messaging client 104. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

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

[0088] As mentioned above, the video table 304 stores video data, which in one example is associated with a message for which a record is maintained within the message table 302. Similarly, the image table 312 stores image data associated with a message for which message data is stored in the entity table 306. The entity table 306 may associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0089] The data structure 300 may also store training data for training one or more machine learning techniques (models) to segment items of real-world objects or real-world environments depicted in images corresponding to locations (e.g., rooms in a home). The training data may include multiple images and videos and their corresponding ground-truth room segmentations. The images and videos may include a mixture of various real-world objects that may appear in different rooms of a home or family. One or more machine learning techniques may be trained to extract features of received input images or videos and establish a relationship between the extracted features and the segmentation. Once training is completed, the machine learning techniques may receive new images or videos and may compute segmentations of items depicted in the newly received images or videos.

[0090] Data communication architecture

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

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

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

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

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

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

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

[0098] Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of a message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to a user via messaging client 104.

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

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

[0101] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tags 420 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.

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

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

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

[0105] Dialogue Management System

[0106] Figure 5 is a diagrammatic representation of a dialog management system 224 according to some examples. The dialog management system 224 can include a dialog access module 512, a web session module 514, and a dialog transfer module 516.

[0107] In some examples, the conversation management system 224 accesses a conversation interface of a messaging application on a web browser and presents the conversation interface in a first window associated with a first web session (e.g., a first web browser application). The conversation management system 224 receives a request to access the conversation interface from a second web session, and in response to receiving the request, the conversation management system 224 transfers the conversation interface from the first web session to the second web session.

[0108] In some examples, the dialog management system 224 retrieves a uniform resource locator (URL) of the messaging application and downloads a markup language document corresponding to the messaging application. The dialog management system 224 processes the markup language document through a web browser application to display a dialog interface on, for example, a desktop computer.

[0109] In some examples, the first web session includes a first tab or first window of a first web browser application. In some examples, the second web session includes a second tab or second window of the first web browser application. In some examples, the second web session includes a second tab or second window of the second web browser application.

[0110] In some examples, the dialog management system 224 prevents one or more operations from being performed on the first web session in response to transferring the dialog interface from the first web session to the second web session. In some cases, the dialog management system 224 prevents one or more updates associated with the dialog interface from being provided to the first web session after transferring the dialog interface from the first web session to the second web session.

[0111] In some examples, the dialog management system 224 replaces the presentation of the dialog interface in the first web session with a notification indicating that the dialog interface has been accessed by multiple web sessions. In such a case, after the dialog interface is transferred from the first web session to the second web session, the dialog management system 224 presents in the notification an option to resume presentation of the dialog interface on the first web session instead of the second web session.

[0112] In some examples, the conversation management system 224 determines, in response to the request, that the conversation interface presented by the first web session includes an active phone call. In such a case, the conversation management system 224 presents a notification with one or more options associated with the active phone call on the second web session in response to determining that the conversation interface presented by the first web session includes an active phone call. The first option of the one or more options includes an option to return to the first web session to continue the active phone call. The first option of the one or more options includes an option to end the active phone call, wherein, in response to receiving an input selecting the first option, the conversation session is accessed on the second web session. The first option of the one or more options includes an option to resume the active phone call in the second web session. In such a case, the conversation management system 224 terminates the active phone call made by the first web session in response to receiving an input selecting the first option, and reestablishes the active phone call on the second web session by reconnecting to one or more participants of the active phone call using the second web session.

[0113] In some examples, dialog management system 224 sends a message to the first web session to terminate the dialog interface in response to transferring the dialog interface from the first web session to the second web session.

[0114] In some examples, the conversation management system 224 determines, in response to receiving the request, that the conversation interface is currently being accessed by the first web session. This can be performed by searching the local storage device for an identifier associated with the first web session and determining that the identifier is stored in the local storage device. The conversation interface can include a plurality of conversation elements, the plurality of conversation elements including: a chat area including one or more messages exchanged in the conversation, a chat input area for enabling the user to compose a message, a presence area indicating an activity status of each of a plurality of friends, a friend area listing a plurality of friends with whom the user previously had a conversation, and a phone call area for placing a phone call to a given friend.

[0115] In some examples, the conversation access module 512 receives a request from a client device 102 to access a conversation interface of a messaging client 104. For example, the conversation access module 512 receives a request to launch a conversation interface on a first web session (e.g., a first window of a web browser application, a first tab of a browser application, or a first computing device). The conversation access module 512 can detect that the request has been received from a particular type of client device 102 (e.g., a desktop computer) and / or from a particular type of software application (e.g., a web browser application). That is, the conversation access module 512 can enable a user to access the content of the messaging client 104 via other types of client applications (e.g., a web browser), rather than launching the messaging client 104 directly from an application running on a mobile device that includes code for executing the messaging client 104.

[0116] In such a case, the conversation access module 512 provides a markup language document to the first web session of the web browser application. The conversation access module 512 stores the random number or value associated with the first web session in the local memory of the client device 102 in response to accessing the conversation interface on the first web session. The markup language document includes a visual display of the conversation interface that mimics the display of the conversation interface on the local messaging application implemented on the mobile device. Specifically, the conversation interface presented on the web browser application by processing the markup language document can have the same look and feel as the conversation interface accessed on the messaging client 104. In some cases, the conversation interface displayed by processing the markup language document is different from the conversation interface presented on the mobile device when the messaging client 104 is directly launched by executing the messaging client 104 software on the mobile device.

[0117] The conversation access module 512 determines that the type of client device 102 and / or software used to access the conversation interface corresponds to the specified type. In such a case, the conversation access module 512 conditionally displays the conversation interface information (e.g., conversation elements) and the manner in which the information is displayed based on certain conditions. As an example, the conversation access module 512 conditionally displays the conversation interface information (e.g., conversation elements) and the manner in which the information is displayed based on whether the conversation interface has been accessed by a different web session.

[0118] For example, Figure 6 As shown in , a user interface display 600 of a conversation interface of a messaging client 104 is provided by a first web session on a web browser application implemented by a desktop computer (or mobile device). The user interface display 600 includes a friend list area 650, a presence area 610, a chat area 620, a chat input area 630, and a phone call area 640. The friend list area 650 displays a list of friends of a user of the client device 102 with whom the user has previously exchanged at least one message, or just generally displays a list of friends of a user on the messaging client 104. The user interface display 600 can receive input selecting a given friend from the friend list area 650. In response, the user interface display 600 displays a conversation including a list of messages previously exchanged with the given friend in the conversation in the chat area 620. If the user has not previously exchanged messages with the selected given friend, the chat area 620 can be blank.

[0119] The user interface display 600 may receive input selecting the chat input area 630. In response, the user interface display 600 monitors the keystroke input of the physical keyboard and adds the characters corresponding to the keystrokes to the chat input area 630. In response to receiving the ENTER key or other send options, the user interface display 600 sends the collected characters from the chat input area 630 to a given friend associated with the conversation. For example, the user interface display 600 generates a message corresponding to the collected characters and adds the message to the chat area 620 for display in the conversation interface provided to the friends participating in the conversation. In some examples, the user interface display 600 receives input selecting the phone call area 640. In response, the user interface display 600 establishes a voice and / or video call with a given friend associated with the conversation being displayed in the chat area 620.

[0120] Return to reference Figure 5, the conversation access module 512 communicates with the web session module 514 to determine whether the conversation interface has been launched or accessed on the second web session or client device 102. For example, the conversation access module 512 conditionally performs presentation of the conversation interface on the first web session or the second web session based on information received from the web session module 514 indicating whether the conversation interface was previously accessed on another web session. For example, the conversation access module 512 receives a request to launch a conversation interface on a second web session (e.g., a second tab or second window of the same web browser application or a different web browser application for running the first web session). In response, the conversation access module 512 communicates with the web session module 514 to determine that the conversation interface has been accessed by the first web session. In such a case, the conversation access module 512 communicates with the conversation transfer module 516 to manage coordination and access to the conversation interface.

[0121] In some examples, the conversation transfer module 516 transfers the conversation interface from the first web session to the second web session. To do this, the conversation transfer module 516 instructs the first web session to stop receiving updates to the conversation interface. The conversation transfer module 516 may also instruct the first web session to block or limit access to and display of any or some parts or elements of the conversation interface. The conversation transfer module 516 then retrieves a markup language document associated with the conversation interface and presents the conversation interface on the second web session using the markup language document. The conversation transfer module 516 receives updates to the conversation interface and presents such updates on the second web session instead of the first web session.

[0122] In some examples, the dialog transfer module 516 receives input from the user to navigate back to the first web session. In such a case, the dialog transfer module 516 presents the following Fig. 7A , where notification 710 informs the user that the conversation interface cannot be accessed on multiple web sessions (e.g., tabs or windows). Notification 710 may specify that conversation transfer module 516 detects that the conversation interface is currently being accessed on a second web session. Notification 710 may inform the user that, in response to an interaction received from the user in first web session 720, the conversation interface may be resumed on first web session 720 and terminated on second web session. For example, in response to first web session 720 receiving a REFRESH command, conversation transfer module 516 may terminate access to the conversation interface on the second web session and resume access to the conversation interface on first web session 720. In such a case, conversation transfer module 516 presents user interface display 600 in which the conversation interface elements are presented in first web session 720.

[0123] In some examples, in response to receiving an input requesting that the conversation interface be presented on the second web session, the conversation transfer module 516 presents a notification allowing the user to decide where to continue presenting the conversation interface. That is, the conversation transfer module 516 may present one or more options instead of automatically transferring the operation of the conversation interface from the first web session to the second web session. The one or more options may include a first option to resume the operation of the conversation interface on the first web session. Figure 6 As shown in , in response to receiving input selecting the first option, the conversation transfer module 516 does not load the conversation interface in the second web session, and automatically navigates the user back to the first web session to view the conversation interface. The one or more options may include a second option to continue the operation of the conversation interface on the second web session. In response to receiving input selecting the second option, the conversation transfer module 516 loads the conversation interface in the second web session, and terminates the updating and presentation of the conversation interface on the first web session. In this case, Figure 6 The dialog interface shown in is presented on the second web session.

[0124] In some examples, the conversation transfer module 516 selectively presents an option of where to continue the conversation session in response to determining that certain operations or activities (e.g., an active phone call, an image capture operation, a video capture operation, an audio recording operation, an AR experience being initiated) are currently active and being performed on the first web session. For example, the conversation transfer module 516 determines that an active phone call is ongoing between the user and one or more friends on the first web session. In such a case, the conversation transfer module 516 presents an option such as Figure 7B , wherein notification 740 allows the user to select how to manage the conversation interface transition. In particular, the conversation transfer module 516 presents the second web session 730 including notification 740. Notification 740 informs the user of those operations or activities that are currently active and being performed by the first web session (e.g., active phone call, image capture operation, video capture operation, audio recording operation, AR experience being initiated). The conversation transfer module 516 presents one or more options for handling the transition.

[0125] In some examples, the first option 741 allows the user to resume an operation or activity (e.g., an active phone call, an image capture operation, a video capture operation, an audio recording operation, an initiated AR experience) on the first web session 720. In response to receiving input selecting the first option 741, the conversation transfer module 516 does not load the conversation interface in the second web session 730, and automatically navigates the user back to the first web session 720 to continue the operation or activity, such as Figure 6 as shown in .

[0126] A second option 742 may be presented for terminating the operation and activity (e.g., phone call, image capture operation, video capture operation, audio recording operation, launched AR experience) of the conversation interface on the first web session 720 to allow the user to continue such activity on the second web session 730. In response to receiving input selecting the second option 742, the conversation transfer module 516 terminates the operation or activity (e.g., active phone call, image capture operation, video capture operation, audio recording operation, launched AR experience) on the first web session 720 and reestablishes the operation or activity (e.g., active phone call, image capture operation, video capture operation, audio recording operation, launched AR experience) on the second web session 730. For example, the conversation transfer module 516 reconnects the active phone call with the same participant participating in the first web session 720 on the second web session 730.

[0127] Figure 8 800 according to some examples. Although the flowchart may describe the operations as a sequential process, many of these operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. The process terminates when its operations are completed. A process may correspond to a method, a program, etc. The steps of a method may be performed in whole or in part, may be performed in conjunction with some or all of the steps in other methods, and may be performed by any number of different systems or any part thereof (e.g., a processor in any system included in the system).

[0128] At operation 801 , as discussed above, the client device 102 accesses a conversation interface of a messaging application on a first web session.

[0129] At operation 802 , the client device 102 presents a conversation interface in a first web session, as discussed above.

[0130] At operation 803 , as discussed above, the client device 102 receives a request to access the conversation interface from the second web session.

[0131] At operation 804 , as discussed above, the client device 102 transfers the conversation interface from the first web session to the second web session in response to receiving the request.

[0132] Machine Architecture

[0133] Fig. 9It is a diagrammatic representation of a machine 900 in which instructions 908 (e.g., software, programs, applications, applet, app, or other executable code) may be executed to cause the machine 900 to perform any one or more of the methods discussed herein. For example, the instructions 908 may cause the machine 900 to perform any one or more of the methods described herein. The instructions 908 convert a general purpose, unprogrammed machine 900 into a specific machine 900 that is programmed to perform the functions described and illustrated in the manner described. The machine 900 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 900 may operate with the performance of 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 900 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular 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 appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 908 specifying actions to be taken by the machine 900. In addition, although only a single machine 900 is shown, the term "machine" should also be considered to include a collection of machines that individually or jointly execute instructions 908 to perform any one or more of the methods discussed herein. For example, the machine 900 may include a client device 102 or any of a number of server devices that form part of the messaging server system 108. In some examples, the machine 900 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 a particular method or algorithm are performed on the client side.

[0134] The machine 900 may include a processor 902, a memory 904, and an input / output (I / O) component 938 that may be configured to communicate with each other via a bus 940. In an example, the processor 902 (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 906 and a processor 910 that execute instructions 908. 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. 9 Multiple processors 902 are shown, but the machine 900 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0135] The memory 904 includes a main memory 912, a static memory 914, and a storage unit 916, all of which are accessible to the processor 902 via the bus 940. The main memory 904, the static memory 914, and the storage unit 916 store instructions 908 that embody any one or more of the methods or functions described herein. The instructions 908 may also reside, completely or partially, within the main memory 912, within the static memory 914, within a machine-readable medium within the storage unit 916, within at least one of the processors 902 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 900.

[0136] The I / O components 938 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 938 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 likely not include such a touch input device. It should be appreciated that the I / O components 938 may include Fig. 9 924 and 926. In various examples, the I / O components 938 may include a user output component 924 and a user input component 926. The user output component 924 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 926 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.

[0137] In other examples, the I / O component 938 may include a biometric component 928, a motion component 930, an environment component 932, or a position component 934, as well as various other components. For example, the biometric component 928 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 930 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0138] Environmental components 932 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 that detects concentrations of hazardous gases for safety or measures pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0139] With respect to cameras, client device 102 can have a camera system including, for example, a front-facing camera on a front surface of client device 102 and a rear-facing camera on a rear surface of client device 102. The front-facing camera can, for example, be used to capture still images and videos (e.g., “selfies”) of a user of client device 102, which can then be enhanced using the enhancement data (e.g., filters) described above. The rear-facing camera can, for example, be used to capture still images and videos in a more traditional camera mode, where the images are similarly enhanced using the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 can also include a 360° camera for capturing 360° photos and videos.

[0140] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 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.

[0141] The position component 934 includes a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or a barometer that detects air pressure that can obtain the altitude), an orientation sensor component (e.g., a magnetometer), and the like.

[0142] A variety of technologies may be used to achieve communication. The I / O components 938 also include a communication component 936 that is operable to couple the machine 900 to the network 920 or device 922 via a corresponding coupling or connection. For example, the communication component 936 may include a network interface component or other suitable device that interfaces with the network 920. In other examples, the communication component 936 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Components (e.g. Low power consumption), Device 922 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0143] In addition, the communication component 936 can detect the identifier or include a component operable to detect the identifier. For example, the communication component 936 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product code (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbol (Dataglyph), maximum code (MaxiCode), PDF417, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 936, such as a location obtained via Internet Protocol (IP) geolocation, ... Location derived from signal triangulation, location derived via detection of NFC beacon signals that can indicate a specific location, etc.

[0144] Various memories (e.g., main memory 912, static memory 914, and memory of processor 902) and storage unit 916 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. When executed by processor 902, these instructions (e.g., instructions 908) cause various operations to implement the disclosed examples.

[0145] The instructions 908 may be sent or received over the network 920 using a transmission medium via a network interface device (e.g., a network interface component included in the communications component 936) and using any of several well-known transmission protocols (e.g., HTTP). Similarly, the instructions 908 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with the device 922 using a transmission medium.

[0146] Software Architecture

[0147] Fig.10 1000 is a block diagram illustrating a software architecture 1004 that can be installed on any one or more of the devices described herein. The software architecture 1004 is supported by hardware, such as a machine 1002 including a processor 1020, a memory 1026, and an I / O component 1038. In this example, the software architecture 1004 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1004 includes layers such as an operating system 1012, a library 1010, a framework 1008, and an application 1006. In operation, the application 1006 invokes an API call 1050 through the software stack and receives a message 1052 in response to the API call 1050.

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

[0149] The library 1010 provides a common low-level infrastructure used by the application 1006. The library 1010 may include a system library 1018 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 1010 may include an API library 1024, 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 2D and 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 1010 may also include various other libraries 1028 to provide many other APIs to the application 1006.

[0150] The framework 1008 provides a common high-level infrastructure used by the applications 1006. For example, the framework 1008 provides various GUI functions, high-level resource management, and high-level location services. The framework 1008 can provide a wide range of other APIs that can be used by the applications 1006, some of which can be specific to a particular operating system or platform.

[0151] In an example, applications 1006 may include a home application 1036, a contact application 1030, a browser application 1032, a book reader application 1034, a location application 1042, a media application 1044, a messaging application 1046, a game application 1048, and a variety of other applications such as external applications 1040. Applications 1006 are programs that execute functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 1006 constructed in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, external applications 1040 (e.g., applications developed by an entity other than the vendor of a particular platform using an ANDROID™ or IOS™ SDK) can be a mobile operating system such as IOS™, ANDROID™, Phone, or another mobile operating system. In this example, external application 1040 can activate API calls 1050 provided by operating system 1012 to facilitate the functions described herein.

[0152] Glossary

[0153] "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.

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

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

[0156] "Component" means a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of specific processing or control functions. Components may be combined with other components via their interfaces to perform machine processing. A component may be a packaged functional hardware unit designed for use with other components and may be part of a program that typically performs a specific one of the related functions.

[0157] Components may constitute software components (e.g., code implemented on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit that is capable of performing certain operations and may be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) as hardware components that operate to perform certain operations described herein.

[0158] Hardware components can also be implemented mechanically, electronically, or any suitable combination thereof. For example, hardware components may include dedicated circuits or logic that are permanently configured to perform certain operations. Hardware components may be dedicated processors, such as field programmable gate arrays (FPGAs) or ASICs. Hardware components may also include programmable logic or circuit systems that are temporarily configured to perform certain operations by software. For example, hardware components may include software executed by general-purpose processors or other programmable processors. Once configured by such software, hardware components become specific machines (or specific components of machines) that are uniquely customized to perform the configured functions, rather than general-purpose processors. It should be recognized that it can be decided for cost and time considerations whether to implement hardware components mechanically in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system. Therefore, the phrase "hardware components" (or "hardware-implemented components") should be understood to include tangible entities, i.e., entities that are physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein.

[0159] Consider an example where hardware components are temporarily configured (e.g., programmed), without configuring or instantiating each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to be a special-purpose processor, the general-purpose processor can be configured to be a different special-purpose processor (e.g., including different hardware components) at different times. The software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time and to constitute a different hardware component at a different time.

[0160] Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be communicatively coupled. In the case of multiple hardware components simultaneously, communication can be realized by signal transmission between two or more hardware components in the hardware components (for example, by appropriate circuits and buses). In the example where multiple hardware components are configured or instantiated at different times, the communication between such hardware components can be realized, for example, by storing information in a memory structure that multiple hardware components can access and retrieving information in the memory structure. For example, a hardware component can perform an operation and store the output of the operation in a memory device that it is communicatively coupled to. Then, another hardware component can access the memory device at a subsequent time to retrieve the stored output and process the stored output. The hardware component can also start communication with an input device or an output device, and can operate on resources (for example, a collection of information).

[0161] The various operations of the example methods described herein may be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the method described herein may be implemented at least in part by a processor, wherein a specific one or more processors are examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors 902 or a processor-implemented component. In addition, one or more processors may also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation may be performed by a group of computers (as an example of a machine including a processor), wherein these operations may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations in the operation may be distributed between processors, not just residing in a single machine, but deployed across several machines. In some examples, the processor or processor-implemented components may be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other examples, the processor or processor-implemented components may be distributed across several geographic locations.

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

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

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

[0165] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

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

[0167] 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.

Claims

1. A method comprising: Accessing a conversation interface of a messaging application on a first web session; presenting the dialog interface in the first web session; receiving a request to access the conversation interface from a second web session; as well as In response to receiving the request, the conversation interface is transferred from the first web session to the second web session.

2. The method according to claim 1, wherein: The first web session includes a first tab or a first window of a first web browser application.

3. The method according to claim 2, wherein: The second web session includes a second tab or second window of the first web browser application.

4. The method according to claim 2, wherein: The second web session includes a second tab or a second window of a second web browser application.

5. The method according to claim 1, further comprising: In response to transferring the conversation interface from the first web session to the second web session, one or more operations are prevented from being performed on the first web session.

6. The method according to claim 1, further comprising: After transferring the conversation interface from the first web session to the second web session, one or more updates associated with the conversation interface are prevented from being provided to the first web session.

7. The method according to claim 1, further comprising: Presentation of the conversation interface in the first web session is replaced with a notification indicating that the conversation interface has been accessed by multiple web sessions.

8. The method according to claim 7, further comprising: After transferring the conversation interface from the first web session to the second web session, an option is presented in the notification to resume presentation of the conversation interface on the first web session instead of the second web session.

9. The method according to claim 1, further comprising: In response to the request, determining that the conversation interface presented by the first web session includes an active telephone call; as well as In response to determining that the conversation interface presented by the first web session includes the active phone call, presenting a notification on the second web session having one or more options associated with the active phone call.

10. The method according to claim 9, wherein: A first option of the one or more options includes an option to return to the first web session to continue the active telephone call.

11. The method according to claim 9, wherein: A first option of the one or more options includes an option to end the active telephone call, wherein the conversation interface is accessed on the second web session in response to receiving input selecting the first option.

12. The method according to claim 9, wherein: A first option of the one or more options includes an option to resume the active telephone call in the second web session, the method further comprising: In response to receiving input selecting the first option, terminating the active telephone call conducted by the first web session; and The active telephone call is reestablished on the second web session by reconnecting to one or more participants of the active telephone call using the second web session.

13. The method according to claim 1, further comprising: In response to transferring the conversation interface from the first web session to the second web session, sending a message to the first web session to terminate the conversation interface.

14. The method according to claim 1, wherein: The visit includes: Retrieving a uniform resource locator (URL) of the messaging application; downloading a markup language document corresponding to the messaging application; and The markup language document is processed by a web browser application to present the conversation interface on the first web session.

15. The method according to claim 1, wherein: The conversation interface includes multiple conversation elements, including: a chat area that includes one or more messages exchanged in the conversation, a chat input area for enabling a user to compose a message, a presence area that indicates an activity status of each of a plurality of friends, a friend area that lists the plurality of friends with whom the user has previously had conversations, and a phone call area for placing a phone call to a given friend.

16. The method according to claim 1, further comprising: In response to receiving the request, it is determined that the dialog interface is currently being accessed by the first web session.

17. The method according to claim 16, wherein: Determining that the dialog interface is currently being accessed by the first web session includes: searching local storage for an identifier associated with the first web session; and In response to determining that the identifier is stored in the local storage, it is determined that the dialog interface is currently being accessed by the first web session.

18. A system comprising: A processor configured to perform operations comprising: Accessing a conversation interface of a messaging application on a first web session; presenting the dialog interface in the first web session; receiving a request to access the conversation interface from a second web session; as well as In response to receiving the request, the conversation interface is transferred from the first web session to the second web session.

19. The system of claim 18, wherein: The first web session includes a first tab or a first window of a first web browser application.

20. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising: Accessing a conversation interface of a messaging application on a first web session; presenting the dialog interface in the first web session; receiving a request to access the conversation interface from a second web session; as well as In response to receiving the request, the conversation interface is transferred from the first web session to the second web session.

Images