Method and system for facilitating user to participate in content participation activity

Abstract

A method includes providing, through a user interface (UI) of a first application on a first screen device, a UI element that prompts a user to connect the first screen device with a second screen device that is presenting video to the user. The method further includes receiving, by the UI element, an indication of a user request to connect the first screen device with the second screen device. In response to receiving the indication of the user request to connect the first screen device with the second screen device, the method further includes pairing the first screen device with the second screen device. The method further includes providing one or more comments provided by one or more other users for the video simultaneously presented on the second screen device for presentation in the UI of the first application of the first screen device.

Description

Technical Field

[0001] Aspects and implementations of the present disclosure relate to methods and systems for promoting users to participate in content participation activities, and in particular, methods and systems for promoting users to participate in content presented by a second user device using a first user device. Background Art

[0002] A platform (e.g., a content sharing platform) can transmit (e.g., stream) media items to client devices connected to the platform over a network. Different types of client devices can be optimized for different tasks, preferred by users for different tasks, etc. For example, a first client device can provide a preferred viewing experience for a media item, while a different client device provides a preferred experience for further engagement associated with the media item. Summary of the invention

[0003] The following summary of the invention is a simplified overview of the present disclosure in order to provide a basic understanding of some aspects of the present disclosure. This summary of the invention is not a comprehensive review of the present disclosure. It is neither intended to identify the key or important elements of the present disclosure, nor to indicate any scope of a specific implementation of the present disclosure or any scope of the claims. Its sole purpose is to present some concepts of the present disclosure in a simplified form as a preface to a more detailed description presented later.

[0004] A system and method for facilitating a user to participate in one or more engagement activities associated with a media item is disclosed. In some implementations, a method includes: providing a UI element through a first user interface (UI) of a first application on a first device, the UI element prompting a user to connect the first device to a second device that is presenting a media item (e.g., a content item) to the user. The method further includes: receiving an indication of a user request to connect the first device to the second device through the UI element. The method further includes: in response to receiving an indication of a user request to connect the first device to the second device, pairing the first device with the second device. The method further includes: providing one or more elements for facilitating one or more engagement activities associated with the media items simultaneously presented on the second device for presentation in the UI of the first application of the first device.

[0005] In some implementations, in response to a user selecting an option to participate in an engagement activity associated with a video presented on a second device, a UI element prompting the user to connect the first device to the second device may be provided through a UI of a first application of the first device. The engagement activity may include viewing one or more comments of the video presented on the second device. The UI element may prompt the user to connect the first device to the second device to participate in the selected activity. The UI element may prompt the user to connect the first device to the second device to view the comments.

[0006] In some implementations, providing a UI element that prompts a user to connect a first device to a second device may include: providing an indication of an option to participate in an engagement activity associated with content presented on the second device through a second UI of a second application on the second device. Participating in the engagement activity may include viewing one or more comments. The presented content may include a video. Providing the UI element may further include: receiving a user selection of an option to participate in one or more engagement activities associated with the presented content through a UI of a second application of the second device. The user selection may include a selection to view one or more comments on a video presented by the second device. Providing the UI element may further include: causing a UI element that prompts a user to connect the first device to the second device to be presented in a first UI of a first application of the first device. Causing the UI element to be presented may be performed in response to a user selection of an option to participate in the engagement activity. Causing the UI element to be presented may be performed in response to a user selection to view one or more comments on a video presented on the second device.

[0007] In some implementations, providing a UI element that prompts a user to connect a first device to a second device may include detecting a user action on a first application of the first device. The first application is associated with a first user account. Providing the UI element may further include determining whether a second application on the second device is associated with the first user account and is presenting a video. Determining whether the second application is associated with the first user account may be performed in response to the detected user action. Providing the UI element may further include causing a UI element to be presented on the first UI of the first application that prompts the user to connect the first device to the second device. Causing the presentation of the UI element may be performed in response to determining that the second application is associated with the first user account and is presenting a video.

[0008] In some implementations, the user action may include at least one of: a user opening a first application on the first device; or a user selecting the first application from a list of applications open on the first device to move the first application from a background mode to an active mode.

[0009] In some implementations, the method may further include: before causing presentation of a UI element on the first UI of the first application prompting the user to connect the first device to the second device, determining that the user has not declined a previous prompt to connect the first device to the second device. The method may include determining that the user has not declined the previous prompt within a threshold amount of time. The method may include determining that the user has not declined the previous prompt during the current viewing session.

[0010] In some implementations, causing the first device to pair with the second device may include generating a first connection between the first device and a server.Causing the first device to pair with the second device may include generating a second connection between the second device and a server.

[0011] In some implementations, the method may further include receiving, through the first UI of the first application on the first device, a user request to adjust the presentation of content on the second device. In response to the user request to adjust the presentation of content presented on the second device, the method may further include causing the presentation of a video on the second device to be adjusted.

[0012] In some implementations, the method may further include identifying a plurality of comments associated with the content presented on the second device provided by a plurality of users. The plurality of comments may include one or more comments provided by one or more other users.

[0013] In some implementations, the method may further include: receiving, through the first UI of the first application of the first device, a new comment from the user regarding the video simultaneously presented on the second device.

[0014] In some implementations, the method may further include: receiving, through the UI of the first application of the first screen device, an indication of user feedback on at least one of the one or more comments provided by one or more other users on the video simultaneously presented on the second screen device. The feedback may include an indication of the user's approval or disapproval of the corresponding comment.

[0015] In another aspect of the present disclosure, a method includes providing a UI element in a UI of a first application on a first screen device, the UI element prompting a user to connect the first screen device to a second screen device that is presenting a video to the user. The method further includes receiving an indication of a user request to connect the first screen device to the second screen device through the UI element. The method further includes pairing the first screen device with the second screen device. Pairing the first screen device with the second screen device may be performed in response to receiving an indication of a user request to connect the first screen device to the second screen device. The method may further include: identifying one or more real-time chats associated with the video presented on the second screen device. The method further includes: allowing the user to participate in a real-time chat between multiple other users about the video presented simultaneously on the second screen device through the first screen device. The method may further include: receiving a message from the user about the video presented simultaneously on the second device through the UI of the first application of the first screen device, and including the user's message in the real-time chat associated with the video.

[0016] In some implementations, a UI element can be provided in response to a user selecting an option to participate in a real-time chat between multiple other viewers about a video presented on a second screen device, the UI element prompting the user to connect the first screen device with the second screen device. The UI element prompts the user to connect the first screen device with the second screen device to participate in the real-time chat.

[0017] In some implementations, providing a UI element that prompts a user to connect a first screen device to a second screen device may include detecting a user action on a UI on the first screen device. A first application of the first screen device is associated with a first user account. The detected action may include opening the first application or selecting to move the first application from a background mode to an active mode. Providing the UI element may further include determining whether the second application on the second screen device is associated with the first user account and is presenting a video. Providing the UI element may further include causing the UI element to be presented on the UI of the first application.

[0018] In another aspect of the present disclosure, a method includes determining whether a first user account identifier associated with a first application on a first screen device matches a second user account identifier associated with a second application on a second screen device. The second application is presenting a content item to a user. The content item may be a video. The method further includes providing a UI element through a UI of the first application on the first screen device, the UI element prompting the user to connect the first screen device with the second screen device. Providing the UI element may be performed in response to determining that the first user account identifier associated with the first application on the first screen device matches the second user account identifier associated with the second application on the second screen device. The method may further include receiving an indication of a user request to connect the first screen device with the second screen device through the UI element. The method further includes pairing the first screen device with the second screen device. Pairing the devices is performed in response to receiving an indication of a user request. The method further includes providing additional information associated with a video presented simultaneously on the second screen device for presentation in the user interface of the first application on the first screen device.

[0019] In some implementations, determining whether a first user account identifier associated with a first application on a first screen device matches a second user account identifier associated with a second application on a second screen device may include receiving a first message from the second screen device. The first message may include an indication that the second device is presenting a video. The first message may include the second account identifier. Determining whether the user account identifiers match may further include receiving a second message from the first screen device. The second message may include the first user account identifier. Determining whether the user account identifiers match may further include determining that a first user account associated with the first user account identifier and a second user account associated with the second user account identifier are the same user account.

[0020] In some implementations, the second message including the first user account identifier may be sent in response to a user action. The user action may be one or more of the following: the user opens the first application on the first screen device; or the user chooses to move the first application from a background mode to an active mode.

[0021] In some implementations, the method may further include determining that the user has not declined a previous prompt to connect the first screen device to the second screen device. The method may include determining that the user has not declined a previous prompt to connect the first screen device to the second screen device within a threshold time span. The method may include determining that the user has not declined a previous prompt to connect the first screen device to the second screen device during the current viewing session.

[0022] In another aspect of the present disclosure, a method includes providing a plurality of options available through a first UI of a first application of a first screen device with respect to a video presented through a second application on a second screen device, wherein the plurality of options are presented on a second UI of the second application on the second screen device. The method further includes: receiving a user selection of one of the plurality of options available on the first screen device through the second UI of the second application on the second screen device with respect to the video presented through the second application on the second screen device. The method may further include: providing a first UI element through the first UI of the first application on the first screen device, the first UI element prompting the user to connect the first screen device with the second screen device to participate in an activity associated with one or more options associated with the user selection. The method may further include: receiving an indication of a user request to connect the first screen device with the second screen device to participate in an activity associated with one of the plurality of options associated with the user selection through the first UI element. The method further includes pairing the first screen device with the second screen device. The method further includes: providing a second UI element to the user through the first UI of the first application on the first screen device to facilitate participation in an activity associated with one of the plurality of options associated with the user selection on the first screen device. In response to receiving an indication of a user request to connect the first screen device with the second screen device to participate in an activity associated with one of the plurality of options associated with the user selection, providing a second UI element and causing the devices to pair are performed.

[0023] In some implementations, the plurality of options may include one or more of: participating in a comment associated with the video; providing feedback on the video; sharing the video; participating in a live chat associated with the video; or facilitating a transaction associated with the video. Providing the first UI element on the first UI of the first screen device may include: in response to detecting a user action with respect to the first application, transmitting to the first screen device an indication of a user selection of one of the plurality of options available on the first screen device. The first application is associated with a first user account. The user action may include opening the first application or selecting to move the first application from a background mode to an active mode.

[0024] Where appropriate, optional features of one aspect may be combined with other aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Aspects and implementations of the present disclosure will be more fully understood from the detailed description given below and from the drawings of various aspects and implementations of the present disclosure, however, they should not be understood as limiting the present disclosure to specific aspects or implementations, but are only for explanation and understanding.

[0026] Figure 1An example system architecture for providing related content to multiple client devices in accordance with some embodiments is shown.

[0027] Figure 2A is an example graphical user interface (GUI) of a communication application of a client device, including prompts for a user, according to some embodiments.

[0028] Figure 2B Depicted is an example communication application GUI when a client device is connected to a second device in accordance with some embodiments.

[0029] Figure 2C Depicted is an example GUI of a client device including an extended content engagement element in accordance with some embodiments.

[0030] Figure 3A An example GUI of a client device including selectable elements for customizing content engagement on a second device is depicted in accordance with some embodiments.

[0031] Figure 3B Depicted is an example GUI of a client device having on-screen engagement elements associated with a presented content item in accordance with some embodiments.

[0032] Figure 4A Depicted is a flow diagram of a method for promoting user engagement associated with a content item in accordance with some embodiments.

[0033] Figure 4B A flow diagram of a method for facilitating user participation in real-time chat associated with a content item is depicted in accordance with some embodiments.

[0034] Figure 4C A flow diagram of a method for facilitating user engagement associated with a content item presented by a device associated with a user account is depicted in accordance with some embodiments.

[0035] Figure 4D Depicted is a flow diagram of a method for facilitating user participation in a selected engagement activity in accordance with some embodiments.

[0036] Figure 4E Depicted is a flow diagram of a method for facilitating a user's participation in a selected engagement activity associated with content presented using a client device, in accordance with some embodiments.

[0037] Figure 4F A diagram of a system for pairing client devices is depicted in accordance with some embodiments.

[0038] Figure 5 is a block diagram illustrating an exemplary computer system according to an implementation of the present disclosure. DETAILED DESCRIPTION

[0039] Aspects of the present disclosure relate to methods and systems for facilitating a user's participation in one or more engagement activities associated with a content item. A platform (e.g., a content sharing platform, etc.) can enable a user to access media items (e.g., video items, audio items, etc.) hosted by the platform (e.g., via a client device connected to the platform). The platform can provide access to the media items to a user's client device via a network (e.g., by transmitting the media items to the user's client device, etc.).

[0040] The media / content item may have one or more additional associated activities that may deepen the user's engagement with the content item. For example, the engagement activity may include a comment section for the content item, a real-time chat associated with the content item, etc.

[0041] In some embodiments, a user may utilize a variety of devices to engage with the content of a content platform, depending on, for example, the type of content the user wishes to consume, the time of day or week, the user's location, the amount of time the user has available, etc. Different user devices may be more or less suitable for specific tasks associated with content items. For example, a television (e.g., a smart TV) that can access a content sharing platform (e.g., through an application installed on the television) may provide a positive experience for watching video content, an IoT device may provide a positive experience for listening to audio content, etc. Deeper engagement with a content item, such as participating in an associated activity, may be better performed on a separate device, such as a device with a physical or virtual keyboard, a device with more fluid user control options, etc.

[0042] In some systems, it may be inconvenient or impossible to participate in one or more activities associated with a content item using a particular device. In one example, a user may find that their mobile phone provides a good experience for participating in a real-time chat associated with a video. However, the user may find that the mobile phone is not an ideal medium for watching videos, for example, due to the small screen size of the mobile phone. In a further example, the user may find that a game console with a TV output is a convenient way to consume content items (e.g., videos). However, it may be cumbersome or impossible to use a game console to participate in a deeper activity (e.g., it may be difficult to navigate a virtual keyboard using a game console remote control, the application executed by the game console may not allow participation in one or more activities associated with the content item, etc.).

[0043] In a conventional system, a user can consume content and participate in related activities on a separate device by navigating each separate device to the relevant content item. For example, a user can navigate to a target video using an application installed on a TV (a first device). The user can cause the video to be presented on the TV. Then, the user can open an application on a mobile phone (a second device) corresponding to the application on the TV. Then, the user can navigate the application on the mobile phone to the same content item to participate in one or more participation activities associated with the content item. In another example, a user can present an audio podcast to a user using a first device. The first device can be an audio device, such as a voice-activated IoT device. The user may not be able to participate in further participation activities through the first device, and it may be cumbersome to participate in further participation activities using the first device. The user can use a second device (e.g., a laptop) to navigate to the same content item (e.g., using an Internet browser, an installed application, etc.) and participate in participation activities (e.g., writing a review of a podcast). However, conventional systems do not provide an effective and user-friendly mechanism to pair two devices. For example, currently users usually need to ensure that the first device (e.g., a smart TV) used to present content and the second device connected to the first device are connected to the same wireless network (e.g., a WLAN network). The user must navigate the TV settings to open the pairing option. The user must open the display settings on the second device (e.g., a mobile phone) to turn on the pairing option. The user then selects the first device from the device list. The user then performs other operations to complete the pairing, such as entering the code displayed on the first device into the UI element of the second device. This multi-step process is cumbersome for the user and requires a lot of computing resources. In addition, for users watching or listening to content on the first device, traditional systems only provide a limited set of options for deeper participation through the second device. In addition, for those participation options currently available through the second device, the user must manually navigate on the second device to the content presented on the first device, which takes up extra time and additional computing resources. In addition, the connection between the devices can be initiated on a device that may be more convenient for participating in the participation activity as usual, and the presentation of the content can be transferred from one device (e.g., a mobile phone) to another device (e.g., a smart TV).

[0044] Aspects of the present disclosure can address one or more of these deficiencies of conventional systems. A platform (e.g., a content sharing platform) can host one or more media items (e.g., video items, image items, audio items, etc.) to provide to one or more users of the platform (e.g., via client devices associated with one or more users). In some embodiments, the media items can correspond to media files (e.g., video files and audio files, etc.). In other or similar embodiments, the media items can correspond to a portion of a media file (e.g., a portion or a block of a video file, an image file, an audio file, etc.).

[0045] The user may select a content item to consume (e.g., select an item corresponding to one or more digital files to be presented to the user in a user interface (UI)). The content item may be presented to the user. The presentation of the content item may be performed through a video display. The presentation of the content item may be performed through an audio device (e.g., a podcast, music, a radio program, etc.). The presentation of the content item may be performed through a combination of media (e.g., video and audio displays), such as to present pre-recorded video content, live video content, etc. The user may wish to participate in one or more engagement activities associated with the presented content item. For example, the engagement activity may include viewing or entering a comment (e.g., a text comment) associated with the content item; participating in a real-time chat associated with the content item; providing or viewing feedback associated with a video, comment, etc. (e.g., like / dislike, written or rated review, etc.); participating in a transaction associated with the content item (e.g., subscribing to a channel that provides the content item, donating to a cause associated with the content item, purchasing one or more items associated with the content item, etc.); interacting with one or more advertisements associated with the content item, etc.

[0046] In some embodiments, a user may connect or pair multiple devices to participate in various activities associated with a content item. In response to a user selecting a content item, causing a content item to be presented, etc., an element (e.g., a UI element) may be provided to the user, thereby prompting the user to connect the device. In some embodiments, the device presenting the content item may cause a message to be sent to another device, thereby initiating a connection between the devices. In some embodiments, the device presenting the content item may provide data indicating the presented content (e.g., for storage by a server associated with a content sharing platform), and another device of the user may request the data, and in response to receiving the stored data, present a UI element to the user prompting the user to request a connection device. In some embodiments, the data provided by the device presenting the content item includes information such as a user account associated with the device presenting the content, a user account logged in for the application presenting the content item, etc. It may be determined that the user account associated with the device presenting the content item is also associated with a device that can be connected to the device presenting the content item. In response to determining that the user account associated with the device presenting the content is related to the user account associated with the device to present the UI element (e.g., the same as the family with the user account, included in the family plan with the user account, etc.), the UI element may be presented. Once connected, the user can engage in one or more activities associated with the content item on one device (e.g., a video can be watched on a television) and engage in one or more other activities associated with the content item on another device (e.g., a field for performing a transaction associated with the video can be presented on a mobile phone). In some embodiments, the connection between the devices can be generated without presenting a UI element prompting the user to connect the devices. For example, the connection between the devices can be generated when the user opens an application associated with the content item on the second device.

[0047] In some embodiments, a user may select a participation activity to participate in using a UI presenting content items. The device presenting the content items may cause (e.g., by a server) to store data indicating the selected activity. Another device may request the stored data and present an element to the user prompting the user to connect the device to participate in the selected participation activity. In some embodiments, a connection between devices may be generated without presenting a prompt to the user on the second device. For example, in response to a user selecting a participation activity using a UI presenting content items, these devices may be connected when accessing a content platform on the second device, an application associated with the content, etc.

[0048] Aspects of the present disclosure produce technical advantages over traditional methods. As discussed above, traditional systems typically use a multi-step process that requires the user to (i) ensure that both devices are connected to the same wireless network, (ii) navigate the TV settings to open the pairing option, (iii) open the display settings on the phone to open the pairing option, (iv) select the first device from the device list, and (v) perform other operations to complete the pairing (e.g., enter the code displayed on the first device into the UI element of the second device). In contrast, aspects of the present disclosure can automatically determine that the user may be interested in connecting two devices (e.g., based on the user account used to watch the video on the TV matching the user account used to open the related application on the mobile device), and provide a prompt to the user, asking the user to confirm that the two devices should be connected. Then, the user only needs to watch the prompt and select the option to confirm the user's request to connect the two devices. Ultimately, a large amount of time and computing resources are saved, some device pairing restrictions are eliminated, and a simpler and more convenient mechanism for initiating device pairing is provided to the user. Furthermore, aspects of the present disclosure may include using a user's history (e.g., records of accepted or declined connection prompts, which devices have been paired with other devices, etc.) to present more informed prompts to the user (e.g., prompts that are more likely to be consistent with the user's preferences), thereby improving the user experience and saving computing resources that would otherwise be expended on generating prompts that the user does not want.

[0049] In addition, by accepting input on one device to perform on another device (e.g., selecting a participating activity to participate in), aspects of the present disclosure can present desired content and / or activities to the user faster and more easily than otherwise. The user may be consuming content items on a device that the user does not prefer for one or more participating activities. For example, the user may be watching a video on a smart TV. After consuming the content, the user may want to participate in an associated activity. For example, the user may want to contribute to a comment section associated with a content item, participate in a real-time chat associated with a content item, purchase a product referenced in a content item, etc. Aspects of the present disclosure allow the user to select a participation option using a device that presents the content, and perform an activity associated with the option on another device (e.g., a mobile phone) that is more suitable for the activity. The second device can present a prompt to invite the user to participate in the activity without any navigation by the user within the application on the device, thereby improving the user experience and saving computing resources that would otherwise be consumed by the navigation activity.

[0050] Figure 1An example system architecture 100 for providing relevant content to multiple client devices according to some embodiments is shown. The system architecture 100 includes client devices 110A and 110B (in some embodiments, more client devices may be included, such as devices 110C, 110D, etc.), one or more networks 105, a content platform system 102, and one or more electronic devices 170. The content platform system 102 includes one or more server machines 106, a two-way communication server 107, one or more data repositories 140, and may include various platforms designed to perform tasks (e.g., tasks associated with content delivery). The platform of the content platform system 102 may be hosted by one or more server machines 106. The platform of the content platform system 102 may include and / or be hosted on one or more computing devices (e.g., rack servers, router computers, server computers, personal computers, mainframe computers, laptop computers, tablet computers, desktop computers, etc.) and one or more data repositories (e.g., hard disks, memories, and databases), and may be coupled to one or more networks 105. In some embodiments, components of the content platform system 102 (e.g., server machines 106, data repositories 140, hardware associated with one or more platforms, etc.) can be directly connected to one or more networks 105. In some embodiments, one or more components of the content platform system 102 can access the network 105 through another device (e.g., a hub, a switch, etc.). The data repository 140 can be included in one or more server machines 106, including an external data storage device, etc. The platforms of the content platform system 102 can include an advertising platform 165, a social network platform 160, a recommendation platform 157, a search platform 145, and a content provider platform 120.

[0051] The one or more networks 105 may include one or more public networks (e.g., the Internet), one or more private networks (e.g., a local area network (LAN), a wide area network (WAN), one or more wired networks (e.g., Ethernet), one or more wireless networks (e.g., 802.11 networks), one or more cellular networks (e.g., a Long Term Evolution (LTE) network), routers, hubs, switches, server computers, and / or combinations thereof. In one implementation, some components of the architecture 100 are not directly connected to each other. In one implementation, the system architecture 100 includes separate networks 105.

[0052] One or more data repositories 140 may reside in a memory (e.g., random access memory), a cache, a drive (e.g., a hard drive), a flash drive, etc., and may be part of one or more database systems, one or more file systems, or other types of components or devices capable of storing data. One or more data repositories 140 may include multiple storage components (e.g., multiple drives or multiple databases) that may also span multiple computing devices (e.g., multiple server computers). A data repository may be a persistent storage device capable of storing data. A persistent storage device may be a local storage unit or a remote storage unit, an electronic storage unit (e.g., a main memory), or a similar storage unit. A persistent storage device may be a single-chip device or a collection of distributed devices.

[0053] Content items 121A-C (e.g., media content items) can be stored in one or more data repositories. The data repository can be part of one or more platforms. Examples of content items 121 can include, but are not limited to, digital videos, digital movies, animated images, digital photos, digital music, digital audio, digital video games, collaborative media content presentations, website content, social media updates, e-books, e-journals, digital audio books, web blogs, software applications, etc. Content items 121A-C can also be referred to as media items. Content items 121A-C can be pre-recorded or live. For the sake of brevity, videos can be used as examples of content items 121 throughout the document.

[0054] Content items 121A-C may be provided by a content provider. The content provider may be a user, a company, an organization, etc. The content provider may provide content item 121 as a video. The content provider may provide content item 121 including live content, for example, content item 121 may include live video, real-time chat associated with the video, etc.

[0055] Client devices 110 may include televisions, smartphones, personal digital assistants, portable media players, laptop computers, e-book readers, tablet computers, desktop computers, game consoles, set-top boxes, and the like.

[0056] The client device 110A (110B, 110C, etc.) may include a communication application 115A. A user may consume content items 121 through the communication application 115. For example, the communication application 115A may access one or more networks 105 (e.g., the Internet) through the hardware of the client device 110A to provide the content items 121 to the user. As used herein, "media", "media items", "online media items", "digital media", "digital media items", "content", "media content items", and "content items" may include electronic files that may be executed or loaded using software, firmware, and / or hardware configured to present content items. In one implementation, the communication application 115 may be an application that allows a user to compose, send, and receive content items 121 (e.g., videos) through a platform (e.g., a content sharing platform 120, a recommendation platform 157, an advertising platform 165, a social networking platform 160, and / or a search platform 145) and / or a combination of platforms and / or networks.

[0057] In some embodiments, the communication application 115 may be a social networking application, a video sharing application, a video streaming application, a video game streaming application, a photo sharing application, a chat application, or a combination of these applications. The communication application 115 associated with the client device 110 may render, display, present, and / or play one or more content items 121 to one or more users. For example, the communication applications 115A and 115B may provide user interfaces 116A and 116B (e.g., graphical user interfaces) to be displayed on the endpoint devices 110A and 110B for receiving and / or playing video content. In some embodiments, the communication applications 115A and 115B are related applications that are each associated with (and managed by) the content platform 102 or the content providing platform 120, provide some overlapping features, and are designed to support different types of client devices 110A and 110B (e.g., mobile phone type and TV type), respectively.

[0058] In some embodiments, communication applications 115A-B may include content viewers 113A-B and interactive components 114A-B. User interfaces 116A-B may display content viewers 113A-B and interactive components 114A-B. Interactive component 114 may allow a user to interact with content, interact with a platform of content platform system 102, and the like. In some embodiments, interactive component 114 may include a search component, for example, a user may utilize a field to search for a target content item 121, a target content channel (e.g., channel A125), a content item 121 associated with a target topic, and the like. In some embodiments, the search component may provide a virtual keyboard to the user to facilitate user input. In some embodiments, multiple content viewers 113 and / or interactive components 114 may be associated with a user interface, communication application, client device, and the like. For example, multiple content items may be displayed to a user at one time. In some embodiments, multiple interactive components 114 may be associated with content item 121. For example, a video may have associated commenting and / or real-time chat features, feedback mechanisms (e.g., like / dislike buttons, thumbs up / down, etc.), review mechanisms (e.g., written reviews of content, rated reviews of content, etc.), transaction options (e.g., channel subscriptions, donations, ancillary product purchases, etc.), etc. In some implementations, the application 115 is a web browser that can access, retrieve, present, and / or navigate content (e.g., web pages, such as hypertext markup language (HTML) pages, digital media items, etc.), and may include an interactive component 114 and a content viewer 113, which may be an embedded media player embedded in a user interface 116 (e.g., a web page associated with viewing content) provided by the content providing platform 120. Alternatively, the application 115 is not a web browser, but is a standalone application (e.g., a mobile application, a desktop application, a game console application, a television application, etc.) downloaded from a platform (e.g., the content providing platform 120, the recommendation platform 157, the advertising platform 165, the social networking platform 160, or the search platform 145) or pre-installed on the client device 110. Standalone application 115 may provide user interface 116, including content viewer 113 (e.g., embedded media player) and interactive component 114. It should be appreciated that components and elements associated with client device 110B (e.g., communication application 115B, user interface 116B, etc.) may have features similar to those described as exemplary features of components and elements associated with client device 110A.

[0059] Electronic device 170 may be any suitable electronic device capable of communicating input to client device 110B. For example, electronic device 170 may include a remote control, a game controller, etc. Electronic device 170 may include one or more directional input devices, such as arrow keys, a directional stick, etc. Electronic device 170 may transmit input to client device 110B for processing by one or more processors associated with client device 110B.

[0060] In some embodiments, the client device 110 can present different user experiences to the user. For example, the client device 110A can be a first screen device having features that facilitate easy user interaction and / or engagement with the presented content. For example, the client device 110A can be a mobile device including touch screen navigation and / or a virtual keyboard, such as a smartphone, a tablet computer, or a laptop computer, a desktop computer including a cursor control device (e.g., a mouse) and a keyboard, etc. The client device 110B can be a second screen device (including a device coupled to a screen, such as a game console) having features that facilitate convenient content consumption, for example, the client device 110B can be a smart TV, a TV plug-in, a digital media streaming device, a game console, etc., with a communication application 115B installed. As an example scenario, client device 110A may be a smartphone with a mobile application 115A that provides a user interface 116A including a content viewer 113A and an interactive component 114A, and client device 110B may be a television (e.g., a smart TV) with a television application 116B (e.g., an application suitable for use with a smart TV, a media streaming device, etc.) that provides a user interface 116B including a content viewer 113B and an interactive component 114B. One device (e.g., client device 110B) may provide a more convenient content consumption experience, while another device (e.g., client device 110A) may provide a richer environment for deeper interaction with content, such as viewing and adding comments, liking and sharing comments, liking and sharing media content, participating in real-time chats, performing transactions, etc.

[0061] In some embodiments, the server machine 106 includes a content engagement manager 150 that initiates pairing of multiple client devices to facilitate user participation in content engagement activities on one client device relative to content presented on another client device. Specifically, the content engagement manager 150 can instruct the client device 110A and the client device 110B to form a communication link with the two-way communication server 107. For example, a communication link can be established between the client device 110A and the client device 110B so that the first device is paired with the second device. In some embodiments, the communication link can allow a user request input through one device to affect an action performed by another device. For example, a first client device (e.g., client device 110A) can provide access to media controls (e.g., play / pause, skip, media queue, etc.), while a second client device (e.g., client device 110B) displays media content, including modifying the presentation of the media based on user input received through the first client device 110A.

[0062] In some embodiments, a connection may be established between two client devices. The connection between the devices may facilitate a richer user experience of interacting with content (e.g., content item 121). For example, content may be viewed on a device (e.g., client device 110B) that is optimized for content consumption (e.g., a video may be viewed on a TV through an app, through a streaming media device, through a game console, etc.). Client device 110B may communicate with a server (e.g., content engagement manager 150 of server machine 106) and identify the content being presented by client device 110B. In some embodiments, server machine 106 may store data indicating communications received from client device 110B, such as an identifier of a user account. Client device 110B may cause server machine 106 to store additional data (e.g., by sending the data to server machine 106). The additional data may include, for example, an indication of the content item 121 being presented, an indication of the network client device 110B is connected to, an indication of the physical location of client device 110B (e.g., through location services), and the like. In some embodiments, the client device 110B may direct the user to open the communication application 115A on the client device 110A (e.g., through the user interface 116B of the client device 110B). In some embodiments, the client device 110A may send a request to the content platform system 102 (e.g., the content engagement manager 150 of the server machine 106). The request may include a request for information about the media being presented by another device. The request may be sent by the client device 110A in response to one or more triggers, such as when the communication application 115A is opened, when the application 115A is activated from the background, when the user interacts (e.g., through a connection request UI element), along with other requests (e.g., a search request, a video viewing request, etc.), etc. In some embodiments, the content engagement manager 150 may determine whether there is an indication that the user may be interested in or benefit from connecting the client device 110A and the client device 110B, for example, the content platform system 102 may check a memory (e.g., stored in a data repository 140, associated with the server machine 106, etc.) to find an indication that the connection between the devices may benefit or interest the user. For example, the read data may include data indicating one or more similarities between devices (e.g., a user is more likely to want to connect devices logged into the same user account, devices connected to the same network, devices in nearby locations, etc.), one or more past actions (e.g., past history of connecting these devices, past history of users associated with connecting these or other devices, past history of users declining prompts to connect devices, etc.), etc. In some embodiments, it may be determined (e.g., by content engagement manager 150 of server machine 106) whether a user is likely to be interested in or benefit from connecting a device.In some embodiments, a prompt to connect the devices may be displayed on client device 110A (e.g., via user interface 116A of communication application 115A). In some embodiments, the prompt may be displayed in response to content engagement manager 150 determining that both devices are associated with the same user account (e.g., both devices' applications are logged into the same user account). Figure 2A Discussion Example Prompts. In some embodiments, a prompt may provide a mechanism to confirm that the same user is associated with both devices, for example, a UI element including a code may be displayed on the second screen device, and the prompt displayed on the first screen device may include a field for entering the code.

[0063] In some embodiments, the user may indicate the features they want to interact with on one client device, and may utilize the features presented on another client device. For example, the user may be watching content (e.g., video) on a client device 110B (e.g., a television, a television connection device, etc.). The client device 110B may be preferred by the user for viewing content, but may not be optimized for further interaction (e.g., typing comments or typing a username on a remote control, a game console controller, etc. to share content may be cumbersome). In some embodiments, the user interface 116B of the client device 110B may display options for interacting with features associated with the displayed content, such as options for interacting with a comment section or real-time chat associated with the video, options for performing transactions associated with the video (e.g., subscribing to a channel associated with the video, donating to a content provider or related charity, purchasing products through an affiliate link, etc.), etc. In some embodiments, the user interface 116B may prompt the user to access the interactive content using another device (e.g., client device 110A). In some embodiments, the client device 110B may provide an indication of a request for the user to access the content (e.g., for storage by the server machine 106). The user may interact with the client device 110A, e.g., by opening the communication application 115A, by activating the communication application 115A from the background, by interacting with a UI element of the communication application 115A, etc. The client device 110A may send a request to the content platform system 102 for information associated with content displayed on another device. The content platform system 102 may send a message to the client device 110A including information indicating that the user wishes to view interactive content, which information is received via the user interface 116B of the client device 110B. The client device 110A may display (e.g., via the user interface 116A) a prompt proposing that the user connect devices, view the requested interactive content, etc.

[0064] In some embodiments, the communication application 115 installed on the client device 110 can be associated with a user account, for example, a user can log into an account on the client device 110. In some embodiments, multiple client devices 110 can be associated with the same client account. In some embodiments, a communication link between client devices can be generated (e.g., via the two-way communication server 107) in response to the client devices being associated with the same user account.

[0065] In some embodiments, the client device 110 may include one or more data repositories. The data repositories may include commands (e.g., instructions that cause operations when executed by a processing device) to render a UI (e.g., user interface 116). The instructions may include commands to render content components and interactive components.

[0066] In some embodiments, one or more server machines 106 may include computing devices such as rack servers, router computers, server computers, personal computers, mainframe computers, laptop computers, tablet computers, desktop computers, etc., and may be coupled to one or more networks 105. Server machines 106 may be stand-alone devices or part of any platform (e.g., content provision platform 120, social networking platform 160, etc.).

[0067] The social networking platform 160 may provide an online social networking service. The social networking platform 160 may provide a communication application 115 for users to create profiles and perform activities using their profiles. Activities may include updating profiles, exchanging messages with other users, evaluating (e.g., liking, commenting, sharing, recommending) status updates, photos, videos, etc., and receiving notifications associated with other user activities.

[0068] The recommendation platform 157 can be used to generate and provide content recommendations (e.g., articles, videos, posts, news, games, etc.). Recommendations can be based on search history, content consumption history, followed / subscribed channel content, linked profiles (e.g., friend lists), popular content, etc. The search platform 145 can be used to allow users to query one or more data repositories 140 and / or one or more platforms and receive query results. The advertising platform 165 can be used to provide video advertisements.

[0069] The content providing platform 120 may be used to provide access to content items 121 to one or more users and / or provide content items 121 to one or more users. For example, the content providing platform 120 may allow users to consume, upload, download, and / or search for content items 121. In another example, the content providing platform 120 may allow users to evaluate content items 121, such as to approve ("like"), disapprove, recommend, share, rate, and / or comment on content items 121. In another example, the content providing platform 120 may allow users to edit content items 121. The content providing platform 120 may also include a website (e.g., one or more web pages) and / or one or more applications (e.g., communication applications 115), which may be used to provide access to content items 121 to one or more users. For example, the client device 110A may use the communication application 115A to access the content items 121. The content providing platform 120 may include any type of content delivery network that provides access to the content items 121.

[0070] The content providing platform 120 may include a plurality of channels (e.g., channel A 125, channel B 126, etc.). A channel may be a collection of content available from a common source, a collection of content with a common topic or theme, etc. The data content may be digital content selected by a user, digital content provided by a user, digital content uploaded by a user, digital content selected by a content provider, digital content selected by a broadcaster, etc. For example, channel A 125 may include two videos (e.g., content items 121A-B). A channel may be associated with an owner, who may be a user who can perform actions on the channel. The content may be one or more content items 121. The data content of a channel may be pre-recorded content, live content, etc. Although a channel is described as one implementation of a content providing platform, implementations of the present disclosure are not limited to content sharing platforms that provide content items 121 through a channel model.

[0071] In implementations of the present disclosure, a "user" may be represented as a single individual. However, other implementations of the present disclosure encompass "users" that are entities controlled by a group of users and / or automated sources. For example, a group of individual users united as a community in a social network may be considered a "user." In another example, an automated consumer may be an automated ingest pipeline, such as a topic channel, for one or more platforms, one or more content items, and the like.

[0072] In addition to the above description, controls may be provided to the user, which allow the user to make a choice about whether and when the system, program, or feature described herein can implement the collection of user information (e.g., information about the user's social network, social actions, or activities, occupation, user preferences, or the user's current location) and whether to send content or communications from the server to the user. In addition, before storing or using certain data, it may be processed in one or more ways to remove personally identifiable information. For example, the user's identity may be processed so that the user's personally identifiable information cannot be determined, or the user's geographic location for which location information is obtained may be generalized (such as to the city, zip code, or state level) so that the user's specific location cannot be determined. Therefore, the user can control what information is collected about the user, how the information is used, and what information is provided to the user.

[0073] According to some embodiments, Figure 2A is an example graphical user interface (GUI) of the communication application 216A of the client device 210A (e.g., Figure 1 In some embodiments, the client device 210A may receive an indication (e.g., from the server machine 106) that the prompt 220 is to be displayed for the user. In some embodiments, the client device 210A may receive an indication (e.g., from the server machine 106) that the prompt 220 is to be displayed for the user. In some embodiments, the client device 210A may respond to receiving an indication that the client device 210A sends a prompt to, for example, a server machine 106 via a network. Figure 1 The prompt 220 is displayed in response to a request of the content platform system 102. In some embodiments, the prompt 220 can be displayed to the user in response to determining (eg, by the server machine 106) that the user can benefit from connecting two or more devices.

[0074] UI 116A may include one or more UI elements. In some embodiments, prompt 220 may replace a rendered component that may include other UI elements in a portion of the screen space of device 210A, for example, prompt 220 may appear on the "top" of UI 216A (e.g., covering a portion thereof) in a transparent, translucent, or opaque form. Example UI 116A includes a first content item indicator 212 (e.g., a video thumbnail, a UI element for presenting a content item, etc.), first content item information 214 (e.g., a title, description, etc.), and a second content item indicator 218 (e.g., a second video thumbnail). Any other appropriate UI elements may be included in UI 116A, for example, additional interactive components (e.g., comments, like buttons, affiliated product links, donation links, etc.), additional social components, additional control components (e.g., UI elements for accessing user profiles, settings, etc.), etc.

[0075] Prompt 220 may include query 222, accept UI element 224, and reject UI element 226. Query 222 may be text-based, visual, graphical, etc. Query 222 may provide information associated with a pending connection request to the user. Query 222 may include additional information displayed to the user, such as an identifier of the device to be connected (e.g., the address of the device, a device name selected by the user, etc.), an identifier of a network associated with the device to be connected, an identifier of a user account associated with the device to be connected, information associated with a content item displayed on the device to be connected (e.g., a content item title, a thumbnail, etc.), a field for entering a code or password, etc. Accept UI element 224 and / or reject UI element 226 may be, for example, a button, an icon, a checkbox, a drop-down list, etc.

[0076] When a user interacts with (e.g., activates or selects) accepting element 224, a connection between client device 210A and another device can be generated. For example, the other client device can be a device that displays content items, such as a television, a digital media streaming device, a game console, etc. A first connection can be generated between a two-way communication server and client device 210A in response to an interaction with accepting element 224, and a second connection can be generated between the two-way communication server and a client device to be connected to device 210A. The two client devices can then communicate, for example, information can be transferred between the two devices regularly, periodically, upon user interaction, etc. In conjunction with Figure 2B An exemplary UI associated with a connected device is discussed. In some embodiments, data associated with the accepted connection can be saved, for example, by server machine 106. The data associated with the accepted connection can include an identifier of the connected device, a context identifier (e.g., time of day, content displayed during the connection, etc.), a user account identifier, etc. The data can be saved, for example, by server machine 106.

[0077] When the user interacts with the rejection element 226, the pending connection between the client device 210A and the other device may be terminated. In some embodiments, the data associated with the rejected connection may be, for example, Figure 1 The server machine 106 stores the information. In some embodiments, presenting the prompt 220 to the user may be performed in light of previous connection activity, for example, in light of previous user interactions with the connection prompt, interactions with the connection prompt acceptance element, interactions with the connection prompt rejection element, etc.

[0078] In some embodiments, prompt 220 may be directed to a specific action. In some embodiments, a user may select a specific participation option on a second device (e.g., a device other than client device 210A, such as a television associated with the same user account as client device 210A). For example, the second device may be displaying a content item to the user, and the user may navigate to a specific participation prompt (such as a comment section) using the UI of the second device. In some embodiments, a signal indicating the user's selection may be sent to client device 110A. Prompt 220 may reflect the user selection, for example, query 222 may ask the user whether he or she is willing to use client device 210A to read / contribute to the comment section associated with the content presented by the second device. Prompt 220 may also include any other information discussed above, such as a user ID, information associated with the device to be connected, information associated with the content item presented by the device to be connected, and the like.

[0079] Figure 2B An example communication application graphical user interface (GUI) 216B (eg, Figure 1 UI 116A or client device 110A). UI 216B may include content item element 230, content delivery control element 232, and content engagement element 234. The arrangement and functionality of these elements may be performed by more or fewer UI elements, and UI 216B may provide more or fewer functions. The functionality described herein associated with one UI element may be performed by another UI element and still be within the scope of the present disclosure.

[0080] The content item element 230 may include an indication to display the content on one or more linked devices (e.g., multiple screens in multiple rooms may display content on devices connected to the client device 210B). The content item element 230 may include a thumbnail, a preview, a title, associated information (e.g., channel owner name, topic or theme, playlist name, etc.), etc. The content delivery control element 232 may include playback controls (e.g., play / pause, skip, etc.), as well as other content delivery control elements such as a viewing queue, a search function, etc. The content delivery control element 232 may be used to adjust the presentation of content on another device (e.g., a smart TV).

[0081] The content participation element 234 may include one or more sub-elements that facilitate participation in one or more content items. For example, the content participation element 234 may include sub-elements associated with a comment section associated with a content item, a channel subscription option, other transaction options, feedback / content evaluation options (e.g., like / dislike buttons), etc. In some embodiments, the content participation element 234 may include one or more sub-elements (e.g., in the form of buttons, icons, check boxes, drop-down lists, text fields, etc.) that allow participation in a corresponding participation mechanism, for example, a user may select a comment, feedback option, etc., and then the UI 216B may display a view configured to facilitate participation in the selected mechanism (e.g., a comment section of a real-time chat window may be displayed in full screen). In some embodiments, a type of content participation may be selected on a different device (e.g., a screen device associated with the same user account as the client device 210B), and the content participation element 234 may navigate to the selected participation mechanism in response to a selection on another device.

[0082] Figure 2C An example UI 216C of a client device 210C is depicted in accordance with some embodiments (e.g., Figure 1 116A of client device 110A), including an expanded content engagement element 242. UI 216C includes content item element 240 and content engagement element 242. In some embodiments, when client device 210C is paired (e.g., connected) to a second client device, client device 210C may display UI 216C. Content item element 240 may provide one or more indications of content items being presented, for example, on a second paired device. Content item element 240 may include a content item title, an image associated with the content item (e.g., a thumbnail), and the like. Content engagement element 242 may display an interface for further engaging with the content (e.g., associated with content item element 240). For example, content engagement element 242 may present a comment section, a description of the content, a live chat, one or more transaction options, and the like. In some embodiments, content engagement items displayed via content engagement element 242 may be selected in response to user input. A user may, for example, select Figure 2B The content participation element 234 indicates the user's intention to participate in a particular participation option. The option (e.g., a comment section, a real-time chat, etc.) can be displayed in the expanded content participation element 242. In some embodiments, the user can indicate the user's intention to participate in the participation option through a UI displayed on a second device (e.g., a client device paired with the client device 210C). FIG. 3A to FIG. 3B Selecting a participation option through a UI on a second device is discussed in greater detail.

[0083] Figure 3AAn example UI 316A of a client device 310A is depicted in accordance with some embodiments (e.g., Figure 1 The UI 116B of the client device 110B of the second device includes selectable elements for customizing content engagement on the second device. The UI 316A may include a content display element 302. The content display element 302 may be configured to provide (e.g., present or play) a content item (e.g., Figure 1 The UI 316A may include engagement elements 304A-C (e.g., buttons, icons, check boxes, fields, etc.). For example, engagement element 304A may provide an option to participate in comments associated with content displayed by content display element 302. Engagement element 304B may provide an option to participate in social network operations associated with the content (e.g., share a video, post a video to a user profile, etc.). Engagement element 304C may provide an option to perform a transaction (e.g., pay to subscribe to a content channel, donate to an organization associated with the content, etc.). Alternative engagement elements may include real-time chat, video descriptions, related videos / playlists, etc. In some embodiments, the number and / or arrangement of engagement elements may vary. Figure 3A The difference shown in .

[0084] In some embodiments, content engagement element 304 may be displayed overlaying content display element 302, e.g., upon receiving a signal from a control device (e.g., a television remote control), one or more engagement options may be displayed over the content presented by client device 310A (e.g., as an overlay UI element in a transparent, semi-transparent, or non-transparent form). In some embodiments, content engagement element 304 may be displayed in a different arrangement, e.g., the content display element may be reduced in size and content engagement element 304 may be displayed in a different portion of the screen of client device 310A, the display of client device 310A may be updated to show content engagement element 304 instead of display element 302 (e.g., UI 316A may scroll content display element 302 off screen to display content engagement element 304), etc.

[0085] In some embodiments, the user can navigate to and / or select one of the engagement elements 304 of UI 316A, e.g., using arrow keys on a television remote control, using an analog stick of a game console controller, etc. Upon selecting the engagement element, a prompt may be displayed on UI 316A instructing the user to access a device installed on another device (e.g., Figure 1In some embodiments, the client device 310A provides (e.g., for storage by the server machine 106) data indicating the user selection (e.g., of the engagement element 304A). A signal indicating the stored data may be transmitted to another client device to facilitate engagement with the selected content, e.g., upon opening the application on the other client device, the other client device may query the server machine 106 for data associated with the user selection, and the client device may display a prompt in the UI requesting the user to connect the two devices, use the second device to engage with the selected content, etc. In some embodiments, the prompt to connect the device may be provided without the user selecting the engagement option. In some embodiments, based on the user selection through the UI 316A, the prompt to connect the device may be updated to a prompt to participate in the content engagement activity (e.g., using text such as "Connect your devices to view comments?," "Connect your devices to share with friends?," "Connect your devices to subscribe to the channel?," etc.). In some embodiments, the devices can be connected without displaying a prompt on the second client device, for example, in response to a user selection of an engagement element and user interaction with the second device (e.g., opening an application associated with the content on the second device), a connection between the devices can be generated.

[0086] Figure 3B An example UI 316B of a client device 310B with on-screen engagement elements associated with a presented content item is depicted in accordance with some embodiments (eg, Figure 1 The UI 316B may include a content display element 320 for presenting content (e.g., a video) to the user. The UI 316B may further include an engagement element 325 that may display additional information to the user. An application of the client device 310B associated with the UI 316B may determine the type of view (e.g., arrangement of elements, included elements, etc.) presented to the user based on the type of content, the user's selection, the content provider's selection (e.g., a channel owner), the type of engagement available for the content, etc. For example, the content display element 320 may display a live video. The engagement element 325 may display a real-time chat related to the live video.

[0087] In some embodiments, the client device 310B may be configured for viewing content, for example, the client device 310B may be a television in a user's home. A device configured for viewing content may not be an efficient tool for further engagement with the content—for example, using a television remote to type to interact with a live chat or comment may be cumbersome. A device configured for convenient interaction (e.g., a device with a physical or virtual keyboard) may not be the preferred device for displaying and / or viewing content—for example, a user may prefer to watch a video on a television rather than a mobile phone.

[0088] In some embodiments, a user may select a participation element 325 using UI 316B of client device 310B. For example, a user may select a live chat to accompany a live video using a television remote control, a game console remote control, etc. In response to a user selection of the participation element 325, client device 310B may facilitate user participation in a selected participation mode (e.g., a mode displayed by participation element 325, such as live chat) through a second client device. Client device 310B may cause a prompt to connect the two devices to be displayed on the second client device. Client device 310B may cause a prompt to participate in the selected participation mode (e.g., "Connect your devices to participate in live chat?") to be displayed on the second client device. Client device 310B may display instructions for the user through UI 316B. For example, client device 310B may display instructions for the user to open an application on the second client device. Client device 310B may cause data to be stored in a server in response to a user selection of the participation element. The stored data may include, for example, a user account identifier, an identifier of the content displayed by the client device 310B, an identifier of the participation method selected by the user, and the like. The second client device may send a request to the server for data associated with the client device 310B (e.g., in response to the user opening an application on the second client device). The second client device may receive data indicating a request to connect the device, a request to display a participation element, and the like, and a device pairing operation may begin. In some embodiments, the device may be connected without displaying a prompt on the second client device. For example, when the user selects the participation element 325, the client device 310B may display instructions to enable the user to open an application associated with the presented content on the second device. In response to the user opening the application, the device may generate a connection, for example, and a device pairing operation may begin. The device pairing operation may include ensuring that the two devices are associated with the same user account, sending and receiving messages indicating the presented content and / or device connection history, and the like.

[0089] Figure 4AA flow chart of a method 400A for promoting user engagement associated with a content item according to some embodiments is depicted. The method 400A is performed by processing logic, which may include hardware (circuitry, dedicated logic, etc.), software (such as running on a general purpose computer system or a dedicated machine), or a combination of both. In one implementation, the method is performed by Figure 1 The server 106 (e.g., the content participation manager 150) executes, while in some other implementations, Figure 4A One or more boxes can be Figure 1 The communication application 115A and / or the communication application 115B are executed.

[0090] Throughout Figure 4A The references and associated descriptions in are for video. Similar methods can be applied to various other types of content items (e.g., image content, audio content, etc.), and for clarity, video is used as an exemplary embodiment. At box 402, processing logic provides a UI element that prompts a user to connect a first screen device to a second screen device. The UI element is presented through the UI of the first application of the first screen device. The second screen device is presenting a video to the user through the second application. In some embodiments, the first and second applications are related applications that are each associated with (and managed by) a content platform, provide some overlapping features, and are designed to support different types of user devices (e.g., mobile phone type and TV type).

[0091] In some embodiments, providing a UI element can be performed in response to detecting a user action, prompting the user to connect a screen device (e.g., a device integrated with a screen, such as a smart TV, a smart phone, a tablet computer, etc.; a device that outputs to a screen for display, such as a personal computer, a game console, a digital media streaming device, etc.). The user operation can be for a first application. The user action can be an action that causes the first screen device to communicate with a server associated with the first application, such as opening an application, selecting an application from a list of open applications to move the application from a background mode to an active mode, searching for or selecting a content item using the first application, selecting a content participation option using the first application, etc. In response to the detected user action, providing a UI element can be further performed in response to determining whether the second application on the second screen device is associated with the first user account. Providing a UI element can further include causing a UI element to be presented on the UI of the first application prompting the user to connect the two screen devices.

[0092] In some embodiments, a previous user interaction with a UI element that prompts the user to connect the device can be used to determine whether to provide a UI element that prompts the user to connect the first screen device to the second screen device. For example, the UI element that prompts the user to connect the two screen devices may have been previously rejected by the user (e.g., identified by a user account associated with one or more applications). In some embodiments, in view of the rejection, the prompt may not be provided to the user. In some embodiments, the prompt may not be provided to the user until a threshold duration has passed, a threshold number of opportunities that may trigger the presentation of the UI element have passed, etc. In some embodiments, each viewing session allows only one prompt to connect the device to the user (e.g., a UI element that displays the prompt). For example, the second screen device can store data identifying the current viewing session. For example, a unique viewing session identifier can be assigned to the current viewing session. The viewing session can be associated with opening a second application, selecting content to be presented, selecting a playlist of content to be presented, etc. The first device can only provide a UI element that prompts the user to connect in each viewing session, as recorded by the viewing session identifier (e.g., a viewing session identifier can be provided to the first device, and it is determined whether a prompt was previously provided during the viewing session associated with the identifier, and the server can determine whether to send instructions to the first device in response to the viewing session identifier, etc.).

[0093] At block 404, processing logic receives an indication of a user request to connect the first screen device to the second screen device via a UI element. In some embodiments, the UI element may present elements for interaction to the user, such as a "connect" button and a "don't connect" button. In some embodiments, the UI element may be displayed via a first application of the first screen device.

[0094] At block 406, processing logic causes the first screen device to pair with the second screen device. In response to receiving an indication of a user request to connect the first screen device with the second screen device, pairing is performed. In some embodiments, pairing the first screen device with the second screen device may include connecting the first screen device with a server (e.g., Figure 1 A first connection is generated between the two-way communication server 107 of the first screen device, and a second connection is generated between the second screen device and the server. The connection with the two-way communication server can enable messages to be passed back and forth between the two screen devices. In some embodiments, one device may affect the actions performed by another device. For example, a UI element can be provided for the first screen device to change the playback of the video presented on the second screen device (e.g., pause, skip, queue next, etc.). As another example, the second screen device can be used to select a participation option, which is then displayed on the UI of the first screen device.

[0095] At box 408, the processing logic provides one or more comments provided by one or more users for the video presented simultaneously on the second screen device for presentation in the UI of the first application of the first screen device. The processing logic may identify one or more comments provided by the user (e.g., by querying a server associated with the video) for display. In some embodiments, the UI of the first application may provide a field for receiving user input. For example, the UI of the first application may provide a field for the user to type his own comments associated with the video displayed on the second screen device. In some embodiments, the first UI may present a mechanism for providing feedback on the presented content item (e.g., a "like" and / or "dislike" button). In some embodiments, the feedback mechanism may express user agreement or disagreement. In some embodiments, the UI of the first application may present a mechanism for providing feedback related to the comments associated with the presented content item, for example, a mechanism for the user to indicate agreement or disagreement with the comment, comment set, etc. Indications of user interaction (e.g., comments, feedback, etc.) may be displayed on the first screen device and / or the second screen device. For example, a user may enter a comment on a video presented on a smart TV on a mobile device, and the comment may be visible in the comment section displayed on the smart TV.

[0096] In some embodiments, one or more devices used in methods similar to methods 400A-E may not be screen devices. For example, a device similar to the second screen device of method 400A may be an audio device, such as an Internet-connected speaker, an Internet of Things device, etc. The second audio device may present audio content, such as a podcast, an audiobook, a radio show, etc. In response to presenting the audio content to the user through the second audio device, a prompt may be presented to the user through the first device to connect the two devices, participate in a participation mechanism associated with the presented content, etc. For example, the first device may be a smartphone, and the user may be facilitated to participate in a comment section associated with the presented audio content by utilizing a virtual keyboard of the smartphone.

[0097] Figure 4B A flow chart of a method 400B for facilitating user participation in a real-time chat associated with a content item is depicted according to some embodiments. The method 400B is performed by processing logic, which may include hardware (circuitry, dedicated logic, etc.), software (such as running on a general-purpose computer system or a dedicated machine), or a combination of both. In one implementation, the method is performed by Figure 1 The server 106 (e.g., the content participation manager 150) executes, and in some other implementation examples, Figure 4B One or more boxes can be Figure 1 The communication application 115A and / or the communication application 115B are executed.

[0098] At box 412, processing logic provides a UI element through the UI of the first application on the first screen device, which prompts the user to connect the first screen device to the second screen device that is presenting the video to the user. The operations associated with method 400B specifically refer to videos, screen devices, etc. A person skilled in the art to which the method belongs will recognize that in some embodiments, a similar method can be implemented using devices other than screen devices (e.g., audio devices). A person skilled in the art to which the method belongs will recognize that in some embodiments, different types of content items (e.g., audio media, image media, etc.) can be presented to the user. The operations of box 412 can be similar to Figure 4A The operations of block 402 of FIG. 4 share features. In some embodiments, the presented video may be live, for example, including live video content.

[0099] In some embodiments, the second screen device may cause data associated with the presentation of a content item (e.g., a video) to be saved. The second screen device may cause the data to be saved on a server, for example, a server associated with (e.g., accessible by) a first application of the first screen device and / or a second application of the second screen device. The saved data may include, for example, an indication of the content presented, an indication of a user account associated with the second application, an identifier of a current viewing session, and the like. In response to the first screen device sending a request to the server and the first screen device receiving from the server an indication of the data to be stored by the second screen device, a UI element may be presented on the first screen device. In some embodiments, presenting a UI element to a user may be performed in response to a history of user interactions with other UI prompts, for example, a UI element prompting a user to connect the first screen device to the second screen device may not be presented to a user who has recently (e.g., within a threshold time period) rejected a connection prompt.

[0100] At block 414, processing logic receives an indication of a user request to connect the first screen device to the second screen device via a UI element. The operation of block 414 may have the same Figure 4A At block 416, processing logic pairs the first screen device with the second screen device in response to receiving an indication of a user request to connect the first screen device with the second screen device. The operation of block 416 may have similar features to those of block 404. Figure 4AThe processing logic may further identify one or more real-time chats associated with the content (e.g., live video) presented on the second screen device. A real-time chat may refer to messages provided and read by one or more users, including updating the chat display to include newly added messages. A real-time chat may be associated with real-time content, for example, a content creator may be a streaming video of a creator performing an activity, and the real-time chat may provide users with a means to interact with the creator, each other, etc. while consuming the content. A real-time chat may be associated with pre-recorded content, for example, pre-recorded content may be presented at a predetermined time, and the real-time chat may provide users, creators, etc. with a means to discuss the presented content, interact with each other, etc.

[0101] At block 418, processing logic allows the user to participate in a real-time chat between multiple other users about the video being simultaneously presented on the second screen device. The real-time chat interaction elements may be presented via the first UI of the first screen device. The operation of block 418 may be similar to Figure 4A The operation of block 408 of the real-time chat may share features. The user may be provided with an updated record of messages provided by other users for the real-time chat. The user may be provided with a method (e.g., a virtual keyboard) for providing one or more messages for the real-time chat. Messages provided by the user as part of the real-time chat may be displayed on the first screen device and / or the second screen device.

[0102] Figure 4C A flow chart of a method 400C for facilitating user engagement associated with content items presented by a device associated with an account of a user is depicted in accordance with some embodiments. The method 400C is performed by processing logic, which may include hardware (circuitry, dedicated logic, etc.), software (such as running on a general purpose computer system or a dedicated machine), or a combination of both. In one implementation, the method is performed by Figure 1 The server 106 (e.g., the content participation manager 150) executes, and in some other implementation examples, Figure 4C One or more boxes can be Figure 1 The communication application 115A and / or the communication application 115B are executed.

[0103] At block 420, processing logic determines whether a first user account identifier associated with a first application on a first screen device matches a second user account identifier associated with a second application on a second screen device. The second application is presenting a video to the user. In some embodiments, another type of device (e.g., an audio device presenting audio content) or another type of content (e.g., audio content, image content, text content, etc.) can be associated with a method similar to method 400C.

[0104] Determining that the first user account identifier and the second user account identifier match may include receiving a first message from the second screen device. The first message may include an indication that the second screen device is presenting a video. The first message may also include an indication of a user account (e.g., a second user account identifier). Determining that the first user account identifier and the second user account identifier match may further include receiving a second message from the first screen device. The second message may include a user account identifier associated with the first screen device (e.g., a first user account identifier). The processing logic may then determine that the first user account identifier and the second user account identifier are associated with the same user account. In some embodiments, the first message and / or the second message may be sent in response to a user action. For example, the first message may be sent in response to a user selecting a video to be presented on the second screen device. As another example, the second message may be sent in response to a user performing an action associated with the first application, such as opening the application or moving the application from a background mode to an active mode.

[0105] At block 422, in response to determining that the first user account identifier associated with the first application on the first screen device and the second user account identifier associated with the second application on the second screen device match, processing logic provides, through the UI of the first application on the first screen device, a UI element prompting the user to connect the first screen device with the second screen device. In some embodiments, the UI element may be presented to the user in response to the first device receiving a response to a message, e.g., a response to a second message including an indication of the user account identifier. The operations of block 422 may be similar to Figure 4A The operations of block 402 share similar features.

[0106] At block 424, processing logic receives, via the UI element, an indication of a user request to connect the first screen device with the second screen device. At block 426, in response to receiving the indication of a user request to connect the first screen device with the second screen device, processing logic causes the first screen device to pair with the second screen device. The operations of blocks 422 and 424 may be similar to Figure 4A The operations of blocks 404 and 406 share common features.

[0107] At box 428, processing logic provides additional information associated with the video simultaneously presented on the second screen device for presentation in the user interface of the first application on the first screen device. In some embodiments, multiple additional information options can be displayed through the first UI. For example, icons can be provided to navigate to comments associated with the content item, reviews, transactions related to the content item, additional content items related to the content item, written descriptions of the content item, etc. In some embodiments, the user can select a particular type of additional information on the second screen device (e.g., by navigating to an icon of the second UI), and the information (e.g., comments associated with the video) can be displayed on the first screen device in response to user input.

[0108] In some embodiments, pairing of the first and second devices can be performed without providing, by the first device, a UI element prompting the user to connect the devices. For example, in response to a user action associated with the first device, it can be determined whether the first screen device and the second screen device are associated with the same user account. The user action may include the user opening a first application on the first screen device, activating the first application from a background mode, interacting with the first UI of the first application (e.g., selecting a content item, selecting the same content item displayed on the second screen device, selecting to participate in an activity, selecting an activity associated with a content item displayed on the second device, etc.), etc. Determining that the first screen device and the second screen device are associated with the same user account may include operations similar to those described in conjunction with box 420.

[0109] Figure 4D A flow chart of a method 400D for promoting a user to participate in a selected participation activity according to some embodiments is depicted. The method 400D is performed by processing logic, which may include hardware (circuitry, dedicated logic, etc.), software (such as running on a general-purpose computer system or a dedicated machine), or a combination of both. In one implementation, the method is performed by an application of a second device (e.g., Figure 1 The communication application 115B) is executed, and in some other implementation examples, Figure 4D One or more boxes can be Figure 1 Executed by server 106 and / or communication application 115A.

[0110] At block 430, processing logic provides, through the UI of the application of the second device, an indication of an option to participate in one or more engagement activities associated with the content presented by the second device. The engagement activities may include viewing or entering comments (e.g., text comments) associated with the content; participating in a real-time chat associated with the content; providing or viewing feedback (e.g., likes / dislikes, written or rated reviews, etc.) associated with the content, comments, etc.; participating in a transaction associated with the content (e.g., subscribing to a channel that provides content items, donating to a cause associated with the content, purchasing one or more items associated with the content, etc.); interacting with one or more advertisements associated with the content, etc.

[0111] At block 432, processing logic receives, through the UI of the application on the second screen device, a user selection of an option to participate in one or more engagement activities associated with the content presented by the second device. The UI of the application of the second device may present some or all of the above engagement activities for the user to select. For example, the user may choose to view comments or participate in a real-time chat related to the content.

[0112] In response to the user's selection of one of the engagement activities, processing logic causes a UI element to be presented in the UI of the application on the first device that prompts the user to connect the first screen device with the second screen device (block 434). In some embodiments, processing logic sends a message indicating the user's selection of the engagement activity to a content platform (e.g., server 106). In response, the content platform sends a message to the application of the first device with an indication of the presentation prompt.

[0113] Figure 4E A flow chart of a method 400E for promoting a user to participate in a selected engagement activity associated with content presented using a client device is depicted in accordance with some embodiments. The method 400E is performed by processing logic, which may include hardware (circuitry, dedicated logic, etc.), software (such as running on a general purpose computer system or a dedicated machine), or a combination of both. In one implementation, the method is performed by Figure 1 The server 106 (e.g., the content participation manager 150) executes, and in some other implementation examples, Figure 4E One or more boxes can be Figure 1 The communication application 115A and / or the communication application 115B are executed.

[0114] At block 440, processing logic provides a plurality of options available through a first UI of a first application of a first screen device with respect to a video presented through a second application on a second screen device. The plurality of options are presented on a second UI of a second application on a second screen device. In some embodiments, the plurality of options may be presented in association with a content item (e.g., a video) being presented. The plurality of options may include a comment section associated with the video, feedback options (e.g., likes / dislikes, ratings / reviews, etc.), transaction options (e.g., subscribing to a channel, purchasing affiliated products, donating to an affiliated cause, etc.), and the like.

[0115] At block 442, processing logic receives, through a second UI of a second application on the second screen device, a user selection of one of a plurality of options available on the first screen device with respect to a video presented through the second application on the second screen device. In some embodiments, the user may use an electronic device (e.g., a television remote control, a game remote control, etc.) to navigate to an icon of the second UI to select an engagement activity to participate in.

[0116] At block 444, processing logic optionally provides, via a first UI of a first application on a first screen device, a first UI element that prompts a user to connect the first screen device to a second screen device to participate in an activity associated with one of a plurality of options associated with the user selection. The operations of block 444 may be associated with Figure 4A The operations of box 402 share common features. In some embodiments, the first UI element may present the user with a choice of whether to connect the two devices. In some embodiments, the first UI element may present the user with a choice of whether to participate in the selected activity. In some embodiments, the device may be connected without providing the first UI element to the user, for example, when a user action associated with the first UI is detected. For example, after receiving a user selection to participate in an activity participated in by the first device through the second UI, an indication of the user's intention to connect the device may be stored. The devices may be connected without further selection by the user, for example, in response to a user interaction with the first application, in response to determining that the first device and the second device are associated with the same user account, etc. In some embodiments, after selecting to participate in the activity through the second UI, the second UI may display a message instructing the user to open the first application on the first device. The message may indicate that the device will be connected when the application is opened.

[0117] At box 446, processing logic receives, via a first UI element, an indication of a user request to connect the first screen device with the second screen device to participate in an activity associated with one of the multiple options associated with the user selection. At box 448, in response to receiving the indication of a user request to connect the first screen device with the second screen device to participate in an activity associated with one of the multiple options associated with the user selection, processing logic causes the first screen device to pair with the second screen device and provide a second UI element to the user, via a first UI of a first application on the first screen device, to facilitate participation in the activity associated with one of the multiple options associated with the user selection on the first screen device. In some embodiments, such as in embodiments where the first UI element prompting the user to connect the devices is not displayed by the first application, operations associated with box 448 may be performed upon receiving a user selection of multiple options. In conjunction with Figure 2C A sample UI that can be used to facilitate participation in an engagement activity is discussed.

[0118] Figure 4F A diagram of a system 400F for pairing client devices according to some embodiments is depicted. The system 400F includes a first client device 450 (eg, a device that facilitates one or more engagement activities associated with a content item, Figure 1 a client device 110A, etc.), a second client device (eg, a device that facilitates consumption of the content item, Figure 1 client device 110B, etc.) and platform system 452 (e.g., Figure 1 The platform system 452 may include a platform for downloading or streaming content items, generating communication connections between devices, etc.

[0119] The user may initiate presentation of the content item via the second client device 454. The second client device 454 may transmit data associated with the user viewing session to the platform system 452, which may be saved at the platform system 452. For example, the saved data may include a user account identifier associated with an application on the second client device presenting the content item, information about the viewing session (such as a start time), information identifying the second client device, an identifier of the presented content item, and the like. In some embodiments, the second client device 454 may send a request to the platform system 452 to store viewing session information in response to a user request, such as a request to pair the second client device 454 with the first client device 450, a request to participate in an engagement activity associated with the content item, and the like. The request to store viewing session information may include one or more indications associated with such a user request. In some embodiments, the platform system 452 may prepare a pairing session ID and transmit the pairing session ID to the second client device 454 for future use in pairing with the first client device 450. In some embodiments, the pairing session ID may be transmitted at another time (e.g., before or after the platform system 452 transmits the pairing session ID to the first client device 450).

[0120] The first client device 450 may send a request to the platform system 452. The request may include a query associated with an active viewing session on another device. The platform system 452 may utilize a user account ID, a previous history (e.g., a stored device ID associated with an application of the first client device 450), network information, etc. to associate the request from the first client device 450 with the stored data associated with the second client device 454. The platform system 452 may respond to the request by providing an indication of the stored viewing session information. In some embodiments, the platform system 452 may transmit data indicating the viewing session (e.g., a start time, displayed content items, etc.). In some embodiments, the platform system 452 may transmit instructions to cause the first client device 450 to present a UI element prompting the user to connect the first client device 450 to the second client device 454. In response to receiving the transmission from the platform system 452, the first client device 450 may present the UI element to the user.

[0121] The first client device 450 may receive a user request through a UI element to connect the first client device 450 to the second client device 454. The first client device 450 may send a request to the platform system 452 to initiate a pairing session with the second client device 454. In response to receiving the request from the first client device 450, the platform system 452 may initiate an operation for connecting the client devices.

[0122] The platform system 452 may provide a pairing session ID (e.g., session tokens) to the first client device 450. The first client device 450 may transmit (e.g., via the platform system 452) a request to connect to the second client device 454 (e.g., including an indication of the pairing session ID). The second client device 454 may utilize the stored pairing session ID (e.g., as transmitted by the platform system 452) and the pairing session ID transmitted by the first client device 450 to generate a connection between the first client device 450 and the second client device 454. Generating a connection between the first client device 450 and the second client device 454 may include multiple connections, e.g., the first client device 450 may generate a connection with the platform system 452, and the second client device 454 may generate a connection with the platform system 452. Generating this connection (e.g., via the platform system 452) may facilitate the communication of messages, information, commands, etc. between the first client device 450 and the second client device 454.

[0123] In some embodiments, the pairing session ID may be provided to the second client device 454 as a later operation, e.g., providing the pairing session ID to the second client device 454 may be performed in response to the platform system 452 receiving a request to initiate a pairing session from the first client device 450. In some embodiments, the second client device 454 may initiate generating a connection between the first client device 450 and the second client device 454 (e.g., after providing the pairing session ID to the first client device 450 and the second client device 454). In some embodiments, the first client device 450 may initiate a connection with the platform system 452 (e.g., using the pairing session ID), and the second client device 454 may initiate a connection with the platform system 452 (e.g., using the pairing session ID). The connection of the first client device 450 to the platform system 452 and the connection of the second client device 454 to the platform system 452 may facilitate communication between the first client device 450 and the second client device 454.

[0124] In some embodiments, the pairing session may be initiated without displaying a prompt to the user on the first client device 450. For example,

[0125] Figure 5 is a block diagram illustrating an exemplary computer system 500 according to some embodiments. The computer system 500 may be Figure 1The server machine 106 or one of the client devices 110A-B of the embodiment of the present invention. The machine can operate in the capacity of a server or an endpoint machine in an endpoint-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine can be a television, a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular phone, a web device, a server, a network router, a switch or a bridge, a game console, a digital media streaming device, or any machine capable of executing a set of instructions (sequential instructions or other instructions) that specify actions to be taken by the machine. In addition, although only a single machine is shown, the terms "machine", "computer", "processing device", etc. should also be understood to include any collection of machines that execute one (or more) sets of instructions to perform any one or more of the methodologies discussed herein, either individually or jointly.

[0126] The example computer system 500 includes a processing device (processor) 502, a volatile memory 504 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM), such as synchronous DRAM (SDRAM), double data rate (DDR SDRAM), etc.), a static memory 506 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 516 that communicate with each other via a bus 530.

[0127] Processor 502 represents one or more general-purpose processing devices, such as a microprocessor, a central processing unit, etc. More specifically, processor 502 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor that implements other instruction sets or a processor that implements a combination of instruction sets. Processor 502 may also be one or more special-purpose processing devices, such as an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, etc. Processor 502 is configured to execute instructions 522 (e.g., for promoting a user to participate in one or more engagement activities associated with a content item) to perform the operations discussed herein.

[0128] The computer system 500 may further include a network interface device 508. The computer system 500 may also include a video display unit 510 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 512 (e.g., a keyboard and alphanumeric keypad, a motion sensing input device, a touch screen), a cursor control device 514 (e.g., a mouse), and a signal generating device 518 (e.g., a speaker).

[0129] The data storage device 516 may include a non-transitory machine-readable storage medium 524 (also a computer-readable storage medium) on which is stored one or more instruction sets 526 embodying any one or more of the methods or functions described herein (e.g., for obtaining optimized encoder parameter settings). During execution of the instructions by the computer system 500, the instructions may also reside completely or at least partially within the volatile memory 504 and / or within the processor 502, which also constitute machine-readable storage media. The instructions may further be transmitted or received over the network 520 via the network interface device 508.

[0130] Although the computer-readable storage medium 524 (machine-readable storage medium) is shown as a single medium in the exemplary implementation, the terms "computer-readable storage medium" and "machine-readable storage medium" should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) that store one or more instruction sets. The terms "computer-readable storage medium" and "machine-readable storage medium" should also be understood to include any medium that can store, encode, or carry an instruction set for execution by a machine and cause the machine to perform any one or more of the methods of the present disclosure. Therefore, the terms "computer-readable storage medium" and "machine-readable storage medium" should be understood to include, but are not limited to, solid-state memories, optical media, and magnetic media.

[0131] References throughout this specification to "one implementation" or "an implementation" mean that a particular feature, structure, or characteristic described in connection with that implementation is included in at least one implementation. Thus, the appearances of the phrase "in one implementation" or "in an implementation" in various places throughout this specification may, but do not necessarily, refer to the same implementation, depending on the circumstances. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more implementations.

[0132] To the extent that the terms "includes," "comprising," "having," "containing," variations thereof, and other similar words are used in the detailed description or claims, these terms are intended to be inclusive in a manner similar to the term "comprising" as an open transitional word and do not exclude any additional or other elements.

[0133] As used in this application, the terms "component", "module", "system", etc. are generally intended to refer to a computer-related entity, that is, hardware (e.g., circuitry), software, a combination of hardware and software, or an entity associated with an operating machine having one or more specific functions. For example, a component can be, but is not limited to, a process, a processor, an object, an executable program, an execution thread, a program, and / or a computer running on a processor (e.g., a digital signal processor). For example, both an application running on a controller and the controller can be components. One or more components can reside within a process and / or execution thread, and a component can be confined to one computer and / or distributed between two or more computers. In addition, a "device" can appear in the following forms: specially designed hardware; general-purpose hardware specialized by executing software on it that enables the hardware to perform specific functions (e.g., generating points of interest and / or descriptors); software on a computer-readable medium; or a combination thereof.

[0134] The aforementioned systems, circuits, modules, etc. have been described with respect to the interaction between several components and / or blocks. It will be appreciated that such systems, circuits, components, blocks, etc. may include those components or specified subcomponents, some of the specified components or subcomponents, and / or additional components, and according to various permutations and combinations of the aforementioned. Subcomponents may also be implemented as components (hierarchical structures) that are communicatively coupled to other components rather than included within a parent component. In addition, it should be noted that one or more components may be combined into a single component that provides aggregation functionality or may be divided into several separate subcomponents, and any one or more intermediate layers such as a management layer may be provided to communicatively couple to such subcomponents in order to provide integrated functionality. Any component described herein may also interact with one or more other components that are not specifically described herein but are known to those skilled in the art.

[0135] In addition, the words "example" or "exemplary" are used herein to mean serving as an example, instance or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be understood as being preferred or advantageous over other aspects or designs. Rather, the use of the words "example" or "exemplary" is intended to present concepts in a specific manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly seen from the context, "X adopts A or B" is intended to mean any natural inclusive arrangement. That is, if X adopts A; X adopts B; or X adopts both A and B, then "X adopts A or B" is satisfied in any of the foregoing cases. In addition, unless otherwise specified or clearly seen from the context that it is for a singular form, the articles "a" and "an" used in this application and the appended claims should generally be understood to mean "one or more".

[0136] Finally, the implementations described herein include the collection of data describing users and / or user activities. In one implementation, the data is collected only if the user consents to the collection of such data. In some implementations, the user is prompted to explicitly allow the data collection. In addition, the user can choose to participate or not participate in such data collection activities.

Claims

1. A method comprising: providing, through a user interface (UI) of a first application on a first screen device, a UI element that prompts a user to connect the first screen device to a second screen device that is presenting a video to the user; receiving, via the UI element, an indication of a user request to connect the first screen device with the second screen device; causing the first screen device to pair with the second screen device in response to receiving the indication of the user request to connect the first screen device with the second screen device; as well as One or more comments provided by one or more other users for the video concurrently presented on the second screen device are provided for presentation in the UI of the first application of the first screen device.

2. A method as claimed in claim 1, wherein when the user selects the option to view the one or more comments of the video presented on the second screen device, the UI element prompting the user to connect the first screen device with the second screen device is provided through the UI of the first application on the first screen device, wherein the UI element prompts the user to connect the first screen device with the second screen device to view the comments.

3. The method of claim 1, wherein providing, through the UI of the first application on the first screen device, the UI element prompting the user to connect the first screen device with the second screen device further comprises: detecting a user action with respect to the first application, wherein the first application is associated with a first user account; In response to the detected user action, determining whether a second application on the second screen device is associated with the first user account and is presenting the video; as well as In response to determining that the second application is associated with the first user account and is presenting the video, the UI element prompting the user to connect the first screen device with the second screen device is presented on the UI of the first application.

4. The method of claim 3, wherein the user action with respect to the first application is at least one of: The user opens the first application on the first screen device; or The user selects the first application from a list of applications open on the first screen device to move the first application from a background mode to an active mode.

5. The method of claim 3, further comprising: Prior to causing presentation on the UI of the first application the UI element prompting the user to connect the first screen device with the second screen device, determining that the user has not declined a previous prompt to connect the first screen device to the second screen device.

6. The method of claim 3, further comprising: Prior to causing presentation on the UI of the first application the UI element prompting the user to connect the first screen device with the second screen device, determining that the user has not declined a previous prompt to connect the first screen device to the second screen device during a current viewing session.

7. The method of claim 1, wherein causing the first screen device to pair with the second screen device comprises: generating a first connection between the first screen device and a server; as well as A second connection is generated between the second screen device and the server.

8. The method of claim 1, further comprising: receiving, through the UI of the first application on the first screen device, a user request to adjust the presentation of the video on the second screen device; as well as In response to the user request to adjust the presentation of the video, the presentation of the video on the second screen device is adjusted.

9. The method of claim 1, further comprising identifying a plurality of comments provided by a plurality of users with respect to the video presented on the second screen device, the plurality of comments including the one or more comments provided by the one or more other users. 10 . The method of claim 1 , further comprising receiving, through the UI of the first application of the first screen device, a new comment from the user regarding the video simultaneously presented on the second screen device.

11. The method as claimed in claim 1 further includes receiving, through the UI of the first application of the first screen device, an indication of feedback from the user regarding at least one of the one or more comments provided by the one or more other users with respect to the video simultaneously presented on the second screen device, the feedback including an indication of the user's approval or disapproval of the corresponding comment.

12. A method comprising: providing a UI element in a user interface (UI) of a first application on a first screen device, the UI element prompting a user to connect the first screen device with a second screen device that is presenting a video to the user; receiving, via the UI element, an indication of a user request to connect the first screen device with the second screen device; causing the first screen device to pair with the second screen device in response to receiving the indication of the user request to connect the first screen device with the second screen device; as well as The user is allowed to participate in a real-time chat among multiple other users regarding the video simultaneously presented on the second screen device through the first screen device.

13. The method of claim 12, wherein when the user selects the option to participate in the real-time chat between the multiple other users with respect to the video presented on the second screen device, the UI element prompting the user to connect the first screen device with the second screen device is provided through the UI of the first application on the first screen device, wherein the UI element prompts the user to connect the first screen device with the second screen device to participate in the real-time chat.

14. The method of claim 12, wherein providing the UI element in the UI of the first application on the first screen device to prompt the user to connect the first screen device with the second screen device comprises: detecting a user action with respect to the UI on the first screen device, wherein the first application is associated with a first user account; In response to the detected user action, determining whether a second application on the second screen device is associated with the first user account and is presenting the video; as well as In response to determining that the second application is associated with the first user account and is presenting the video, the UI element prompting the user to connect the first screen device with the second screen device is presented on the UI of the first application.

15. The method of claim 14, wherein the user action with respect to the UI on the first screen device is at least one of the following: The user opens the first application on the first screen device; or The user selects the first application from a list of applications open on the first screen device to move the first application from a background mode to an active mode.

16. The method of claim 12, further comprising identifying one or more real-time chats associated with the video presented on the second screen device.

17. The method of claim 12, further comprising receiving a message from the user regarding the video simultaneously presented on the second screen device through the UI of the first application of the first screen device, and including the message from the user in the real-time chat associated with the video.

18. A method comprising: determining whether a first user account identifier associated with a first application on a first screen device matches a second user account identifier associated with a second application on a second screen device, the second application presenting a video to a user; In response to determining that the first user account identifier associated with the first application on the first screen device and the second user account identifier associated with the second application on the second screen device match, providing, through a user interface (UI) of the first application on the first screen device, a UI element prompting the user to connect the first screen device with the second screen device; receiving, via the UI element, an indication of a user request to connect the first screen device with the second screen device; causing the first screen device to pair with the second screen device in response to receiving the indication of the user request to connect the first screen device with the second screen device; as well as Additional information associated with the video concurrently presented on the second screen device is provided for presentation in the user interface of the first application on the first screen device.

19. The method of claim 18, wherein determining whether a first user account identifier associated with a first application on a first screen device matches a second user account identifier associated with a second application on a second screen device comprises: A first message is received from the second screen device, wherein the first message includes: an indication that the video is being presented by the second screen device; and the second user account identifier, receiving, from the first screen device, a second message including the first user account identifier; and A determination is made that a first user account associated with the first user account identifier and a second user account associated with the second user account identifier are the same user account.

20. The method of claim 19, wherein the second message is sent in response to a user action, and wherein the user action is at least one of: The user opens the first application on the first screen device; or The user selects the first application from a list of applications open on the first screen device to move the first application from a background mode to an active mode.

21. The method of claim 19, further comprising: Before providing the UI element on the UI of the first application that prompts the user to connect the first screen device to the second screen device, determining that the user has not declined a previous prompt to connect the first screen device to the second screen device.

22. The method of claim 19, further comprising: Prior to providing the UI element on the UI of the first application prompting the user to connect the first screen device to the second screen device, determining that the user has not interacted with a previous prompt to connect the first screen device to the second screen device during a current viewing session.

23. A method comprising: providing a plurality of options available through a first user interface (UI) of a first application of a first screen device with respect to a video presented through a second application on a second screen device, wherein the plurality of options are presented on a second UI of the second application on the second screen device; receiving, through the second UI of the second application on the second screen device, a user selection of one of the plurality of options available on the first screen device with respect to the video presented through the second application on the second screen device; When receiving the user selection of the one of the plurality of options: enabling the first screen device to pair with the second screen device; as well as A first UI element is provided to the user through the first UI of the first application on the first screen device to facilitate engaging in an activity associated with the one of the plurality of options associated with the user selection on the first screen device.

24. The method of claim 23, wherein the plurality of options available through the first UI include one or more of the following: participate in the commentary associated with said video; provide feedback on said video; share said video; participate in a live chat associated with the video; or Facilitating a transaction associated with the video.

25. The method of claim 23, wherein causing the first screen device to pair with the second screen device is performed in response to: Detecting a user action with respect to the first application, wherein the user action with respect to the first application is at least one of: The user opens the first application on the first screen device; or The user selects the first application from a list of applications open on the first screen device to move the first application from a background mode to an active mode.

26. The method of claim 23, further comprising: in response to receiving the user selection of the one of the plurality of options, providing, through the first UI of the first application on the first screen device, a second UI element, the second UI element prompting a user to connect the first screen device with the second screen device to participate in the activity associated with the one of the plurality of options associated with the user selection; as well as An indication of a user request to connect the first screen device with the second screen device to participate in the activity associated with the one of the plurality of options associated with the user selection is received through the second UI element.

27. The method of claim 26, wherein providing a first UI element through the first UI of the first application on the first screen device, the first UI element prompting a user to connect the first screen device with the second screen device to participate in an activity associated with the one of the plurality of options associated with the user selection comprises: detecting a user action with respect to the first application, wherein the first application is associated with a first user account; as well as In response to the detected user action, an indication of the user selection of one of the plurality of options available on the first screen device is transmitted to the first screen device.

28. The method of claim 27, wherein the user action with respect to the first application is at least one of: The user opens the first application on the first screen device; or The user selects the first application from a list of applications open on the first screen device to move the first application from a background mode to an active mode.

Images