Systems and methods for large scale near real-time display of personalized streaming platform event content

Abstract

A computer-implemented method for enabling a client device to display personalized and state-specific update content associated with a streaming platform event in near real-time as the streaming platform event undergoes state changes. For example, implementations described herein. For example, the method includes causing a client device to subscribe to a topic associated with a streaming platform event and causing the client device to prefetch state-driven metadata associated with the streaming platform event. The method then includes sending low-latency update messages indicating that the streaming platform event has undergone a state change. These update messages cause the subscribing client device to update content to reflect the state change associated with the streaming platform event. Various other methods, systems, and computer-readable media are also disclosed.

Description

[0001] Cross-references to related applications This application claims priority and the benefit of U.S. Patent Application No. 18 / 622,815, filed March 29, 2024, entitled “Systems and methods for displaying personalized streaming platform event content in near real-time at scale,” the entire contents of which are incorporated herein by reference. Background Technology

[0002] Digital content streaming has become an increasingly popular activity as viewers turn to digital content streaming platforms to watch movies and TV shows. Previously, digital content streaming was typically limited to pre-recorded content. Recently, digital content streaming platforms have evolved and now offer additional content such as interactive video games and live streaming events (e.g., events broadcast live for simultaneous, real-time viewing).

[0003] However, the rise of live streaming and interactive content has increased the need for near-simultaneous client-side updates. For example, scheduled live streaming events can be associated with visual content (e.g., selectable artwork, previews, banners) displayed to viewers via their client devices. In some implementations, digital content streaming platforms can update the content viewers see based on the current state of the live streaming event, indicating that the event is "live tomorrow," "live in 10 minutes," "live now," "program ended," etc. Due to the nature of live streaming events, it may be impossible to know in advance when any of these event states will occur.

[0004] Sending update messages about the status of live streaming events to client devices often results in spikes in computing resource consumption that are difficult to recover from. For example, within typical network communication protocols, notifying client devices of update statuses associated with streaming platform events often leads to a "thundering herd" of requests for new displayable content (e.g., updated banners, icons, badges) associated with the update status. This surge in requests often forces the streaming platform to update a large number of client devices simultaneously—resulting in slow response times and limited ability to serve personalized content. Summary of the Invention

[0005] As will be described in more detail below, this disclosure describes an implementation that enables client devices to display personalized and state-specific updates associated with a streaming platform event in near real-time as the event undergoes a state change. For example, the implementation includes: generating an update message based on a state update associated with the streaming platform event; identifying one or more subscribed devices associated with the streaming platform event; and broadcasting the update message to the one or more subscribed devices to re-render one or more prefetched user interface elements associated with the streaming platform event within the streaming platform application on the one or more subscribed devices.

[0006] In one or more implementations, the streaming platform event is a live streaming event. Additionally, some implementations include enabling one or more subscribing devices to prefetch state-specific data associated with the streaming platform event. In at least one implementation, the state-specific data associated with the streaming platform event includes coordination arrangements associated with the streaming platform event, live event user interface elements, and live event metadata.

[0007] In one or more implementations, generating update messages based on state updates includes generating messages reflecting changes in coordination arrangements associated with streaming platform events. Furthermore, in one or more implementations, the state updates associated with streaming platform events include current state metadata received from a live event monitoring service.

[0008] One or more implementations also include: storing update messages, determining when an add-on subscription device comes online during a streaming platform event, and broadcasting the update messages to the add-on subscription device to cause one or more prefetched user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the add-on subscription device.

[0009] In addition, one or more implementations include: receiving an additional state update indicating that the streaming platform event has ended, generating an additional update message based on the additional state update, and broadcasting the additional update message to one or more subscription devices to remove one or more prefetch user interface elements associated with the streaming platform event within the streaming platform application on one or more subscription devices.

[0010] Some examples described herein include a system having at least one physical processor and physical memory, the physical memory including computer-executable instructions that, when executed by the at least one physical processor, cause the at least one physical processor to perform various actions. In at least one example, the computer-executable instructions, when executed by the at least one physical processor, cause the at least one physical processor to perform actions including: generating an update message based on a state update associated with a streaming platform event; identifying one or more subscription devices associated with the streaming platform event; and broadcasting the update message to the one or more subscription devices to cause one or more prefetched user interface elements associated with the streaming platform event to be re-rendered within a streaming platform application on the one or more subscription devices.

[0011] In some examples, the methods described above are encoded as computer-readable instructions on a computer-readable medium. In one example, when executed by at least one processor of a computing device, the computer-readable instructions cause the computing device to: generate an update message based on a state update associated with a streaming platform event, identify one or more subscription devices associated with the streaming platform event, and broadcast the update message to the one or more subscription devices to cause one or more prefetched user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the one or more subscription devices.

[0012] Based on the general principles described herein, features of any of the embodiments described herein can be used in combination with each other. These and other embodiments, features, and advantages will be more fully understood upon reading the following detailed description taken in conjunction with the accompanying drawings and claims. Attached Figure Description

[0013] The accompanying drawings illustrate several exemplary embodiments and are part of the specification. These drawings, together with the following description, illustrate and explain various principles of this disclosure.

[0014] Figure 1 An overview of a network environment, based on one or more implementations, is shown, in which a near real-time system operates to enable client devices to display instantaneous and state-specific content in relation to events on a streaming media platform.

[0015] Figure 2 A flowchart is shown of a method for implementing near real-time state-driven updates of client-side content associated with streaming platform events, according to one or more implementations.

[0016] Figure 3 and Figure 4 The diagram illustrates a streaming platform user interface, including updated, state-specific user interface elements, depending on one or more implementations.

[0017] Figure 5 An overview of the prefetch phase and near real-time update phase implemented by a near real-time system, according to one or more implementation methods, is shown.

[0018] Figure 6 An overview of near real-time systems based on one or more implementations is shown.

[0019] Figure 7 A block diagram of an exemplary content distribution ecosystem is shown.

[0020] Figure 8 It shows Figure 7 A block diagram illustrating an exemplary distribution infrastructure within a content distribution ecosystem.

[0021] Figure 9 It shows Figure 8 A block diagram of an exemplary content player within a content distribution ecosystem is shown.

[0022] Throughout the accompanying drawings, the same reference numerals and descriptions indicate similar but not necessarily identical elements. While the exemplary embodiments described herein are readily adaptable to various modifications and alternatives, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, this disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims. Detailed Implementation

[0023] As mentioned above, typical streaming platform communication frameworks are not configured to adequately provide viewers' client devices with timely, personalized, and state-specific content. For example, in typical content delivery architectures, sudden state changes associated with streaming platform events (e.g., state changes associated with live streaming events that may start late, have unexpected problems, or end early) can be delivered to client devices. Due to these unexpected state changes, typical streaming platforms can push generic content updates to viewers' client devices, but this generic content lacks personalization. Instead, client devices can simultaneously request updated content specific to the new state of the streaming platform event and personalized for their viewers. This means that the streaming platform receives and attempts to respond to sudden, unexpected, and numerous simultaneous requests. These types of traffic bursts often overwhelm server resources, leading to slowdowns and bottlenecks within the streaming platform network.

[0024] In view of this, this disclosure generally relates to a system that enables a client device to display personalized and state-specific updates associated with a streaming platform event almost immediately when the event undergoes a state change. For example, as will be discussed in more detail below, the system described herein enables the client device to prefetch personalized and state-specific metadata associated with an upcoming streaming platform event (e.g., personalized display content and event scheduling for a specific language, geographic region, etc.). In one or more implementations, the system allows the client device to render streaming platform application user interface elements with personalized and state-specific display content based on the prefetched event schedule. If an unplanned state change occurs (e.g., delayed start or long event duration), the system generates a low-latency update message based on the state change and sends it to the client device, the update message causing the client device to automatically update or re-render the user interface elements according to the state change. In at least one implementation, the system enables the prefetching and broadcasting of update messages based on the client device's topic subscription.

[0025] In this way, the system avoids the "thundering herd" problem exhibited by typical network communication protocols, which leads to peak computational resource consumption and corresponding slowdowns and bottlenecks. For example, the system prefetches high-cardinality, state-driven metadata to client devices, enabling the rapid transmission and processing of unexpected state changes associated with streaming platform events. Therefore, while typical network communication protocols cause slowdowns and unexpected delays with streaming platform events, the system described herein demonstrates low-latency agility, allowing unexpected state changes to be reflected near real-time on client devices.

[0026] Based on the general principles described herein, features of any of the implementations described herein can be combined with each other. These and other implementations, features, and advantages will be more fully understood after reading the following detailed description in conjunction with the accompanying drawings and claims.

[0027] The following will be referenced Figures 1-9 A detailed description of a near real-time system is provided, which enables client devices to display instantaneous and state-specific content in relation to events on a streaming media platform. For example, Figure 1 An overview of the network environment in which the near real-time system operates is shown. Figure 2 A flowchart is shown for a method to implement near real-time state-driven updates of client-side content associated with streaming platform events. Figure 3 and Figure 4 The streaming platform user interface is shown, including updated, state-specific user interface elements. Figure 5 An overview of the prefetching phase and the near real-time update phase implemented by the near real-time system is shown. Figure 6An overview of the additional features of the near real-time system is shown. Figures 7-9 Additional details about content distribution systems (e.g., digital streaming platforms) are shown.

[0028] As mentioned above, Figure 1 An exemplary network environment 100 implementing aspects of this disclosure is shown. For example, network environment 100 includes one or more servers 112, client devices 114a, 114b, and 114c, and network 124. As further shown, the one or more servers 112 and client devices 114a-114c respectively include memories 106, 118a, 118b, and 118c, additional items 108, 120a, 120b, and 120c, and physical processors 110, 122a, 122b, and 122c.

[0029] In one or more implementations, such as Figure 1 As shown, client devices 114a-114c are devices capable of playing digital content items. For example, in some implementations, client devices 114a-114c are any of a smartphone, tablet, laptop, desktop computer, smart wearable device, virtual reality headset, etc. In at least one implementation, any of client devices 114a-114c is a set-top box device that receives streaming input from one or more servers 112 and provides streaming content to a television for playback. In one or more implementations, client devices 114a-114c are also capable of playing live streaming events originating from one or more servers 112.

[0030] like Figure 1 As further shown, the near real-time system 102 is implemented as part of a digital streaming platform 104 within memory 106 on server(s) 112. In one or more implementations, the digital streaming platform 104 includes a subscription streaming service for providing digital media content to subscribers. In one or more examples, such digital media content includes non-interactive content, such as movies and television programs, and interactive content, such as video games. In an additional example, such digital media content also includes live streaming events broadcast in real time from the digital streaming platform 104. Furthermore, the digital streaming platform 104 also provides static information, such as selectable thumbnails and menus associated with digital media items.

[0031] like Figure 1As further shown, client devices 114a-114c include digital streaming media platform applications 116a, 116b, and 116c respectively within memories 118a-118c. In some implementations, digital streaming media platform applications 116a-116c include some or all of the functionalities of the near real-time system 102. In at least one implementation, digital streaming media platform applications 116a-116c generate content requests and send these requests to the digital streaming media platform 104. In some implementations, digital streaming media platform applications 116a-116c are native applications installed on client devices 114a-114c. In an additional implementation, digital streaming media platform applications 116a-116c are accessed via a web browser installed on client devices 114a-114c.

[0032] As described above, client devices 114a-114c are communicatively coupled to server(s) 112(s) via network 124. In one or more implementations, network 124 represents any type or form of communication network, such as the Internet, and includes one or more physical connections, such as LANs, and / or wireless connections, such as WANs. In some implementations, network 124 represents a telecommunications operator network. In at least one implementation, network 124 represents a combination of networks.

[0033] Although Figure 1 The components of the exemplary network environment 100 are illustrated in one arrangement, but other arrangements are also possible. For example, in one implementation, the near real-time system 102 operates as a native application installed on any of the client devices 114a-114c. In another implementation, the near real-time system 102 operates across multiple servers. In additional implementations, the exemplary network environment 100 includes any number of client devices across any number of users, partitions, geofenced regions, countries, etc.

[0034] As mentioned above, Figure 2 This is a flowchart of an exemplary computer-implemented method 200 for implementing near real-time state-driven updates of client-side content associated with streaming media platform events. Figure 2 The steps shown can be performed by any suitable computer-executable code and / or computing system, including Figure 6 The system(s) shown. In one example, Figure 2 Each step shown can represent an algorithm whose structure includes and / or is represented by multiple sub-steps, examples of which will be provided in more detail below.

[0035] like Figure 2As shown, in step 210, the near real-time system 102 generates an update message based on state updates associated with the streaming media platform event. In one or more examples, the near real-time system 102 generates an update message that reflects near real-time changes in the live streaming event schedule prefetched by client devices subscribed to the live streaming event. Therefore, in one or more implementations, the update message indicates metadata associated with a specific state change of the live streaming event and an indication of a previous state that is now invalid. For example, a state including "starts in 5 minutes" could be invalidated by an update message indicating that the live streaming event "starts in 10 minutes".

[0036] like Figure 2 As further shown, in step 220, the near real-time system 102 identifies one or more subscribed devices associated with streaming media platform events. In one or more examples, the near real-time system 102 identifies one or more subscribed devices as client devices associated with the digital streaming media platform 104 that have subscribed to live streaming events provided by the digital streaming media platform 104. In addition to subscribing to live streaming events, the near real-time system 102 may also identify client devices that meet other characteristics, such as being located in a specific geographic area, associated with a specific membership level, having a specific device type, or being associated with a specific language.

[0037] like Figure 2 As further shown, in step 230, the near real-time system 102 broadcasts an update message to one or more subscribed devices to re-render one or more prefetched user interface elements associated with the streaming platform event within the streaming platform application on the one or more subscribed devices. For example, in one or more implementations, the near real-time system 102 causes the subscribed devices to prefetch state-driven metadata associated with the live streaming event. In one implementation, the near real-time system 102 causes the subscribed devices to prefetch this metadata in response to subscribing to a live streaming event. In one or more examples, the state-driven metadata includes state-specific user interface elements (e.g., banners, icons, badges, thumbnails, preview content). In at least one example, the state-driven metadata also includes a live event schedule for planned changes to the live event state. Therefore, the near real-time system 102 sends an update message indicating a change in the live event schedule that requires modifications to one or more user interface elements within the streaming platform display on the subscribed client devices.

[0038] To further illustrate, Figure 3 and Figure 4A streaming media platform user interface 300 is shown, which includes multiple digital content item thumbnails, such as digital content item thumbnails 302a, 302b, 302c, and 302d. In one or more implementations, the digital streaming media platform 104 causes a client device (e.g., client device 114a) to display a user interface such as the streaming media platform user interface 300 via a streaming media platform application (e.g., digital streaming media platform application 116a) installed thereon. In response to detected user interaction with the displayed digital content item thumbnails, the digital streaming media platform application 116a may update the user interface or a portion of the user interface to display additional information associated with the corresponding digital content item. In an additional implementation, in response to detected user interaction with user interface elements, the digital streaming media platform 104 may cause the client device to subscribe to one or more topics, including live streaming events, open a user profile, initiate playback of a digital content item, etc.

[0039] like Figure 3 As further shown, the digital streaming platform 104 also includes user interface elements that provide additional information associated with digital content items within the streaming platform user interface 300. For example, the digital streaming platform 104 (e.g., via the digital streaming platform application 116a) overlays user interface elements 304a and 304b onto digital content item thumbnails 302a and 302d, respectively. In one or more implementations, user interface elements 304a and 304b reflect the current state associated with the corresponding digital content. For example, user interface element 304a reflects that the digital content associated with digital content item thumbnail 302a (e.g., a live streaming event) will begin "today". Similarly, user interface element 304b reflects that the digital content associated with digital content item thumbnail 302b (e.g., another live streaming event) will begin "7 / 20".

[0040] In one or more implementations, these state-specific user interface elements are prefetched by the client device 114a along with a live event schedule that indicates when the state associated with a live streaming event should change and which user interface elements should be re-rendered in light of those state changes. However, live streaming events often experience unexpected state changes due to technical difficulties, human issues, etc. Therefore, the near real-time system 102 determines when a state change occurs and transmits that change to the client device 114a in near real-time.

[0041] like Figure 4As shown, upon receiving an update message associated with a state change, client device 114a re-renders user interface element 304a to reflect the state change. For example, near real-time system 102 causes digital streaming platform application 116a on client device 114a to re-render user interface element 304a (e.g., previously stated that the live streaming event “starts today”) to indicate an updated state (e.g., the live streaming event is now “live in 1 minute”). In one or more implementations, near real-time system 102 causes digital streaming platform application 116a to re-render user interface element 304a according to a prefetched coordination schedule associated with the live event, the prefetched coordination schedule indicating when the state of the live event changes.

[0042] In at least one implementation, near real-time system 102 generates an update message and sends it to client device 114a in response to determining that a triggering state change occurred outside of the prefetching coordination schedule (i.e., the state change is unexpected). In this implementation, near real-time system 102 uses the update message to override the prefetching coordination schedule and causes client device 114a to immediately display user interface element 304a based on the updated state. In one or more implementations, both versions of user interface element 304a are part of an original prefetch performed by client device 114a in conjunction with subscribed live streaming events, thereby allowing client device 114a to re-render user interface element 304a to display the updated state without needing to fetch the updated version of user interface element 304a from server 112 in real time.

[0043] Although Figure 3 and Figure 4 The illustration shows a near real-time system 102 incorporating live streaming events to trigger a state-driven user interface update on client device 114a. However, near real-time system 102 can also trigger state-driven client changes in other contexts. For example, in one implementation, near real-time system 102 can trigger a state-driven user interface update in conjunction with cloud gaming events. For instance, near real-time system 102 can generate and broadcast an update message to the client device, causing the client device to update user interface elements to reflect in-game activity relative to the currently active cloud-based game (e.g., "There are currently 390k players online," "A tournament is starting in 1 hour," etc.).

[0044] In an additional implementation, the near real-time system 102 can trigger state-driven updates on the client device beyond user interface updates. For example, the near real-time system 102 can generate and broadcast an update message to the client device, causing the client device to transition from a "normal" state to a "troubleshooting" state, in which the client device suspends specific functions, reports data back to the digital streaming platform at a higher granularity, etc. For instance, in one example, the near real-time system 102 can generate and broadcast an update message to a specific type of client device (e.g., a specific brand and model of TV with the digital streaming platform application installed), causing that type of client device to transition to a troubleshooting state and report high-granularity debug data back to the digital streaming platform 104. Therefore, the near real-time system 102 can cause the client device to display prefetched user interface elements based on the updated state of live events, cloud gaming, etc. Furthermore, the near real-time system 102 can also cause the client device to modify its functionality based on the transmitted state.

[0045] Figure 5 An overview of the prefetch phase 500 and near real-time update phase 506 implemented by the near real-time system 102 in enabling client devices to display state-specific updates associated with streaming platform events in near real-time as these events undergo state changes. For example, during the prefetch phase 500, the near real-time system 102 enables client devices 114a-114c to prefetch streaming platform event metadata 504 from streaming platform data 502 maintained by the digital streaming platform 104.

[0046] In one or more implementations, near real-time system 102 causes client devices 114a-114c to prefetch streaming platform event metadata 504 in response to determining that client devices 114a-114c have subscribed to one or more topics—such as streaming platform events associated with streaming platform event metadata 504. Additionally or alternatively, near real-time system 102 causes client devices 114a-114c to prefetch streaming platform event metadata 504 in response to determining that client devices 114a-114c have subscribed to one or more topics associated with a specific digital streaming platform characteristic (e.g., language subgroup, geographic region subgroup, specific audience preference subgroup) connected to the streaming platform event associated with streaming platform event metadata 504.

[0047] In one or more implementations, the streaming platform event metadata 504 associated with a specific streaming platform event includes various personalized and / or state-driven user interface elements, one or more coordination arrangements associated with the streaming platform event, and other data associated with the streaming platform event. More specifically, state-driven user interface elements may include banner elements, badge elements, icon elements, digital media previews (e.g., short digital videos), etc. In one or more examples, the state-driven user interface elements are personalized for each of the client devices 114a-114c (e.g., including text in a specific language, including specific colors, including personalized animations). In at least one implementation, the state-driven user interface elements include multiple versions of the same banner, badge, or icon, where each version includes different state-based language (e.g., “Starting tomorrow,” “Starting in 1 hour,” “Started,” “Ending soon”).

[0048] In one or more implementations, the near real-time system 102 causes client devices 114a-114c to prefetch streaming media platform event metadata 504 a predetermined amount of time prior to the start of the associated streaming media platform event. In some implementations, the near real-time system 102 may invalidate the already prefetched streaming media platform event metadata in response to determining that new metadata associated with the streaming media platform event has been added to the streaming media platform data 502. In this case, the near real-time system 102 initiates a new prefetch phase 500 for the client devices 114a-114c.

[0049] At some point after or concurrently with the prefetch phase 500, the near real-time system 102 enters the near real-time update phase 506. During the near real-time update phase 506, the near real-time system 102 detects or determines that a streaming platform event state update 508 has occurred or has been received from within the cloud gateway 510. For example, the near real-time system 102 may receive a streaming platform event state update 508 indicating that a state change has occurred regarding a streaming platform event. For instance, in one example, the streaming platform event state update 508 indicates that the streaming platform event state has changed from "about to begin" to "beginning now".

[0050] Upon receiving the streaming platform event state update 508, the near real-time system 102 generates an update message based on the streaming platform event state update 508. In one or more examples, the near real-time system 102 generates the update message as a low-latency network communication indicating a state change or update associated with the streaming platform event. In some examples, the near real-time system 102 also generates an update message indicating prefetched metadata on client devices 114a-114c affected by the state change.

[0051] In one or more implementations, the near real-time system 102 broadcasts the generated update message to client devices 114a-114c, causing client devices 114a-114c to render or re-render one or more user interface elements to indicate the current state of the streaming platform event. In one or more examples, the near real-time system 102 repeats the near real-time update phase 506 each time a state change related to a streaming platform event is detected.

[0052] As stated above, and as Figure 6 As shown, the near real-time system 102 performs various functions in enabling client devices to display personalized and / or state-specific updated content associated with streaming platform events in near real-time as streaming platform events undergo state changes. Figure 6 This is a block diagram 600 illustrating how the near real-time system 102 operates within the memory 106 of one or more servers 112 while performing these functions. Therefore, Figure 6 Provide additional details about these functionalities. For example, in one or more implementations, such as Figure 6 As shown, the near real-time system 102 includes a prefetch manager 602, a streaming media platform event manager 604, and a subscription manager 606. For example... Figure 6 As further shown, addendum 108 stores and maintains streaming platform event metadata 504.

[0053] In some implementations, near real-time system 102 represents one or more software applications, modules, or programs that, when executed by a computing device, enable the computing device to perform one or more tasks. For example, and as will be described in more detail below, one or more of the prefetch manager 602, streaming media platform event manager 604, and subscription manager 606 may represent software that is stored and configured to run on one or more computing devices, such as one or more servers 112. Figure 6 One or more of the prefetch manager 602, streaming media platform event manager 604, or subscription manager 606 of the near real-time system 102 shown may also represent all or part of one or more dedicated computers used to perform one or more tasks.

[0054] As stated above, and as Figure 6 As shown, the near real-time system 102 includes a prefetch manager 602. In one or more implementations, the prefetch manager 602 handles tasks associated with prefetching streaming media platform event metadata 504, as described above regarding... Figure 5As discussed. For example, prefetch manager 602 can enable client devices 114a-114c to prefetch streaming platform event metadata 504 at a predetermined time point prior to the streaming platform event. In some implementations, prefetch manager 602 introduces jitter into the requests to client devices 114a-114c so that servers(one or more) 112 do not experience a request "thundering herd".

[0055] As described above, the prefetch manager 602 enables client devices 114a-114c to prefetch streaming platform metadata that is both state-specific and personalized. Therefore, in one or more examples, the prefetch manager 602 manages the prefetching of metadata reflecting personalized language choices, personalized design choices, and other personalized configuration choices. Thus, the prefetch manager 602 enables this personalized metadata to be prefetched to client devices 114a-114c, making it "on the fly" ready when needed on the client side.

[0056] Furthermore, in one or more implementations, the prefetch manager 602 invalidates outdated client-side metadata. For example, the prefetch manager 602 determines when new streaming platform event metadata is available and identifies existing metadata that should be replaced. In at least one implementation, the prefetch manager 602 instructs client devices 114a-114c to invalidate existing metadata and prefetch new streaming platform event metadata. In one or more examples, the new streaming platform event metadata includes updated user interface display elements, updated coordination arrangements, etc.

[0057] As stated above, and as Figure 6 As shown, the near real-time system 102 includes a streaming media platform event manager 604. In one or more implementations, the streaming media platform event manager 604 tracks or detects state changes associated with streaming media platform events. For example, the streaming media platform event manager 604 receives messages (e.g., current state metadata) from one or more event-specific subsystems or live event monitoring services and analyzes the received messages to determine whether a state change has occurred. State changes may include, for example, when an event went live, when an event completed, when content was marked as sensitive, etc.

[0058] In response to determining that a state change has occurred, the streaming platform event manager 604 also generates an update message and broadcasts it to the client devices 114a-114c. As described above, the streaming platform event manager 604 generates low-latency network communication that indicates the state change and causes the client devices 114a-114c to re-render or remove user interface elements using prefetched streaming platform event metadata 504 already stored on the client devices 114a-114c. In at least one implementation, the streaming platform event manager 604 utilizes the WebSocket communication protocol to broadcast the update message to the client devices 114a-114c.

[0059] In one or more implementations, the streaming platform event manager 604 generates and broadcasts update messages when a streaming platform event undergoes an unexpected state change. For example, as described above, the prefetch manager 602 causes client devices 114a-114c to prefetch one or more coordination schedules associated with a streaming platform event. However, streaming platform events may undergo schedule changes, schedule delays, or other states that cannot be scheduled in advance. Therefore, in most implementations, the streaming platform event manager 604 allows client devices 114a-114c to display personalized and state-specific user interface elements based on the prefetched coordination schedules and sends update messages that cause client devices 114a-114c to re-render user interface elements when an unexpected or unplanned state change occurs. Similarly, in some examples, the streaming platform event manager 604 suppresses planned state changes when event changes or delays invalidate planned state changes.

[0060] In one or more implementations, the streaming platform event manager 604 considers subscribed client devices that are late in watching the streaming platform event. For example, the streaming platform event manager 604 maintains a cache of outgoing update messages for delivery when a user device comes online during the event—whether late or intermittently. The streaming platform event manager 604 then polls user devices watching the streaming platform event at regular intervals during the event to identify latecomers or devices that have lost connection and reconnected. In one or more examples, the streaming platform event manager 604 broadcasts one or more update messages from the cache to these additional client devices, causing them to re-render prefetched user interface elements associated with the streaming platform event, thereby ensuring that users on those devices see the correct state-based information associated with the event.

[0061] While many examples described herein involve displaying instantaneous, state-specific display elements on client devices 114a-114c during live streaming events within the digital streaming platform 104, the streaming platform event manager 604 manages instantaneous and state-specific updates associated with other types of state-driven events. For example, another example includes the streaming platform event manager 604 implementing instant notifications associated with state changes to specific digital streaming platform 104 configuration values. In yet another example, the streaming platform event manager 604 implements one-to-one personalized messaging between services within the digital streaming platform 104 and client devices associated with specific accounts. Therefore, streaming platform events can be live or non-live events.

[0062] As stated above, and as Figure 6 As shown, the near real-time system 102 includes a subscription manager 606. In one or more implementations, the subscription manager 606 manages subscriptions associated with streaming platform events and identifies client devices that have subscribed to various topics associated with the streaming platform events. For example, the subscription manager 606 enables client devices 114a-114c to subscribe to (e.g., via GraphQL) one or more topics. In at least one implementation, the subscription manager 606 organizes client devices 114a-114c into communication nodes based on their subscriptions. In response to receiving a subscription, the subscription manager 606 generates a subscription key based on a hash of the subscription type and subscription parameters (i.e., meaning the key will be the same for the same subscription).

[0063] Subsequently, when the streaming platform event manager 604 generates an update message associated with a streaming platform event, the subscription manager 606 uses the target information associated with the streaming platform event to locate the subscription key and the corresponding communication node. The subscription manager 606 then enables the streaming platform event manager 604 to broadcast the update message to the correct client device via the identified subscription key and communication node.

[0064] like Figure 1 and Figure 6As shown, server(s) 112 and client devices 114a-114c each include one or more physical processors, such as physical processors 110 and 122a-122c. Physical processors 110 and 122a-122c generally represent processing units of any type or form of hardware implementation capable of interpreting and / or executing computer-readable instructions. In one implementation, physical processors 110 and 122a-122c access and / or modify one or more components of the near real-time system 102. Examples of physical processors include, but are not limited to, microprocessors, microcontrollers, central processing units (CPUs), field-programmable gate arrays (FPGAs) implementing soft-core processors, application-specific integrated circuits (ASICs), portions of one or more of the aforementioned processor components, variations or combinations of one or more of the aforementioned processor components, and / or any other suitable physical processor.

[0065] In addition, such as Figure 1 and Figure 6 As shown, server(s) 112 and client devices 114a-114c respectively include memories 106 and 118a-118c. In one or more implementations, memories 106 and 118a-118c generally represent any type or form of volatile or non-volatile storage device or medium capable of storing data and / or computer-readable instructions. In one example, memories 106 and 118a-118c store, load, and / or maintain one or more components of the near real-time system 102. Examples of memories 106 and 118a-118c include, but are not limited to, random access memory (RAM), read-only memory (ROM), flash memory, hard disk drive (HDD), solid-state drive (SSD), optical disk drive, cache, variations or combinations of one or more of the above memory components, and / or any other suitable storage memory.

[0066] In addition, such as Figure 6 As shown, one or more servers 112 include an addendum 108. On one or more servers 112, the addendum 108 includes streaming platform event metadata 504. In one or more implementations, as described above, the streaming platform event metadata 504 includes coordination arrangements and personalized, state-specific metadata associated with the streaming platform event. In some implementations, the streaming platform event metadata 504 includes a high cardinality value prefetched prior to the streaming platform event.

[0067] In summary, the near real-time system 102 enables the display and / or updating of personalized and state-specific content on client devices in near real-time as the state of events on the streaming media platform changes. Where previous systems utilized protocols that caused sudden, disruptive spikes and consumption of system resources, the near real-time system 102 utilizes prefetched and low-latency update messages to enable client devices to instantly re-render or otherwise update digital streaming media platform application elements. Due to the prefetching of critical elements, the near real-time system 102 allows these changes to occur in near real-time without causing spikes in server request levels or leading to service interruptions and other bottlenecks.

[0068] The following will be referenced Figure 7 A detailed description of an exemplary ecosystem is provided, in which content is pre-provisioned to end nodes, and requests for content are directed to specific end nodes. Corresponding to Figure 8 and Figure 9 The discussion presents an overview of exemplary distribution infrastructures and exemplary content players used during a playback session. These exemplary ecosystems and distribution infrastructures are discussed in the aforementioned references. Figures 1-6 Implemented in any of the embodiments.

[0069] Figure 7 This is a block diagram of a content distribution ecosystem 700, which includes a distribution infrastructure 710 communicating with a content player 720. In some embodiments, the distribution infrastructure 710 is configured to encode data at a specific data rate and transmit the encoded data to the content player 720. The content player 720 is configured to receive the encoded data via the distribution infrastructure 710 and decode the data for playback to a user. The data provided by the distribution infrastructure 710 includes, for example, audio, video, text, images, animations, interactive content, haptic data, virtual or augmented reality data, location data, game data, or any other type of data provided via streaming media.

[0070] Distribution infrastructure 710 typically refers to any service, hardware, software, or other infrastructure component configured to deliver content to end users. For example, distribution infrastructure 710 includes content aggregation systems, media transcoding and packaging services, network components, and / or various other types of hardware and software. In some cases, distribution infrastructure 710 is implemented as a highly complex distribution system, a single media server or device, or anything in between. In some examples, regardless of size or complexity, distribution infrastructure 710 includes at least one physical processor 712 and memory 714. One or more modules 716 are stored or loaded into memory 714 to implement adaptive streaming as described herein.

[0071] Content player 720 generally refers to any type or form of device or system capable of playing audio and / or video content already provided via distribution infrastructure 710. Examples of content player 720 include, but are not limited to, mobile phones, tablets, laptops, desktop computers, televisions, set-top boxes, digital media players, virtual reality headsets, augmented reality glasses, and / or any other type or form of device capable of rendering digital content. Like distribution infrastructure 710, content player 720 includes a physical processor 722, memory 724, and one or more modules 726. Some or all of the adaptive streaming process described herein is performed or implemented by module 726, and in some examples, module 716 of distribution infrastructure 710 coordinates with module 726 of content player 720 to provide adaptive streaming of digital content.

[0072] In some embodiments, Figure 7 One or more modules 716 and / or 726 represent one or more software applications or programs that, when executed by a computing device, cause the computing device to perform one or more tasks. For example, and as will be described in more detail below, one or more modules 716 and 726 represent modules stored and configured to run on one or more general-purpose computing devices. Figure 7 One or more modules 716 and 726 in the document also represent all or part of one or more special-purpose computers configured to perform one or more tasks.

[0073] Furthermore, one or more of the modules, processes, algorithms, or steps described herein transform data, physical devices, and / or representations of physical devices from one form to another. For example, one or more modules described herein receive audio data to be encoded, transform the audio data by encoding it, output the encoded result for use in an adaptive audio bitrate system, transmit the transformed result to a content player, and provide the transformed data to an end user for consumption. Additionally or alternatively, one or more modules described herein transform a processor, volatile memory, non-volatile memory, and / or any other part of the physical computing device from one form to another by performing on a computing device, storing data on a computing device, and / or otherwise interacting with a computing device.

[0074] Physical processors 712 and 722 generally represent processing units of any type or form of hardware implementation capable of interpreting and / or executing computer-readable instructions. In one example, physical processors 712 and 722 access and / or modify one or more modules 716 and 726, respectively. Additionally or alternatively, physical processors 712 and 722 execute one or more modules 716 and 726 to facilitate adaptive streaming of digital content. Examples of physical processors 712 and 722 include, but are not limited to, microprocessors, microcontrollers, central processing units (CPUs), field-programmable gate arrays (FPGAs) implementing soft-core processors, application-specific integrated circuits (ASICs), portions of one or more of the above processor components, variations or combinations of one or more of the above processor components, and / or any other suitable physical processor.

[0075] Memory 714 and 724 generally refer to any type or form of volatile or non-volatile storage device or medium capable of storing data and / or computer-readable instructions. In one example, memory 714 and / or 724 stores, loads, and / or maintains one or more modules 716 and 726. Examples of memory 714 and / or 724 include, but are not limited to, random access memory (RAM), read-only memory (ROM), flash memory, hard disk drive (HDD), solid-state drive (SSD), optical disk drive, cache, variations or combinations of one or more of the above memory components, and / or any other suitable memory device or system.

[0076] Figure 8 This is a block diagram of exemplary components of a distribution infrastructure 710 according to certain embodiments. The distribution infrastructure 710 includes a storage device 810, a service 820, and a network 830. Storage device 810 generally refers to any device, group of devices, and / or system capable of storing content for delivery to end users. Storage device 810 includes a central storage repository with devices capable of storing terabytes or petabytes of data, and / or includes distributed storage systems (e.g., devices that mirror or cache content at internet-connected locations to provide faster access to mirrored content within specific partitions). Storage device 810 may also be configured in any other suitable manner.

[0077] As shown in the figure, storage device 810 can store various items, including content 812, user data 814, and / or log data 816. Content 812 includes television programs, movies, video games, user-generated content, and / or any other suitable type or form of content. User data 814 includes personally identifiable information (PII), payment information, preference settings, language and accessibility settings, and / or any other information associated with a specific user or content player. Log data 816 includes viewing history information, network throughput information, and / or any other metrics associated with a user's connection or interaction with the distribution infrastructure 710.

[0078] Service 820 includes personalization service 822, transcoding service 824, and / or packaging service 826. Personalization service 822 includes personalized recommendations, content streaming, and / or other aspects of the user's experience with distribution infrastructure 710. Transcoding service 824 compresses media at different bitrates, as described in more detail below, enabling real-time switching between different encodings. Packaging service 826 packages the encoded video before deploying it to a delivery network (such as network 830) for streaming.

[0079] Network 830 generally refers to any medium or architecture capable of facilitating communication or data transmission. Network 830 uses wireless and / or wired connections to facilitate communication or data transmission. Examples of network 830 include, but are not limited to, intranets, wide area networks (WANs), local area networks (LANs), personal area networks (PANs), the Internet, power line communication (PLC), cellular networks (e.g., Global System for Mobile Communications (GSM) networks), portions of one or more of the above networks, variations or combinations of one or more of the above networks, and / or any other suitable network. For example, such as Figure 8 As shown, network 830 includes the Internet backbone network 832, the Internet service provider network 834, and / or the local network 836. As discussed in more detail below, bandwidth limitations and bottlenecks in one or more of these network segments trigger video and / or audio bitrate adjustments.

[0080] Figure 9 yes Figure 7 A block diagram illustrating an exemplary implementation of the content player 720. The content player 720 generally refers to any type or form of computing device capable of reading computer-executable instructions. The content player 720 includes, but is not limited to, laptop computers, tablets, desktop computers, servers, cellular phones, multimedia players, embedded systems, wearable devices (e.g., smartwatches, smart glasses, etc.), smart vehicles, game consoles, Internet of Things (IoT) devices (such as smart home appliances), variations or combinations of one or more of the above devices, and / or any other suitable computing device.

[0081] like Figure 9 As shown, in addition to the processor 722 and memory 724, the content player 720 includes communication infrastructure 902 and a communication interface 922 coupled to a network connection 924. The content player 720 also includes a graphics interface 926 coupled to a graphics device 928, an audio interface 930 coupled to an audio device 932, an input interface 934 coupled to an input device 936, and a storage interface 938 coupled to a storage device 940.

[0082] Communication infrastructure 902 generally refers to any type or form of infrastructure that facilitates communication between one or more components of a computing device. Examples of communication infrastructure 902 include, but are not limited to, any type or form of communication bus (e.g., Peripheral Component Interconnect (PCI) bus, PCI Express (PCIe) bus, memory bus, front-side bus, Integrated Drive Electronics (IDE) bus, control or register bus, host bus, etc.).

[0083] As previously described, memory 724 generally refers to any type or form of volatile or non-volatile storage device or medium capable of storing data and / or other computer-readable instructions. In some examples, memory 724 stores and / or loads operating system 908 for execution by processor 722. In one example, operating system 908 includes and / or represents software that manages computer hardware and software resources and / or provides public services to computer programs and / or applications on content player 720.

[0084] Operating system 908 performs various system management functions, such as managing hardware components (e.g., graphics interface 926, audio interface 930, input interface 934, and / or storage interface 938). Operating system 908 also provides a process and memory management model for playback application 910. Modules of playback application 910 include, for example, a content buffer 912, an audio decoder 918, and a video decoder 920.

[0085] Playback application 910 is configured to acquire digital content via communication interface 922 and play the digital content via graphics interface 926 and audio interface 930. Graphics interface 926 is configured to transmit rendered video signals to graphics device 928. Audio interface 930 is configured to transmit rendered audio signals to audio device 932. In normal operation, playback application 910 receives a request from the user to play a specific title or specific content. Playback application 910 then identifies one or more encoded video and audio streams associated with the requested title.

[0086] In one embodiment, playback application 910 begins downloading content associated with the requested title by downloading a sequence of data encoded to the lowest possible audio and / or video playback bitrate to minimize playback start-up time. The requested digital content file is then downloaded to content buffer 912, which is configured to act as a first-in, first-out queue. In one embodiment, each downloaded data unit includes either a video data unit or an audio data unit. As video data units associated with the requested digital content file are downloaded to content player 720, video data units are pushed into content buffer 912. Similarly, as audio data units associated with the requested digital content file are downloaded to content player 720, audio data units are pushed into content buffer 912. In one embodiment, video data units are stored in video buffer 916 within content buffer 912, and audio data units are stored in audio buffer 914 within content buffer 912.

[0087] The video decoder 920 reads video data units from the video buffer 916 and outputs video data units in a sequence corresponding to the duration of a fixed-span playback time. Reading video data units from the video buffer 916 effectively dequeues the video data units from the video buffer 916. The video frame sequence is then rendered by the graphics interface 926 and transmitted to the graphics device 928 for display to the user.

[0088] Audio decoder 918 reads audio data units from audio buffer 914 and outputs the audio data units as an audio sample sequence (typically time-synchronized with the decoded video frame sequence). In one embodiment, the audio sample sequence is transmitted to audio interface 930, which converts the audio sample sequence into an electrical audio signal. The electrical audio signal is then transmitted to the speaker of audio device 932, which generates an acoustic output in response.

[0089] When the bandwidth of the distribution infrastructure 710 is limited and / or variable, the playback application 910 downloads and buffers consecutive video and / or audio data portions from video encoders with different bitrates based on various factors (e.g., scene complexity, audio complexity, network bandwidth, device capabilities, etc.). In some embodiments, video playback quality takes precedence over audio playback quality. Audio playback quality and video playback quality are also balanced against each other, and in some embodiments, audio playback quality takes precedence over video playback quality.

[0090] The graphics interface 926 is configured to generate video data frames and transmit them to the graphics device 928. In one embodiment, the graphics interface 926 is included as part of an integrated circuit along with the processor 722. Alternatively, the graphics interface 926 is configured as a hardware accelerator that is different from the chipset including the processor 722 (i.e., not integrated within the chipset including the processor 722).

[0091] Graphics interface 926 generally refers to any type or form of device configured to forward images for display on graphics device 928. For example, graphics device 928 is manufactured using liquid crystal display (LCD) technology, cathode ray technology, and light-emitting diode (LED) display technology (organic or inorganic). In some embodiments, graphics device 928 also includes a virtual reality display and / or an augmented reality display. Graphics device 928 includes any technically feasible means for generating images to be displayed. In other words, graphics device 928 generally refers to any type or form of device capable of visually displaying information forwarded by graphics interface 926.

[0092] like Figure 9 As shown, the content player 720 also includes at least one input device 936 coupled to the communication infrastructure 902 via an input interface 934. The input device 936 generally refers to any type or form of computing device capable of providing computer-generated or human-generated input to the content player 720. Examples of the input device 936 include, but are not limited to, keyboards, point-and-click devices, voice recognition devices, touchscreens, wearable devices (e.g., gloves, watches, etc.), controllers, variations or combinations of one or more of the above devices, and / or any other type or form of electronic input mechanism.

[0093] The content player 720 also includes a storage device 940, which is coupled to the communication infrastructure 902 via a storage interface 938. The storage device 940 generally refers to any type or form of storage device or medium capable of storing data and / or other computer-readable instructions. For example, the storage device 940 is a disk drive, a solid-state drive, an optical disc drive, a flash drive, etc. The storage interface 938 generally refers to any type or form of interface or device used for transferring data between the storage device 940 and other components of the content player 720.

[0094] Example Implementation Example 1: A computer-implemented method that enables client devices to display state-specific updates associated with a streaming platform event in near real-time as the event undergoes a state change. For example, the method may include: generating an update message based on the state update associated with the streaming platform event; identifying one or more subscribed devices associated with the streaming platform event; and broadcasting the update message to the one or more subscribed devices to re-render one or more prefetched user interface elements associated with the streaming platform event within the streaming platform application on the one or more subscribed devices.

[0095] Example 2: The computer implementation method of Example 1, where the streaming platform event is a live streaming event.

[0096] Example 3: A computer-implemented method according to any one of Examples 1 and 2 further includes enabling one or more subscription devices to prefetch state-specific data associated with streaming platform events.

[0097] Example 4: A computer-implemented method according to any one of Examples 1 to 3, wherein state-specific data associated with a streaming platform event includes coordination arrangements associated with the streaming platform event, live event user interface elements, and live event metadata.

[0098] Example 5: A computer-implemented method according to any one of Examples 1 to 4, wherein generating an update message based on a state update includes generating a message reflecting changes in the coordination arrangements associated with events on the streaming media platform.

[0099] Example 6: A computer-implemented method according to any one of Examples 1 to 5, wherein the state update associated with a streaming media platform event includes current state metadata received from a live event monitoring service.

[0100] Example 7: A computer-implemented method according to any one of Examples 1 to 6 further includes storing an update message, determining that the add-on subscription device is online during a streaming platform event, and broadcasting the update message to the add-on subscription device to cause one or more prefetched user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the add-on subscription device.

[0101] Example 8: A computer-implemented method according to any one of Examples 1 to 7, further comprising receiving an additional state update indicating that a streaming platform event has ended, generating an additional update message based on the additional state update, and broadcasting the additional update message to one or more subscription devices to remove one or more prefetch user interface elements associated with the streaming platform event within a streaming platform application on one or more subscription devices.

[0102] In some examples, a system may include at least one processor and physical memory, the physical memory including computer-executable instructions that, when executed by the at least one processor, cause the at least one processor to perform various actions. For example, the computer-executable instructions may cause the at least one processor to perform actions including: generating an update message based on a state update associated with a streaming platform event; identifying one or more subscription devices associated with the streaming platform event; and broadcasting the update message to the one or more subscription devices to cause a re-rendering of one or more prefetched user interface elements associated with the streaming platform event within a streaming platform application on the one or more subscription devices.

[0103] In some examples, a method may be encoded as non-transitory computer-readable instructions on a computer-readable medium. In one example, when executed by at least one processor of a computing device, the computer-readable instructions cause the computing device to: generate an update message based on a state update associated with a streaming platform event, identify one or more subscribed devices associated with the streaming platform event, and broadcast the update message to the one or more subscribed devices to cause one or more prefetched user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the one or more subscribed devices.

[0104] Unless otherwise stated, the terms “connected to” and “coupled to” (and their derivatives) as used in the specification and claims shall be interpreted as allowing direct and indirect (i.e., via other elements or components) connections. Furthermore, the terms “a” or “an” as used in the specification and claims shall be interpreted as meaning “at least one”. Finally, for ease of use, the terms “comprising” and “having” (and their derivatives) as used in the specification and claims are interchangeable with the word “including” and have the same meaning.

Claims

1. A computer-implemented method, comprising: An update message is generated based on the state update associated with the streaming media platform event; Identify one or more subscription devices associated with the streaming platform event; as well as The update message is broadcast to the one or more subscription devices to cause one or more prefetch user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the one or more subscription devices.

2. The computer-implemented method according to claim 1, wherein the streaming media platform event is a live streaming media event.

3. The computer-implemented method of claim 1 further includes causing the one or more subscription devices to prefetch state-specific data associated with the streaming media platform event.

4. The computer-implemented method of claim 3, wherein the state-specific data associated with the streaming media platform event includes coordination arrangements associated with the streaming media platform event, live event user interface elements, and live event metadata.

5. The computer-implemented method of claim 4, wherein generating the update message based on the state update includes generating a message reflecting changes in the coordination arrangement associated with the streaming media platform event.

6. The computer-implemented method of claim 1, wherein the state update associated with the streaming media platform event includes current state metadata received from a live event monitoring service.

7. The computer-implemented method according to claim 1, further comprising: Store the update message; Determine if add-on subscription devices are online during the streaming platform event; as well as The update message is broadcast to the add-on subscription device to cause the one or more prefetch user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the add-on subscription device.

8. The computer-implemented method according to claim 1, further comprising: Receive additional status updates indicating that the streaming platform event has ended; An additional update message is generated based on the additional state update; as well as The additional update message is broadcast to the one or more subscription devices to remove the one or more prefetch user interface elements associated with the streaming platform event within the streaming platform application on the one or more subscription devices.

9. A system comprising: At least one physical processor; as well as Physical memory, including computer-executable instructions, which, when executed by the at least one physical processor, cause the at least one physical processor to perform actions, the actions including: An update message is generated based on the state update associated with the streaming media platform event; Identify one or more subscription devices associated with the streaming platform event; and The update message is broadcast to the one or more subscription devices to cause one or more prefetch user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the one or more subscription devices.

10. The system of claim 9, wherein the streaming media platform event is a live streaming media event.

11. The system of claim 9, further comprising computer-executable instructions that, when executed by the at least one physical processor, cause the at least one physical processor to cause the one or more subscription devices to prefetch state-specific data associated with the streaming media platform event.

12. The system of claim 11, wherein the state-specific data associated with the streaming platform event includes coordination arrangements associated with the streaming platform event, live event user interface elements, and live event metadata.

13. The system of claim 12, wherein generating the update message based on the state update includes generating a message reflecting changes in the coordination arrangement associated with the streaming media platform event.

14. The system of claim 9, wherein the state update associated with the streaming media platform event includes current state metadata received from the live event monitoring service.

15. The system of claim 9, further comprising computer-executable instructions, which, when executed by the at least one physical processor, cause the at least one physical processor to perform an action, the action comprising: Store the update message; Determine if add-on subscription devices are online during the streaming platform event; as well as The update message is broadcast to the add-on subscription device to cause the one or more prefetch user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the add-on subscription device.

16. The system of claim 9, further comprising computer-executable instructions, which, when executed by the at least one physical processor, cause the at least one physical processor to perform an action, the action comprising: Receive additional status updates indicating that the streaming platform event has ended; An additional update message is generated based on the additional state update; as well as The additional update message is broadcast to the one or more subscription devices to remove the one or more prefetch user interface elements associated with the streaming platform event within the streaming platform application on the one or more subscription devices.

17. A non-transitory computer-readable medium comprising one or more computer-executable instructions, which, when executed by at least one processor of a computing device, cause the computing device to: An update message is generated based on the state update associated with the streaming media platform event; Identify one or more subscription devices associated with the streaming platform event; as well as The update message is broadcast to the one or more subscription devices to cause one or more prefetch user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the one or more subscription devices.

18. The non-transitory computer-readable medium of claim 17, further comprising one or more computer-executable instructions, which, when executed by the at least one processor of the computing device, cause the computing device to cause the one or more subscription devices to prefetch state-specific data associated with events of the streaming media platform.

19. The non-transitory computer-readable medium of claim 17, further comprising one or more computer-executable instructions, which, when executed by the at least one processor of the computing device, cause the computing device to: Store the update message; Determine if add-on subscription devices are online during the streaming platform event; as well as The update message is broadcast to the add-on subscription device to cause the one or more prefetch user interface elements associated with the streaming platform event to be re-rendered within the streaming platform application on the add-on subscription device.

20. The non-transitory computer-readable medium of claim 17, further comprising one or more computer-executable instructions, which, when executed by the at least one processor of the computing device, cause the computing device to: Receive additional status updates indicating that the streaming platform event has ended; An additional update message is generated based on the additional state update; as well as The additional update message is broadcast to the one or more subscription devices to remove the one or more prefetch user interface elements associated with the streaming platform event within the streaming platform application on the one or more subscription devices.

Images