A system and method for management of video rendering and caching

The system addresses playback interruptions in video streaming by offline rendering and caching video content portions, ensuring continuous streaming through dynamic buffer management and robust fault tolerance.

WO2026239287A1PCT designated stage Publication Date: 2026-11-19ICHANNEL LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2026/054727
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-05-12
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Conventional video streaming systems face challenges in maintaining uninterrupted playback due to reliance on short loop buffers or pre-rendering methods that lack flexibility, leading to delays, degraded quality, or interruptions under unstable network conditions.

Method used

A system and method for managing video rendering and caching that involves offline rendering of video content portions and storing them in cache memory, with subsequent streaming, and dynamically triggering additional rendering to ensure continuous streaming by maintaining a sufficient buffer of rendered content ahead of playback.

Benefits of technology

Ensures uninterrupted video streaming by maintaining a sufficient buffer of rendered content in cache memory, reducing dependency on real-time rendering, and providing robust fault tolerance and flexibility to adapt to changing network conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2026054727_19112026_PF_FP_ABST
    Figure IB2026054727_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A computerized method for managing video rendering and caching includes offline rendering a first portion of video content to generate a rendered first portion having a first duration. The rendered first portion is stored in a cache memory. The rendered first portion is streamed from the cache memory. In response to determining that an unstreamed remainder of the rendered first portion is below a second duration, a second portion of the video content is offline rendered to generate a rendered second portion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming. The offline rendering is performed by a renderer faster than the rendered video content is streamed.
Need to check novelty before this filing date? Find Prior Art

Description

A SYSTEM AND METHOD FOR MANAGEMENT OFVIDEO RENDERING AND CACHINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 804,336, filed May 12, 2025, titled “A System and Method for Management of Video Rendering and Caching,” the entire contents of which are hereby incorporated by reference.TECHNICAL FIELD

[0002] The disclosure generally relates to video rendering, and more specifically to a system and method for managing offline video rendering and caching to facilitate uninterrupted video streaming.BACKGROUND

[0003] Video streaming systems have become a cornerstone of modem content delivery, supporting a wide variety of use cases including entertainment, education, news broadcasting, and real-time communication. These systems are often designed to deliver content on demand, adapting to different bandwidth conditions and device capabilities.

[0004] To ensure smooth playback, conventional systems typically rely on short loop buffers. Other systems attempt to pre-render the entire video content and stitch together rendered segments ahead of playback. While the latter approach may avoid runtime rendering delays, it suffers from limited flexibility. For example, it may not allow overlaying real-time graphics, modifying elements such as logos, or adapting content dynamically during playback. In many cases, particularly under unstable network conditions, approaches relying on short loop buffers may lead to delays, degraded quality, or interruptions in the viewing experience, i.e. , the dreaded black screen.

[0005] It is therefore desirable to provide a solution that overcomes the deficiencies of the known solutions.SUMMARY

[0006] A summary of several example embodiments of the disclosure follows. This summary is provided for the convenience of the reader to provide a basic understanding of such embodiments and does not wholly define the breadth of the disclosure. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later. For convenience, the term “certain embodiments” may be used herein to refer to a single embodiment or multiple embodiments of the disclosure.

[0007] One aspect of this disclosure provides a computerized method for managing video rendering and caching. The method includes the following operations. A first portion of video content is offline rendered to generate a rendered first portion having a first duration. The rendered first portion is stored in a cache memory. The rendered first portion is streamed from the cache memory. In response to determining that an unstreamed remainder of the rendered first portion is below a second duration, a second portion of the video content is offline rendered to generate a rendered second portion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming. The offline rendering is performed by a Tenderer faster than the rendered video content is streamed.

[0008] Another aspect of this disclosure provides a system for management of video rendering and caching. The system includes one or more processors and a memory. The memory includes instructions that, when executed by the one or more processors, cause the one or more processors to perform the following operations. A first portion of video content is offline rendered to generate a rendered first portion having a first duration. The rendered first portion is stored in a cache memory. The rendered first portion is streamed from the cache memory. In response to determining that an unstreamed remainder of the rendered first portion is below a second duration, a second portion of the video content is offline rendered to generate a rendered secondportion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming. The offline rendering is performed by a Tenderer faster than the rendered video content is streamed.

[0009] Yet another aspect of this disclosure provides a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the following operations for managing video rendering and caching. A first portion of video content is offline rendered to generate a rendered first portion having a first duration. The rendered first portion is stored in a cache memory. The rendered first portion is streamed from the cache memory. In response to determining that an unstreamed remainder of the rendered first portion is below a second duration, a second portion of the video content is offline rendered to generate a rendered second portion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming. The offline rendering is performed by a Tenderer faster than the rendered video content is streamed.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Some embodiments of the disclosed subject matter described, by way of example only, with reference to the accompanying drawings. With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present disclosed subject matter only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the disclosed subject matter. In this regard, no attempt is made to show structural details of the disclosed subject matter in more detail than is necessary for a fundamental understanding of the disclosed subject matter, the description taken with the drawings making apparent to those skilled in the art how the several forms of the disclosed subject matter may be embodied in practice. In the drawings:

[0011] FIG. 1A shows an example network diagram utilized to describe the variousembodiments.

[0012] FIG. 1B is a schematic diagram illustrating an example deployment architecture according to some embodiments.

[0013] FIG. 2 is a schematic diagram of an illustrative management server according to an embodiment.

[0014] FIG. 3 is a flowchart illustrating an illustrative method for video rendering and caching, according to an embodiment.DETAILED DESCRIPTION

[0015] Below, exemplary embodiments will be described in detail with reference to accompanying drawings so as to be easily realized by a person having ordinary knowledge in the art. The exemplary embodiments may be embodied in various forms without being limited to the exemplary embodiments set forth herein. Descriptions of well-known parts are omitted for clarity, and like reference numerals refer to like elements throughout.

[0016] It is important to note that the embodiments disclosed herein are only examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claims. Moreover, some statements may apply to some inventive features but not to others. In general, unless otherwise indicated, singular elements may be in plural and vice versa with no loss of generality.

[0017] Disclosed is a system and method for management of video rendering and caching to ensure continuous video streaming. The method includes rendering offline a first portion of a video content and storing it in cache memory. The rendered portion is streamed from the cache memory until a remaining unstreamed portion falls below a predefined duration. At that point, offline rendering of a second portion of the video content is resumed, such that the remainder of the rendered first portion and the newly rendered second portion together create a third duration. The rendering is performed at a speed faster than the streaming speed, allowing for uninterrupted playback.

[0018] FIG. 1A shows an example system 100A utilized to describe the various embodiments. In the example system 100A, a management server 120, a plurality ofTenderers 130-1 through 130-N (hereinafter referred to individually as a Tenderer 130 and collectively as Tenderers 130, merely for simplicity purposes), a plurality of cache memories 140-1 through 140-M (hereinafter referred to individually as a cache memory 140 and collectively as cache memories 140, merely for simplicity purposes), a plurality of network-level delivery nodes 150-1 through 150-K, (hereinafter referred to individually as a delivery node 150 and collectively as delivery nodes 150, merely for simplicity purposes), a plurality of user devices 160-1 through 160-Q (hereinafter referred to individually as a user device 160 and collectively as user devices 160, merely for simplicity purposes), and a plurality of storages 170-1 through 170-L (hereinafter referred to individually as a storage 170 and collectively as storages 170, merely for simplicity purposes) are communicatively connected to a network 110.

[0019] The network 110 is a communication infrastructure that interconnects the various components of the system 100A. Network 110 may include, but is not limited to, parallel or serial transmission over any of: a wireless network, a wired network, a local area network (LAN), a wide area network (WAN), the Internet, the worldwide web (WWW), the like, or any permissible combination thereof. The network 110 facilitates data exchange between content sources, processing components, user devices and the like.

[0020] The management server 120 is a computing device configured to control and coordinate the operation of the system 100A. It may include processing circuitry and memory containing executable instructions. The management server 120 is responsible for selecting a Tenderer 130 from a plurality or Tenderers 130, issuing rendering instructions to a selected render 130, storing rendered video content in a cache memory 140, monitoring the availability of cached video content in cache memories 140, allocating resources, and handling communication with user devices and storages 170. While the management server 120 is depicted as a single logical entity, its functionality may be distributed across multiple physical servers or cloudbased instances, including but not limited to virtual machines (VMs).

[0021] The Tenderers 130 may be implemented as one or more software-based rendering engines, dedicated hardware units (e.g., GPU), a cloud-based rendering service, or any permissible combination thereof. Each Tenderer 130 is configured to processvideo content either in an offline manner, producing rendered output segments suitable for later streaming, or in an online manner, particularly in scenarios involving live video sources. The Tenderers 130 may operate in parallel or be selected dynamically based on system conditions, rendering cost, or processing availability, as further described herein.

[0022] The cache memories 140 are storage components used to store post-rendering video segments, which are hereinafter collectively referred to as “rendered” segments, “rendered” portion, or “rendered” video content, depending on the context. The purpose of the cache memories 140 is to hold rendered video content, allowing the system to stream such content quickly without the need for real-time rendering.

[0023] The network-level delivery nodes 150 may include, for example, a TV provider’s head-end, a content delivery network (CDN) ingest node, and the like. The delivery node 150 may serve as a distribution hub that receives rendered video content from the cache memory 140 and transmits it on demand to multiple user devices, e.g., the user device 160, as further discussed herein. The storage 170 is a data repository configured to store at least video content and associated metadata. The storage 170 may be implemented in various forms, including but not limited to a local storage server, a network-attached storage (NAS), a cloud-based database service, or a distributed storage system. Each storage 170 may store original, pre-rendering (i.e., unrendered) video content in the form of full-length files, segmented media units, structured data representations, and the like. In some embodiments, storages 170 may also maintain version histories, content tags, or prioritization flags to assist the management server 120 in selecting and retrieving content for processing.

[0024] The user devices 160 may include, but are not limited to, mobile phones, tablets, desktop computers, smart TVs, and the like. Each user device 160 may be configured to communicate with the management server 120 to request video content, send a prompt to initiate streaming, or provide feedback regarding playback status. In some embodiments, the user device 160 may receive rendered video segments from the delivery node 150 or streaming relay.

[0025] In an embodiment, the method begins with rendering offline a first portion of a prerendering (i.e., unrendered) video content. To perform this operation, the managementserver 120 selects an item of pre-rendering video content from one of the connected storages 170. The selected pre-rendering video content may be selected based on system needs, user request, or a predefined schedule, stored, for example, but not by way of limitation, in a storage 170. The pre-rendering video content may consist of a full-length video, a video segment, a dynamically generated media item, permissible combinations thereof, and the like.

[0026] The management server 120 determines a first duration for the first portion to be rendered. This first duration may be configured statically (e.g., 8 hours), or determined dynamically based on factors such as expected playback length, content type, or timesensitive data requirements.

[0027] In an embodiment, the management server 120 instructs at least one selected Tenderer 130 to retrieve the selected pre-rendering video content from the storage 170 for offline rendering. In a further embodiment, the management server 120 may select one or more Tenderers 130 to retrieve and render the pre-rendering video content based on current rendering load, availability, rendering cost, and the like, and any permissible combinations thereof.

[0028] The Tenderer 130 that retrieves the pre-rendering video content performs offline rendering of the first portion of the pre-rendering video content. Offline rendering, in this context, refers to processing the video content in advance of streaming, rather than in real time. The rendering produces an output format suitable for streaming delivery, such as a sequence of a group of pictures (GOPs), audio, subtitles, and the like, and any permissible combinations thereof.

[0029] In an embodiment, the management server 120 instructs that the rendered first portion of the video content, generated by the selected Tenderer 130, be stored in a cache memory 140. In an embodiment, the management server 120 determines the target cache memory 140 based on factors such as proximity to a designated delivery node 150, current cache load, redundancy requirements, or considerations related to optimized streaming performance. In some embodiments, the selection may further take into account an expectation that the end user will receive the video stream from a specific machine, e.g., identified by IP address, preferably one that is topologically, or network-wise, close to the consuming user device 160. The selected cache memory140 may be located locally with the delivery node 150, centrally within the system 100A, or in a distributed architecture spanning multiple cache memory nodes. In some embodiments, cache memory 140 is positioned proximate to a network-level delivery node, e.g., the delivery node 150, such as a TV provider’s head-end or a content delivery network (CDN) ingest node. The delivery node 150 may serve as a distribution hub that receives the rendered video content from the cache memory 140 and transmits it on demand to multiple user devices, e.g., the user device 160, either directly or via downstream relays, based on user requests or session-based playback scheduling. This strategic placement helps minimize delivery latency and reduces the likelihood of transmission failures or interruptions along the downstream transmission path.

[0030] In some embodiments, the rendered first portion of the video content may be stored in more than one cache memory 140, for example, to allow fault tolerance or load balancing. The storing may occur in parallel, sequentially, or independently across cache memories 140, depending on system architecture and operational priorities. Once stored, the cached content becomes available for subsequent streaming to one or more delivery nodes 150 and then to one or more user devices 160, from anyone of the cache memories 140 containing the rendered video content. In an embodiment, if a user device 160 ceases to receive rendered video content from a first cache memory 140 it may request the rendered video content from a second cache memory 140 containing therein the same rendered video content, resuming streaming from the point of failure. As the rendered streams are bit-identical, such switching may be performed at any point within the stream, and not necessarily at a GOP boundary. In certain implementations, additional metadata may be associated with the cached content, including information such as its duration, encoding format, resolution, timestamp, or other playback-related attributes.

[0031] In an embodiment, the management server 120 is configured to monitor the streaming status of rendered video content from each cache memory 140. Upon detecting a failure or interruption in the streaming of rendered video content from a first cache memory 140, caused, for example, by a hardware fault, network disruption, or cache node unavailability, the management server 120 instructs one or moredelivery nodes 150 or user devices 160 to resume streaming of the rendered video content from a second cache memory 140 that contains the same rendered video content. Because the rendered video content stored across multiple cache memories 140 is bit-identical, the failover transition may be performed seamlessly at any point within the stream, without requiring re-rendering, re-buffering, or alignment to a GOP boundary. In some embodiments, the management server 120 may perform this failover autonomously, without requiring an explicit request from the user device 160, thereby ensuring continuity of playback that is transparent to the end user. The monitoring may be performed continuously or at defined polling intervals, and the failover response time may be configured based on quality-of-service requirements or service-level agreements applicable to the streaming session.

[0032] According to an embodiment, the management server 120 initiates the streaming of the rendered first portion of the video content from the cache memory 140 to one or more user devices 160 using the delivery nodes 150. The streaming may be triggered in response to a command, a scheduled event, or a detected playback request originating from a user device 160. In certain cases, the user device 160 may explicitly send a prompt to begin streaming, or the management server 120 may autonomously initiate streaming based on internal logic or predefined criteria.

[0033] In some embodiments, the prompt may comprise a signal indicating a disruption in the streaming of another, separate video stream (e.g., a disruption in streaming a live video stream). For example, if a live video feed currently being streamed to a user device 160 is unexpectedly interrupted due, for example, to connectivity issues, content unavailability, or quality degradation, the management server 120 may respond by initiating streaming of the rendered first portion of the video content from cache memory 140 as a fallback or alternative stream. This allows graceful recovery from failures and ensures uninterrupted playback for the end user, avoiding the dreaded black screen.

[0034] The rendered first portion of the video content is streamed directly from the cache memory 140, thereby eliminating the need for real-time rendering during playback. This allows low-latency delivery, reduces the real-time computational load on the Tenderer 130 at the time of streaming, and further avoids render related failures duringstreaming. It should be noted that one or more cache memories 140 may serve content to multiple user devices 160 in parallel, sequentially, independently, or stream different segments to different user devices 160 depending on entity profiles, quality of service (QoS) requirements, or session management rules.

[0035] According to an embodiment, the management server 120 instructs the Tenderer 130 to resume offline rendering of a pre-rendering second portion of the video content upon determining that the remainder of the rendered first portion of the video content, yet to be streamed, has fallen below a predefined second duration. This conditional triggering ensures that the rendering of the next pre-rendering portion of the video content begins in a timely manner, prior to the exhaustion of the rendered first portion during streaming.

[0036] In an embodiment, the second duration is determined based on the rendering speed of the selected Tenderer 130. Specifically, the management server 120 may calculate the second duration such that it is sufficient to allow the Tenderer 130 to complete rendering of the second portion of the video content before the unstreamed remainder of the rendered first portion is exhausted. For example, if the Tenderer 130 renders video content at a rate of six times real-time speed, the management server 120 may set the second duration to a value that provides at least enough lead time for the Tenderer 130 to generate a sufficient buffer of rendered content ahead of the streaming front. In some embodiments, the management server 120 may dynamically recalculate the second duration based on changes in the rendering speed of the selected Tenderer 130, for example in response to fluctuating system load or a switch to a different Tenderer 130 with different performance characteristics. This dynamic adjustment ensures that the triggering threshold remains appropriately calibrated to the actual rendering capabilities of the system at any given time, thereby reducing the risk of a gap in available rendered content during streaming.

[0037] In some embodiments, the system 100A is configured to dynamically switch between offline rendering mode and online rendering mode based on the type of content being processed or on runtime conditions detected during operation. Offline rendering, as described herein, refers to the processing of video content in advance of streaming. Online rendering, by contrast, refers to rendering performed in real time,concurrent with streaming, and is particularly applicable to live video sources where content is not available in advance. The management server 120 may determine the appropriate rendering mode by evaluating one or more of the following: the nature of the content source, for example whether it originates from a stored media file or a live feed; the availability of pre-rendered content in the cache memory 140; current system load; latency requirements of the streaming session; or explicit content metadata indicating the rendering mode preference. For instance, if a scheduled content item is replaced at runtime by a live broadcast segment, the management server 120 may instruct the Tenderer 130 to transition from offline rendering of the pre-scheduled content to online rendering of the live feed. Conversely, if a live feed is interrupted and a pre-rendered fallback segment is available in the cache memory 140, the system may revert to offline-rendered content delivery. In some embodiments, the transition between rendering modes may be performed without interrupting the stream being delivered to the user device 160, by ensuring that a sufficient buffer of rendered content exists in the cache memory 140 at the time of the switch.

[0038] In some embodiments, the management server 120 alternatively or additionally initiate rendering of a new video content portions based on dynamic playback changes, such as updates to a user’s playlist, manual content selection, or application logic that alters the streaming schedule. In scenarios involving live video sources, rendering may be performed in real time (i.e., online rendering) to accommodate the nature of the source content.

[0039] In an embodiment, the rendering instructions associated with already rendered and cached content may change dynamically. For instance, the management server 120 may have previously instructed a Tenderer 130 to render a video segment intended for playback between 12:00 and 16:00, which was subsequently stored in a cache memory 140. If the playlist is later modified such that different content is to be played between 14:00 and 15:00, the management server 120 identifies the affected time window and triggers re-rendering of the updated media segment by a selected Tenderer 130. Upon completion, the newly rendered segment is inserted into the appropriate temporal location within the cached content, effectively replacing the outdated segment. The cache memory 140 is then updated to reflect the modification,ensuring seamless and uninterrupted playback continuity without requiring full rerendering of unaffected portions.

[0040] Depending on the streaming settings and system configuration, the management server 120 may utilize areas of the cache memory 140 that previously held content already streamed, in order to store the newly rendered second portion, or portions thereof. This reuse of cache memory may be performed when additional space is required. However, the management server 120 ensures that cache memory 140 areas containing content that has not yet been streamed are preserved and not overwritten.

[0041] The resumed rendering may be executed by one of the Tenderers 130, which is selected by the management server 120. The selection may rely on the same criteria used for the initial rendering, such as current load, availability, rendering speed, or cost. Alternatively, the management server 120 may apply updated or adaptive selection criteria based on changes in system state, rendering queue status, or updated resource optimization policies at the time the pre-rendering second portion needs to be rendered.

[0042] The remainder of the rendered first portion of the video content, combined with the newly rendered second portion, together form a third duration. This third duration may be equivalent to the original first duration or vary depending on system configuration. The key objective of this process is to ensure continuous streaming without interruption, by maintaining a sufficient amount of rendered content in the cache memory 140 at all times.

[0043] According to an embodiment, the rendering of each portion of the video content, whether the first portion, the second portion, or any other subsequent portion, is performed by a Tenderer 130 at a speed that exceeds (or matches for live streaming) the rate at which the rendered video content is streamed to the user devices 160. This ensures that the system can generate sufficient rendered content in advance of playback requirements, even in cases where rendering is resumed reactively during ongoing streaming.

[0044] The rendering speed may be measured in terms of real-time ratio (e.g., rendering one minute of video in 10 seconds) or as an absolute processing throughput. Theability to render faster than streaming is particularly important in scenarios involving time-sensitive content or when the system experiences variable rendering load. By maintaining this rendering advantage, the management server 120 can avoid playback interruptions and ensure that each portion of the video content is available in the cache memory 140 before it is needed for streaming. It further allows the management server 120 to determine the characteristics of a selected Tenderer 130, as if a slower speed Tenderer 130 can be used it may provide a cost advantage and when it is necessary to have a faster rendering speed to avoid streaming interruptions the cost function is different.

[0045] In some embodiments, the selection of the Tenderer 130 for performing offline rendering may be optimized based on several factors such as the current cost associated with using a given Tenderer 130 and the amount of rendered video content presently stored in the cache memory 140. The management server 120 may take both of these parameters into account when determining which Tenderer 130 to assign for rendering tasks. For example, if the cache memory 140 already contains a sufficient buffer of post-rendering content, the management server 120 may deprioritize use of more costly rendering resources. Conversely, when the available cached content falls below a configured threshold, the management server 120 may select a Tenderer 130 that offers faster performance despite higher cost, in order to restore buffer levels and maintain continuous streaming.

[0046] In some embodiments, streaming of the rendered first portion of the video content may be scheduled to occur subsequent to the streaming of another video stream, for example, in scenarios where the system is configured to deliver sequential segments or alternate types of content. Conversely, in other embodiments, streaming of the rendered first portion of the video content may be configured to occur prior to another stream. This may be applicable both in scenarios where the system delivers preliminary content, such as trailers, promotional segments, and the like, and in scenarios where the rendered first portion of the video content constitutes primary content intended to be streamed before other primary content, such as in the case of programs composed of multiple parts or consecutive episodes. These configurations allow the management server 120 to schedule content delivery flexibly, based onsession structure, user experience goals, or operational considerations.

[0047] According to another embodiment, the cache memory 140 may be further configured to store rendered video content for future reuse. In particular, the cache memory 140 is not limited to temporarily holding rendered video content for immediate transmission to a delivery node 150, but is also adapted to retain selected rendered segments for later utilization, hereinafter referred to as a "history cache." To facilitate such reuse, the management server 120 may instruct the cache memory 140 regarding which rendered segments should be preserved and when these stored segments should be retrieved and used.

[0048] In some embodiments, the management server 120 is configured to identify, prior to initiating offline rendering of a portion of video content, whether a rendered version of the same content, or a portion thereof, already exists in the history cache. Such identification may be performed by comparing the content identifier, content metadata, or scheduling parameters of the requested video content against an index of previously rendered and retained segments maintained by the management server 120. If a matching rendered segment is found in the history cache, the management server 120 may retrieve and reuse the previously rendered segment in lieu of initiating a new rendering operation, thereby avoiding redundant rendering and reducing associated processing time and cost.

[0049] In some embodiments, the history cache is indexed by one or more temporal parameters, such as the original streaming time window during which the content was rendered and transmitted. For example, if a video content item was previously rendered and streamed between a first time and a second time, the management server 120 may store a reference associating the rendered segment with that time window. Upon scheduling the same or substantially similar content for a subsequent streaming session, the management server 120 may query the history cache using the relevant time window or content identifier to locate the previously rendered segment. If the segment is found and determined to be valid for reuse, based, for example, on criteria such as encoding format compatibility, resolution, absence of time-sensitive overlay elements that require re-rendering, or cache retention policy, the management server 120 may instruct the cache memory 140 to make the retrievedsegment available for streaming without initiating a new rendering operation.

[0050] In some embodiments, the management server 120 may apply a cache retention policy to determine which rendered segments are eligible for retention in the history cache and for how long. Such a policy may take into account factors such as available storage capacity, the likelihood of future reuse based on content scheduling patterns, content expiration rules, or operator-defined priorities. Segments that are unlikely to be reused, or that have exceeded a defined retention period, may be evicted from the history cache to free storage resources, while frequently reused or high-priority segments may be retained for extended periods.

[0051] Reference is now made to FIG. 1B, there is shown a schematic illustration 100B of a deployment architecture according to some embodiments. The system includes four main networks: A rendering local network 110-1, to which a management server 120, one or more Tenderers 130, and one or more storages 170 are connected. An internet network 110-2, to which one or more storages 175 and one or more cache memories 145 are connected. A caching local network 110-3, to which the cache memory 145 and one or more delivery nodes 150 are connected. A delivery network 110-4, configured to connect the delivery nodes 150 to one or more user devices 165.

[0052] In operation, the management server 120 instructs the Tenderer 130 to retrieve pre-rendering video content from the storage 170 over the rendering local network 110-1, and / or from the storage 175 over the internet 110-2, and further instructs the Tenderer 130 to perform offline rendering of a first portion of the video content, the rendered first portion having a first duration. The management server 120 is configured to instruct the Tenderer 130 to send the rendered first portion via the internet network 110-2 to the cache memory 145. The cache memory 145 stores the rendered first portion and, via the caching local network 110-3, provides the content to one or more delivery nodes 150. Each delivery node 150 is configured to stream the rendered video content to one or more user devices 165 over the delivery network 110-4.

[0053] Upon determining that the remainder of the rendered first portion yet to be streamed falls below a second duration, the management server 120 instructs the Tenderer 130 to resume offline rendering of a pre-rendering second portion of thevideo content, thereby ensuring that the combination of the remainder and the newly rendered portion forms a third duration, which maintains continuous streaming.

[0054] According to the disclosed architecture, the separation into multiple specialized networks provides several advantages in terms of system reliability and operational efficiency. In particular, operations such as offline rendering, content retrieval, and cache storage are performed over isolated local networks, thereby minimizing reliance on external network infrastructure. This separation ensures that rendering and cache operations remain unaffected even in the event of disruptions or failures in the public internet network 110-2.

[0055] It should be noted that the deployment architectures described herein, including but not limited to the examples illustrated in FIGS. 1A and 1B, are provided for exemplary purposes only. The specific arrangement of components, networks, cache memories, delivery nodes, and storage units is not intended to be limiting. Various other configurations, infrastructures, or communication pathways may be utilized to implement the principles of the disclosed embodiments. Modifications to the depicted architectures, such as changes in network topology, alternative cache hierarchies, different types of delivery infrastructures, or dynamic scaling of system components, are all considered to fall within the scope of the present invention, as defined by the appended claims.

[0056] It should be noted that the network 110 illustrated in FIG. 1A may, in some embodiments, represent a combination of multiple distinct networks as described in FIG. 1B. Specifically, the network 110 may encompass a rendering local network, an internet network, a caching local network, and a delivery network, each fulfilling different roles within the overall system architecture. Accordingly, the depiction of network 110 in FIG. 1A is provided for illustrative simplification, while in practice, the underlying infrastructure may involve a separation into multiple specialized networks, as exemplified in FIG. 1B.

[0057] FIG. 2 is a schematic diagram of an illustrative management server 120 according to an embodiment. The management server 120 includes a processing circuitry 221 coupled to a memory 222, a storage 223, and a network interface 224. In an embodiment, the components of the management server 120 are communicativelyconnected via a bus 225.

[0058] The processing circuitry 221 may be realized as one or more hardware logic components and circuits. For example, and without limitation, illustrative types of hardware logic components that can be used, include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), Application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), and the like, or any other hardware logic components that can perform calculations or other manipulations of information.

[0059] Memory 222 may be volatile (e.g., random access memory, etc.), non-volatile (e.g., read only memory, flash memory, etc.), or any combination thereof. In an embodiment, memory 222 is an on-chip memory, an off-chip memory, the like, and a combination thereof. In certain embodiments, memory 222 is a scratch-pad memory for the processing circuitry 221. In yet other embodiments the memory 222 may further provide cache memory functionality.

[0060] Storage 223 may be magnetic storage, optical storage, and the like, and may be realized, for example, as flash memory or other memory technology, or any other medium which can be used to store the desired information.

[0061] In one configuration, software for implementing one or more embodiments disclosed herein may be stored in storage 223, in memory 222, the like, and any combination thereof. Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code). The instructions, when executed by processing circuitry 221, cause the processing circuitry 221 to perform the various processes described in greater detail herein. More specifically, in an embodiment, such instructions may be used to control the operations described in FIGS. 1 through 3 and / or the operation of the system 100.

[0062] The network interface 224 is configured to connect to a network. The network interface 224 may include, but is not limited to, a wireless port (e.g., an 802.11compliant Wi-Fi circuitry), a wired Ethernet interface (e.g., 802.3 and 802.1 standards) configured to connect to a network, a universal serial bus (USB), whether serial or parallel, and the like. The network interface 224 allows the management server 120 to communicate with storages 170, other servers, user devices 160, and the like, such that the management server 120 can execute the embodiments discussed herein.

[0063] It should be understood that the embodiments described herein are not limited to the specific architecture illustrated in FIG. 2, and other architectures may be equally used without departing from the scope of the disclosed embodiments.

[0064] FIG. 3 is a flowchart describing an illustrative method for management of video rendering and caching, according to an embodiment. The disclosed method may be executed by the management server of FIG. 2 as well as in the context of FIG. 1.

[0065] At S310, a first portion of a pre-rendering (i.e., unrendered) video content is rendered offline. The rendered first portion has a first duration. The rendering may be performed by one or more Tenderers (e.g., the Tenderers 130 of Fig. 1) selected by the management server 120 based on load, availability, or cost considerations. The video content is received from a storage (e.g., the storage 170 of Fig. 1). The rendering produces an output format suitable for streaming delivery, such as a sequence of a group of pictures (GOPs).

[0066] At S320, the rendered first portion of the video content is stored in a cache memory, (e.g., the cache memory 140 of Fig. 1). In some embodiments, the same rendered portion may be stored in more than one cache memory instance to allow redundancy or load balancing.

[0067] At S330, the rendered first portion is streamed from the cache memory (e.g., the cache memory 140 of Fig. 1) to one or more delivery nodes (e.g., the delivery nodes 150 of Fig. 1) and then to one or more user devices (e.g., the user device 160 of Fig.1). Streaming may be triggered in response to a playback prompt, a scheduled event, or as a fallback when a disrupting video stream fails.

[0068] At S340, the system checks whether the remainder of the rendered first portion of the video content yet to be streamed has dropped below a second duration. This check is performed continuously by the management server 120 during playback and may rely on real-time streaming metrics or playback feedback. If the remainder has notdropped below the second duration, the management server 120 continuously monitors the streaming progress to determine whether the remainder of the rendered first portion of the video content yet to be streamed falls below a second duration.

[0069] At S350, upon determination that the remainder of the rendered first portion of the video content has been consumed from the cache memory 140 to below the second duration, the management server 120 instructs the Tenderer 130 to resume offline rendering of a pre-rendering (i.e., unrendered) second portion of the video content. In some embodiments, the management server 120 alternatively or additionally initiate rendering of a new video content portions based on dynamic playback changes, such as updates to a user’s playlist, manual content selection, or application logic that alters the streaming schedule. In scenarios involving live video sources, rendering may be performed in real time (i.e., online rendering) to accommodate the nature of the source content. The pre-rendering second portion may be selected dynamically and rendered by an available Tenderer 130. The unstreamed remainder of the rendered first portion together with the rendered second portion form a third duration of a rendered video content, ensuring continuity of playback. Depending on the streaming settings and system configuration, the management server 120 may utilize areas of the cache memory (e.g., the cache memory 140 of FIG. 1) that previously held content already streamed, in order to store the newly rendered second portion. This reuse of cache memory (e.g., the cache memory 140 of FIG. 1) may be performed when additional space is required. However, the management server 120 ensures that cache memory (e.g., the cache memory 140 of FIG. 1) areas containing content which has not yet been streamed are preserved and not overwritten.

[0070] The disclosed system and method offer a novel and efficient solution for management of the rendering and streaming of video content, ensuring continuity of playback even in changing environments. By separating the rendering process from the streaming timeline and performing rendering operations offline, the system eliminates the dependency on real-time rendering capabilities during playback. This architectural choice significantly reduces the risk of playback interruptions due to processing overload, rendering failures, or fluctuating system conditions.

[0071] An advantage of the system lies in its intelligent cache management mechanism.Rendered video segments are stored in one or more cache memories, selected based on proximity to the user devices, current load, or redundancy needs. This allows the system to optimize content delivery paths, reduce latency, and ensure high availability of video segments during streaming. Furthermore, in cases where content is already streamed, the corresponding cache space may be repurposed, allowing the system to efficiently reuse memory without compromising content integrity.

[0072] The system also provides triggering of additional rendering operations. When the remainder of the currently streamed content falls below a certain threshold, the management server initiates the rendering of the next portion in a timely manner. The rendering process is executed at a speed exceeding the streaming rate, ensuring that new content is always available before it is needed. This approach guarantees smooth and uninterrupted streaming, even in scenarios with time-sensitive or adaptive content.

[0073] Resource allocation is another area where the system demonstrates advantages.The management server selects Tenderers based on real-time factors such as rendering speed, availability, and operational cost. This flexibility allows for intelligent trade-offs between performance and resource efficiency. When system load is low or ample content is already cached, lower-cost Tenderers may be used; when urgency increases, faster resources are prioritized to maintain continuity.

[0074] Finally, the system is inherently robust and fault tolerant. Multiple cache memories and streaming fallback mechanisms allow rapid recovery from disruptions. If streaming from one cache node fails, the system can resume from an alternate cache memory node containing the same content, with minimal delay. Additionally, the architecture supports a wide range of content workflows, from live-stream fallback scenarios to sequenced content delivery, making it suitable for diverse applications including broadcasting platforms, adaptive video services, and hybrid streaming networks.

[0075] The principles of the disclosure are implemented as hardware, firmware, software, or any combination thereof. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium. The application program may be uploaded to, and executed by, amachine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units ("CPUs"), a memory, and input / output interfaces. The computer platform may also include an operating system and microinstruction code. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such computer or processor is explicitly shown. In addition, various other peripheral units may be connected to the computer platform such as an additional data storage unit and a printing unit.

[0076] All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the principles of the disclosure and the concepts contributed by the inventor to furthering the art and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the disclosure, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e. , any elements developed that perform the same function, regardless of structure.

[0077] A person skilled-in-the-art will readily note that other embodiments of the disclosure may be achieved without departing from the scope of the disclosed disclosure. All such embodiments are included herein. The scope of the disclosure should be limited solely by the claims thereto.

Claims

CLAIMSWhat is claimed is:

1. A computerized method for managing video rendering and caching, the method comprising:offline rendering a first portion of video content to generate a rendered first portion having a first duration;storing the rendered first portion in a cache memory;streaming the rendered first portion from the cache memory; andin response to determining that an unstreamed remainder of the rendered first portion is below a second duration, offline rendering a second portion of the video content to generate a rendered second portion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming;wherein the offline rendering is performed by a Tenderer faster than the rendered video content is streamed.

2. The method of claim 1 , further comprising receiving the video content from a storage.

3. The method of claim 1 , wherein the first duration is determined based on timesensitive data to be rendered within the video content.

4. The method of claim 1, wherein the second duration is determined based on a rendering speed of the Tenderer.

5. The method of claim 1, wherein the streaming begins in response to receiving a prompt to begin streaming, and the prompt comprises a signal indicating a disruption of another video stream.

6. The method of claim 5, wherein the rendered first portion is streamed as a fallback stream in response to the disruption of the another video stream.

7. The method of claim 1 , further comprising selecting the Tenderer from a plurality of Tenderers based on at least one of a current rendering load, Tenderer availability, rendering speed, rendering cost, or an amount of rendered video content stored in the cache memory.

8. The method of claim 7, wherein selecting the Tenderer comprises selecting a lower-cost Tenderer when the cache memory stores at least a predetermined amount of rendered video content.

9. The method of claim 7, wherein selecting the Tenderer comprises selecting a faster Tenderer when an amount of rendered video content stored in the cache memory is below a predetermined buffer threshold.

10. The method of claim 1 , wherein the rendered first portion is streamed after another stream of video content.

11. The method of claim 1 , wherein the rendered first portion is streamed before another stream of video content.

12. The method of claim 1 , wherein storing the rendered first portion in the cache memory comprises storing the rendered first portion in a first cache memory and storing the rendered first portion in a second cache memory.

13. The method of claim 12, further comprising, in response to a failure of streaming from the first cache memory, resuming streaming of the rendered first portion from the second cache memory.

14. The method of claim 1 , further comprising selecting the cache memory from a plurality of cache memories based on at least one of proximity to a delivery node, current cache load, redundancy requirements, or streaming performance.

15. The method of claim 1 , further comprising streaming the rendered first portion from the cache memory to a delivery node, and streaming, by the delivery node, the rendered first portion to a user device.

16. The method of claim 1, further comprising dynamically switching between offline rendering and online rendering based on a content type or a runtime condition.

17. A system for management of video rendering and caching, comprises:one or more processors; anda memory, the memory containing instructions that, when executed by the one or more processors, cause the one or more processors to:offline rendering a first portion of video content to generate a rendered first portion having a first duration;storing the rendered first portion in a cache memory;streaming the rendered first portion from the cache memory; and in response to determining that an unstreamed remainder of the rendered first portion is below a second duration, offline rendering a second portion of the video content to generate a rendered second portion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming;wherein the offline rendering is performed by a Tenderer faster than the rendered video content is streamed.

18. The system of claim 17, wherein the first duration is determined based on timesensitive data to be rendered within the video content.

19. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations for managing video rendering and caching, the operations comprising:offline rendering a first portion of video content to generate a rendered firstportion having a first duration;storing the rendered first portion in a cache memory;streaming the rendered first portion from the cache memory; andin response to determining that an unstreamed remainder of the rendered first portion is below a second duration, offline rendering a second portion of the video content to generate a rendered second portion, such that the unstreamed remainder and the rendered second portion together provide a third duration of rendered video content for continuous streaming;wherein the offline rendering is performed by a Tenderer faster than the rendered video content is streamed.

20. The non-transitory computer-readable medium of claim 19, wherein the first duration is determined based on time-sensitive data to be rendered within the video content.