Method and system for file system synchronization between a central site and a plurality of remote sites

Abstract

A method and system of synchronizing files between a central site and a plurality of remote sites is disclosed. The method and system comprises providing a list of files to the plurality of remote sites by the central site, prior to a callback time of the remote sites and reporting which of the files are missing by each of the plurality of remote sites to the central site. The method and system further includes determining within the central site which of the files needs to be sent to each of the plurality of remote sites. Accordingly, a system and method in accordance with the present invention helps deliver content from a central site to multiple remote sites. A system and method in accordance with the present invention uses the DMD in conjunction with a software client described below to maintain the file synchronization between the central server and remote site servers.

Description

FIELD OF THE INVENTION

[0002] The present invention relates to digital media distribution and more particularly to web file server synchronization between a central site and remote sites.

BACKGROUND OF THE INVENTION

[0003] Although broadcasters have sophisticated systems for inserting national commercials into a program stream, including integrated traffic and billing systems, there are numerous obstacles to implementing a system to insert local commercials at small markets into a national program feed distributed by satellite. Until now, such local spot insertion advertising was the responsibility of the local broadcaster or cable operator.

[0004] Inserting local advertising poses several non-trivial technical, logistical and business challenges. First, literally hundreds of widely distributed local operators (or affiliates) would need to receive the commercials. Ad agencies would then have to ship analog tapes to hundreds of organizations, with different traffic and billing systems. The analog tapes would need to be tested for quality assurance, tracked, and stored until needed. The tapes would then have to be distributed to video tape recorders and readied for computer controlled playout (analog) at the proper time, 24 hours a day, seven days a week. Such infrastructure generally exists at well-funded affiliates in major markets but is nonexistent and prohibitively expensive for smaller operators or affiliates in small markets.

[0005] Managing such tapes with ads for local commercials and inserting them properly into the program feed is a complex undertaking not well-suited for the smaller operators, especially for channels with smaller audiences in smaller markets. A quality broadcast involves more than excellent program material; it must also provide seamless insertion of national and local advertisements, promotions, and station identifications.

[0006] Equally important is the ability to maintain the integrity of the national television programming. Centralized control of the channel's programming (playout) is required to prevent local affiliates from tampering with the programming. In addition, it is important that there be synchronization between a plurality of remote sites and the centralized control to ensure that information is provided to each of the remote sites in a timely and efficient manner.

[0007] Typically each remote site will have their own file system, they will deposit their web content onto the central site server under their file system. The requirement is to deliver only the new or updated files to the remote sites and maintain the same directory structure. The remote site and central site file system must be in synch. If a remote site is down or unoperational for a number of days, central site must resend the latest copy (there could be multiple updates to the same file while the remote site is down) of the file(s) again once the remote site comes alive. In other words, a central site must know what's missing on the remote sites and be intelligent enough to send the missing or out-dated files.

[0008] Accordingly, a need exists for an efficient system for optimized distribution of digital media data to remote sites in a multimedia broadcast system from the central site. The present invention addresses such a need.

SUMMARY OF THE INVENTION

[0009] A method and system of synchronizing files between a central site and a plurality of remote sites is disclosed. The method and system comprises providing a list of files to the plurality of remote sites by the central site, prior to a callback time of the remote sites and reporting which of the files are missing by each of the plurality of remote sites to the central site. The method and system further includes determining within the central site which of the files needs to be sent to each of the plurality of remote sites.

[0010] Accordingly, a system and method in accordance with the present invention helps deliver content from a central site to multiple remote sites. A system and method in accordance with the present invention uses the DMD in conjunction with a software client described below to maintain the file synchronization between the central server and remote site servers.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 illustrates a block diagram of a digital media distribution system in accordance with the present invention.

[0012] FIG. 2 illustrates an example of a suitable layered architecture for the central site server.

[0013] FIG. 2A illustrates an FSS helper application and an ACSO mechanism in a central site.

[0014] FIG. 2B illustrates an FSS RSO mechanism in a remote site.

[0015] FIG. 3 illustrates a block flow diagram of a file synchronization process system in accordance with the present invention.

DETAILED DESCRIPTION

[0016] The present invention relates to digital media distribution and more particularly to web file server synchronization between a central site and a plurality of remote sites. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.

[0017] A block diagram of a DMD (digital media distributor) in accordance with the present invention is illustrated in FIG. 1. As shown, the DMD includes three major components: a central site 10, a distribution network 12, and a remote site 14. Although one remote site 14 is illustrated, one of ordinary skill in the art recognizes there is typically a plurality of remote sites for receiving and transmitting information. The central site 10 is the location for the digital encoding of MPEG-2 files from source video tapes, storage and management of digital files, management of remote site(s) 14, and distribution of schedules and MPEG-2 files. Thus, the processing, analysis, distribution, and management of data occurs at the central site 10. The distribution network 12 is the mechanism by which the remote site(s) 14 receive program streams and digital spots. The data distribution is accomplished via various methods, such as a satellite and/or land-based distribution. The broadcaster may choose to have the program stream sent via terrestrial links (e.g., token ring, ethernet, etc.), while the spot insertion is sent via satellites or vice versa.

[0018] The remote site(s) 14 house the remote site server(s) 16. By way of example, a suitable remote site server 16 includes a Pentium processor-based device with a hard disk for local storage and a video switch card (to switch between program and commercial insertion) running software including Windows NT, DMD programming, Lotus Notes client, Program Loader, and Symantec pcANYWHERE. These unattended, computerized systems receive the local insertion and provide As-Run file generation. The remote site server 16 is a video server that receives and stores digitized spots utilized for local insertion at the cable head-end. The remote site server 16 receives digitally encoded ads via satellite or other distribution network. These spots are decoded to an analog signal and inserted into the cable or network operator feed at scheduled times, i.e., into scheduled local availability times. The remote site server 16 can be customized in various configurations based on the number of output channels required, the type of output format (e.g., NTSC, PAL), the amount of local storage required (i.e., the number of spots on disk), the type of network (satellite or terrestrial), the type of trigger for spot insertion (e.g., time of day, VITC, cue-tome, VBI trigger), the audio format and connections (stereo, mini-XLR or XLR), the redundancy requirements (RAID, mirrored disks), and the preview channel.

[0019] By way of example, the following provides a sample process that illustrates an example of one process which the DMD solution can support. A region, e.g., any grouping of one or many cable head-ends for cities, states, provinces, or countries, defined by cable or network operators in an area, sells a commercial in the local availability time. All remote site servers 16 within the same region play the same material at the same time, including all network programs, national spots, local commercials, announcements, etc. The videotaped segment for the commercial is digitally encoded. The digital material is scheduled for delivery to each remote site server 16 prior to broadcast. The playlist, digitized spots, and the broadcast program stream are sent, via satellite, to all of the remote site servers 16 within the region. All of the remote site servers 16 within the region air the local spots for that region at the scheduled time. As-Run logs are retrieved by the central site 10 from the remote site servers 16. As-Run logs are sent to the local markets, reviewed, reconciled, and customers are billed. Commercials and As-Run logs are archived.

[0020] In accordance with the present invention, the central site 10 efficiently distributes objects and thus manages the resources of the remote site 14. By managing these resources, the central site 10 can determine when to send information to the remote site(s) 14. A main component in producing the management of the resources is the central site server 18. By way of example, a suitable central site server 18 includes an IBM RS/6000 F50 dual CPU system or a Pentium II compatible PC, running the IBM UNIX operating system, AIX, DB2 server software, Lotus Notes server software, ADSM, Windows NT (for PC-based central site server), and the DMD programming. Suitable components for the control workstations 19 include Pentium compatible PCs running Windows NT, Lotus Notes client, DB2 client, Microsoft Internet Explorer, and DMD programming.

[0021] The central site server 18 includes software on a suitable computer readable medium that is architected using a layered model, in which each layer isolates the upper layers from the details of the lower layers and individual components within a layer provide a unique set of services, as is well appreciated by those skilled in the art. FIG. 2 illustrates an example of a suitable layered architecture for the central site server 18. The top layer 20 addresses the external interfaces of the central site server 18, including a graphical user interface (GUI) component and the interfaces to the external systems. The GUI component, e.g., using Lotus Notes, provides administrators and operators with the ability to monitor and control the DMD. The interfaces to external systems include interfaces to traffic systems, which interface to the central site 18 by way of files exchanged on an Internet file server, for example, interfaces to stations in a box (SIBs) which send Lotus Notes messages, and interfaces to encoder systems (22, FIG. 1), which store encoded spot files in a disk pool server for retrieval by the central site server 18.

[0022] Underneath the top layer is a layer 24 of specialized components including a stage manager component 26, an uplink server component 28, and a transmission scheduler component 30. This layer 24 may also include specialized components for creating commands and interpreting responses from SIBs, managing access to all the database queues and other data stores, and providing automated agents that run based on time or events to manage the external interfaces, e.g., processing files received from traffic systems. The stage manager 26 manages any tape related activity, the uplink server 28 manages transmissions through the uplink network (12, FIG. 1), and the transmission scheduler 30 manages scheduling tasks in accordance with the present invention.

[0023] Also included as a next layer is a programming layer 32. The layer 32 includes the programming libraries and APIs (application programming interfaces) that are used to build the specialized components. The lower two layers include an operating system layer 34 and a hardware layer 36 for the fundamental operation of the central site server 18, as is well appreciated by those skilled in the art.

[0024] There are two entities at the central site 10 that are utilized in accordance with the present invention for synchronizing the files of the central site 10 with the files of the plurality of remote sites 14, a file system synchronization (FSS) helper application 25 and an automated central site operations (ACSO) mechanism 27. Each of the remote sites 14 has an entity referred to as the FSS remote site operations (FSS RSO) mechanism 29. FIG. 2A illustrates an FSS helper application and an ACSO mechanism within the transmission scheduler 30 of the central site 10. FIG. 2B illustrates an FSS RSO mechanism within the remote site server 16 within the remote site. To describe the interaction of these entities refer now to the following discussion in conjunction with the accompanying figure.

[0025] A system and method in accordance with the present invention makes possible one way synchronization between a central site 10 and a plurality of remote sites 14. Additionally, using the system and method in accordance with the present invention, all remote sites 14 which subscribe to the same file system can be grouped and connected back to the central site 10 at the same time. Callback time can be programmed in the remote site application. At a predetermined, configurable period of time, such as five minutes before the callback time, the central site server prepares the latest loadlist for that group and sends it to the remote sites 14, thus giving remote sites 14 enough time to prepare for the “missing file list” and determine which files can be deleted from the remote site server 16.

[0026] In a preferred embodiment, the time is synchronized between central site 10 and remote sites 16. This is important because the time is used to determine the call back time and when the loadlist is generated on the central site. Time synchronization can be performed either by installing GPS clocks at the central site and all remote sites or by using time synchronization programs, such as NTP time server, W32Time from Microsoft Windows Resource Kit.

[0027] The central site 10 waits for the remote sites 14 to callback and report which files are missing. The central site 10 will wait until timeout (five minutes, for example, after the scheduled callback). After the remote sites 14 in the same group call back and deposit their “missing file list”, the central site server will consolidate the list and determine if any files can be multicasted to multiple remote sites 14. The central site 10 can support multiple groups by partitioning the central site server into multiple file systems.

[0028] Accordingly, a system and method in accordance with the present invention helps deliver content from a central site to multiple remote sites. A system and method in accordance with the present invention uses the DMD in conjunction with a software client described below to maintain the file synchronization between the central server and remote site servers. To describe the features of the present invention in more detail, refer now to the following discussion in conjunction with the accompanying figure.

[0029] DMD-Integrated File System Sychronization

[0030] A method and system in accordance with the present invention ensures that the desired files in a specified file system are available on a remote site or sites 14 in the same file. Referring back to FIG. 1, the DMD is leveraged to minimize storage and transmission needs for the synchronization of files between the central site 10 and remote sites 14.

[0031] A remote site 14 may not receive files, for example, during power outages or bad weather. The central site 10, however, automatically keeps a master inventory of files as specified in a monitored file system for which there is a parallel file system at every remote site 14. Each of the remote sites 14 are configured to report back to the central site 10 at a pre-defined time, based on a callback scheduling algorithm. These report back periods are used to provide, among other data, information about the files that a remote site 14 will need. In so doing, the remote sites 14 save the most reliable information therewithin.

[0032] All remote sites 14 can be synchronized according to a central site's file system (or web server). A loadlist, which consists of file name, file path, file size, and timestamp of the file, is generated by the central site server and sent over to the remote sites 14. Each of the remote site servers 16 uses the latest loadlist to compare with the previously executed loadlist and then determines the files needed to be downloaded from the central site 10. The files can be deleted from the remote site 14. Filename, file path, file size, and the timestamp of the two loadlists are compared to determine new or updated files which need to be downloaded, and which files can be removed from the remote site's 14 local directory. The new or updated file list, which is called “missing file list”, is then sent from the remote site 14 back to the central site 10.

[0033] The central site 10 uses the “missing file list” from remote sites 14 and transmits the files to the remote site 14. The remote site 14 receives the “missing files” and uses the information in the loadlist (the file path field) to move the files to the proper directory.

[0034] To describe the present invention in more detail, refer now to the following discussion in conjunction with the accompanying figure. FIG. 3 illustrates a flow diagram of a file synchonization process system in accordance with the present invention. As is seen, the steps 302, 304, 318 and 320 are executed by the FSS helper application 25, steps 306, 308 and 322-326 are executed by ACSO mechanism 27 and the steps 310-316, 328 and 330 are executed by FSS RSO mechanism 29.

[0035] Referring now to FIGS. 1, 2, 2A, 2B and 3 together, after the system is set up, the process starts when an updated master inventory of files in the monitored file system is “published”, or fixed, for that day by the FSS helper application 25, via step 302. Typically the file system comprises an NT file system. The fixing of the updated files typically will occur a few hours ahead of a pre-defined report back time for the remote sites 14 participating in the file system synchronization.

[0036] In a preferred embodiment, the FSS helper 25 application, also running on an NT platform, prepares the list of the files in the file system (loadlist file), including the fall paths (directory structures), and the date-time stamp for each file. The loadlist file is date-time stamped and then transferred to the remote sites 14 ahead of the scheduled report back time, via step 304. The ACSO mechanism 27 then schedules the loadlist in a transmission queue within the DMD, via step 306. Next, the ACSO mechanism 27 transmits the loadlist to remote sites 14 ahead of the scheduled return time, via step 308.

[0037] Upon receiving the loadlist, the FSS RSO mechanism 29 compares the new loadlist against the last copy of the loadlist to create a list of files it will need, via step 310. These files may have changed, as evidenced by comparison of the date-time stamp of the files in the loadlist. The FSS RSO mechanism 29 then compares the list of needed files with an inventory of files that are to be found locally, via step 312, and builds a report of files “needed” for file system synchronization, via step 314.

[0038] The remote sites 14 then report back to the central site 10 upon a pre-defined schedule with the list of needed FSS files, via step 316. Once communications have been re-established, the central site 10 automatically begins the synchronization process, via step 318, and sends both additional files (and may also send commands) as needed, via step 320. If, for example, a remote site 14 has gone down for four days, it will make its comparisons with the last good “loadlist” and current inventory, and will report the list of needed FSS files based only on the latest information.

[0039] Additionally, the remote site 14 will send to the central site 10 a list of all the files that were delivered since the last report back to the central site 10, also via step 316. The ACSO mechanism 27 will then compare the list of delivered files with the list of files that the central site 10 believes the remote site 14 should have, and calculates a list of files that should have been delivered but are “missing” (i.e., the delivered files missing log), via step 322. The ACSO mechanism 27 will then add these missing files to the distribution list for this receiver.

[0040] The reports of needed FSS files, and lists of missing “delivered” files from earlier distribution requests, are handed off to the ACSO mechanism 27, which automatically determines which remote sites 14 share a need for the same files, and then optimizes the distribution of those files for multicasting to various groups of remote sites 14, via step 324.

[0041] Through the use of the “Needed FSS files” as well as the delivered log-based calculations for missing files, files do not need to be transferred that were perhaps once needed for synchronization purposes, but that are no longer needed (such as transient news stories which may have been replaced by updated accounts). A system and method in accordance with the present invention helps ensure that the unneeded files are not transferred while keeping remote site 14 content up-to-date. For example, if a remote site 14 were to go down on the third day of operation, and not return to service until the day six, files would not be automatically transferred that had been needed for days 4 and 5 unless they were specified as needed on day 6.

[0042] The ACSO mechanism 27 then transfers the files much as any other DMD transmission object to the plurality of remote sites 14, via step 326.

[0043] Upon receiving the files, the FSS RSO mechanism 29 interrogates its last known loadlist, which contains fall path information for every file in the NT file system, to determine the final location (i.e., directory) of the file, via step 328, and then moves the file to that directory, via step 330.

[0044] The system and method in accordance with the present invention has the following advantages over conventional systems:

[0045] 1. The system and method is simple and scaleable. The central site 10 only needs to know the loadlist of its own server. No keeping track of each remote site “history file” is required. Work is distributed to each remote site 14. A remote site 14 uses the most recent loadlist and the previously executed loadlist to determine what needs to be transmitted from central site 10 and will send a request to central site 10 via a “missing file list”. When there are hundreds of thousands of remote sites 14 trying to connect back to the central site and sync the file system, figuring out who needs what requires a lot of computation time if all the work is done by the central site is a complex task.

[0046] 2. The system and method operates automatically. The user does not need to be prompted to select the more current data.

[0047] Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims

1. A method of synchronizing files between a central site and a plurality of remote sites comprising the steps of: (a) providing a list of files to the plurality of remote sites by the central site, prior to a callback time of the remote sites; (b) reporting which of the files are missing by each of the plurality of remote sites to the central site; and (c) determining within the central site which of the files needs to be sent to each of the plurality of remote sites.

2. The method of claim 1 in which the providing step (a) utilizes a file system synchronization (FSS) helper application.

3. The method of claim 1 in which the reporting step (b) utilizes a file system synchronization remote site operation mechanism.

4. The method of claim 1 in which the determining step (c) utilizes an automated central site operation mechanism.

5. The method of claim 1 wherein the list of files comprises a loadlist.

6. The method of claim 5 wherein each of the files in the loadlist are date and time stamped.

7. A system for sychronizing files comprising: a central site, the central site including a file system synchronization (FSS) helper application and an automated central site operations (ACSO) mechanism for transmitting the list of files; and at least one remote site, the at least one remote site including a file system synchronization remote operating mechanism (FSS RSO), wherein the FSS RSO mechanism creates a group of files it will need based upon the transmitted files.

8. The system of claim 7 wherein the list of files comprises a loadlist.

9. The system of claim 8 wherein each of the files in the loadlist are date stamped.

10. The computer readable medium containing program instructions for synchronizing files between a central site and a plurality of remote sites, the program instructions for: (a) providing a list of files to the plurality of remote sites by the central site, prior to a callback time of the remote sites; (b) reporting which of the files are missing by each of the plurality of remote sites to the central site; and (c) determining within the central site which of the files needs to be sent to each of the plurality of remote sites.

11. The computer readable medium of claim 10 in which the providing step (a) utilizes a file system synchronization (FSS) helper application.

12. The computer readable medium of claim 10 in which the reporting step (b) utilizes a file system synchronization remote site operation mechanism.

13. The computer readable medium of claim 10 in which the determining step (c) utilizes an automated central site operation mechanism.

14. The computer readable medium of claim 14 wherein the list of files comprises a loadlist.

15. The computer readable medium of claim 10 wherein each of the files in the loadlist are date and time stamped.