Method and system for object retransmission without a continuous network connection in a digital media distributor system

Abstract

The present invention provides a method and system for object retransmission in an asynchronous environment without a continuous network connection in a digital media distributor (DMD) system. The method and system include receiving objects in a receiver from a central site, generating a response document in the receiver, and sending the response document asynchronously to the central site. The received response documents are then utilized in the central site to determine which object to retransmit to the receiver. In another aspect of the present invention, the central site manages the inventory of objects in the receiver by instructing the receiver to delete objects not needed.

Description

FIELD OF THE INVENTION

[0003] The present invention relates to digital media distribution, and more particularly to object retransmission in an asynchronous environment without a continuous network connection in a digital media distributor (DMD) system.

BACKGROUND OF THE INVENTION

[0004] 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.

[0005] Inserting local advertising poses several nontrivial technical, logistical and business challenges. First, literally hundreds of widely distributed local operators (or affiliates) would need to receive the commercials; ad agencies would have to ship analog tapes to hundreds of organizations, with different traffic and billing systems. These tapes would need to be tested for quality assurance, tracked, and stored until needed. They 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.

[0006] 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 provide seamless insertion of national and local advertisements, promotions, and station identifications.

[0007] 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.

[0008] Accordingly, a need exists for an efficient system for retransmission of digital media data in an asynchronous environment to receivers of a digital media distributor system. The present invention addresses such a need.

SUMMARY OF THE INVENTION

[0009] The present invention provides a method and system for object retransmission in an asynchronous environment without a continuous network connection in a digital media distributor (DMD) system. The method and system include receiving objects in a receiver from a central site, generating a response document in the receiver, and sending the response document asynchronously to the central site. The received response documents are then utilized in the central site to determine which object(s) to retransmit to the receiver. In another aspect of the present invention, the central site manages the inventory of objects in the receiver by instructing the receiver to delete objects not needed.

[0010] Through a method and system in accordance with the present invention, the central site manages object retransmission to the receiver in an asynchronous environment without a continuous network connection. Particularly through the implementation of the present invention, streamlined management of retransmission ensures efficient and accurate delivery of objects to the receivers.

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. 3 illustrates a flow diagram showing the process of generating a Response Document in the receiver in accordance with the present invention.

[0014] FIGS. 4 and 4A illustrate a data flow diagram of the Response Document Processor process in accordance with the present invention.

DETAILED DESCRIPTION

[0015] The present invention relates to digital media distribution, and more particularly to object retransmission in an asynchronous environment without a continuous network connection in a DMD system. Objects include assets or spots, which are media files, and system supporting files, which are non-media files. 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.

[0016] In accordance with the present invention, a DMD system provides a complete end-to-end system that gives local cable or network affiliates the ability to provide local ads and announcement insertion together with the delivery of cable or network feeds. In general, the DMD integrates the entire process of sales, traffic, digital encoding and storage of spots, transmission of data, local insertion of digital ads and announcements, account reconciliation, and billing. Assets (i.e., media such as commercials, station identification, public service announcements, etc.) are digitized by the cable or network operator, and then digitally transmitted to the local cable head-ends or network affiliates from a central site. These digital assets are then stored on the receiver servers located at each head-end or affiliate.

[0017] A block diagram of a DMD 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 receiver 14. Generally, receivers 14 are grouped into zones. All receivers 14 within the same zone play the same material at the same time, including all network programs, national spots, local commercials, announcements, etc. 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 receivers 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 receiver(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] Each of the receivers 14 house a receiver server 16. By way of example, a suitable receiver 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 receiver server 16 is a video server that receives and stores digitized spots utilized for local insertion at the cable head-end. The receiver 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 receiver 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 zone, defined by cable or network operators in an area, sells a commercial in the local availability time. The videotaped segment for the commercial is digitally encoded. The digital material is scheduled for delivery to each receiver server 16 prior to broadcast. The playlist, digitized spots, and the broadcast program stream are sent, via satellite, to all of the receiver servers 16 within the zone. All of the receivers 14 within the zone air the local spots for that zone at the scheduled time. As-Run logs are retrieved by the central site 10 from the receiver servers 16. As-Run logs are sent to the local markets, reviewed, reconciled, and customers are billed. Commercials and As-Run logs are then archived.

[0020] The central site 10 efficiently distributes objects and thus manages the resources of the receivers 14. By managing these resources, the central site 10 can determine when to send information to the receivers 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.

[0022] 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 20a and the interfaces to the external systems 20b. The GUI component 20a, e.g., using Lotus Notes, provides administrators and operators with the ability to monitor and control the DMD. The interfaces to external systems 20b 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 receivers 14 which send Lotus Notes messages, and interfaces to encoder systems, which store encoded spot files in a disk pool server for retrieval by the central site server 18.

[0023] Underneath the top layer is a layer 24 of specialized components including a stage manager component 26, an uplink server component 28, a transmission scheduler component 30, and a response document processor component 32. This layer 24 also includes specialized components for creating commands, 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. The response document processor module 32 analyzes and interprets responses from receivers 14. Also included as a next layer is a programming layer 34. The layer 34 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 36 and a hardware layer 38 for the fundamental operation of the central site server 18, as is well appreciated by those skilled in the art.

[0024] The transmission scheduler 30 of layer 24 is responsible for managing transmissions from the central site 10 to the receiver servers 16. The transmission scheduler 30 manages the transmission by executing a plurality of transforms (i.e., bodies of logic that take particular inputs and perform certain operations to produce particular outputs) and utilizing a plurality of queues, as described in co-pending U.S. patent application No. Ser. No. 09/524,082 entitled METHOD AND SYSTEM FOR OPTIMIZATION OF DISTRIBUTION TO REDUCE STORAGE REQUIREMENTS IN A DIGITAL MEDIA DISTRIBUTOR, assigned to the assignee of the present invention, and incorporated herein by reference. Receivers 14, however, may not receive objects that have been transmitted from the central site due to, for example, power outages, satellite problems, or bad weather. Once communications have been reestablished, the central site 10 automatically begins the synchronization process and sends both additional assets and commands as needed.

[0025] In accordance with the present invention, the central site 10 coordinates object retransmission to the receivers 14 through the utilization of the response document processor (RDP) module 32. The RDP module 32 analyzes a response document generated by each receiver 14 in a zone, and determines which, if any, objects to retransmit.

[0026] FIG. 3 illustrates a flow diagram showing the process of generating a Response Document in the receiver in accordance with the present invention. Referring to FIGS. 1 and 3 together, first the central site 10 transmits playout objects to the zone, where the playout objects include assets, playlists, and purge lists via step 100. Next, the objects are transmitted to the receivers 14 via step 110, and received by each receiver (1 through N) 14 in step 115. In a preferred embodiment, each receiver 14 utilizes the objects to manage its inventory and to ensure proper delivery of spots on time. Next, each receiver 14 deletes the files listed on the purge list via step 120. Thereafter, each receiver 14 examines the assets listed on the playlist, compares them with the inventory on hand, and generates a list, the Missing Assets List via step 130. The Missing Assets List provides information concerning which assets are missing and will be needed soon. The generation of the Missing Assets List is described in more detail in co-pending application Ser. No. 09/523,827 entitled, METHOD AND SYSTEM FOR ENSURING RELIABLE PLAYOUT IN A DMD SYSTEM, assigned to the assignee of the present invention, and incorporated herein by reference.

[0027] Next, each receiver 14 will create a log of all objects received within a predetermined time period, via step 140. This log is referred to as the Delivered Files Log. The predetermined time period is referred to as the Receiver Time Window. The objects' respective received times are also recorded.

[0028] Next, each receiver 14 generates a Response Document, which includes the Missing Assets List and the Delivered Files Log, via step 150. In a preferred embodiment, a Content List is also included. The Content List provides the receiver's 14 asset inventory.

[0029] Once the Response Document is complete, it is ready for delivery to the central site 10. Communication between each receiver 14 and the central site 10 is asynchronous, i.e., the receiver 14 periodically reports back to the central site 10 but does not maintain a continuous network connection to the central site 10. The call back times are predetermined and periodic, e.g. every thirty (30) minutes. The time period between call backs for a receiver 14 is referred to as the Receiver Time Window. Thus, as mentioned above, the Delivered Files Log lists the objects received by the receiver during the time between call backs to the central site 10.

[0030] Next, each receiver 14 calls the central site 10 at the receiver's predetermined time, via step 160. Thereafter, the receiver 14 delivers the Response Document to the central site 10, via step 170. In a preferred embodiment, the Response Document is sent to the central site 10 via modem. The scope of the present invention, however, is not limited to any one particular mode of transmission, as one skill in the art would appreciate that other modes of transmission, such as LAN, are available.

[0031] Object retransmission is based on the contents of the Response Documents delivered from the receivers 14 in a zone to the central site 10. At the central site 10, the Response Document Processing (RDP) module 32 (FIG. 2) performs a process to analyze the Response Document from each receiver 14 in a zone. The RDP process is a four step process to determine which objects, if any, must be retransmitted to a zone or receiver 14.

[0032] The first step in the RDP process is to create a purge list for each receiver 14. The second step is to perform a zone level Missing Asset Process to determine which, if any assets, to retransmit to the zone. The third step in the RDP process is to perform a zone level Delivered Files Log Process to determine which objects, if any, to retransmit to the zone. Finally, the fourth step is to perform a receiver level Delivered Files Log Process to determine which objects to retransmit to the receiver 14. To understand the RDP process in more detail, refer now to the following description in conjunction with the accompanying figures. FIGS. 4 and 4A illustrate a data flow diagram of the RDP process in accordance with the present invention.

[0033] Referring now to FIGS. 1, 2, and 4 together, first, in step 200, the central site 10 receives the Response Documents from the receivers 14 in the zone. The RDP process starts by creating a purge list for each receiver 14, via step 210. In this step of the process, the RDP module 32 analyzes the Content List (which reports the asset inventory at the receiver 14) and compares that list to the asset inventory list for the zone. Assets in the receiver 14, but not in the zone, are not needed and are placed on the purge list.

[0034] In the second step of the RDP process, the RDP module 32 performs a zone level Missing Asset process, via step 230, wherein the RDP module 32 analyzes the Missing Assets List section of the Response Document for each receiver 14 and compiles the missing assets for all the receivers 14 in the zone. The RDP module 32 instructs the scheduler module 30 to retransmit all the missing assets to the zone, via step 225. This step of the RDP process is “receiver-centric” because it is based solely on the Missing Assets Lists generated by the receivers 14.

[0035] In the third step of the RDP process, the RDP module 32 performs zone level Delivered Files Log processing, via step 230. Here, the Delivered Files Log is analyzed from the perspective of the zone. In other words, the RDP module 32 examines the files received by all the receivers with received times falling within a Zone Time Window. The Zone Time Window starts when the last Zone Time Window ended, and ends when the first receiver 14 in the zone calls back to the central site 10. Therefore, because the Zone Time Window is determined by the first call back from a receiver 14 in the zone, the Receiver Time Window (i.e., the time period between call backs for a particular receiver) can be slightly offset from the Zone Time Window.

[0036] The RDP module 32 examines the Delivered Files Logs from all the receivers 14, and compares that with the objects the central site 10 transmitted to the zone within the Zone Time Window. The RDP module 32 determines which objects, if any, need to be retransmitted to the zone, keeping in mind that assets in step 225 have already been scheduled for transmission to the zone. The RDP module 32 compares the objects identified in step 230 with the assets already in the retransmit queue from step 225, via step 232.

[0037] By performing step 232, the RDP module 32 optimizes transmission efficiency to the zone because assets already in the queue in step 225 are not retransmitted to the zone more than once. Referring now to FIG. 4A, the scheduler 30 is instructed to retransmit to the zone those objects identified in step 232, via step 235.

[0038] The fourth and final step in the RDP process involves the RDP module 32 performing receiver level Delivered Files Log processing. In step 240, each object in the Delivered Files Log is compared to the objects transmitted by the central site 10 to the zone within the Receiver Time Window. In this process step, the RDP module 32 determines which, if any, objects to retransmit directly to the receiver 14, keeping in mind that objects identified in steps 225 and 235 are already scheduled to be retransmitted to the zone. The RDP module 32 compares the objects identified in step 240 with those already in the retransmit queue from steps 225 and 235, via step 242.

[0039] By performing step 242, the RDP module 32 optimizes transmission efficiency to the receiver 14 because objects retransmitted to the zone are not retransmitted to the receiver 14. In step 245, the scheduler 30 is instructed to retransmit to the receiver 14 those objects identified in step 242. At this point, the RDP process is complete, and the scheduler 30 retransmits the objects to the zone and to the receivers 14, via step 250.

[0040] By analyzing the objects, missing and not received, from the zone and receiver 14 levels, the RDP module 32 can ensure that all the receivers 14 in a zone receive the appropriate assets and command files in a timely manner. Moreover, the four step RDP process ensures that assets already slated for retransmission will not be transmitted more than once to the zone (multicast) or to an individual receiver 14 (uni-cast). Thus, processing time in the central site 10 is minimized and transmission resources are optimized. In addition, the present invention enables efficient object retransmission in an asynchronous environment without a continuous network connection, thereby offering reliable object transmission without heavier network investment.

[0041] Through the RDP module 32 of the present invention, Response Documents, generated by the receivers 14 and provided back to the central site 10 in an asynchronous environment, are analyzed to determine whether object retransmission is necessary. Once the RDP module 32 identifies objects which should have been, but were not, received by on or more receivers 14 in a zone, the RDP module 32 ensures that the objects will be retransmitted to the receivers 14 either through a multicast to the zone or directly. In this manner, the efficient retransmission of objects to the receivers 14 is achieved.

[0042] 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 for object retransmission from a central site to a receiver, the method comprising the steps of: (a) receiving a plurality of objects in the receiver from the central site; (b) generating a response document in the receiver; (c) sending the response document to the central site asynchronously; and (d) determining which of the plurality of objects to retransmit to the receiver based upon the response document.

2. The method of claim 1, wherein the determining step (d) further comprises the steps of: (d1) determining which objects to retransmit to a zone, the zone including a plurality of receivers; and (d2) determining which objects to retransmit to the receiver.

3. The method of claim 2, wherein the central site further comprises a scheduler module for scheduling objects for transmission.

4. The method of claim 3, further comprising the step of: (e) instructing the scheduler to retransmit the objects based upon step (d1) and step (d2).

5. The method of claim 2, wherein the plurality of objects further comprises asset files and system support files, wherein the asset files are media files and the system support files further include an upcoming playlist.

6. The method of claim 5 wherein the response document further comprises a Missing Asset List and a Delivered File Log.

7. The method of claim 6, wherein the generating step (b) further comprises the step of: (b1) preparing the Missing Asset List; wherein the Missing Asset List preparing step (b1) further comprises the steps of: (b1a) comparing the upcoming playlist with an inventory of asset files in the receiver; (b1b) determining which assets are missing in the receiver; and (b1c) listing missing assets in the Missing Asset List.

8. The method of claim 7, wherein the sending step (c) further comprises the step of: (c1) establishing a call back time when the receiver contacts the central site, the call back time occurring at regularly scheduled time intervals, a time period between successive call back times being a receiver time window.

9. The method of claim 8, wherein the generating step of (b) further comprises the step of: (b2) preparing the Delivered File Log, wherein the Delivered File Log contains the plurality of objects received by the receiver and a respective received time for each object of the plurality of objects, the received time being within the receiver time window.

10. The method of claim 9, wherein the determining step (dl) further comprises: (d1a) analyzing the Missing Asset Lists sent by the plurality of receivers in the zone; and (d1b) compiling a list of all missing assets in the zone.

11. The method of claim 10, wherein the determining step (d1) further comprises: (d1c) calculating a zone time window, wherein the zone time window is a period of time starting at a prior zone time window calculation end time and ending when a first receiver in the zone contacts the central site; (d1d) analyzing the Delivered Files Log sent by the plurality of receivers in the zone to compile a list of all objects received within the zone time window by the plurality of receivers in the zone; (d1e) comparing the list of all objects received with an inventory of objects in the zone transmitted during the zone time window; (d1f) compiling a list of all objects missing in the plurality of receivers in the zone; and (d1g) comparing the list of all objects missing in the plurality of receivers in the zone with the list of all missing assets in the zone to determine which objects to retransmit to the zone.

12. The method of claim 11 wherein determining step (d2) further comprises: (d2a) analyzing the Delivered File Log sent by each receiver in the zone; (d2b) comparing the Delivered File Log with an inventory of objects in the zone transmitted during the receiver time window; (d2c) compiling a list of missing objects in the receiver; (d2d) comparing the list of missing objects in the receiver with the objects determined in step (d1) to determine which objects to retransmit to the receiver; and (d2e) repeating steps (d2a)-(d2d) for each receiver in the zone.

13. The method of claim 1 wherein the response document further comprises a Content File List, the Content File List listing a receiver's inventory of objects.

14. The method of claim 13 further comprising the step of: (e) utilizing the response document in the central site to manage the receiver's inventory of objects; wherein the utilizing step (e) further comprises the steps of: (e1) comparing the Content File List to an inventory of objects in a zone comprised of a plurality of receivers; (e2) compiling a list of objects on the Content File List but not in the inventory of objects in the zone; (e3) generating a Purge List comprised of the list of objects compiled in step (e2); and (e4) instructing the receiver to delete the objects listed in the Purge List.

15. A digital media distributor system comprising: a central site for transmitting a plurality of objects; a receiver receiving the plurality of objects, the receiver generating and sending asynchronously a response document to the central site; and a response document processor (RDP) module in the central site for receiving the response document from the receiver, and for utilizing the response document to determine which objects of the plurality of objects to retransmit to the receiver.

16. The system of claim 15 wherein the plurality of objects further comprises asset files and system support files, the asset files being media files, and the system support files further including an upcoming playlist.

17. The system of claim 16 wherein the response document further comprises a Missing Asset List and a Delivered File Log.

18. The system of claim 17 wherein the Missing Asset List is generated by: comparing the upcoming playlist with an inventory of asset files in the receiver; determining which assets are missing in the receiver; and listing missing assets in the Missing Asset List.

19. The system of claim 18 wherein the receiver contacts the central site at regularly scheduled call back times, a time period between successive call back times being a receiver time window.

20. The system of claim 19 wherein the Delivered File Log contains the plurality of objects received by the receiver and a respective received time for each object of the plurality of objects, the received time being within the receiver time window.

21. The system of claim 20 wherein the receiver is one of a plurality of receivers in a zone, and wherein the RDP determines which objects to retransmit to the zone by: analyzing the Missing Asset List sent by the plurality of receivers in the zone; compiling a list of all missing assets in the zone; calculating a zone time window, wherein the zone time window is a period of time starting at a prior zone time window calculation end time and ending when a first receiver in the zone contacts the central site; analyzing the Delivered Files Log sent by the plurality of receivers in the zone to compile a list of all objects received within the zone time window by the plurality of receivers in the zone; comparing the list of all objects received with an inventory of objects in the zone transmitted during the zone time window; compiling a list of all objects missing in the plurality of receivers in the zone; and comparing the list of all objects missing in the plurality of receivers with the list of all missing assets to determine which objects to retransmit to the zone.

22. The system of claim 21 wherein the RDP further determines which objects to retransmit to the receiver by: analyzing the Delivered File Log sent by each receiver in the zone; comparing the Delivered File Log with an inventory of objects in the zone transmitted during the receiver time window; compiling a list of missing objects in the receiver; comparing the list of missing objects in (c) with the objects determined in claim 21 to determine which objects to retransmit to the receiver; and repeating steps (a)-(d) for each receiver in the zone.

23. The system of claim 22 wherein the RPD instructs a scheduler module in the central site to retransmit objects determined in claim 21 to the zone and objects determined in claim 22 to the receiver.

24. The system of claim 15 wherein the receiver is one of a plurality of receivers in a zone and the response document further comprises a Content File List, the Content File List listing a receiver's inventory of objects.

25. The system of claim 24 wherein the RDP manages the receiver's inventory of objects by: comparing the Content File List to an inventory of objects in the zone; compiling a list of objects on the Content File List but not in the inventory of objects in the zone; generating a Purge List comprised of the list of objects compiled in step (b); and instructing the receiver to delete the objects listed in the Purge List.

26. A method for object retransmission from a central site to a receiver in a digital media distributor (DMD) system, the receiver being one of a plurality or receivers in a zone, the method comprising: (a) receiving a plurality of objects in the receiver from the central site; (b) generating a response document in the receiver; (c) sending the response document to the central site asynchronously at a predetermined time; (d) receiving a plurality of response documents from the receivers in the zone; and (e) determining which objects or the plurality of objects to retransmit to the zone and to the receiver based upon the plurality of response documents.

27. The method of claim 26, wherein the central site further comprises a scheduler module for scheduling object transmission.

28. The method of claim 27 further comprising: (f) instructing the scheduler to retransmit the objects determined in step (e) to the zone and to the receiver.

29. A digital media distributor system for transmitting objects to receivers, comprising: a central site for transmitting a plurality of objects; a receiver for receiving the plurality of objects, each receiver being one of a plurality of receivers in a zone, each receiver generating and transmitting asynchronously a response document; and a response document processor module (RDP) in the central site for receiving the response documents from the plurality of receivers, and for utilizing the response documents to determine a retransmission of objects to the zone and to the plurality of receivers.

30. The system of claim 29, wherein the receiver makes asynchronous contact with the central site at regularly scheduled times.

31. The system of claim 29, wherein the RPD instructs a scheduler module in the central site to retransmit the objects to the zone and to the plurality of receivers.

32. A computer readable medium containing program instructions for retransmitting objects from a central site to a receiver, the program instructions for: a) generating a response document in the receiver based on objects received from the central site; b) sending the response document to the central site asynchronously; and c) determining which objects are to be retransmitted based upon the response document.

33. The computer readable medium of claim 32, wherein the determining instruction (c) further comprises programming instructions for: (c1) determining which objects to retransmit to a zone comprised of a plurality of receivers; and (c2) determining which objects to retransmit to the receiver.

34. The computer readable medium of claim 33, wherein the central site comprises a scheduler module for scheduling objects for transmission.

35. The computer readable medium of claim 34, further comprising program instructions for: (d) directing the scheduler to retransmit the objects based upon step (c1), and step (c2).