Abstract:
A method for digital data distribution or broadcasting that takes advantage of non-deterministic (or “opportunistic”) unused bandwidth in dynamically optimized broadband digital broadcast systems. Digital data files received from broadcasts are stored in mass storage devices for viewing at a later time at high speed, overcoming “last mile” narrow bandwidth issues. Instead of reserving a particular communications channel or data transfer spectrum, data is opportunistically “piggybacked” onto unrelated broadcasts, using otherwise unused bandwidth within existing broadcast channels or spectrums. The broadcast source does not target the digital files at specific identifiable users or broadcast contents based on their interactive requests. Data broadcasting in accordance with the present invention may be implemented to work with any medium which allows the delivery of large files in a one-to-many fashion (i.e., “broadband broadcast medium”), such as digital cable, digital broadcast satellite, terrestrial digital television, and computer networks that are broadcast-enabled and sufficiently broadband.

Description:
BACKGROUND OF THE INVENTION  
         [0001]    1. Field of the Invention  
           [0002]    This invention relates to data broadcasting, and more particularly to a method and apparatus for opportunistically broadcasting rich media digital content.  
           [0003]    2. Description of Related Art  
           [0004]    Existing methods and devices for the transmission of digitized content each suffer from a number of inherent limitations on their ability to distribute rich digital content such as movies, video games, audio and other large digital files to large numbers of users quickly, efficiently and inexpensively. These limitations on file size and/or audience size present a significant barrier to the growth of electronic commerce for mass-market content and digital distribution.  
           [0005]    While the Internet has emerged as a powerful tool for distribution of digital content, it is optimal when used as a means of transporting unique data from many sources to many destinations (many-to-many distribution) at a system level. However, at an operational level, the Internet is in effect point-to-point, based on one-to-one communication (i.e., in a unicast environment, in which a node has the ability to send to only one other node at a time). This means that a separate data stream must be reserved to serve each user individually during data transmission. For example, when a large group of N people want the same information, the information server has to send it out either N times or in a single operation as in multicasting to N specific client addresses, via N specific transmission paths. Technological limitations (including bandwidth) and the basic architecture of the Internet as a network of networks render it cumbersome and relatively expensive as a means for mass distribution of large digital files from a single source. The limitations even apply to mass simultaneous distribution of small digital files.  
           [0006]    Methods have been developed to move content closer to the end user by storing copies of the content on multiple, geographically distributed servers, located for example at local Internet Service Providers (ISPs). This technique avoids the need to move the content from a single, centralized server through potentially a large part of the Internet to reach the user. Companies such as Digital Island, Akamai, and iBeam provide such systems. However, these systems still have a “last mile” bandwidth limitation problem. In fact, these companies have either shut down, gone bankrupt, or are in financial distress. While a number of methods have been developed for multi-cast distribution of rich content using transmission over coaxial cable, fiber optics and a variety of other broadband transmission systems, they do not solve the infamous “last mile” problem at the “edge” of the data network. A number of solutions, most notably DSL (digital subscriber line) and high speed cable access have emerged to attempt to address the last mile problem, but the effectiveness of these solutions have met with mixed results, due in part to their failure to address the unicast problem.  
           [0007]    Further, past systems did not adequately address some of the practical aspects of data transmission that relates to the nature of the content, usage and applications based on the data network. For example, prior pay-per-view (PPV) systems exhibit significant limitations for transmitting programming content in near video-on demand (NVOD) or video-on-demand (VOD) systems. In conventional NVOD systems the user selects and orders content, such as a movie, from a predetermined schedule. The PPV provider transmits the content in real-time in accordance with the predetermined schedule, sometimes repeatedly transmitting the same content for use at predetermined times. When an order is placed, the purchased program is unscrambled by a proprietary decoding receiver and made available for viewing by the user in real-time.  
           [0008]    VOD systems differ from NVOD systems in that the user may order any content from a list of available titles in the provider&#39;s library. For a true VOD system, the content is available at any time on demand by the user, and may be transmitted to the user in a number of ways, including both real-time transmission and burst transmission in a period of time that is substantially less than real-time. In many VOD systems, the user has enhanced control of use of the content as compared to real-time NVOD systems. For example, movies transmitted using a VOD system may be stored at the point of use, and thus the user may exercise VCR-type control during playback of the movie such as stop, pause and rewind functions. It is also possible to achieve such VCR-type control using real-time transmission by sending commands from client to server. While convenient to users, VOD systems are complex, costly and relatively inefficient in both server utilization and transmission bandwidth.  
           [0009]    U.S. Pat. No. 5,710,970 to Walters sought to overcome some of these limitations of NVOD and VOD systems by using short cycle burst transmission of audio/video programming. Walters teaches the cyclic distribution of audio/video program information in a burst of time that is substantially less than the time required for real-time viewing of that audio/video programming. This method takes advantage of the lower costs associated with NVOD systems, while providing more content and in some instances VCR-type control to the user.  
           [0010]    Walters teaches an apparatus that includes a central library storing a multiplicity of time compressed digital audio/video programs that may be selectively transmitted in a burst time period to corresponding storage at one or more remote subscriber locations where the program would be decompressed and viewed. The central library provides cyclic, predetermined transmission of the programs, and a receiver at the user&#39;s location continuously monitors the communications channel over which the sequential stream of compressed program data is broadcast, but stores only the programs that have been ordered by the user.  
           [0011]    The method and apparatus taught by Walters, however, is a point-to-point transmission system, which requires the allocation of a specific communications channel in an ATM (asynchronous transfer mode) network, for transmission of the program data at a relatively high cost. In addition, because the method selectively stores only the program or programs ordered by the user, the transmission cycles must be extremely short to avoid delays between the time a program is ordered and the time it is delivered to the customer. Short transmission cycles require frequent retransmission of the same data, seriously limiting the number of different programs that can be offered per communications channel and resulting in significant inefficiencies and underutilization of bandwidth.  
           [0012]    Broadcasting is the most effective way to deliver popular media to a mass audience because it is a one-to-many distribution method wherein the bandwidth capacity is not dependent on the number of users tuned to a given broadcast. For example, local television stations broadcast the same TV show to every home at the same time. Content providers can distribute popular programs to millions of people at the same time, and at the same speed. Whether a telecast is viewed by one or one hundred households, the cost of transmission via the established broadcasting network is the same.  
           [0013]    Until recently, broadcasting has also presented significant limitations as a means for the distribution of rich digital content, including lack of methods and apparatus for economically and efficiently using broadcast bandwidth, lack of methods and apparatus for receiving and managing content, and lack of a standardized digital broadcasting infrastructure, and in particular a standardized wireless digital broadcasting infrastructure. In response to legislation, television stations have now established a significant digital broadcast infrastructure, which will continue to develop over time. However, the existing capacity and infrastructure of digital broadcasting are currently under-utilized by the television broadcast networks.  
         SUMMARY OF THE INVENTION  
         [0014]    The present invention takes advantage of the existing digital broadcast capacity and infrastructure, and overcomes the remaining limitations in the prior art by taking advantage of non-deterministic (or “opportunistic”) unused bandwidth in dynamically optimized broadband broadcast systems and by using inexpensive storage devices for mass storage of digital data files received from broadcasts which can be viewed at a later time by the user. When viewed later by the user, the data is retrieved from the user&#39;s local disk storage at high speed, thereby overcoming the “last mile” bandwidth problem. The present invention does not require reservation of a particular communications channel or data transfer spectrum. Instead, data is opportunistically “piggybacked” onto unrelated broadcasts, using otherwise unused bandwidth within existing broadcast channels or spectrums. The broadcast source does not target the digital files at specific identifiable users or broadcast contents based on their interactive requests.  
           [0015]    In one aspect of the present invention, it possesses at least the following characteristics:  
           [0016]    a. non-deterministic schedule and bandwidth; the present invention uses the same channels that are being used for regular broadcasting by the stations, and need not create new channels, in a non-deterministic schedule and bandwidth fashion;  
           [0017]    b. enhancement of a medium designed for one use (e.g., audio-video programming) by other uses (e.g., movies game download);  
           [0018]    c. orthogonal revenue stream, in that more video programs or more fidelity do not increase advertising revenue; the services provided in accordance with the present invention create a new revenue stream for broadcast stations (or satellite or digital cable provider, etc.); and  
           [0019]    d. extremely useful for delivering relatively large and/or highly demanded files of digital content simultaneously to many users, such as video, audio, game, software, and web content.  
           [0020]    Data broadcasting in accordance with the present invention may be implemented to work with any medium which allows the delivery of large files in a one-to-many fashion (i.e., “broadband broadcast medium”), such as digital cable, digital broadcast satellite, terrestrial digital television, and computer networks that are broadcast-enabled and sufficiently broadband. In one aspect of the present invention, data broadcasting is conducted via wireless transmissions. In a further aspect of the present invention, data broadcasting is conducted via wireless transmissions based on unused bandwidths in audio-visual broadcasting such as terrestrial digital television broadcasting.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0021]    [0021]FIG. 1 is a block diagram of the digital data broadcasting architecture in accordance with the present invention.  
         [0022]    [0022]FIG. 2 is a schematic diagram illustrating a data broadcasting network configured in accordance with one embodiment of the present invention.  
         [0023]    [0023]FIG. 3 is a block diagram showing the functional components of the publishing services, transport services, subscriber services, and back office services, corresponding to the overall architecture of the data broadcasting network in accordance with one embodiment of the present invention.  
         [0024]    [0024]FIG. 4 is a block diagram showing the interactions of the functional components of the various services to handle information flow for the overall architecture of the data broadcasting network in accordance with one embodiment of the present invention.  
         [0025]    [0025]FIG. 5 is a schematic diagram of a local television station.  
         [0026]    [0026]FIG. 6 is a block diagram illustrating the use of opportunistic bandwidth in an IP-based network.  
         [0027]    [0027]FIG. 7 is a schematic diagram further illustrating IP encapsulation of two digital data streams.  
         [0028]    [0028]FIG. 8 is a block diagram illustrating the primary receiver hardware components.  
         [0029]    [0029]FIG. 9 is a block diagram illustrating the architecture of a receiver/storage device in accordance with one embodiment of the present invention.  
         [0030]    [0030]FIG. 10 is a functional block diagram illustrating the client architecture of the data broadcasting network in accordance with one embodiment of the present invention.  
         [0031]    [0031]FIG. 11 is a block diagram showing the basic data groups used in the preferred embodiment.  
         [0032]    [0032]FIG. 12 is a flow chart illustrating the flow of data from reception to scheduling for acquisition.  
         [0033]    [0033]FIG. 13 is a flow chart illustrating the flow of data from scheduling for acquisition to storage.  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0034]    The present description is of the best presently contemplated mode of carrying out the invention. This description is made for the purpose of illustrating the general principles of the invention and should not be taken in a limiting sense. The scope of the invention is best determined by reference to the appended claims.  
         [0035]    The present invention substantially overcomes the bandwidth limitations in the prior art data mass distribution systems, and reduces the difficulties and disadvantages associated with other techniques of distribution of rich media digital content. To facilitate an understanding of the principles and features of the present invention, they are explained herein below with reference to its deployments and implementations in illustrative embodiments. By way of example and not limitation, the present invention is described herein below in reference to examples of deployments and implementations in the TV broadcast environment. The present invention can find utility in a variety of implementations without departing from the scope and spirit of the invention, as will be apparent from an understanding of the principles that underlie the invention.  
         [0036]    The detailed descriptions that follow are presented largely in terms of methods or processes, symbolic representations of operations, functionalities and features of the invention. These method descriptions and representations are the means used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. A software implemented method or process is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. These steps require physical manipulations of physical quantities. Often, but not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated.  
         [0037]    Useful devices for performing the software implemented operations of the present invention include, but are not limited to, general or specific purpose digital processing and/or computing devices, which devices may be standalone devices or part of a larger system. The devices may be selectively activated or reconfigured by a program, routine and/or a sequence of instructions and/or logic stored in the devices. In short, use of the methods described and suggested herein is not limited to a particular processing configuration.  
         [0038]    It is noted that in prior publications, the terms “broadcast” and “data broadcast” are used in a different context as compared to the invention described herein. For example, in U.S. Pat. No. 5,710,970 to Walters discussed in the Background section, it describes a point-to-point data transmission system, which is not a true one-to-many broadcast system. It is therefore unrelated to data broadcasting as in the present invention.  
         [0039]    Prior to discussing the details of the inventive aspects of the present invention, it would be helpful to define some of the terms in the context used throughout this specification:  
         [0040]    bandwidth: The amount of data that can be transmitted via a given channel within a given time.  
         [0041]    broadcast: To make a signal available via a data mass distribution system to any receiver configured for bitstream selection, such as by frequency tuning to the data broadcast channel, IP address listening, multicast group joining, and/or analogous processes.  
         [0042]    multicast: To send a signal to multiple receivers.  
         [0043]    unicast: To send a signal to a receiver.  
         [0044]    computer network: A bi-directional communications, data exchange and resource sharing system created by linking two or more computer nodes and establishing standards, or protocols, so that they can work together. A computer network may also serve as a broadcast network in uni-directional data mass distribution.  
         [0045]    broadcast network: A uni-directional data mass distribution system created by linking two or more broadcasting stations or intermediary stations, for broadcasting content over a wide area.  
         [0046]    channel: A path along which data is transmitted in a data mass distribution system; a broadcast channel may be associated with a particular data transmission frequency span, a particular IP address, an IP multicast address, and/or analogous bitstream selection means.  
         [0047]    Referring now to FIG. 1, there is shown a block diagram illustrating the basic architecture of the digital content broadcasting system in accordance with the present invention. Rich media content, including without limitation, movies, music, video games, software and publishing, is provided by content publishers or distributors  100  to the network operations center  110 . The network operations center  110  processes and formats the content data and provides it to local television stations  120 . The local television stations  120  then opportunistically broadcast the content to receivers/storage devices  130  where it is stored for use by the customers.  
         [0048]    Referring now to FIG. 2, there is shown a more detailed schematic illustration of the distribution system used to implement the present invention. Rich media content is first provided by the publisher or distributor to the content ingestion center  210 , where the data comprising the content is staged and packaged as described more fully below. The content can be provided in any form, including physical media such as digital versatile disk (“DVD”), CD-ROM and magnetic media, as well as networked media such as satellite and Internet connectivity.  
         [0049]    The packaged and staged data is then stored to the national programming server  220  by network management  230 . The network operations center  110  then distributes the staged data packets to local television stations  120  or local station nodes via a virtual private network (“VPN”) using satellite and terrestrial bandwidth providers  240 .  
         [0050]    Each local television station  120  will be equipped with network equipment that interconnects the local node to the VPN and stores the staged data packets received from the network operations center  110 . The network equipment will interface with the local programming server  260  to manage subsequent broadcast by means of a digital television data injector and a digital television antenna  270 , as described more fully below.  
         [0051]    The data broadcast is then picked up by the antenna  280  of the user&#39;s receiver/storage device  130  and is stored in the receiver/storage device until accessed by the user. The receiver/storage device will initially be a universal serial bus (“USB”) appliance or a PCI card attached to a computer with a standard web browser and network application software. Over time, it is anticipated that receiver/storage devices will be integrated into personal computers and other digital devices, including digital televisions, Internet appliances, mobile digital computing products and personal digital recorders (“PDR”, such as the TiVo system).  
         [0052]    Overall, data packets in time domain in MPEG format are scrambled and transmitted at the transmitter end. The data packets are unscrambled to time domain at the receiver end. The data staging and packetizing process will now be described in more detail. When digital content arrives at the content ingestion center  210 , it is downloaded onto a secure storage system. It is then staged with a variety of information as requested by the content provider, including metadata and any content protection. The data is then IP protocol encapsulated (using for example ATSC A/90 standard or DVB MPE—EN 301 192—standard), so that the resulting packetized, staged data can be throughput to the national programming server  220 . At the network operations center, the metadata (including an announcement stream and user interface data) are updated and the packetized staged data is prepared for distribution to the local nodes or local television stations through the VPN described above. The announcement stream contains information about the data being broadcast, allowing the receiver to select the data of interest; it is associated with the meta-data ascribed to the data content. The transmitter metadata mirrors the receiver metadata, including, for example, information identifying the content provider, the acquisition priority, a profile for the transmission group, content categories and type subgroups, channel and packet identification, start-time, end time, storage information (e.g., purging information), file descriptor, application usage, action to be undertaken, and cache management information, etc.  
         [0053]    [0053]FIG. 3 is a block diagram showing the functional components of the publishing services, transport services, subscriber services, and back office services, corresponding to the overall architecture of the data broadcasting network. FIG. 4 is a block diagram showing the interactions of the functional components of the various services to handle information flow for the overall architecture of the data broadcasting network. Referring also to FIG. 2, the publishing services, subscriber services, and back office services may be implemented at the network operations center  110 .  
         [0054]    Referring now to FIG. 5, the operation of a local station or node will be described in more detail. Once the packetized staged data has been distributed out to the local nodes or local television stations through the VPN described above, the local nodes store the packetized staged data to be broadcast on secure servers  310 . The local programming server  320  manages the packetized data and controls its insertion into the broadcast stream using data transmission engines  330  and a digital television data injector  340 .  
         [0055]    Referring now to FIG. 6, the injection of the packetized staged data into the digital broadcast stream will be described in more detail. For broadcasting, the network utilizes excess bandwidth in the 19.4 Mbps ATSC Broadcast Transmission system of this embodiment. Data is opportunistically inserted into the MPEG stream by encapsulating the IP datagrams into MPEG packets using the Multi-Protocol Encapsulation specification found in the DVB specification EN 301 192. To complement the transmission, the ATSC receiver/storage device discussed below is responsible for providing and creating all routines, such as DirectShow filter graphs, such that the encapsulated IP datagrams are rendered to the IP stack. (DirectShow is a Microsoft Windows-specific implementation. Other equivalent or substitute methods exist on other platforms, e.g., set-top boxes.) It will be seen that this allows the local node or station to manage and transmit any IP based content, while simultaneously allowing multiple standard definition television signals or a single high-definition television signal over the ATSC 8-VSB transmission standard (a part of the ATSC A/53 standard).  
         [0056]    Referring specifically to FIG. 6 and FIG. 7, at the content ingestion center  210 , content including video and/or audio are processed by a station encoder and multiplexer  410  to produce a transport stream (A) having X % null (N) packets. An IP Encapsulator replaces some null packets with content packets (Y) to produce a transport stream of XY % null packets, which is transported by a transmitter  440  downstream of the system. A local programming server  430  (e.g., an “iBlast” server operated by the assignee of the present invention) communicates with the IP Encapsulator  420  and provides the IP data (Y) to the IP Encapsulator  420 .  
         [0057]    Referring to FIG. 8, at the receiver, a tuner  460  outputs a signal of intermediate frequency (which could also be a baseband frequency—depends on particular demodulator chip used), which is demodulated by a demodulator  470  into a transport stream. An interface  480  such as a USB or PCI based interface couples the transport stream for further processing and/or storage. In certain implementations, a hardware demultiplexer exists between demodulator  470  and interface  480 . The hardware demultiplexer reduces software processing requirements.  
         [0058]    The operation of the receiver/storage device will now be described in more detail. As set forth above, the receiver/storage device will initially be a universal serial bus (“USB”) appliance or a PCI tuner card attached to a computer with standard web browser and network application software. It is anticipated that a wide variety of digital devices will be developed to function as receiver/storage devices, including digital televisions, set-top boxes, internet appliances and mobile digital computing products.  
         [0059]    Referring now to FIG. 9, the architecture of the receiver/storage device is made up of four (4) distinct layers: hardware layer  510 , software driver layer  520 , middleware layer  530  and application layer  540 . The hardware layer consists of an ATSC tuner demodulator  511 , in some instances equipped with a smart steerable antenna for locations with multiple transmitters. The software driver layer  520  consists of an ATSC tuner driver  521 , transport stream demultiplexor  522 , IP renderer  523 , an IP sink  524 , an IP security module  525 , and an IP stack  526 . The ATSC tuner driver sets the reception frequency and controls the ATSC tuner for channel selection. As illustrated in FIG. 10, the software driver layer  520  directs the flow of incoming content data, demultiplexes the content packets from the main data stream using either software or hardware demultiplexing, and moves it into the IP stack together with other incoming content from direct Internet connections for handling by the middleware layer.  
         [0060]    The middleware layer  530  controls all content data acquisition and management for the receiver/storage device. The middleware layer  530  is a meta-data driven application. To understand the operation of the middleware layer  530 , it is helpful to understand how the content data is organized for transmission. Referring now to FIG. 11, a package  610  contains one or more transmission groups  620 . A transmission group  620  contains one or more items  630  and each transmission group  620  has a unique identification (“ID”) code. An item  630  is a unique piece of content, which may be an individual file such as a movie, or a collection of files such as a web site.  
         [0061]    Using identifying meta-data in the incoming data packets, the middleware  530  can tune to a particular channel, identify the available transmission groups  620 , select which transmission groups  620  to capture, and manage the cache memory where incoming data is stored. Meta-data tags must be provided for all transmission groups  620  to define the reception attributes for the items in each transmission group  620 . Meta-data tags are optional on packages of transmission groups  620  and on items. If an item arrives without meta-data, the middleware will create a minimum set of meta-data automatically.  
         [0062]    Transmission group  620  meta-data tags contain critical information and commands used by the middleware to manage the operation of the receiver/storage device. For example, transmission group  620  tags may include information identifying the content provider, the acquisition priority to resolve conflicts in acquiring content from different channels, a profile for the transmission group  620 , content categories and type subgroups, channel and packet identification, start-time, end time and purging information.  
         [0063]    Referring again to FIG. 9, the general operation of the middleware  530  in managing reception and storage of content will be described further. Once the ATSC tuner  511  has been set to a proper channel and data is being received, the middleware  530  acquires or updates meta-data from the announcement stream, which is present on all frequencies used by the network, and is identical across all frequencies, since it describes all data concerning the broadcasts at all frequencies in a given market. In other words, it aggregates meta-data across all broadcast network stations in a given market. This allows the receiver to ascertain all available data concerning the broadcasts at all frequencies by tuning to only one channel at one time. This meta-data file is transmitted on a periodic basis and provides configurable look-ahead capability, which in this embodiment is on the order of several days, to allow planning for content acquisition well in advance and to allow the user to look up the acquisition queue when the receiver/storage device is powered up.  
         [0064]    The meta-data file is fed to the file manager  531  for meta-data parsing and initial profiling and filtering of data to identify and schedule transmission groups  620  for acquisition. Together with trigger data and announcement data, this information is fed to the queue management and conflict resolution manager.  
         [0065]    [0065]FIG. 10 is a functional block diagram illustrating the client architecture of the data broadcasting network in accordance with one embodiment of the present invention. This diagram shows the interaction of the functional blocks of the receiver described in connection with FIG. 9 and the subscriber servers (see FIG. 3), and additional functions that complement the system. As can be seen, some of the functional blocks in FIG. 10 were described above in connection with FIG. 9.  
         [0066]    [0066]FIG. 12 illustrates this operational flow to the queue management conflict resolution manager  532 . Metadata schedule, PID, and channel information is updated using SAP/SDP packets broadcast on approximately an hourly basis. In another embodiment, XML is used as the metadata format.  
         [0067]    Referring now to FIG. 13, the operational flow from queue list creation to storage is illustrated. When the time to acquire a transmission group  620  in the acquisition queue arrives, the middleware  530  checks the channel and PID information, resolves any scheduling conflicts, then sends the acquisition request to the content receiver  533 . The cache manager  534  checks to determine whether there is sufficient cache space for the acquisition, and purges the lowest priority items in the cache to make room and/or requests more cache room (e.g., from the system or the user). Once sufficient room is available, the transmission group  620  is acquired. Items  630  in the transmission group  620  are checked for meta-data, and if not present it is created. The meta-data for each item  630  is then placed in the cache database and purge events are scheduled. In another embodiment, the cache manager “sweeps” the cache on a regular basis to comply with metadata-specified requirements of, e.g., total cache size.  
         [0068]    The content receiver  533  reassembles and stores the content in the cache on, e.g., hard disk. Other media for storage may be used instead, such as RAM, magnetic media, DVD, CD ROM or a combination of such media. This content is then accessed by the user through the application layer  540 , using standard Internet and PC application programs.  
         [0069]    The middleware layer  530  also provides for collection of statistics, IP security controls, and communication with the network via an Internet back-channel. The cache is managed based on the amount of storage available, the priority assigned to stored content and purge instructions, if any, for particular items.  
         [0070]    In this embodiment, the network will opportunistically broadcast different content simultaneously on a plurality of channels or frequencies. The meta-data file will be broadcast on all channels or frequencies, as will metadata updates provided in SAP/SDP packets (latter not required). In an alternate embodiment, XML will be used instead of SAP/SDP. This system provides for the one-to-many transmission of huge quantities of content data, on a flexible schedule (may be predetermined, periodic, or opportunistic) that can be updated or revised. Data transmission speeds exceed other broadband connections such as cable modem and DSL by approximately 18× and dial up connections by approximately 125×, at substantially lower costs per megabyte of data. By opportunistically accessing unused digital spectrum, the invention allows each local television station in the network to broadcast additional rich media digital content in large file sizes in any given day without requiring additional bandwidth. For example, for a given ATSC broadcast station that broadcasts video 24-hour-a-day averaging about 4 megabits per second (which leaves roughly 15 megabits per second unused), the invention can broadcast upwards of 150 gigabytes per day. A minimum of 75 gigabytes of data per day can be achieved quite readily. For markets with multiple local stations, minimum distribution of multiples of 75 to upwards of 150 gigabytes of data or more per day are possible.  
         [0071]    It will be appreciated that this embodiment is only one implementation of the invention, which involves a national or regional broadcast network. The invention could also be implemented in a local system employing the same basic elements of content ingestion, staging and packetizing the data, cyclical data injection and broadcast, and reception and storage management without departing from the scope and spirit of the invention.  
         [0072]    References are made to the following publications by iBlast, Inc., the assignee of the present invention, concerning data broadcasting: (1) A Standards-based Data Broadcasting Network, by Pete Lude (SMPTE Pasadena, Calif. Oct. 19, 2000); (2) Balancing Bandwidth and Bytes: Managing storage and transmission across a datacast network, by Pete Lude and Dan Radke; and (3) iBlast Data Broadcasting Field Tests—A Study to Understand and Quantify Reception of the ATSC Signal, by Andrew Miller et al. (Apr. 23, 2001). These publications were available on iBlast&#39;s website (http://www.iblast.com) at least as early as Apr. 23, 2001 (the filing date of the present application), and are fully incorporated by reference as if fully set forth herein.  
         [0073]    While the invention has been described with respect to the described embodiments in accordance therewith, it will be apparent to those skilled in the art that various modifications and improvements may be made without departing from the scope and spirit of the invention. For example, the inventive concepts herein may be applied to wired or wireless system, based on IP, or other protocols, for entertainment, business, commercial or other types of digital content applications, without departing from the scope and spirit of the present invention. Accordingly, it is to be understood that the invention is not to be limited by the specific illustrated embodiments, but only by the scope of the appended claims.