Obviousness

A person having ordinary skill in the art (PHOSITA) in the field of video streaming and network optimization, at the priority date of US Patent 10,484,442 (July 18, 2012), would have possessed knowledge of several existing techniques and recognized specific problems within the domain, as articulated in the patent's own "Description of the Related Art" section. The combination of these known elements, driven by a clear motivation to overcome identified deficiencies, would render the claims of US10484442 obvious under 35 U.S.C. § 103.

Prior Art References (as described in US10484442's Background section):

1. Reference A: Mobile Video Optimization and Transcoding Challenges. A PHOSITA would be aware of the increasing prevalence of mobile devices and the need to optimize streamed videos for varying qualities, frame rates, and compression levels suitable for wireless transmission and mobile viewing. They would also know that while "optimization does improve the bandwidth usage," the "optimization process usually causes a delay in video streaming and playback as servers begin the transcoding process," leading to an adverse user experience. [cite: "Mobile devices, such as smart phones and tablets, have become prevalent in recent years. ... In many cases, videos available on the network are not optimized for wireless transmission or viewing on mobile devices ... optimization often involves transcoding a source file such as a video into a format that more closely fits the capabilities of mobile devices or the network provider's system. While optimization does improve the bandwidth usage ... the optimization process usually causes a delay in video streaming and playback as servers begin the transcoding process."]
2. Reference B: Local Caching by Individual Video Optimizers. It was a known practice for "Network providers and media sources" to use "local caching as a method for improving the streaming quality of source files such as video to mobile devices." Such local caches would "store the transcoded source file (or optimized version of the source file) for a short duration" to avoid "repeatedly retrieving and transcoding a particular file for a particular user during a single session." [cite: "Network providers and media sources may use local caching as a method for improving the streaming quality of source files such as video to mobile devices. When a source file is transcoded and optimized by a video optimizer, for example, it may be saved into a local cache. Local caching allows the video optimizer to store the transcoded source file (or optimized version of the source file) for a short duration and respond to a user's requests (e.g., replaying the video or skipping in the timeline of the video) without having to re-retrieve the source file for transcoding. Thus, the local cache configuration avoids repeatedly retrieving and transcoding a particular file for a particular user during a single session."]
3. Reference C: Problem of Uncoordinated Local Caches and Redundant Transcoding. Despite local caching, a significant limitation was that "a user has to be fortunate enough to be routed to a particular video optimizer, out of potentially thousands, having cached the optimized source file. Otherwise, the user has to wait through the same transcoding operation as the user who had previously streamed the video from another video optimizer." This highlights the problem of redundant transcoding across a network of optimizers due to their uncoordinated local caches. [cite: "Even if cached files are not purged, a user has to be fortunate enough to be routed to a particular video optimizer, out of potentially thousands, having cached the optimized source file. Otherwise, the user has to wait through the same transcoding operation as the user who had previously streamed the video from another video optimizer."]

Motivation for Combination:

Reference C clearly articulates the primary problem that a PHOSITA would be motivated to solve: the inefficiency and user dissatisfaction caused by redundant video transcoding operations across a network of optimizers due to the lack of coordination among their individual local caches. The goal would be to leverage existing optimized content across the entire network to minimize transcoding delays and improve overall network efficiency and user experience.

Obviousness Argument (Combination of References A, B, and C):

A PHOSITA, seeking to overcome the problem presented in Reference C, would find it obvious to combine the concepts from References A and B with general knowledge of distributed computing and content management to arrive at the claimed invention.

1. Introducing a Centralized/Distributed Index for Optimized Videos: To address the issue of uncoordinated caches (Reference C), a PHOSITA would logically consider implementing a mechanism to track which optimized video versions are stored where across the network of video optimizers (Reference B). This is a fundamental principle in distributed systems and content delivery networks (CDNs), where a directory or database is used to index and locate distributed resources. Thus, combining Reference B with general knowledge of Distributed Content Management would lead to the concept of a "cache database for monitoring local caching of optimized video occurring at numerous video optimizers," which "maintains entries corresponding to each optimized video locally cached at a given optimizer." [cite: "Embodiments disclosed herein include a cache database for monitoring local caching of optimized video occurring at numerous video optimizers. The cache database maintains entries corresponding to each optimized video locally cached at a given optimizer."]

2. Developing a Unique Identifier for Specific Optimized Versions: To effectively query this new cache database, a PHOSITA would recognize the need for a precise identifier for each specific optimized version of a video. Given that video optimization involves various parameters (e.g., resolution, bitrate, audio properties) to suit different devices and network conditions (Reference A), a simple identifier for the original source file would be insufficient. Therefore, combining Reference A with general knowledge of Data Identification techniques would lead to the obvious step of generating a unique "ID key" that encapsulates both the identity of the "original source file" and the "optimization parameters" used for transcoding. This allows the cache database to accurately determine if an already optimized version, matching the specific requirements of a new request, exists. [cite: "The network controller 140 as shown includes a key generator 145 for generating a identification (ID) key that uniquely identifies request source files and optimization parameters describing how a video optimizer 150 should transcode the source file for the user device 110."]

3. Implementing Reuse Mechanisms Upon Cache Hit: Once the cache database identifies that a matching optimized version exists on a "second video optimizer" (a "cache hit"), the subsequent steps for a "first video optimizer" to reuse this content would be obvious based on standard networking and content delivery practices. A PHOSITA would naturally choose between two well-known methods: either retrieving the optimized version from the second optimizer and streaming it to the user, or redirecting the user's device directly to the second optimizer to receive the stream. Both approaches efficiently leverage existing content and reduce the processing load on the initial optimizer. [cite: "The optimizer receiving the optimization request for the source file may then retrieve the optimized file from another optimizer or redirect the user device to the second optimizer, thus eliminating the need to generate redundant optimized source files."]

Therefore, the method, system, and computer-readable medium claims of US Patent 10,484,442 would have been obvious to a PHOSITA. The invention is a logical and straightforward application of known distributed caching and content delivery principles to solve a clearly identified problem of redundant transcoding in a network of video optimizers.