U.S. Pat. No. 11,794,116

The features and advantages of embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number.

DETAILED DESCRIPTION

I. Introduction

The following detailed description discloses numerous embodiments. The scope of the present patent application is not limited to the disclosed embodiments, but also encompasses combinations of the disclosed embodiments, as well as modifications to the disclosed embodiments.

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

In the discussion, unless otherwise stated, adjectives such as “substantially,” “approximately,” and “about” modifying a condition or relationship characteristic of a feature or features of an embodiment of the disclosure, are understood to mean that the condition or characteristic is defined to be within tolerances that are acceptable for operation of the embodiment for an application for which it is intended.

Furthermore, it should be understood that spatial descriptions (e.g., “above,” “below,” “up,” “left,” “right,” “down,” “top,” “bottom,” “vertical,” “horizontal,” etc.) used herein are for purposes of illustration only, and that practical implementations of the structures and drawings described herein can be spatially arranged in any orientation or manner Additionally, the drawings may not be provided to scale, and orientations or organization of elements of the drawings may vary in embodiments.

Numerous exemplary embodiments are described as follows. It is noted that any section/subsection headings provided herein are not intended to be limiting. Embodiments are described throughout this document, and any type of embodiment may be included under any section/subsection. Furthermore, embodiments disclosed in any section/subsection may be combined with any other embodiments described in the same section/subsection and/or a different section/subsection in any manner.

Section II below describes example embodiments for enhancing session participation through queue management. In particular, Section ILA describes example systems for session participation through queue management and Section ILB provides example user interface embodiments. Section III below describes example mobile device and computing device embodiments that may be used to implement features of the embodiments described herein. Section IV below describes additional examples and advantages, and Section V provides some concluding remarks.

II. Example Embodiments for Enhancing Session Participation Through Queue Management

Methods, systems, apparatuses, devices, and computer program products are provided herein for enhancing session participation through queue management. A user or a group of users may desire to play or participate in an online activity session, such as for a video stream or game, with another user or group of users where session capacity is at a premium for the given activity. That is, the number of users that wish to play or participate may exceed a maximum number of users that can participate at any given time. Therefore, because multiplayer experiences typically have a limited set of player spots, multiplayer experiences run into scenarios where there are more people wanting to play than are allowed into the experience. Whether it is playing with friends, random strangers, a game streaming audience, or it is a very important person/player (VIP) wanting to play with a community, this problem can occur. If a streamer wants to engage with their audience in play sessions as guest players, or a multiplayer game initiator wants to play a game with friends, few options are currently available to handle this overflow of participants. When a game is over, if the host/streamer wants to take a new set of guest players from their group or audience, the host/streamer has to remove all the guest players of the current game (if possible in that game), or leave the game “lobby” outright and begin the process again. This does not allow any sort of priority to be applied to the viewers/players—whoever joins first gets into the game.

By automatically queuing players who have expressed interest in session participation, and by automatically cycling through those users over a period of time and a number of sessions, the described embodiments provide for efficiently and automatically satisfying as many requests for session participation as possible. Additionally, the users waiting in queues are in an asynchronous state so they can do other things while they wait. Accordingly, the described embodiments enable efficient session setup and participation via automatic queuing of players.

For example, a session queuing service may execute on a session queuing system host (e.g., a processing system or server) that resides on a network between a session host/streamer client device (e.g., a client device of a content streamer, a content creator, a game player such as a VIP or service platform personnel, a game influencer, etc.) and client devices of other users that wish to participate in sessions of games or streams as guest players. The session queuing service is configured to automatically queue the other users, add the other users as guest players, and remove guest players for sessions of games/content streams. The session queuing service positioned between the host/streamer and user/participant client devices is enabled to receive requests from the other users to join sessions of activities (e.g., games) streamed by the streamer client device, and to automatically queue users of client devices and insert them into the sessions as guest players. In this way, the session queuing service is enabled to centrally manage session participation for any number of the other users over any number of titles by different developers in a manner that is specific to each instance of streamed content.

For instance, a user who is playing a title on a client device (e.g., a streamer/host client device) may stream their title play such that this content stream may be viewed over a network by one or more other users at respective client devices (e.g., guest client devices). Other users may be enabled to simply view the content stream, while in other cases, other users may be enabled to view and interact with the title session being streamed, e.g., during sessions which may be pre-defined or streamer-defined portions of the stream. That is, other users may join a title session of the user playing the title at the streamer client device. Likewise, users in a lobby for a multiplayer game instance created by a host may be joined by such users.

The described embodiments provide for platform level features that can work for any number of different title streams or games (e.g., “activities”), and by enabling automatic assembling of participants into sessions, benefits are provided, including improving user experiences, reducing system load for clients, reducing network traffic loads, etc. That is, a streamer/host user is enabled to post a looking for group (LFG) message that does not require the host to confirm participation applicants, putting them into a party, inviting them into a game, and then attempting to repeat the process session after session, game after game. The LFG post may be thus utilized to act as a first-in-first-out queue of players that want to participate in a session of an activity with the streamer, according to embodiments. LFG posts may also be accessible to title developers if they wish to integrate the described embodiments into their titles from the platform detailed herein. That is, the streamer/host can create a game-specific LFG that is of this type of activity. For example, when the streamer/host enters a game, an option may be provided to gather the LFG into their game lobby. Initially, a user may request to view a stream for an activity or join a group to play a multiplayer activity, such as a game, being played or initiated by the streamer/host user. The session queuing service, or alternatively a gaming/streaming service such as Xbox Live® from Microsoft Corporation of Redmond, Wash., may be configured to associate the user with a multiplayer game, video stream, or other activity by including the user in an activity group, e.g., as a guest player, a spectator of the stream, etc. Users may request participation in a session and be automatically queued. The title developer is thus enabled to pull users from the top of the queue to participate automatically in a session as guest players. If a user in the queue logs off or becomes unavailable, the described embodiments are configured to automatically remove the unavailable user from the queue. After the completion of a session, automatic removal of the guest players from the lobby/LFG may be performed, and the next set of users from the top of the queue may be pulled into a new session as guest players. The session queuing service, or alternatively a streaming service, may be configured to track when multiplayer sessions start, end, or change in between, thus providing the ability to automatically determine when the addition and/or removal of players should take place at specified moments.

Accordingly, the described platform features allow efficient and seamless queuing and cycling of players for session participation such that the streamer and participants are relieved of the burden involved with managing the process. The described embodiments may be applied to any type of streaming/session participation scenario, as well as multi-player interaction scenarios where a host player creates a game session or activity without actively streaming, that include without limitation: a scenario where a streamer wants to play with audience members, a scenario where a VIP gamer advertises game sessions in a social context and needs to queue participant users, a scenario where a game player wants to play with friends but the collection of friends exceeds the play size of the activity (i.e., so some players need to queue and wait for their turn), scenarios where gaming clubs having a large member base want to organize play sessions with multiple sessions to play in available, and/or the like.

Embodiments also allow for queuing and session management of unintegrated titles to be improved. For instance, a streamer/host for an unintegrated title is still provided access to an improved game/stream flow by using the described platform as a virtual meeting place to form parties where the streamer/host starts the process of accepting users into a party from the top of the queue. The selected users may be automatically included in a party, where the streamer/host enabled to insert the whole party into the game or activity for participation in a session. After the session ends, because the title is unintegrated, the streamer/host may perform the additional step of leaving the game lobby and starting again, and thus the action of kicking the existing guest players from the session and selecting a new set of users from the queue as guest players for a new session is accomplished with a single button click of a streamer/host user interface before repeating the party process described above.

Integration of titles with the described embodiments for enhanced session participation through queue management is virtually seamless, and the session queuing services operate as minimally opinionated services for how the users are queued. The session queuing hosts are scalable to handle very large numbers of users and session participants for different games or content streams. Queuing may be prioritized according to streamer/host preferences, e.g., based on queued users being followers, being friends, having certain in-title attributes including any type of statistic or information related to in-title performance of a user, having subscriptions, having relatively higher times spent viewing streams of the streamer/host, being enrolled in pay-to-play programs, having an amount of viewing/spectating rewards received, and/or the like.

In other words, the embodiments disclosed herein provide enhanced session participation through queue management. These and further embodiments are described in greater detail as follows.

A. Example Systems for Session Participation Through Queue Management

In embodiments, systems and devices may be configured in various ways for enhanced session participation through queue management. For instance,FIG.1is a block diagram of a queuing system100, according to embodiments. Queuing system100is configured to enable enhanced session participation through queue management, according to embodiments. As shown inFIG.1, queuing system100includes a streamer/host client device102a, a guest client device102b, a session queuing host104, and a title developer server114which may communicate with each other over a network110. It should be noted that any numbers of streamer client devices, guest client devices, and session queuing hosts, and/or title developer servers may be present in various embodiments. Additionally, any combination of the components illustrated inFIG.1may be present in queuing system100, according to embodiments.

As noted above, streamer/host client device102a, guest client device102b, and session queuing host104, as well as title developer server114, are communicatively coupled via network110. Network110may comprise any type of communication links that connect computing devices and servers such as, but not limited to, the Internet, wired or wireless networks and portions thereof, point-to-point connections, local area networks, enterprise networks, and/or the like.

Title developer server114may comprise one or more server computers or computing devices, which may include one or more distributed or “cloud-based” servers. Title developer server may be configured to enable developers to develop and/or publish titles, such as video games, interactive applications, etc. Accordingly, title developer server114, or storage associated therewith, may include one or more titles116. Title(s)116may include code or applications for executing and/or supporting execution of titles developed by a developer. Title(s)116may be provided for download to a client device, electronically, over a network as described herein, and/or may be encoded on computer readable storage media to be read/accessed by a client device, to execute a title.

Session queuing host104may comprise one or more server computers or computing devices, which may include one or more distributed or “cloud-based” servers. In embodiments, session queuing host104may be associated with, or may be a part of, a game or streaming service system or platform such as Xbox Live®. User of client devices may be authenticated for the game/streaming services or platforms, such as via a user interface (UI)112aof streamer/host client device102aand/or via a UI112bof guest client device102bvia network110, and upon authentication, streamer/host client device102amay stream content or create a multiplayer game instance, guest client device102amay view streamed content, and streamer/host client device102aand guest client device102amay join in multi-user activities such as games. Session queuing host104is configured to receive requests from client devices, such as via a user interface (UI)112aof streamer/host client device102aand/or via a UI112bof guest client device102bvia network110to add users to groups and/or queues for participation in activities and sessions thereof. For example, a streamer/host user may be playing a title and streaming live content of the title via streamer/host client device102a, while another user may be a spectator viewing the streaming live content in a virtual lobby, or otherwise, for the title at guest client device102b. In another example, the streamer/host user may be creating a multiplayer game/activity the title via streamer/host client device102a, while another user may be a spectator viewing the streaming live content in a virtual lobby, or otherwise, for the title at guest client device102b.

As illustrated, session queuing host104includes a session tracker106and a session queuing service108. It is noted that session tracker106may be located remotely from session queuing host104in embodiments, such as in a remote and/or associated system for game or streaming service system or platform (not shown for brevity and illustrative clarity) communicatively connected via network110. It is also contemplated herein that while only a single instance of session tracker106and session queuing service108are shown inFIG.1for brevity and illustrative clarity, multiple instances of these components may be present in embodiments.

Session queuing host104is configured to receive requests, at session queuing service108, to participate in a multiplayer game or a title stream from spectating/viewing users of the title, e.g., from UI112bof guest client device102b. Session queuing service108is also configured to queue the requesting users/client devices for insertion into a session of the game/stream and to insert sets of queued users into sessions of games/streams. Accordingly, session queuing service108is configured to operate as a service (e.g., an LFG service) to facilitate group formation and session participation therefor. Requests to participate in the game/title stream from spectating/viewing users may be received by session queuing service108either before or after a streamer/host user of streamer/host client device102aactivates or enables queuing. For instance, while streaming a title, the streamer/host user may note, e.g., via UI112a, that many requests are being received for spectator user participation in a session of the stream, and the queuing of spectators for insertion into a session of the game/stream may then be activated by the host/streamer user. In such cases, session queuing service108may be configured to keep track of requesting spectators and the order of their respective requests prior to being queued such that when the streamer/host enables queuing, the FIFO ordering is maintained. In one example, requesting users may be placed in the queue before queuing is activated by the streamer/host to maintain ordering when or if activation occurs, while the queue may be cleared by the streamer/host or when the stream/game ends. In some embodiments, the queuing of spectators may be enabled upon launch of the title by the streamer/host user. It is also contemplated that that option to request queuing for participation may only be provided to spectators, e.g., via UI112b, subsequent to queue activation by the streamer/host, e.g., via UI112a. In such scenarios, a notification may be provided to the spectating users via UI112b, e.g., by highlighting or activating a selectable option for requesting to join a session, by message, etc.

Session tracker106is configured to track sessions of games and content streams. That is, session tracker106is configured to monitor sessions to determine when sessions start, end, or change in between states. Session tracker106may provide indications of session states and changes thereof to session queuing service108. Accordingly, session queuing service108is configured to determine when new sessions are to begin, to provide alerts of imminent sessions, to insert sets of users into the beginning of streaming sessions as guest players, to remove or kick guest players from sessions at their completion, etc.

Session tracker106and/or session queuing service108may each be implemented in hardware or hardware combined with one or both of software and/or firmware, and may be configured to perform any functions/operations described herein for enhancing participation in online games, content streams, and/or activities through management of session tracking and automated queuing.

Streamer/host client device102aand/or guest client device102bmay be any type of computing device or computing system, including a game console (e.g., any type of Xbox™ or Xbox One™ console from Microsoft Corporation of Redmond, Wash., any type of PlayStation® console of Sony Corporation, etc.), a terminal, a personal computer, a laptop computer, a tablet device, a smart phone, etc., that may be used by users to play, stream, and/or spectate titles from title developers. Titles may be distributed by developers electronically or via computer readable storage media that may be inserted or uploaded into the described client devices for execution of the titles. As described herein, streaming and spectating users may utilize session queuing host104. Streamer/host client device102aand/or guest client device102bare configured to provide user authentication/credential information over network110to a game/streaming service system or platform, e.g., via UI112a/UI112b. Additionally, a user may utilize UI112aor UI112bfor streaming, spectating, session queuing and participation, and/or the like, as described herein. In embodiments, streamer/host client device102aand/or guest client device102bmay include a stored instance of such a UI, received from session queuing host104and/or from game/streaming service system or platform, or as a component of streamer/host client device102aand/or guest client device102b. In embodiments, UI112aand/or UI112bmay be any type of service/application UI, browser, client or electronic communication application, messaging application, portal, and/or the like. In some examples, UI112aand/or UI112bmay be a component of a title from a title developer.

It should be noted that streamer/host client device102amay be configured to operate as a guest client device like guest client device102b, and that guest client device102bmay be configured to operate as a streamer client device like streamer/host client device102a. That is, the different client devices described herein are not limited in their functionality and operation by their labels which are attributed as such only for purposes of illustration and description herein. Additionally, streamer/host client device102aand/or guest client device102bmay each be configured to play titles without streaming or spectator viewing, as will be understood by persons of skill in the art(s) having the benefit of this disclosure.

Note that as described herein, embodiments for enhancing participation in online activities through management of session tracking and automated queuing are applicable to any type of system where a game/streaming service system or platform communicates with client devices over a network. One example is where session queuing host104and/or session queuing service108are “cloud” implementations, applications, or services in a network architecture/platform. A cloud platform includes a networked set of computing resources, including servers, routers, etc., that are configurable, shareable, provide data security, and are accessible over a network such as the Internet. Cloud applications run on these computing resources, often atop operating systems that run on the resources, for entities that access the applications over the network. A cloud platform may support multi-tenancy, where cloud platform-based software services multiple tenants, with each tenant including one or more users who share common access to software services of the cloud platform. Furthermore, a cloud platform may support hypervisors implemented as hardware, software, and/or firmware that run virtual machines (emulated computer systems, including operating systems) for tenants. A hypervisor presents a virtual operating platform for tenants.

Accordingly, a session queuing host system, such as session queuing host104, may be configured in various ways for improvements and enhancements for participation in online content streams or activities through management of session tracking and automated queuing for users of streamer client devices and/or guest client devices. For example,FIG.2is a block diagram of a session queuing service host system200(“system200” herein) configured for improvements and enhancements for participation in online content streams or activities through management of session tracking and automated queuing. System200is an embodiment of queuing system100ofFIG.1. System200is described as follows.

System200includes a session queuing host202, which may be an embodiment of session queuing host104ofFIG.1, and may be any type of server computer or computing device, as mentioned elsewhere herein, or as otherwise known, including cloud-based server implementations. As shown inFIG.2, system200and session queuing host202includes one or more of a processor (“processor”)204, one or more of a memory and/or other physical storage device (“memory”)206, one or more network interfaces (“network interface”)226, and a session queuing service208that may be an embodiment of session queuing service108ofFIG.1. System200may also include a session tracker222, which may be an embodiment of session tracker106ofFIG.1described above, as well as user information224. System200may also include additional components (not shown for brevity and illustrative clarity) including, but not limited to, components and subcomponents of other systems herein, such as UI112aand/or UI112b, etc., as well as those described below with respect toFIGS.9and10, such as an operating system.

Processor204and memory206may respectively be any type of processor circuit or memory that is described herein, and/or as would be understood by a person of skill in the relevant art(s) having the benefit of this disclosure. Processor204and memory206may each respectively comprise one or more processors or memories, different types of processors or memories, remote processors or memories, and/or distributed processors or memories. Processor204comprises circuitry that is configured to execute computer program instructions such as but not limited to embodiments of session queuing service208, which may be implemented as computer program instructions for enhancement participation in online content streams or activities through management of session tracking and automated queuing, etc., as described herein. Memory206is configured to store such computer program instructions/code, as well as to store other information and data described in this disclosure including, without limitation, title information, user information, tracking information, etc.

Network interface226may be any type of wired and/or wireless network adapter, modem, etc., configured to enable system200to communicate with other devices over a network, such as communications between system200and other devices utilized in a network as described herein (e.g., streamer/host client device102a, guest client device102b, and/or title developer server114) over a network such as network110as described above with respect toFIG.1.

User information224may include, without limitation, information regarding a user, a user's account (e.g., login credentials, a user alias or handle, etc.), a user's client device, a user's network, titles played or viewed as a spectator by the user, user rewards earned, and indications of users being logged into system200or to a game/streaming service system or platform. User information224may also include criteria data such as information regarding tracked time viewing content streams, spectator participation, title events viewed during a content stream, a set of followers of the user, a set of other users the users is following, subscriptions, a set of friends of the user, memberships (e.g., club or community memberships), in-title attributes/data of the user or in-title characters of the user, and/or any other types of criteria data. In embodiments, such criteria data may be used to determine if a user for qualifies for queue prioritization.

Session queuing208includes a plurality of components for performing the techniques described herein for enhancements in session participation through queue management, e.g., as an LFG service. As shown, session queuing service208includes communicator210, an audience manager212, a queue manager214, a session manager216, application programming interfaces (APIs)218, and a UI provider220. While shown separately for illustrative clarity, in embodiments, one or more of communicator210, audience manager212, queue manager214, session manager216, APIs218, and/or UI provider220, may be combined together and/or as a part of other components of system200. In some embodiments, less than all of the components of session queuing service208illustrated inFIG.2may be included. In software implementations, one or more components of session queuing service208and/or session queuing host202may be stored in memory206and may be executed by processor204.

Communicator210is configured to receive and/or transmit electronic communications for session queuing service208of system200. For instance, communicator210is configured to receive requests from users of client devices regarding session participation, queuing activation commands, indicia of users spectating, session state information, requests for UIs, etc., as described herein, as via network interface226. Similarly, session queuing service208of system200is configured to issue, transmit, and/or provide, notifications to users, UIs, and/or the like, as described below, via communicator210.

Audience manager212may be configured to track users that are viewing streams, in lobbies of titles, are joined in groups for game participation or stream viewing, etc. For example, spectating users may be logged in to, or authenticated and online, a game/streaming service system or platform associated with session queuing service208and system200. The service system or platform may provide mechanisms for users to watch active streams, congregate in lobbies for specific games or titles, join in group rooms, and/or the like. Audience manager212may be configured users that are actively viewing streams or otherwise present with respect to a title such that only users present in this manner are eligible to be queued, and/or remain queued, for session participation.

Queue manager214may be configured to queue users for participation in game/stream sessions. Queue manager214may be configured to insert users into a queue, and remove users from a queue, based on information from audience manager, as noted above. Queue manager214may be configured to manage a FIFO queuing structure, or any other type of queuing structure, and may be configured to manage queuing for multiple titles and any number of users. When queued users are inserted into a session, queue manager214is configured to remove the users from the queue. In embodiments, queue manager214is configured to prioritize users in queues based on criteria information as described above with respect to user information224. Queue manager214may also tentatively queue users based on requests for session participation before a streamer/host user expressly activates queuing for participation in a session of a stream. In some embodiments, guest players from completed sessions that are kicked or removed by session manager216, described below, may be automatically re-queued by queue manager214.

Session manager216may be configured to insert queued users into sessions as guest players and to remove guest players from completed sessions. Session manager216may be configured to add a set of queued users to a session, e.g., at the beginning of the session, where a set of users to be inserted into a session is based on a maximum limit of concurrent participants for a session excluding the streamer/host or is based on a preference of a streamer/host user specifying a number of users in the set that is less than or equal to the maximum. In scenarios where there are fewer queued users than the maximum limit and/or the preference of the streamer/host user, the number of queued users may be inserted into the session. Session manager216may be configured to add and/or remove users/guest players from beginning and completed sessions, respectively, based on session information from session tracker222. In embodiments, session tracker222and session manager216may be included together, conceptually or otherwise, as a single component. Session manager216is configured to automatically add and/or remove queued users and/or guest players without additional, or any, inputs being provided.

API218may include one or more APIs to perform specific functions related to tracking and communications described herein. In embodiments, one or more APIs of API218may be included in, or utilized by, a component(s) of session queuing host202, such as but not limited to, session queuing service208and its subcomponents. For example, an API of APIs218may be utilized with session tracker222to communicate session states of games and content streams. Similarly, other APIs may be used to facilitate other network communications and notifications. In embodiments, notifications or alerts may be provided to spectating/viewing users as a single API call, i.e., a single message communication. In embodiments, such an API may be configured to concurrently issue communications for large numbers of spectating users, e.g., up to 100,000 spectators, or more.

UI provider220is configured to provide UIs to client devices. For example, UI provider220may be configured to provide UI112a(or a portion thereof, or content/information therefor) to streamer/host client device102aand/or to provide UI112b(or a portion thereof, or content/information therefor) to guest client device102b. Further embodiments of UI112aand UI112bare described in additional detail below.

Session queuing service208may operate in various ways to enable enhancements for participation in online content streams or activities such as multiplayer games through management of session tracking and automated queuing. For instance,FIG.3shows a flowchart300for enhancements of participation in online content streams or activities through management of session tracking and automated queuing, according to an example embodiment. Session queuing service208may operate according to flowchart300, in an embodiment. Further structural and operational examples will be apparent to persons skilled in the relevant art(s) based on the following description. Flowchart300is described as follows with respect to queuing system100ofFIG.1and system200ofFIG.2.

Flowchart300begins at step302. In step302, users are associated with an activity of a host player by including the users in an activity group. For example, audience manager212of session queuing service208inFIG.2is configured to associate users with a game or video stream of a host player by denoting the users as belonging to an activity group. Users to be grouped may include those that are authenticated with, i.e., logged in to, a game/streaming service or platform, such as an online service like Xbox Live®. The grouped users may be viewing the video stream as spectators, may be present in a lobby of the title being streamed, may be present in a group lobby to join a multiplayer game, and/or the like. In embodiments, audience manager212may store indications of users being grouped this way in memory206. Accordingly, user eligibility to be queued for participation in a session of a game or content stream can be administered so as to require users to be present in association with the game or content stream.

In step304, requests are received from at least a subset of the users in the activity group to join a session of the game/video stream as guest players, the session including participation in an activity with the host player. For instance, queue manager214ofFIG.2may be configured to receive requests to join a session of a game/video stream from the authenticated users described in step302. These users may request to join a session by selecting an option on a UI, such as UI112b, which provides a communication message to queue manager214indicating that the user wishes to join in a session. In some embodiments, less than all authenticated users may provide requests. Activities may include game play, demonstrations, virtual reality experiences, and/or the like.

In step306, the users that submitted the requests to join the session are queued. For example, queue manager214may be configured to place the requesting users in a queue. Queues may include queuing structures such as FIFO queues which may be stored in a storage such as memory206by queue manager214. In FIFO queue examples, the user that corresponds to the first received request is placed at the top, or head, of the queue—in other words, the order of the received requests corresponds to the users' placement in the queue. In embodiments, prior to queuing the requesting users, queue manager214is configured to verify that the requesting users are still present with respect to the video stream, e.g., utilizing the stored indications of grouped users from audience manager212.

In step308, a beginning of the session is determined. For instance, session manager216is configured to determine when a session is ready begin and/or when a session begins. As described above, session manager216may receive information from session tracker222. When session manager216determines that a session is ready to begin, session manager216may be configured to provide indications to queued users that will be inserted into the next session that is about to begin, or to all queued users.

In step310, a predetermined number of the queued users are automatically inserted into the session to initiate an active session. For example, session manager216is configured to automatically insert a set of queued users into the session. The number of queued users inserted into the session may be predetermined as the maximum number allowable in a session simultaneously, or as a number corresponding to the preference of the streamer/host, and in some embodiments may be one or more of the users in the queue when that number of users is less than either of the other numbers. Session manager216may be configured to automatically insert the set of queued users into the session one at a time until the specified/maximum number is reached (e.g., in a predetermined order or in an order corresponding to indications from users for participation acceptance as described herein), or the queued users of the set may be inserted at the same time or approximately the same time. When the users are inserted as guest players, the session may automatically become active. In embodiments, after insertion of the queued players, the streamer/host may activate the session via a host UI, e.g., UI112a.

By automatically inserting queued users into sessions, network traffic is reduced significantly. For example, repeating or consecutive sessions may take place seamlessly without additional communications between client devices102a/102band session queuing host202for rejoining new games/streams/groups/lobbies, selection different users to insert into the next session, etc. Furthermore, the continuity of activities enabled by the described embodiments provides for less down time in setup of activities which decreases power consumption of client devices.

Moreover, and as previously noted, the session queuing service is centrally positioned between the streamer and guest client devices, and is enabled to dynamically manage queuing and session participation based on the specific preferences of the streamer/host users, for each such user over each available title supported by a game/streaming service system or platform. In this way, the session queuing service is enabled to efficiently manage session participation and improve the content streaming system, and the users' experience thereof, for any number of users. Thus, customization for queuing management and session participation is enabled, per-title and per-streamer/host, from a centralized service.

Still further, an API of API218ofFIG.2may also be configured to issue, in real-time, one-to-many communications including alerts/notifications, to users, queued users, and/or guest players. As similarly described above, the centrally located session queuing service is configured to system performance with respect to queue management and session participation, as well as network utilization. Network traffic and load is further significantly reduced by the described embodiments as the described session queuing service is configured to issue single notifications related to queuing and session participation to all the client devices of authenticated users. That is, alerts and notices are distributed in a manner, e.g., via APIs218as noted above, that does not require individual notices to spectating users from the service, from a title, or from a streamer/host. The network traffic reduced according to the described title queuing services and systems is significant as the number of users supported for participating in games or viewing the streaming of a title, queuing, and session participation can be in the thousands to the hundreds of thousands.

After being inserted into a session, guest players may participate in an activity with the streamer/host users until the session is completed. Upon completion of a session, session queuing service208ofFIG.2is configured to automatically and seamlessly repeat the session initiation and queued user insertion.

For instance,FIG.4shows a flowchart400for enhancements of participation in online content streams or activities through management of session tracking and automated queuing, according to an example embodiment. Session queuing service208may operate according to flowchart400. Flowchart400may be a further embodiment of flowchart300ofFIG.3. Further structural and operational examples will be apparent to persons skilled in the relevant art(s) based on the following description. Flowchart400is described as follows with respect to queuing system100ofFIG.1and system200ofFIG.2.

Flowchart400begins at step402. In step402, a prior active session that occurs before the active session is tracked. For example, session manager216ofFIG.2may be configured to track a session via session tracker222, as described above. In embodiments, session manager216may receive session information from session tracker222originating from a game/streaming service system or platform such that the stream, and the session, are directly or indirectly monitored to obtain tracking information.

In step404, the completion of the prior active session is determined. For example, session manager216is configured to obtain tracking information as described above for step402. Session manager216may determine completion of sessions based on the tracking information. Session manager216is thus configured to wait to perform removal of guest players from sessions until after a prior session is determined to be complete.

In step406, all guest players of the prior active session are automatically removed based on the completion and before said automatically inserting the predetermined number of the queued users into the session. For example, session manager216may be configured to automatically remove guest players from sessions when the sessions are completed. Session manager216is thus configured to wait to perform insertion of queued users into a new session as guest players until after the removal of guest players from a prior session.

In step408, the beginning is determined based on a completion of the prior active session. For instance, as noted above, before a new session is activated, a prior session of the activity is completed. When the prior session completes, session tracker222is configured to notify session manager216. In embodiments, session tracker216may be configured to determine when to begin a new active session, e.g., via insertion of queued users as guest players, responsive to the completion of the prior active session.

In embodiments, the steps of flowchart400may be performed automatically, e.g., without inputs from a user, to seamlessly and efficiently manage session participation and flow.

Accordingly, flowchart300and flowchart400(and session queuing service208of system200) enable improvements and enhancements for participation in online content streams or activities through management of session tracking and automated queuing by having a session queuing service208configured to operate as an automatic queue manager and session manager for any number of sessions and games/streams for titles of different developers over any number of users. The embodiments provide for efficient, network traffic/load reducing notifications and integration of users into activity sessions.

FIG.5,FIG.6, andFIG.7illustrate flow diagrams according to the described embodiments.FIG.5shows a flow diagram500,FIG.6shows a flow diagram600, andFIG.7shows a flow diagram700, each being for enhancements in participation in online content streams or activities through management of session tracking and automated queuing, according to example embodiments. For illustration, the described flow diagrams are associated with respect to the embodiments described above. Session queuing service208may operate according to flow diagram500, flow diagram600, and/or flow diagram700. Flow diagram500, flow diagram600, and/or flow diagram700may be further embodiments of flowchart300ofFIG.3and/or flowchart400ofFIG.4. Further structural and operational examples will be apparent to persons skilled in the relevant art(s) based on the following description.

Flow diagram500ofFIG.5is described as follows with respect to queuing system100ofFIG.1and system200ofFIG.2and to a streamer client device, such as streamer/host client device102aofFIG.1.

A host launches a multiplayer title at step502, e.g., via streamer/host client device102a, which the host desires to play with other users. In the context of the example illustrated in flow diagram500, the host is described with respect to a host/audience model where the host is streaming their play to an audience of users such as users of guest client devices102b. A multiplayer (MP) service stream (or game session) is created at step504responsive to step502, e.g., by a game/streaming service system or platform configured to stream the title or host multiplayer game sessions. At, or approximately at, the same time, a persisted connection506, e.g., a WebSocket connection as illustrated, to session tracker222is created (and operates as a real time activity (RTA) service instance in this context) which is kept up-to-date on changes to and states of the session. Session tracker222, acting as an RTA service instance, may operate as a publish/subscribe model service where subscribers receive pushed updates on items in real-/near-real-time.

The host then begins broadcasting, e.g., via the platform, from streamer/host client device102aat step508. The host (or streamer in this case) may then decide to create an auto play LFG process at step510, which will continually pull in new audience members who want to play after each streaming session, as described for the embodiments herein. Details512for the LFG process may be auto-filled or customized to include without limitation, the number of users to add to sessions (i.e., user slots), duration of sessions, prioritizing audience members who are subscribers, followers, active in chat, etc., and/or the like. Details512may be default options and/or customized via a UI, such as UI112a(described further below). Creation of the auto play LFG at step512causes session queuing service to create the LFG process which may be provided to users via a UI, such as UI112b(described further below). Additionally, visibility options may allow for the users of the audience to be the only users able to view the LFG process, in embodiments.

Turning now toFIG.6and flow diagram600, this example embodiment is described with respect to a guest client device, such as guest client device102bofFIG.1. Flow diagram600is also described with respect to flow diagram500ofFIG.5, e.g., as a client-side illustration that coincides with flow diagram500.

A stream viewer (or a user generally) may watch a streamer's/host's broadcast or content stream (or join a multiplayer game session) of a title at step602via a client device, such as guest client device102b. For instance, a stream that is broadcast in step508of flow diagram500may be viewed. The user may view the stream in a lobby or other online location provided by a game/streaming service system or platform (shown inFIG.7below) from which the stream is broadcast. The streamer/host may enable an auto play LFG process for the audience, as in step510of flow diagram500. For example, in an interactive UI, such as UI112aofFIG.1, the streamer/host enables a selectable option for the audience users to activate, e.g., UI112b, to participate in an activity or session of the stream with the streamer/host. The viewer requests to be in the session queue in step604.

Upon receiving requests from the users, the platform may provide user metadata to the session queuing service in step606for any queue prioritization that is to be performed. This metadata may include criteria data described herein that may be stored with user information224ofFIG.2. When a user is successfully added to the session queue in step608, e.g., by session queueing service208as described above, the queued user may have a persistent connection, e.g., a WebSocket connection as illustrated, to session tracker222established in step610to keep the queued user up-to-date on their place in the queue and other updates on the LFG process.

RegardingFIG.7and flow diagram700, this example embodiment is described with respect to a session queuing system, such as queuing system100ofFIG.1and/or system200. Flow diagram700is also described with respect to flow diagram500ofFIG.5and flow diagram600ofFIG.6, e.g., as a system level illustration that coincides with these flow diagrams.

When the streamer/host at streamer/host client device102ahas a sufficient amount of interest in the auto play LFG, or when one or more other users are queued, the streamer/host may begin the process of selecting queued users, at one or more guest client devices102b, for insertion into a session by activating an object to begin on their UI at step702, e.g., UI112aofFIG.1. This activation causes a corresponding notification to be provided to session queueing service208to begin selecting the top-most user in the queue and attempting to fill the game session at step704, e.g., via queue manager214. In some embodiments, session queueing service208may begin selecting users from the queue automatically when a pre-determined number of users are queued (or after a period of time when one or more users are queued).

Session queueing service208is configured to automatically provide notifications such as WNS notifications to guest client devices102bof the selected users at step706, e.g., via session manager216. The selected users may respond to the notification by a selectable object in their UI, e.g., UI112bofFIG.1, to accept the session invite, or in other embodiments, the selected users in the queue may be provided an informational alert that they are being added to the session without additional user inputs. As each selected user in the queue accepts, they are automatically added to the game session at step708, e.g., by session manager216of session queueing service208. If a selected user declines or fails to accept the invitation notification for a predetermined period of time, session queueing service208is configured to remove that user from the queue, or alternately place that user at the end of the queue, and select the next user at the top of the queue.

Once a session has been populated according to a specified number of participants as described above, the streamer/host may initiate the session as active, while in some other embodiments, the session may be activated automatically. In either case, the session is conducted to its completion. Based on a session state tracked by session tracker222, at the completion of a session, it is determined if the game/stream has finished at step710. If the game/stream is finished, the title or session queueing service208will remove guest players from the session and disconnect the queued users in step712, e.g., by session manager216. If the game/stream is not finished, session queueing service208will remove or kick the guest players from the session, e.g., by session manager216, to free available slots in the session for new guest players and leave just the streamer/host in step714. Session tracker222is configured to relay information between session queueing service208and the MP service stream (or game session) at a game/streaming service system or platform716of available session slots in the game/stream and of the next users available in the queue. The described processes may then automatically repeat, e.g., starting selecting the next users available in the queue at step704and sending WNS game invitations to the selected users at step706.

During waiting periods while sessions are in progress, any guest players that left the game/stream may be automatically removed from the queue in embodiments, e.g., by queue manager214. No action by the streamer/host will need to take place for selecting next queued users as new guest players once the process is restarted, because of the automatic nature of the described embodiments, until the streamer/host cancels or ends the game/stream and the sessions. Additionally, the users who are stream viewers or otherwise desire to be activity participants can remain in the queue and see their place in the queue while they wait via their respective UIs.

Thus, the described session participation and queue management systems and processes enable network traffic and load to be greatly reduced for network110by reducing communications required for session setup, and power consumption of systems and devices herein is also reduced through seamless iteration of sessions enabling more efficient implementations over current solutions. Furthermore, the current state of the art lacks session participation and queue management systems that are configured and/or programmed to operate in this efficient manner.

B. Example User Interface Embodiments

Users of client devices described herein, e.g., streamer/host client device102aand/or guest client device102bas shown inFIG.1, are configured to interact with each other and with session queueing host104ofFIG.1and/or session queueing host202and session queuing service208of system200inFIG.2. Streamer/host client device102aand/or guest client device102bmay be any type of computing device or computing system, including a game console, a terminal, a personal computer, a laptop computer, a tablet device, a smart phone, etc., that may be used by users to play, stream, and/or spectate (i.e., view streams of) titles of title developers. As noted above, such devices may include UIs such as UI112aand UI112bofFIG.1. UIs described herein as well as information/content therefor, may be provided in whole or in part by the titles executed by the client devices or other systems/hosts, may be embedded in the client devices, or any combination thereof.

Turning now toFIGS.8A and8B, UIs that are respective embodiments of UI112aand UI112bare described.

InFIG.8A, a block diagram of a host UI800A is shown. Host UI800A as illustrated is a further embodiment of UI112a. Host UI800A may be a UI provided to streamers/hosts from UI provider(s)220ofFIG.2. Host UI800A is described as follows.

Host UI800A may include a game/stream play window802configured to show activities of a streamer/host as they occur during a stream or game play of a title. Host UI800A may also include configurable objects that may be selected or interacted with by a streamer/host to configure credentials. For example, a session credentials object804and a priority credentials object806are shown. Session credentials object804and/or priority credentials object806may include pull-down menus or other types of expandable interfaces that enable a streamer/host to specify and/or select credentials for implementation in the session participation and queue management embodiments described herein. Session credentials object804provides for configuring options related to user credentials for being able to join in sessions of games/streams. As an example, a streamer/host may wish to require that only her followers and friends, or only members of specific communities or groups, be allowed to join and participate in game/stream sessions. It is contemplated, however, that other characteristics/credentials of users may be specified with respect to session credentials object804. Priority credentials object806provides for configuring options related to user credentials for having priority queue placement when requesting to join and participate in sessions of games/streams. As an example, a streamer/host may wish to allow for users having a passcode provided by the streamer/host via a messaging object816, or subscribers to her streaming channel, to be placed at the top of the queue, but behind others with such characteristics/criteria already queued (i.e., ahead of those queued users without such characteristics/criteria. It is contemplated, however, that other characteristics/credentials of users may be specified with respect to priority credentials object806.

Host UI800A may also include a selectable object808, that when selected, is configured to start a LFG process, i.e., activate a session mode for a stream, to begin participating in sessions for activities with other users. In embodiments, selecting object808causes guest UI800B to display, or make active, one or more portions thereof to a user, as described below. Host UI800A may also include a representation of a queue, e.g., a queue object810, in which users are queued according to the described embodiments. Queue object810may illustrate the users queued and their location in the queue. Queue object810may also provide an indication812that denotes the queued users, or the number of queued users, that will be added to the next session (e.g., users in queue positions1and2as illustrated). In other words, in the embodiment shown, two queued users are allowed as a subset of the queued users to be added for each session for a total of three participants including the streamer/host, although other numbers for subsets of users are contemplated herein. Queue object810may illustrate other information/characteristics associated with the users in the queue, e.g., avatar images, badges, subscription indications, and/or the like. In some embodiments, a streamer/host may be enabled by host UI800A to select specific users from queue object810to be prioritized.

Host UI800A may also include a selectable object814for other actions not explicitly shown for illustrative clarity and brevity. Other actions performed upon selection of object814may include, without limitation, removing a user from queue object810, ending a session, ending a stream, beginning a session, setting limits for session participants, setting durations for sessions, displaying session information such as time remaining or session objective progress to guest UIs, and/or the like. In embodiments, selecting object808or object814may provide a list or history showing session options that have previously been implemented by the streamer/host.

InFIG.8B, a block diagram of a guest UI800B is shown. Guest UI800B as illustrated is a further embodiment of UI112b. Guest UI800B may be a UI provided to streamers/hosts from UI provider(s)220ofFIG.2. Guest UI800B may be provided upon entry to a title lobby, a group, etc., by a user. Guest UI800B is described as follows.

Guest UI800B may include a game/stream viewer window818configured to show activities of a streamer/host as they occur during a stream or game play of a title. Game/stream viewer window818may be configured to display session information such as time remaining or session objective progress. Game/stream viewer window818may be configured to show a user's participation in sessions of games/streams subsequent to being added thereto, as described herein.

Guest UI800B may include a credentials object820, a request to join object822, a queue object824, and an alert indication object828. One or more of these objects may be configured to not be displayed, or as deactivated, prior to a streamer/host activating an LFG process or sessions (e.g., via object808of host UI800A).

Credentials object820may be configured to enable a user to enter, or select in some embodiments, credentials to provide to the streamer/host for verification of a permission for the user. For instance, credentials object820may be a text field in which a user may enter a passcode provided by a streamer/host via a messaging object830. Request to join object822may be selectable by a user to cause a request to join a session to be sent, as described herein.

Queue object824may display a representation of a queue in which users are queued according to the described embodiments. Queue object824may illustrate the users queued and their location in the queue, including the user viewing guest UI800B. Queue object824may also provide an indication826that denotes the queued users, or the number of queued users, that will be added to the next session (e.g., users in queue positions1and2as illustrated). In other words, in the embodiment shown, two queued users are allowed as a subset of the queued users to be added for each session for a total of three participants including the streamer/host, although other numbers for subsets of users are contemplated herein.

Alert indication object828is configured to provide an alert indication for the initialization of an active session in which the user will participate as a guest player. Alert notifications provided by alert indication object828may include visual and/or audible notifications of any type. In embodiments, alert indication object828may be configured as a selectable object that is activated by a user to accept an invitation to join a session, as described above. For instance, when a queued user is automatically selected for inclusion in a session and a notification is automatically provided to the user as in steps704and706of flow diagram700inFIG.7described above, the user may respond to this notification to accept insertion into the session by selecting alert indication object828.

These and other functions of host UI800A and guest UI800B, as would be understood by persons of skill in the relevant art(s) having the benefit of this disclosure, may be combined with any other embodiments and features of the described systems and devices.

III. Example Mobile Device and Computing Device Embodiments

Embodiments described herein may be implemented in hardware, or hardware combined with software and/or firmware. For example, embodiments described herein may be implemented as computer program code/instructions configured to be executed in one or more processors and stored in a computer readable storage medium. Alternatively, embodiments described herein may be implemented as hardware logic/electrical circuitry.

As noted herein, the embodiments described, including queuing system100ofFIG.1, system200ofFIG.2, host UI800A ofFIG.8A, and guest UI800B ofFIG.8B, along with any components and/or subcomponents thereof, as well as the flowcharts/flow diagrams described herein and/or further examples described herein, may be implemented in hardware, or hardware with any combination of software and/or firmware, including being implemented as computer program code configured to be executed in one or more processors and stored in a computer readable storage medium, or being implemented as hardware logic/electrical circuitry, such as being implemented together in a system-on-chip (SoC), a field programmable gate array (FPGA), or an application specific integrated circuit (ASIC). A SoC may include an integrated circuit chip that includes one or more of a processor (e.g., a microcontroller, microprocessor, digital signal processor (DSP), etc.), memory, one or more communication interfaces, and/or further circuits and/or embedded firmware to perform its functions.

Embodiments described herein may be implemented in one or more computing devices similar to a mobile system and/or a computing device in stationary or mobile computer embodiments, including one or more features of mobile systems and/or computing devices described herein, as well as alternative features. The descriptions of mobile systems and computing devices provided herein are provided for purposes of illustration, and are not intended to be limiting. Embodiments may be implemented in further types of computer systems, as would be known to persons skilled in the relevant art(s).

FIG.9is a block diagram of an exemplary mobile system900that includes a mobile device902that may implement embodiments described herein. For example, mobile device902may be used to implement any system, client, or device, or components/subcomponents thereof, in the preceding sections. As shown inFIG.9, mobile device902includes a variety of optional hardware and software components. Any component in mobile device902can communicate with any other component, although not all connections are shown for ease of illustration. Mobile device902can be any of a variety of computing devices (e.g., cell phone, smart phone, handheld computer, Personal Digital Assistant (PDA), etc.) and can allow wireless two-way communications with one or more mobile communications networks904, such as a cellular or satellite network, or with a local area or wide area network.

Mobile device902can include a controller or processor910(e.g., signal processor, microprocessor, ASIC, or other control and processing logic circuitry) for performing such tasks as signal coding, data processing, input/output processing, power control, and/or other functions. An operating system912can control the allocation and usage of the components of mobile device902and provide support for one or more application programs914(also referred to as “applications” or “apps”). Application programs914may include common mobile computing applications (e.g., e-mail applications, calendars, contact managers, web browsers, messaging applications) and any other computing applications (e.g., word processing applications, mapping applications, media player applications).

Mobile device902can include memory920. Memory920can include non-removable memory922and/or removable memory924. Non-removable memory922can include RAM, ROM, flash memory, a hard disk, or other well-known memory devices or technologies. Removable memory924can include flash memory or a Subscriber Identity Module (SIM) card, which is well known in GSM communication systems, or other well-known memory devices or technologies, such as “smart cards.” Memory920can be used for storing data and/or code for running operating system912and application programs914. Example data can include web pages, text, images, sound files, video data, or other data to be sent to and/or received from one or more network servers or other devices via one or more wired or wireless networks. Memory920can be used to store a subscriber identifier, such as an International Mobile Subscriber Identity (IMSI), and an equipment identifier, such as an International Mobile Equipment Identifier (IMEI). Such identifiers can be transmitted to a network server to identify users and equipment.

A number of programs may be stored in memory920. These programs include operating system912, one or more application programs914, and other program modules and program data. Examples of such application programs or program modules may include, for example, computer program logic (e.g., computer program code or instructions) for implementing one or more of queuing system100ofFIG.1, system200ofFIG.2, host UI800A ofFIG.8A, and guest UI800B ofFIG.8B, along with any components and/or subcomponents thereof, as well as the plots and flowcharts/flow diagrams and/or further examples described herein.

Mobile device902can support one or more input devices930, such as a touch screen932, a microphone934, a camera936, a physical keyboard938and/or a trackball940and one or more output devices950, such as a speaker952and a display954. Other possible output devices (not shown) can include piezoelectric or other haptic output devices. Some devices can serve more than one input/output function. For example, touch screen932and display954can be combined in a single input/output device. Input devices930can include a Natural User Interface (NUI).

One or more wireless modems960can be coupled to antenna(s) (not shown) and can support two-way communications between processor910and external devices, as is well understood in the art. Modem960is shown generically and can include a cellular modem966for communicating with the mobile communication network904and/or other radio-based modems (e.g., Bluetooth964and/or Wi-Fi962). At least one wireless modem960is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communications within a single cellular network, between cellular networks, or between the mobile device and a public switched telephone network (PSTN).

Mobile device902can further include at least one input/output port980, a power supply982, a satellite navigation system receiver984, such as a Global Positioning System (GPS) receiver, an accelerometer986, and/or a physical connector990, which can be a USB port, IEEE 1394 (FireWire) port, and/or RS-232 port. The illustrated components of mobile device902are not required or all-inclusive, as any components can be deleted and other components can be added as would be recognized by one skilled in the art.

In an embodiment, mobile device902is configured to implement any of the above-described features of flowcharts herein. Computer program logic for performing any of the operations, steps, and/or functions described herein may be stored in memory920and executed by processor910.

FIG.10depicts an exemplary implementation of a computing device1000in which embodiments may be implemented. For example, embodiments described herein may be implemented in one or more computing devices similar to computing device1000in stationary or mobile computer embodiments, including one or more features of computing device1000and/or alternative features. The description of computing device1000provided herein is provided for purposes of illustration, and is not intended to be limiting. Embodiments may be implemented in further types of computer systems and/or game consoles, etc., as would be known to persons skilled in the relevant art(s).

As shown inFIG.10, computing device1000includes one or more processors, referred to as processor circuit1002, a system memory1004, and a bus1006that couples various system components including system memory1004to processor circuit1002. Processor circuit1002is an electrical and/or optical circuit implemented in one or more physical hardware electrical circuit device elements and/or integrated circuit devices (semiconductor material chips or dies) as a central processing unit (CPU), a microcontroller, a microprocessor, and/or other physical hardware processor circuit. Processor circuit1002may execute program code stored in a computer readable medium, such as program code of operating system1030, application programs1032, other programs1034, etc. Bus1006represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. System memory1004includes read only memory (ROM)1008and random access memory (RAM)1010. A basic input/output system1012(BIOS) is stored in ROM1008.

Computing device1000also has one or more of the following drives: a hard disk drive1014for reading from and writing to a hard disk, a magnetic disk drive1016for reading from or writing to a removable magnetic disk1018, and an optical disk drive1020for reading from or writing to a removable optical disk1022such as a CD ROM, DVD ROM, or other optical media. Hard disk drive1014, magnetic disk drive1016, and optical disk drive1020are connected to bus1006by a hard disk drive interface1024, a magnetic disk drive interface1026, and an optical drive interface1028, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computer. Although a hard disk, a removable magnetic disk and a removable optical disk are described, other types of hardware-based computer-readable storage media can be used to store data, such as flash memory cards, digital video disks, RAMs, ROMs, and other hardware storage media.

A number of program modules may be stored on the hard disk, magnetic disk, optical disk, ROM, or RAM. These programs include operating system1030, one or more application programs1032, other programs1034, and program data1036. Application programs1032or other programs1034may include, for example, computer program logic (e.g., computer program code or instructions) for implementing embodiments described herein, such as queuing system100ofFIG.1, system200ofFIG.2, host UI800A ofFIG.8A, and guest UI800B ofFIG.8B, along with any components and/or subcomponents thereof, as well as the plots and flowcharts/flow diagrams described herein and/or further examples described herein.

A user may enter commands and information into the computing device1000through input devices such as keyboard1038and pointing device1040. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, a touch screen and/or touch pad, a voice recognition system to receive voice input, a gesture recognition system to receive gesture input, or the like. These and other input devices are often connected to processor circuit1002through a serial port interface1042that is coupled to bus1006, but may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB).

A display screen1044is also connected to bus1006via an interface, such as a video adapter1046. Display screen1044may be external to, or incorporated in computing device1000. Display screen1044may display information, as well as being a user interface for receiving user commands and/or other information (e.g., by touch, finger gestures, virtual keyboard, etc.). In addition to display screen1044, computing device1000may include other peripheral output devices (not shown) such as speakers and printers.

Computing device1000is connected to a network1048(e.g., the Internet) through an adaptor or network interface1050, a modem1052, or other means for establishing communications over the network. Modem1052, which may be internal or external, may be connected to bus1006via serial port interface1042, as shown inFIG.10, or may be connected to bus1006using another interface type, including a parallel interface.

As used herein, the terms “computer program medium,” “computer-readable medium,” and “computer-readable storage medium,” etc., are used to refer to physical hardware media such as the hard disk associated with hard disk drive1014, removable magnetic disk1018, removable optical disk1022, other physical hardware media such as RAMs, ROMs, flash memory cards, digital video disks, zip disks, MEMs, nanotechnology-based storage devices, and further types of physical/tangible hardware storage media (including memory1020ofFIG.10). Such computer-readable media and/or storage media are distinguished from and non-overlapping with communication media and propagating signals (do not include communication media and propagating signals). Communication media embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wireless media such as acoustic, RF, infrared and other wireless media, as well as wired media. Embodiments are also directed to such communication media that are separate and non-overlapping with embodiments directed to computer-readable storage media.

As noted above, computer programs and modules (including application programs1032and other programs1034) may be stored on the hard disk, magnetic disk, optical disk, ROM, RAM, or other hardware storage medium. Such computer programs may also be received via network interface1050, serial port interface1042, or any other interface type. Such computer programs, when executed or loaded by an application, enable computing device1000to implement features of embodiments discussed herein. Accordingly, such computer programs represent controllers of the computing device1000.

Embodiments are also directed to computer program products comprising computer code or instructions stored on any computer-readable medium or computer-readable storage medium. Such computer program products include hard disk drives, optical disk drives, memory device packages, portable memory sticks, memory cards, and other types of physical storage hardware.

IV. Additional Example and Advantages

As described, systems and devices embodying the techniques herein may be configured and enabled in various ways to perform their respective functions. In embodiments, one or more of the steps or operations of any flowchart and/or flow diagram described herein may not be performed. Moreover, steps or operations in addition to or in lieu of those in any flowchart and/or flow diagram described herein may be performed. Further, in examples, one or more operations of any flowchart and/or flow diagram described herein may be performed out of order, in an alternate sequence, or partially (or completely) concurrently with each other or with other operations.

While embodiments described in the Sections above may be described in the context of a streamer/host user that is streaming a title being viewed by other users, e.g., in a virtual or online lobby associated with the title, the embodiments may also be applied to groups of users that “meet” in virtual or online locations, e.g., a group of friend, to play a game that is not streamed for viewing. For example, a multi-player game session that allows four or eight players to simultaneously participate may be created and hosted by a user that wishes to play with a group of friends. When the group of friends, including the host user, exceeds the number of allowed participants for the game, the embodiments described herein for management of session tracking and automated queuing are equally applicable to such scenarios.

The described embodiments improve not only the experience of users and the performance of their client devices (such as power consumption and reduced processing cycle over-burden by more efficient handling of functions by a central system), as well as the load of the network therebetween, but also improve the performance of game/streaming service systems/platforms. Computing resource utilization for title developers is also reduced (e.g., reduced development time and development processing cycles) via the seamless integration of titles described herein. Additionally, the centrally-located session queuing systems and devices herein provide dynamically configurable queue management for game/stream session participation that is customized for each specific streamer host according to their preferences and the title they are streaming. It should be noted that a “centrally-located” system may include geographically-diverse components (e.g., servers, data centers, etc.) configured to efficiently facilitate the described embodiments in different geographic regions—that is, “centrally-located” may describe the functions and implementation of the described embodiments and/or physical location of the systems. Real-time queue status updates are enabled by the described persistent connections, which also provide for the ability to automatically manage the queues without streamer/host oversight (e.g., removing users from a queue for non-responsiveness or leaving a stream/lobby). Thus, the time waiting to join a session, as well as the complexity of user interaction to join sessions, is greatly reduced by the efficient management and processing of automatic queues for session participation reducing processing requirement at the host/streamer and client devices, the service platform itself, and further reducing network traffic. That is, the managed functions of queuing users that submitted requests to join a session, determining a beginning of the session, and then automatically inserting a predetermined number of the queued users into the session to initiate an active session reduces processing of the client devices and the service platform involved and requires far fewer network communications therebetween. Additionally, determining the completion of a prior active session, and automatically removing all guest players of the prior active session based on the completion and before automatically inserting the predetermined number of the queued users into the session further increases processing efficiency for queue management as described herein and further decreases network communications. Likewise, management such as automatically re-queuing one or more removed guest players of an ended session responsive to their removal, and automatically de-queuing any of the users that leave the activity group further increase queuing efficiency improves queuing efficiency and operation which in turn positively impacts session participation.

Furthermore, the described embodiments do not exist in software implementations for improved participation in online content streams or activities through management of session tracking and automated queuing, e.g., in cloud-based implementations.

Still further, real-time queue status information is automatically provided to streamers/hosts during streaming as well as queued users without additional inputs while viewing a content stream and/or waiting for session participation via guest UIs, and users are automatically inserted into sessions from the queue at the appropriate time, e.g., when a beginning of a session is determined, thus improving the UI functionality and experience. Additionally, streamer/host users are able to view, via host UIs, the queue status as sessions automatically iterate allowing the streamer/host continuous monitoring of session participation and streaming.

It is also contemplated herein that session participation and/or performance may be linked to rewards services associated with the title streamed and/or the game/streaming service or platform used. Rewards may include, without limitation, badges, skins, in-game items, experience points, in-game unlocks, and/or the like.

The additional examples and embodiments described in this Section may be applicable to examples disclosed in any other Section or subsection of this disclosure.

A session queuing system is described herein. The session queuing system may be configured and enabled in various ways to enhance participation in online content streams or activities through management of session tracking and automated queuing, as described herein. The session queuing system includes one or more processors and one or more memories that store program code to be executed by the processor. The program code includes an audience manager, a queue manager, and a session manager. The audience manager is configured to associate users with an activity (e.g., game or video stream) of a host player by including the users in an activity group. The queue manager is configured to receive requests from at least a subset of the users in the activity group to join a session of the activity as guest players, the session including participation in an activity with the host player, and to queue the users that submitted the requests to join the session. The session manager configured to determine a beginning of the session, and to automatically insert a predetermined number of the queued users into the session to initiate an active session.

In an embodiment of the session queuing system, the session manager is configured to track a prior active session that occurs before the active session, and determine the beginning based on a completion of the prior active session.

In an embodiment of the session queuing system, the session manager is configured to determine the completion of the prior active session, and automatically remove all guest players of the prior active session based on the completion and before said automatically inserting the predetermined number of the queued users into the session.

In an embodiment of the session queuing system, the session manager is configured to provide notifications to the predetermined number of the queued the users of their insertion into the session, receive corresponding responses to the notifications, and automatically insert the predetermined number of the queued the users into the session based on the corresponding responses.

In an embodiment of the session queuing system, the queue manager is configured to perform one or more of automatically queue one or more removed guest players of an ended session responsive to their removal, automatically de-queue any of the users that leave the activity group, or prioritize queuing of a user based on a characteristic of the user.

In an embodiment of the session queuing system, the program code further includes a guest user interface (UI) provider configured to provide a guest UI to a user in the activity group, where the guest UI includes at least one of a selectable object that when activated provides a request to join the session of the video stream, a credential portion configured for verification of a permission of the user, an indication of a queue position for the user, or an alert indication for an initialization of the active session in which the user will participate as a guest player.

In an embodiment of the session queuing system, the program code further includes a host user interface (UI) provider configured to provide a host UI to the host player, the host UI including at least one of a selectable object that when activated initiates a session mode in which a guest UI is caused to be provided to a user in the activity group, a first configurable object that specifies credentials for eligible users in the activity group to join the session of the video stream, or a second configurable object that specifies credentials by which the users in the activity group are prioritized in queuing to join the session of the video stream.

A method for session queuing performed on a processing system is also described. The method enhances participation in online content streams or activities through management of session tracking and automated queuing, as described herein. The method includes receiving requests from at least a subset of users in an activity group to join a session of an activity as guest players, the session including participation in an activity with a host player, and queuing the users that submitted the requests to join the session. The method also includes determining a beginning of the session, and automatically inserting a predetermined number of the queued users into the session to initiate an active session.

In an embodiment, the method further includes tracking a prior active session that occurs before the active session, and determining the beginning based on a completion of the prior active session.

In an embodiment, the method further includes determining a completion of the prior active session, and automatically removing all guest players of the prior active session based on the completion and before said automatically inserting the predetermined number of the queued users into the session.

In an embodiment, the method further includes providing notifications to the number of the queued ones of the users for insertion into the session, receiving corresponding responses for the notifications, and automatically inserting the number of the queued ones of the users into the session based also on the corresponding responses.

In an embodiment, the method further includes at least one of automatically queuing one or more removed guest players of an ended session responsive to their removal, automatically de-queuing any of the users that leave the activity group, or prioritizing queuing of a user based on a characteristic of the user.

In an embodiment, the method further includes providing a guest user interface (UI) to each of the users in the activity group, the UI including at least one of a selectable object that when activated provides a request to join the session of the video stream, a credential portion configured for verification of a permission of the user, an indication of a queue position for a user, or an alert indication for an initialization of the active session in which the user will participate as a guest player.

In an embodiment, the method further includes providing a host user interface (UI) to the host player, the UI including at least one of a selectable object that when activated initiates a session mode in which a guest UI is caused to be provided to a user in the activity group, a first configurable object that specifies credentials for eligible users to join the session of the video stream, or a second configurable object that specifies credentials by which users are prioritized in queuing to join the session of the video stream.

A computer-readable medium having program instructions recorded thereon that, when executed by a processing device, perform a method for session queuing is also provided herein. The method enhances participation in online content streams or activities through management of session tracking and automated queuing, as described herein. The method includes associating users with an activity of a host player by including the users in an activity group, and receiving requests from at least a subset of the users in the activity group to join a session of the activity as guest players, the session including participation in an activity with the host player. The method also includes queuing the users that submitted the requests to join the session, determining a beginning of the session, and automatically inserting a predetermined number of the queued users into the session to initiate an active session.

In an embodiment of computer-readable medium, the method further includes tracking a prior active session that occurs before the active session, and determining the beginning based on a completion of the prior active session.

In an embodiment of computer-readable medium, the method further includes determining the completion of the prior active session, and automatically remove all guest players of the prior active session based on the completion and before said automatically inserting the predetermined number of the queued users into the session.

In an embodiment of computer-readable medium, the method further includes providing notifications to the number of the queued ones of the users for insertion into the session, receiving corresponding responses for the notifications, and automatically inserting the number of the queued ones of the users into the session based also on the corresponding responses.

In an embodiment of computer-readable medium, the method further includes at least one of automatically queuing one or more removed guest players of an ended session responsive to their removal, automatically de-queuing any of the users that leave the activity group, or prioritizing queuing of a user based on a characteristic of the user.

In an embodiment of computer-readable medium, the method further includes providing a guest user interface (UI) to a user in the activity group, the guest UI including at least one of a selectable object that when activated provides a request to join the session of the video stream, a credential portion configured for verification of a permission of the user, an indication of a queue position of the user, or an alert indication for an initialization of the active session in which the user will participate as a guest player. In the embodiment, the method also includes providing a host UI to the host player, the host UI including at least one of a selectable object that when activated initiates a session mode in which a guest UI is caused to be provided to each of the users in the activity group, a first configurable object that specifies credentials for eligible users in the activity group to join the session of the video stream, or a second configurable object that specifies credentials by which one or more users in the activity group are prioritized in queuing to join the session of the video stream.

V. Conclusion

While various embodiments of the disclosed subject matter have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be understood by those skilled in the relevant art(s) that various changes in form and details may be made therein without departing from the spirit and scope of the embodiments as defined in the appended claims. Accordingly, the breadth and scope of the disclosed subject matter should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.