Obviousness

To analyze the obviousness of US patent 6182128 under 35 U.S.C. § 103, we will identify prior art combinations that would render the claims obvious and explain the motivation for a person having ordinary skill in the art (PHOSITA) to combine them. We will focus on independent Claim 2, as it is generally broader and more comprehensive, and thus a strong candidate for an obviousness challenge.

Claim 2 Analysis

Claim 2 of US6182128 describes:
"2. A system for distributing data files to users connected in a plurality of independent networks, said system comprising:
a) a plurality of distribution centers, each including:

1. a network interface including an input and an output for connecting to a single one of the networks;
2. a library including a plurality of data files;
3. a library interface including an input and an output connected to said library; and
4. a processor connected to said network interface and said library interface, said processor for:
   (a) receiving a request from a user via said input of said network interface, said request including information on one or more data files and a user address;
   (b) determining which of said requested data files are available in said library (“available requested data files”), and which of said requested data files are unavailable in said library (“unavailable requested data files”) and for each of said available requested data files, retrieving said available requested data file from said library via said library interface; and for each of said unavailable requested data files, sending a file import request to a central controller requesting said unavailable requested data files and receiving said unavailable requested data files through said network interface;
   (c) transmitting said requested data files to said single one of the networks via said output of said network interface; and
   (d) recording request information indicative of said requested data file and said user address; and
   b) a central controller directly connected to said network interface of each of said distribution centers for:
5. receiving file import requests from a requesting distribution center, said file import requests including information relating to requested data files;
6. searching the library within at least one other of said distribution centers to locate at least one requested data file of said requested data files; and
7. instructing said other distribution center to retrieve and transmit the requested data file that was located therein to said requesting distribution center."

Prior Art References and Obviousness Combination

A PHOSITA in 1998, the priority year of US6182128, would have found Claim 2 obvious in light of US5781889A (Martin) in combination with common knowledge in the art regarding distributed computing systems, or further in combination with US5550577A (Alcatel).

Primary Reference: US5781889A (Martin) - "Computer jukebox and jukebox network" (Priority Date: 1990-06-15; Publication Date: 1998-07-14)

Martin discloses a "computer jukebox and jukebox network" that distributes "digital audio files." This reference provides many elements of Claim 2:

• a) a plurality of distribution centers: Martin discloses "a plurality of jukebox computers," each storing digital audio files and connected to a network, which function as "distribution centers."
• 1) a network interface: The jukebox computers are connected via a "network" and would inherently possess network interfaces for communication.
• 2) a library including a plurality of data files: Each jukebox computer includes its "library" of "digital audio files" (music selections). The term "data files" in Claim 2 broadly encompasses these digital audio files.
• 3) a library interface: A library interface is an inherent component for accessing and managing files within the library.
• 4) a processor: Jukebox computers would necessarily include processors to manage their functions.
• (a) receiving a request from a user...: Users interact with the jukebox to select music. User address information, for billing or personalized services, was a well-known requirement for such on-demand systems.
• (b) determining which of said requested data files are available in said library... sending a file import request to a central controller... and receiving said unavailable requested data files through said network interface; Martin explicitly states: "If a particular selection is desired which is not found in the particular jukebox's library... a message is sent via the network to the central computer which obtains the selection from a master library and downloads it to the jukebox requesting the selection." This teaches determining local availability, requesting unavailable files from a central controller (the "central computer"), and receiving them.
• (c) transmitting said requested data files...: The jukebox computers play the selected music for users, effectively transmitting the audio data.
• (d) recording request information...: Martin mentions a "central database containing information as to the location of the particular selections (digital audio files) and can download this information to the various jukebox computers." Such a central database would commonly record request information for purposes like billing, royalty payments, or usage statistics, which was a known business practice for content distribution by 1998.
• b) a central controller directly connected to said network interface of each of said distribution centers for: Martin describes a "central computer" that supervises the network of jukebox computers, acting as the "central controller."
• 1) receiving file import requests from a requesting distribution center...: The central computer receives messages from jukeboxes when they cannot fulfill a request locally.
• 3) instructing said other distribution center to retrieve and transmit the requested data file... to said requesting distribution center: Martin states the central computer "obtains the selection from a master library and downloads it to the jukebox requesting the selection." The central computer, as a master library, directly retrieves and transmits.

Missing Element from Martin:

The primary element missing from Martin for Claim 2 is:

• 2) searching the library within at least one other of said distribution centers to locate at least one requested data file of said requested data files; Martin's central computer primarily relies on its "master library" and does not explicitly teach searching other jukebox computers for content.

Motivation to Combine with General Knowledge / Secondary Reference (e.g., US5550577A Alcatel):

A PHOSITA in 1998 would be motivated to enhance Martin's system (or similar distributed content systems like Alcatel's video-on-demand network) by having the central controller search other distribution centers.

1. Problem: In a large-scale networked jukebox system like Martin's, relying solely on a single "master library" at the central computer for all non-local content could lead to performance bottlenecks, increased network latency, and higher bandwidth/storage costs at the central hub.
2. Known Solution in Distributed Computing: By 1998, the principles of distributed computing and network optimization were well-established. PHOSITAs understood that distributing load, caching content locally, and facilitating content exchange between peer nodes via a central orchestrator could significantly improve scalability and efficiency. Concepts like federated search and distributed database queries were known, where a central directory or coordinator could direct requests to multiple peer nodes.
3. Predictable Result: Applying these known distributed computing principles to Martin's system would yield the predictable result of improved efficiency, reduced latency, and better utilization of cached content across the distributed jukeboxes. For instance, if Jukebox A requests a song not in its local library, the central computer (controller) could, instead of only querying its master library, first check an index of content available at other jukebox computers (other distribution centers). If Jukebox B has the song and is geographically or network-wise closer, the central computer could instruct Jukebox B to send it to Jukebox A (or directly to the requesting user via Jukebox A).
4. Motivation to Improve Scalability/Efficiency: This modification would be an obvious design choice for a PHOSITA seeking to improve the scalability and efficiency of a large-scale content distribution network by leveraging distributed resources and minimizing reliance on a single central repository.

Furthermore, US5550577A (Alcatel), published in 1996, describes a "video-on-demand network" with a "central video server" and "distributed video servers." Alcatel also teaches that "Each distributed video server stores a limited number of the most often requested films for local distribution, while any other film can be delivered by the central video server, either by means of a separate transmission to the subscriber or by downloading to the distributed video server." While Alcatel also points to the central server as the ultimate source, its explicit description of a distributed server architecture with local caching and central fallback reinforces the context of such systems. A PHOSITA would readily transfer principles from video-on-demand systems (Alcatel) to music-on-demand systems (Martin), as both deal with distributing digital media files in response to user requests. The combination of Martin's music-specific system with Alcatel's broader distributed VOD architecture further illustrates the obviousness of such distributed content management strategies.

Therefore, the combination of US5781889A (Martin) with the established knowledge in distributed computing and network design, or explicitly with the distributed server architecture of US5550577A (Alcatel), would render Claim 2 of US6182128 obvious to a PHOSITA.